I have been having issues with cm10.1 "android OS" using too much battery. And i have seemed to squash out the bugs. nearly doubling screen time. (in the sense that by bed time i had about 4 hours screen time and 10% battery left and now can hit 8 hours in a day)
I am going to slowly try different things to see where hte main issues were. but here are the majority of the changes i made.
1. Wifi, this should be off during the day, simple but true. Also i noticed build.prop had wifi scan interval set to 15 instead of the recommended 120
2. Auto rotate screen, i have read this has bugs in some builds (not sure on ours) it should be disabled unless you absolutely need it, you can add a quick tile for quick toggling. (I honestly think this is the biggest cuplrit)
3. Dev options, try to have all unneeded dev options off. I had strict mode enabled, not sure if it made a difference, but its useless cpu cycles.
4. Battery apps, as helpful as they are, uninstall asap, unless you are isolating a problem they eat cpu cycles trying to figure out what is eating your cpu cycles...
5. Notification Light, its not the LED so much as it is the CPU cycles required for the timing of the led light.
6. sign out of or uninstall/freeze (disable) google talk.
7. disable gps (use quick toggle for when really needed)
8. go to system settings -> google (under accounts) -> maps & lattitude -> make sure "report from this device" is unchecked and if you dont move around a lot (aka you work really close to home) turn location reporting to either do not update, or set location...
9. and of course any other common place one, screen brightness etc...
I will slowly implement these back in to see if they cause the drain to come back.
I think its auto rotation honestly, but it could have been a combination of all of them.
I get 8-9 hours on stock 4.1.2
I get 6 hours screen time in 4.2.2 without doing any of that, and I still think that's pretty bad compared to touchwiz. I use all those functions mentioned (except gtalk) all the time, so cm10.1 is nowhere near usable as a daily driver for me.
So battery is not draining on its own anymore.
Now time to find the culprit.
If its autorotation then the cm team can fix it and that's a good thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GN2 using XDA app.
simonxliu said:
I get 6 hours screen time in 4.2.2 without doing any of that, and I still think that's pretty bad compared to touchwiz. I use all those functions mentioned (except gtalk) all the time, so cm10.1 is nowhere near usable as a daily driver for me.
Click to expand...
Click to collapse
I'm not saying cm10.1 is the culprit. I'm trying to figure out what is and so I can help squash it.
Sent from my GN2 using XDA app.
I get 8-9 hours on stock 4.1.2
I use Deviant's Xone rom. Get 2 days+ of use depending on how I use my phone. Even with heavy use I get a good day out of it, at least for what I need.
Related
While I own an international unlocked version of the S2, i assume the Sprint version must be very similar. After countless hours of trying to figure it out, this is what i discovered and solved my battery draining issue (it's been two months with no problems at all) i get 4 to 5 hrs display time and it lasts me all day. I was on stock 2.3.3 and recently upgraded to 2.3.4. with same results. The following tips are things i did prior to rooting, and they solved my battery drain issue.
1. Anything that tracks location is a battery drainer and i discovered that i was using wireless networks for location (it's also not that accurate) and it was the biggest culprit, so i disabled it and now i use gps (more accurate) as needed and turn it off when done. If you use Google maps with google latitude enabled, sign out of latitude when done using it.
2. App killers use more battery than saving it by closing apps and processes that run in backgroung that will automatically open right back again. Stay away from them.
3. Some apps if left in memory will constantly cause cpu spikes (suspend and events/0), in my case it was Facebook and Xfinity apps. So i close all active apps in task manager. Don't really clear ram, just close active apps.
4. Use Watchdog from Market to track any apps that might be using a lot of cpu.
5.Enabling Back up my data also drained my battery, so i disable it.
Hopes this helps...
AqueousBor said:
1. Anything that tracks location is a battery drainer and i discovered that i was using wireless networks for location (it's also not that accurate) and it was the biggest culprit, so i disabled it and now i use gps (more accurate) as needed and turn it off when done.
Click to expand...
Click to collapse
While I can't state for certain that it's causing any extra battery drain, Carrier IQ is hooking into the location service, and every time your location changes, grokking your latitude, longitude, accuracy, and a timestamp. This is new to the Epic Touch.
I constantly have alerts for suspend and event/0 in watchdog. In the stock task manager there really isnt much running to kill. It's driving me nuts. haha My battery life isnt horrible but I think it could be better..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried Andromadus, Desire s port and ICS for desire z. Although the battery is better with each release, it still drain really fast.
When I say drain I mean in use. Not really noticed typical 'battery drain' from background services etc.
My DD has been various versions of Miui or CM7 for a few months and the battery is great.
Loads of people are saying that battery is good on ICS but I just don't see it.
Am I doing something wrong?
Well let's start knocking stuff off a list...
For each of these, think about what it's like on ICS compared to MIUI or CM7:
Brightness setting
Screen time on
Music time
WiFi time
3G time
Browsing/syncing time
Different apps running in background (how many do you kill if any on either?)
Any apps replacing stock ones? (messaging mainly)
Number of messages
Sound/vibrate on or off
Think about if these are equal for both. I've noticed mainly and largely that my battery drain from having 3G turned on is SIGNIFICANTLY lower than on MIUI, just an example.
noneabove said:
Brightness setting
Screen time on
Music time
WiFi time
3G time
Browsing/syncing time
Different apps running in background (how many do you kill if any on either?)
Any apps replacing stock ones? (messaging mainly)
Number of messages
Sound/vibrate on or off
Click to expand...
Click to collapse
Brightness set to auto on both.
Screen set to 1 minute auto off on both. Running time is just general use (as a heavy user).
Haven't used music for a little while.
So far most of my testing was on wifi so that and 3G were left alone.
As for usage and apps. I use stock apps on both. And any apps that I added were added on both.
Vibrate/sound were mostly the same on both with haptics turned on but selection sounds off.
As far as I can tell, without testing again to get the battery stats, my usage was standard for me but ICS uses battery like a machine. Oh and no app killing.
Sent from my HTC Desire Z using xda premium
My observations are the same as yours no builds of ICS gave me more battery life than MIUI and CM roms.
I wasn't getting great battery life on ICS either until this morning when I flashed Virtuous Quattro. I'd say it's just as good as what I was getting on GB.
'Good' to see others are getting similar results.
I'll keep an eye on updates as they are bound to improve just as GB roms have.
Sent from my HTC Desire Z using xda premium
with andromadus im back at a days batterylife, with ILWT cm7 i get about 27 hours use, 7 hours is of course when im sleeping, but i get 8 hours of music with some pauses for games.
here you can see where im playing games, and when im just listening to music
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine hasn't been too bad. This was with AndroICS. Took it off the charger Christmas morning around 7-730am. Was out and about all day with some moderate use (ya know, to keep my sane around the family), wifi on probably half the time.
Then again I don't know how well battery stats are tracked in that ROM.
I'm running AOKP 20 and Franco kernel but seem to be getting really bad battery life. I see folks claiming 1% battery loss over 8-9 hours of sleep. Mine loses 12-15% while I sleep and that is with WIFI on.
I'm not real familiar with the Better Battery Stats or Battery Monitor Widget. Can I use one of those to find out what is killing my battery life?
Does anyone know of something that might be causing this or how I can find out what it is?
Rogue app? Wich Franco are you using?
Sent from my Galaxy Nexus using xda premium
I tried 14.4 but went back to 13.1 hoping things would improve. Same on both.
Better Battery Stats' ugly interface really does mask what I feel is a great app. In your case, assuming you have it installed, change the top box in the app to Kernel Wakelocks and Partial Wakelocks and see what is preventing your phone from sleeping (post the screenshots of the two pages if they mean nothing to you).
I've also found CPU Spy to be an easier to understand quick overview of what's going on with my device. It'll list out the various clock speeds my kernel has and how much time was spent in each. If you notice "deep sleep" isn't the biggest bar, you likely have something going on.
Juvenall said:
I've also found CPU Spy to be an easier to understand quick overview of what's going on with my device. It'll list out the various clock speeds my kernel has and how much time was spent in each. If you notice "deep sleep" isn't the biggest bar, you likely have something going on.
Click to expand...
Click to collapse
Yup, yup. I was going to suggest CPUSpy, it's a decent little app. My phone will spend ~60-70% of the time in deep sleep over a nine hour or so period with WiFi on.
It looks like my phone is going into deep sleep and then something is waking it up and it can't go back. These processes don't mean much to me...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The audio out wake lock is caused by keyboard sounds, touch sounds and screen lock/unlock sounds. Turn those off.
The other wakelock seems to be your gallery syncing constantly.
Sent from my Galaxy Nexus using xda premium
Touch sounds were on, I turned those off. Why would those be waking my phone up in the middle of the night though?
How do I keep my gallery from syncing constantly? The only setting I see in the gallery options is to turn off my google account sync which I assume would turn off my gmail and other things as well?
Never mind, I found where to turn off photo sync.
Is it normal for touch sounds and gallery updates to keep your phone awake all the time? If so, what is the point of having them if they are going to eat your battery...
what franco are you using?
13.1
10 chars
Here is a screen of my overnight usage. I don't know why but I've just noticed the clock has gotten stuck. Stupid thing.
*Edit* I have a few things syncing over night, and the LED was literally flashing for the entire time, I didn't check my e-mails on purpose to see what nine and a half hours battery drain would do when that bright little LED was flashing all night, not bad I reckon!
recomand Apex rom
from bigxie
http://forum.xda-developers.com/showthread.php?t=1399238
15% after 63 hours, UV and OC
As you can see my phone Charges pretty fast. It Charges 0 to 100 in one hour. But charge Drains fast also like 4 and half hour screen time. Im on MIUI 13 global.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Koriam said:
As you can see my phone Charges pretty fast. It Charges 0 to 100 in one hour. But charge Drains fast also like 4 and half hour screen time. Im on MIUI 13 global.View attachment 5579973
Click to expand...
Click to collapse
That's stock MIUI, right? It's possible you have some background stuff going on that drains the battery on a regular basis. If you haven't already, try clearing your Recents view to see if that helps.
I am using Arrow OS 12.0, myself, and ended up enabling the Developer Options selection for 'kills all activities once user leaves them'. This improved my active consumption rate from being ~8-9% per hour to ~6% per hour. You can give it a try, too!
Veiranx said:
That's stock MIUI, right? It's possible you have some background stuff going on that drains the battery on a regular basis. If you haven't already, try clearing your Recents view to see if that helps.
I am using Arrow OS 12.0, myself, and ended up enabling the Developer Options selection for 'kills all activities once user leaves them'. This improved my active consumption rate from being ~8-9% per hour to ~6% per hour. You can give it a try, too!
Click to expand...
Click to collapse
Yes its stock. I couldnt find any app yet, im Still searching and looking for a help.
Oh, maybe you have the same issue that I had.
Check if the MIUI gallery is going crazy in the background. I have yet to figure out what caused that, but it wrecked havoc on my device.
Get something to view your CPU frequency in real time, normally all cores should idle at under 1000MHz with nothing else open in the background (I used CPU Float to check that).
If your little and/or middle cores appear to be clocked high, try to see if force closing the gallery and not reopening it helps. I fixed it for good only after having disabled its storage permission, ended up switching to google photos instead.
Hope this helps.
Dariusdd said:
Oh, maybe you have the same issue that I had.
Check if the MIUI gallery is going crazy in the background. I have yet to figure out what caused that, but it wrecked havoc on my device.
Get something to view your CPU frequency in real time, normally all cores should idle at under 1000MHz with nothing else open in the background (I used CPU Float to check that).
If your little and/or middle cores appear to be clocked high, try to see if force closing the gallery and not reopening it helps. I fixed it for good only after having disabled its storage permission, ended up switching to google photos instead.
Hope this helps.
Click to expand...
Click to collapse
It looks like this and going crazy up and down all the time. I force stopped gallery and remove the permission but its Still the same.
Good afternoon!
I have a question about AOSP based ROM's. At first I thought this was only occurring in the Nameless ROM but I can also find this behavior on other custom ROM's. It seems that apps are getting closed automatically after some time, as if I would go to the 'Recents' screen (or however this screen is called) and I would swipe those apps away.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is definitely noticeable when I wake up in the morning, almost all my apps are gone from Recents while I almost never swipe any apps away. I find this behavior not efficient since my phone never makes use of the 12GB RAM which I've spend extra money on. Here you can see that only 7 GB is actually used (including cached processes).
When I open up all my apps at once my RAM usage goes up but after some time it seems to close apps and it goes back to 5-6 GB of usage or so.
I find this frustrating. I have an iPhone 12 from work and I use that phone rarely. But a week later I can expect my app to still be open where I left it.
In the ROM's I tried, I tried disabling any battery savers if there were any, without result. I also have FKM installed and tried changing some memory related kernel settings which did appear to have some effect but that also might be a placebo and tbh I'm not fully aware what kernel settings I should apply.
TLDR: Can anyone advice me how I can stop my AOSP rom from clearing apps in the background?
Thanks for your input
Kind regards,
GolovaRaoul
Hi,
I have not tried any custom ROM yet, but I can confirm that default ROMs for "OnePlus, Xiaomi, Samsung" are all doing the same behavior once the phone is setting down and not being used for a while "sleep mode" this actually good in my opinion, it will automatically close all apps except the apps you are choosing to not to be closed "locked apps" in oxygen os, you can select multiple apps to prevent them from being closed during night or even when you tap "close all" button.
So, I think this is an Android optimization to save battery during night not only in AOSP ROMs.
Thanks for your response
Well I don't like this behavior personally. It takes time and processing power to re-open apps and navigate them back to the stage where I had them before. I need to relaunch Spotify 5 times per day which is annoying and I really shouldn't need to on a flagship smartphone with 12 GB of RAM.
GolovaRaoul said:
Thanks for your response
Well I don't like this behavior personally. It takes time and processing power to re-open apps and navigate them back to the stage where I had them before. I need to relaunch Spotify 5 times per day which is annoying and I really shouldn't need to on a flagship smartphone with 12 GB of RAM.
Click to expand...
Click to collapse
This actually not belong to RAM capacity itself, it is system implementations and how should apps behave. As I said it will only close the apps during "sleep period" and you can select multiple apps that you want them run in background all the time see attached photos.
You are welcome
dream2poet said:
This actually not belong to RAM capacity itself, it is system implementations and how should apps behave. As I said it will only close the apps during "sleep period" and you can select multiple apps that you want them run in background all the time see attached photos.
You are welcome
Click to expand...
Click to collapse
Yeah you could be right about the behavior. I still want to change it tho. And by default, AOSP does not have something like 'memory locking' and this is a feature of Oyxgen OS.