yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shawn122:
14 hours...fairly heavy use

I want to thank everyone who has chimed in with their tweaks and settings. Below is screenshot of my battery use from yesterday.

Kyan Rom 1.5 (I like most of the Samsung features: Voice recorder, camera etc)

I/O Scheduler: noop

governor: abyss plug

I am still tweaking the voltages but yesterday I was pretty happy with the stock battery life. Screen on time was 2 hours but my voice calls were an 1.5 hours. I had the mobile hotspot on for about an hour as well.

MHz mV

2106 - 1185

1998 - 1150

1890 - 1130

1809 - 1105

1728 - 1090

1674 - 1070

1512 - 1070

1458 - 1050

1404 - 1030

1350 - 1005

1296 - 990

1242 - 955

1188 - 945

1134 - 940

1080 - 935

1026 - 915

972 - 900

918 - 895

864 - 865

810 - 855

756 - 845

702 - 830

648 - 815

594 - 800

540 - 790

486 - 780

384 - 770

192 - 760

144 - 750

96 - 740
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dntesinfrno:
Looking at your screen shots, i'd be willing to bet turning off that cpu montior in you notification bar will save you a good bit of battery life. Just an educated guess but it seems to me that would keep the CPU from ever actually sleeping fully since its constantly reporting itself to this process. Would be worth trying in any case :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Cool tool take very few battery. Around 2% and it doesn't keep the CPU from sleeping fully since it is not the CPU that report itself but cool tool that monitor the CPU .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Here are screen shots to prove my point. Cool tool is not even in the list and I get almost 5hours of video and gaming.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noahattic:
I'm pretty interested in getting an extra battery and love the idea of the 4400maH capacity.

I am just wondering if you could upload a picture of the back cover?? I am a bit worried about the thickness of extra larger battery and build quality of the cover.

I tried to dig out some pictures from eBay already, but none of them really shows how it looks in the real life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Since this is not a battery thread, I would appreciate if this conversation and any others conversations about battery could be continued via PM or another thread :)

Thank you!;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Ktoonsez,

I know you are one busy man but I have a question for ya, is it possible to implement the tweaks available for the s2 on your siyah build with extweaks for the s3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I don't think ktoonsez spend so much time in here. You should try his kernel thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shawn122:
Thanks very much for the feedback. I am new to this game but I like to tweak things and I have been doing the trial and error thing for the past few days. I don't use cool tool much...and only have it on for a few seconds at a time.

One question though...

I always leave bluetooth on so that when I enter my car it launches the Tune In app when it connects via a tasker profile. I noticed today that bluetooth increased my battery drain significantly (not obscene amounts but by a few percentage points). Does anyone know if the bluetooth drain is higher on the S3 than other devices? I am coming from the Samsung Captivate which was running Cyanogen Mod 9 with Devil Kernel and somehow I feel the bluetooth didnt drain as much battery when connected.

Any thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Btw liltitiz, no disrespect intended with your name, just pointing out I think why some people thought you may be of the most female persuasion. Nice work here.

---------- Post added at 07:27 PM ---------- Previous post was at 07:23 PM ----------

BT drinks battery for me on my s3 and on my captivate since éclair. Since you have Tasker, set it up to automatically disable bt after 3 or whatever minutes disconnected. I do this, and have it turn it on automatically in the times I'm most likely to be I in the car, and then just turn it on manually otherwise, notification widget makes it fast. Now if I could only figure out how to make jb or ics auto connect instead of having to press the bt device name, I'd be sailing happy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
In case anyone missed this in kernel thread:

These settings are for better battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Gonna try these settings

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shawn122:
Thanks for the feedback. I don't seem to have a problem with bluetooth auto connecting provided I don't switch it off. Is this what you were referring to? Switching it on and off and then having to touch the screen to connect?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Anyone can help me figure out what is going on with my phone?

I think I might have some kind of voltage problem.

