yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mw86:
I forgot if enableoc.sh gets corruption it wont set your max mhz right. Maybe like castle_bravo just try doing the kernel install only again with the kernel cleaner too. Maybe it will fix those scripts. Make sure to fix permissions in recovery too.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] castle_bravo:
Are you on aosp? In system settings near the bottom there is a performance option where you can set min and Max. Look at those I just thought of it.
[Sprint Samsung Galaxy S III] mw86:
Yes what castle_bravo mentions are cpu settings also and will cause issues if those are set to anything at all. They should be as stock as the rom was when first installed. Nothing checked there at all.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk

---------- Post added at 11:25 PM ---------- Previous post was at 11:17 PM ----------

Posted this in Ktoonsez kernel in response to the quoted question. Figured you guys should take note as well.

I gave system tuner and android tuner both same developer a chance and clearly the cpu temp itself for me is not reported correctly everytime. I cannot depend on data thats not accurate. I have android tuner but i use Temp Monitor in play store and has been 100% accurate on mine. In Temp Monitor go to settings and enable cpu temp reading. In app shows battery and cpu in F or C. Plus can show in status bar and or tell it to only show in status bar if over a certain temp. Using both apps and heating cpu temp monitor accurate up through 195+ temps and android tuner still showed 150f instead. Fail if you ask me.

What 210F look scary? Yeah it probably is. Now lets see if media scanner runs rampant or qosmgr on a phone overlocked to high, will cpu get too hot possibly... of course. Might make you think twice about your max mhz. Btw guys my phone still runs as good as it did day one :P these things weren't made to die under just any circumstances. The cpu and gpu are located under the screen above the home button. If it gets really hot to the touch there you may want to track cpu temp, the heat is also felt below battery on the back in center area below battery to right of. Micro sd slot.

Be safe guys!

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] mcluvin1065:
Hey guys, after taking off my the overclock through KTweaker, making the max 1512, the deep sleep meter has dissapeared from the cpuspy app, and shows that is is an "unused cpu state. " Is that normal?
[Sprint Samsung Galaxy S III] jcdominguez:
Even after you lock your phone and do nothing with it is the deep sleep still unused?

Reset the timers. Reboot phone and see if that helps.

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!

---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------

The total time indicates 15 minutes your lowest mhz has no more than 2 minutes

