yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] castle_bravo:
if you are using the same governor then the last applied settings should rule. Your script and ktweaker are going to conflict with each other
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
Odd thing is, they seemed to run well. Only thing was, it was a bit odd a battery hog. Insane performance.

TEAM MiK

MikROMs Since 3/13/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Has anyone noticed any changes with the new kernel good, bad or otherwise

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
I've applied your setup + script (along with TK mod). It ran amazingly well for a day but now my frequencies are playing yoyo every second = bad on the battery. Should i clear it and start over?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Check if every values of the script are being applied correctly. You could also try to clear data for ktweaker and not input the settings manually.

Or a few reboots could do it as well :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I just came across this logcat app on the portal. It can bu use as a full screen app but you can also see the log in a floating that you can resize. I thought some of you may find it handy.

http://xdaforums.com/showthread.php?t=1513166
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Nice find Lilitz excellent!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalhead2791:
Hello everyone,

I am running the latest kt747 4.2.2 kernel and my phone seems to be pretty stable when undervolted all the way down to 125 mV under the stock voltage all across the board. I have no force closes or lag.. Nothing. I have been reading up and I am not exactly sure this much undervolting is doing my phone any good, apart from keeping the heat down of course? Also read it can be detrimental to the battery life also. What do you think my good people?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
liltitiz,

I get instant reboot upon running your script with your KTweaker settings. Is there anything you (or anyone else) would recommend changing to fix this? I am on TW Jellybeans Build 18 ROM (from Verizon S3).

Edit:

I tried something as simple as this in Terminal Emulator and still got a reboot about 6 seconds afterwords:

su
echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

Should I try a different governor? Which one? From what I understand only certain governors have settings that can be modified like asswax. There is limited information about what are the differences between these governors.....and the names are really ambiguous (asswax.....wtf?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
Question, guys. Running Task and balanced bull v2. I'm having difficulty with the asswax script. It runs perfectly when I perform an AnTuTu test to make the cpu1 folder available and run the script through Scripter. The script runs cleanly and the asswax governor sticks. The problem is that Scripter can't set it on boot.

I can get the same script to run on SManager, however, I get permission and no directory found errors when I run it under the same AnTuTu conditions. SManager will give me the option to set on boot but nothing sticks. KTweaker set on boot as well. From what I'm reading, the timing should work out.

I'm missing something and it's right in front of me. I know it's got to be a timing issue if Scripter can do it after boot and SManager can't. Thoughts? Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
Make sure you run the script as SU in SManager. Once you click on the script....there are menu options. You must click the one with the skull n crossbones to run the script as SU...you must also click Save to save the SU setting for running the script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spider_Pig27:
What is the best setting to get good battery life and fast processor? Thanks in advanced
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
I'm having an issue. When I enable my screen off mhz, once the screen goes off I get an instant reboot. No over or underclock, voltages are stock (1150 and up), doesn't matter which governor or how high I set the screen off max. I'm on TW stock 4.1.2. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
The setting that works best for your device. I'm sure if you bother to take a look in the last few pages you'll find some settings to test and you will probably find one that works well for your device ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
And what are you trying to use as your screen off max freq?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Around 594, but I've tried all frequencies. No dice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
Bump...please help me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] castle_bravo:
It's this everything? If you disable hotplugging in ktweaker and force cpu1 on, do you still get a reboot when you run the script?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
1. Disabling Hotplugging...then applying the script worked! I missed that I guess.....

2. BUT once I re-enable hotplugging as suggested (this should be done, correct?) I get reboot.

3. After the reboot, my settings have reverted to normal (no asswax on CPU1).

Any ideas? Do I have to have hotplugging permanently disabled for this to work....is that ideal or expected behavior?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Not at all. I'm currently running my Balanced ROW/Ktoonservative setup on CPU0 while running Asswax on CPU1. Hotplug is enabled and no reboots. It's running incredibly smooth I may add.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
OK....well, that sounds like I should be able to re-enable hotplugging after running the Asswax script on CPU1....but when I do, I get reboot....why? Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Which governor are you using for cpu0?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flak0:
Msm-dcvs for governor :)

