yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
U both fully wipe, both get by the same tower, both run same brightness, both have the same sync settings...both run the same apps?

If not, why are we comparing?

We both have mustangs, we both have the same fuel, (battery) but we drive differently. I'm heavy on the gas, you're not. I shift at different rpm's than u, I sit at idle longer than u....

There's too many variables to take into consideration when discussing battery.

Unless it's draining during idle, there's not much more people can do to help. Every device is different. Do u have a lot of wake locks? Are u on lte?

Toooooo many variables!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
With the settings I use I pull 4+ hours on a full 24 hour charge :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psloan:
Hey liltitiz,

I am trying your settings from a couple pages back. but I think these are a bit to much for me and my phone. My phone seems a bit laggy when pressing the back button for example. I think I should back off on some of the settings, but I am not sure which effect performance in this way. Could you suggest witch ones would be best to back off a bit?

Thanks.

--pat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Set boost_turn_on_2nd_core: to 1 instead of zero. Should fix it for you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I realize that even when using lil's settings, I will not be getting the same battery life as him as there are many other variables involved. However, he gets 5 hours of screen on time while I get 2 and a half at most. Even with those variables accounted, I feel that the difference should not be that big.

I never use GPS, hardly ever use data, brightness is controlled by Lux, wifi on for most of the day. Google Now is off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
App controlling brightness are a good way to eat up battery. Set the brightness manually, should help your battery life ;)

I rarely set my brightness higher than 50% unless I really need it

Never forget that your screen is the biggest battery consumer. No governor settings will change that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
so you don't recommend using the built in auto brightness? Hmm.. maybe that could make a difference for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Auto-brightness is the worst for your battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I usually average about 2.5 to 3 hours by the end of the day with about 50% left, seriously (no offense) but 5 hours of screen time is like looking at your phone for literally half the day lol.

Also in my experience it takes at least a cycle or two until you get the most out of your settings.

Also brightness is personal preference, but I leave mine at the lowest unless I'm outside, then I turn on auto. I feel like the lowest brightness setting is pretty bright, I even keep screen filter installed in case I want it darker than that. Maybe its just my 20/15 vision :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Im not really expecting to get 5 hours of screen on time. I just want it so I will have more than 5-10% battery left after the school day (6pm or so). As for the Lux thing, even at the max setting outdoors, I still have it at about half way brightness. It has not affected my battery life at all. When indoors, I have it below the stock lowest brightness setting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I would still try not using lux. You'll be surprised by how an app controlling brightness consume battery. Anyway it is not that hard to set it manually when you go outside
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I would not be able to use this phone at night without Lux or Screen Filter. Even at the lowest setting the screen is just way too bright in a dark room.

Lux can be set to only adjust on wake, or to full manual if you are worried about it consuming cpu time or constantly polling the sensor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you set it manually it is fine. But if you use auto-brightness, the constant use of the sensor consume battery like crazy.

Anyway! You know my opinion on auto-brightness, now back to kernel discussion :D thank you :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Does everyone use default min/max values? Starting to tinker with it more and curious how I should adjust it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I use 96/2106
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Thanks! On your sampling rate min I couldn't find your value. I got 60000 for the one above that. Did you make any changes to the one below it. Sorry for the questions. And thanks for your help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You can't change sampling rate min, it is just there to tell you the minimum sampling rate possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
New build up! Liltitz.... Your settings have given me 4+ hours of screen time. Best ever....can't wait to see if you change anything in ktoon's newest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Task's AOKP(3.13.2013) & KT747(3.14.2013)

Min/Max: 96-2106MHZ

Ktoonservative + Zen

Vibration strenght: 40

Screen off: 486mhz & noop

Touch Boosters: 1026MHz & 594MHz

Brightness: 50% max

Ktoonservative adjustements:

Battery_ctrl_batt_lvl_high: 30

Battery_ctrl_batt_lvl_low: 15

Battery_ctrl_disable_chrg: 1

Battery_ctrl_batt_lvl_high: 1512

Battery_ctrl_batt_lvl_low: 1026

Boost_2nd_core_on_button: 1

Boost_turn_on_2nd_core: 0 (if it feels laggy, change it to 1)

CPU_down_block_cycles: 0

Disable_hotpluging: 0

Disable_hotpluging_bt:0

Down_threshold:60

Down_threshold_hotplug:50

Freq_step:1

ignore_nice_load: 1

