yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mcluvin1065:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Guys my battery life on tpr isnt that good with my usual set up for fre3...any ideas? I dont have app wavelocks or anything... Speed is great though...
[Sprint Samsung Galaxy S III] chrischoi:
What did you do for a fix? I ended up upping all the voltages.

Def not the port because it was a bluetooth headset.
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Sorry for confusion, I had posted an off topic question but figured it out. Will change it to avoid more confusion.

Did u use Pberges volt settings or just up them across the board?
[Sprint Samsung Galaxy S III] pberge:
I wanted to add a little more info about my audio problem for anyone in the same situation.

I only encountered the issue when I enabled an equalizer using DSP manager. It didn't matter what the setting was, just toggling the equalizer enable switch seemed to cause it. My primary app for music was Spotify, both streaming and locally cached content behaved the same.

The problem was more than just some crackling for me. It was painfully loud squealing and popping that made me rip my headphones out of my ears as fast as I could. As I upped the voltages at the lower clock speeds the problem slowly went away. The loud squeals turned into muffled popping or clicking and eventually went away completely when I got to around 950mv.

The kernel i'm testing out now uses 800mv at 192 and 384 and I have not had a single audio glitch yet. :confused:
[Sprint Samsung Galaxy S III] Dhyneland:
What is the best setup for CM10.1 for balance between performance and battery life, leaning more towards performance?

I applied both the safe UV as well as balanced performance/battery life "Ktoonservative 50 30 85 80 docnas tunables" from first page and my device seems pretty laggy now. If I enable yoyo with 1 it seems to make it a little better. But curious as to what others on CM are running.

Thanks!
[Sprint Samsung Galaxy S III] beyeond:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I just switched to that I/o and my top value is way diff than yours...?
[Sprint Samsung Galaxy S III] thomasmatt25:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Which font is that? I like!
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I am using one of the tweaked set ups from OP
[Sprint Samsung Galaxy S III] MorphiousGX:
Random Question

I've been following this for a while. Is it safe to assume that this could work with Verizon's version of the phone using the Kernel? I've been running it so far and like it. But want to try the tweaks.
[Sprint Samsung Galaxy S III] beyeond:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