Sent from my SGH-T999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
OK..but isn't it true with that governor that we cannot change all the extra settings like what is done with the asswax script (idle freq, max/min cpuload, etc)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pgg285:
With the asswax script enabled and liltitiz's Ktoonservative governor tweaks, whenever I open KTweaker it tells me my governor settings don't match my saved settings. Is that par for the course or am I doing something wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Clear data for ktweaker and don't restore the settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
I use Ktoonservative governor for CPU0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pgg285:
Thanks for the reply. Do I re-enter your governor tweaks manually after that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yes you reenter your previous settings or new manually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you use ktoonservative you don't need to check auto hotplug
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Or are you talking about enable hotplug in ktoonservative's tunables?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
To be as clear as possible, I will restate everything I do:

1. Currently set to KToonservative Gov

2. I disable Hotplugging entirely in KTweaker (Auto Hotplug unchecked and disable_hotplug_bt=1, disable_hotplugging=1)

3. I make sure CPU1 is running and execute Asswax script and wait.

4. Confirm script settings are written proper by checking individual files in system

5. I re-enable Hotplugging by setting disable_hotplug_bt=0, disable_hotplugging=0 inside KTweaker KToonservative Gov settings

6. I get reboot within 5 seconds.......

Did I do something wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
This has been known to occur on certain TW ROMS such as MOAR. Not quite sure what the cause is. All I know is the script was originally made on AOSP and I'm thinking it may have something to do with a mismatch between tunables and/or values. I'm currently running an AOSP ROM so I wouldn't know for sure but I have the same setup and no issues whatsoever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
When I have time I'll flash a TW rom and try to sort this out. What rom are you runninh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] luss007:
ktweaker doesn't open now

Hey guys ...first post ever on xda..wonder if someone can help me! For some reason ktweaker app does not open anymore on my phone...i instaled kt747 kernel a couple of weeks ago and everything was working just fine ...overclocking and underclocking, voltage....and since yesterday,cant access app at all..tried to flash zip kt747 again..no change......erased ktweaker .apk and than reflashed zip..no change again..! Im rooted with stock rom/ sammy's kernel kt747....if you guys wonder why im on stock rom, i keep getting f....ing assert failed/get prop status 7 error message when i want to flash a custom rom so im Still on stock...if someone can help me whit that 2, would be very appreciated..

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
The people that are having your error are stating that you need to be on latest recovery to avoid the error. I also think someone said something about needed to change build prop or get at&t recovery. Can someone confirm the at&t thing that has had the issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Thanks for the report! I'm working on it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dntesinfrno:
I'll start with the status 7 error message when flashing ROM .zips as i just ran into this yesterday. Since you didnt specifiy i'm going to assume a few things. The first is fairly safe since you were successfully running KT747 i'm guessing you are on an AT&T i747. The second is a crap shoot although i have a sneaking suspicion you are using TWRP...correct me if i'm wrong and please provide the version of whatever recovery you are using. Going ahead with my assumption the TWRP 2.3 update had an issue installing some.zip's with the status 7 issue which they have since fixed in the new 2.3.1 released today, according to the changelog. I cannot confirm this as i haven't tried it yet, and also they did mention in the 2.3 update that they changed to the recovery 3 api which could cause problems with installing .zip files that weren't scripted for this. In any case if the ROM(s) you are trying to install don't work on the 2.3 version you can always flash back to 2.2.2 which should work with no problem.

As far as the ktweaker issue, you said since yesterday....what changed on your device before you noticed the ktweaker app not functioning properly? I'm not going to so far as to say that programs don't up go rouge all by themselves ever, chances are pretty slim. At some point, somewhere there is almost always a root cause. The easy answer is to say wipe/reflash but this is a workaround and not really a solution.

