Database Info

1.6GHz

:giggity: Adrynalyne test kernel
{
"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"
}
quadrant

Care to Share How?

This is cool but with it at 1.6 how long did the battery last >.>

And it begins! adrynalyne is a beast.
Sent from my ADR6400L using XDA App

You getting about 5 mins of battery life now?

That's teh sex!

Christ I wouldn't want the CPU that fast... 1.2Ghz would be my limit just because the battery wouldn't take too drastic of a hit. I mean the phone is already pretty well sound in the speed department

The real question (rather than being a smartass about it) is whether or not the custom kernel is simply overclocked... or if it is undervolted and overclocked.
It is very possible to obtain higher clock speeds at lower voltages on many CPUs. Therefore, there is no battery sacrifice when using the faster CPU clock speed!
Wasn't the G2 or MT4G overclocked to 1.6GHz and also undervolted to provide better battery life than the stock kernel?!

Well I did that just to show it works and is actually stable (ran it for 10 mins at that speed, no reboot). I just put it on there a couple minutes before that.

bmcclure937 said:
The real question (rather than being a smartass about it) is whether or not the custom kernel is simply overclocked... or if it is undervolted and overclocked.
It is very possible to obtain higher clock speeds at lower voltages on many CPUs. Therefore, there is no battery sacrifice when using the faster CPU clock speed!
Wasn't the G2 or MT4G overclocked to 1.6GHz and also undervolted to provide better battery life than the stock kernel?!
Click to expand...
Click to collapse
I honestly have no idea.

JayfromBK86 said:
Christ I wouldn't want the CPU that fast... 1.2Ghz would be my limit just because the battery wouldn't take too drastic of a hit. I mean the phone is already pretty well sound in the speed department
Click to expand...
Click to collapse
I had my OG droid OCd to 1.1ghz and had better battery life running Bugless beast and chevy's low voltage 1.2 kernel. Stock on the OG was 550 i think so i was doubling that speed, 1.6 once its played around with will probably not sacrifice your battery at all down the road.

I want one, I want one! Lol
Sent from my ADR6400L using XDA App

i want!!!!

hmm...~1700 on Adrynalyne's kernel for das BAMF 2.9 to 2300 OC'd. not bad

bmcclure937 said:
The real question (rather than being a smartass about it) is whether or not the custom kernel is simply overclocked... or if it is undervolted and overclocked.
It is very possible to obtain higher clock speeds at lower voltages on many CPUs. Therefore, there is no battery sacrifice when using the faster CPU clock speed!
Wasn't the G2 or MT4G overclocked to 1.6GHz and also undervolted to provide better battery life than the stock kernel?!
Click to expand...
Click to collapse
The D1's would run undervolted/overclocked with no problem. I ran mine @ 1.1ghz and undervolted.

magneticzero said:
You getting about 5 mins of battery life now?
Click to expand...
Click to collapse
Higher clock speeds =/= more battery usage

The UV stock clocked version of this kernel is hitting high 1800s to low 1900 in quadrant for me on a debloated but otherwise stock rom.

engagedtosmile said:
Higher clock speeds =/= more battery usage
Click to expand...
Click to collapse
not always. if it is a higher clock speed at a lower voltage it won't

nosympathy said:
not always. if it is a higher clock speed at a lower voltage it won't
Click to expand...
Click to collapse
That's what he was saying. "=/=" is "does not equal."
;-)

that's just silly without any extra qualifying statement.

Battery Life Suggestions - Please Post SetCPU Config's Please

Good Morning Thunderbolt Community:
I am looking for the best way to extend my battery life, I have a 2750 Extended battery and still only get a little over a day of battery life. I've read that some folks are using SetCPU again, and would like a thread dedicated to those who want to share their settings to benefit others....
Thanks in advance...ChiefDroid (a.k.a Chiefd23)

Running chingys 3d rom runing set cpu st 1113 max 368 min no profiles and st the end of my 12 hour day I have 70% left. have any more questions lemme know

