yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] bso44:
Well, I'm currently using a sampling rate of 100K on flastnole's variant of noclevername. Seems to be working pretty well.
[Sprint Samsung Galaxy S III] Jamin13:
Good information, thanks guys. I'm gonna look into this governor more and see if I can come up with something substantial.
[Sprint Samsung Galaxy S III] flak0:
hmm I might take a stab at tweaking this thing next
[Sprint Samsung Galaxy S III] LuigiBull23:
I say go for it bud. I'm sure we'd all love to give both setups a good run through.
[Sprint Samsung Galaxy S III] flak0:
thanks for the inspiration.
[Sprint Samsung Galaxy S III] prboy1969:
[MENTION=1462429]flak0[/MENTION] here is a box link to your latest setup SimplySmooth ;).

https://app.box.com/s/ohuyr1z6rrjb2pxcrigv

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] flak0:
Thanks buddy! I will update my post now.

---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------

post updated above with box link thanks prboy!!

---------- Post added at 08:57 AM ---------- Previous post was at 08:57 AM ----------

post updated above with box link thanks prboy!!
[Sprint Samsung Galaxy S III] prboy1969:
Your Welcome :) . Will give it a run as soon as I'm done testing flastnoles11 setup. Which BTW I'd running great :D

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] galaxys3man30:
I think everyone should read this its fixing to interesting for the galaxy s3 and s4

http://au.ibtimes.com/articles/4841...laxy-s3-official-android-4-2.htm#.UfTGs3PD_qA
[Sprint Samsung Galaxy S III] Jamin13:
Just have to hope that Sprint doesn't interfere much with the update. That or get a leak.

Sent from my Nexus 7 (2013)
[Sprint Samsung Galaxy S III] galaxys3man30:
Sprint shouldn't mess with it its all based on sammobile releasing the update the s4 has so many problems thats why it has been delayed so long and trust this phone has been a pain in my butt they sold it with a unstable rom and I mean very unstable
[Sprint Samsung Galaxy S III] bso44:
I read a rumor that Samsung was planning to skip 4.2 and going to straight to 4.3 for the S3.
[Sprint Samsung Galaxy S III] galaxys3man30:
Thats basically how they are putting it In that article the s3 probably will see 4.3 if the hardware can handle it
[Sprint Samsung Galaxy S III] galaxys3man30:
I will get to taste keylime pie at the end of the year
[Sprint Samsung Galaxy S III] Jamin13:
Yeah, that's what I'm hoping for. Sometimes, I'm glad I didn't switch to an S4 lol

Sent from my Nexus 7 (2013)
[Sprint Samsung Galaxy S III] galaxys3man30:
I dont regret going to the s4 at all its a really sweet phone and amazingly fast buts bacically what the s3 was soppose to have been to sum it up in a short answer
[Sprint Samsung Galaxy S III] Jamin13:
I don't think adaptive will offer efficient battery savings unless it has smarter hotplugging.

With my setup (min:540, max:1080), one core stayed on the minimum while the second core fluctuated between 740 and 1080. It seemed as if both cores were active at least 95% of the time.
[Sprint Samsung Galaxy S III] mw86:
That's a great sample rate to make the governor smarter and save juice by being less likely to scale up on a slight spike in load for a background task. 80-100k is real good for covering those type of setups. For more responsiveness one would need to go lower but i can attest my phone is quite responsive on 80-100k sample rate.
[Sprint Samsung Galaxy S III] flak0:
Might do this on mine, if sampling_rate is let's say 80000 then what would you set down factor to

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] flastnoles11:
Sampling down factor? I would set it to two...
[Sprint Samsung Galaxy S III] flak0:
So i just changed to sampling_rate 80000 and sampling_down_factor to 5 so in essence the cpu doesn't ramp down until 400000 milliseconds however I did notice less responsiveness. I'm going to try 60000 sampling_rate with a sampling_down_factor of 6 or 7. Before any mods the original SimplySmooth has sampling_rate of 40000 and sampling_down_factor of 10 and it's very responsive and fluid

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] mw86:
I agree with flastnoles.

The lack of response was due to setting sampling down factor so high. Two I agree is most you would like to use 4 max I'd recommend.

" sampling_rate of 40000 and sampling_down_factor of 10" 40-65k is great for responsiveness but the 400k from sampling down means it will scale up or down from 1-1.2ghz and up at 400k meaning it's super hard to scale up into upper ranges when needed.

