Today I was sick and I decided the spend the day testing the phone. This configuration is great for battery life and stable
For cpu
1200000 1175
1100000 1125
1000000 1075
900000 1025
800000 975
700000 950
600000 950
500000 950
400000 900
300000 850
200000 825
100000 800
According to the tests I've done 86% of the time, cpu is below 600MHz state. Also I've decided to insert the 100mhz. It works great without any problems and we can save up a bunch of juice, near - 150mv.
Would recommend you guys leave the 500mhz till 800MHz as is. Or it'll freeze the phone.
Any thoughts? Wanna know your opinion.
The Gpu cannot be undervolted the limit is 1000mv for 200mhz and 267mhz.
160mhz I would love to test with 925mv
100MHz is 900mv
64mhz us 850mv
The only thing we can do to make sure it'll conserve battery is to raise the percentage before he raises frequency. I've decided to make near 85% to raise and 75% to decrease with 5 steps. Seems to be A OK.
Wanna know opinions. Phone is working great for hours with gaming etc. Please let me know your opinion
Sent from my GT-I9100 using Tapatalk 2
Related
Can anyone post their Voltage settings for Nemesis2all OTB OC kernal? Like posting ALL of them? Thankss.
You could skim through the thread starting at page 20 or so and look for lists of voltages and/or thumbnails.
I've been using this kernel recently. Here's my settings so far, although the overclocked settings have only been in place for a few hours, and I'm cautious about overvolting right now (this is my second fascinate ).
For reference, I had used comavolt before with no issues, but apparently barely (these settings aren't much of an improvement, other than overclocking of course).
I/O scheduler is set to cfq (sio gave me lockups in the market with comavolt settings). Enabled steps are 200, 400, 800, 1000, 1120, and 1200 MHz. I'm not bothering with 600 or 900 steps as I couldn't get any better voltage than with the 800 and 1000 steps. 1300 (and maybe even 1400) should be doable with overvolting, but doesn't stand a chance without it.
100-200 MHz: 850 mV
400 MHz: 975 mV
600-800 MHz: 1125 mV
900-1000 MHz: 1225 mV
1120 MHz: 1275 mV
1200 MHz: 1300 mV
I'm using the following 4 steps. You can swap in the last step for a 1500/~1400mV but I personally have yet to get that 1500 stable. At 1.4ghz I'm seeing 2000 in Quadrant, 20 mflops in Linpack. I'm also getting insanely efficient battery usage. Thank you Nemesis.
200 - 875mV
600 - 1150mV
1000 - 1250mV
1400 - 1350mV
*CFQ scheduler has kept 1400 crash free.
what are good setcpu settings? currently i have my main profile at 200-1000 ondemand, and i have 2 profiles: 200-200 conservative screen off, and 200-200 conservative temp>50c
as for the voltages i followed this
1600 MHz - 1425 mV
1400 MHz - 1250 mV
1200 MHz - 1150 mV
1000 MHz - 1050 mV
800 MHz - 950 mV
500 MHz - 850 mV
200 MHz - 800 mV
is there anything i should change for my profiles etc? my aim is to have the battery last as long as possible.
Not another thread for the same thing,
http://forum.xda-developers.com/showthread.php?t=1158102
Regards.
seems like you got a good CPU, cause mine cannot even set 200MHz voltage to 825mV
Kernel: Siyah Kernel v6 beta 4
Rom: Omega Rom v18
Highest Quadrant score: 5177 (Omega Rom v16.2)
Power Saving:
300 MHz - 400 MHz (both 925 mV)
powersave
Normal Use:
300 MHz - 1400 MHz (default voltages)
ondemand
Benchmarking:
1500 MHz (default voltage) - 1600 MHz (1600 mV or it your phone will crash)
lulzactiveq
WARNING:
Setting 1500 MHz to 1600 MHz may cause your phone to crash.
Do not tick "set on boot" option just to be safe.
You have been warned.
Hi guys,
I'm currently using Resurrection Remix v2.6.1 ICS and am experiencing battery drain whilst using the phone. (I think it's okay when in deep sleep).
It was installed on a full-wipe so I was expecting good battery life - but it's dying like crazy.
I have a feeling its my voltages.
These are my current settings in SetCPU (I haven't touched it since I installed RR 2.6.1 but I'm wondering if these settings stay from times where I have mucked around ages ago)
Governor: CONSERVATIVE
Schedule: CFQ
1600 MHz: 1350 mV
1500 MHZ: 1325 mV
1400 MHz: 1250 mV
1300 MHz: 1225 mV
1200 MHz: 1200 mV
1100 MHz: 1150 mV
1000 MHz: 1100 mV
900 MHz: 1000 mV
800 MHz: 1000 mV
700 MHz: 975 mV
600 MHz: 950 mV
500 MHz: 925 mV
400 MHz: 925 mV
300 MHz: 925 mV
200 MHz: 900 mV
100 MHz: 875 mV
50 Mhz: 850 mV
Do these look alright? What can I change them to?
I'm looking for best battery life...I don't need it to be super fast....as long as I can run everything fine which is not that much..I'm happy
thedunnyman said:
Hi guys,
I'm currently using Resurrection Remix v2.6.1 ICS and am experiencing battery drain whilst using the phone. (I think it's okay when in deep sleep).
It was installed on a full-wipe so I was expecting good battery life - but it's dying like crazy.
I have a feeling its my voltages.
These are my current settings in SetCPU (I haven't touched it since I installed RR 2.6.1 but I'm wondering if these settings stay from times where I have mucked around ages ago)
Governor: CONSERVATIVE
Schedule: CFQ
1600 MHz: 1350 mV
1500 MHZ: 1325 mV
1400 MHz: 1250 mV
1300 MHz: 1225 mV
1200 MHz: 1200 mV
1100 MHz: 1150 mV
1000 MHz: 1100 mV
900 MHz: 1000 mV
800 MHz: 1000 mV
700 MHz: 975 mV
600 MHz: 950 mV
500 MHz: 925 mV
400 MHz: 925 mV
300 MHz: 925 mV
200 MHz: 900 mV
100 MHz: 875 mV
50 Mhz: 850 mV
Do these look alright? What can I change them to?
I'm looking for best battery life...I don't need it to be super fast....as long as I can run everything fine which is not that much..I'm happy
Click to expand...
Click to collapse
Are you actually using 1.2GHz and up? And 50MHz ?
Why mate? I mean your voltages look good. I would suggest using 100 or 200 to 1000MHz. And maybe different I/O sched. and maybe a different cpu gov.
Cheers
Sent from my GT-I9100 using xda premium
Your voltages look good. Try underclocking, changing CPU gov/IO Scheduler
Sent from my GT-I9100 using xda app-developers app
okmijnlp said:
Your voltages look good. Try underclocking, changing CPU gov/IO Scheduler
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Cheers guys.
It was initially set to:
200-1200MHz
Governor: Pegasus
I/O Sch: CFQ
I've changed it to:
100-1200MHz
Governor: Lulz-something
I/O Sch: SIO
Looks good so far but maybe it's a placebo reaction - will let you guys know
May I ask how crap is your battery that you claimed? It may be perfectly normal depending on your usage pattern. For stock battery, it might last only 3 hours playing Nova3 or 2 days minimal use picking up calls or sms.
Adjust gov setting to fit your usage or demand, turn down the brightness, or underclock the cpu will give you some obvious result.
Voltages on the other side play an insignificant role.
ksilver89 said:
May I ask how crap is your battery that you claimed? It may be perfectly normal depending on your usage pattern. For stock battery, it might last only 3 hours playing Nova3 or 2 days minimal use picking up calls or sms.
Adjust gov setting to fit your usage or demand, turn down the brightness, or underclock the cpu will give you some obvious result.
Voltages on the other side play an insignificant role.
Click to expand...
Click to collapse
I don't think I do anything too much.
I mainly use it to check emails, Whatsapp, Facebook, Twitter.
Other than that it is just sitting there.
I have auto-sync on for Gmail, Enhanced Email - both on 'push' for email and calendars. Don't think that consumes too much battery though.
I forgot to mention that I also changed the under-clocking to -50 ... whatever that means
Install BetterBatteryStats and check for wakelocks, maybe some apps are preventing the cpu get into deep sleep. Alteratively download CPU spy from the play store to check deep sleep.
ksilver89 said:
Install BetterBatteryStats and check for wakelocks, maybe some apps are preventing the cpu get into deep sleep. Alteratively download CPU spy from the play store to check deep sleep.
Click to expand...
Click to collapse
Don't think I have a problem entering deep sleep.
It's just that my battery is draining too much.
e.g. normal morning....
100% when I wake up
95% when I leave house
70-75% after I use my phone for 40-50 mins for the whole time on the train
At that usage rate it should be considered normal, since you need to get mobile data running and you're constantly moving. (affect signal strength)
If you wish to go further, you have to exchange with cpu performance, or otherwise get a bigger battery.
Downclock the cpu to 800/1000Mhz,
lulzactive inc load set to 80%,
sampling up/down 30000/40000
pump up/down 1/1
hotplug min_freq 400Mhz
gpu set to 100/160/200
up down thres 75 45 80 45
stay count 0 1 1
The above settings will pull some handbrake on ur cpu, but you should probably gain 10-15% extra battery life.
The result will be obvious for lightweight task, but it's likely to see same drain on higher load.
I think we can post our own values of that kernel values, for finding a good measure for the best stability and less battery drain.
I think it's better to post only UV on stock frequencies; for making easier the comparison.
"Stable" means you have no reboots ever, you have to try for a long time and making an intense use of your CPU (there's an app called Stability Test, running it for 30 min is a very good measure of stability I think)
So, mine are:
300 - 830
600 - 900
800 - 1000
1000 - 1150
1200 - 1250
Mine are currently:
300 - 830
600 - 950
800 - 1050
1000 - 1100
1200 - 1200
I know there's more than a few people on these boards who enjoy adjusting their voltages to fit their specific devices, so it'd probably be a good idea to have a thread that shared that info. Yes, each device might differ, but having reference points are useful to save time and see potential limits. This could also help devs. figure out safe regions common to all SGPs (though they seem to be close enough atm)
I don't know how much the SGP Int'l and US differ w/r/t voltages and battery, but I'll go ahead and make the assumption that it doesn't.
Anyway, I've been testing these values with (scaling) Stability Test between 30 cycles of all freq., followed by two 15 cycles of highs alone and lows alone. with no crashes so far:
[SGP 5.0 US: Paranoid Android 2.57 on Mercurius kernel]
1520 @ 1300 mV
1320 @ 1250 mV
1096 @ 1175 mV
800 @ 1025 mV
400 @ 950 mV
200 @ 850 mV
I've lowered the voltages for the highs to 1275 mV, 1200 mV, and 1150 mV, but ran only 23 error-free cycles before battery got too low to continue.