Liquid gingersense 1.6. Imoseyons 3.5 kernel on extreme mode. Verizon 2750 battery. I get 50 hours easy with a lot of phone usage.

Gingeritis 3D beta VI, ziggys kernel set at 245/1.344 smartass gov, with script fusion (set cpu can be a big no no with some kernels, and id rather use scripts anyway) . I get 20+ hours with average use on a stock battery.
Sent from my TBolt using my f***king thumbs...

Pureasoptheory 1.3x modded imo kernel (stock with rom) setcpu at 1222/245 interactive and a profile for less than 30% @745/245 avg is around 24 hours on stock battery with low to moderate use, maybe a couple youtube videos lots of texting a few calls and lots of web browsing.
Edit: about 50% of the time I'm on wifi vs. 4g to clarify.

M0N0LITHTH3ORY. 245/1024 extreme battsaver. Standard battery. Lucky to get 8 hours. Best battery life of any rom for me so far. Average an hour of calls, 100 texts, TweetDeck and friendcaster pretty much every hour, words with friends, and web browsing.
Sent from my HTC Thunderbolt 4G LTE: M0N0LITHTH3ORY V1.1: MR2 using XDA Premium App

Hack3dao5p by dhacker29. 12 hours and I'm at 80% NO UNDERVOLTING. I will undervolt with vipermod tomorrow and report back. Don't use setCPU. Use vipermod or speedtweak. I recommend vipernod for more control.

Just plug it in every night. I can get 2 days out of my extended battery but what's the point??? Have fun with it instead of worrying about getting more than one day of battery out of it!
Sent from my ADR6400L using Tapatalk

pitchblack86 said:
M0N0LITHTH3ORY. 245/1024 extreme battsaver. Standard battery. Lucky to get 8 hours. Best battery life of any rom for me so far. Average an hour of calls, 100 texts, TweetDeck and friendcaster pretty much every hour, words with friends, and web browsing.
Sent from my HTC Thunderbolt 4G LTE: M0N0LITHTH3ORY V1.1: MR2 using XDA Premium App
Click to expand...
Click to collapse
Same here on all accounts
xTFGx said:
Hack3dao5p by dhacker29. 12 hours and I'm at 80% NO UNDERVOLTING. I will undervolt with vipermod tomorrow and report back. Don't use setCPU. Use vipermod or speedtweak. I recommend vipernod for more control.
Click to expand...
Click to collapse
I think I might make the switch! How much use? light, mod, heavy?

M0N0LITHTH3ORY straight out of the box, I'm getting close to 20 hours with 20% left for the first time ever. 4g when I'm out and WIFI at home. Like I said in the MONO thread this ROM is the best out there. oh yeah stock battery too. Thanks DT!

This is by no stretch of the imagination an Android development thread.

Fits better in General. I've moved it there.
Continue.

I haven't used SetCPU on my Tbolt in a while. My config is in my sig and my settings are implemented through ScriptFusion. The following is the settings I'm using in ScriptFusion. The first image is the clock/voltage settings, the second image is time-in-state. As you see, it spends most of it's time sipping .8 volts or less. As long as I'm not tapping glass like a mad man, eeking out a full day on the stock battery isn't terribly difficult.
{
"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"
}

justavillain said:
Same here on all accounts
I think I might make the switch! How much use? light, mod, heavy?
Click to expand...
Click to collapse
Mod-heavy mostly internet jtexting and Facebook with a few phonecalls here and there. GPS off

i use gingeritis 3d, wifi when im home, and when im out, i only activate mobile data if i wanna check my fb or look something up. cpu is usually max 1113600 min 8064000 scaling powersaver, i also use chainfire's nightmode setting when im not actively using my thunderbolt (tested today and seamed to help alot), auto brightness on. at the end of the day on a stock battery i am usually at 20-10%