no_2nd_cpu_screen_off:1

Sampling_down_Factor: 5

Sampling_rate: 60 000

Sampling_rate_screen_off: 120 000

Up_threshold: 90

Up_threshold_hotplug: 95

use_yoyo_cpu_load:0

Zen adjustements

async_expire:2500

fifo_batch:1

sync_expire:300

Ktweaker backup

https://www.dropbox.com/s/hhqecqep0fdykpo/ktoon-zen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
Could you post txt file?

AOKP 4.2.2/kt747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I added the link in the post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Giving these settings a shot, see how it goes

edit: Damn you got one hell of a well made S3. First screen off with your settings and I had to batt pull to get life back to the device. used to be able to UV -50 but lately I haven't been able to reliably undervolt at all. Oh well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Did it enter the adjustments manually or did you use my backup file. Maybe your i747 just don't run 96mhz. Manually set up the ktoonservative and zen adjustments and use the min/max and voltage you know your phone can take
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnthomX:
Ouch, you have voltage up. Mine didn't like that. Is this for performance and battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Mostly batterylife but i never had any performance issue with those settings.

And yeah I raised the voltage for the backup I shared on drop box. The voltage I use (posted a few page back) usually don't play well with most of i747 except mine. You are better using your min/max MHz and your own voltage and input my ktoonsrvative and zen adjustments manually. I don't recommend using my backup :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Why am I not seeing a sampling_rate_screen_off? I have all the other options.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You're not on the latest kt747 that came out yesterday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Oh, that makes sense. I hadn't realized there was an update. Thanks! :thumbup:

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djtiko:
Liltitiz,

So like I said a couple of days ago I was going to try your settings and see what results I got.

Well it's simply amazing. I've never got such great battery life before. I'm on the 3.10 release with the settings you had posted up earlier only difference is that I had to increase my voltage a couple of steps.

I got 1 day and 15 hours of usage with 3 hours and 30 minutes of screen time. Before I would never make it pass 14 hours with barely 3 hours of screen time

I noticed there is a new release now with amazing results with no idle drain but I'm so happy with my results I'm not sure if I want to change it lol.

Thanks so much for your help dude :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Man i must have gotten a good battery because im easily getting 5 hours of screen time on my stock battery. Im curious what type of talk time people are getting with regular use. I personally dont use my phone as a phone as often as I should because I also have a work phone that I use instead.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloud9x:
I don't use my phone often enough for talk either, but I'd wager 30 minutes nets a loss of 5-10%?

5 hours of screen times seems like you'd have to have very little in terms of idle time. I think it's feasible to get 5-6 hours if you run the phone's screen from unplugging through and through.

Beyond that, I think it's very difficult to get past 3.5-4 hours through a whole 20-30 hours.

And for auto-brightness, use Lux Auto Brightness. Best money you'll spend on play store. You can set it to sample light every x seconds, or just on wake, and you can automatically link different brightness levels to different ambient LX readings. Very very useful!

edit: Actually, ought to be feasible to get 5 hours. I'm usually at 2.5h by the time I'm at 45-50%. But I'm on 2G/Wifi that whole time. LTE is a totally different story.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Alot of my data is over wifi. At 4.5h screen on right now with a little over 12h total since unplugging and 20% left.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Hey, liltitiz, do you use a battery saving app, or do you just rely on your kernel settings? I have the XDA version of DS Battery Saver, and I don't know if I'm being redundant by using it along with all those kernel tweaks. Sorry if you've already answered that. I've been following this thread for a while and don't remember seeing anything about it.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I dont use any other app since I don't like my WiFi and data being turned off when I turn of the screen but I don't think it is redundant, it can help save some battery. It's really up to your liking
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] luc.highwalker:
Question, and I apologize in advance if this is in the wrong thread.

But if my rom has a performance control app built into the system. Do I need the ktweaker app? Or are there options which are unique to ktweaker?

Sent from a galaxy far far away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Stick with ktweaker there's a lot that it does that performance control doesn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whod:
Definitely the best battery life I have seen on my phone after using liltitiz settings. Thank you so much!

I currently use Carbon nightly rom if anyone's curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ameanl:
great work

wow! thanks for the great indepth information on governors and schedulers. I haven't seen these explanations before. Keep up the good work.