The lowest undervolt I can apply in ICS is -50UV to all, less than that everything freezes.

in AOKP as soon as I install Ktoonsez's kernel my phone keeps crashing and freezing even after a fresh full wipe...

I'm not sure what to do

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
So it boots? I guess you could try raising voltage and see if that does anything but I recommend trying another kernel. Some phones don't like certain kernels. Try faux or lean (in tmo forum)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Let it reboot some phone can reboot 10-15 times before running the kernel alright. Mine just did it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
just tried these settings and during my sleep my battery plummeted from 98% to 25% while i slept. wtf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
But the problem is that Faux didn't update his kernel for AOKP.

I'll check out Lean's thanks

EDIT: I tried Lean's, it freezes during boot :S (when you see "android" on the screen)

oh really?

interesting....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Something kept your s3 from deep sleep. Check with better battery stats to find it. Check maps, your GPS, Bluetooth. Weather in the notification menu or lock screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dntesinfrno:
Or any other processes that are labeled in the details as *wakelock*, which is exactly as it sounds. This means the process is locking the phone in awake mode and although the screen may be off the phone is still awake and plugging away keeping this(or these) process(es) happy. Most of the time this is usually a sync function or something similar that can be disabled in the app settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
I looked at my CPU app and it says the phone was in deep sleep while I was sleeping. I heard betterbatterystats has been sucking lately with crashes so I haven't dled it yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
It still freezes after 10 reboots...

The only way I can stay stable is if I add +50Mv to all steps.... that's not normal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Well, nothing is abnormal when it comes to how your phones react to a kernel.if you were running this kernel previous version without experiencing this issue, just try to format everything, data, system, cache, dalvik and sdcard. And reinstall it. Flash ROM and gapps, reboot in recovery, flash kernel, clear cache, clear dalvik and fix permissions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Sometimes phones hard reboot and it makes the battery drain like crazy in one shot did you noticed if it rebooted during the night?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Try the official aokp I think it comes with fauxs kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
No I did not notice it reboot. I am trying it agian and it seems to be dropping quite fast agian

At 90%

34 minutes ever since i took it off plug. 23 minutes time on.

4G on, Gps wifi off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Go through 3-4 charging cycle your phone must be decalibrated. Are you using the same governor as before this happened?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
I am goin to let it drop to around 5% and recharge 3-4 times. I am using the same governor and scheduler.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I've been doing this today with Paranoid Android 2.23 and KT 10/22 and 10/16.

The voltages are stock starting at 1080.

700 mv
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
This is weird.... not sure your CPU will really like this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Posted this in the main KT747 thread, thought I'd post it here as well.

Here is what I am currently running with 0 problems thus far. I tested these settings with Stability Test, using the scaling test (currently over a hour so far). *See pic below.

If you are going to try these UV settings, please make sure to disable set at boot; less you get stuck in a bootloop.

ROM: AOKP 10/16

Kernel: KT747 AOSP JB 10/16

Min: 96 Mhz

Max: 1728 Mhz

I/O Scheduler: deadline (stock values)

CPU Governor: ktoonservative (stock values)

Touch Boosters: stock values

Screen Off Profile: 486000

Vibration Strength: 90

Voltages:

1728 Mhz = 1080mv (had to raise it back to my previous settings, the only crash I got was at this value)

1674 Mhz = 1060mv

1512 Mhz = 970mv (could have eaisly been 800mv, but I had to leave room for the other frequencies ;) )

1458 Mhz = 960mv

1404 Mhz = 950mv

1350 Mhz = 940mv

1296 Mhz = 930mv

1242 Mhz = 920mv

1188 Mhz = 910mv

1134 Mhz = 900mv

1080 Mhz = 890mv

1026 Mhz = 880mv

972 Mhz = 870mv

918 Mhz = 860mv

864 Mhz = 850mv

810 Mhz = 840mv

