Database Users

SetCPU draining battery?

Anyone else have this problem. I usually am running at 1516 with cm. 6.1.1. So the other day for ****s and giggles I decided to disable set on boot and revert to 806 mhz (stock) and man what a difference. I got 26 hours of battery life. I've tested today with setcpu on running at 806 and tfhe battery life is way off. Somethings up.
[G2/HTC Vision]

Try the app cpu tuner, afaik, any speed above 1.2ghz is overvolted anyway which speeds battery usage. Cpu tuner has worked well for me as I think the verdict is still out to whether setcpu's screen off profiles actually work. That, and I personally don't see a difference in 1ghz vs 1.5ghz in daily activities, unless gaming
Sent from my HTC Vision using XDA App

Actually I use set cpu and I get about 36 hrs before I have to recharge. I'm oc @ 1.2 ghz and with moderate use. I guess it really does vary from phone to phone.
Sent from my CyanogenMod powered G2.

How are you guys getting such high battery lives? I was at 28% after 6.5 hours today... like wtf? And i didnt overclock or anything... I was using the phone with continuous data for about 90 minutes... other than that just texting...

Setcpu is the culprit. I would just like to know why it varys for every user. Maybe ill try reinstalling the app and see the outcome.
[G2/HTC Vision]

Yeah I get the same crap. I have CM7. Suppose to be good with battery power management. With Glacier I got 17 hours with set cpu profiles.
G2 its a joke. I got 9 hours luckily.
Now its 5 hours I got %39. Is it my phone or the battery?
Sent from my HTC Vision using XDA App

Hmm I beg to differ. I am running CM 6.1 and this is my battery life. BTW I only use SetCPU to OC to 1.3Ghz . No profiles
{
"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"
}
brzgw said:
Yeah I get the same crap. I have CM7. Suppose to be good with battery power management. With Glacier I got 17 hours with set cpu profiles.
G2 its a joke. I got 9 hours luckily.
Now its 5 hours I got %39. Is it my phone or the battery?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App

flak0 said:
Hmm I beg to differ. I am running CM 6.1 and this is my battery life. BTW I only use SetCPU to OC to 1.3Ghz . No profiles
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's very nice. I just disable the profiles and left it at 806 MHz. The battery drainage slowed down. So profiles really mess up. I have tried virtuous rom, with profiles I got pretty good for HTC sense. But I haven't gotten any close to yours.
With cm 6.1 I had %20 in 4 hours with normal usage.
Also is minimum and Max at 1.3 ghz?
Sent from my HTC Vision using XDA App

As long as mine lasts the day I'm Happy

My batterry life.
You can see I'm overclocked @ 1.2ghz as well.

Diffrent pic.
Last pic of my home screen was a bit blurry so i uploaded a new one. Now you can see the o.c speed a bit better.

Why would it vary from every user then? I do have profiles setup with ondemand as all my profile governors. I find it very weird how some people are getting good batt life with setcpu running and I'm getting amazing battery with it off. Ran it off for 20 hours so far and I'm at 45 percent.
[G2/HTC Vision]

Maybe some people haven't configured their profiles properly in SetCPU? I know I didn't. I have my phone OC at 1.2ghz and had profiles set for lots of different profiles including screen off at 245/245; i was only getting 14 hours top. However, I realised that the priorities that I had set the different profiles to were clashing. I discovered this when I only the screen off profile enabled with the rest of the profiles disabled and with moderate use (few phone calls via Bluetooth, 25-30mins, a few SMS msgs, very little data, wifi switched on, 2g+3G, not much browsing) I have got 52% after 17hrs 33mins)
Thats very good battery life for me!
Try having profiles enabled but with just the screen off profile activated. It worked wonders for me!

No maximum is 1.3 and min is 245mhz interactive governor
brzgw said:
That's very nice. I just disable the profiles and left it at 806 MHz. The battery drainage slowed down. So profiles really mess up. I have tried virtuous rom, with profiles I got pretty good for HTC sense. But I haven't gotten any close to yours.
With cm 6.1 I had %20 in 4 hours with normal usage.
Also is minimum and Max at 1.3 ghz?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App