Now what I use as my ROM is Slimbean and BMS as my Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Holy crap, so jealous of you guys :| Im using liltitiz latest settings, currently at 67% after 2hr 45min, 1hr 22min screen on time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I've learned almost all phones react differently to kernel settings. I'm using liltitiz settings as a base and tweaking different things to try to find my phone's sweet spot.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whod:
I believe partial wakelocks are the reason your battery may drain quickly when your screen is off. So removing these wakelocks can have a big impact on battery life. I like using Greenify to hibernate a few apps that cause wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I looked at a wakelocks guide but the only wakelock my phone suffers from is an AudioOut one. I've also heard that apps like facebook and Maps cause wakelocks, so I might look for alternatives to those
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
i hope ktoonez implement all the missing option soon in 3.4 kernel :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
How's everyone's batt life on the new 3.4? I haven't made the jump myself to a 3.4 based rom and kernel because of all the issues I've read about. You guys getting any reboots, glitches, ect?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I was having issues yesterday, but since upping my voltages slightly, I haven't had an issue all day.

I currently have 30 mins screen time and 7:20 on battery with 79% remaining with stock battery on 3g with variable signal and scanning for about an hour. Running ktoonservative / zen with basically the same setting kt was using when he was on zen. Rootbox rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Hey liltitiz, what settings are you using on the new 3.4 kernel? I'm using PAC-Man ROM with it and I'm noticing a pretty big drain on my battery life as opposed to before. Your settings proved to make a better balance of performance and battery life before, so hopefully you'll be able to help me out again. Thanks in advance, bro!

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Question for those of you who get 3+ hrs of screen on time: do you use your phone as an mp3 player? DO you listen to music throughout the day?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
boost_2nd_core_on_button:1

boost_cpu:1026

boost:gpu:0

boost_hold_cycles:0

boost_turn_on_2nd_core:1

:cpu_down_block_cycles:0

down_threshold:60

down_threshold_hotplug:50

freq_step:2

ignore_nice_load:1

no_2nd_cpu_screen_off:1

sampling_down_factor:4

Sampling_rate:60000

SAmpling_rate_screen_off:120000 ( as ktoonsez stated, if you experience a higher battery drain when screen is off, set it to 90000 )

up_threshold:80

up_threshold_hotplug:95

You will have to open ktweaker on each reboot and press OK when ktweaker asks you if you wish to apply governor adjustments. It only happens because of the down threshold not being applied on boot due to the order in which the threshold are being set. If you don't do it, your phone will act really weird :p

So far I got good battery life with these but I feel like my battery drain faster than prior linux 3.4 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yeah, I use my phone as a mp3 player, but when I do, I raise the maximum freq for screen off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
How does that change things?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Thanks! I'll give those a try. You're still using ktoonservative and zen right?

It'll help prevent your music from skipping and/or stopping while the screen is off. I figured that one out the hard way, haha.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Well, I have no issues with music stopping or skipping. However, whenever I play music I get huge battery drains in the form of audioout_2 partial wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bboy2143:
Hey lilitz what type of battery are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Are you using ktoonservative with no_2nd_cpu_screen_off set to 1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Stock battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I'm trying noop and row to see if It will help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
That is normal I think and should not be related. Its a wake lock that occurs every time sound is played on the device like key touch sounds, lock screen and more. Please read about it here. http://xdaforums.com/showthread.php?p=30088906 Maybe see how much options are checked in settings>sounds and settings>language and input (perhaps disable key pad sounds)

I just mentioned in att KT kernel thread so I figured I could supply you the same info ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
I'm trying to figure out why your latest setup isn't default for ktoonservative liltitiz. Running very smooth and better battery then usual so far. Loving it

Edit: Actually, I'm back to 3.0 battery life, if not slightly better.

Edit edit: I've NEVER EVER gotten 1hr30m screen time with thirty minutes of music playing while screen off and been at 75%.

You're on to something here bro...

Edit edit edit: 19 min later with screen on and I'm at 74%. Jesus Christ!

Edit edit edit edit :p 2h40m and at 59%...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheDriller:
Couple of good alternatives are Friendcaster in place of Facebook. Doesn't have the crappy wake locks. And I use NavFree USA its free on the play store, uses NO cellular data unless you do a Google search because the map data is stored on your phone and never runs in the background

7000 lemons? wtf!?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I just added PegasusQ and Row tunables explanation in the second post. I tought it coulb be something interesting for some of you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I'll be playing with pegasusq for a while, see where it goes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yes, I am.