810 Mhz = 840mv

756 Mhz = 830mv

702 Mhz = 820mv

648 Mhz = 810mv

594 Mhz = 800mv

540 Mhz = 790mv

486 Mhz = 780mv

384 Mhz = 770mv

192 Mhz = 760mv

144 Mhz = 750mv

96 Mhz = 740mv

If you try these and are getting a crash, I'd suspect it's most likely the lower underclock, or high overclock values.... but what do I know. :o

Hope this helps!

^^^Been running this since last week, with no problems.^^^

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
What kind of life you getting out of one charge? Do you have an extended battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] citsong:
Ok here's my voltage table. It's pretty similar to what's been posted already at the low end. I had some of the mid range speeds alot lower but it made it harder to UV the higher ranges. Been running the pegasus gov with the settings posted in the thread with noop and averaging around 3hours screen time with about 18hrs with PA 2.25. Screen off at 486mhz. Pretty content with the results I've been getting with the latest kernels, couldn't uv past 850mv at 96 until the last 3 kernels or so. Going to try out the new wheatley gov today and see how it works.

Min/Max = 96mhz/1728mhz

96mhz --- 740mv

144mhz --- 750mv

192mhz --- 760mv

384mhz --- 770mv

486mhz --- 780mv

540mhz --- 790mv

594mhz --- 800mv

648mhz --- 815mv

702mhz --- 830mv

756mhz --- 845mv

810mhz --- 860mv

918mhz --- 890mv

972mhz --- 910mv

1026mhz --- 930mv

1080mhz --- 940mv

1134mhz --- 970mv

1188mhz --- 970mv

1242mhz --- 1000mv

1296mhz --- 1015mv

1350mhz --- 1025mv

1404mhz --- 1055mv

1458mhz --- 1075mv

1512mhz --- 1100mv

1674mhz --- 1125mv

1728mhz --- 1130mv
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I tried swift voltage table but my phone rebooted. Tried yours and it worked however I notice lag and it took longer for apps to start so I went back to my settings.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
It's actually doing great. It's passed just about every benchmark and stability test I've thrown thrown it. It runs all the apps I've tried fine, no reboots/crashes.

They only trouble I've had is occasionally Google now will crash the phone, other than that one app everything works great.

Samsung seemed to have the widest range of build qualities for their chips. I guess mine was a lucky one that could handle the 700mv. It's sad really how others have so much trouble with this kernel/undervolting.

Edit: the fact that everything else works fine makes me think it's the Rom which needs an update...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Have you used Google maps?

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yeah, every app I use in a normal day has worked flawlessly at 700mv from 1512 to 1134.

I can't believe it, but it's rock stable. I can't get it to crash, except with google now.

I've found that if i set it to 1458 instead of 1512 it doesn't crash google now. i even went from 700mv to 775 on 1512 and google now still crashed. It is stable at stock, I don't really care enough to fight a million reboots just to get a "google now stable" voltage for the highest step. I'd rather take a 54 mhz decrease in my cpu frequency and run at 700mv....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
My newest stable settings

2 Hours of Stability test - Scaling test

Core 1 Seccessful runs: 104

Core 2 Seccessful runs: 102

Ram (760 mib / run) Seccessful runs: 2574

30 min of extremely heavy use (youtube, Facebook, Browser, text)

2 days of normal use with no random reboots.

Running Parinoid Android v2.5 with Ktoonsez's KT747 10/22 Jelly Bean kernel

I/O Scheduler = noop

Governor = ktoonservative

Mhz ______ mV _____ Difference from stock

2106______1220_____-130

1998______1190_____-135

1890______1160_____-140

1809______1135_____-140

1728______1110_____-140

1674______1085_____-115

1512______1070_____-130

1458______1050_____-135

1404______1040_____-145

1350______1025_____-150

1296______1015_____-160

1242______1000_____-150

1188______0985_____-165

1134______0965_____-160

