yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: KT747 KTweaker: share and discuss your setting

You should try my settings I posted last page, Those settings have been fantastic for me on AOSP. if you are on a touchwiz rom i don't know if it will be good for you. but seriously try my settings, they work fantastically for me.

My settings are even more conservative but I never feel like i need more performance at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Re: KT747 KTweaker: share and discuss your setting

You will need like a 8500mAh battery to get 8hrs of screen time. The closest I have ever come across was 5:30hrs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Re: KT747 KTweaker: share and discuss your setting

There's no way that is with a 2100 mAh battery. You also would have to be underclocked and have the lowest screen brightness with data turned off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
I am running the same settings and cannot attest to the battery life yet (as I need more time), but performance is not a zero bit laggy. While undoubtedly a step or two behind what I was running with ROW, I can live with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JAG50:
Re: KT747 KTweaker: share and discuss your setting

I would like to make a proposal. We see many folks post photos about their awesome battery life. What if we make it a rule to have them also upload their settings file? In this manner we can compare results and tweak the best settings that work the best for most people. Just a suggestion...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: KT747 KTweaker: share and discuss your setting

Good idea, but the trouble is there are lots of variables that affect battery life.

Heck, even the batteries are different for per device performance...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747 KTweaker: share and discuss your setting

Underclocked doesn't save battery, you just need to find the right voltages and settings for your phone. If you take the time to check the previous post I was referring to you will see I'm running 96-2106mhz. My data wasn't off but I clearly stated I was on WiFi for the whole time. My brightness was a bit higher the minimum and yes it is with a brand new stock 2100mah battery. With the stock battery I got with my 1747 I couldn't get over 2-3hrs of screen time so I got a new one this weekend and it looks like not all batteries are the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747 KTweaker: share and discuss your setting

If you look to my previous you'll see that I shared my settings and even the KT weaker backup file ;) . feel free to try it but be careful, not many i747 loves my undervolting values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747 KTweaker: share and discuss your setting

All right, I'm tired of the debate about whether or not it is possible to get 8hrs screen time with a stock battery. If you don't believe me fine but I don't see why I would have post this if it wasn't true? I clearly stated I was on wifi. Ill add that I wasn't on airplane mode and that my brightness was a bit above the minimum. I probably couldn't get 8hrs if on 4g all day with Bluetooth on, GPS and Google maps.

So now you know it is possible to get 8hrs on stock battery, it just depends on how you use your phone. Personally I never activated Google now cause the last time I did I had some ****ty battery life even if I did use it and I never use it so.

Can we get back to talking about and sharing settings now. I seriously don't care if you don't believe it :D it is just the results of 8 months of tweaking my settings and my voltage to find the sweet spot for MY i747, even if I shared my settings, it doesn't mean your device is exactly the same as mine, so you'll have to find what works best for yours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Re: KT747 KTweaker: share and discuss your setting

Does anyone know why my battery would drain so fast on idle and nothing running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747 KTweaker: share and discuss your setting

Something is keeping it from going into deepsleep. Use better battery stats to find out what it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JAG50:
Re: KT747 KTweaker: share and discuss your setting

liltitiz,

Thanks. I did notice that your running an ASOP ROM. I'm on TW (chemistry 6). Question, any changes to i/o scheduler?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747 KTweaker: share and discuss your setting

No changes to I/o scheduler settings, theyre pretty much alright the way they are. With all the tweaking and testing, I found out that scheduler doesn't affect battery life as much as governor. Which makes sense since it just the order tasks are assigned to your CPU that changes a little. The scheduler will help reduce latency on your phone if you see any with zen, try noop it'll probably fix it.on another hand, row is more aggressive and I've seen I very small effect on battery life with it, but it is like 30 -40 minutes less of screen time by charge. So if you have better performance with row, don't worry about battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JAG50:
Re: KT747 KTweaker: share and discuss your setting

liltitiz,

I've read the entire thread twice and there has been a lot of debate regarding settings for up/down thresholds. I was having latency and mw 86 suggested I increase the up/down threshold values. How does lowering then help reduce latency and increase battery life? Your answer will help a lot of us intermediate users.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747 KTweaker: share and discuss your setting

