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.
Related
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
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?
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
The changes I have made that seems to coincide with this issue are:
1. rooted the device using the .bat script method
2. installed TWRP recovery
3. switched to Nova Launcher
It's important to note, I have not rom'd my device, and am still running the stock rom.
This is happening one out of every 15 or so times I unlock my device. I have switched from pattern to password unlock to see if it's an issue related specifically to the pattern lock screen (although I have used pattern unlock since the day I got the device).
Any ideas would be greatly appreciated!
Thanks
longboarder543 said:
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
The changes I have made that seems to coincide with this issue are:
1. rooted the device using the .bat script method
2. installed TWRP recovery
3. switched to Nova Launcher
It's important to note, I have not rom'd my device, and am still running the stock rom.
This is happening one out of every 15 or so times I unlock my device. I have switched from pattern to password unlock to see if it's an issue related specifically to the pattern lock screen (although I have used pattern unlock since the day I got the device).
Any ideas would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
I don't have that issue and I'm stock , rooted and with twrp you should probably check it's either some settings causing this or more likely an app you installed.
Sent from my SGH-T889 using Tapatalk 2
Thanks for the info Naruto. I think I'm going to remove Nova launcher and see if the problem goes away.
Meanwhile, the problem just happened again, but manifested itself slightly differently. Basically, just a few minutes ago when I pushed the power button to wake the device, nothing happend for ~ 10 seconds. Finally, the lock screen came up, but I got an error message "Sorry! Process system isn't responding. Do you want to close it?" Options were "Wait" and "OK". I selected OK and was taken to the lock screen like normal.
What do you guys think?
I had root from dalingrin and twrp on stock rom for about 2 months and i never experienced this issue you report. The lock screen is related to the launcher and as you use nova launcher i d say that it is most probably caused by it.
Thanks for all the help guys. I'm not ready to say that the problem is fixed quite yet, but after switching back to the stock launcher and rebooting, I have locked and unlocked the tablet about 50 times without issue. Looks like the problem was indeed Nova Launcher. That's kind of a bummer because I love Nova, and I have it setup exactly like my phone and it works great for me.
Maybe you could try to re download nova again that's what I'm using and I have no issues. Maybe it was a setting you had checked inside of its settings ?
Sent from my SGH-T889 using Tapatalk 2
longboarder543 said:
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
Click to expand...
Click to collapse
I got the same thing on a completely unmodified G Pad last weekend. It happened once, worked ok for a few unlocks, then happened a second time. Each time I had to hold the power button down to force a reboot. It's hasn't happened before or since, so I've no idea what caused it, but I did notice something that might or might not be relevant - I happened to be looking at the battery graph later that day, and noticed that at the time of the forced reboots, the battery appeared to drop instantly by about 10%. There was a break in the graph - no vertical line showing the drop, the line just ended, then started off again immediately 10% lower down. If you get the same issue again, it would be interesting to see if your battery graph behaved in the same way.
I had this problem with stock rom changed to Mahdi
No reboots yet.
By the way, I saw a review video on YouTube and the guy was showing knock knock (spell?) and the g pad just crashed and rebooted.
Edit:
I have an LG G2, best phone ever never crashed no lag and a fast phone with great LCD maybe the best mobile screen I have ever seen.
Sent from my LG-V500 using xda app-developers app
Ok, so I don't think the problem was nova launcher after all. After switching back to the stock launcher, the tablet worked great for several hours, but eventually the problem started happening again. At that point, I rebooted into recovery, cleared cache and dalvik, then fixed permissions, and rebooted. Fingers crossed, but the issue hasn't returned once since, and we're going on 18 hours. I've even been using nova launcher without issue. Still not sure what the issue is, but at least for me, clearing cache and fixing permissions has worked so far.
Sent from my LG-V500 using Tapatalk
There is a known issue with 4.2+ of rebooting if you have third party widgets (Not sure which) on the lock screen. Do you have any on there?
http://blogs.computerworld.com/android/21427/android-42-random-reboots
stevessvt said:
There is a known issue with 4.2+ of rebooting if you have third party widgets (Not sure which) on the lock screen. Do you have any on there?
http://blogs.computerworld.com/android/21427/android-42-random-reboots
Click to expand...
Click to collapse
Thanks for that -- unfortunately I don't have any third-party widgets on the lock screen.
Victoria75001 said:
I got the same thing on a completely unmodified G Pad last weekend. It happened once, worked ok for a few unlocks, then happened a second time. Each time I had to hold the power button down to force a reboot. It's hasn't happened before or since, so I've no idea what caused it, but I did notice something that might or might not be relevant - I happened to be looking at the battery graph later that day, and noticed that at the time of the forced reboots, the battery appeared to drop instantly by about 10%. There was a break in the graph - no vertical line showing the drop, the line just ended, then started off again immediately 10% lower down. If you get the same issue again, it would be interesting to see if your battery graph behaved in the same way.
Click to expand...
Click to collapse
When I get home I'll check my battery stats to see if similar happened on mine
Hi all,
Bit of an odd problem my S9+ seems to have developed. Since I got the September update a few days a go, my Exynos S9+ on Three (but unlocked/unbranded) in the UK keeps on turning the Always on Display on.
I have it turned off by default, but on occasion when I plug it in it'll reactivate it. It doesn't happen all the time, only occasionally, but it does happen often enough for it to be annoying. I had a to add the AOD short cut to the pull down menu to be able to quickly turn it off, so it definitely wasn't something I was accidentally pressing (at least not until I added that button, but it is on the second page of shortcuts).
Anyone else having this problem since the update? Or have I just got a weird phone with a mind of its own?!
Thanks
Always on Display
Hi, I got my Samsung Galaxy S9 2 days ago and it is sort if driving me nuts!
The minute I get a mail or notification from the many groups I'm in- the screen flashes- I guess it's the lock-screen.
I turned off the "Always On Display" but it still flashes...
Is there any way to stop this... I'm a little ADD and it's really annoying.
At he moment I'm just turning it upside down so as not to see it!
Thanks in advance- Robin
kingdave82 said:
Hi all,
Bit of an odd problem my S9+ seems to have developed. Since I got the September update a few days a go, my Exynos S9+ on Three (but unlocked/unbranded) in the UK keeps on turning the Always on Display on.
I have it turned off by default, but on occasion when I plug it in it'll reactivate it. It doesn't happen all the time, only occasionally, but it does happen often enough for it to be annoying. I had a to add the AOD short cut to the pull down menu to be able to quickly turn it off, so it definitely wasn't something I was accidentally pressing (at least not until I added that button, but it is on the second page of shortcuts).
Anyone else having this problem since the update? Or have I just got a weird phone with a mind of its own?!
Thanks
Click to expand...
Click to collapse
Hey hey,
I'm experiencing the follow issue with my Pixel 3a XL. I put it onto charge at bedtime, and when I got up in the morning after the alarm went off the screen got black and unresponsive. I believe the phone is still working at this point because I can hear vibrations when I try to turn it off or boot into fastboot mode, but the screen is totally dead.
Anyone experiencing anything similar? Any ideas or suggestion on this one?
I experienced the same thing last week. Happened two days in a row and in addition to what you stated it seemed that my default home launcher had been unset in default apps, My phone seemed to bounce between launchers while navigating.
I'm running lineage and at 1st I thought maybe it was something in the update, but I don't think that was actually anything to do with it. If you're not running lineage then it for sure wasn't. Maybe a rogue app update, google services? I don't know.
I also don't know what cleared the problem up. Like I said the only thing I noticed was my default home launcher had become unset, and I set it back in default apps. Maybe something relating to that caused the phone to act seemingly dead?
Either way, if you just hold your power button for 15 sec or so it'll reset, and check your default home app. I don't really know the cause or solution, but it seems to have cleared up since then and everything is back to normal.
Hi,
I am experiencing the same thing with my pixel 3xl. I plugged it in before going to bed and in the morning it was unresponsive and black screen. I tried changing chargers and plug but nothing changed. When i plug it in a PC it shows QUSB_BULK_CID and then the serial number but nothing else. I have found many people in the google support forums that have the same issue (https://support.google.com/pixelpho...-pixel-3xl-black-screen?hl=en&msgid=121361292) but no one has replied with a fix or even an update.
Have you resolved your issue?
This is an annoying problem that I've been suffering from my pixel 3a xl for a long time. This would sometimes happen to me when just using my phone regularly but happened a lot more often when charging my phone overnight. When it first started happening to me, I noticed that I could resolve the problem by not having any magisk modules enabled.
However, this didn't seem to be a permanent solution. Nowadays my phone occasionally locks up in the way you describe, but if I leave it alone it usually comes back to a working state in about 4-8 minutes. It's very annoying and motivating me to get a new phone.
It might be worth taking a look at this issue thread on the magisk GitHub that describes the same error: https://github.com/topjohnwu/Magisk/issues/3171
My phone did this yesterday. I woke up and it was unresponsive, seemed dead. I just held the power button, restarted, and back to normal. I know had a bunch of google apps update the day before and even that morning. If I remember right, I had google apps update the last time it happened. I think there something there that's causing the problem, and once the phone is restarted it's good.
I can't say that's it for sure, but it's something I noticed. It is kind of odd that when it happen to one person here, there's usually another in about the same time frame.
Yeah mines still dead and unresponsive. I lost hope like two days ago. There was nothing out of the ordinary when it happened and no weird updates. Just plugged it in like every night and then it bricked during the night.
vagelisot said:
Hi,
I am experiencing the same thing with my pixel 3xl. I plugged it in before going to bed and in the morning it was unresponsive and black screen. I tried changing chargers and plug but nothing changed. When i plug it in a PC it shows QUSB_BULK_CID and then the serial number but nothing else. I have found many people in the google support forums that have the same issue (https://support.google.com/pixelpho...-pixel-3xl-black-screen?hl=en&msgid=121361292) but no one has replied with a fix or even an update.
Have you resolved your issue?
Click to expand...
Click to collapse
Hi!
It turned out that there was an issue with the screen (I completely don't understand why). I had it replaced and everything is back to normal.
Hope you will have your issue resolved!