1080______0945_____-180

1026______0920_____-155

0972______0910_____-165

0918______0900_____-150

0864______0885_____-165

0810______0865_____-160

0756______0845_____-180

0702______0825_____-150

0648______0815_____-160

0594______0800_____-150

0540______0785_____-165

0486______0775_____-150

0384______0765_____-160

0192______0755_____-170

0144______0745_____-180

0096______0735_____-190

---------- Post added at 01:34 PM ---------- Previous post was at 12:55 PM ----------

Since your 1080Mhz is at a stock 1125mv, All your voltage from 1134-1512 is 1125mv, you cant have more than 100mv difference between steps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hmm... ktoonsez never indicated anything like that... what dictates the 100mv difference?

Edit: I PM'd Ktoonsez and he confirms, he doesn't agree.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Not a Tegra kernel, that rule doesn't apply.... This was a rule you had to follow when I was on the Atrix; had to keep all frequencies within 100mv of the step before or after it, or your UV supposedly wouldn't take... But like I said, that shouldn't apply here.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
Does make sense it was probably on the atrix forum that I read it on.

I just don't see how it's possible to run those steps at 700mv, it doesn't seem like enough power.

You could install Current widget and it will give you actual real time mV

https://play.google.com/store/apps/details?id=com.manor.currentwidget
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I'm also sceptical about it. It doesn't make any send to me that a lower freq need more voltage than a higher freq. I'm not an expert though, I can be wrong.

This widget monitors the battery not the CPU. It won't really help in this situation. Unless you know exactly how much voltage every other part of your s3 needs :p.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I'm skeptical about it too..... 700 seems too low. IDK... the build qualities are so different, some say they can't drop 5mv...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
Sorry my midnight googling isn't that great lol give me a few min to get to work and I'll see of I can find a way to view real time cpu voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
TBH I think there is something with Ktoonsez's kernels.

In ICS with his Touchwiz kernel I cannot UV more than -50mv