At low mhz it uses the stocl sample rate but at 1-1.2ghz the sampling down factor activates. A more responsive and power saving setup would be 40-65k @ 4-2 sampling down factor or 75-100k @ sampling down factor 2-1. Sampling down factor 1 is stock and means it doesn't get used. Not scaling up or down fast enough in mid to upper mhz where sampling down factor activates would give a less responsive feel with inefficient use of battery because the mhz can sit on a finished workload longer than needed. Remember cpu wise over all aspects includong undervolt and governor the ability to use as little mhz as will get a job done without slowing things down saves the most juice so getting up to high mhz only when needed is best and right back down is best whenever possible. So 400k sample rate in cpu cycles is an eternity to sit on a frequency and is far higher than even tbe defaults in conservative governor.

Try it all amd get a feel, but watch that mhz like a hawk and be sure it can scale down from a full load to idle mhz fast enough to not drain the battery unnecessarily.

I'd say a max of 240/250k for the total sampling down factor adds up to.. So if on like 120k sample and 2 sample down it would scale up or down on mid to high mhz at at the 240millisecs. Or make lower mhz faster scale and upper the same slower 240k range. Ie 60k sample with a sample down of 4 for an upper mhz up or down response time of 240k about a quarter of a second.

I'm on GS4 but governor's work the same and I use 80k sample rate with sampling down factor of 2 like flastnoles recommended. So in mid mhz or higher it scales up or down at 160K between 1/5th and 1/10th a second.
[Sprint Samsung Galaxy S III] nappent:
My sioktoonzvariant run results

This light usage but still impressive in my opinion.

Using the AceSoft NFC 3160mAh stock sized battery.
[Sprint Samsung Galaxy S III] flak0:
U sir are awesome, thanks for providing me with this knowledge. I think imma go with 65k and sampling_down_factor of 2. Will report back. No wonder I noticed the Mhz hanging out in 1404 for a while before ramp down.

Sent from my SGH-T999

---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------

Btw do u know of any other values I could add to my setup. I'm really enjoying wheatley sio.

Sent from my SGH-T999

---------- Post added at 08:47 PM ---------- Previous post was at 08:42 PM ----------

@mw86 wow dude I changed to 65/2 and I was swiping across my home screen Nova Prime and look at mhz. Ur awesome.

Oh and I'm a huge decepticon fan lol

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] mw86:
Nice I'm glad it's working much better now :) I'll think on that, I myself haven't used Wheatley much. Sio is good.
[Sprint Samsung Galaxy S III] flak0:
Reason I went with wheatley is because of deep c4 state and love sio

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] mw86:
Wheatley is great for good sleeps states, yes. It's a very fast reacting governor which I am a fan of. Work should be finished fast and back to idle.
[Sprint Samsung Galaxy S III] flak0:
Yes I agree, sometimes feels more responsive then ondemand, although it's based on ondemand. Do u know about the parameters ideal target residency

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] mw86:
Yeah it is and uses residency/latency measures to help keep it responsive. If you post pic of the tunables i don't mind mentioning anything if I see any area for improvement and the members could comment to :)
[Sprint Samsung Galaxy S III] flak0:
Thanks.

Here they are, I made the recommended change to sampling_rate 80000 and sampling_down_factor to 2.

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] mw86:
Here is a good read on wheatley parameters. http://www.pinoyden.com.ph/index.php?topic=204875.0

I think I would raise your allowed misses from 5 to 8 based on the sample rate it may be better this number correlate to your sample rate.

Please enable i/o busy it will smooth phone operations when cpu is idle but i/o is busy. I use that one on mine.
[Sprint Samsung Galaxy S III] flak0:
Can't stop saying thanks. Gonna make those changes now. Thanks again

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] iamikon:
I would also put up threshold to 85.
[Sprint Samsung Galaxy S III] flak0:
Changing it now. Can u provide me some insight as to why. I really enjoy learning about this.

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] mw86:
It will scale up mhz slightly easier and not need to be so bogged on a mhz to do so... essentially scales up mhz at that cpu load threshold but with wheatley it will also consider those added tunables before scaling. If you find light load is too jumpy on the 85, try 90 instead.
[Sprint Samsung Galaxy S III] krntehknik303:
Starting to slowly learn some things.... After reading the last 6 pages or so.. Lol. This is fun!! Keep up the great work!!
[Sprint Samsung Galaxy S III] LuigiBull23:
Ok everyone.. So I've decided to move away from my default ROW/Ktoonservative combo and focus more on a setup consisting of SIO and the Nightmare governor as it is oftentimes overlooked. I've adjusted almost all tunables to my liking in attempt to further increase battery life while still maintaining general performance. My first full run lasted 1 full day on battery with a solid 5 hours of screen time. That said, I feel I've accomplished my overall goal but it means nothing without feedback from my fellow users and teammates. So If anyone is interested, I will release it soon after a couple more test runs.

