Hello everyone. I have an AT&T Tilt, and it's great so far, except for two issues:
1) After I end a phone call, the backlight seems to go off and the screen is very dim. Pressing keys does not bring the backlight back. If I power the screen off and on, the backlight comes back on and the screen is at its normal brightness.
2) I lock my AT&T Tilt using the "Device unlocked" area on my home screen, and when I unlock the phone, sometimes it asks for my PIN, and sometimes it just shows the unlock button on the screen. My settings are for a 12 hour timeout.
If anyone can shed any light on possible fixes to these issues, that would be great. Thanks!
mrbofus said:
Hello everyone. I have an AT&T Tilt, and it's great so far, except for two issues:
1) After I end a phone call, the backlight seems to go off and the screen is very dim. Pressing keys does not bring the backlight back. If I power the screen off and on, the backlight comes back on and the screen is at its normal brightness.
2) I lock my AT&T Tilt using the "Device unlocked" area on my home screen, and when I unlock the phone, sometimes it asks for my PIN, and sometimes it just shows the unlock button on the screen. My settings are for a 12 hour timeout.
If anyone can shed any light on possible fixes to these issues, that would be great. Thanks!
Click to expand...
Click to collapse
I have the same issue after a phone call....
Same issue here too... it doesn't happen when on USB-power... and I don't remember it doing this before the security-Exchange policy was forced onto my phone.
http://forum.xda-developers.com/showpost.php?p=1566518&postcount=2
I think this happens coz the phone goes into standby / lock mode during your phone call. Just press the on/off button to turn screen off, and press again to turn on. Now your phone will be responsive again.
Minor bug.
Or you can just scroll the volume wheel to turn it back on.
michi123 said:
http://forum.xda-developers.com/showpost.php?p=1566518&postcount=2
Click to expand...
Click to collapse
thanks michi
thanks everyone for your replies. I will try the StayUnlock application.
I still don't understand my second issue though. If the bug is causing this issue, shouldn't it at least be consistent in either requiring me to type in my PIN or just hit the unlock button? I have set my phone to lock after 12 hours, so it should never ask for my PIN, just the unlock button...
I now see that people have been having the first issue since the Cingular 8125 but I have been unable to find any references to my second issue.
ATT Til and Backlight
When making a phone call, once connected, about 12 seconds later the screen goes dark regardless of the setting on the backlight. I am not using a password, and the only way to get back is to use the power button. using the phone button puts the call on hold
Related
When I place a call, at 10 seconds the phone backlight turns-off, and at 15 seconds the "power-off" occurs (like when you touch the power button and the screen blanks, not actually powering down the phone). At first, it seemed like a minor annoyance, but I realize now it is a problem, because when I touch the power button to bring the screen on, the start menu and some menu and touch features are locked. You have to wait until the call is over, and even then, you must touch power button off, then on to unlock the start menu and other features. It does not matter if you use the touch screen or hard buttons.
I have adjusted the backlight and power off features all the way to completely off, both during and not during a call, it still occurs.
I have been told by the company I purchased the TyTN II from that this is a known problem?? If so, is there a solution?
Respectfully,
Dave Kleiman - http://www.davekleiman.com
Take a look at the information in this thread:
http://forum.xda-developers.com/showthread.php?p=1519024
Thanks!! That was quick.
I wonder since I am reporting about the start menu and such being locked/non-operational when I bring the phone "back on" during a call, if there might be an additional problem with the phone. I see no mention of that issue in the other thread.
To fix the start menu/screen lock problem simply disable your lock pasword. It is a bug with the device. If you must have the password you will just have to deal with the problem until there is a rom update.
Hello all,
I just got my AT&T Tilt and love it so far, except for one major annoyance. When I press the power button, the device will turn the screen back on after a few seconds to a few minutes. The problem is when it's in my pocket, it can accidentally call people. My 8125 and 8525 did not experience this issue.
Any suggestions?
Thanks!
Button lock
It sounds as though the phone isn't set to lock all buttons except the power button when it is in standby. This happened to me last time I re-flashed my Wizard, and I couldn't figure out for ages why my battery was draining so quickly as well!
Settings > Buttons > Lock
Hmm, not seeing any option under Buttons or Lock. I do remember this setting from WM5. It does appear, however, that the buttons are not turning the phone on, it's just waking up even if I leave it on a desk.
You can add lock to the home screen
first press and hold the hang-up button so that it locks. Then just push the power button once. This puts it in standby.
There is a idle timeout for going on standby mode, but I can't find a setting to auto-lock.
JBHorne said:
When I press the power button, the device will turn the screen back on after a few seconds to a few minutes.
Click to expand...
Click to collapse
Are you paired to a Bluetooth device? I see similar behavior in my 8525 when in my car - the BT car kit does stuff which "wakes" the 8525
Richard
Try this leaving Google Maps On the Screen
Hi Guys,
I get this behavior when I have Google Maps running. It will even cycle the screen on and off a couple times.
nope and nope. just sitting on the today screen.
JBHorne said:
When I press the power button, the device will turn the screen back on after a few seconds to a few minutes.
Click to expand...
Click to collapse
I have the very same problem.
However, my girlfriend whom I also bought a Tilt for, her's doesn't do it.
We've installed all the same software too, so I'm a little puzzled.
start>settings>system> key lock. set it to lock all buttons except power.
rzanology said:
start>settings>system> key lock. set it to lock all buttons except power.
Click to expand...
Click to collapse
Hmmm.. yeah, umm my key lock is already set to lock all buttons except power.
The problem isn't with when you press a button it comes on. The problem is the phone turns on by itself, sitting on a table, nothing being pressed, no new email, no new sms, just lights up and that's it.
JonRick said:
Hmmm.. yeah, umm my key lock is already set to lock all buttons except power.
The problem isn't with when you press a button it comes on. The problem is the phone turns on by itself, sitting on a table, nothing being pressed, no new email, no new sms, just lights up and that's it.
Click to expand...
Click to collapse
Any number of applications might be starting the device, from weather apps to calendar, diary, time sync etc etc. For example, HTCs weather app will do it depending on how often you have it set to another example I came across from someone was TREO ALERTS that contains a script "refresh.mscr" and it was set up refresh time 30 seconds (this was turning his TyTn II on by itself).
Mike
hard reset and try again.
i'm betting that none of these suggestions were helpful (except the one about some application generating a wakeup event without any other visual notifications).
i was having the same problem, but i just tried to narrow down which running program was causing the events. it's one of:
* wireless manager
* messaging
* IM
my guess is IM; i'm going to test that out in a second.
well, it's none of the above. still seems to wake up randomly anywhere from 15 seconds to several minutes.
seems to happen more frequently when it's just been turned off.
Even if you were to find what was turing the phone back on, this can still be a problem just from normal use... obviously, you WANT the phone to turn on for things like a call coming in. The solution for people like us who stick our phones in our pockets is to "lock" the phone. But for whatever reason, the Tilt doesn't lock the phone while holding down the end key. That means the only convenient way to lock it is to keep the lock function on the today screen, wasting space. Hopefully someone can find a way to allow the end key to lock the device on the Tilt just like the unbranded device.
dscline said:
Even if you were to find what was turing the phone back on, this can still be a problem just from normal use... obviously, you WANT the phone to turn on for things like a call coming in. The solution for people like us who stick our phones in our pockets is to "lock" the phone. But for whatever reason, the Tilt doesn't lock the phone while holding down the end key. That means the only convenient way to lock it is to keep the lock function on the today screen, wasting space. Hopefully someone can find a way to allow the end key to lock the device on the Tilt just like the unbranded device.
Click to expand...
Click to collapse
i'm fine with using the lock function, but it still turns on randomly, using battery, and eventually unnecessarily yellowing the screen from backlight aging. my next approach is to check out the notification queue, using a notification cleaner app.
So i am having a similar problem. When i press the power button, the phone's screen turns off but when the keyboard slides, it turns back on... is there a way to make it so the keyboard sliding does not turn on the device? I think the keyboard slides around a little when in my pocket and i hate pushing 3 buttons to unlock my phone... thanks
I was having the same problem.
This is an issue with the ATT rom. Flash over HTC rom and you will be all set.
I have been having the same problem as well. I just installed this DeviceLock program:
http://forum.xda-developers.com/showthread.php?t=305402
If you enable the "Lock on Wake" option, the device will be locked when it wakes up, so the backlight stays off and you won't call anyone by accidentally hitting buttons.
Also, I ran across this related thread you might want to check out (basically talking about the same thing, but for the TyTn II):
http://forum.xda-developers.com/showthread.php?t=341419
Basically I had a look about here and can't see anyone else with the same issue.
I've not long had the phone and the other night I had a call quite late saying I'd been phoning them 5 times. I'd locked my phone but when I looked at it it was awake and unlocked.
I can lock my phone (hold down the end call key) but with a bit of movement to the phone it brings up the unlock screen and unlocks itself.
This also happens if I lock the phone and turn off the screen with the power button. After a little shake about the phone will turn on and unlock itself.
You can imagine the problems this can cause whilst in my pocket.
I've not messed with the firmware yet or even any registry entries, it's as it was from HTC.
I am having this same issue with mine. I hold down the End key for a few seconds to lock, it locks successfully, but if I move my finger a bit and touch any other part of the surface it unlocks almost instantly. Sometimes the lock remains, but it's more likely that it will get unlocked.
I tried using TouchLockPro, but that didn't seem to help me much (it seems like it's not even functioning, actually). I'm running A.Z.T.O.R. V7 WWE ROM.
Nick
Have you tried going to settings then hitting "key lock". On the screen that comes up check the first option "lock all buttons except power button".
Works fine for me - when I switch off screen using power button everything is locked (buttons and screen) until I hit power button again or I get an incoming call.
Mine is set to that, but it doesn't seem to have much effect.
Sometimes I will hit the power button to shut the screen off and later when I pull it out of my pocket the screen is on and something (e.g. Calendar, System Time, etc) is open. During the period it was in my pocket I received no calls or texts.
When I try to hold the end key to lock the phone, it will lock it for ~1 second and then automatically unlock it. Doing it a second or third time will usually get a lock that "sticks" (at least for a while).
There has to be a good solution for this out there, but I've tried PocketShield and TouchLockPro without luck.
Nick
Diamond unlocks itself
I have this problem as well. I went to a meeting, locked my phone and it made 20 calls to my friend abroad, so I am really pissed, it happened before but I thought it was because it got knocked in my handbag.- Please help
Also my battery life has depreciated in a big way, at first 24 hours , 4 months later I'm lucky if it's lasting 6 hours and that's without making a call. I've turned of wi-fi, 3G etc. What is happening
Use sensorlock its great if you set it to unlock when you take the stylus out and relock when u slide it back in
mancsoulja said:
Use sensorlock its great if you set it to unlock when you take the stylus out and relock when u slide it back in
Click to expand...
Click to collapse
TouchLockPro should just work. In post #5 alternatives are mentioned (and also why the built-in Windows Mobile lock is not a solution for your problem)!
The screen keeps blinking back to full brightness, every 30 seconds or so, when it is left alone and the screen dims normally. It is as if something is pressing a button or touching the screen.
When I press the power button and send it to suspend mode, the backlight goes off, and the tilt no longer responds to touch or button pressing. For some reason it pops itself out of suspend and turns back on every couple minutes. My battery life is going down extremely fast. 100% to 40% in three hours.
Any help would be greatly appreciated. I searched the forum but never found a specific topic for this issue.
MiniDevil said:
The screen keeps blinking back to full brightness, every 30 seconds or so, when it is left alone and the screen dims normally. It is as if something is pressing a button or touching the screen.
When I press the power button and send it to suspend mode, the backlight goes off, and the tilt no longer responds to touch down extremely fast. 100% to 40% in three hours.
Any help would be greatly
appreciated. I searched the forum
but never found a specific topic for
this issue.
Click to expand...
Click to collapse
I have the same problem w
th the backlight comming on by itself & battery life depletes extremely fast. I am using HD 15 Nov with 3.29.
In addition to backlight issue my hardware keys are no longer working.
Please has anyone got any advice
i have the same problem. the only thing that seems to work is doing the keypad lock and putting it to sleep. it will occasionally blink like its trying to come back on but doesnt. another thing i did is put my phone in flight mode, locking the keypad and putting it to sleep. when i do that it doesnt blink or anything. sadly i wont receive phone calls or emails and texts. i think the blinking has something to do with phone signal and accessing the networks.
hth
also i noticed that it wakes from sleep when the keypad "unlock" screen pops up.
i think i found a fix
Ok I hope this helps for you because it seems to work for me. I first went to start/settings/sounds & notifications. Then I clicked on the notification tab and unchecked everything leaving only the ringer on for when calls come in. when I did that, for about 5 minutes (longest I tested it at) the phone did not turn on and the backlight didn’t do that weird grayish flash thing. Afterwords I at first was going to go down the list of all notifications and turn things on/off to see what wakes up my phone but i got too lazy and only checked one setting. One thing I noticed is that when I have the beam: autorecieved notification turned on for display a message on the screen I get that weird backlight flickering thing. So for now I just have sound alerts on when I receive any type of messages and a sound alert for reminders. So far so good, my phone hasn’t woken from sleep in 20 minutes.
I can't tell if this issue is with the specific ROM I'm using, or if it's just a Lollipop issue in general. During phone calls, the screen goes black (as it should) when I bring the phone to my ear, but now with Lollipop ROMs, most of the time when I pull the phone away, the screen stays black instead of coming back on. Normally, the screen would illuminate when I pull the phone away, but now it doesn't always work correctly. This is particularly annoying at the end of a call when I would normally touch 'end call', but now I have to wait for the caller on the other end to hang up before the screen comes on. Anybody else notice this?
I'm running gruesomewolf's GPE version 1 and I noticed it. I can usually just press the power button and the screen comes back on though.
A workaround
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Abdou.rk said:
I also have noticed this problem, and i am 100 positive it is a lollipop problem, nothing wrong with the sensor (otherwise the screen wouldn't turn off when it comes close to your ear) nor the ROM (also present in the stock ROM), One solution i found is to set the power button to end the call, this option can be found in Settings>accessibility.
Click to expand...
Click to collapse
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
One more solution
coal686 said:
That's a good idea although if you had to use your phone while on a call to look something up or press the keypad, pressing power to turn on the screen will also hang up the call. But, if you never have that issue, your workaround is :good:
Click to expand...
Click to collapse
You can also enable DoubleTap2Wake by using a custom kernel.
Same problem on TMo m7
Last week I upgraded to Android 5.0.2 on my TMo HTC One m7.
Since then when I remove the device from next to my head during a phone call the screen stays black.
This means I cannot use a keypad to navigate a phone menu or to enter a PIN.
I can tap the power button to re-awaken the screen but it takes several seconds to come back - and sometimes stays dark.
This is a mild nuisance if simply trying to end a call but is a major issue if I'm trying to use an IVR (this device is, after all, a PHONE!)
I have run the HTC Function test on the phone and the P-Sensor test runs fine.