In JB(ktoon's rom) as soon as I install his kernel my phone hangs, crashes and reboots.

BUT

In JB If I leave the stock kernel I have no issue.

in ICS if I install Faux's kernel, NOW I can UV by -125mv to all steps with no issues

So it's like if the voltages in KTweaker are not correct(at least that's what I'm thinking)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
He stated several times that he used more optimization flags when compiling that allows more undervolting. The drawback to more optimizations has been that the kernel wont boot for some phones but I think he fixed that issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
sadly not yet :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yeah i agree with you but 700mv @ 1512mhz is still hardly believable :p I have drop mine to 900 @1512mhz And it was stable but I stepped it up to 1090 to let room for others freq. Now I'm doing the whole stability test again to see how much my phone can take now :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Not even the iPhone 5 can do that!:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hit 9630 on Antutu, 2740 on Atutu 3D, not bad. New kt and task 1.3 stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
So this isn't as much a settings questions as it is I can't get something to work and i'm wondering if changing settings will help.

I'm trying to get HDMI working with the MHL adapter. On completely stock software it works no problem. Once I install this kernal it stops. I really love the battery life I was getting but I need this to work.

Does anyone have any advice they can offer or settings that will make it work again?

Running stock TW/ICS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zugshad:
Curious to see what recommendations would be for the new Ktweaker settings with the ability to have a screen-off gov ... currently I have been running Ktoonsertive and Sio.... would there be a better gov for just screen off ??

thnx for input
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
New kernel, new governors, more butter. Who can ask for more with 10/28?

Been playing around with new governors anyone else find a better setting for overall performance and battery than deadline + Abyss?

AT&T SGS3

ParanoidKangDroid 1.1.0

KT747 10/28 OC'ed & UV'ed

Medical MJ Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you tweaks interactive or coservative a little you can get pretty nice results. Smartassv2 do a nice job if you set it how you want it to act.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I've been using noop and ktoonservative with up_threshold_hot plug ramped to 68 and sampling_rate ramped to 30000. I've been seeing best battery with these settings.

Any governor adjustments?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
I'm on the noop/ktoon with sampling at 300000 and frequency stepping at 2, - 15v UV at every step. Min freq at 192.

That gives me serious stability and no reboots with wicked battery. Yesterday at 14 hours with just over 2 hours of screen on an 1 hour of audio out I was still at like 52%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
My setup exactly. I don't think it can get any better, really. 8100 antutu and it sips on battery better than any ever setup I've tried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the green man:
Could you explain what sampling and frequency stepping is? I would like to try your settings but am unsure how to apply them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
I believe it's in the Faq in the OP, but I may be mistaken. I just saw other people were fiddling around with those settings and went from there. :what:

I had problems with it killing tasker if I set my min frequency under 192.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
"Governor adjustments" in General.

---------- Post added at 06:52 PM ---------- Previous post was at 06:52 PM ----------

300,000? Or 30,000?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
http://xdaforums.com/showthread.php?p=19846276
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
You guys have any suggestions for screen off governor selection to conserve battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Wondering if you mean 300,000 or 30,000.

Also, why don't you have 96 MHz enabled?

I think I might try your settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I was curious too so I tried 300,000 and it's possible that's what he meant cause it lags a little but seems to conserve a lot of battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
I mean 300k and no lag here at all. At least nothing noticeable. I can't manage a stable UV on this phone, so I went that route instead.

As for the lowest step, 96 or whatever, it kept crashing tasker and forking up GNow. Also, I stream a lot of NPR over the TuneIn Pro app, and it would fail when the screen shut off @ lowest step.

Still fails on wifi with screen off, but I'm grandfathered unlimited, so w/e.

http://www.imgur.com/VNdPe.png
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Most of the devices can run the same voltage at 96 as 384 so it's kind of pointless. Anything under 384 causes screen flicker for me.I ran 96 for a while and just would disable the hw overlay but never saw a difference idling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
AT&T SGS3

ParanoidKangDroid 1.1.0 ROM

KT747 10/28 OC'ed & UV'ed

Medical MJ Suporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Apocalypse487:
My current settings:

Min: 96

Max: 1809

Governor: Ktoonservative

I/O Scheduler: Deadline

Frequency Boosters: Stock

Governor: what I had changed

Frequency Step: 2

Sampling Rate: 30,000

Up_Threshold_Hotplug: 68

I/O Scheduler: what I had changed

Fifo Batch: 2

Write_Expire: 2000

Voltage:

1809: 1135

1728: 1075

1674: 1055

1512: 965

Minus 10 all the way down to 96

Battery: 83% and discharging

On battery: 2 hours, 38 minutes and counting.

Screen time: 59 minutes and counting.

Picture upload failed. Not sure why.

Addition: This is 10 hours later and finally beating AC3.

Now: 12 hour and 55 minutes. 56% and 1 hour and 38 minutes of use.

After seeing everybody's results, I think my results are about the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alex2x3:
I recently got a replacement s3, and have for some reason been having pretty bad battery life.

I'm running AOKP and Ktoonz kernal just like I had before, with the exact same apps pretty much, literally running the same set up i had before.

Except that this phone can handle better undervolting, almost 100 less then I had it on my last phone.

BUT i'm not getting the better or even the same battery life that i did before.

Could someone help me?

I searched around and everyone says to install betterbatterystats and see what is eating it up.

For me it's PowerMangerService the most, then wlan_rx_wake, and then smdcntl0.

What does that mean though? haha

Would really appreciate some help because I was ecstatic to find that it could handle undervolting better but now a little bummed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
There is a point where too much undervolting can cause worse battery life. Try using your old voltage table. Or try just -100 or so across the board.

Also in better battery stats look at partial wake locks, not kernel wake locks. These are caused by apps that can usually be prevented.