I'm pretty sure the rest is In deep sleep its just not showing or reporting. Reboot phone, reset timers and report back

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] mw86:
In addition like you mentioned the deep sleep try to see if you leave screen off if you accumulate deep sleep. Its 90% easier to go into sleep on screen off (barring nothing is running when it shouldn't) and rare and hard to accumulate deep sleep with screen on. Both cores must be finished i heard at the same time to fully drop into deep sleep or if in single core in anycase must finish the workload. Thing is like a computer these phones have background tasks to keep the OS running and unlikely to have no cpu workload often while screen on.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] xblackvalorx:
Should update to the 1/9 kernel
[Sprint Samsung Galaxy S III] adamdelozier:
OK, I tried searching from my phone but came up with nothing...anyone have thoughts on using zepplinrocks supercharger, with all of these kernel tweaks? Before I dive in i wanted to get some opinions here. It helped me a lot on my OG Epic, but not sure its needed here on a much more powerful phone. Thanks in advance.

Sent from my cracked out SGS3
[Sprint Samsung Galaxy S III] galaxys3man30:
Post a link for us so we can it out
[Sprint Samsung Galaxy S III] galaxys3man30:
I got another supercharger made by mijji
[Sprint Samsung Galaxy S III] adamdelozier:
Its all about setting the low memory killer and minfrees.

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

Sent from my cracked out SGS3

---------- Post added at 08:44 PM ---------- Previous post was at 08:44 PM ----------

Can you share that link?

Edit: sorry...quoted wrong post. Was meant for Galaxys3man30

Sent from my cracked out SGS3
[Sprint Samsung Galaxy S III] xblackvalorx:
Supercharger is just a pain in the ass on jb. Pimp my rom, kernel tuner, countless other ways to adjust oom lowmem and minfrees
[Sprint Samsung Galaxy S III] galaxys3man30:
Theres no thread for it I just know its used in the goodness rom thats where jellybomb rom got it from I got a link but it just to download it thats all

http://www.xdafileserver.nl/Files/S...OLDER/GSIII JB MODS/Goodness SuperCharger.zip
[Sprint Samsung Galaxy S III] xblackvalorx:
Are there any tweaks for anthrax kernels.

Considering this is team kernelizers, not team kt, maybe some branching out and playing with other kernels is necessary?
[Sprint Samsung Galaxy S III] galaxys3man30:
Here is a new step for flash a new rom

Just ignore first part that info is just the jellybombers on the jellybomb rom

I have both an S3 and a Note 2..... Now that version 12.0.0 is on its way soon... Be sure to wipe and wipe and wipe!

I am forwarding a good suggestion from OneoftheRabble on the JellyBomb note 2 thread... Just to give you a heads-up on the new flashing of the upcoming JellyBomb version 12.0.0! (Its not out yet!)

Greetings,

Just a small tip to help some of you that seem to be getting "pieces" of files left over after/during a flash......

After you WIPE everything... take a bit and TURN OFF the phone and PULL THE BATTERY before you flash.

Yep, it might take you a minute longer, but it will sure help those electrons get away from your NAND chips.

After all, we are dealing with electronic circuits here. The capacitors DO store a charge. Those ROM memory chips

won't get completely cleaned out until you remove that charge that they still get from 'upstream".

Oh yes... make sure the phone is unplugged. So... wipe everything a couple of times, turn OFF the phone, pull the battery and wait about 30 seconds or so. Bet you have less junk hanging about.

If you take the extra minute to do this I think you will find you have a LOT less problems with residual stuff hanging out.

See ya'

OotR

*** Be sure not to charge while flashing! It adds extra voltage to the circuits and can cause issues with the upcoming amazing ROM Chief Beach has cooking!
[Sprint Samsung Galaxy S III] castle_bravo:
I just heard about that kernel and I'm doing some reading on it as well as other things I'm currently testing or involved in but I haven't had any experience with it. We are team kernelizers and we frequently use the ktoonservative governor. If someone else has experience with it or wants to test it and let us know what they think I'm interested for sure.

---------- Post added at 11:36 PM ---------- Previous post was at 11:28 PM ----------

Galaxy, we can get into a nerd argument about that all day but I don't agree entirely with that article, ROM is non volatile memory that power has no effect on, if it lost power and electrical charge for a year it sound still have the information saved and ready to go once it gets power. I do s agree with the circuits being charged and capacitors having juice on em but I done think its relevant to the rom
[Sprint Samsung Galaxy S III] galaxys3man30:
This is true the team mainly deals with the ktoonsnative governor the tweaks n all go along with that governor but if the testers on my team would go out and get info and test it out for the team so we found what we can do for that kernel or even post a link n I will go check it out as well

Lol nerds thats cool do have a point but from what I have seen far and talking to everybody that as used it says it works thats the only i posted here for that reason its just to get out there that here another step to do if want to be sure you get a clean install when you flash a new rom you dont have to do it its something thats there if you want to do it thats all
[Sprint Samsung Galaxy S III] jcdominguez:
I started with the anthrax kernel on my daily s3 device but never experienced the battery life as provided by ktoonz kernel so I gave that up.

I'll upload the kernel to my other s3 and test it and see if I can surpass what I get with ktoonz and I'll share my tweaks and settings.

I'm too devoted to ktoonz kernel.

:)

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] castle_bravo:
Yea I wasn't trying to discredit your statement, I just couldn't help myself. I just disagreed with the rom getting cleared by losing power, there are other chips and circuits involved that i can see being an issue. Nerding out is what I call it haha
[Sprint Samsung Galaxy S III] galaxys3man30:
Oh I know you wasnt trying to buddy but I do what ur saying there other factors n there more just to pulling a battery out lol