http://db.tt/IYDwlNTX
[Sprint Samsung Galaxy S III] jcdominguez:
[Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I have a SIII on Verizon and yes these tweaks work equally compared to sprint. As a team legal disclaimer, we urge anyone to always have a latest nandroid backup and try anything and everything at his or her own doing.... But yes I have an SIII with vzw, spr, and att and these work.

Obviously if you have issues you can report back and notify us.

_____________

Device: Sprint Galaxy S3

ROMS: Jellybam, Chemistry

Kernel: Ktoonz, Anthrax

"Extending android battery life through research, testing, and calibration."

Proud contributor and official kernel scientist for Team Kernelizers!
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Never thought to watch the other carriers forum

Goin nuts on this gs3

​
[Sprint Samsung Galaxy S III] decimalman:
I know I'm showing up waaaaay late, but I've been doing some investigating based on some of what you guys have been discussing. Some of it might be of some interest.

On voltage:

Most (all?) custom kernels are undervolted by default, even though the default voltage tables are basically stock. In the stock source, the voltage tables for certain CPUIDs (some, but maybe not all S3s?) are adjusted after-the-fact so that all frequencies run at 1150 mV or higher. All the kernel code I've seen either disables or circumvents this adjustment, meaning that by default most lower frequencies run at lower voltage than stock. If you don't want to look up the defaults, this means that 384 MHz is undervolted 225 mV compared to stock, and 96 MHz is effectively undervolted 300 mV :eek:. This is probably the reason that so many devices aren't "compatible" with KT747.

Also, if anyone remembers the 700 mV thing, there's a quirk in KT747 (and most other kernels) where upper frequencies always run at 1050 mV or higher, which is why if your device is stable at 1050 mV you can set the voltages to 700 mV and it won't affect anything.

On entropy:

I set up a counter in my pet-project kernel to track entropy pool depletions. I discovered what Seeder & CrossBreeder users knew already: with the default settings, the entropy pool is often completely emptied during regular use. However, there is a parameter (write_wakeup_threshold) that determines when the kernel will wake up qrngd to refill the entropy pool from the S3's hardware random number generator. The S3's hardware random number generator turns out to be pretty fast, and is more than capable of keeping up with everyday usage. Once write_wakeup_threshold is increased to as little as 256, qnrgd can keep up just fine, and the entropy pool never depletes. Effectively, increasing write_wakeup_threshold accomplishes the same goal as Seeder & CrossBreeder, but without using much CPU or draining battery excessively.

I also adapted erandom (frandom's faster, unseeded equivalent) so I could switch /dev/urandom between urandom and erandom on-the-fly. erandom is much faster than urandom (45 MB/s vs. 3 MB/s), but as far as I can tell that doesn't translate into increased performance. Even 3 MB/s of random data is a lot--the only way I can think of to use it all would be securely wiping hard drives, so I didn't expect that urandom's bottleneck was causing any performance issues.

Benchmarks don't show any improvement in performance (which didn't surprise me at all). I'm not particularly sensitive to lag, so if either of the changes I made had any effect, I didn't notice. Anyone have any ideas how I can test (or better yet, measure) the effects that a faster entropy source will have on everyday performance?
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I am by no means an expert but had a feeling something along these lines was going on. Thanks so much for the write up. Great work. Keep it up.
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I've been toying around with Zen I/o scheduler, and after a few minor tweaks and running it for a few days I've come to realize (what's already been said and what I've read) that Zen is essentially noop with the ability to make some tweaks. I have been getting 24hrs plus with light usage. The problem occurs with moderate to heavy, while trying to download something, stream audio or video, load webpages with a lot on them, or play cpu intensive games, this thing sucks down battery like a 6 year old on a milk shake (I like comparisons). Battery drain was abnormally high while performing those functions using Zen.

I would rate this I/o scheduler a bit different than the others, although it is on par with noop or deadline it just does very poorly with heavy loads (lol). Noop didn't see nearly as much drain as deadline or Zen and I felt I got better battery with noop. IMO, I wouldn't recommend this scheduler and instead i recommend noop or even deadline, noop being the better choice of the two.

Goin nuts on this gs3

​
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Thanks for always testing and sharing the knowledge. Been wanting to know what was up with zen.
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

If I were to have any recommendations it would be row for performance, bfq for balanced, and noop for battery life.

While testing row scheduler with suppressed values like mw86 showed, I noticed similar results as the above described with Zen minus lag and stutter, my next test is elevated numbers for row scheduler, still standing by my previously posted (second OP) settings for row, at least until this testing is over.

Goin nuts on this gs3

​
[Sprint Samsung Galaxy S III] MorphiousGX:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Thanks. That's what I thought. I have been experimenting with these tweaks on my phone following the OP. But I keep running into the issue of I/O scheduler settings not holding.

Defaults for all schedulers hold fine, but if I adjust, I find that I have to run Tweaker again.

Not quite sure why the modified scheduler values don't hold
[Sprint Samsung Galaxy S III] styles420:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

That quirk sounds like an issue with the circumvention not working for the higher frequencies... I wonder if there would be any benefit to fixing it to work completely, or if we're better off not being able to undervolt those frequencies further (given that some phones are already incompatible as it is)
[Sprint Samsung Galaxy S III] daniel4653:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Anyone running goodness 8.0.3 do not delete or rename any of the files in init.d. I tested it out and experienced horrible lag.
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Has anyone try to delete mediaserver yet from bin? I haven't had time to test it yet
[Sprint Samsung Galaxy S III] DirtyShroomz:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I started playing with the voltages due to the audio issues I was having and i upped all the voltages under 950 to 950 as well as set min to 192 and audio issues disappeared. The cracking, popping, crackling, etc
[Sprint Samsung Galaxy S III] jcdominguez:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Got bootloop. Thank you backup.
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Nice. Sounds similar to Pberges shich are working great for me with a few minor min/max adjustments. I think a few r working on testing this setup to iron out a baseline for those with the issue for op maybe. This is good data point.
[Sprint Samsung Galaxy S III] beyeond:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Have you guys tried agats kernel? It also have the ktoonservative governor.. comes overcooked at 1.8 and my settings stick. So far so good using ktoon/noop with all other settings default.
[Sprint Samsung Galaxy S III] daniel4653:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Yeah I have used agats kernel since I had an epic touch. Its a good kernel :)
[Sprint Samsung Galaxy S III] decimalman:
The quirk is separate from the minimum voltage adjustment. The stock Vmin adjustment happens while initializing (without disabling it, all frequencies would show at least 1150 mV but could still adjust below that), where the quirk happens specifically when setting frequency past 1080 MHz. The quirk is the result of an extra check that ktoonsez added. I'll have to PM him and ask what the motivation for it was, since my phone is completely stable without it, even with voltages dropped below 1050 mV.

There's probably little to be gained from removing the quirk. In all likelihood, only a few frequencies will be stable with their voltage reduced below 1050 mV--you need to undervolt more than 75 mV before the quirk affects a single frequency. On the other hand, since the quirk doesn't have any effect with the default voltages, removing it won't break compatibility.

