SOLVED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
After the 4.4.4 update, I failed to lock the screen by pressing the power button...........
I update from 4.4.3 to 4.4.4 when i see the official notification.
Now, the screen can only be locked when timeout (i set to 30 seconds).
It is not hardware failure of the power button, as when i hold it, it can show me the dialog for me to shutdown the phone.
Anyone else????
help
Amazing, I solved it after i wipe the cache :laugh::laugh::laugh::laugh::laugh:
Good job! Glad you were able to fix it!
I had same problem.but rebooting solved
It
Sent from my Nexus 5 using XDA Free mobile app
Had no problem on my side. Unlocked rooted 4.4.3 was running with TWRP update went smooth
Sent from my Nexus 5 using XDA Premium 4 mobile app
Related
att one x, rooted and bootloader just unlocked. i had just restored a titanium backup when it suggested a reboot. after the reboot i get the messages com.android.phone and process.acore have stopped. then the phone reboots and the same messages again. anybody know how to get out of this loop?
We're you restoring Titanium Backup to a new ROM? It sounds like you could have accidentally installed the past phone application or other system applications. I suggest restoring again and checking the apps that are being restored
Sent from my HTC One X using xda premium
Hope you have not restored system apps or data... just do a factory reset... and restore only user apps... also u have not mentioned about whether you installed any new ROM, if yes then app data compatibility issue may crop up between different ROMs . Try the first solution first however....
Sent from my GT-N7000 using xda premium
ruffdogtechy said:
We're you restoring Titanium Backup to a new ROM? It sounds like you could have accidentally installed the past phone application or other system applications. I suggest restoring again and checking the apps that are being restored
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i cant get the phone to stop rebooting long enough to do anything ive tried to do a factory reset and clear storage but all i get is an htc warning about development purposes
Can you get into the downloader? I'm prettysute you can access it by holding do the sleep/wake button and the volume button for about 30 seconds to a minute
Sent from my HTC One X using xda premium
Hold down the power button until the capacitive buttons start blinking (about 5 seconds). Keep holding it until the phone shuts off. The phone will be off for a few seconds, then reboot. While its off (screen and buttons dark), hold the volume down rocker. Don't release it until you see the white bootloader screen, you can factory reset from there, or go into recovery and do it.
solution
use cwm recovery reset everything(including data,system,cache..) ,switch to twrp and install any rom and see it working.it worked for me too(i had this problem).
i keep getting the System UI stopped error, hit ok comes back.
i have tried wiping the whole phone with TWRP before flashing cm12 rom, phone boots just fine, hit the power button to turn off the display, turn it back on i get the system ui stopped error over and over.
tired installing XPerience rom same problem, so its not a cm12 problem.
does anyone know whats causing this?
yes i have used the search and google, nothing i found fixed the problem.
please help
Does the nav and status bar disappear when you press ok?
Sent from my VS985 4G using XDA Free mobile app
DEFNUB said:
Does the nav and status bar disappear when you press ok?
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
yes it disappear, screen also flash black for a small bit before coming back with the error.
Whenever I tried rebooting the phone, 9 out of 10 times, the phone will stuck in black screen and I have to pull the battery to fix that. Is anyone else having this issue? Any fix?
Thanks.
Well im on lollipop and i dont have that issue so i would suggest a factory reset to see if that works
Sent from my LG-D850 using XDA Free mobile app
I have a weird touchscreen issue after flashing 5.1.1. (D2303_Vodafone NL_1281-3810_18.6.A.0.175_R4C) on D2303
After startup, when I need to enter the SIM unlock pin the touchscreen is not responding for about 5 minutes. After that it suddenly comes alive and the phone is operating normally.
I've not rooted this (for now) nor did I do any other modifications, although before when I tried to root it I screwed it up (because of device encryption) and the device did a complete reset after 7 wrong (but correct) PIN attempts.
The phone is not encrypted this time.
Anyone with similar experience or any clue what could be wrong?
i have the same problem but that happened after rooting my phone
D2302
Just lock and unlock with the power button and everything to be done... I thing all of us having the same problem
Sent from my D2303 using XDA Free mobile app
This is a bug that Sony didn't find out.Also the camera driver in Lollipop is making our photos worse that with kit kat.
Just like the title says. I'm using mm 6.0.1., stock, non-rooted. This started after I uninstalled Good Lock App from Galaxy App store. I already wiped cache using the up/home/power button method. I wiped the cache in Galaxy App app, I wiped the cache in Googles App store app for S'n'G's. Any help would be greatly appreciated. And thank you in advance.
Update: Just reinstalled Good lock from the Galaxy App Store to see if it would restore the power button and recent app. It restored the recent app, but not the power button. To clarify, when I hold the power button down, it does not give me the option to power off/ restart etc. It just reboots and starts at the Sprint Screen. Trying to find solution before I have to do a factory reset.
Update: Will probably do a factory reset. All sorts of problems now. When I try to transfer files, open other programs, it all leads to a reboot. A real FUBAR. Not sure if this has to do with it as well. I use the Package Disable Pro App, when I upgraded to MM 6.0.1, I forgot to enable all my packages. I re-enabled them now to see if that would solve my dilemma, but it does not. So I will go through a factory reset and update how it comes out.
Update: I was able to finally do a factory reset after some trial and error. Will probably not use that Good Lock app until there is a more stable version. Everything seems to be back to normal, power button works fine and no more reboots by accessing apps or settings.
DirtyStacks said:
Just like the title says. I'm using mm 6.0.1., stock, non-rooted. This started after I uninstalled Good Lock App from Galaxy App store. I already wiped cache using the up/home/power button method. I wiped the cache in Galaxy App app, I wiped the cache in Googles App store app for S'n'G's. Any help would be greatly appreciated. And thank you in advance.
Update: Just reinstalled Good lock from the Galaxy App Store to see if it would restore the power button and recent app. It restored the recent app, but not the power button. To clarify, when I hold the power button down, it does not give me the option to power off/ restart etc. It just reboots and starts at the Sprint Screen. Trying to find solution before I have to do a factory reset.
Update: Will probably do a factory reset. All sorts of problems now. When I try to transfer files, open other programs, it all leads to a reboot. A real FUBAR. Not sure if this has to do with it as well. I use the Package Disable Pro App, when I upgraded to MM 6.0.1, I forgot to enable all my packages. I re-enabled them now to see if that would solve my dilemma, but it does not. So I will go through a factory reset and update how it comes out.
Update: I was able to finally do a factory reset after some trial and error. Will probably not use that Good Lock app until there is a more stable version. Everything seems to be back to normal, power button works fine and no more reboots by accessing apps or settings.
Click to expand...
Click to collapse
For future reference if you open the good lock app from the app drawer there's an option to uninstall it.
Sent from my SM-N920P using XDA-Developers mobile app
zomgalama said:
For future reference if you open the good lock app from the app drawer there's an option to uninstall it.
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
I knew that already, and I did. That is how this whole problem started. I mentioned that I did uninstall in my original post. Thanks for the obvious.
DirtyStacks said:
Just like the title says. I'm using mm 6.0.1., stock, non-rooted. This started after I uninstalled Good Lock App from Galaxy App store. I already wiped cache using the up/home/power button method. I wiped the cache in Galaxy App app, I wiped the cache in Googles App store app for S'n'G's. Any help would be greatly appreciated. And thank you in advance.
Update: Just reinstalled Good lock from the Galaxy App Store to see if it would restore the power button and recent app. It restored the recent app, but not the power button. To clarify, when I hold the power button down, it does not give me the option to power off/ restart etc. It just reboots and starts at the Sprint Screen. Trying to find solution before I have to do a factory reset.
Update: Will probably do a factory reset. All sorts of problems now. When I try to transfer files, open other programs, it all leads to a reboot. A real FUBAR. Not sure if this has to do with it as well. I use the Package Disable Pro App, when I upgraded to MM 6.0.1, I forgot to enable all my packages. I re-enabled them now to see if that would solve my dilemma, but it does not. So I will go through a factory reset and update how it comes out.
Update: I was able to finally do a factory reset after some trial and error. Will probably not use that Good Lock app until there is a more stable version. Everything seems to be back to normal, power button works fine and no more reboots by accessing apps or settings.
Click to expand...
Click to collapse
Yeah the same thing was happening to me after I updated to marshmellow. What I did to fix it was just reinstall the tar file here on XDA and it works fine after
Sent from my SM-N920P using XDA-Developers mobile app