Up threshold is the amount of usage(as a % of the max CPU usage) your CPU will need to reach before it steps to a higher frequencies. So the lower you set it, the better performance you'll get because your CPU will scale up faster for less usage. Set it too low and your CPU will scale up uselessly and eat more battery, set it too high and your phone may overheat and start being laggy. So set it with what works best for you.

Down threshold is basically the same, except it is the amount of usage your CPU need to reach before it scales down to a lower frequency once is done processing the task. The lower you set it, better performance but also eats up more battery since your CPU won't scale down appropriately according to the task left to process. Set it too high and you CPU will scale down too soon and your CPU will take more time to process a task that would've take a fraction of the time at a higher frequency. So it will also eat more battery, may overheat and cause laggyness.

Up and down hotplugging thresholds work the same as regular threshold, but they set the amount of usage your CPU needs to reach before it turns on or off the second core.

Set the up hot plugging threshold higher than your up threshold and your CPU will reach your max freq before turning the second core on.

Set the down hot plug threshold lower than your down threshold and your CPU will reach the lower freq before turning off the second core.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JAG50:
Re: KT747 KTweaker: share and discuss your setting

liltitiz,

Outstanding! You described all the processes in layman's terms. This info will help many of us. We're promoting you to executive director for training!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Re: KT747 KTweaker: share and discuss your setting

I was referring to your down threshold was set above up threshold and it wont work that way. The value i encouraged you to increase is sample rate as you mentioned a stuttery performance an could of been from cpu dropping down when still plenty of load to take care of and too low a smple rate can cause that erratic behavior.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JAG50:
Re: KT747: share and discuss your settings

mw86,

Affirmative. Since I wasn't sure what you were talking about, I misunderstood your instructions. liltitiz provided us with a very thorough explanation and we're all good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Re: KT747: share and discuss your settings

The only thing I've changed is I'm now using lux for my screen brightness tool
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Same for me noop drains my battery but it seems to make my phone snappier than sio. So I always switch between these two depending on what I need :p good luck with your UV!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Killua_22:
I have a question liltitiz. What do you have your "Set options on boot" to?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I have mine ser to 5sec delay.. Figured if I undervolt so bad that the 5 seconds was enough time to go in there and fix it.. Though now that I think about it I should probably increase it a bit till I know I'm done with my under voting tests
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Killua_22:
Is there any difference between on boot and having it on a 5 second delay after you are positive that your volt values are good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
If your settings are stable, there is no reason to delay it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you're trying new lower voltage it is better to set a delay so you won't be stuck if your phone doesn't like your voltage but like waiter said if your setting are stable there is no need for a delay
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Killua_22:
Thanks for the replies guys, if I had any "thanks" left they would've gone your way.

Btw, The settings I'm using currently are the ones you first put up, except that I'm using Sio instead. I'll post up some pictures in a day or so after the phone settles.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tduquefjc:
I am having good luck with lulzactive/bfq... Setting bfq i/o scheduler slice_ idle to "1".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EndlessBliss:
Adaptive governor

Anyone else here using adaptive, and care to share their choice of scheduler and other settings? This seems to be the only governor that keeps the CPU at lower frequencies until necessary. I don't know why it's not more popular... :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I use Ktoon and noop, it runs so good I'm afraid of trying something else
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Try this. If sio doesnt work for y ou try another scheduler but thèse governor settings should keep your clock speed really Löw unless necessary

96Mhz-2106Mhz

Screen off profile: 486MHz

Scheduler: SIO

Governor: Pegasusq

Kernel: kt747 9/13

Rom: AOKP 9/13

pegasusQ settings:

cpu down rate:20

cpu up rate:10

down differential:10

dvfs debug:0

freq for responsiveness:500000

freq step:9

hotplug 1_1:500000

hotplug 2_0:200000

hotplug 2_1:500000

ignore nice load:0

io is busy:0

max cpu clock:0

min cpu lock:0

sampling down factor:4

sampling rate:10000

sampling rate min:10000

up nr cpus:1

up treshold:90

up treshold at min freq:70
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Anyone have any suggestions for i/o scheduler tweaks now that we've got i/o scheduler configuration available?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
i didnt try anything yet I'm still learnin how scheduler works :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I tried adjusting deadline and I found these settings to optimize latency