Update: I let ktoonsez know about it, and he made a change that eliminates the quirk.
[Sprint Samsung Galaxy S III] Ragnar:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

FYI Ktoonsez just dropped new kernel.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] Flint420:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Adds some new tuneables too. Can't wait to see you guys use these to make our phones even better.
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Anyone running it? Curious to see the changes to row, I'll flash it in a few days, testing row with those higher settings right now,

Goin nuts on this gs3

​
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Odd thing I noticed last night and I just thought of it while downloading a Rom on Wi-Fi with Zen as my scheduler it took 3 hours, and that is outrageous for my internet speed. I thought maybe it was high traffic time in the neighborhood but tonight I downloaded something and remembered my experience but I'm running row now, so I downloaded it with row and this file I downloaded took about 3 minutes, I changed schedulers to bfq and duplicated the download test and it took 30 seconds less than with row. Interesting, I wonder if the memory handling and cpu work by the scheduler has anything to do with downloads, because as it's downloading it has to put the incoming files somewhere,

Goin nuts on this gs3

​
[Sprint Samsung Galaxy S III] mw86:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Thats why i stopped using Zen after having network download and copy and paste issues. Row working good for me. Bud im trying my quantums at 250 and 225 for the other one with no issues and the rest stock. Ill try the 25 read idle again later on, i tried 30 and it seemd to have less consistency on speeds.

---------- Post added at 03:00 AM ---------- Previous post was at 02:45 AM ----------

Nice write up Decimalman. The voltage protection I pointed out in our previous conversations seems to be true for me and just past few days of testing. If i drop 100mv-150mv but cap at 1026mhz it seems to stabalize but seems better to match a few voltages near the bottom like 96-486 stock is same mv, it wouldn't hurt to use whatever works on 486 on 96mhz or higher as it makes it more stable switching from low to high frequency. So between what you discussed above and also the scaling of mhz with voltage ultimately determines how stable it will be. We may be better guys using a higher sample rate as it wont destabilize switching from low to high frequency to fast.

Ktoonsez recommends for 4.2+ android builds as is the cpu calculation has improved vs initial kernel release and the best bet is to use about 45k sample rate. This is needed for 4.2 because of previous noticed jumping of frequency and hotplug status unnecessarily. After using 4.2 builds and kt747 myself I came to the same conclusion on the sample rate. Disable yoyo load calculation now and use the higher sample rate. Also on 4.2 use for hotplug up and up threshold use upper 50-60 range values so it doesnt feel laggy.

Builds under 4.2 could probably do fine using a higher sample rate to prevent cpu from scaling more than necessary in a moment of sudden cpu load. Sample rates over 50 could seem to not drop or rise to load as fast as one may prefer.

The new kernel update is out and row and Ktoonservative have improvements as well as conservative gov. Hotplug on screen off and on independently and an option to have dual core always on. Ktoonsez suggestion in the kernel thread is great and what I would recommend too. Screen off core two off and screen on core two on during touch events (like touch boost).
[Sprint Samsung Galaxy S III] willyumlu:
hey!

i have a couple questions

does undervolting help conserve more battery than JD? and if so, does the OP undervolt chart still the most recent?

and also i followed the suggestion to get lux, but i was wondering if anyone wants to share some of their settings? dunno really how to use it well.

thanks!
[Sprint Samsung Galaxy S III] foreverinpanama:
I'll reply on your question on lux, everything else I'll let more educated minds handle it lol. I am a learner and experimenter. Lux works best if rooted btw, but what I found the easiest was to sit somewhere you would normally use your phone (like work), then with lux adjust it down to a brightness that is manageable to still read and use your phone, then hold down the chain links looking button until it saves that preset.

I did these about three or 4 times, once at home sitting in pitch black bedroom, living room with standard lighting, at work, w/e. From these settings lux seems to adjust the brightness pretty well around the rest of my day (like driving the car at night and such).

Also under lux settings>general, I had best luck setting it to adjust on wake only.
[Sprint Samsung Galaxy S III] jcdominguez:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

By JD you mean juice defender, right? If so, undervolting in combination with JD will help you achieve the MAX battery life. Because undervolting controls the... Well voltage and JD controls the radios (wifi, data, etc) they really aren't comparable with each other as they both assist in getting the MAX battery life while each controlling it's own separate thing.

If your issue is that you do no want to undervolt then that is fine, although highly recommended to get the best battery possible, you can try other battery saving techniques listing all through this forum. See OP and post 2.

For Lux, is there an auto setting. I didn't see it. So I have to launch the app everytime to get it to auto set?[/QUOTE]

