I want to try a kernel compatible with CM9 on my i9020 with a slow refresh rate to test how many battery can be saved.
I see in bedalus kernel comparison that AniDroid Hardened is a 45fps one but seem a little out of date.
Any other kernel with 45-50fps refresh?
progitto said:
I want to try a kernel compatible with CM9 on my i9020 with a slow refresh rate to test how many battery can be saved.
I see in bedalus kernel comparison that AniDroid Hardened is a 45fps one but seem a little out of date.
Any other kernel with 45-50fps refresh?
Click to expand...
Click to collapse
That's funny. I was trying to get Anidroid 45fps to work with some of the new IMM76I ROMs this morning, but had no luck.
The best battery saving kernel is still matr1x, even with nominal voltages and 56fps.
I`ll take a test with the Matrix kernel.
Have you ever compared battery drain of two version of the same kernel with the only difference of display refresh?
I`m very curious to understand how much this parameter can be helpful in a battery saving setup
From bedalus battery drain thread
{
"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"
}
56 fps eat ~43mv , 65fps eat ~47mv
Thread link : http://forum.xda-developers.com/showthread.php?t=1478406
Sent from my Nexus S using Tapatalk 2
Yes, as you can see in the post above, and i recently tested 56 and 50 hz versions of trinity.
It definitely affects power!
Yes, I've just readed it on the battery drain thread. I have definitely to try this.
Related
I know there's already a battery life thread, but I thought it would be interesting to have one where people also included the amount of time their display was turned on for, since that seems to be the primary source of battery drain for me at least. Also if you wouldn't mind posting the average brightness it was set at, as well as any custom rom, kernel, or battery saving techniques you're using, that would be cool as well. And if you have a really long display on time, like over 5 hours, maybe you could include a screenshot fort verification too if it's not too much trouble. Thanks!
The most I've ever got is about 5 hours or so of display on time at around 25% brightness with sky ics 7.4, faux kernel 009m, -50 global uv, 1.5ghz CPU speed, and juice defender ultimate with 15 min sync interval. I can't find the screenshot for that one, but here's one that's almost as good:
{
"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"
}
Stock rom
Faux 009m kerna
JD ultimate
2hrs display time 10% brightness
Don't know why I seem to get so little compared to some of you
Sent from my SAMSUNG-SGH-I727 using XDA
Copied from the other battery thread
These are my specs.
-QuickWiz Rom
-009m Faux kernel ( 1.242ghz max - 384mhz min / -75mV )
Undervolted using Fauxclock (Y)
-Froze bunch of bloatware using Titanium backup
SkyCoke ROM
Faux 009u Kernel
-100mV UV, 1.188 gHz max clock
No JuiceDefender or anything else extra besides whatever came with the ROM
{
"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"
}
First of all, download an app called "Setxperia" , go to your cpu settings and set your governor to ondemand, and threshold to 40 (This gives responsiveness and speed comparable to higher end phones such as my galaxy s2). Second, download an app called "Deep sleep battery saver" , set the preset on any you want (I recommend strong) , set your screen on and off delay to 5 seconds. For battery discharge settings, set it to 10% , for recharge settings, press ignore. (Doing this compensates for power the low threshold uses) and there you go, done! Tested on my galaxy s2 first then sidekick 4g, methods work for both devices.
Sent from my SGH-T839 using Tapatalk 2
i just flashed a new rom and overall experience is the great
But...battery life is not that good now
going to try this today and iw ill inform you with the results
auda said:
i just flashed a new rom and overall experience is the great
But...battery life is not that good now
going to try this today and iw ill inform you with the results
Click to expand...
Click to collapse
Alright hope it works well for you
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
I only ever see a battery issue when I use wifi. But I might as well try this out.
Does anyone have any idea what these event wakelocks are? They are draining a lot of battery, and as you can see from the screenshots, my battery appears to be substantially worse than everyone else's. I'm not exactly a power user either!
I'd appreciate it if someone could help me out with this.
Here are some screenshots: https://plus.google.com/photos/+LewisLebentz/albums/6047049438489245601?sort=1
I have included pictures of the built in battery page, on screen time, awake time and a screenshot from WLD.
I have them too. But only recently. I'm on PA beta 2, AK stable Kernel 30.
As you can see Android os is eating away the battery.
{
"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 Paranoid ONE
I have them as well. No idea what they mean though. On Mahdi + Franco.
Trying out AK, getting them on here too. All kernel wakelocks
Guys, wakelocks are normal and needed. There are times when they are excessive though. I think bacon-599 has a better discussion on battery drain than worrying about a few minor wakelocks. 10 minutes in a few hours isn't that bad.
tiny4579 said:
Guys, wakelocks are normal and needed. There are times when they are excessive though. I think bacon-599 has a better discussion on battery drain than worrying about a few minor wakelocks. 10 minutes in a few hours isn't that bad.
Click to expand...
Click to collapse
Mine is excessive isn't it?
Sorry, what is bacon-599?
7ewis said:
Mine is excessive isn't it?
Sorry, what is bacon-599?
Click to expand...
Click to collapse
I don't think so. Not sure what the issue is.
Oh BACON-599 refers to issue 599 on cms issue tracker where bacon is the device specific project.
Issue tracker is at jira.cyanogenmod.org
Since I see so much Ignorant in the Battery thread, I like to point out (rant) some things..
1. A person 6 hour of Screen On Time usage is different from person to person.
2. Temperature can have a great affect on battery life.
3. Signal strength can have a great affect on battery life.
So with that in mind, I suggest everyone try to do a PC Mark bench, it is fair and give people a much better idea of what of what they should be getting. To do this test here are the few settings you need to set
1. BRIGHTNESS AT 23-25% (EYEBALL IT)
2. Wifi on
3. do not disable Mobile data or sync
4. Clear all RAM before start
below are the CONTROL numbers from a stock rom (pictures are from greenbot.com)
{
"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"
}
Below is my stat, using arter kernel and foreverloco rom. (I DO UNDERVOLT MY KERNEL)
Is this ok? Running skyhigh 2.1 and darthstalker v4 rom. A57 cores @ 2.4ghz and gpu @ 852mhz with a -75mv uv all accross the board.
I ll post my battery result as soon as i can, meanwhile here s my previous battery result i got a few days ago... http://forum.xda-developers.com/showthread.php?p=63851201
Here s my pcmark battery score too. I started it from 90% after already using the phone for a whole hour (sot of about 1h6mins)
ran pcmark again with skyhigh 2.3 ...running at 2.4ghz a57...
Hello,
Is my Geekbench score okay or something is wrong?
{
"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"
}
Quite under the expected range. Did you perform it at ambient temperature, or used a heavy-load app stressing the chip just before running the test?
I remember my first one gave similar results, I then ran an other one and it was more accurate to the chip advertised performances.
Jaxom84 said:
Quite under the expected range. Did you perform it at ambient temperature, or used a heavy-load app stressing the chip just before running the test?
I remember my first one gave similar results, I then ran an other one and it was more accurate to the chip advertised performances.
Click to expand...
Click to collapse
I tried to run it after a while and it performs much better now, I don't know what caused it, before first test I was using Chrome nothing much...
hiMLASTAR7 said:
I tried to run it after a while and it performs much better now, I don't know what caused it, before first test I was using Chrome nothing much...
Click to expand...
Click to collapse
When you look at your screenshot, it seems the CPU is also focusing on how energy is spent (energy_aware), which could also explain the first results. The device can understand how you use it and adapt the power usage depending on what you "teach" it. So nothing to worry about.
Also, the Android 13 Beta is showing some improvements for Exynos versions of the device, so expect it to run even better with time.
Here are my current results with the Android 13 Beta 1 on my Exynos 2200, so you can see the little improvement.
Android 13 one ui 5 beta exynos 2200