And btw, you really should have started your own post in the Q&A forum instead of randomly posting where you saw mention of the app you are having trouble with
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Wrong thread go in the q&a section! This thread is all about sharing and discussing ktweajer settings not troubleshooting it. Please do not post here. Unless it is setting related, thank you ;)

So if anybody wants to help him do it via pm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] luss007:
Sorry guys for posting here and thanks a lot for the reply...just solved my ktweaker problem and planning on flashing other versions of recoverys.:cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
I'm running liltitiz bfq/abysssplug settings, uv on each step +40 from your voltage table because I kept getting hard reboots. Fairly stable now, but the Facebook app just caused 2 "soft" reboots, each while I was doing different things within the app. Anyone else seen this with the fb app specifically or do I just need to keep bumping my uv settings until the reboots are gone?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I have tried not uving at all and Facebook make my phones soft reboot every times I try to watch someone's pictures... :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Just with bfq?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
We every possible combinaisons :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
Cool, that's exactly what caused it the first time. The second time, I tried to tap a different pic to see the tags.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I wouldn't tweak UV settings based on Facebook causing reboots. Its not exactly the most stable app to begin with. Its actually in the process of a complete rewrite which will hopefully be out soon
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Use Friendcaster... better app anyway.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I think I have the perfect set-up for abyssplug! ( for my usage of course) Feel free to try it on your phone and give me some feedback about battery life or lags:)

I think I got rid of the CRT animation lag!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Was just gonna thank you I'm following your setup and I have 3 hours of screen with 50% left. I'm gonna try these to see if it gets better!

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
Damn... my phone does not like these settings at all. I can't even get them completely entered before Ktweaker freezes and the phone reboots. Tried it twice, same result each time. Your previous abyssplug adjustments seem to be working fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yokopol:
same here...running previous setup with hotplug and its really nice. this one just freezes before even i can finish
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Same here. As soon as I leave the page it reboots. You sure you didn't make any other changes?

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Slim Bean but doesn't matter what AOSP ROM I run. Never have any issues. Reboots only seem to occur on TW, most notably on MOAR ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I was asking Stupifier sorry wrong quote :p I was asking for TW rom that doesn't work with the script
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
lol ok well if it helps, MOAR is definitely one of them. So you might wanna check that ROM out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stupifier:
I am on Jellybeans B18. The ROM RErick always recommends.

Also, thank you for confirming I did

NOT

miss anything

Also worth mentioning, like others, I removed the following line from your script for the script to run properly:

echo 1026000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrFhenix:
DONATION COMMING UP!!!!!!!!!!!!!!!! DAMN EXFAT WORKING LIKE A CHARMMM!!!!! on a 64 G THANK YOU :laugh::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeduardors:
grat post! thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Which post? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GTOJim:
When making a script with BusyBox where can I find it to make a copy to save? I haven't been able to locate it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Hey Liltitiz. When I was entering all of the Ktoonservative gov adjustment settings, I noticed that there were several that you didn't cover. Did you leave the ones that you didn't mention at their stock values? Is this setup what you would recommend for decent battery life with a stock battery?

Sent from my Galaxy S3 Tapatalk 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
The tunables that aren't covered are left stock. This is the setting I've been using for a while now and it's a setup to get good battery life and to keep everything smooth and lag free. You'll still be able to play most of the game and your apps won't take 3hours to open :p.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I am also having problems with Ktweaker that you may or may not be able to help me out with. When I close Ktweaker out of the recent apps menu, it resets all of my settings & asks me all of the yes/no questions the next time I open it. Do you by any chance know of any way to stop this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Answer "No" for all questions then exist and reenter Ktweaker and reapply your settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Thanks. That did it. Is that necessary on every reboot or just that one time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
It should just be that one time. There are some instances where clearing Ktweaker data or modifying the settings will cause the messages to come up again. It will most likely happen if you haven't locked frequencies and have other specific tuner apps installed. So it's always important to lock your frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Can anyone tell me which lines of the asswax script need to be edited to make it run properly on TW ROMs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Find the tunables that isn't in asswax or that is different for the touch wiz version and you will have your answer. I didn't find any time to flash a touch wiz rom and try it yet so I can't really help you further more
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubluv1:
Thought id contribute.. Here's my best numbers so far :

