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?
Ok so I've had this phone for about a week, ordered it right from the Cricket website, I use it often at night as I work third shift and I noticed several times that when I hit the power button to lock the screen it goes black but sometimes still remains just slightly lit. It's happened several times and I have no idea what causes it and I have tried several different things I do all the time before locking it but I still have no definitive reason it might do this. I kept myself from messing with it to see how long it would remain like this and I managed to leave it for about 32 mins, which ate up about 8% of the battery. Any ideas what might cause this out how to fix?
Sent from my HTC One V using xda app-developers app
HTC One V screen lock issues
I'm also having this same issue. I've had the phone for a very short time maybe three weeks now at the most. I've noticed it does this more often when the phones been in standby for extended periods of time. Sometimes it'll do it multiple times in a row (eg: ill lock the screen, notice that it doesnt power off all the way so I'll unlock it and lock it again and the screen will still remain slightly powered.) Also, the screen "blurs" and gets lines through the image when this happens and doesnt have that crisp blacking out of the screen that it should when locking the phone. I havent been able to find any other mention of this problem other than right here. Phone is not unlocked and is serviced by Cricket. If anyone has info on how to fix this I'd really appreciate it.
Unexpected Rage said:
Ok so I've had this phone for about a week, ordered it right from the Cricket website, I use it often at night as I work third shift and I noticed several times that when I hit the power button to lock the screen it goes black but sometimes still remains just slightly lit. It's happened several times and I have no idea what causes it and I have tried several different things I do all the time before locking it but I still have no definitive reason it might do this. I kept myself from messing with it to see how long it would remain like this and I managed to leave it for about 32 mins, which ate up about 8% of the battery. Any ideas what might cause this out how to fix?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
This is a known issue, I have it on my Virgin Mobile One V. (Rooted but all stock except I use Nova Launcher)
mine too. i did notice the problem went away when i flashed a custom rom. this used to bug the heck out of me, so i am glad i got this solved.
by the way, if you flash a custom rom for a cricket follow this guide for mms
http://forum.xda-developers.com/showthread.php?t=2120559
Has anyone experienced any spontaneous reboots on their ZL yet?
Mine has done it twice, both times while doing things related to Google apps or accounts. The first time my phone rebooted, I was actually adding my Google account after a reset to fix the notification LED issue. When I unchecked the option to backup and restore my Google account, my phone blinked the xperia logo, then rebooted (Sony logo, xperia logo, boot animation then done). It was a very quick reboot.
The next time, I was installing apps from the Play Store. A bunch of apps were queued up, downloading and installing over Wi-Fi. I hit the home button, then was about to open up a folder to check my Gmail app settings when again, the phone blinked the xperia logo and proceeded to reboot. When it was done, it continued to install my apps as queued from the Play Store, as if nothing happened. It hasn't done it since (of course, this was only a few hours ago).
My phone is not rooted & I have not messed with the bootloader unlocking or anything. It's 100% stock while I'm evaluating it against my SGS3 for a potential permanent switch. I've got the US C6506 model (black, on AT&T -- LTE is working fine).
I really, really like this phone so far, and I'm just hoping that these two reboots were a random oddity, not to be repeated.
Interestingly, I actually fully set up the phone yesterday evening, but when I discovered I had the notification issue, I reset it this morning and re-did all of it. The phone did NOT reboot at all yesterday in the 4 or 5 hours I spent playing with it, either. It sat in standby overnight without incident as well -- all prior to the reset today & the 2 subsequent reboots.
I guess from here it'll be a waiting game to see if it does it again, but in the meantime, I was curious if anyone else had seen anything like this with their ZL.
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
rajeshr said:
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
Click to expand...
Click to collapse
Thanks ... in some ways it's good to know, and in others, it worries me. I hope it isn't a pattern, though. Thus far, I've used the phone since the two reboots without incident (music playing, bluetooth connections, and phone calls).
EDIT: A third reboot. This time I had just updated a few apps in the Play Store, returned to my home screen and was about to turn my Wi-Fi off when it rebooted. One common thread thus far is that my Wi-Fi has been on each time. I have no idea if that's related or not, though.
I have been using mine for 1 week and have not had any reboots. I am using the hspa version (c6502) and I am a heavy user
Seems to me that the random reboots are isolated to 6506 models. I haven't had one single reboot in the past week I have been extensively using mine (6502). However, while I was on CM10, my phone hung and rebooted like hell.
Yeah I'm c6502 aswell no random reboots.
Sent from my Nexus 4 using xda premium
No reboots on C6502
Same here, have been using my ZL (C6502) for the past 22 days without a single reboot or freeze. Heavy usage for last week or so (wifi on all the time). I too think this and the low call volume issue might be specific to C6506 (LTE) version.
6502 here as well, no reboots so far and I'm rooted. Been about 2 weeks.
I'm starting to think this issue is unique to me and/or my phone -- at least my specific case. Actually, I'm glad for that, because I love this phone.
I realized I may in fact have memory card corruption. I'm going to explore that further, because I had some serious issues with my SGS3 corrupting microSD cards. I thought it hadn't done it on my current card, but I have discovered some corrupted sound files on it, so I think I'm going to do a format of my microSD and see what happens.
Thanks for all the input, folks!
I had some reboots in past one week
using since March 10th
today itself had 2-3 reboots
one more thing is had blank screen during a phone call also
we need Roms for this device I never understood
why there is so much delay in release of custom Roms
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
safuan7822 said:
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't call that a reboot, at least not in the sense that I was seeing them. That's more like a freeze that would require a battery pull on a phone with a removable battery (I used to have this all the time on the Samsung Captivate).
My ZL was rebooting fully right in front of me (screen goes black, then the xperia logo, followed by the full normal boot sequence, just very rapid -- the boot animation is shorter than a cold boot).
Note -- I have not actually fixed my memory card yet, and I have not seen any more reboots. I'm nearly a full day on my current battery charge, too.
I have the C6506 also, and I get numerous random reboots also. I did get few logcats, but I have not seen any revelant info that causes the random reboots. I replaced my micro-sim, thinking it may caused modem panic reboots, but that wasn't root of the problem. However, I did notice that the reboots occurred less without micro SD card, but I haven't completely made that conclusion yet (I want to listent to my music!).
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Qmann05 said:
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Click to expand...
Click to collapse
Interesting. I've replaced all my corrupted files on my microSD card as of now, and so far, aside from that first day, I have not had a single reboot of the kind I saw before. Actually, no reboots at all, and my current uptime shows it (111 hours).
What happened to me was I had had a bad microSD card in my SGS3 -- files would become corrupted with time on it. I finally replaced it with a new one, but apparently when I copied my data back to it, I inadvertently copied a few of the corrupted audio files (notification sounds, actually) but never noticed it. I realized this when I was resetting my notification sound for text messages and heard the signs of corruption in the file, and so I began to think my phone had been responsible for the corruption. I know now that that can't be true -- otherwise I'd have some corrupt photos as well, and I don't. Only a few select sound files were bad, and because I keep regular backups of the contents of my microSD cards, I just copied the wrong ones (d'oh!).
Of course, I've had random reboots on android devices before (Asus TF101), so I'm quite wary of them -- if I see anything further, I'll post about it.
I looked at the log and saw nothing conclusive that would be making my screen turn off. I also checked my up time and it hasn't reset, so I know it's not a true reboot. When I put my SD card in I just wiped it from the phone. The only thing I put back was music files. Thinking about that now it wasn't the clean start I usually give my phones. So I just wiped the card again and we will see today if anything happens
C6503 here and I've been getting a couple reboots a day since I bought it. 2 days ago I used PC Companion to solve another issue (random loss of network signal) by reinstalling the phone software and that seems to have fixed it. Unfortunately the random reboots are still present.
I don't use any SD card at the moment.
I've now been using my ZL for a month or so, and since that first day when I made this post, no spontaneous reboots at all. I have no idea how or why, they just stopped on their own.
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.
Dear,
So I have my phone for 2 weeks now and suddenly my screen creates these black/green/white/blue lines on my phone and my phone screen was full of it, I couldn't see anything so I restarted the phone by holding my power button, it restarted and on boot some of these lines occurred again. I decided to download a game to test my phone (Need for speed No limit) and I saw like some graphical glitches and also suddenly my phone went to invert colors without me turning the option on in quick settings or accessibility.
I'll take a look how often I get these and will probably just go to the store where I bought it, or is there a quick for this?
Still on Android 6.0 no root.
It's most likely a hardware issue and you're best to return it to the store you got it and get a new one.
Sent from my Nexus 5X using XDA-Developers mobile app
LesleyXYZ said:
Dear,
So I have my phone for 2 weeks now and suddenly my screen creates these black/green/white/blue lines on my phone and my phone screen was full of it, I couldn't see anything so I restarted the phone by holding my power button, it restarted and on boot some of these lines occurred again. I decided to download a game to test my phone (Need for speed No limit) and I saw like some graphical glitches and also suddenly my phone went to invert colors without me turning the option on in quick settings or accessibility.
I'll take a look how often I get these and will probably just go to the store where I bought it, or is there a quick for this?
Still on Android 6.0 no root.
Click to expand...
Click to collapse
Does this happen on boot animation too? ( the google and android loading logo ) If yes, then it's probably caused by faulty lcd and/or lcd cable. If not, then something is wrong with the software.
LG Nexus 5X glitch on screen
anazhd said:
Does this happen on boot animation too? ( the google and android loading logo ) If yes, then it's probably caused by faulty lcd and/or lcd cable. If not, then something is wrong with the software.
Click to expand...
Click to collapse
I am experiencing this issue as well. I get it most of the time on boot. If i leave it on the glitchy screen long enough, the phone will just reboot.