Question why not a minimum of 245mhz. Btw the SetCpu widget is a battery drainer.
Utorrent76 said:
Last pic of my home screen was a bit blurry so i uploaded a new one. Now you can see the o.c speed a bit better.
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App

Utorrent76 said:
Last pic of my home screen was a bit blurry so i uploaded a new one. Now you can see the o.c speed a bit better.
Click to expand...
Click to collapse
Dude cancel that appt ... injection ahead!!
Sent from my T-Mobile G2 using XDA App

Can't.
zkid2010 said:
Dude cancel that appt ... injection ahead!!
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I kinda need it. It's a cortisone shot.

Recently I rooted by DZ and got CM7 installed.
Got SetCPU loaded.
I've seen a considerable battery 9hours and the batt is dead.
Governor: Interactive
Main: 1017/245
Screen off: 368/245
Temp: 806/245
Battery <10% 245/245
Charging 1017/245

fluxgfx said:
Recently I rooted by DZ and got CM7 installed.
Got SetCPU loaded.
I've seen a considerable battery 9hours and the batt is dead.
Governor: Interactive
Main: 1017/245
Screen off: 368/245
Temp: 806/245
Battery <10% 245/245
Charging 1017/245
Click to expand...
Click to collapse
The screen off profile does more harm than good and you do not need it if you are using either the smartass/interactive/scary governer considering they will already underclock when the screen is off, the switching of profiles regularly is a real killer. Beyond that, look into calibrating your battery as well the next time you fully charge the phone. The battery calibration app is also available on the market.

flak0 said:
Hmm I beg to differ. I am running CM 6.1 and this is my battery life. BTW I only use SetCPU to OC to 1.3Ghz . No profiles
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
It seems like you aren't even using your phone. Nothing else shows up but the 3 standards.
Sent from my T-Mobile G2 Coredroid unity-streamlined2

Undervolting SG2 thread!

So, i know alot of us SG2 user are always on the go with tweaking, OC/UC/OV/UC, all for better battery!
And i noticed there are no such threads about this, therefore i decided to start this one , so we could all share our experience and UV values for comparison.
I'm on CM7 stable? (2.3.7) with the following UV values set on boot for a couple of days now；
1200Mhz - 1175mV
1000Mhz - 1075mV
800Mhz - 975mV
500Mhz - 875mV
200Mhz - 625mV (yes! i know . tried 650mV and my screen washed out!)
like i said, i have been using this for a couple of days now, and everything seems fine; quadrant, Asphalt, golf, maps, everything.
So, what are your values.

everyones values will be diferent mate mine wont undervolt by much before it crashes , where as my old sgs2 could be undervolted loads
to be honest iam using speedmod kernel at the minute and there really isnt any need to undervolt or overclock
iam getting pretty much the same battery i did on my old sgs2 that could be undervolted loads like your one can
iam also getting great scores on benchmark programs

Yes, i know everyone's value will be different, i just think it would be interesting to see what people are doing with their beasts!
oh, and what happened to your old SG2?

What do I need to undervolt my SG2? Another different kernel?
I am on stock KI3 + CF-Root
Any recommended STABLE kernel?
Thank you

Thanks for the update

henrychukx said:
So, i know alot of us SG2 user are always on the go with tweaking, OC/UC/OV/UC, all for better battery!
And i noticed there are no such threads about this, therefore i decided to start this one , so we could all share our experience and UV values for comparison.
I'm on CM7 stable? (2.3.7) with the following UV values set on boot for a couple of days now；
1200Mhz - 1175mV
1000Mhz - 1075mV
800Mhz - 975mV
500Mhz - 875mV
200Mhz - 625mV (yes! i know . tried 650mV and my screen washed out!)
like i said, i have been using this for a couple of days now, and everything seems fine; quadrant, Asphalt, golf, maps, everything.
So, what are your values.
Click to expand...
Click to collapse
From what I've read on xda, you can't go 625.. that's why you can set 650 but can't do that for 625. It will jump to the minimum possible mV. Correct me if I'm wrong.

I don kno abt this uv thing worked the same on my sgs1 so iam not into uv on sgs2....kernel fixs tht prblm....but will try now an c wat the effect is...presently on siyah 2 kernel.....cheeerz