I already have all touch sounds off, didnt change a single thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
Is this set up still running smooth for you? So, you are running Koonservative? What scheduler are you using? AND are you still using the settings that liltitiz provided? Have you tweaked them? Thanks in advance.... :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
The wake lock usually just runs as long as you played audio... If you play music and stop it and let phone rest does audio_2 wake lock continue to accrue time in BBS? If not then you don't have a wake lock. A wake lock being the audio-out process didn't stop and kept phone from sleeping. We can have a lot of time on audio out wake lock and its not a bad thing, it is only if it doesn't stop while idle. If you played audio for 30min an audio out of 30-40min is appropriate, its when that says 2hours and you only played music for a few min that you should worry. Touch sounds are only one aspect. Any sound ever produced on our phone is shown in this wake lock...

If the advice has not helped then somebody else may have some input as this is all I can really say on Audio_out wake lock. If you go to that thread it is a more appropriate location for your question where perhaps TJ Bender or another user in that thread could be of more assistance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sguerra923:
Just out of curiosity what are you guys running in terms of Min/Max? And any recommendations in terms of battery life? I have my min set at 96 does that drain or help battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Every phones different for me I get better battery life with 144 min than 96
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If audio out wake lock really consume a lot of battery while screen is off, it coulb be because of your 2nd CPU staying off.

My girlfriend had the same issue with her galaxy nexus, I made profile so her CPU would always run on one core while screen is off and music played well with no sound glitches but there was a huge battery drain, so I added another profile to only activate 2nd core when playing music and it fixed the battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Is that something via script or kernel? Perhaps you can bring this concept to KT and see if he could implement such a function too? Very awesome Lilitz ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I took the easy way :p all i needed was setcpu hahaha. I created a profile to hot plug while screen is off and also reduce maximum freq. I then added another profile on top of it that switch to a non-hotplugging governor when using double twist.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Is this the case even if we set it to set on boot? Is it a bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yes it will happen even if set on boot. It happens because my down threshold is higher than the stock up threshold. The thresholds get applied in the order they appear in ktweaker and it is illegal to set a higher down threshold than the up threshold so my down threshold don't get set on boot. That is why you have to open ktweaker and press OK when it asks to apply governor adjustment. This way, down threshold gets set after the up threshold and my value is applied because it is no longer an higher value than the up threshold.

I hope this makes sense to you :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
M'y new voltage table for the new steps is almost finished :D took me a lot of test to get it right :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Ktoonservative Adjustments:

boost_2nd_core_on_button:1

boost_cpu:1026

boost:gpu:0

boost_hold_cycles:0

boost_turn_on_2nd_core:1

cpu_down_block_cycles:0

down_threshold:60

down_threshold_hotplug:50

freq_step:1

ignore_nice_load:1

no_2nd_cpu_screen_off:1

sampling_down_factor:3

Sampling_rate:60000

SAmpling_rate_screen_off:160000 ( as ktoonsez stated, if you experience a higher battery drain when screen is off, set it to 90000 )

up_threshold:80

up_threshold_hotplug:90

I did all the undervoltage testing with the adjustments above. I started by undervolting 81-135MHz, Tested it with SuperPI to see if i could calculate PI with 64K digits and adjusted the voltage until I got a sucessful run. Then i ran stabilityTest for like 10-15minutes. After that, I added 10mV to the first stable voltage i got and then I upped the max frequency by one step and repeated the test above till i got everything stable. I found out that my CPU won't do any better than 81-1890MHz so no 2106MHZ for me :(.

I'm a little suspicious about the amount of undervoltage my CPU can take if any of you could try my voltages for the lower freqs and give me some feedback about it, I would appreciate it. So here it is:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I might have time to try tweaking these more this weekend and try to oc, but these are what I have been using for months, including the latest 3.4 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
My phone was always weird, I can undervolt way more on the higher frequencies compared to the low. Perhaps the new cm commit (see kt747 thread) will give me more stability on the lower frequencies. I'll have to play with it and see
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Maybe I need to post this on the official thread for the kernel, but just wanna see if anyone else is having this issue...

On the latest 3.0 linux ktoons kernel, when I get to these settings:

Battery_ctrl_batt_lvl_high:

Battery_ctrl_batt_lvl_low:

Regardless of what I put there, as soon as I back out of that menu they both reset to 0. Everything else sticks, though.