I run deadline with pegasusq 96-2106mhz, undervolted and 486mhz screen off. Best setting for battery life for my phone :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shugga101:
Testing out both yours and the post above mine to see if i notice improvements and better battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I thought pegasusq was optimized for quad core devices
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
It is optimized for multi core.

This guide is useful: http://xdaforums.com/showpost.php?p=24233103&postcount=3

Check it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shugga101:
Well I noticed an improvement and I messed with my undervolting as well as overclocking. I had many reboots cause my phone doesn't like to uv that much but I found a low uv setting that works. Thanks for the information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Longcat14:
Many thanks to OP, your values work GREAT on my phone, and my battery life increased quite a bit.

No harsh effects.. wonder if I can lower it more... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
What's the best io scheduler for performance and best one for battery life? Or do they depend on which governor your using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Re: KT747: share and discuss your settings

I thanked the post and thought it was well written. Lilitz has been at this longer than we have had a team together. This thread came out soon after GS3 released. I believe i have a link to here in our 2nd post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: KT747: share and discuss your settings

I'm running the minimum sampling rate with very high thresholds all around, things have been fantastic for me.

I don't know how often you guys use cool tools but cool tools will show you exactly what your chip is running at during every task. For example me using Swype here with high up thresholds my chip doesn't go past 384 mhz whereas before it would jump to the highest, unnecessarily.

Point is high up thresholds with quick sampling rate to me seems to me to be the best combination of scaling for battery life and performance.

Maybe Mr. Lillitiz can confirm?

Edit: depending on the app I'm typing in sometimes i can get it to stay at either 144 or 192mhz. It's working great. My under volting is causing occasional graphics/text errors but I'm willing to deal with it.

Oh and a comment about Wi-Fi, sometimes depending on the router I've heard that the Wi-Fi can keep pinging back and forth keeping the phone awake. I read about it in the kt747 thread awhile back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747: share and discuss your settings

Since this thread is starting to become way bigger than I thought it would, I decided to make a real op and a useful second post with links and infos. Go take a look!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Re: KT747: share and discuss your settings

Nice work Lilitz, trying to keep up the same work in Kernelizer thread, its good to see the the same devotion to knowlege and innovation through research, experience and development.

---------- Post added 12th February 2013 at 12:10 AM ---------- Previous post was 11th February 2013 at 11:54 PM ----------

I dont have issues at 10200 sample. I just am. Trying to stabalize undervolt more and prevent it from jumping up as quick when leys say a process loads cpu and for awhile a higher sample rate may react slower to sudden increases so i dont go right to max mhz even with high up thresholds. I use high up thresholds myself higher than Lilitz listed. Just as of recent since i had same opinion as you that low sample rate is good and high up thresholds but these cpus may be less comfortable with fast cpu speed and hotplug switching. Im using 75k, Lilitz a few posts back showed setup woth volts and is using 70k sample rate. I agree 10000 is good but it's worth seeing if letting cpu stay at a frequency just a little longer would keep it from driving up into max mhz. Im still using same up threshold. This way i see less core two on. Low sample rate i see it on more often because governor hits up threshold hotplug too often for me... thats with 99 upthreshold hotplug. I cant go higher without disabling hotplug altogether.

Overall low sample rate good, its easy to notice sometimes it doesn't makethe best decision because 10ms changes i mean one 10ms core two called to turn on next 10ms off and over and over sometimes which is not efficient and will not calculate as well when core two really was needed...

Noticed if your on 4.2 it needs a higher sample rate and under 4.2 lower is no prob. Ktoonsez recommends 45000. I may go back to 10200 too but its worth trying new things. Been a fan of cool tool forever. I use it on my phone all the time, its always running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juancaperez2000:
Re: KT747: share and discuss your settings

Excuse me liltitz just quick question about the settings that you share, those are more for battery savinga than performance right, also from where you get your new battery, thanks for sharing and ur support
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Re: KT747: share and discuss your settings

Awesome work on the OP liltitz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747: share and discuss your settings

Yep! The settings I shared are more for battery savings but so far I didn't have any problems with performance for GPS, gaming, streaming and camera. I got my battery from a store in Quebec city. www.futureshop.ca.

But you can find them on eBay and directly from Samsung's website.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: KT747: share and discuss your settings

If any of you think I should add other information or link in the op just hit me up in pm! :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Question for those of you who run your min freq at 96..

Am I the only one who sees higher cell standby drain at 96 vs 144/192 even 384?

