Problem
In the last two days I've tried CM 10.2 weekly, Mokee OS, VanirAOSP, and MIUI v5, all with ONE common problem. The touch screen goes unresponsive after the phone automatically goes to sleep (although the hardware buttons work, and wakes the device up, you can't unlock or touch anything). Swipe to wake doesn't work in bringing the touch back, and disabling it didn't help either.
Finally, I think I have a solution. This worked in MIUI v5 (in which I faced the same trouble)
My guess is that it is related to the proximity sensor auto lock feature.
Solution
When the screen goes unresponsive keep your hand over the whole screen as if you've put the phone in your pocket, for about 5 seconds. Make sure you're covering the proximity sensor. And now, try swipe to wake or power button or whatever.
This works like charm, and you can in fact use it to trick your friends where they fail to unlock your phone and you do focus pocus magic on it!
Note
This is annoying when someone calls you and you can't pick up because the screen isn't responsive. For that, (at least in MIUI v5) enable the volume up hardware key to answer the call, and power button to end the call. (In Settings -> Control Panel -> Calls, in MIUI v5)
Edit: If this didn't work directly from sleep, press some hardware key to make the screen light up and then press the phone to your chest
Related
Anyone have problems with the 4 hard keys on the front of the phone and the scroll wheel? Talking about the att fuze here. Randomly when using the text program it will scroll in and out without stopping. Only way to make it stop is to press the power button to turn the screen off then again to turn the screen back on. Also, when i press the bottom left key to bring up the dialer sometimes it will not and just do nothing. Just as in a phone call i press the bottom right hard key to hang up the call and sometimes it will not respond what so ever.
I know the keys work because when i press them they light up showing i pressed them but they have no effect. This happens about 50% of the time and not at all rom related. I have tried over 8 different roms including those with tf3d2 and wm6.5 and all have the same problem. I have even tried flashing to the stock att rom and even on that rom i am still having this problem. I have never dropped my phone or any physical damage. Any ideas? I have already called warranty exchange and have another fuze on its way to me. I am convinced it has to be hardware related some how since no rom will work 100% for me with these keys. I have had my phone since january and out of the blue this all started about 3 weeks ago.
Bump Bump Bump
I dont have that problem, but sometimes my keys dont work and I have to turn off the screen and turn it back on
sometimes I even have to soft-reset my phone
this is partially because the Left and Right directional button is roughly between the Home/pick up and Back/hang up keys respectively. you have to press more towards the corner otherwise it will register as a left or right press.
another situation is when it is running a bunch of processes in the background it forgets what keys are what and you just have to turn it off and turn it back on (the display) and it should work again. that or open a random program and exit out back into tf3d
goodluck
Actually, I have exactly the problem that you're reporting where the zoom in happens circurlarly, without any ceasing. It's driving me batty.
Not sure if any of you had this but I notice my phone when placed on speaker mode, after calling my screen goes blank and none of the key function work (all buttons including home, power, etc) and I had to do a battery pull. I assume this may not happen as often but I recently get it a couple times already.
I spoke with the S2 guys and notice this happens to their handheld due to the sensor set. One best way to work around is simply Turn off proximity sensor under Call setting.
This happen when I had a 2.3.6 TGY KK5 stock rom.
Moodaleon said:
Not sure if any of you had this but I notice my phone when placed on speaker mode, after calling my screen goes blank and none of the key function work (all buttons including home, power, etc) and I had to do a battery pull. I assume this may not happen as often but I recently get it a couple times already.
I spoke with the S2 guys and notice this happens to their handheld due to the sensor set. One best way to work around is simply Turn off proximity sensor under Call setting.
This happen when I had a 2.3.6 TGY KK5 stock rom.
Click to expand...
Click to collapse
yeah buddy same thing happens with my device as well.. bt it doesent always have to be on speaker mode. on normal mode also sometimes my device goes blank..
anyone here help please.....
Several users on our russian forum have reported same problem on different ROMs (2.3.4, 2.3.5 and 2.3.6). Most of them are using phone calls about 60-90 minutes per day.
I never had this issue with my 2.3.5 Germany ROM, but I am using my phone for calls just for 5-10 minutes in a week.
Tip
You don't have to replace battery. Just long press power button (over 10 seconds), and phone should reboot.
I've seen the same problem on my phone, but after I pressed the power button for about 7 seconds and let go, the screen came back and I was able to hang up the call. I've turned off the proximity sensing (settings -> calls -> proximity sensor) and haven't seen the issue since then.
cocoa7 said:
I've seen the same problem on my phone, but after I pressed the power button for about 7 seconds and let go, the screen came back and I was able to hang up the call. I've turned off the proximity sensing (settings -> calls -> proximity sensor) and haven't seen the issue since then.
Click to expand...
Click to collapse
okk i wll give it a try........
my gf is experiencing this issue on her SGR as well. After a call, the phone will become unresponsive and the red spot(light sensor) near the speaker at the top of the phone will be lighted up.
using stock + ardatdat's 1.3A kernel (default settings).
will try the proximity sensor solution and hope the issue goes away.
PauseZ said:
my gf is experiencing this issue on her SGR as well. After a call, the phone will become unresponsive and the red spot(light sensor) near the speaker at the top of the phone will be lighted up.
using stock + ardatdat's 1.3A kernel (default settings).
will try the proximity sensor solution and hope the issue goes away.
Click to expand...
Click to collapse
yes buddy after unchecking the promixity sensor in call option it 0does work... bt still sometime red sensor glows and slows my phone down..... if anything of this kind is experienced then do share..
should be fine once you switch the proximity sensor off as thats what it seems to cause all the prob and the only thing u have to live with is ur screen doesnt go dim when you stick it to ur face while talking
I'm using xXminiWHOOPERxX's v6 kernel and have a few issues with wake launch gestures.
1) They don't respect being in my pocket. Swipe up is set to flashlight and down is set to play/pause music. Often, i set them off when taking phone out of pocket, or putting it in pocket.
2) Wake launch gestures won't go past lock screen (I wrote about this in the developer section). So, i can't use wlg to open apps or unlock the device. No matter what action i have wlg set for it only wakes the device to the lockscreen.
3) Yesterday, after about a day of using miniwhooper's v6 kernel, my phone suddenly started vibrating and rebooting. It did this constantly for about 30 minutes so i turned my phone off for about an hour. When i started it back up, it was fine. The phone wasn't hot or anything, either. Also, i have s2w, s2s, disabled, so it wasn't the issue where people were swiping the soft keys and getting long vibration/reboot.
Thanks again for all your hard work xXminiWHOOPERxX!
jollywhitefoot said:
I'm using xXminiWHOOPERxX's v6 kernel and have a few issues with wake launch gestures.
1) They don't respect being in my pocket. Swipe up is set to flashlight and down is set to play/pause music. Often, i set them off when taking phone out of pocket, or putting it in pocket.
2) Wake launch gestures won't go past lock screen (I wrote about this in the developer section). So, i can't use wlg to open apps or unlock the device. No matter what action i have wlg set for it only wakes the device to the lockscreen.
3) Yesterday, after about a day of using miniwhooper's v6 kernel, my phone suddenly started vibrating and rebooting. It did this constantly for about 30 minutes so i turned my phone off for about an hour. When i started it back up, it was fine. The phone wasn't hot or anything, either. Also, i have s2w, s2s, disabled, so it wasn't the issue where people were swiping the soft keys and getting long vibration/reboot.
Thanks again for all your hard work xXminiWHOOPERxX!
Click to expand...
Click to collapse
Try this kernel with Sense 6.0 toolbox, it has fixes for these problems. Or you can wait til xXminiWHOOPERxX updates her kernel
I've got an intermittent problem - sometimes when I wake the phone up, the touch screen doesn't work. It happens when I wake it up with the power button, when someone calls, or when an alarm wakes up the screen. That means when the problem happens, I can't answer the call, or turn off the alarm (sometimes locking the screen and waking it up immediately works).
It doesn't seem to be affected by whether or not the phone is or has been charging, whether it's been in my pocket or the temperature of the device. I've not been able to discern a pattern at all. Once the phone is unlocked and the touchscreen is working though, it works perfectly. The problem never returns while I'm using it, only if I lock it, and only sometimes.
If I leave the screen on while touch is unresponsive, I can tell when it is responsive to touch again by a line that quickly flashes along the top edge of the screen. At that point, the screen operates entirely normally.
In what may be a related item, when I'm on a call, sometimes the proximity sensor doesn't work properly and the screen turns back on and starts working. I get off the call and find my phone in a different app.
Does the Nexus 5 use the proximity sensor while the screen is off as a way to weed out unintended touches while the phone is in a pocket?
I'm going to try and store it face up over the next couple of weeks and see if the problem continues, but I was hoping that someone might have some insight.
About the phone:
I cracked the screen over the summer and had it replaced, but I didn't have any issues with it at all until I installed Lollipop. 5.0.1 hasn't made a difference
Hi guys,
This problem has me stumped, so I figured I'd consult the hive mind.
The touchscreen works fine after the phone is turned on - be that for a continuous period of 30 seconds or 30 minutes. However, if/when it goes to sleep, the touchscreen becomes completely unresponsive on wake up. The screen turns on, rotates, and the physical buttons work fine. I figure no touch input is acknowledged, because if I tap the screen after it dims nothing happens; but if I press a physical button, then full brightness is restored.
I have been looking around for a solution for some time, but none of the three I found appear to be working, ie:
- Ensuring the Wi-Fi's set to be permanently on (no change on any of the settings)
- Changing the ROM (problem appeared in stock ROM, it now sports LineageOS)
- Changing the digitizer (problem is the same on old or salvaged screen)
At this point, I am not sure what else I can try. Any ideas would be most welcome.
Maybe charger? Some cables/chargers make touch panel go crazy (it used to happen to me with bad chargers) so try to change charger and USB cable.