Related
I've been constantly battling sleep issues. I am on PRI/NV 1.77 and latest radio. I tried downgrading to 1.77 just recently to see if it would fix it and it hasn't, but I'm staying put.
Running latest MIUI and Savage 1.6 kernel.
Spare parts had been showing on average 50% running time even though my screen on time would be something like 5%. I had read that ideally these ratios should match, since it means your phone is properly sleeping.
Spare parts shows paltry wake locks of just a few seconds or minutes for Android System as the top app. I've killed all my widgets and even tried airplane mode and don't notice too much of a drop. After getting rid of all updating widgets (minimal text and the MIUI cal widget) and stopping google calendar sync I'm currently at 30% running vs 5% screen on. I've basically got everything that would run in the BG disabled -- set cpu, system monitor, etc. Is this a "good ratio"? Any other ideas on debugging what seems to be an obvious wake lock? I've looked at logcat and don't see a thing that looks interesting, hardly any activity. Am I just being crazy or does it seem like I still have a wake lock?
Thanks for reading
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
freeza said:
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
Click to expand...
Click to collapse
Thanks for the reply.
So, this is a bad ratio then, i'm not nuts?
I kill EVERYTHING then sleep and i'm still seeing the issues. Is there some more fool proof way I can guarantee nothing is running before sleeping? My guess would be something syncing more than it should have. Should I try toggling everything app's sync off and then sleeping?
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
lil-dice said:
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
Click to expand...
Click to collapse
Interesting, I had that UID 10018 problem before and I never figured it out. It maybe Google Talk, Gmail, or even the Calendar. You may have to try clearing caches of one or all three to really see.
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
lil-dice said:
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
Click to expand...
Click to collapse
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
freeza said:
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
Click to expand...
Click to collapse
I'm not sure how to get to that in MIUI, in battery settings i jut see my minutes since unplugged. No Awake time.
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Saturn2K said:
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Click to expand...
Click to collapse
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
lil-dice said:
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
Click to expand...
Click to collapse
That's just how it is for all AOSP kernel using roms. Their wifi sleep mode is absolutely terrible. On the plus side, it seems as though it doesn't use an absurd amount of battery to keep the wifi on.
So after using about 3 GB kernels (Nubecoder, mkasick, IAP) for the past few days, I've noticed that my CPU Spy app has not detected any deep sleep frequencies whatsoever. Is this normal? Because from what I can remember, past Froyo kernels I've run have always used deep sleep frequencies when left idle.
Sent from my SPH-D700 using xda premium
From what I've read, we don't literally use deep sleep, but I believe it can be done by a kernel dev taking source from a modified nexus kernel. To my knowledge, our epics aren't really ever entering deep sleep (unless you count shutting off your phone as deep sleep, lol) just a hibernation-ish sleep? Like a pre-quel to deep sleep, but no 'true' deep sleep with the kernels we have at the moment. I sure do wish a kernel dev looked into it though. The battery savings would be insane that it even makes ME want to cook the code into the kernel if I had the proper experience.
Sent from my SPH-D700 using XDA App
No that is not normal. If you have the phone off charge, screen off and not using it for about 15 minutes, some deep sleep should be seen in CPUSpy. It does not sleep while on charge. If you cannot obtain deep sleep according to CPUSpy you should Odin back to stock and move forward from there or get better battery stats and try to find out what is keeping your phone awake. Perhaps a bad sync or chat app like gtalk, google + or something like that.
I've noticed recently that when using the torch on my phone the phone doesn't go to sleep, in fact it keeps running at 400MHz. It definitely didn't used to do this because I could leave it on for hours andit would hardly drain the battery. Now it shoots ddown.
Any ideas why? I'm using Omega 9.1 with Redpill, whatever the latest is. The same happens with the status bar control or tesla led.
Any ideas about this? Strange that turning the torch on makes the phone stay at 400MHz. Also when using the status bar Assist Light function the UI crashes if auto rotate is on and the phone turns.
Well it's not the Redpill kernel. I just flashed Perseus and it's the same. Seems it's stuck at 200, not 400 like I thought earlier. I might try the newest Omega to see if that helps.
It might not sleep (which imo sounds normal since it has a task going on)
But leaving your flash on for hours cannot be good for it.
Sent from my GT-N7100 using xda premium
I'm fairly sure it didn't before but I might be wrong. I noticed my phone warming up while using it in work during the week (when the electric was off) which it definitely didn't do before.
Can't see any reason why it would be bad. Plenty of LED torches out there, it'll just use up the battery a bit.
No it's not bad. Even if the flash goes out for excessive usage it's pretty cheap to replace. But the device shouldn't go to deep sleep, it's not only a torch, it's an app running, that's why it could never go to deep sleep, normal.
'Swyped' from my GT-N7100
jujuburi said:
No it's not bad. Even if the flash goes out for excessive usage it's pretty cheap to replace. But the device shouldn't go to deep sleep, it's not only a torch, it's an app running, that's why it could never go to deep sleep, normal.
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
Fair enough. I may have been getting mixed up with the FM radio. That deep sleeps unless radio information is turned on. And I was using the torch at the same time so may have got mixed up possibly.
Anyone notice problems with the NY Times app recently? I noticed some high network activity out of my Note Pro over the last few days, and dug into it last night. Turned out, my tablet never went to deep sleep, and looking at battery usage, the NY Times app was behind only the OS and System.
I can't uninstall the NY Times, but I can revert to the factory image, and that seems to have put a halt to the network activity, and also the tablet is now going into deep sleep again. So it looks like it was an app update, somewhere along the way?
What's deep sleep as opposed to sleep as opposed to going into airplane mode?? Your posting about the ny times and sleep is difficult to understand.
ericbergan said:
Anyone notice problems with the NY Times app recently? I noticed some high network activity out of my Note Pro over the last few days, and dug into it last night. Turned out, my tablet never went to deep sleep, and looking at battery usage, the NY Times app was behind only the OS and System.
I can't uninstall the NY Times, but I can revert to the factory image, and that seems to have put a halt to the network activity, and also the tablet is now going into deep sleep again. So it looks like it was an app update, somewhere along the way?
Click to expand...
Click to collapse
nychotxxx said:
What's deep sleep as opposed to sleep as opposed to going into airplane mode?? Your posting about the ny times and sleep is difficult to understand.
Click to expand...
Click to collapse
Not difficult to understand at all, this is apparently a wake lock issue with the application.
Tapping the power button to turn off the screen puts the device in sleep mode but CPU speed still varies as background activity continues. Application processes can place wake locks on the CPU to keep it from going into deep sleep which is the lowest power consumption setting. A device that never goes into deep sleep will experience higher battery drain with the screen off for extended periods than one that does go into deep sleep. Sleep has nothing to do with airplane mode, which turns off all radios and has no direct impact on CPU.
First thing I would try with the NY Times app is turn off all notifications for it. Personally I don't use it and have it frozen so I can't verify the wake lock issue on my device.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
First thing I would try with the NY Times app is turn off all notifications for it. Personally I don't use it and have it frozen so I can't verify the wake lock issue on my device.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Much better explanation than I could have given, thanks! So wish I could root my tablet (a Verizon...), feel like I'm trying to debug things with both hands tied behind my back!
So far, the NYT problem hasn't come back - can't freeze or uninstall it without root, but have removed it from Magazine UI and basically backed out all updates by restoring it to its factory image and clearing its data. BTW, it was set to only get updates every 4 hours. Obviously it had a different idea.
Yeah I hate it when apps get like that.
It's times like that where I'll use Greenify sparingly to push the misbehaving app into hibernation. Otherwise I'll just let android do it's thing.
A few days ago, I noticed the NY Times app only it's you view 10 articles for free every month. I was going to say, why not trash that garbage? It requires root, though, since it's actually a system app. That is just profoundly stupid.
At least Samsung didn't pick CNN as it's news app, amirite?
Hey guys,
I always wondered, why my phone wouldnt Deep Doze (according to Gsam). Be aware: I am not talking of the Deep Sleep (the CPU state, that is happening).
I always lost between 1,5 and 2% per hour overnight with the phone just sitting on the table, connected to the home wifi.
I disabled the Sim-Card (physical one, no e-sim) before going to bed tonight and my phone deep dozed now.
Yes, I am aware that there is this Mobile Network Standby Drain Bug. But since I disabled "Always use mobile date" in developer settings and was using WIFI during mentioned times, I dont know how that appiles to me.
Anyone has ideas?
Thanks!
Put it into airplane mode overnight and see if you get the drain. At least you'll know if it's a app or radio issue.
xflowy said:
I disabled the Sim-Card (physical one, no e-sim) before going to bed tonight and my phone deep dozed now.
Click to expand...
Click to collapse
Blade22222 said:
Put it into airplane mode overnight and see if you get the drain. At least you'll know if it's a app or radio issue.
Click to expand...
Click to collapse
no offense dude, but did u read my post? see above.
What the heck is deep doze?
As stated above, it is a doze state that is being entered after the light doze. Check Gsam battery for your stats regarding deep doze.
I had the same problem, dropping 2-3% per hour over night. I turned 5G off, turned off 'mobile data always active' in developer settings and turned off adaptive connectivity.
Now im only losing .2-.5% per hour overnight.
xflowy said:
Hey guys,
I always wondered, why my phone wouldnt Deep Doze (according to Gsam). Be aware: I am not talking of the Deep Sleep (the CPU state, that is happening).
I always lost between 1,5 and 2% per hour overnight with the phone just sitting on the table, connected to the home wifi.
I disabled the Sim-Card (physical one, no e-sim) before going to bed tonight and my phone deep dozed now.
Yes, I am aware that there is this Mobile Network Standby Drain Bug. But since I disabled "Always use mobile date" in developer settings and was using WIFI during mentioned times, I dont know how that appiles to me.
Anyone has ideas?
Thanks!
Click to expand...
Click to collapse
May be related to a ProxyController bug that people have reported. One workaround I've heard of (cannot confirm it works) is to turn off Airplane mode, reboot, then turn on Airplane mode,
ProxyController wakelock draining battery - Google Pixel Community
Thanks everyone!
Napa7m said:
I had the same problem, dropping 2-3% per hour over night. I turned 5G off, turned off 'mobile data always active' in developer settings and turned off adaptive connectivity.
Now im only losing .2-.5% per hour overnight.
Click to expand...
Click to collapse
I did all that. No deep doze tho. And even when I had deep doze when disabling the sim-card entirely, i had more than 1% drain per hour in standby. How tf do u get .2-.5%!? Do u have telegram/whatsapp/insta?
Lughnasadh said:
May be related to a ProxyController bug that people have reported. One workaround I've heard of (cannot confirm it works) is to turn off Airplane mode, reboot, then turn on Airplane mode,
ProxyController wakelock draining battery - Google Pixel Community
Click to expand...
Click to collapse
I see no proxy handler wakelock in gsam so i dont assume its that. Already did that airplane mode reboot and it didnt work.
xflowy said:
Thanks everyone!
I did all that. No deep doze tho. And even when I had deep doze when disabling the sim-card entirely, i had more than 1% drain per hour in standby. How tf do u get .2-.5%!? Do u have telegram/whatsapp/insta?
I see no proxy handler wakelock in gsam so i dont assume its that. Already did that airplane mode reboot and it didnt work.
Click to expand...
Click to collapse
Just by doing what I said...
I was about to send the phone back until I discoveredt this fix. Battery life is great now.
I don't use any of those apps.
xflowy said:
As stated above, it is a doze state that is being entered after the light doze. Check Gsam battery for your stats regarding deep doze.
Click to expand...
Click to collapse
Sounds like a bunch of hooey to me. Light doze, deep doze, medium awake doze.. come on look at your cpu stats and deep sleep when screen is off. If it's not deep sleeping overnight at least 90% then something is keeping the phone awake and you need to find it. Get BBS and look at your alarms and partial wakelocks. You have a runaway program that is constantly waking up your device. Mine was Mi Fit and I tweaked it so it's not awake all night long. Went from 1.8% / hour to 0.4% - 0.7% consistently.
@Napa7m Insta and WhatsApp shouldn't be doing it. Not sure about Telegram but I do recall some issues a year ago and I deleted it from the phone.
bobby janow said:
Sounds like a bunch of hooey to me. Light doze, deep doze, medium awake doze.. come on look at your cpu stats and deep sleep when screen is off. If it's not deep sleeping overnight at least 90% then something is keeping the phone awake and you need to find it. Get BBS and look at your alarms and partial wakelocks. You have a runaway program that is constantly waking up your device. Mine was Mi Fit and I tweaked it so it's not awake all night long. Went from 1.8% / hour to 0.4% - 0.7% consistently.
@Napa7m Insta and WhatsApp shouldn't be doing it. Not sure about Telegram but I do recall some issues a year ago and I deleted it from the phone.
Click to expand...
Click to collapse
you should do some reading
xflowy said:
Thanks everyone!
I did all that. No deep doze tho. And even when I had deep doze when disabling the sim-card entirely, i had more than 1% drain per hour in standby. How tf do u get .2-.5%!? Do u have telegram/whatsapp/insta?
I see no proxy handler wakelock in gsam so i dont assume its that. Already did that airplane mode reboot and it didnt work.
Click to expand...
Click to collapse
Either something is using up power when device should be deep sleeping, or it's just defective.
So he's right, monitor app usage and go from there. The built-in battery stats work well enough. It's how I discovered that 'mobile network standby' was consuming 20-30% over night with nothing going on.
DOn't forget to expand the 'system usage' at the very bottom of 'battery usage'.
xflowy said:
you should do some reading
Click to expand...
Click to collapse
I did and it still sounds like you're looking in the wrong place for your awake status. It's a background process that can't really be tweaked or modified on it's own. But alarms and wakelocks can that's why I said look there first. If your phone is not deep sleeping err.. deep dozing then something is keeping it awake. Find it and you're home free. What kind of deep sleep are you getting overnight?
xflowy said:
As stated above, it is a doze state that is being entered after the light doze. Check Gsam battery for your stats regarding deep doze.
Click to expand...
Click to collapse
Deep sleep = deep doze? My wifi is on and have 4G enabled. This as taken about a month ago but nothing has changed.
Napa7m said:
I had the same problem, dropping 2-3% per hour over night. I turned 5G off, turned off 'mobile data always active' in developer settings and turned off adaptive connectivity.
Now im only losing .2-.5% per hour overnight.
Click to expand...
Click to collapse
I have about the same as you, mobile network standby around 20-25% overnight. I don't turn off 5G but I am connected to wireless with a very good signal. I have mobile data always active enabled as well as adaptive connectivity enabled. What I did to was turn off every adaptive setting in battery settings. Perhaps it's the wifi I'm connected to but I'm getting average 0.5-0.6% drain overnight. Deep sleep around 92 %. As I said, I did see some partial wakelocks and alarms when I was almost 2% / hour and either deleted the apps or figured out how to stop/slow them when not in use.
@bobby janow ok my man. first of all. a read for you, what deep/light doze is: https://www.andreasschrade.com/android-battery-optimisations
and no, its not the same as deep sleep. deep sleep is the cpu frequency.
my phone is now (out of a sudden) going into deep doze overnight, so that seems fine. also wakelocks couldnt have prevented my phone from going into deep doze, cause then, it would have also not gone into deep doze when I had my cd-card disabled (since there should be still wakelocks, when my phone is connected to wifi and all, right
since mobile standby is concerningly huge in the battery stats i assume its the usual culprit, but disabling adaptive connectivity, 5g and enabling that dev option does not help.
tho i am willing to find some wakelocks (since they seem to affect the device also a bit in terms of my standby drain). according to gsam everything is fine in that department, cant really find unusual wakelocks. does bbs show more there? im not very keen in running an adb to make it work...what does that command line do exactly?
thanks!!
@xflowy BBS needs 4 adb commands and it takes about 30 seconds to complete with a copy and paste from his thread. It has two wakelocks stats, kernel and partial. The kernel ones are meaningless to me but the partial tell a lot, you'll see. Also just as important is the alarms stat. It gives you that amount of time an app is firing i.e. wakeups. Check it out see if it helps you. Thanks for the read, but it's beer day today and that looks like it will take all my concentration. Lol.
@xflowy On first read it looks like battery optimization regulates doze mode, right? I mean that's really the only way?
It also happened to me after many tests I have managed to solve it, deactivating the sim card and esim, and restart, then activate the sims and drain solved, it already goes into deep sleep.
I have the exact same issue. I thought I'm the only one. But I'm unable to resolve with this by disabling sim n reboot method. Can anyone suggest if it's hardware fault ?