the minimum that i would undervolt at is at 800mv on 100mhz..anything under that would just freeze my phone...so to the OP you must have one damn beastly phone to be able to go that low..anyway i always manage to get 5hours screen on time with my settings so im happy..but please share how you manage to use it that low and not have any problems

I'm on CheckRom Revolution 1.0 and running RAGEmod U1-v1.1b.
These are my stable UV settings.
1200Mhz - 1150mV
1000Mhz - 1050mV
800Mhz - 950mV
500Mhz - 850mV
200Mhz - 825mV

gusoldier said:
From what I've read on xda, you can't go 625.. that's why you can set 650 but can't do that for 625. It will jump to the minimum possible mV. Correct me if I'm wrong.
Click to expand...
Click to collapse
i think each SG2's chip is different in some way.
for e.g, i can't set my 1200Mhz @ 1150mV, would be fine for a min or 2, then freeze. i think i also know some guy on XDA here who has 650mv or so.
what apps are you guys using ? setcpu or tegrak ?

yakyllan said:
What do I need to undervolt my SG2? Another different kernel?
I am on stock KI3 + CF-Root
Any recommended STABLE kernel?
Thank you
Click to expand...
Click to collapse
I don't think CF-root supports OC/UV. you need to flash a kernel that supports that! its amazing how much battery u can save....
i get about 68-75% left after using the for 14hours! wih about 2-3hrs of music, few calls, sms, mobile internet.
last night i forgot to plug in for recharge and i only lost 1% battery in 8hrs!
its awesome!

