Database Develop

[REQ]Kaiser (tilt) backlight

Hello, I was doing some thinking after using Android on the kaiser. What about having the backlight fade out while not in use and fade in when touched, much like Android or any of the newer HTC's?
If it worked in Android already then it should be somewhat easy to do in WM if it can be controlled.
Basically the backlight would dim from the user set amount to something close to being totally off, but not actually off. then when used it would quickly and smoothly fade back to the users setting.
Though i'm not a developer (skinner really) anyone want to try to do it? And anyone interested in something like this?

I think this would be great for the Kaiser and would welcome this feature...

Yes please fix this stupid backlight issue on our Kaiser. I would like to see the above fix worked out.

I think this would be a excellent addition to the tilt!
Anyone know if there is a method to accomplish this?

i like the sound of it

Me too! If it can happen in anroid, I am sure it can happen in WM as well! Maybe some software guru can help us out...

ai6908 said:
Me too! If it can happen in anroid, I am sure it can happen in WM as well! Maybe some software guru can help us out...
Click to expand...
Click to collapse
I believe that those newer models have additional components that make this happen. (PROXIMITY SENSOR I THINK). and since we dont have it, the only possible way would be to have the phone dim really low, but still be active(not standby), and your phone would basically never be allowed to go into standby(battery killer).
thats what i think thou, nothing official.

thats weird,i watched my tilt and it dimmed like my g1 did ,just not as dark,and if i wait longer it will shut off the screen ,like the g1.but when the screen shuts off on the g1 the phone gets locked and you have to press a button then menu to unlock it or slide it open,on the tilt i just press the power button and the screen comes on or sliding it open.

Best lock/unlock app

Hello
wanted to get everyone's opinion to whats the best lock app for our phones. i have tried several and i have problems with a lot of them.
i really like phone buddy, but i find it uses too much memory and power.
pocketshield is good too but i had problems with it. the phone wouldnt stay locked and i think i had a memory problem as well.
s2u2 is what i have used before and i do like it. but i had a problem with the volume on calls.
not sure if its something else im running.. im running the diamond2 g sensor and that may be it. or something else... not sure
help and suggesting would be great. i would like to find something i can use on my phone.
thanks

Mayonesa said:
pocketshield is good too but i had problems with it. the phone wouldnt stay locked and i think i had a memory problem as well.
Click to expand...
Click to collapse
pocketshield. best i've found, no impact on battery life and answering the phone is great. download the latest (they've been updating it alot) and turn off the shake wake up (gestures), light wakeup, center button, and stylus (so the only thing is slide down). i haven't had it wake up unexpectedly with those settings.
i tried s2u2 along time ago, but have heard from multiple sources that it negatively influenced battery life. anyone know if this is still true?

i liked pocketshield a lot but like i said, i turned the phone off so it would lock, as soon as i turned the phone on it would unlock without me fliping it or anything else.
the answer thing is nice but i like the slide to answer i already have. if it didnt disable that when i used the pocketshield one i would use it.
like i said, im not sure if something else if causing my issues.... i think i may uninstall the dimond2 g sensor.

still cant find any lock app that will work well.... sensorlock and glocker dont work at all. and pocketshield works for a short time but stops. not sure if its cause you have to pay for it. i would pay for it if it worked for a while with no problems. dont wanna pay for it and have the same problems.
any ideas?

S2U2
try using S2U2 fully configurable and if done right does not use up battery.
http://www.ac-s2.com/

I use S2U2. Doesn't affect my battery life

using S2U2 with tPro skin... nice

jcylcruzin said:
try using S2U2 fully configurable and if done right does not use up battery.
http://www.ac-s2.com/
Click to expand...
Click to collapse
S2U2 is my favorite.
On a fast ROM (Like most of the ROM's on our forums), the program runs smoothly and nice.
I also like being able to pick pictures of my dog, or my bike, for the screens.
But my best practice for locking the phone is simply lock it out of habit when you put it away. Have "Slide to wake" disabled unless you really use it.

pocketshield for me, i had a few issues in the earlier releases but the newest is absolutely perfect, and pretty much everything is configurable to how i like it! seriously try the new one out and play in the settings to tweak it

Just use the new vertion of S2u2 together with the new skin
http://forum.xda-developers.com/showthread.php?t=467435
Works without problem. and looks good.

Mayonesa said:
...
pocketshield is good too but i had problems with it. the phone wouldnt stay locked...
Click to expand...
Click to collapse
Maybe you have "light unlock" enabled and it is unlocking before you even notice it? (actually its the way it should be if you enable that feature)

has anyone tried throttle lock ? it has a slide to answer when you recieve calls while locked and it unlocks by drawing a pattern on a 3X3 grid of dots . Its a real nice app and has at least 35 different skins and is customizable. (customizing is rather arduous and takes awhile to do when it comes to making a new skin)

can anybody help me find Phone Buddy? i was trying to search it and i am not getting an conclusive results. The only thread that cmae up with anything is this thread....

S2U works just fine on my TP with stock rom, no negative battery impact noticable.

It seems all locking programs seem to have their own 'locked screen' that goes over the today screen. I have customized my today screen to have all the information i need at a glance and don't need another one.
I think Touchlock Pro is the only recent one that does not have this but I have other issues with it. Are there others I have missed?

Sunra said:
It seems all locking programs seem to have their own 'locked screen' that goes over the today screen. I have customized my today screen to have all the information i need at a glance and don't need another one.
I think Touchlock Pro is the only recent one that does not have this but I have other issues with it. Are there others I have missed?
Click to expand...
Click to collapse
I'm using AnswerkeysDisabler which locks the touch screen completely when a call comes in. Answering is only with the hardware keys. It's simple - no home screens, no swinging the phone around in circles to answer or anything Just plain works (as touch pro has those HW keys).
I found it from here somewhere - try it.

I use sensor lock. It's great! You can use phone gestures with the accelerometer to unlock your phone. For example, you can rotate your phone 360º to lock/unlock it.
Here is the app. http://forum.xda-developers.com/showthread.php?t=422871

[Q] Screen inaccuracy issues

I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?

Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.

It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.

I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App

msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.

It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).

Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!

Most probably replaced the phone's MB.

Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...

I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.

ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App

pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?

xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.

The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.

Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.

The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.

Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.

Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App

[Q] That screen...

I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."

I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!

Is there an FAQ about this digitizer issue?

JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once

DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.

JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.

Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?

JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me

Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733

JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.

Multitouch with +5 fingers

****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.

When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.

JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones

Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.

pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine

Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?

anyone ?

This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO

nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem

It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?

thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.