I call this... Nightmare To Remember
[Sprint Samsung Galaxy S III] prboy1969:
Always ready to test a new setup :)

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] loneranger2293:
Hey i have source of kernel 3.0.13 can u make a coustom kernel for a a89 phone
[Sprint Samsung Galaxy S III] flak0:
Dude this is exactly why I went with wheatley /SIO combo. It's awesome exploring the unknown and it helps our fellow xda-ers along the way

Sent from my SGH-T999

---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------

If u don't mind I'll attempt to mirror ur setup using scary gov since nightmare is not available for TW. Thinking about playing with asswax again since I have gained all this knowledge

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] cballin22:
hey did u put the link to download that nightmare to remember
[Sprint Samsung Galaxy S III] LuigiBull23:
Don't mind at all bro. Of course this all depends on how well my setup plays on other devices. Performance appears to be good and battery life is ridiculous.. Sleeps like a baby :)

EDIT: I'm interested in trying that Scary setup myself.

---------- Post added at 01:13 PM ---------- Previous post was at 01:09 PM ----------

No. As I said, I will release it after a couple more test runs. Just wanna be certain everything is running smoothly :)
[Sprint Samsung Galaxy S III] flastnoles11:
Scary has no adjustment parameters... Was gonna do one last week... :(:(:(
[Sprint Samsung Galaxy S III] flak0:
12: Scary

A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.

So i jus played with scary (still on it as I write this) and I was flicking through Instagram to view cpu mhz and noticed scary keeps core 0 at low frequency and core 1 at higher. I'm wondering if this is because of hotplugging in ktweaker option.

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] LuigiBull23:
That sucks.. :(
[Sprint Samsung Galaxy S III] flak0:
Goin for asswax and potentially smartass if it's tunable. Lol we should all pick a governor test and post results like in a table. Showing performance vs battery. Hmm I think I just inspired an idea. Thoughts?

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] flastnoles11:
I'm working on an asswax one right now, but the more the marrier :D:D
[Sprint Samsung Galaxy S III] flak0:
Dude do u have any reference to point to what all the tunables mean in asswax. I'm wondering if on wheatley if I tune target residency if I get more battery life

Sent from my SGH-T999
[Sprint Samsung Galaxy S III] flastnoles11:
I have no references, the way I do it is I run out stock, change on thing at a time and see how the frequencies hang and scale and go from there.. Pretty much trial and error with me bud
[Sprint Samsung Galaxy S III] prboy1969:
Hey flastnoles11. Just had my second awesome run on your latest siovariant setup :D . Bad news is for the second time in a row, I didn't get screenies :( . Setup ran smooth. Great screen on time. Over 14hrs each time. Over 3+ days on one charge. Had a brain fart. Remembered after I switched to test flak0's wheatly/sio setup.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] flastnoles11:
Glad it's working out for you... Thinking of doing something with the sleepy governor next :cool::cool::cool:
[Sprint Samsung Galaxy S III] prboy1969:
Sounds like a plan :) . If it runs anything like this setup, it will be choice.

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] haveagr8day:
IIRC, the governor only affects cpu 0 when set using ktweaker as there were issues with running both on the same governor, or something like that.
[Sprint Samsung Galaxy S III] LuigiBull23:
Looking forward to that as well. Any chances of an siovariant part 2? :)
[Sprint Samsung Galaxy S III] flastnoles11:
Possibly, not sure I can improve much upon that setup though... I can sure try though! :D:D:D
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
Does mostly everyone use Gmail apk? I just wish they'd allow for custom poll times instead of having push on all the time so the battery isn't wasted. What alternative are you guys using if not Gmail? I know of k9 but there are still some bugs to iron out. Sorry i know its not kernel related but it deals with battery savings of which we all are trying to achieve.
[Sprint Samsung Galaxy S III] TheDriller:
I use Emoze
[Sprint Samsung Galaxy S III] prboy1969:
Thanks for the Tip :good:. I may have to try that out.
[Sprint Samsung Galaxy S III] mw86:
Excellent I will try this out. If a few report good results, how bout we add this to the post with recommended apps?
[Sprint Samsung Galaxy S III] JohnnyEpic:
Just switched from Emoze to Mail.

