Hi All, quick question. Since upgrading to 5.1 on my verizon Moto X, I noticed that they removed the option to restart the phone. When I just "power off" all my recent apps are still remaining. This makes me think it is not truly resetting cache and doing a full re-boot. Is this true? If so, is there a way to do a "cold boot" or full restart? (Not wipe, just reboot)
Thanks in advance!
mikeosu said:
Hi All, quick question. Since upgrading to 5.1 on my verizon Moto X, I noticed that they removed the option to restart the phone. When I just "power off" all my recent apps are still remaining. This makes me think it is not truly resetting cache and doing a full re-boot. Is this true? If so, is there a way to do a "cold boot" or full restart? (Not wipe, just reboot)
Thanks in advance!
Click to expand...
Click to collapse
i believe you need to root to enable reboot mode.
jco23 said:
i believe you need to root to enable reboot mode.
Click to expand...
Click to collapse
Bummer, kind of lame there is no option.
Sent from my XT1060 using Tapatalk
mikeosu said:
Bummer, kind of lame there is no option.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
check on the play store, I know that some apps (although may require root), may let you reboot. look at titanium backup for example.
jco23 said:
check on the play store, I know that some apps (although may require root), may let you reboot. look at titanium backup for example.
Click to expand...
Click to collapse
That's a little annoying Motorola would make it so that I have to root my phone just to reboot it.
Sent from my XT1060 using Tapatalk
Not Motorola, Google Android.
Sent from my Moto X using XDA Free mobile app
jco23 said:
Not Motorola, Google Android.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Oh, didn't realize it was Android that prevents that. So there is no way to really refresh the system if it seems to be getting bogged down?
mikeosu said:
Oh, didn't realize it was Android that prevents that. So there is no way to really refresh the system if it seems to be getting bogged down?
Click to expand...
Click to collapse
Turn it off, turn it back on.
Jizzylax said:
Turn it off, turn it back on.
Click to expand...
Click to collapse
Oh, I was doubting whether that really reset anything because all my recent apps are still there. But if it has a similar effect, awesome.
Sent from my XT1060 using Tapatalk
mikeosu said:
Oh, I was doubting whether that really reset anything because all my recent apps are still there. But if it has a similar effect, awesome.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
here's how to root on the latest OS: http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125
you may also be able to boot in the stock recovery by holding down all 3 buttons (power + volume up + volume down) for 5 seconds, then release power & volume up. once in recovery, navigate with the volume down button only (volume up = enter). from there, you may be able to wipe cache/dalvik which can help clear out the cob webs. this is safe and does not wipe data or factory resets.
also, if you go to your settings -> storage, you can clear out cached data.
hope this helps.
Related
So to quickly sum up, the battery of my Moto X is good for precisely 3 days after I got it, and then started draining quickly in it's sleep. I performed a factory reset, installed the same applications, and the battery was once again good for 3 days, until it experienced the same symptoms. Anybody have any idea why this would happen? Thanks.
P.S. Battery stats reports that my Wi-Fi is always on even if I turn it off. The only way to "turn off" the wifi is to turn off the low-battery location tracking in the wifi menu, so this is kindof leading me to believe that the phone is pinging for location quite often, thus always keeping my wifi on. Just a thought.
Guessing you are on 4.4
Sent from my XT1058 using Tapatalk
murso74 said:
Guessing you are on 4.4
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Yep. I just ran my phone in safe mode for a bit and the battery is marginally better.
I troubleshoot for a living. You've already solved the mystery:
It's fine for 3 days. You install YOUR (key) usual apps. It doesn't sleep....
It's one of your apps
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
I troubleshoot for a living. You've already solved the mystery:
It's fine for 3 days. You install YOUR (key) usual apps. It doesn't sleep....
It's one of your apps
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
See you would be right, if it weren't for the fact that I install and completely set up all my apps within an hour of restoring the phone, and don't install any after that.
Ok so I've now taken the device out of safe mode, let it run on Wifi a bit, and then let it run on LTE. Even though the phone isn't registering it, the device is waking. I can determine this by the CPU run time vs the screen-on time vs the wake time. You can see in the screenshots.
You can see the dip as soon as I turn on LTE. The CPU total goes up so wakelocking is the problem on idle, even though it's not showing it.
dsass600 said:
So to quickly sum up, the battery of my Moto X is good for precisely 3 days after I got it, and then started draining quickly in it's sleep. I performed a factory reset, installed the same applications, and the battery was once again good for 3 days, until it experienced the same symptoms. Anybody have any idea why this would happen? Thanks.
P.S. Battery stats reports that my Wi-Fi is always on even if I turn it off. The only way to "turn off" the wifi is to turn off the low-battery location tracking in the wifi menu, so this is kindof leading me to believe that the phone is pinging for location quite often, thus always keeping my wifi on. Just a thought.
Click to expand...
Click to collapse
Do you have a custom kernel or ROM installed? these kind of problems are usually caused by a 'bad flash'
dsass600 said:
See you would be right, if it weren't for the fact that I install and completely set up all my apps within an hour of restoring the phone, and don't install any after that.
Click to expand...
Click to collapse
So you're saying that out of ALL of your apps, it's impossible that one creates a rogue or persistent process? Lol. Well, you're wrong.
I'm done trying to help. Examine your apps. I gave you your answer.
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
So you're saying that out of ALL of your apps, it's impossible that one creates a rogue or persistent process? Lol. Well, you're wrong.
I'm done trying to help. Examine your apps. I gave you your answer.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
that's not what I'm saying, and that's not what you suggested either. You said to examine the last after I installed and see if it's waking my device. Then I told you that I installed all my applications immediately after factory reset on the device. It makes no sense that an app would not display rogue behavior until three days later. Plus, after running in safe mode, the battery life did not improve.
joemon871 said:
Do you have a custom kernel or ROM installed? these kind of problems are usually caused by a 'bad flash'
Click to expand...
Click to collapse
nope. Completely stock.
dsass600 said:
nope. Completely stock.
Click to expand...
Click to collapse
Would you be willing to root your phone and installing a custom recovery so you can wipe cache and dalvik cache? Or maybe manually install a ROM yourself. Its worth a try. You can just Unroot it back if you don't want root
joemon871 said:
Would you be willing to root your phone and installing a custom recovery so you can wipe cache and dalvik cache? Or maybe manually install a ROM yourself. Its worth a try. You can just Unroot it back if you don't want root
Click to expand...
Click to collapse
yes but I do not want to lose root as soon as the 4.4.2 update is released on February 1st. I plan on rooting the phone after that. I'm worried that after I root though, I discover it is a hardware issue, its going to be a long process of unrooting the phone to send back to Motorola.
Get Gsam and see what is going on. Simple. The stock battery info is next to useless.
Then you can take screen shots that have better info.
Sent from my XT1058 using Tapatalk
If you suspect its a hardware issue then its best to have the phone replaced as soon as possible before messing with it too much you know?
Sent from my SGH-M919 using Tapatalk
I figured it out. Installed a CPU monitoring application since I'm not rooted and saw that the phone was barely sleeping. Purely by chance I guessed it was Snapchat, greenified the application, and it worked! Thanks for your help guys.
dsass600 said:
I figured it out. Installed a CPU monitoring application since I'm not rooted and saw that the phone was barely sleeping. Purely by chance I guessed it was Snapchat, greenified the application, and it worked! Thanks for your help guys.
Click to expand...
Click to collapse
So.....I was right?
Rogue processes happen, my man.
Sent from my XT1060 using Tapatalk
Gsam would have pointed it out quickly. Its my number one app.
Sent from my Moto X cellular telephone...
battery drain
I've had the same issue over the last 2 days, and the Kernel (Adroid OS) takes 26.5% of the battery drain, allthough CPU has only had to work 3m 30s...
Gsam. Lol
Sent from my Moto X cellular telephone...
Has anyone else noticed that their Moto X doesn't seem as "snappy" as it used to? It feels like I'm waiting a lot longer for the camera to open and take a picture, it takes several seconds to attach a photo to a message using Hangouts, SwiftKey doesn't pop up as quickly, etc. I've been running 4.4 since AT&T pushed it out. I'm considering doing a factory data reset to see if it helps speed things up, but that's a bit of a hassle so I've been holding off. Just wondering if anyone else has noticed this.
Nope. Has never slowed down here.
Sent from my Moto X cellular telephone...
Wipe dalvik and cache and see if that helps.
Sent from my Dev Edition Moto X
lifetechnician said:
Has anyone else noticed that their Moto X doesn't seem as "snappy" as it used to? It feels like I'm waiting a lot longer for the camera to open and take a picture, it takes several seconds to attach a photo to a message using Hangouts, SwiftKey doesn't pop up as quickly, etc. I've been running 4.4 since AT&T pushed it out. I'm considering doing a factory data reset to see if it helps speed things up, but that's a bit of a hassle so I've been holding off. Just wondering if anyone else has noticed this.
Click to expand...
Click to collapse
Wow! I almost made a thread about having this same issue recently. My x keep lagging and home screen scrolling was choppy and opening apps was very choppy also. I did clear cache partition and it has fixed it so far.
Sent from my XT1060 using Tapatalk
Schaweet said:
Wipe dalvik and cache and see if that helps.
Click to expand...
Click to collapse
I reset the cache, will update with results.
I've been using this.
http://forum.xda-developers.com/showthread.php?t=2132878
I think it helps out but not too sure if anyone wants to test it out. Just flash through recovery I have safestrap.
Schaweet said:
Wipe dalvik and cache and see if that helps.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Forgive the noob question, but can this be done if I'm not rooted? If so how? Thanks for any help.
Sent from my XT1060 using XDA Premium 4 mobile app
Ryano89 said:
Forgive the noob question, but can this be done if I'm not rooted? If so how? Thanks for any help.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good question. I haven't had stock recovery on a device for longer than about 20 seconds so I'm not sure. Maybe someone else can answer that question.
Sent from my Dev Edition Moto X
Schaweet said:
Good question. I haven't had stock recovery on a device for longer than about 20 seconds so I'm not sure. Maybe someone else can answer that question.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I don't remember where I found these instructions but they work for me.
To wipe the cache partition, follow these steps:
With the phone powered off, press and hold the Volume down key and Power key for 2-3 seconds until the the Boot options screen appears.
Release the keys.
Use the Volume down key to scroll to highlight Recovery.
Press the Volume up key to select.
The phone will display the Motorola logo then the Android recovery screen.
Once the Android recovery screen displays, press and hold the Volume up key for 10-15 seconds.
Quickly tap and release the Power key.
The Android recovery screen will appear.
Scroll down using the Volume down key to highlight wipe cache partition.
Use the Power key to select.
The phone will power-cycle.
Don't know about other models, but such an option is not available on my XT1053. Did I miss something here?
Sent from my XT1053 using Tapatalk 2
x2h said:
Don't know about other models, but such an option is not available on my XT1053. Did I miss something here?
Sent from my XT1053 using Tapatalk 2
Click to expand...
Click to collapse
Root with gravity box.
MOTO X SLAPPED
If you're rooted and don't want Xposed/gravity box, try quick boot from the playstore. Has all the reboot, boot to recovery ...etc...options.
Sent from my N5 cell phone telephone....
I thought if you held it down it just rebooted..
Slapped X on Tapatalk
Never understood why this hasn't been implemented into stock android yet. Most of the OEM skins include it.
Flexia32 said:
I thought if you held it down it just rebooted..
Slapped X on Tapatalk
Click to expand...
Click to collapse
Thanks. That answers my question.
Sent from my XT1053 using Tapatalk 2
kj2112 said:
If you're rooted and don't want Xposed/gravity box, try quick boot from the playstore. Has all the reboot, boot to recovery ...etc...options.
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
Great app, used it for years before I got Gravity Box.
Flexia32 said:
I thought if you held it down it just rebooted..
Slapped X on Tapatalk
Click to expand...
Click to collapse
Yes, holding down Power and VOL DOWN will reboot the phone, simulating pulling the battery out. Using an app like QuickBoot or Gravity Box is just faster and more convenient.
[email protected] said:
Root with gravity box.
MOTO X SLAPPED
Click to expand...
Click to collapse
For clarity's sake: you need to obtain root, disable read/write access (probably) and then install Xposed Framework and the Gravity Box module. If you're already on 4.4.2, the only real option is holding power and volume down, as you can't revert to obtain root.
You don't have to hold volume down. Just holding power works
-Moto X-
fury683 said:
Yes, holding down Power and VOL DOWN will reboot the phone, simulating pulling the battery out...
Click to expand...
Click to collapse
FWIW - the power+vol "trick" is meant to simulate a battery pull since the battery is inaccessible (think phone frozen/unresponsive). What this means is that it is a hard stop on ALL processes, which is bad for memory allocation and may cause Android system slowness while it recovers from the abrupt stop. I never figured out if the Quick-Boot app does the same thing.
So when I hear/read people say they've performed a "soft-reboot" on their device, i often wonder what this technically means since there isn't an actual way to accomplish a "soft-reboot" gracefully. it's the equivalent of hitting the reset button on your PC while Windows is running.
640k said:
FWIW - the power+vol "trick" is meant to simulate a battery pull since the battery is inaccessible (think phone frozen/unresponsive). What this means is that it is a hard stop on ALL processes, which is bad for memory allocation and may cause Android system slowness while it recovers from the abrupt stop. I never figured out if the Quick-Boot app does the same thing.
So when I hear/read people say they've performed a "soft-reboot" on their device, i often wonder what this technically means since there isn't an actual way to accomplish a "soft-reboot" gracefully. it's the equivalent of hitting the reset button on your PC while Windows is running.
Click to expand...
Click to collapse
That's why I'd say use the quick boot app or gravity box. Then it reboots more "gracefully ".
Sent from my N5 cell phone telephone....
I am puzzled that the Moto X also doesn't have a restart. I feel like Android is so smart in so many ways, but misses some of the most basic functions...
Just root and use xposed + gravity
Enviado desde mi XT1053 mediante Tapatalk
640k said:
FWIW - the power+vol "trick" is meant to simulate a battery pull since the battery is inaccessible (think phone frozen/unresponsive). What this means is that it is a hard stop on ALL processes, which is bad for memory allocation and may cause Android system slowness while it recovers from the abrupt stop. I never figured out if the Quick-Boot app does the same thing.
So when I hear/read people say they've performed a "soft-reboot" on their device, i often wonder what this technically means since there isn't an actual way to accomplish a "soft-reboot" gracefully. it's the equivalent of hitting the reset button on your PC while Windows is running.
Click to expand...
Click to collapse
The soft reboot is exactly the same as a normal reboot from gravitybox or quickboot or anything else. The ONLY difference is that soft reboot starts the boot at a kernel level, and the 'hard' reboot starts at the bootloader level. They both stop processes in the exact same way.
Sent from my XT1060 using Tapatalk
Hey,
Ever since the OTA update my phone reboots randomly about once every two days [I'm on Verizon].
Is anyone else experiencing this?
Screen just goes black, vibrates once quickly, then its back on that LG G2/Verizon screen and then boots. Then everything is fine.
Vexorg said:
Hey,
Ever since the OTA update my phone reboots randomly about once every two days.
Is anyone else experiencing this?
Screen just goes black, vibrates once quickly, then its back on that LG G2/Verizon screen and then boots. Then everything is fine.
Click to expand...
Click to collapse
Nope... Have you done a FDR yet? It is highly recommended to do one after taking this OTA if you have ANY kind of trouble at all.
acejavelin said:
Nope... Have you done a FDR yet? It is highly recommended to do one after taking this OTA if you have ANY kind of trouble at all.
Click to expand...
Click to collapse
Fdr is a full factory reset?
Sent from my VS980 4G using Tapatalk
Vexorg said:
Fdr is a full factory reset?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yes, FDR = Factory Data Reset, basically a factory default, not reflashing the original factory images.
acejavelin said:
Yes, FDR = Factory Data Reset, basically a factory default, not reflashing the original factory images.
Click to expand...
Click to collapse
Sorry for all the questions but you're just referring to go going to settings > backup and reset > factory data reset?
Sent from my VS980 4G using Tapatalk
Vexorg said:
Sorry for all the questions but you're just referring to go going to settings > backup and reset > factory data reset?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yes
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Yes
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Cool thanks
Sent from my VS980 4G using Tapatalk
Problem still persists, I'm surprised I'm the only person getting this issue.
Vexorg said:
Problem still persists, I'm surprised I'm the only person getting this issue.
Click to expand...
Click to collapse
Your not the only one, but this is a very rare occurrence... Across all the major forums only 3 or 4 users have reported this issue.
Sent from my Nexus 4 using Tapatalk
Fairly common on custom builds
Vexorg said:
Problem still persists, I'm surprised I'm the only person getting this issue.
Click to expand...
Click to collapse
It's a fairly common occurrence for people on custom builds. I've noticed it when trying to do too many things at once.
There also apparently appears to be a link between SwiftKey and this problem from what I've read, or maybe that's an entirely different problem.
Mine have stopped after I disabled Google Services Sound Search.
hardheart1 said:
It's a fairly common occurrence for people on custom builds. I've noticed it when trying to do too many things at once.
There also apparently appears to be a link between SwiftKey and this problem from what I've read, or maybe that's an entirely different problem.
Mine have stopped after I disabled Google Services Sound Search.
Click to expand...
Click to collapse
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
substitutesam said:
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
Click to expand...
Click to collapse
I haven't looked at any logs or anything on a remotely technical level. I noticed the google sound search was eating battery so I disabled it. Reboots are gone.
substitutesam said:
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
Click to expand...
Click to collapse
hardheart1 said:
I haven't looked at any logs or anything on a remotely technical level. I noticed the google sound search was eating battery so I disabled it. Reboots are gone.
Click to expand...
Click to collapse
First and foremost, I was not rooted or using anything customer. I never tried rooting this phone because I figured there would be updates in the near future (I was optimistic).
I am also receiving:
Random Reboots
Overheating
Random Apps Crash frequently (Kindle, Search, Home, etc)
I am also using swiftkey.
Vexorg said:
First and foremost, I was not rooted or using anything customer. I never tried rooting this phone because I figured there would be updates in the near future (I was optimistic).
I am also receiving:
Random Reboots
Overheating
Random Apps Crash frequently (Kindle, Search, Home, etc)
I am also using swiftkey.
Click to expand...
Click to collapse
I believe there are known issues with the G2 and Swiftkey on stock roms (rooted, custom, or otherwise).
What language are you using on Swiftkey. I'm on Swiftkey and Carbon and I'm not having any problems.
Using English (US)
Sent from my VS980 4G using Tapatalk
Vexorg said:
Using English (US)
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I'm also on Swiftkey and am experiencing very similar issues, using English as well.
On a side note, I also work in a building that has no cell service and continuously cycles through wifi connections because the 3 networks I have entered vary greatly in strength based on a 10 ft radius of where I walk.. could this be a cause as well and is there a way to stop it from happening?
I've tried removing all of the connections except 1 wifi signal but then I'm really only connected when I'm at my desk and if I standup to walk somewhere it's disconnected...
#1stWorldProblems
These issues are still persisting... anyone think taking it to Verizon would do anything?
My phone is completely stock. I am wondering if I should just flash a new ROM or something.
Vexorg said:
These issues are still persisting... anyone think taking it to Verizon would do anything?
My phone is completely stock. I am wondering if I should just flash a new ROM or something.
Click to expand...
Click to collapse
I second this, still having random reboots and running completely stock. I'm getting close to just removing Swiftkey all together?
I stopped using swiftkey and I'm still getting random reboots
Hello and Happy Turkeyday to all. I have an issue with my wife's note. When she gets any notifications they turn the screen on and it doesn't turn off. I feel pretty knowledgeable about the android O.S. in a whole, I have my S5 rooted and running AICP. I just can't figure out why the notifications cause the screen to stay on. Has anyone else had this problem maybe you could help shed some light on my issue. Thanks in advance.
Is the phone rooted?
Sent from my SM-N910T using Xparent Pink Tapatalk 2
No she won't let me root her phone.
Same problem
I have the exact same problem on my Note 4 (N910F).
My phone is rooted and I have had the problem from the start.
I am also running a custom kernel now but the problem persists.
Any ideas on why this is happening anyone? I've got it to not turn the screen on for a notification but now it won't turn off when plugged in.
Turn off the lock screen notifications, or everything you can on the lock screen settings, most likely something is causing the screen to wake lock. My bet is the weather widget.
Sent from my SM-N910T using XDA Free mobile app
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Bullet_King1996 said:
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Click to expand...
Click to collapse
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Bullet_King1996 said:
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Click to expand...
Click to collapse
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
u1988 said:
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
Click to expand...
Click to collapse
arjun90 said:
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
Click to expand...
Click to collapse
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Boot into recovery and clear cache
or factory reset like everyone said
Great to hear all is well. Please tell me that you're going to root.
u1988 said:
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Click to expand...
Click to collapse
arjun90 said:
Great to hear all is well. Please tell me that you're going to root.
Click to expand...
Click to collapse
It's not my phone, so for now no need to root .
btort1 said:
Boot into recovery and clear cache
or factory reset like everyone said
Click to expand...
Click to collapse
I gave you Another solution.