Was home all day today where reception is great and noticed a little higher idle drain than usual...

Reception strong the whole time as you can see

Cell reception is at 15%, when its usually under %10.

I know 96 seems to be pretty popular so I'm just curious because I seem to get better results at 144.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
96 is fine on my i747 but yours may perform better at 144 or higher. Your voltages may influence this too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
You could call a voip phone like with your gmail phone and set a max and min frequency to 384, then 144, then 96 and leave it sitting there with the phone call going and see which eats battery quicker. I'm pretty sure there don't be much difference..

I imagine it'll be very similar. But if you've making long phone calls it may mange a difference.

The importance would be consistency in the tests
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Question: If the phone is not getting a strong cell signal and is always showing Yellow in the wireless radio power reading within the Battery menu, does that pretty much negate any Kernel power save settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
I'm ALWAYS in yellow at home and work and drop about 1% every 2 hours with data off with the screen off. Overnight while I'm asleep has me waking up excited to grab my phone just to see how little I lost overnight. Ktoonservative/noop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
My data/WiFi is always on at home. I was dropping 1.3% per hour overnight and it just seems like during the day with just data on I drop a hell of a lot faster just with the screen for short bursts. But I'm always in the yellow while at work and at my new house.

I'm running Ktoonservative/zen and have UV'd -75 across the board.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ayoking:
hey wat is the best governors for touchwiz rom...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
I don't run TW, but I feel that ktoonservative is the best governor. You should try it out! And if you do, be sure to delete the necessary file as directed in the KT747 OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ayoking:
please do know wat to delete please

---------- Post added at 09:33 PM ---------- Previous post was at 09:28 PM ----------

please can u help please .. i have 4.1.1 touchwiz rom .. dont know wat governor to use and the tweak,,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
http://xdaforums.com/showthread.php?p=99829

It is clearly stated in the op you are supposed to read before flashing this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Nobody can tell you what governors you should use. It depends on your device, usage and preference. If you want to learn how to tweak, take a look a the op of my thread. It can help you. If you don't know what you are doing, you shouldn't be tweaking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
phone kept restarting with those settings.. am i doing something wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Probably the voltage table. Up your voltages
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Start stock and drop 25mv on stock table before using the fancy undervolts. Maybe even 10mv. Some phones are near their lowest volts on stock. Checking chip quality can give you an idea though its not set in stone how any one cpu can behave. Using a terminal command it can see what has been labeled for the cpu: slow, nominal, fast. Slow needing more volts and less volts going up to fast. Slow may handle less of an overclock vs nominal (average) and fast labeled cpus.

http://xdaforums.com/showthread.php?p=36788330

If you follow the links there is even a nice good starting point for voltage before getting fancy listed for slow, nominal and fast labeled chips.

As i mentioned nothing is set in stone so a slow label chip could be superfast and undervolt good, you never know. Its more of a guideline to start you could say.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Try just the settings without my voltage table. If it keeps rebooting then you phone doesn't like the settings. Maybe your phone don't take 96mhz-2106mhz or You can try lowering the sampling rates and up thresholds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Thanks for the info :beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Thanks if you see Jcdominguez make sure to thank him, he posted it in Kernelizer thread. Hes a very helpful bro!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ayoking:
thanks man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
I'm also curious to know more on this subject... if it's normal to drain faster during the day when not connected to WiFi...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwalker0906:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Thanks, and why is this? Just because 3g/4g signal is not as efficient as wifi?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Takes tons of power to keep running a high frequency radio taking to towers through walls and hundreds of feet of air.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Makes sense!

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I have a question for those who are doing a lot of undervolting. Do you use Google Maps, Navigation or any other GPS app like Waze? When I undervolt these apps seem to be the ones giving me the most trouble. My phone can be running perfectly fine, but maps shows an insane amount of graphics glitches and navigation will always crash on me after a few minutes. Waze also shows lots of glitches.

I'm wondering if other people are experiencing this or am I one of the only ones using navigation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Certain apps, especially resource intensive ones will be more sensitive to voltage adjustments. I know a lot of people use Google now as a test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I understand that, but I have tried quite a few resource intensive apps, including Google Now, and had no issues until I got in my car and started using navigation. That is why I was specifically asking if other people have tried navigation apps while undervolting.