I flashed the newest radio turned off 4g and am running CL3ANTH3ROY and i got 20 hrs on the charge off of 1.0. Im on 1.1 now at about 14.5 hrs on mod/heavy use with a little 4g use in there.
I know if you do not have 4g in your area all the time turning that off is a MANOR battery saver. If you didnt know go *#*#4636#*#*phone identity, scroll down and choose cdma auto (prl)
sent from my thunderbolt running CL3ANTH3ROY, using the XDA premium app

z06mike said:
Just plug it in every night. I can get 2 days out of my extended battery but what's the point??? Have fun with it instead of worrying about getting more than one day of battery out of it!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
This.
I charge mine every night and it makes through the whole day no matter what I throw at it. I keep email on push notifications and gps/sync on all the time. 4G is on all the time. None of those are ever turned off.
Why? Because that's how smartphones are supposed to be used! It's not a marathon race.
Sent from my Synergized Thunderbolt via XDA Premium App

Can I just make a quick comment about freq_min, freq_max, and governors? I like to equate them to a car's engine. At idle (freq_min), it's should be just loafing along, doing the least needed to keep things going. At red line (freq_max), it's chugging down the fuel and kicking out all the horsepower possible to haul that ride down the road. And your governor is kinda like your cruise control. You're cruising across Nebraska, not a hill in sight (you're phone is doing nothing) and it's just BARELY tipping that throttle in to maintain. But, you hit Colorado with those big ol' hills, and now it's flooring it, letting off, then flooring it again to get over those hills. Think of those hills like you making your phone do stuff.
Here's my point:
When you set your freq_min to 800MHz with, it's like running your engine at 5000RPM, all the time, regardless of load. Setting your freq_max at 800MHz is kinda like jamming a stop under your throttle so it will never make enough power to pull you over those big hills. The idea of a governor is to throttle the speed up and down relative to the load... kinda like your cruise control. Some could do it better, some have very limited real-world application (performance and powersave), and some are pretty much ideal. It really depends on how the dev has set them up or how you've tweaked them.
I post this because I'm looking at some of the setting some of you are using and I KNOW they could be more efficient. I would encourage you to look at your time-in-state and experiment with your freq_min, freq_max, and gov. As you can tell from mine, though I have my max set at 1.49GHz, it spends VERY little time up there. It's more like the nitrous shot if things get real hairy and the system needs the extra power.

i currently use BURNTH3ORYX V1.5 w/ the MR3.5 (802) radio, also have the 2750mAh battery, and i just use the built in "performance" option. I set it to 'OnDemand' and overclock to 1.5 Jigga Hertz.
for example, last night the battery was at 100% and decided to watch the movie "Return Of The Living Dead" all the way through. when it was done, the battery was at 95%.

[Q] voltage control tutorial?

Is there a tutorial (written or video) that shows how to use this? I've never overclocked or changed the voltage before and i dont wna just go in there n start messing with stuff when i have no clue what im doing. Ive looked around for maybe a begginers tut or like voltage control for dummies, but havent really found anything. Anyone know of one? Thanks.

It's really not very hard. The regular Voltage Control will not allow you to overvolt, so you will not run the risk of frying your processor. Don't go over 1400 mhz though. Bad magic after that.
Undervolting will not harm your phone, the most it will do is make it lock up. Just experiment with different voltages. Back in the day I used to run -75 mV across the board without many issues, but I don't really have a use for it anymore since I carry a spare battery. Don't be frustrated if your phone doesn't like even -25 mV though, because every processor is slightly different in their abilities to handle voltage and frequency changes out of spec.
Please note that PBJT kernel is already undervolted a good amount.
Sent from my SCH-I510 using xda premium

Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!

n1ghtwish said:
Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!
Click to expand...
Click to collapse
Can you please tell me what the actual voltage is? I found that with IMO 4.0 kernel, and with Tegrak Overclock Ultimate, I can clock the at 1.252 Ghz @ 1285mV and 1.3 Ghz @ 1330mV stably. However, I don't know what the actual stock voltage is or the PBJT voltage or IMO 4.0 voltage, etc.
I figure you could check the voltage at least with the free version of Tegrak.

{
"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"
}
Stable for days... Vr ..smartassv2.. 1200 max 100 min.. Eclipse with 1/15 pb&j
Sent from my SCH-I510 using XDA App

Phone is laggy
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb

dees_74 said:
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb
Click to expand...
Click to collapse
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
My phone was great when I flashed, but within about 12 hours, things were horrible. I have since flashed back to the stock fp1 kernel, and life is good. Unfortunately, I am not a person who 'leave well enough alone'. I'd like to enter the world of over/ under clocking and see if I can gain some additional performance.
Thanks in advance for any additional info/advice you can provide.
Sent from my Xoom using XDA

shrike1978 said:
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.
Click to expand...
Click to collapse
War Eagle!
I thought that was how it worked, but I will open voltage control from time to time and it will read that its currently at 400 or 800 MHz. Does the program not display properly?
edit: Playing around with it some more, if I change it to something else and then switch it to performance it goes right to 1000. Weird that it displays incorrectly when the program is opened.

[Q]Galaxy Tap 7.7 Can OverClock?

Galaxy Tap 7.7 Can OverClock?
...and It can Overclock ..how to do it?

PJTONz said:
Galaxy Tap 7.7 Can OverClock?
...and It can Overclock ..how to do it?
Click to expand...
Click to collapse
Until someone develops a custom kernel for overclocking, then the answer is "no."
However, if/when this does happen, you can use a root app called SetCPU.

PJTONz said:
Galaxy Tap 7.7 Can OverClock?
...and It can Overclock ..how to do it?
Click to expand...
Click to collapse
hi!
You can overclock your tablet with the Tegrak application on the market... be careful not to forget to increase the voltage at the same time in the overclokage... mine is Overclocked a 1.6GHz

hella i use tegrak too, you have set 1600 for ever? You are not scared if higth frequency fries your cpu? and what about mali400? U set the gpu to 400mhz and leave it at 400 for ever?

not my processor is set "on demand" it between 200 and 1600mhz.... However, I do not overclock the GPU....
{
"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"
}

I just tried overclocking with Tegrak too.
However, when overclocking to say 1.5 or 1.6Ghz it causes lag, why?

have you ever tried Zeta ROM ?

hillzx said:
have you ever tried Zeta ROM ?
Click to expand...
Click to collapse
It's ok with zeta rom.......v4

I bought Tegrak overclock, too.
Using stock ICS 4.04, does anyone know the right voltage to get up to 1.6Ghz ?
I tried mine 1.6Ghz at 1.45v, but I think it resulted lower Antutu benchmark, I don't know why..

dlee064 said:
I bought Tegrak overclock, too.
Using stock ICS 4.04, does anyone know the right voltage to get up to 1.6Ghz ?
I tried mine 1.6Ghz at 1.45v, but I think it resulted lower Antutu benchmark, I don't know why..
Click to expand...
Click to collapse
The bester for 1,6ghz is 1,250 and it's Ok with 1.3v
My quadrand is 5300

micger21 said:
The bester for 1,6ghz is 1,250 and it's Ok with 1.3v
My quadrand is 5300
Click to expand...
Click to collapse
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ?
or is the default voltage setup already too high enough that can be reduced while staying stable?
is it okay if you share your stable voltage for each ghz list ?
thanks

dlee064 said:
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ?
or is the default voltage setup already too high enough that can be reduced while staying stable?
is it okay if you share your stable voltage for each ghz list ?
thanks
Click to expand...
Click to collapse
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ? yes
or is the default voltage setup already too high enough that can be reduced while staying stable? yes very stable, no issue
.........lowering processor voltage, the gain of battery can be observed, and the power is here!

micger21 said:
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ? yes
or is the default voltage setup already too high enough that can be reduced while staying stable? yes very stable, no issue
.........lowering processor voltage, the gain of battery can be observed, and the power is here!
View attachment 1308231
View attachment 1308232
View attachment 1308233
View attachment 1308234
Click to expand...
Click to collapse
Thanks a lot for your screenshots,, first two pics are the same btw

dlee064 said:
Thanks a lot for your screenshots,, first two pics are the same btw
Click to expand...
Click to collapse
!
Also, my battery temperature has dropped 4 to 5 degrees working with these settings ... These are personal settings ..... it is more than 15 days is up and it works perfectly on my tablet ....
gpu is at 400mhz with 1100mv for you information ....it's for that I have this score to nenamark2!
I tested too and its ok:
processor: 1.652 ghz for 1.3
1.600 ghz for 1.250v and 1.3v
1.552 ghz for 1.250
1500 ghz for 1.200
1400 ghz for 1.200......and i think your can 1.150v...no tested
......computing power as well as the benchmark machine improves significantly under voltage processor and not the other way .... I read on the internet that samsung would tend to increase the voltage of its processors ..... i do not know why
Before making my settings ... when I was surfing on wifi and the power was connected, the battery temperature ranged from 39 to 43 degree ... with these new parameters, the heating pad and earns much less 10 degrees less. now .... I'm a little less than 32 degree..... with much better performance!

micger21 said:
!
Also, my battery temperature has dropped 4 to 5 degrees working with these settings ... These are personal settings ..... it is more than 15 days is up and it works perfectly on my tablet ....
gpu is at 400mhz with 1100mv for you information ....it's for that I have this score to nenamark2!
I tested too and its ok:
processor: 1.652 ghz for 1.3
1.600 ghz for 1.250v and 1.3v
1.552 ghz for 1.250
1500 ghz for 1.200
1400 ghz for 1.200......and i think your can 1.150v...no tested
......computing power as well as the benchmark machine improves significantly under voltage processor and not the other way .... I read on the internet that samsung would tend to increase the voltage of its processors ..... i do not know why
Before making my settings ... when I was surfing on wifi and the power was connected, the battery temperature ranged from 39 to 43 degree ... with these new parameters, the heating pad and earns much less 10 degrees less. now .... I'm a little less than 32 degree..... with much better performance!
Click to expand...
Click to collapse
By the way, few questions,
Is there a way to set in Tegrak so that, I set 200Mhz or 500Mhz, and directly jump to 1.6Ghz+ ?
Maybe I'm a bit too analytic, using one of the Android system info, I use about ~10 to 20% of 800mhz/1000mhz/1400mhz, and I feel that those transitional process could make it 'sluggish' when processing demand is really required.
So perhaps, for a sake of 'smoothness' (but not using 'performance'-mode) I want to just use 200/500mhz and 1.6ghz+..
When CPU0 is set to 1.6ghz, the next lowest CPU1 is 1596mhz, (-4), and I can't change CPU2 and the rest..
Btw, I haven't treid 1.65, but I'll try it now and let you know

i noticed that sometimes my tab doesn't sleep. the minimum is just 200mhz causing my battery to drain faster than normal. and once it stayed 1.6 mhz. is it related to the OC kernel used? is there other kernels available for OC aside from EZYICS kernel?

Advice on battery life, Beans 14/lean kernel

Hey guys, I'm new to this forum but not Android Central. Anyways, I just recently switched to jelly beans build 14 w/lean kernel. For some reason my battery life is just terrible. I'm just barely making it through an 8 hour workday, and that's not even using it that much. I was wondering if you guys had any tips for good battery life on this ROM/Kernel combo. I do have set cpu installed and running but I'm only Overclocked to 1.6 and undervolting by 50 mv. I also have a save battery life profile that drops it down to 1026 when the screen is off, it's charging, or battery is below 40%. Can you guys give me advice on settings to use to save battery life? I really like this ROM and kernel but I'm getting such terrible battery life. I think it's probably more user error than anything but maybe you guys could provide some tips.
Thanks in advance.
Nick
sent from my Galaxy S3 on beans 14 via tapatalk 2

How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
http://rootzwiki.com/topic/31329-ke...nimalistic-kernel/page__st__1410#entry1042976
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!

nicholi2789 said:
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
Click to expand...
Click to collapse
I actually have my voltages set to exactly what Imoseyon has listed for the nominal cpu. As far as my screen off, I honestly just picked a low number and since I don't see lag I keep it there haha in addition, I use interactive governor which scales up the cpu once the screen comes on so it balances out either way.
To check which cpu type you have, do this. Details on what the cpu differences are included in the link as well. Matching your cpu type and adjusting your voltages may help extend your battery life but some say it is marginal.
No, your radio actually stays the same unless you manually flash a different one. I should also ask, what else do you have enabled? For example, in Maps/Settings, do you have everything disabled except "Enable Location History"?

{
"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"
}
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2

nicholi2789 said:
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Click to expand...
Click to collapse
Well it's under Location Settings but if you have Maps frozen until needed then it's an unnecessary step. You have done even more than I do or suggest haha I haven't frozen anything.
What would you say you're seeing as your average screen on time?
Sent from my SCH-I535 using xda app-developers app

Oh average screen on time is probably around 2.5 to 3 hours or so. Nothing crazy. I just wanna get my battery life back to before, where basically I could leave home fully charged and work a 10-12 hour day and come home with around 30% or so battery life. That's good enough for me.
So about these recommended voltages. I have the "fast" processor, should I just st the voltages for what he recommends? Are those recommended for bet battery life or best performance? I want to undervolt as much as possible without creating an unstable system or causing damage.
And can you help me understand the governor settings, my understanding is that "ondemand" activate both cores when needed, and interactivex is all the time? Is that roughly correct?
sent from my Galaxy S3 on beans 14 via tapatalk 2

Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!

nicholi2789 said:
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
Click to expand...
Click to collapse
Yea flashing kernels and roms is very addicting. Since you have a fast cpu, you can actually UV much lower than I can with my nominal cpu. You can set your voltages to match Imoseyon's table and you'll be fine or maybe try lower. I know from experience that I can't UV lower than 900 mv without my phone immediately locking up lol You can even hold off on setting voltages at boot if you want to get a feel for performance while UV'ed.
I can't really speak on OC vs. regular clock battery life, I keep mine OC'ed at 1.62 ghz so I'd notice minor drops in battery life compared to say 1.8 ghz. I don't even have much need for that since its fast enough to me as is. I haven't noticed too much of a hit on battery, I still range between 2.5-4 hours screen on pending if I'm on LTE or wifi during that charge.
Also, if you want to try your hand at really digging into kernel settings then you should also check out the the Team Kernelizer's thread for KT747 kernel. Personally, I use LeanKernel cuz it works really good for me so I applied some settings from there but not everything was applicable. This thread has some really knowledgeable people in it. Definitely give KT747 a look, or any other kernel for that matter, and see which ones you like the best.

Yeah i think i may have had a bad battery. I checked and I know my phone is deep sleeping, but since adjusting my voltages and settings last night it'd definetely improving. I have my voltages set to 25mv under what is recommended on that chart down to 1.4 the in the lower clock settings o have it exactly at the recommended settings. Seems to work okay. I have set on boot enabled but i also have the stock voltage settings on my SD Just in case of a boot loop.
sent from my Galaxy S3 on beans 14 via tapatalk 2

Does anyone have any suggestions? I really like this ROM and would prefer to keep it if possible but this battery life is terrible. Ant ideas on some measures I could take to try and improve it a bit?
I wiped cache partitions, davlik cache, and did factory reset before installing. I even do them twice just to be sure.
Would maybe wiping and re flashing the Rom help? I'm totally stumped here.
sent from my Galaxy S3 on beans 14 via tapatalk 2

I don't understand. I used cpu spy and i know phone is deep sleeping. I have set CPU to drop the clock speed when screens off.
Why the heck is it using so much battery? I'm dropping about 6-7% battery at idle. Somebody shed some insight.
sent from my Galaxy S3 on beans 14 via tapatalk 2