As for Lux settings there really isn't much adjustment needed. There auto settings you can get choose from and the app does the rest.

I love Lux because it lets you decide how responsive you want the auto brightness to be, and when it should poll the light sensor. “On wake” (the default) is actually a good choice because it means every time you switch on the screen, the light level would quickly be adjusted. But if you often find yourself going indoors or outdoors WHILE USING the phone, you might want to go with Dynamic or Periodic. Periodic better choice for that reason.

_____________

Device: Sprint Galaxy S3

ROMS: Jellybam, Chemistry

Kernel: Ktoonz, Anthrax

"Extending android battery life through research, testing, and calibration."

Proud contributor and official kernel scientist for Team Kernelizers!
[Sprint Samsung Galaxy S III] Jpr0930:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Do these come set this way as default. It would seem so but want to be sure.
[Sprint Samsung Galaxy S III] daniel4653:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Yes they do. You just have to change q few options
[Sprint Samsung Galaxy S III] pberge:
I used to use Lux on the dynamic setting, but switched back to on wake only and have been much happier. Lux does a great job of automatically adjusting brightness, but I found too many situations, especially in very dark conditions, where it didn't always get it right. I set lux as low as -80% in complete darkness while using my phone before bed, but this setting is almost impossible to see in even a dimly lit room that may also give a zero lux reading according to the sensor.

With dynamic mode enabled, I would lower the brightness just to have it auto adjust on me a minute later. Setting to adjust on wake only gets me pretty close to where I need to be, but allows me to tweak brightness as needed without having to worry about it changing on me.
[Sprint Samsung Galaxy S III] DirtyShroomz:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

My battery life is amazing. Music has been on the entire 6 hours except for one 5 minute phone call. Regular Facebook, page manager, xda and news and weather usage. Battery was at 46% today when it would normally be at 10%. Battery life almost doubled.
[Sprint Samsung Galaxy S III] jcdominguez:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Awesome!!

Are you on latest kernel?

_____________

Device: Sprint Galaxy S3

ROMS: Jellybam, Chemistry

Kernel: Ktoonz, Anthrax

"Extending android battery life through research, testing, and calibration."

Proud contributor and official kernel scientist for Team Kernelizers!
[Sprint Samsung Galaxy S III] Wrngway:
Can anyone explain CPU Down Block Cycles and the related input on the newest version?

I get the impression higher values may increase battery life while reducing performance, but can't find out what it really does.
[Sprint Samsung Galaxy S III] DirtyShroomz:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I'm on 01/09/13. Staying put, I doubt there is anything better out there and definitely not worth the time for a possible 10-20 minutes of extra battery life.
[Sprint Samsung Galaxy S III] jcdominguez:
[Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I'm having unusual battery drain upon upgrading to new version. As I don't have weekend plans ill be tweaking and modifying hopefully get some answers here soon.

_____________

Devices: Galaxy S3 (spr, vzw, att)

Roms: Jellybam, Chemistry

Kernels: Ktoonz, Anthrax

"Extending android battery life through research, testing, and calibration."

Proud contributor and official kernel scientist for Team Kernelizers!
[Sprint Samsung Galaxy S III] DirtyShroomz:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Let us know what you get. Unfortunately i am one of the ones that had audio issues and that took almost a week to figure out. I'm done tweaking for a while lol
[Sprint Samsung Galaxy S III] 5FOOTER:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Not to shabby on PACman ROM with mid range settings and its still real snappy.
[Sprint Samsung Galaxy S III] adamdelozier:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I was experiencing that the first day...second day much better....guess it just had to settle.
[Sprint Samsung Galaxy S III] prboy1969:
So far doing really good on the latest TW Kernel. Have to see what kind of Battery Life. To soon to tell.
[Sprint Samsung Galaxy S III] castle_bravo:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

I flashed chemistry because I saw a couple guys on here using it and freegs3 started to get buggy on me after a couple weeks, plus I was getting tired of it. But upon flashing the new kernel I was constantly getting max mhz all the time with my typical settings. So I went in to init.d and looked at a bunch of the scripts, deleted one and modified 69gruesome to get rid of the I/o code and have since not had the issue again. Can't remember the name of the file I deleted.

goin nuts on this gs3!

​
[Sprint Samsung Galaxy S III] galaxys3man30:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Hey guys how is everyone?

President of {Team Kernelizers}

Im Gman and I approve this message
[Sprint Samsung Galaxy S III] Ragnar:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Great and you?

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] prboy1969:
Howdy stranger :D . Doing alright. How are things on your end ?
[Sprint Samsung Galaxy S III] GTOJim:
Welcome back.