Hi guys,
I am having a very strange issue with my Pixel 2XL, being that the phone will crash whenever I lock it and leave it for 3 seconds or more. Any less and I can unlock the phone again just fine. Also I tried playing some music through chrome and locking the phone, which carried on playing for 20 minutes and I could unlock the phone again with no issues. It gets stuck on the ambient display with the time when the phone crashes and I have to restart it (With power and volume + buttons).
I have tried to factory reset and even flash older factory images (I am by no means an expert and just gave it a try).
As of now I am out of ideas as to what it can be. I can only assume that a service or something is in standby and is causing an error when it goes to ambient/standby. I have also tried to change all settings in battery optimisation to not optimised, which did nothing.
Has anyone else had a similar issue and know how to fix it.
TIA!!
The same with me
Hi My Pixel 2 XL has exactly the same issue. Have you found any fixing method? Thank you:crying:
Related
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.
My Note4 has developed a weird issue where it will be on just fine for like 5-10 hours then all of a sudden it will show the Verizon logo full-screen with nothing else and be unusable. I need to pull the battery to fix it.
Q1: What the heck would cause this? Only changes Ive made were using the new GearVR and sideloadVR, not sure if related. But seemed to have happened several days after installing them, not at the same time.
- I use synapse and have tried undervolting thinking it might be overheating. No change. Put it back to normal.
- Happens with both the standard battery and Zero Lemon battery.
- Happens when in or out of power save mode (black and white screen etc)
Q2: If I factory reset, will I lose root? Note: A software update has been downloaded and its been asking me every day to install it and I always decline.
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.
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Gnatcatcher said:
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Click to expand...
Click to collapse
Maybe replace battery?
Hi there! I am not sure if your problem was fixed yet. But my Pixel XL died yesterday and did the same exact thing. It went into an infinire boot-loop, and after trying many times to power off and reboot, some weird artifacts appeared.
I think I messed up the phone, because at first the phone booted and then restarted, but now it just restarts and never ends....
EDIT: After some hours of rebooting, and more artifacts, the Pixel finally booted on android. Battery was at 4% so I guess that helped. It keeps rebooting from time to time, but at least I can copy my photos now haha.
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
no solution from me. But I have exact same problem and tried same things. Yesterday I did not used the phone. Day before shut down, today tunred it on and it starts with the issue. Strange it happens to both of us at the same time frame. removing sims did not help either.
By holding down "volume down+power" I was able to boot in safe mode but the same issue occur; no way to get into the phone.
Yeah that's weird. Draining the battery did nothing for us. There was not much data that we wanted to extract from the phone. Most of it was contacts and an emulated Pokémon game save file. So my wife eventually reflashed the OS with Xperia companion which did actually resolve the issue of not being able to use the phone.
I faced the same problem today ,i have xz2 , yesterday it was 24% and today i found it 0% so I put it in the charger ,but I faced this problem