The log in from the middle east (Israel) server thingy doesn't sit well with me.
[Sprint Samsung Galaxy S III] TheDriller:
At least its Israel and not Africa or India
[Sprint Samsung Galaxy S III] TheDriller:
I need a couple of testers.
[Sprint Samsung Galaxy S III] RedJack117:
Pm?

Running Dandroid 3.9 on my Kernelized GS3
[Sprint Samsung Galaxy S III] Jamin13:
Did a run trying out adaptive. Seemed like it performed alright. Sleep performance overnight needs some improvements (~8% after 8-9 hours). Any suggestions besides stop using adaptive?
[Sprint Samsung Galaxy S III] TheDriller:
Pm sent
[Sprint Samsung Galaxy S III] iamikon:
Try not using zen. Its a battery hog.
[Sprint Samsung Galaxy S III] TheDriller:
Its only a battery hog if you don't set it up right. I've gotten 6 hours 23 minutes of screen time with zen browsing the internet and playing games. Most of my setups use zen. Its definitely setup specific as to how much power it draws but if set up properly can wield battery results like noop
[Sprint Samsung Galaxy S III] kaos1211:
I'm down for testing
[Sprint Samsung Galaxy S III] flastnoles11:
If you still need testers I'm always available
[Sprint Samsung Galaxy S III] Da Kine:
I was just about to flash a new ROM, if you still need a tester.
[Sprint Samsung Galaxy S III] TheDriller:
I'm booked for testers at the moment but the final version of this should be released to you guys this week or this weekend. Its sexy and y'all are gonna LOVE it. We might need another round of testers after our next update.
[Sprint Samsung Galaxy S III] Jamin13:
I think I had it set up pretty nicely (didn't save the settings) but now I've switched to row. I hope I set it up will enough after reading up on each parameter.
[Sprint Samsung Galaxy S III] michaelg117:
Just wanted to say, had a damn heart attack with those error messages when installing.

Sent from Charles
[Sprint Samsung Galaxy S III] flastnoles11:
These guys are real jokesters huh? :D:D:D
[Sprint Samsung Galaxy S III] michaelg117:
Yes! But I may have cried.. Just a little.

Sent from Charles
[Sprint Samsung Galaxy S III] TheDriller:
Can you check your entropy levels for me? https://play.google.com/store/apps/details?id=com.promethylhosting.checkrandentropyavail
[Sprint Samsung Galaxy S III] galaxys3man30:
Sorry guys been meaning to post this moving the reunion up to this saturday hope everybody can make it I should posted this sooner but im trying to move and its just been a super pain in my ass sucks living on the 3rd floor hope to see yall there guys

Thanks

Galaxys3man30
[Sprint Samsung Galaxy S III] michaelg117:
4096.

What does this mean?

Sent from Charles
[Sprint Samsung Galaxy S III] TheDriller:
Lol its perfect. That's where you want it. That means that [MENTION=4342879]flastnoles11[/MENTION] something went wrong on your install. You're the only one to report this problem. I will look into implementing the install script to a shell script, but I think either A) your init.d folder is fu©ked up or you don't have true init.d or B) your permissions are wrong on your init.d folder which I can add a line to set correct permissions on init.d before trying to install.
[Sprint Samsung Galaxy S III] prboy1969:
@ michaelg117 that's a good thing :)

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] flastnoles11:
Yep, my init.d folder is missing... I knew that, but didn't think crossbreeder would need it (because it doesn't)... Glad it was isolated to me though
[Sprint Samsung Galaxy S III] RedJack117:
4089 here...also had to restore and uninstall everything because I forgot to install ktoonz first lol but all seems well now
[Sprint Samsung Galaxy S III] bso44:
You guys are talking about your entropy with Crossbreeder right?
[Sprint Samsung Galaxy S III] RedJack117:
Correct
[Sprint Samsung Galaxy S III] michaelg117:
What does this mean?