And ty for testing buddy just let us know what you come up with n maybe we can try to take it a step farther but ktoonzs kernel is the hottest kernel right now so idk we will see ill get with mw n gto to see what they think
[Sprint Samsung Galaxy S III] davidja92:
hey guys im using slimbean 4.2.1 beta 2.2 using the newest ktoonsez 4.2.1 kernel and i have the 35 11 setting and the mw86 settings thats supposed to stick on i/o but for some reason my cpu gov settings wont stick the up_threshold_hotplug is supposed to be at 35 but it resets itself to 68 no matter what i do i even press no on applying my saved settings and tried pressing back when the reset occurs anyone else have this?
[Sprint Samsung Galaxy S III] daniel4653:
Do you have ROM toolbox. If not you night want to use that to make it stick
[Sprint Samsung Galaxy S III] davidja92:
i have rom toolbox but havent been using it because every other rom i used with same settings lets the ktweaker setting stick but yea your right rom toolbox will be the temporary fix
[Sprint Samsung Galaxy S III] evouser22:
what i/O should i put it on if im doing the mw86 tweaks?
[Sprint Samsung Galaxy S III] daniel4653:
Bfq

That's what most of us use
[Sprint Samsung Galaxy S III] evouser22:
i set my tweaks but every time i turn my screen off and turn it back on, when i try to go into govenor adjustments it says "this governor does not have any adjustments parameters" ? what does that mean ???

---------- Post added at 09:59 AM ---------- Previous post was at 09:51 AM ----------

evrytime i exit the ktweaker app and i entr back into it , the tweaks are stock not the way i set them up
[Sprint Samsung Galaxy S III] steelers_exe:
What ROM are you running? Do you have ROM toolbox?
[Sprint Samsung Galaxy S III] evouser22:
Fre3 2.34c and yes I do
[Sprint Samsung Galaxy S III] steelers_exe:
Did you already try the workaround from the OP? This usually works for us.
[Sprint Samsung Galaxy S III] styles420:
I second your doubt - the only way to cause a chip to not erase data is to not supply the required voltage, which is the opposite of having a residual charge ;)

Those of us who know you know that you're only trying to help as always :)

As for the reports of success - that article made several mentions of "wipe, wipe, wipe," or the triple wipe (or 3x wipe) that I remember from the early days of the OG Epic, but that turned out to be a software issue that was fixed in later recoveries (thankfully - the 3x wipe still wasn't 100% reliable, but at the time it was three times more likely to succeed than a single wipe, so you can imagine how common the errors were back then, lol). I was able to successfully flash with just a single wipe (and no battery pull) for more than a year after the fix. So I think the battery pull step is a placebo, and the triple wipe is closer to the solution. It sounds like their custom recovery is as bugged as the first ones that came out for the Epic.

But whoever wrote that article seems to have the unfortunate talent of sounding (to the unsuspecting average user) like he knows what he is talking about, when he really has no clue - that's much more dangerous than a guy who obviously knows nothing, because his next suggestion could be a brick-maker, and a lot of people might find that out the hard way before news gets around (especially if the people who get bricked only had internet access on their phones, lol).
[Sprint Samsung Galaxy S III] castle_bravo:
I might have a record breaking run today, I'm at 1 day 5 hours on this run using row scheduler with some minor tweaks with 3.5 hours screen time, light/moderate usage since I'm home but has Wifi on most of the time. Phone feels a bit more responsive, not crazy different though. But I have noticed a little better initial load times and less lag. I think the combination of a battery conscience kernel setup and a tweaked row scheduler will take away any lag originally experienced. And now prefer it over bfq. I noticed a bit quicker drain on heavy usage though which I think is important to note (but smoother operation) I don't do any benchmarking though so no numbers for you guys. The other day I had an app go straight up nuts and my overall run was 16 hours with 3 hours screen time. Which isn't too bad really (although I expect 20 hours)
[Sprint Samsung Galaxy S III] xblackvalorx:
I get better battery with the kt kernel, but only with the tweaks in this thread. Which is why I ask if maybe tweaks for anthrax would be a possibility, but due to idiots on this site, who kang Chad and then accuse him of kanging, among other false accusations from some one with out the knowledge to back them up, he's had to take down his kernels.

And might discontinue his development career.

This would be a very sad day for android, especially the rooting community
[Sprint Samsung Galaxy S III] castle_bravo:
My quantums I think could be a little more aggressive but this is working great for me, its the row scheduler
[Sprint Samsung Galaxy S III] castle_bravo:
So I'm thrown it on the charger now, at 4% 1 day 8.5 hours off charge with 5 hours screen time so not a record :/ but close. Had over an hour of streaming music, an hour of streaming movies, texting, surfing the webs. With row scheduler and above tweaks with my 97 75 setup. I like how the phone feels now, no lag or delays noticed with this scheduler, during high loads though it seems to drain a bit more but on normal usage which is mostly what I do, I think it acts great and its a good counter against the battery conscience kernel setups like I have.

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

I'll be moving on to noop after this charge to give that a test, I'll give it two runs like I gave row
[Sprint Samsung Galaxy S III] pberge:
Wow, this is looking really promising!

Can I ask which kernel you are running? I notice you didn't have the options for use_yoyo_cpuload and cpu_down_block_cycles in your screenshots, so I'm assuming that you aren't using the latest kt747 build.

Also, have you applied all of the build.prop and init.d tweaks talked about on the first page?
[Sprint Samsung Galaxy S III] evouser22:
OP? What is that?
[Sprint Samsung Galaxy S III] GTOJim:
First post in this thread, also lots of settings in the second post
[Sprint Samsung Galaxy S III] Ragnar:
OP= Original Post or Original Poster. Just so you know exactly what it references.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] daniel4653:
Nice run!