What kernel are you using for the UV?
Any recommended ?
(I don't want to lose my root)

{
"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"
}

henrychukx said:
So, i know alot of us SG2 user are always on the go with tweaking, OC/UC/OV/UC, all for better battery!
And i noticed there are no such threads about this, therefore i decided to start this one , so we could all share our experience and UV values for comparison.
I'm on CM7 stable? (2.3.7) with the following UV values set on boot for a couple of days now；
1200Mhz - 1175mV
1000Mhz - 1075mV
800Mhz - 975mV
500Mhz - 875mV
200Mhz - 625mV (yes! i know . tried 650mV and my screen washed out!)..
Click to expand...
Click to collapse
I'm using roughly similar settings (top is 1252mhz @ 1175mv).. although my 200mhz is at 825mV, can it really go down to 625mV without issues? Anyone else have input on this?

yakyllan said:
What kernel are you using for the UV?
Any recommended ?
(I don't want to lose my root)
Click to expand...
Click to collapse
now im on CM7, using codewokx kernel (cmw 5.0).
a while back when i was on stock ROMs i used, Ninpho and siyah kernels, both were good on battery, i know with siyah 1.7.8 u can UC to 100Mhz (the standard 200mhz).
u should try one of em out, and see which is best for you.

viva.fidel said:
I'm using roughly similar settings (top is 1252mhz @ 1175mv).. although my 200mhz is at 825mV, can it really go down to 625mV without issues? Anyone else have input on this?
Click to expand...
Click to collapse
On 200mhz, i can only set voltage from 875-800, and anything btw 800 and 625 gives me a reboot. right now im doing 1d3h28m and still got 34% left.

Thanks to the OP, didn't think I could get to 625mv on 200hz.
850 mv 200 Mhz was my previous setting (825mv would crash)
Tested 625mv and so far so good. CM7 kernel & SetCPU.
200 Mhz - 625 mV
500 Mhz - 850 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1150 mV
Stable.

Geumbou said:
Tested 625mv and so far so good. CM7 kernel & SetCPU.
200 Mhz - 625 mV
Click to expand...
Click to collapse
That's unbelievable. my phone just freezes at such a low voltage

Most custom kernels now a days comes with undervolting underclocking scripts.
Eg: my galaxy s2 is on Touch X xwki8 based rom, which contains undervolting scripts.
Mhz : mv
1400 : 1275
1200 : 1175
1000 : 1075
800 : 975
500 : 875
200 : 850
100 : 825
All of them installing these roms never complained on hanging or not booting problems.
I installed them and never caused a problem for me either. But when I replaced the siyah 1.8 kernel with siyah 2.1, the same scripts never worked on the same phone. In fact it never booted. I had to change the voltages slightly inorder to make it boot again.
My conclusion is the phone manufacturers are making the phones almost 99.99% alike. The changes in volts must be because of different roms or probably kernels installed on different phones. I believe 2 same phones with the same rom and kernel will work with the same under volt script.
What do you think..?
Sent from my GT-I9100 using xda premium

click on my sig to see the results of mine

My battery is now just terrible.

I have had data on for a huge chunk of this time and played shadow gun for 10 minutes. I'm over locked to 1300 Max 800 Min on ondemmand. Auto brightness, disabled auto sync, and all the other tricks you can think of. With data off I can pull off an extra 6 hours without games. What is this horse s**t?
{
"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"
}
P.S. It died 3 minutes after posting this... And that black space is from my phone randomly rebooting on me... And then failing the first boot animation (as usual), re-rebooting itself and then finally, after getting by the second boot animation it turned on.
Nexus S - CyberGR Hybrid ICS (5), Matrix Kernel (15.5)

Try Eugene kernel with luzuactive. I am having good battery life with that.
Sent from my Nexus S using xda premium

That seems fairly normal to me on ICS; maybe even better than what I can get. I can only get about 2.5 hours of on screen time + 20 hours idling.
You have about 4 hours on on screen time and no idling. Seems about right.
However on Gingerbread you could probably pull off more on-screen usage.

herzlich said:
Try Eugene kernel with luzuactive. I am having good battery life with that.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Does NS Tools work with that? I want to keep my BLN and Deep Idle . And can you point me in the direction of the kernel
***** EDIT: Nvm found it, going to try it. It does work with NS Tools says the dev and users of the ROM
AeroEchelon said:
That seems fairly normal to me on ICS; maybe even better than what I can get. I can only get about 2.5 hours of on screen time + 20 hours idling.
You have about 4 hours on on screen time and no idling. Seems about right.
However on Gingerbread you could probably pull off more on-screen usage.
Click to expand...
Click to collapse
I was able to get a lot more out of it a week ago... The same things I do now I could do for 4-7 (+some off screen use...) hours, off screen would be MUCH better... It just suddenly stopped being good. ICS wasn't always this bad lol

For starters your min is 800 MHz.... What the heck?! Who needs that? I'm sure that and being OC'd to 1300 hurts too.

MrDrumngun said:
For starters your min is 800 MHz.... What the heck?! Who needs that? I'm sure that and being OC'd to 1300 hurts too.
Click to expand...
Click to collapse
So should I drop all the way down to 100, or go for 200 or 400? 100 seems blegh to me. I'm thinking of 200? I am however keeping the 1300 . If I must I'll go down to 1200.

Kernel is definitely not the problem. I've ran matrix before and its had some of the best battery life.
Problem is with your 800mhz min. You definitely don't need that. Run it at 200 and the difference won't be that significant.
Sent from my Nexus S using xda premium

moneybag said:
Kernel is definitely not the problem. I've ran matrix before and its had some of the best battery life.
Problem is with your 800mhz min. You definitely don't need that. Run it at 200 and the difference won't be that significant.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Okay thanks . So I'm going to go for 1200 / 100 on the speedy 7 kernel (lulzactive)... Good? If it works out eventually I'll switch back to Matrix 15.5 and see the difference. I've heard Trinity is very good
Just waiting on a full charge will post results when they come in. I'll be doing some very heavy usage because that's what I'm concerned about.
P.S. I've enabled Auto-Brightness after "re-thinking" the advantages to it in terms of battery use + screen visibility.

With smartassv2/sio on CyberGR & Eugene kernel I'm getting the best battery performance I've had ever since I put on ICS. At this rate I can hit 3 days idling. With heavy usage, probably 6-8 hours? Try it.

deetailed said:
With smartassv2/sio on CyberGR & Eugene kernel I'm getting the best battery performance I've had ever since I put on ICS. At this rate I can hit 3 days idling. With heavy usage, probably 6-8 hours? Try it.
Click to expand...
Click to collapse
I'll try it on lulzactivev2 first. Isn't lulactivev2 better than smartassv2 ? Every site I go to with information regarding governors tells me something else lol. Except ondemand that's the only one that has had a consistent definition.

Sent from my Nexus S using XDA App

Set min freq to 200 first off. 800 min is way too high if you want to save battery.
Secondly leave deep idle turned off, it doesn't do anything on ics.
check out bedalus battery drain comparison.
I get around 4 hours of screen on time for about 12-14hrs on battery.
I also undervolt more than the kernels are already undervolted.

nodstuff said:
Set min freq to 200 first off. 800 min is way too high if you want to save battery.
Secondly leave deep idle turned off, it doesn't do anything on ics.
check out bedalus battery drain comparison.
I get around 4 hours of screen on time for about 12-14hrs on battery.
I also undervolt more than the kernels are already undervolted.
Click to expand...
Click to collapse
I already have a 100 min on-going so I don't want to mess up the test . Afterwards I'll do 200. As for deep idle the option on my NS Tools has mysteriously vanished so I won't be able to enable it either way . I'm not going to touch under voltage I don't know much about over clocking (besides it speeds up your phone) as is. Lol rather not get into another hole

309041291a said:
I already have a 100 min on-going so I don't want to mess up the test . Afterwards I'll do 200. As for deep idle the option on my NS Tools has mysteriously vanished so I won't be able to enable it either way . I'm not going to touch under voltage I don't know much about over clocking (besides it speeds up your phone) as is. Lol rather not get into another hole
Click to expand...
Click to collapse
I read somewhere that 200 is better than 100 bit the only way to know is to try it out!
That's coz speedy doesn't have deep idle. Nstools doesn't show options the kernel doesn't have.
Well if you wanna try undervolting just uncheck set at boot in nstools.
Then search for stock nexus s voltages and see what they are and then look see what yours are and work from there.
The worst that will happen is that your phone will reboot but it will boot into the kernels stock voltages because you unchecked set at boot! No harm done!

Are you running the kernel with the 65 fps hack or no?
Sent from my Nexus S using XDA App

800mhz min?!?!
wow.
if anything, that should be your MAX speed...
I'm running 1000mhz max 100min with smartassv2 on the latest matr1x kernel and it lasts all day with pretty heavy use

nodstuff said:
I read somewhere that 200 is better than 100 bit the only way to know is to try it out!
That's coz speedy doesn't have deep idle. Nstools doesn't show options the kernel doesn't have.
Well if you wanna try undervolting just uncheck set at boot in nstools.
Then search for stock nexus s voltages and see what they are and then look see what yours are and work from there.
The worst that will happen is that your phone will reboot but it will boot into the kernels stock voltages because you unchecked set at boot! No harm done!
Click to expand...
Click to collapse
Haha very true! Will do . Already I am not noticing the mass heat emitting from my phone (1200/100).
mathkid95 said:
Are you running the kernel with the 65 fps hack or no?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Umm I'm not sure :S? How do I check?
derekwilkinson said:
800mhz min?!?!
wow.
if anything, that should be your MAX speed...
I'm running 1000mhz max 100min with smartassv2 on the latest matr1x kernel and it lasts all day with pretty heavy use
Click to expand...
Click to collapse
Haha, yeah I had originally intended for epic speed. I soon realized it wasn't worth it (my quadrant scores are only 300-500 lower now...). Oh wow. Well hopefully these new settings and governors will help me!

When did you download the zip?
Maybe you can post the mediafire link of the one you downloaded?
Sent from my Nexus S using XDA App

mathkid95 said:
When did you download the zip?
Maybe you can post the mediafire link of the one you downloaded?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I downloaded the ZIP today so it would be the most recent download link (if that helps).

Yeah you're good then..
Just follow nodstuff's advice and lemme know what happens!
Sent from my Nexus S using XDA App

Share your Voltage Settings here!

Hey everyone, I figured we deserved to have this thread as I hadn't seen one yet. I'm forever trying to tweak and adjust my voltages on my NS4G and I just wanted to see what everyone else was running and with what degree of success.
List your ROM/Kernel combo and your OC/OV/UV settings!
Currently:
CodenameAndroid 1.4.0
Matr1x v17.5 cfs
1300/400 SavagedZen
Deep Idle on.
@1.3GHz - 1430mV
@1.2GHz - 1350mV
@1GHz - 1280mV
@800MHz - 1205mV
@400MHz - 1030mV
...Stability tests are ongoing.

Rom: MIUI 2.3.9 (ICS)
Kernel: Matrix 17.5
Live OC: 105
Min: 210
Max: 1050
Voltage: All stock voltages dropped by 25
Scheduler: Deadline
Deep Idle: On
The voltages being dropped immensely helps battery life. I get at least 12 hours with heavy use and about a day and a half with light use.
Sent from my Nexus S 4G using xda premium

Almost same..
http://forum.xda-developers.com/showthread.php?t=1335429

Undervolting doesn't actually help the battery :$.... Well by much anyways. If it does it will be like a 2% difference... Instability doesn't seem worth it for 2%
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged

309041291a said:
Undervolting doesn't actually help the battery :$.... Well by much anyways. If it does it will be like a 2% difference... Instability doesn't seem worth it for 2%
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
Click to expand...
Click to collapse
I always doubted bedalus claims on the matter (and even communicated with him through PM).
Time permitting, I'd like to do some tests myself about undervolting, because I am pretty sure it has an impact.
Anyway, my settings are in my signature.
polobunny said:
For those interested, I spent the night yesterday testing out ARM voltages on my phone that were absolutely stable but hopefully under the stock ones to save more battery.
Had a look at morfic's git for a good idea, so thanks to him.
Might not work on your phone, so use at your own risk.
100MHz 875mv (75mv under stock)
200MHz 875mv (75mv under stock)
400MHz 900mv (150mv under stock)
800MHz 1125mv (75mv under stock)
1000MHz 1225mv (25mv under stock)
Click to expand...
Click to collapse
Some people have a problem with 400MHz at 900, 950mv seems good for anyone though.

AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900

lolokman said:
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
Click to expand...
Click to collapse
What's the battery like? And I believe the matrix kernel is already Undervolted by default.
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged

Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app

gear.h34d.2012 said:
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
On-screen time? With a screen
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (110 - Noop)
v6 Supercharged

lolokman said:
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
Click to expand...
Click to collapse
Interestingly I'm able to undervolt quite a lot more than I've ever been able to using this smartassv2/ noop setup. I'm not sure what it is but anytime I'd try to under volt matrix v18 any below stock I'd get reboots but with this setup I'm close to the values you've set and it's been stable so far. Its not undervolted as heavily and I don't have liveoc enabled at the moment. I'm just enjoying the ability to under volt it to where it is at the moment.
Sent from my Nexus S using Tapatalk

Currently using Franco kernel 1.2 and I dropped the stock voltages by 50(I was feeling a bit adventurous). Getting pretty nice battery life and stable(no reboots yet).
Sent from my Nexus S using Tapatalk 2 Beta-2

polobunny said:
I always doubted bedalus claims on the matter (and even communicated with him through PM).
Time permitting, I'd like to do some tests myself about undervolting, because I am pretty sure it has an impact.
Anyway, my settings are in my signature.
Some people have a problem with 400MHz at 900, 950mv seems good for anyone though.
Click to expand...
Click to collapse
Not sure if lower voltages, would make for less amp/wattage draw,
Sent from my Nexus S 4G using Tapatalk

what exactly is the difference between arm and int voltage? and what should i drop? both?
i have been undervolting with the internal voltage controle of aokp and this only drops int voltages //edit: After taking a second look, it seems like its arm thats changing...

I've dicked around with undervolting since my Evo days, and honestly, it does nothing for battery life. Multiple kernel developers - not to mention bedalus's tests - confirm this.
Undervolting seems useful only for providing an excuse for futzing with your phone. Any power savings are likely anecdotal or psychological.

i start from now the undervolitng , i chek and after i post my expirience .

gear.h34d.2012 said:
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
{
"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"
}
There it is.

gear.h34d.2012 said:
There it is.
Click to expand...
Click to collapse
I bet your phone was on idle most of the time.

currently running with these voltage settings:
freq arm int
1200 1350 1125
1000 1225 1075
800 1075 1000
400 950 1000
200 875 975
Governor:SmartassV2
Scheduler:noop
mix/max:200/1200
Rom:Codename Android 3.6.0
Kernel:AirKernel 65fps+BlueColor HBM #211
no reboots so far, but i feel that i've not reached the down-limit point! especially for 1000mhz freq

i'm default

please give me description about voltages.

[Request] AMOLED-Oriented Battery Kernel

I miss the ICS days of Matrix 20.0. I pulled 7 hours of on-screen use twice, and always at least 5 hours of on screen time in 10-28 hours overall. That was some amazing battery life.
I really wish someone would make a kernel or implement these features on a currently active kernel for us AMOLED i9020 Nexus users.
What features?
Under voting, 50 FPS, tweaked deadline scheduled for battery, on demmand with the current settings bedalus uses, 100 min setting, and adjustable (400/800) Live OC.
Some people may argue all of those features save little to no battery. I'd disagree on all except maybe Live OC. I know for a fact that my battery has been NOWHERE near the same as ICS since JB. I struggle to get 4 hours of screen use. I know get about 2.5-4.0. Coming from 5.5-7.3 hours of on screen use this is terrible! I know those 'small' features in combination with each other made a huge impact on battery.
If I had the resources to make my own kernels I would. But I don't have the resources (good computer or knowledge or time) to do so. Hopefully some amazing DEV will make a JB kernel dedicated to battery life on AMOLED screens for our Nexus. That would be great ...
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Marmite Kernel (4.4.5 - Bedalus)
Smartassv2 (1000/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Stock Voltage)

309041291a said:
I miss the ICS days of Matrix 20.0. I pulled 7 hours of on-screen use twice, and always at least 5 hours of on screen time in 10-28 hours overall. That was some amazing battery life.
I really wish someone would make a kernel or implement these features on a currently active kernel for us AMOLED i9020 Nexus users.
What features?
Under voting, 50 FPS, tweaked deadline scheduled for battery, on demmand with the current settings bedalus uses, 100 min setting, and adjustable (400/800) Live OC.
Some people may argue all of those features save little to no battery. I'd disagree on all except maybe Live OC. I know for a fact that my battery has been NOWHERE near the same as ICS since JB. I struggle to get 4 hours of screen use. I know get about 2.5-4.0. Coming from 5.5-7.3 hours of on screen use this is terrible! I know those 'small' features in combination with each other made a huge impact on battery.
If I had the resources to make my own kernels I would. But I don't have the resources (good computer or knowledge or time) to do so. Hopefully some amazing DEV will make a JB kernel dedicated to battery life on AMOLED screens for our Nexus. That would be great ...
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Marmite Kernel (4.4.5 - Bedalus)
Smartassv2 (1000/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Stock Voltage)
Click to expand...
Click to collapse
You may not get it. Most of the features you are asking are a strict no-no from the current Kernel devs of Nexus S. The only kernel that include a voltage mod today is Air Kernel, but you may need to do undervolting yourself. You can try reducing all voltages by 25 and check stability, my phone can take up to 75 voltage reduction.
Again there are no 50 FPS kernel for JB. You can modify ondemand settings & voltage settings using NSTools. Live OC isn't there in any JB kernel and will not be included by any one as it is unstable. Bedalus ondemand settings are below:
Sampling rate - 20000
Up Threshold - 95%
Sampling down factor - 1 step
All the best..

anshumandash said:
You may not get it. Most of the features you are asking are a strict no-no from the current Kernel devs of Nexus S. The only kernel that include a voltage mod today is Air Kernel, but you may need to do undervolting yourself. You can try reducing all voltages by 25 and check stability, my phone can take up to 75 voltage reduction.
Again there are no 50 FPS kernel for JB. You can modify ondemand settings & voltage settings using NSTools. Live OC isn't there in any JB kernel and will not be included by any one as it is unstable. Bedalus ondemand settings are below:
Sampling rate - 20000
Up Threshold - 95%
Sampling down factor - 1 step
All the best..
Click to expand...
Click to collapse
I know the DEVs of today won't do it, but that doesn't mean nobody might give it a shot or make a new kernel...Matrix 20.0 was 50 FPS on ICS so it's possible. I've UV at 50 on Air and it was fine. I already know the Bedalus settings.... My kernel is Marmite lmao.
I'm not asking for MK, r_data, or Bedalus to do this. I'm asking someone else. If I could I'd try to make an AMOLED battery kernel. I miss good JB battery.
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Marmite Kernel (4.4.5 - Bedalus)
Smartassv2 (1000/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Stock Voltage)