it often happens that the touch crashes, go freeze, it does not work, and I must press the power button to turn the display off and then turn it back on and unlock go again to resolve. Has not happened only to the display unlock, but sometimes even when I used it. Do you know what it is, what comes from and maybe how to fix?
http://forum.xda-developers.com/showpost.php?p=56376790&postcount=4
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 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
I have had a search around, but cannot find anything useful, I hope someone can help me, this is my only problem with the Diamond now!
Sometimes after the phone goes to sleep, it does not wake up properly. I have the phone set to switch the screen off after a delay and to autolock at that point as well. All has been fine with that except in the last few days sometimes when I try and bring the phone out of this sleep mode, it doesnt work.
Geneally I will press the centre button and the phone comes to life and I tap unlock and I am away. However, sometimes now only the top bar where the start button is will appear. The HW buttons light up, but the rest of the screen does not come to life and whatever I do, I cannot get it to come back. I can press the power button and it will go to sleep again and then when I try and wake it, exactly the same problem occurs. Only a soft reset will solve it - far from ideal.
Can anyone help please?
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
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.