BTW did you make any tweaks to row, or leave it as is ?
[Sprint Samsung Galaxy S III] mw86:
I live by row now. BfQ is still great and for those looking for the best battery life and not best i/o speeds Noop offers the most battery its the simplest scheduler.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk

---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------

I heard this too and is sad as it equally could have been an alternative.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] Chinkybean:
mw86, freecharlesmanson & galaxys3man ftw!

You guys are absolutely lifesavers! I was considering reverting back to Jellybomb 7/8 cuz the battery life was absolutely stunning with those builds which used LJ7 stock kernel. Being the noob I am, I just couldn't get this kernel to replicate that kernel. I was not pleasuring the thought of scouring the other Ktoons threads for the fixes so needless to say I am in Jellybomb heaven once again. Stop mpdecision was the gamechanger for me! Still a little early on this cycle but check this screenie.
[Sprint Samsung Galaxy S III] mw86:
Thanks for testing. Okay that means you are on Touchwiz rom freegs3. Okay sweet just set your debug.mdpcomp.maxlayer to 2 again and reboot. Don't both for now using the hwoverlay option seems on touchwiz it doesn't like the gpu controlling screen composition 100% of the time. To also point out the issue is specifically not full screen but possibly just the screen rotation function could be the issue too. I see how you press it and video resumes. This is just something with Touchwiz. I will make a note on my post above that option will be less stable on Touchwiz and not a big loss just there will be a little more cpu overhead preparing screen overlays. Thanks for testing. AOSP Android 4.1.2 users will still benefit from the tweak so if its not a bother whenever your phone has been rebooted make sure to recheck that option.

*** note about using my 65 99 tunables is when scrolling from idle if your on 96mhz min like me keep scrolling and scroll large amounts, the cpu will ramp up and stay there as needed but the initial sec you start it needs to fill the cpu to get o the proper ranges. Small amounts of scrolling you may near 384mhz and larger jumps for pages of on screen material about 1000mhz. Initial lag is seen because cpu is only using mhz that are necessary in 50.5ms it ramps from 96mhz to 540mhz if necessary on the smallest frequency step needed 2% if using 96-2106 max that is.

