Hi fellow lineageos users,
I have this lockscreen that appears sometimes on my Xiaomi Mi 5s with the last official LineageOS ROM. It's pretty rare, but when it happens I cannot unlock my device and have to force reboot it. I was able to switch the torch on (by keeping the power button pressed), and even to take this screenshot, but I couldn't unlock it and had to do a force reboot to be able to use the phone again.
Any ideas where it could come from ?
I don't know... maybe is a screensaver when the phone go into deep sleep [emoji32] (i had the same problem on AOKP but without this screen, then i found a .zip to fix it)
Inviato dal mio ALE-L21 utilizzando Tapatalk
I have had almost the same exact issue with a LG G4 running LOS 14.1. Happened a few times. I have no idea what triggered it.
In my case I got a lock screen with a circle in the middle that I could not unlock no matter what I tried (never got any password prompt or anything), and like the OP, had to reboot by pulling the battery on the phone (I don't think any of the usual restart button combos worked) in order to be able to gain access again.
Who knows what I would have done if like most phones these days the battery was non-removable - probably have to wait until it went dead..
Related
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
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.
Hey everyone,
couldn't find a topic about this yet so here I am. I recently got a Mi A2 lite and happily unlocked it, rooted it and so on. Worked perfectly fine till yesterday. Then suddenly it started to freeze. Meaning the fingerprint sensor didn't have any reaction anymore. I couldn't use the screen anymore either. I was able to start the screen by pressing the power button once, it was also possible to press it twice to start the camera or keep pressing it to show the restart menu or forcefully restart it, but no matter what I did I couldn't interact with anything on the screen. So I had to forcefully restart the phone and then it was working fine again until some time later.... I've had it like 6 times in 90 minutes so I decided to make a clean install and see what happens. Rooted the phone again and it was the same once again... Didn't change anything.
Now I locked my phone again (getting ready to send it back) and will try "stock" and see if the root has anything to do with it.
My guess is that it's a hardware problem but before I send it back I wanted to check if anyone here has another idea or solution.
Thanks in advance
Edit: Stock isn't working either, error still happening. I'm returning it.
I was using the evolution rom and after about 5 days this will happen about 2-5 times a day. i will go to unlock my phone randomly and it is unresponsive even to finger printing unlock or regular unlock it'll freeze on the lockscreen and it will seem only force rebooting by holding the power button "fixes" it. i clean flashed the Syberia rom and it still is happening. is there any way to stop this?
if anyone wants any error log just tell me how to get one when it happens and I'll post it. thanks in advance
Yesterday my Poco F3 crashed out of nowhere while I was just texting someone. Now it's stuck in a bootloop where it's constantly rebooting itself, I can only enter fastboot or recovery for like 2 seconds, after that it reboots again.
I was able to get it on later by holding all buttons, but it quickly crashed again and now holding all buttons doesn't work.
I'm running the latest version (as of now)
Edit: No the bootloader is not unlocked, it's fully unmodified.
Has anyone else had this problem?
It's your phone ok now?If it's still broken,I think it's a motherboard issue or maybe a software bug.Anyways,if you are able to boot into recovery by hording power+vol up,try a data wipe
ZaroxJH said:
Yesterday my Poco F3 crashed out of nowhere while I was just texting someone. Now it's stuck in a bootloop where it's constantly rebooting itself, I can only enter fastboot or recovery for like 2 seconds, after that it reboots again.
I was able to get it on later by holding all buttons, but it quickly crashed again and now holding all buttons doesn't work.
I'm running the latest version (as of now)
Edit: No the bootloader is not unlocked, it's fully unmodified.
Has anyone else had this problem?
Click to expand...
Click to collapse
I've had this issue in the past with Samsung phones. The root cause for those was a jammed power button. I had to give it a vigorous shake/jerk to get it back to normal but it would happen again out of nowhere. Depending on how much you actually press the button, there's a very good chance that it could be the reason.
I had the exact same issue yesterday. I had wiped data from the menu and it was fixed. I don’t know why did that happen out of the blue. If any one knows what issue that is, please let me know.
Happened to me today.
I pressed power button quickly for a while. Then, when rebooted in system, i disabled pin lock fast and reboot in recovery.
Wipe dalvik cache seems resolved the problem to me until now.
I'm in Xiaomi.eu 13.0.7
Sounds like your hardware power button is slightly depressed. Even when you're not touching the button, it reboots every few seconds.
Something different happened to me yesterday. It was clearly the power button. If I touch the power button (like for fingerprint unlock), it would identify as power button pressed. So my phone started bootlooping, but not so frequently. And power menu was showing up more frequently.
What I did to fix it was swipe a soft tissue through the side of the phone (where power and vol buttons are placed).
the exact thing happenend to me yesterday and I don´t know how to fix it. i tried to flash twrp but now my device just reboots to fastboot mode about every 5 seconds and i can´t flash anything that takes longer than that. I would be happy if someone knew how to fix this
If u can open the phone get the power button flex disconnect then try again to see if that fix
Hello, i have had the same issue, did you also noticed color leaking when it enters poco logo? like a color lining on the screen which changes location with every reboot? i have submitted my phone to service center, but they are telling me it's motherboard and asking cost which is more than a phone. i was texting someone too when it happened.
Alipk52 said:
Hello, i have had the same issue, did you also noticed color leaking when it enters poco logo? like a color lining on the screen which changes location with every reboot? i have submitted my phone to service center, but they are telling me it's motherboard and asking cost which is more than a phone. i was texting someone too when it happened.
Click to expand...
Click to collapse
What ?
The Poco F3 costs new actually 300 €.
They ask you for more ?
Try a local repair shop, probably a CPU issue a reballing of the CPU should not cost more than 30 to 40 €..
Everything else is a rip off..
L8ter said:
What ?
The Poco F3 costs new actually 300 €.
They ask you for more ?
Try a local repair shop, probably a CPU issue a reballing of the CPU should not cost more than 30 to 40 €..
Everything else is a rip off..
Click to expand...
Click to collapse
They told me the Motherboard needs to be replaced, which is really expensive, i have said no to them and asked for a return of device, i wonder if Motherboard is faulty, how come it enters fastboot mode? I have tried recovery mode as well, it entered once, i flashed xiaomi eu update over existing and it ended with error, now i have tried to boot into recovery couple of times only but it didn't booted, i sent it to service center. I think i should have tried better with recovery or fastboot mode. Xiaomi service centers all over the world is crap and known to impose different faults even if it's not there. That's why i don't believe them.
I still have my Samsung S7 Edge and from time to time, it turns itself off and you can not restart it if you press the power button.
You can boot it into Odin download mode, but nothing else.
Only if you put in the USB cable to load it, it will boot.
Also strange, I'm saying this because you asked why your device boots into fastboot mode, but nothing else
Devices are sometimes very strange and not reasonable the way the work or not.
Hope you get it fixed for reasonable costs.
Good luck buddy .