Sent from Charles
[Sprint Samsung Galaxy S III] TheDriller:
Our modded CrossBreeder does need init.d as well as our sysctrl. We are adding some NOS scripts too which will also require init.d. CrossBreeder doesn't need init.d but I modded it to not interfere with governor/io and I also modded it to leave net buffers alone. Both TK versions need init.d because the unmodded one has a force script to force cross breeder to run for those that have issues with that like [MENTION=4745870]mw86[/MENTION]. The modded one has a melting script which will disable DNSmasq, ISP bypass, Tether boost and some other stuff which isn't really needed. Those features can be re-enabled manually if you choose the modded one and decide you want those options, but it still has the force script
[Sprint Samsung Galaxy S III] bso44:
People were posting their entropy levels so I was asking if they were using Crossbreeder.
[Sprint Samsung Galaxy S III] flastnoles11:
So are you saying both the versions in tkmod need init.d? Because I didn't install the modded one... :confused::confused::confused: I just don't like init.d scripts, imo they are a very lazy and inefficient way of doing things... Not saying you guys are lazy or anything, just not a fan of init.d scripts...
[Sprint Samsung Galaxy S III] bso44:
What's this modded Crossbreeder you're referring to? Is it going to be in the new TK Mod? Sorry, I've kind of been out of the loop lately.
[Sprint Samsung Galaxy S III] TheDriller:
Well our sysctrl stuff needs to be loaded at each boot and aside from modding the entire OS (because each ROM is different... AND we are making this multi carrier AND multi device) this is the simplest and most efficient way of implementation to make it safe for any device. Its not about being lazy. This is in fact very efficient and makes things easier for the end user who wants a simple entropy booster and other mods without needing a terminal emulator to stop things from interfering with ISP's or other connectivity issues

---------- Post added at 11:21 PM ---------- Previous post was at 11:15 PM ----------

Yes it will be released in the next TKmod. There will also be a lot more goodies in store, for now we have been getting testers to test things as we implement them one thing at a time to be sure everything is working together perfectly. There WILL BE NO more issues... [MENTION=4745870]mw86[/MENTION] and myself have worked our asses off on this with countless sleepless nights and close to 250 hours between us put into this to get it right. And we are still working on it. We have a time crunch and deadline to have it done by Saturday. There's a lot in this and all I can say is if you are lucky enough to test enjoy the smoothness that this brings
[Sprint Samsung Galaxy S III] bso44:
Awesome...looking forward to it.
[Sprint Samsung Galaxy S III] TheDriller:
From stack overflow.com

"In Unix-based computer operating systems, init(short for initialization) is the firsts process started during booting of the system. Init is a daemon process that continues running until the system is shut down. It is the direct or indirect ancestor of all other processes and automatically adopts ALL orphaned processes. Init is started by the kernel using a hard-coded filename, and if the kernel is unable to start it, a kernel panic will result. Init is typically assigned process identifier 1."

So just so you know all UNIX based systems (this means android) uses some form of init.d whether you have a folder for it or not
[Sprint Samsung Galaxy S III] KennyG123:
Thread cleaned

It's one thing to have a development debate filled with facts

It is an entirely different thing when the debate is filled with personal digs

THEN I step in as this will not be tolerated on XDA

You want to take personal digs, you WILL be infracted so take it to PM or Twitbook but keep it out of XDA threads

Thank you for your cooperation

Friendly Neighborhood Moderator
[Sprint Samsung Galaxy S III] Dgsaxhitman84:
Over the past month I have been using this and haven't yet had the time to test all of the mods available I a wondering if someone has found the best option for saving battery as well as keeping the performance... I know this is an opinion question but I just don't have the time I used to... Otherwise I'd tweak myself

I should mention I'm running M. O. A. R. 5.01
[Sprint Samsung Galaxy S III] GTOJim:
The two biggest drain on battery is screen and the data connection. Keeping brightness low can save juice, also using inverted apps, black theme, the color black does not use juice with our screens. Also turn off data when not needed, poor reception can drain battery even faster, use Wifi when possible as it can be more battery friendly.

With buterlicious I just got 7 days with 23 1/2 hours screen on. See post 23 in this thread.

http://xdaforums.com/showthread.php?p=44133162#post44133162