When tuning Ktoonservative frequency step is different when using different min and max numbers. If people need help having the frequency step right to hit all frequencies from min to max let us know. 2-4% is good for most depending on min and max. If using 384 min and not a high overclock that number needs to be higher than 2 and possibly 3.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
I'm running Ktoonservative with 99% of your settings, what's the better gov for battery with these settings? If you mentioned it already, my apologies, I didn't see it.

Ridin the Mystic jellybean unicorn on my Ktweaked SG3
[Sprint Samsung Galaxy S III] mw86:
Im pretty sure my newer one i call by their up down thresholds so the 65 99 one for better battery. Core two is one for much less time and the first core matches mhz to what is needed very well from observing. Music screen on or off can play at 96mhz with core two keeping up with whatever is necessary to stay there. Browsing and typing 96-384mhz. Tasks that max out cpu will always use max mhz on both core no matter what settings used. So my goal for that one was to be able to sit at a smart mhz on core one and core two by normal behavior helps keep up on work with its own algorithm, while i hotplug core two when load drops too fast for mhz down threshold to be enough and core one then maintains or lowers but doesn't drop unnecessarily because down threshold is 65 this prevents jumps up and down over and over load in a graph is smoother that way and no unnecessary mhz use. Core two turns on anytime cpu one needs to raise mhz to keep up, ultimately to me its best this way for performance and i drop core two off at a good level so it continues to be efficient and not wasteful of resources when unnecessary. Core two helps multitask and keep phone cooler by keeping core one only where necessary. Power as needed and less core two on vs my 75 95 which i have core two stay on till idle has completely happened. Better performance but based on workload core two may barely turn off which does help keep both cores mhz down too but at cost of battery.

The 65 99 should have close to the same performance and under full load the exact same performance but run cooler and use less battery than the 75 95 setup.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] Xalky:
I've been using these since this morning on the new JB 11.0 Rom. The phone is smooth and battery life seems to be real good.

What is MPdecision?

I followed your advice to go into rom toolbox,to make the settings take on boot but no joy, i still had to manually go into ktweaker. So here is what i did to make it take on boot.

First i set all my settings, sliders and tweaks in ktweaker. then i go into rom toolbox.

Rom toolbox/cpu control/ and make sure sliders are set correctly, check "apply on boot".

Hit back button go to Kernel tweaks, voltage control, check apply on boot.

slide over to Governor tab, check apply on boot.

This seems to hold it on boot.

If your having trouble making your settings stick, try this and report back.
[Sprint Samsung Galaxy S III] mw86:
Yeah cool thanks for posting this, you will need those steps when using romtoolbox for most of the settings. I use Ktweaker for everything and anythibg missing i use romtoolbox. But doing that on occasion my governor tunables would reset at boot anyway and i found using the governor tunable at boot option in romtoolbox fixed the isue for me. But as of right now, after clearing romtoolbox data once and resetting all my options all is loading now in Ktweaker without romtoolbox and i use romtoolbox for the script for mp decision and setting my ram memory options labeled OOM Memory manager as well as i work on build prop in romtoolbox.

So if you guys use romtoolbox for more of the settings and less in Ktweaker for the kernel than use the above directions.

Nice work Xalky! Thank you i am glad you like the settings.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] galaxys3man30:
Mpdecision is what controlling core 2 it overrides the tweaks we have so if you stop it u keep core 2 from running wild n saves alil more battery but that's with is bud hope I defined it right if not mw86 will he's my kernel man lmao

jelly bombed SGS3 jelly bomber 4 life
[Sprint Samsung Galaxy S III] pureEVO91:
So I am on Build FreeSG3 2.0. Ktoonsez kernel android 4.1.1 TW. I was having issues with the stock video player freezing. In doing some more testing it only happens when in (Developer Options) disable hardware overlays is checked. if I unchecked it all is well no freeze but with it checked it will freeze after 5sec. All other "tweaks" applied.
[Sprint Samsung Galaxy S III] mrgodai:
is there a reason to use script to stop MPDECISION instead of just renaming it?

I renamed mine and everything seems ok so far.
[Sprint Samsung Galaxy S III] galaxys3man30:
Have u check to see if running still?

jelly bombed SGS3 jelly bomber 4 life