I need help with the kernel auditor to get better battery life, i have installed last cm nighties nad last NJ2 band, i read that if u change the kernel you can get better battery stats, the battery drop really fast, with low brightness and wi-fi off, just LTE data, without GPS. I use the app called "Root Booster" and the Calibrate Battery but it's the same. I need help with the kernels.
Sorry for the bad english, is not my native lenguage
B
My goto settings on this phone were interactive governor with the following tunables tweaked:
hispeed_freq = 918000
min_sample_time = 50000
timer_rate = 30000
Row I/O scheduler with 1024 kb read ahead.
Good battery life and not awful performance.
However, tweaking the kernel is unlikely to get you a miraculous change in battery life. Chances are if you're battery is draining super fast you have some rogue app or process keeping your phone from getting into deep sleep. You can troubleshoot that with better battery stats.
jason2678 said:
My goto settings on this phone were interactive governor with the following tunables tweaked:
hispeed_freq = 918000
min_sample_time = 50000
timer_rate = 30000
Row I/O scheduler with 1024 kb read ahead.
Good battery life and not awful performance.
However, tweaking the kernel is unlikely to get you a miraculous change in battery life. Chances are if you're battery is draining super fast you have some rogue app or process keeping your phone from getting into deep sleep. You can troubleshoot that with better battery stats.
Click to expand...
Click to collapse
Explain me more about "gettin into deep sleep"
Your phone's CPUs will scale up and down under load, but they will always run at some minimum frequency even under low load if they are "awake". I think it was around 300 MHz minimum on the i747.
In deep sleep the CPU powers off entirely, and your phone goes into a very low power draw mode. It is still listening for calls, texts, etc., but drawing much less power than if it was awake.
Your phone should be trying to get into deep sleep any time the screen is off, but wakelocks can prevent it. Not all wakelocks are bad. You don't want your phone switching into deep sleep if you're playing music or downloading files with the screen off; however, some wakelocks are unnecessary. Low priority apps syncing excessively or some app or process going rogue and holding a wakelock when it serves no purpose are not entirely uncommon. The kernel holds wakelocks and therefore sometimes catches the blame, but rarely is the kernel actually the culprit for excessive wakelocks. The kernel is typically just doing what the higher level software like the android system or apps are telling it to do.
One good indication the i747 was suffering from wakelocks was if it felt warm to the touch even after sitting with the screen off for an hour or two. This phone always heated some during use, but it should be room temp / cool to the touch after a long time idle. Since lollipop I don't find android's battery menu in settings to be all that useful. The better battery stats app I linked to in the post above is a great tool for investigating wakelocks. It will let you know what % of the time your phone is in deep sleep, and what is keeping it awake; a much more analytical approach than the "is it warm when it should be cool" method.
jason2678 said:
Your phone's CPUs will scale up and down under load, but they will always run at some minimum frequency even under low load if they are "awake". I think it was around 300 MHz minimum on the i747.
In deep sleep the CPU powers off entirely, and your phone goes into a very low power draw mode. It is still listening for calls, texts, etc., but drawing much less power than if it was awake.
Your phone should be trying to get into deep sleep any time the screen is off, but wakelocks can prevent it. Not all wakelocks are bad. You don't want your phone switching into deep sleep if you're playing music or downloading files with the screen off; however, some wakelocks are unnecessary. Low priority apps syncing excessively or some app or process going rogue and holding a wakelock when it serves no purpose are not entirely uncommon. The kernel holds wakelocks and therefore sometimes catches the blame, but rarely is the kernel actually the culprit for excessive wakelocks. The kernel is typically just doing what the higher level software like the android system or apps are telling it to do.
One good indication the i747 was suffering from wakelocks was if it felt warm to the touch even after sitting with the screen off for an hour or two. This phone always heated some during use, but it should be room temp / cool to the touch after a long time idle. Since lollipop I don't find android's battery menu in settings to be all that useful. The better battery stats app I linked to in the post above is a great tool for investigating wakelocks. It will let you know what % of the time your phone is in deep sleep, and what is keeping it awake; a much more analytical approach than the "is it warm when it should be cool" method.
Click to expand...
Click to collapse
Perfect answer, that give me a lot of info i dont know about it, thanks a lot dude i will use the app and check what is the problem here!
Related
Ok. So I have a G2, with CM7R4. I have SetCPU with all sorts of profiles and JuiceDefender on Extreme. I still can't get more than 6-7 hours out of my battery. I take it off the charger before I leave for work, and before I even clock out, the phone is dead. This is whith even minimal usage. The thing is, with minimal and heavy use, I get about the same battery life. What could possibly be causing this?
I went in to Battery Stats, and Cell Standby was at 60% or more, but my browser (which I've been using for 3 or so hours, and a game I've been playing for about the same, are both only at 2%. I went in to Spare Parts, and it showed the phone has been running constantly for about 3 hours with no sleep, even though I've shut the screen off and stopped using it completely numerous times in the last 3 hours.
There has got to be something I can do. How are people getting 2 days uptime when I can't even get 8 hours? Someone help please!
Edit: Thank you everyone for your suggestions! I drained my battery, wiped battery stats, removed a bunch of SetCPU profiles, and installed Green Power to regulate my data usage. I've seen no decline in functionality, but I have already begun to see a vast battery life improvement.
Stop using setcpu.
Sent from my G2 running Cyanogenmod 7.
Do you have a reason for this? I was told to start using SetCPU the last time I brought this issue up.
What are you setCPU profiles?
Oh yeah, if you made your profiles all whack, the cpu will be constantly running. Specifically if you've set a performance governor anywhere. The more you mess with the profile creator, the more battery life you can free up easiest way to learn is to play around with the governors from time to time.
Sent from my HTC Vision using XDA Premium App
Kevin001111 said:
What are you setCPU profiles?
Click to expand...
Click to collapse
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
detox702 said:
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
Click to expand...
Click to collapse
Why are you charging your phone at 1516 max? Your max for charging should be 806 (stock clock), to prevent excessive heat.
Have you tried wiping battery stats in ClockworkMod recovery?
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
SnowOokami said:
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
Click to expand...
Click to collapse
is it really necessary to let the battery drain in order to wipe the battery stats? I'm thinking about trying this myself, but there's some debate on whether or not the battery should be drained or not in other threads.
Sent from my HTC Vision using XDA Premium App
ohshootrawr said:
is it really necessary to let the battery drain in order to wipe the battery stats? I'm thinking about trying this myself, but there's some debate on whether or not the battery should be drained or not in other threads.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
True it's not "healthy" to drain a li-on battery, but it's not 100% drained and I've been without power several times because I forgot to turn it off before I got home to charge it
Also in my opinion a 1-time total drain doesn't damage the battery. Just let your navigation on till it's empty (leave the screen on too) it will go off, you will be able to boot the phone once or twice after that, so it's not a 100% drain, boot in recovery mode then delete the battery stats, reboot and put the charger in it. That did the trick for me. Hopefully it works for you too
I guess you could do it the other way around, charge the phone completely, wipe the battery stats, drain it till it goes off and reboot. That takes a bit longer I guess.
You said it was the "phone" using most of your battery? I know there was or is a setting in cm "flip to ignore" that when enabled it kept the phone awake. Worth a shot...
Why are you charging your phone at 1516 max? Your max for charging should be 806 (stock clock), to prevent excessive heat.
Click to expand...
Click to collapse
That's why I have the temp. profile. I basically have to have my phone in a charger at all times, otherwise it dies. So I have it set to run at max so my games and whatnot work well.
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
Click to expand...
Click to collapse
Thanks! I'll try this today, because my phone will undoubtedly die before I get home from work. I'd love to get 28hrs use. Last night, I got 7h30m30s on battery. That's good compared to what I usually get, but it left me without a phone during the deadest part of my shift.
You said it was the "phone" using most of your battery? I know there was or is a setting in cm "flip to ignore" that when enabled it kept the phone awake. Worth a shot...
Click to expand...
Click to collapse
Thanks! I'll look and see if this is causing it. I wouldn't've turned it on, but maybe it's on by default?
You need to recalibrate it by doing what that one post said, after using so many roms, your phone battery needs to be recalibrated
Since I've got the phone, I've only used CM, but I have used at least 5 different versions. I'm working on killing it right now. It'll be dead much earlier than usual with all the use its's getting, and I was smart enough to bring a charger so I can charge it as soon as it dies and gets recalibrated.
Let me know if it works for you!
detox702 said:
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
Click to expand...
Click to collapse
I had a setup similar to this (many different profiles) and I had awful battery drain. I read in a thread somewhere here that it was setcpu that was the culprit of the excessive drain because having many profiles has it constantly using cpu power.
I have since switched my default to 1017/245 on demand and now I only use a screen off profile at 245/245. Since making that change, my battery life improved significantly (25-30% improvement)
I don't do anything that requires the full 1.5ghz on my phone which is why I now run at 1ghz but definitely feel that the setcpu profiles cause some major drainage...
SnowOokami said:
True it's not "healthy" to drain a li-on battery, but it's not 100% drained and I've been without power several times because I forgot to turn it off before I got home to charge it
Also in my opinion a 1-time total drain doesn't damage the battery.
Click to expand...
Click to collapse
Its unlikely, but possible your battery will not take a charge after you discharge the battery too low (safety circuit does not properly kick in). I've seen this problem crop up (pretty occasionally) from time to time back on the Touch Pro 2 forums, and have seen it happen here to a couple people on the Vision as well.
The battery meter is not all that accurate, anyway. Most of what you suggest if fine: to delete battery stats, let it charge to full, but then drain to 10% or so. You aren't really gaining much by doing that versus totally empty, and its safer.
TrueYears said:
You need to recalibrate it by doing what that one post said, after using so many roms, your phone battery needs to be recalibrated
Click to expand...
Click to collapse
There is no such thing as calibrating a Li-ion battery. You are calibrating the battery meter on the phone.
I have been rooting for years but I never bothered to really mess with kernel settings to increase battery life. All I'd do is over clock or under clock. What do you guys do to increase battery life? Like for example, lower voltages? I have no clue exactly how this works. I'm kind of tired of carrying 2 spare batteries around lol I'm on Franco's kernel with the hot plug enabled from his app but I might switch to imo's. Anyone wanna be kind enough to help me out please?
I just got a 200mah battery and its animal.
Before I used APEX kernel and took the usual steps, dimmed the screen etc.
Thank you for the response. I'm sorry, I should have stated that I'm on the CDMA version lol
I've been considering a custom rom/kernel and reading up on them a bit. I'm pretty much a n00b, so maybe this is nothing new to you, but it seems that controlling kernel wakelocks and specialized cpu governor settings + undervolting are the main things that increase battery life. I think minimizing unnecessary wakelocks seems to be the main key.
For the most part, battery drain comes down to two issues:
1. Screen use (not much we can do here)
2. Radio use (which tends to wake up the phone unnecessarily, I think)
I think the radios -gps/voice/3g/4g - is what causes unnecessary wakelocks on stock rom/kernel - as I get virtually no, nada, zip, zilch, zero sleeping drain in airplane mode.
If your battery drains 1%+ an hour just sleeping, it can add up significantly. Even when things are turned off, they still sometimes cause wakelocks. Take NFC for example, I just read in a forum post that it was causing wakelocks even when turned off.
Question
Do you guys think since in AMOLED displays the black color is essentially the pixels being turned off, having a black wallpaper uses less battery? because each time I check my battery usage I see that my display is always on top, and I have this theory can anyone confirm it or correct me if I'm wrong?
I've been fooling around with undervolting.
When setting them -25mV nothing much seems to happen, no gain or loss. But when I set them -50mV or lower, I get a massive battery drain.
Is this a normal problem?
I don't crash or anything, the battery just doesn't last.
The very act of undervolting should be saving you battery, because undervolting makes it so that you use less energy at each clock speed.
Masters2150 said:
I've been fooling around with undervolting.
When setting them -25mV nothing much seems to happen, no gain or loss. But when I set them -50mV or lower, I get a massive battery drain.
Is this a normal problem?
I don't crash or anything, the battery just doesn't last.
Click to expand...
Click to collapse
It can, if services start crashing in the background and it voids deep sleep mode. You'd better just leave it default or try to nip off v's in the maximum freq department.
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
hshaikh said:
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
Click to expand...
Click to collapse
I suggest to decrease your max CPU until you feel it affects performance too much. You can also try switching to a governor less aggressive than interactive (try ondemand).
Don't expect magic though. I've played with decreasing max CPU clock, max CPU screen off, governor settings etc with three different kernels. Gathered stats for at least one week each time. Never noticed a difference large enough to actually matter to me. For maximizing battery life, you can gain more by hunting apps that cause a lot of (partial) wakelocks and alarms, and use low screen brightness.
hshaikh said:
and screen off max is 384.
with all that information, what do you suggest?
Click to expand...
Click to collapse
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Darunion said:
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Click to expand...
Click to collapse
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Petrovski80 said:
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Click to expand...
Click to collapse
you are correct. there is a magic middle ground because power consumption doesnt scale in a linear way. but finding that spot would take massive testing and even getting to the center, would still probably only gain about 10-15mins average use on a battery charge :/
bk201doesntexist said:
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
Click to expand...
Click to collapse
what speed show i set to max when screen is off.
did you read anything that Darunion and Petrovski80 wrote? I keep mine at it's max, i don't care, i don't live in the woods with no electricity.
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
hshaikh said:
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
Click to expand...
Click to collapse
Exactly. I get similar performance.
Sent from my Galaxy Nexus using Tapatalk 2
Hello there,
I found a solution to the wake up lag, I tried everything before but nothing did the work. Its an app called wakelock, so far so good, batter drain is not that big, about 8% in 8 hours idle, I can live with that. I'm worried if there's a side effect to this? being the cpu constantly on, will this shorten its lifetime? Thanks.
Going from the name of the app and a quick peek, what it does is use a wakelock(!) to prevent the phone going to deep sleep. My guess is it will shorten battery life by around 20%, but I can't see how it should do any damage to the cpu.
Sent from my GT-N7100 using Tapatalk 2
It's not an amazing solution tbh, as it's keeping your CPU awake all the time. If the CPU doesn't enter deep sleep, there is no wake-up lag.
I don't imagine you'd immediately notice any major issues with it, but longer term nobody can really say - I don't think you will have a problem in a normal period of usage of the CPU such as a year or two. But at the end of the day, any time you change things like this, there's a risk, regardless of how small.