I updated to QP1A.191005.007, Oct 2019 earlier this week. Since then (has happened 3 times now), I've randomly been getting the "G" loading screen. Only way to get out of it is to do a hard reset (hold power button for 10 seconds). I have noticed that when this happens, I'm plugged into to the charger. I am running on the latest Magisk Canary build.
Has anyone else experienced this?
xomikronx said:
Has anyone else experienced this?
Click to expand...
Click to collapse
Not here. Try to replicate in safe mode to rule out one of your apps.
Related
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Stuke00 said:
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Click to expand...
Click to collapse
No one else has seen this issue?
Many ROMs have their little quirks here and there, this could be one. I use hashcode's ROMs so this is just speculation though.
I had this issue with twa_priv's rom. If I keep at the button, pushing it multiple times at different intervals, it would eventually come on. Interestingly, if I went into the developer options and put the CPU at the full 1200MHz, it didn't happen.
Not having this issue with CM (though I'm running 10.2) so not sure there.
This was a common occurrence in cm10.1 with TWA_priv's build I believe. This is called a Sleep of Death or SoD. I thought that was cleared up, but maybe not. If there is a newer version of the ROM that you are on, I recommend trying that. There is no way to recover from an SoD except to force power off like you did, and start back up.
Sent from my Nexus 7 using Tapatalk
I've had my Pixel 3 XL for about 3 weeks now, not been dropped or damaged or anything like that, also not rooted. Its fully up to date, Android 9, security patch 5th Jan 2019.
Yesterday it stopped unlocking properly - the screen takes 20-30 seconds to respond after either pressing the lock button to wake it, touching the fingerprint sensor or double tapping the screen. I occasionally get "System UI has stopped responding" when I get it to eventually unlock.
So far I've tried:
* Full restart of the phone
* Force reset by long press power button
* Boot into Safe Mode
* Factory reset
None of the above have fixed the issue. Its weird - for a few minutes after a fresh boot, the issue doesn't happen then slowly creeps in. Is it perhaps a memory issue?
Has anyone else seen this issue? If you have, what's the fix for it - or is it a faulty phone?
phantomlore said:
I've had my Pixel 3 XL for about 3 weeks now, not been dropped or damaged or anything like that, also not rooted. Its fully up to date, Android 9, security patch 5th Jan 2019.
Yesterday it stopped unlocking properly - the screen takes 20-30 seconds to respond after either pressing the lock button to wake it, touching the fingerprint sensor or double tapping the screen. I occasionally get "System UI has stopped responding" when I get it to eventually unlock.
So far I've tried:
* Full restart of the phone
* Force reset by long press power button
* Boot into Safe Mode
* Factory reset
None of the above have fixed the issue. Its weird - for a few minutes after a fresh boot, the issue doesn't happen then slowly creeps in. Is it perhaps a memory issue?
Has anyone else seen this issue? If you have, what's the fix for it - or is it a faulty phone?
Click to expand...
Click to collapse
You apparently tried everything that google would have you do. I see no reason to continue trying to fix it. RMA that puppy :good:
Not sure there would be much difference compared to a factory reset, but you could try sideloading the OTA again. The other option (assuming it is the Google variant and not Verizon) would be to unlock your bootloader and flash the factory image.
Badger50 said:
You apparently tried everything that google would have you do. I see no reason to continue trying to fix it. RMA that puppy :good:
Click to expand...
Click to collapse
Think I'll take it back tonight :/
So after this morning's post, I've found that keeping it face up on my desk seems to prevent the issue from occuring (i.e. so the always on display stays on)... Turn it over (Flip to Shh is disabled) or put it in my pocket and the issues start. Is it maybe a faulty proximity sensor? The glass protector I've got on the screen has a cutout around the notch so shouldn't be over the proximity sensor.
Edit: the above was done with it plugged into a charger. Unplug it, leave it face up and the issue returns? WTF?
So youve never tried to root or flash anything?
hilla_killa said:
So youve never tried to root or flash anything?
Click to expand...
Click to collapse
Nope.
phantomlore said:
I've had my Pixel 3 XL for about 3 weeks now, not been dropped or damaged or anything like that, also not rooted. Its fully up to date, Android 9, security patch 5th Jan 2019.
Yesterday it stopped unlocking properly - the screen takes 20-30 seconds to respond after either pressing the lock button to wake it, touching the fingerprint sensor or double tapping the screen. I occasionally get "System UI has stopped responding" when I get it to eventually unlock.
So far I've tried:
* Full restart of the phone
* Force reset by long press power button
* Boot into Safe Mode
* Factory reset
None of the above have fixed the issue. Its weird - for a few minutes after a fresh boot, the issue doesn't happen then slowly creeps in. Is it perhaps a memory issue?
Has anyone else seen this issue? If you have, what's the fix for it - or is it a faulty phone?
Click to expand...
Click to collapse
just sideload an ota and then factory reset.
The last two times I allowed my phone to charge fully, the phone locked up (would not come on when the power button was pressed) and I had to do a soft reset (hold the power button for 30 seconds). This happened on two different chargers with two different cables (one of which is the factory set). Thus, the issue is almost certainly not hardware related.
There have been no changes to my phone, no newly installed apps, etc. There have been a number of app updates, including several Google/Android core apps, and I am wondering if one of those could be the problem. (After the first time the phone locked, I updated the kernel to the latest version, i.e., PQ3A.190801.022. Note also that the phone is rooted with Magisk.)
Has anyone else experienced this problem? If so, what did you do to resolve it? What can I do to try to figure out why this is happening?
groston said:
...What can I do to try to figure out why this is happening?
Click to expand...
Click to collapse
Try replicating it in safe mode to rule out 3rd party apps.
I'm having the same issue the last 2 weeks. I haven't updated any apps and I have auto updates off. No changes to my phone since the end of august and it just started doing this.
Were you able to figure out what was causing it? My issues occur using a 5W Qi charger. So it is definitely not cable/charger related.
Sorry to report, but I have no idea. Since having posted my question, my phone has been behaving properly.
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
darkstar73 said:
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
Click to expand...
Click to collapse
Weird. I'm still on 9 that was working fine and no update that I know of.
I confirmed the issue with both QI charging and cable charging on my phone.
I've taken to making sure my phone is charged before bed and just pulling it off the charger before going to sleep. Since my phone is also my alarm and having it go unresponsive is no good. Only looses about 3% battery overnight.
Well, not sure what happened but the day before yesterday my phone did it's usual lock up while charging requiring a reboot. Unusually after reboot if I logged on too fast it would immediately shutdown. But for some reason this time it took me 7-8 tries to get in. I haven't updated any apps, changed any modules in Magisk or anything. It just went to almost boot looping.
As soon as I got it stable I popped into Magisk and looked at what modules were there. I noticed I had added Substratum previously, to try and do a dark theme, but apparently I never removed or disabled it. I disabled all the modules and suddenly no more problems. Reboots without shutting down after log in and no longer locking up on the charger.
I removed two audio mods (audio compatibility patch and audio modification library), as well as substratum. Three of 5 mods I had downloaded.
I am currently only have Active Edge Mod and V4A legacy FX for mods and my phone is now working fine. If it changes I'll let you guys know.
This may sound a little strange has anyone ever encounted the problem where their phone will not shut down. Holding in the power button and choosing shut down just restarts it. Choosing shut down from fastboot also just restarts it. I even tried locking the bootloader with the December update , but it still happens..... Strange
Gosimer4 said:
This may sound a little strange has anyone ever encounted the problem where their phone will not shut down. Holding in the power button and choosing shut down just restarts it. Choosing shut down from fastboot also just restarts it. I even tried locking the bootloader with the December update , but it still happens..... Strange
Click to expand...
Click to collapse
Is it plugged in when this happens? If so, try again with the cable disconnected. Else, it's think this means a sticky power button.
Thank you, but it happens unplugged. It says shutting down..... Turns off for about 3 to 4 seconds..... Then the white screen to boot..... If it was a sticky button, wouldn't to keep going to the power menu?
Have you tried rebooting to safe mode then seeing of you can shutdown? If it works in safe mode, it's probably an app causing a weird glitch.
Same thing happened to me a few months ago, solved with a factory reset.
Did this get resolved, I have a pixel3 that will only stay turned off of the charger cable is connected. everything else works fine.
Latest Android 11, multiple factory resets and still will not stay shutdown.
Power button does not seem to be stuck, doubletap for camer works flawlessly and so does any other function I can think of.
andy hall said:
Did this get resolved, I have a pixel3 that will only stay turned off of the charger cable is connected. everything else works fine.
Latest Android 11, multiple factory resets and still will not stay shutdown.
Power button does not seem to be stuck, doubletap for camer works flawlessly and so does any other function I can think of.
Click to expand...
Click to collapse
Did you solve your problem? I have exact issue.
gtsik said:
Did you solve your problem? I have exact issue.
Click to expand...
Click to collapse
Did you figure this out? I got the same issue after wiping phone and going from 9 to 12 when trying to clean it up for a trade in.
amtrak23 said:
Did you figure this out? I got the same issue after wiping phone and going from 9 to 12 when trying to clean it up for a trade in.
Click to expand...
Click to collapse
I was in repair shop and they told me it's hardware problem and needs expensive repair. I refused to repair. Phone still works and will see what will happened.
Hello, I have an a5y17lte with latest official LineageOS 18.1 build which yesterday started exhibiting an issue with the screen where when waking it up the screen stays black. I was able to fix it by force powering it off, but soon it happened a couple more times, one time the screen not turning on after the 1st force reboot and thus requiring multiple force power offs to start working again. Later on during that day there were no issues with the screen, but since this morning this happens constantly and regularly and it always takes more than one force reboot to fix it. I have tried reflashing the system image, which worked for a bit before it started doing the same thing once again. Does anyone have a clue what could possibly be causing this?