SlimBean rom

189 - 1512 CPU

-50 voltage across the board

Ktoonservative / row

Screen off profile

Lowered vibration strength a little

(Onite 2300ma battery)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I'm sure know but locking frequencies could potentially cause overheating. Lock frequencies disables thermal throttling, or it used too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I don't ever recall locking frequencies would disable thermal throttling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NellyWhads:
I assume this kernel cleaner would work with other kernels too? If yes, I'm going on a field day with kernels today.... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
http://xdaforums.com/showpost.php?p=38379662&postcount=9170
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Except Ktoonsez sometime after that by request (I asked amongst other users and I greatly enjoyed testing builds to get it all implemented :) ) worked on a few days to implement thermal throttle control. His ktweaker thermal settings override the lock frequency lock, in fact it doesn't even ovveride it is with what lock frequencies allows ie anything in ktweaker is forced to work with that checked without the system may ovverride stuff as well as third party apps. So using that option and setting thermal throttle in ktweaker will actually ensure it handles how you programmed it. Recommended setting enabled.

---------- Post added at 02:09 PM ---------- Previous post was at 02:06 PM ----------

Yes a kernel cleaner tool will help you make sure no remnants of previous kernel are there before installing a fresh kernel over an existing rom install. But ktoonsez is so awesome if you flash his kernel it cleans what's needed and doesn't need to have the kernel cleaned just update installed over top. But if your going to go all will nilly lol on any kernels available than I would recommend flash kernel cleaner before each new kernel install..

The best kernel hands down is KT747. The other developers deserve just as much credit though as they all here out out great work :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Where can I find this kernel cleaner?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
http://xdaforums.com/attachment.php?attachmentid=1319515&d=1347395869

In OP here http://xdaforums.com/showthread.php?p=29426212
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Casadisole:
Battery Life

Just wanted to share. Greenify is incredibly awesome. Battery life easily increased by simply putting apps to sleep when the screen is off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aeduardors:
Original thread :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lucius1972:
Hi liltitiz,

I am planning to use youre settings in KTweaker and your script but i have 1 question?

What about the other setting in KTweaker? for example under the option "Extra"?

Screen of CPU max, GPU max etc?

You leave them untouched?

Thank you in advance..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Sorry for the late reply. I let you set those settings because In my opinion, they are more devices specific so just go with what works best for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Little mistake :p

Edited out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
Running KT's newest on Task's 4.3 with Balanced Bull and Ktooservative. For some reason, my Asswax script isn't sticking since moving to 4.3. My script hasn't changed and all file paths are still valid.

/sys/devices/system/cpu/cpufreq/asswax/ isn't persistant as it used to be under 4.2. As soon as I move away from Asswax as my cpu0 governor that folder disappers. What am I missing? Are there any changes needed between 4.2 and 4.3? This may be a stupid question but any advice would be appreciated. Thanks in advance...

echo 1080000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 1000 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 189000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 80 > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 60 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 250000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 100000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 5000 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I think you meant to say cpu1 governor but anyways, if you're running a hotplugging governor for cpu0, such as ktoonservative, that folder will always disappear anytime the 2nd core goes offline then reappears as it comes back online. So in other words, you need to make sure cpu1 is online when checking the Asswax folder, otherwise it won't appear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
Thanks. I got it resolved. The issue was with SManager Finally ran AnTuTu again and navigated to confirm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guugle:
Hey guys,

i've did some benchmarks for every single frequency and am wondering why the 81 Mhz clearly has more performance than the 135 Mhz and 189 Mhz steps. I searched a bit about this but got no answer.

It's happening on every ROM with KT747 (didn't try other kernels).

So why is this happening?

My settings are:

gov: performance

min/max: same frequency

frequencies are locked