Using the stock ROM for the Galaxy Nexus, Android 4.04 from Google, I'm finding this bug (which has been elsewhere reported, but not acted upon by Google) where the touch screen is unresponsive. You press the 'power' button, the 'slide to unlock' screen appears, but the touch screen doesn't respond to anything.
If I get a call while the phone is sleep, the same thing occurs - can't answer the phone.
I usually have to put the phone to sleep/wake it up 5, 6, or more times before the touch screen again becomes enabled in these situations.
Does anyone know why this happens? There has been much conjecture about this, but I have yet to see anyone say for sure why this would be happening. A disabled touchscreen at such a crucial point in a GUI is pretty horrific.
- Tim
was gonna make a new thread on this but since i found one with the exact same thing happened figured why waste space, but anyway this just happned to me running stock 4.0.4 cdma unrooted. was just charging my phone unlocked it to check twitter and the lock screen was completely unresponsive for whatever reason. I continued to turn the screen off and on several times and then just decided to pull my battery and it worked fine.
This is the first time its happened to me and its kinda troubling as I dont want this to be a recurring thing and was wondering if this continues to happen or its just some single random occurence?
Related
Ok, I was having some software issues with my Tilt 2 (TP2) and I talked to Tech @ AT&T, cause I wanted to get it exchanged. So they had me go and check to see if my ROM was outdated, which it was. I bileive it was on 1.59-ish, and now its on the most current one direct from HTC's Support site. My main problem right now is that the phone is 99% unuseable at the moment. AT&T has already agreed to send a replacement after talking with them a few hours ago, but its going to take about a week to get here, and it'll most likely have the same ROM and the same problems, so here I am posting to let people know whats going on, and see if anyone else knows what causes this/has this issue.
Right now the phone is completely stock, only installed app is MS My Phone so I could sync my contacts. I can let the phone sit till the screen shuts off from idle, but if I need to turn on the screen once it turns off, it requires the battery to be taken out. Right now my phone is sitting in front of my keyboard, with its screen black and off, while the keyboard is lit up. Something to note - the keys on the bottom of the screen are NOT lit up. Pushing buttons on the keyboard does nothing. Caps Lock and FN do NOT light up their coresponding indicator lights. If I am lucky, I can get the phone to come out of this state by having someone call me, but aside from that, taking out the battery has been the only way to reset it. Only way to keep the screen from freezing is to constantly use the phone. Using the phone is slow as balls. I thought TF3D was slow, Sense is just as bad. It worked perfectly fine at first, right after it was updated, it was nice and fast, but now that its been used for a few hours, its sluggish.
Anyone ever had this issue with this ROM?
And does anyone know how to possibly fix this issue, or at least get it so the screen will show that its on? I can deal with it being slow, so long as I can use the screen
Thanks guys
null_x86 said:
Ok, I was having some software issues with my Tilt 2 (TP2) and I talked to Tech @ AT&T, cause I wanted to get it exchanged. So they had me go and check to see if my ROM was outdated, which it was. I bileive it was on 1.59-ish, and now its on the most current one direct from HTC's Support site. My main problem right now is that the phone is 99% unuseable at the moment. AT&T has already agreed to send a replacement after talking with them a few hours ago, but its going to take about a week to get here, and it'll most likely have the same ROM and the same problems, so here I am posting to let people know whats going on, and see if anyone else knows what causes this/has this issue.
Right now the phone is completely stock, only installed app is MS My Phone so I could sync my contacts. I can let the phone sit till the screen shuts off from idle, but if I need to turn on the screen once it turns off, it requires the battery to be taken out. Right now my phone is sitting in front of my keyboard, with its screen black and off, while the keyboard is lit up. Something to note - the keys on the bottom of the screen are NOT lit up. Pushing buttons on the keyboard does nothing. Caps Lock and FN do NOT light up their coresponding indicator lights. If I am lucky, I can get the phone to come out of this state by having someone call me, but aside from that, taking out the battery has been the only way to reset it. Only way to keep the screen from freezing is to constantly use the phone. Using the phone is slow as balls. I thought TF3D was slow, Sense is just as bad. It worked perfectly fine at first, right after it was updated, it was nice and fast, but now that its been used for a few hours, its sluggish.
Anyone ever had this issue with this ROM?
And does anyone know how to possibly fix this issue, or at least get it so the screen will show that its on? I can deal with it being slow, so long as I can use the screen
Thanks guys
Click to expand...
Click to collapse
You already ruled out a software issue by flashing another stock ROM. This is something hardware related. Sense on the AT&T ROM is dreadfully slow. Use a custom ROM if you want the features of Sense, but in a faster iteration.
anyone had problem with the screen not responding after waking up?
There's no way to turn off the phone / make it respond unless to unplug the battery and plug it in again. Had this problem on the first GN and my second replacement GN.
Yep, happened to me the other day as well. There was a crash right before which made the phone reboot. Once it came back, the hardware buttons responded fine but the touchscreen was dead until a battery pull.
Hasn't happened since though.
Had this at lunch today also had it a few days ago.
When returning from sleep the touch input seems to be completely unresponsive.
I left mine for a while to see if it recovered, it did, it came up with the crash report for "System Process" The screen was then responding fine.
Weird. This is indeed different to the sleep of death, because the screen comes on.
Although maybe it's related in some way?
This just happened to me, and so I googled to find an answer. It thankfully led me here. It's like you guys described: I just tried unlocking my phone, but the screen was completely unresponsive. Not a single touch would register, even when trying to touch the Power Off option.
I read robaldred's comment, so I decided to try the waiting game. Thankfully, after a few minutes the screen just came on and the device was ready to use. I don't believe I saw a crash report though.
I hope this won't become a serious issue. I'd hate to be stranded at a point when I need to use my phone.
I had this problem too. have you guys used custom notification sounds?
Sent from my Galaxy Nexus using XDA App
I had this exact problem and I found it was due to Juice Defender (I have the Ultimate version as well). It kept happening after I installed and but since removing it over a week ago no problems.
Just had it happen here, had to pull batt. Using BatteryXL but will keep it on and see if it happens again.
I rooted my brother's slide a while back and installed a stock froyo based rom (I'm not sure which one). He had been having some minor issues with his phone (no big deal) and I had been planning to switch him over to cyanogenmod, but this morning his screen would not go to sleep no matter what he did. It just wakes up immediately. He suspects that the device is registering a push on the optical trackpad, because when he tried to restart the phone, it auto selects and sometimes confirms options for him in the popup menu. The trackpad wake seems to be preventing the phone from sleeping, but it could also be something else.
I thought the best course of action would be to install CM6 (he had the older clockwork recovery so I thought i'd put the stable 6.1 on there to walk him through the steps while I wasn't physically present to mess with his phone). The installation went perfectly, but the problem is persisting. If i'm not mistaken, cm6 comes with a custom kernel of its own so that's probably not the issue. Also, for some reason, when his phone wakes up after attempting to be locked, it now briefly shows the lock screen and jumps ahead to the recent apps screen (as if the home button has been long pressed).
This problem is baffling us. If any of you have any ideas what might be wrong I'd greatly appreciate it. Thanks guys.
EDIT: I thought it would be worth mentioning that in recovery, the trackpad function seems to be normal (according to him). He's several hundred miles away from me at the moment so I haven't seen the issue up close myself.
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.