yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mw86:
Thanks sure, no rush. Any data we can get on the topic will be beneficial. Thanks Clankfu. Let me know how those frequency step do, they are working smoothly on mine.
[Sprint Samsung Galaxy S III] cballin22:
I'm was having wifi issues also with the latest tkmod k build props I went back to the very first tk beta mod n wifi works great much faster it seems then when using the other beta 2 n or 3
[Sprint Samsung Galaxy S III] luis86dr:
Also make sure under wifi settings / advanced that "Avoid poor connections" is unchecked.
[Sprint Samsung Galaxy S III] robertm2011:
Hi, if anyone is still having runaway media battery drain, this has helped me (it is not automated, it has to be applied manually).
[Sprint Samsung Galaxy S III] galaxys3man30:
My rom thread is up n running fuys
[Sprint Samsung Galaxy S III] galaxys3man30:
Guys
[Sprint Samsung Galaxy S III] mw86:
Link? Nice GMAN

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] KennyG123:
It was a test release of Galaxy's ROM and no ROM should brick a phone because you are not writing to the bootloader. It may have sponged or soft-bricked your phone requiring a restore of a nandroid or reflash of any other ROM if it did not work.
[Sprint Samsung Galaxy S III] castle_bravo:
Light use, Wi-Fi only, 3g rarely. No % loss over night, Stock battery, there was a backup and I flashed a couple things in recovery.

sent from rooted stock freeza's deodexed lj7
[Sprint Samsung Galaxy S III] mw86:
She bangs! Nice work sir

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] daniel4653:
Thats the best I have seen in a while. I just did a clean wipe on my phone and I installed ktoonz kernel on stocked deodexed LJ7 and uses CharlesMansons rweaks. And holy cow. Only lost 3percemt in 5.5 hours. Thats the best idle time I've had.
[Sprint Samsung Galaxy S III] steelers_exe:
I'm so jealous of you guys! I'm gonna have to spend some quality time with touchwiz I think.
[Sprint Samsung Galaxy S III] mw86:
Bro they are both good. Ive got epic battery life on AOSP dont knock it :) im trying a touchwiz rom later myself though. Just saying slimmest least overhead roms I've used were AOSP. Im going to try Killjoy and remove even more bloat when i get it. Their goal was to make a stock jb tw rom slim and aosp like.

Guys have new tunable and a revision to one of my settings.

The 65 down threshold, 99 up threshold profile has 55 set for down threshold hotplug. This is now going to be 45 to prevent stutters noticed by core two cutting out too early.

*please take not Galaxys3man and update OP in your own time to reflect my changes.

New Tunable to be a mix of both of the other two. This one should be powersaving on raising mhz like the second one i came up with and the better performance of the first on by having hotplug down not engage till nearly idle levels but unlike the other two an even lower down threshold (mhz threshold) giving a more stabalized cpu scaling. Less switching and more being on the right frequency. You should see also rather than forcing a lower mhz this newest implementation allows the cpu to stay on a frequency longer and therefore work to finish faster with a faster return to idle rather than dropping at that time and adding more time to return to idle due to lower frequency. I was afraid it wouldn't drop to low enough mhz under medium heavy load but ots actually meeting ny requirements quite well. This may or may not result in better performance or battery life but it succeeds in staying smooth once the cpu has ramped up yet gives it a hard time to use max frequency unless necessary.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] 02bugeye:
Thanks mw I'll apply the new setting now.

One thing mw in your pic that you posted it shows 11 for the hot plug and 42 for the down threshold. Should we be using that setting for down or 45 like you wrote?
[Sprint Samsung Galaxy S III] mw86:
As pictured the 42. The 45 is the the new corrected down hotplug for my 99up/65down tunables in the original post.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] crazymook:
I'm currently using these settings from the first post.

down_threshold-75

down_threshold_hotplug-11

freg_step-2

ignore_nice_load-0

sampling_down_factor-1

sampling_rate-12500

sampling_rate_min-10000

up_threshold-95

up_threshold_hotplug-75

I'll give these new ones a go. Been having awesome luck with the above settings so I trust anything you provide, haha.
[Sprint Samsung Galaxy S III] castle_bravo:
These are the settings I rock. Same settings as my 2 day run with no 3g usage, this run is going to be with 3g enabled the whole time to see the difference

sent from rooted stock lj7
[Sprint Samsung Galaxy S III] mw86:
Looking good. Yeah thats why i have my revision above for that one i figured 45 down will be a better bet for anyone on that one. The 97 you set is a good idea to slow the raising of the mhz a little more.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] sparkie172:
Well here's my second run without plugging in for charge using 75 settings.

Gonna try out mw86 new setting. After I uninstall rt and clear data for ktweaker. Getting every pop up possible in KT for all settings.

Also can someone point me in the right direction I'm looking for freecharles post about his script for kernel settings. I've been looking for it but can't seem to find it. Doesn't help that I only have 2 towers near me so internet sucks in speed:( think my best speed test was .3mb
[Sprint Samsung Galaxy S III] mw86:
Looks good for being a busy phone in those spots of activities.

I have bad reception area too where i live it drains plenty of juice at low signal levels one bar all of the time.

Did you restore your backup twice in Ktweaker hit okay on all prompts during the restore of your backup and reboot with it set at apply at boot immediately and let everything load?

If not set all the options way you like and save a backup. Have it set as apply at boot immediately and just reboot?

The benchmarks and tests you ran i figure are the two big drains and the idle drain seems to be okay.

Before i had Ktoonservative and Kt747 kernel battery life was not more than 11-12 hours and 2-3 hours screen on. I dont use a stock battery now but id say your doing good for running those tests not just regular usage. What was screen on time about?

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] sparkie172:
I never load settings twice but gonna try that now. Screen on was around between 2-3hrs forgot already lol. I think I UV -15 trying -20 now

Am trying your new settings out.

Gonna read up on what each setting means so I can understand better
[Sprint Samsung Galaxy S III] crazymook:
Running new settings all day... Only thing I've noticed is the app drawer gets a bit laggy switching pages.

I find clearing ram helps randomly. Didn't seem to have this issue as much on previous settings. It's a minor gripe.

Battery has been great today.
[Sprint Samsung Galaxy S III] rhodiggah:
Well, this is my best so far with heavy use.

It seems like the phone is awake most of the time...

Sent from my SPH-L710 TPR_TW!
[Sprint Samsung Galaxy S III] cballin22:
On another note I flashed beta mod 1 booted up with working wifi then 3 rev n it's working fine may want to give that try
[Sprint Samsung Galaxy S III] iamikon:
Can you do us a favor and as [MENTION=4745870]mw86[/MENTION] said comment out (# in front of each line) any that were changed by tkmod. Reboot. After a reboot flash the newest 1.03 ver2? Seems as though an install from a untouched build prop fixes it. And you guys that are restoring unless you flashed the newest over a clean ROM then you are restoring old tkmod backups that are edited. Example flash 1.02 then 1.03 test then restore and flash 1.03v2 you are restoring the 1.02 build.prop not the ROM original
[Sprint Samsung Galaxy S III] noother84:
AOSP, Slim Bean build 5
[Sprint Samsung Galaxy S III] 5FOOTER:
Ok that maybe the issue going from one Tk Mod to the newest without flashing your rom. I'm on md4 baseband I will try a fresh install of rom and newest Tk Mod in the morning. Working nights so I can't test right now. If that does not fix I'll try a couple of the basebands and see.

You settle 4 less I want M.O.A.R.
[Sprint Samsung Galaxy S III] bso44:
I'm testing the wifi now without JD. And that frequency step is working perfectly. Very smooth.
[Sprint Samsung Galaxy S III] mw86:
I mentioned this to Luis just a few hours ago so I agree to that can easily be issue here.

---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------

Thank you, every bit of user input is important. Thanks 5FOOTER.

---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------

Thanks Clankfu and great I also have a good performance feel with it, yet its using good mhz range without skipping so many it becomes less battery efficient.
[Sprint Samsung Galaxy S III] jsbowling42:
I'm on fre3 2.54 with MD4 and i am experiencing the WiFi issue even on clean install. I'm not using any radio toggling apps as well. And im trying to narrow down the problem. No luck yet but I'm trying.
[Sprint Samsung Galaxy S III] luis86dr:
New build prop verification is now almost done.

The script will detect if you have modified your build prop and perform a safe install if you have. You now no longer need to restore before flashing. It will detect if it needs to for you. :)
[Sprint Samsung Galaxy S III] iamikon:
Something is strange on your side then cuz that's what I did my first test on earlier today. Are you using any other mods?
[Sprint Samsung Galaxy S III] jsbowling42:
nope im only using tkMod build.prop tweaks. what kernel version did you use? ill try clean install again for safe keeping and see what happens.
[Sprint Samsung Galaxy S III] MorphiousGX:
Just curious.... any of the people here having issues flashed or installed NOS injections?

---------- Post added at 09:29 PM ---------- Previous post was at 08:52 PM ----------

To help gather all the issues with TK-Mod, here is a form similar to the Tweak Test form. Please make sure to be as detailed as possible. It will help us serve you better and faster

This can also be used to request features/enhancements.

Form Link is http://goo.gl/WtRd0

Response Link is http://goo.gl/d9fka

** Team members, if you need edit access, please PM me with your email address
[Sprint Samsung Galaxy S III] presumedsublime:
For what it's worth wifi worked for me until I installed crossbreeder. Once I uninstalled it worked again.
[Sprint Samsung Galaxy S III] bso44:
I've got Croosbreeder installed and not experiencing wifi issues.
[Sprint Samsung Galaxy S III] iamikon:
I always install cross breeder before tkmod maybe try that.

---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------

I always use the latest kernel
[Sprint Samsung Galaxy S III] jsbowling42:
for some reason i tried flashing the mod in a different order and for some reason that i am unaware of wifi is working at the moment. and thanks for letting me know the kernel you used.
[Sprint Samsung Galaxy S III] luis86dr:
I would recommend flashing TK Mod last after you've applied any additional mods that effect the build prop.

Just got finished testing the verification script and all seem good for me, morph, and mw. Might do some more adjustments on it but I'll have a update out tomorrow for sure.
[Sprint Samsung Galaxy S III] BTT8:
So KToons just released an updated version of the kernal. I'm still new to being a part of flashing TK mod so would I need to reflash TK mod after flashing the updated kernal?
[Sprint Samsung Galaxy S III] luis86dr:
No, tho you may or may not have to restore your backup in KTweaker. Only need to re flash when flashing a rom.
[Sprint Samsung Galaxy S III] BTT8:
The fast response you gave, I thank you for it.
[Sprint Samsung Galaxy S III] bso44:
So I'm going on 6 hours of wifi without JD enabled and haven't lost connection.
[Sprint Samsung Galaxy S III] iamikon:
I think in some weird way it has to do with the order mods are flashed.

Side note for the TK world flash tkmod last to avoid possible issues. Not sure why but it seems to have fixed the WiFi for most of us.

the devil's in the details....

ktoon sez rock that blurple gs3
[Sprint Samsung Galaxy S III] bso44:
I've been testing mw's and gman's balanced-performance setup and it's smooth as hell. Haven't had a full day on it but the battery life seems to be solid as well.
[Sprint Samsung Galaxy S III] Androiduser96:
Could you or anyone give me the link to this set? I think I know which one it is but im not sure.
[Sprint Samsung Galaxy S III] bso44:
mw and gman gave it to me to test so I'm not going to give it out without their permission.
[Sprint Samsung Galaxy S III] mw86:
You can PM it clankfu if you still have link. Thank you for watching out for our interests.
[Sprint Samsung Galaxy S III] bso44:
Gotcha...will do. Thanks.
[Sprint Samsung Galaxy S III] ryandubbz:
I'll take it too please :)
[Sprint Samsung Galaxy S III] mw86:
I had sent or had it sent to you already a few day ago?
[Sprint Samsung Galaxy S III] Roni P.:
Ok ao I'm stock rooted... hiw would I go about tweaking these settings because its not a complete match yo to what I see on my phone?
[Sprint Samsung Galaxy S III] Maxamillion:
Why is it that my phone freezes all of a sudden and forces me to reboot?

I'm on gmans Ktoons/noop 189/1350

UV 25 across the board and 8% frequency step. Is it that the settings are too aggressive?
[Sprint Samsung Galaxy S III] mw86:
Can you post the volt table. Just open your backup as a text on your phone and copy and paste here as it will show the volts. The governor settings shouldn't cause reboot.
[Sprint Samsung Galaxy S III] Maxamillion:
Thanks for the help.

false

true

1

189000

1350000

1175 1160 1160 1150 1150 1125 1125 1100 1100 1050 1050 1025 1025 1000 1000 950 950 925 925 900 900 900 900 900

0

7

noop

ktoonservative

battery_ctrl_batt_lvl_high battery_ctrl_batt_lvl_low battery_ctrl_disable_chrg battery_ctrl_mhz_lvl_high battery_ctrl_mhz_lvl_low boost_2nd_core_on_button boost_turn_on_2nd_core disable_hotplug_bt disable_hotpluging down_threshold down_threshold_hotplug freq_step ignore_nice_load no_2nd_cpu_screen_off sampling_down_factor sampling_rate sampling_rate_min sampling_rate_screen_off up_threshold up_threshold_hotplug

10 5 0 1026000 918000 1 0 0 0 65 66 8 1 1 1 55000 10000 55000 89 95

918 Mhz

120

Disabled

Disabled

ktoonservative

Selected Scaling Min

Enabled

noop

0

0

0

0

0

false

Enabled

1000

45

43

1

918000
[Sprint Samsung Galaxy S III] clothednblack:
I don't see a issue with voltage, does it freeze at random or only with a certain app you are trying to open?
[Sprint Samsung Galaxy S III] Maxamillion:
It freezes at random.

Sometimes with chrome or when I pull down the notification bar. It just freezes. It allows me to turn the screen off and on but it stays frozen.
[Sprint Samsung Galaxy S III] styles420:
I thought that some devices used 950 for the lowest voltage whole others used 850 - my numbers might be off, but my point is that if he has one of the processors that requires the higher of the two options, then the table he posted is undervalued slightly, which could be the cause of his reboots... Just a thought, hope it helps :)
[Sprint Samsung Galaxy S III] clothednblack:
Removed
[Sprint Samsung Galaxy S III] styles420:
The fact that you offer your setup as a rebuttal proves that you don't understand what I'm saying - you would have to show me the lowest stable voltages of every gs3 in existence in order to prove anything, and I know for certain that, if you were able to grab everyone's lowest stable voltages, some of those devices would not be stable below 950.

Just because your device does not have the problem that some phones have, it does not mean that no other phones have that issue - yours doesn't, but the guy with the reboot problem might have one of those less UV tolerant processors... So thanks for sharing, but your info is meaningless in this case ;)
[Sprint Samsung Galaxy S III] clothednblack:
Ok, help him out then and ignore my post... It's been a long day already and my bad for posting a comment that didn't matter.

---------- Post added at 01:07 PM ---------- Previous post was at 12:47 PM ----------

Another option would be to open KTweaker and restore default settings and see if the issue goes away
[Sprint Samsung Galaxy S III] Maxamillion:
I increased the voltage by 15 and so far no freezes. Thank you for your help.
[Sprint Samsung Galaxy S III] styles420:
I get that not all devices are unstable at the same voltage... But since we were talking about his device, I don't know how bragging about how low another device can go will help - that's all I was saying. No need to get offended, I was only trying to focus on the problem at hand instead of saying, "That's nice, but look at how my phone doesn't have that problem," which doesn't solve the guy's problem unless you intend to trade phones with him ;)
[Sprint Samsung Galaxy S III] clothednblack:
I'm not offended at all, I'm a xda member too lol. I was just showing the extreme low without issue, not bragging :D. I still think a default test may help narrow it down.
[Sprint Samsung Galaxy S III] Maxamillion:
If it freezes again I will revert to default and test :)
[Sprint Samsung Galaxy S III] mw86:
This is mine if it helps. I get no noticed drain at this.

1350 1325 1300 1265 1265 1250 1200 1190 1190 1175 1175 1150 1150 1125 1125 1075 1075 1050 1050 1025 1025 975 975 950 950 950 950 950 950 950

For 2106-81mhz

Im just using 1512max right now
[Sprint Samsung Galaxy S III] luis86dr:
New Tk Mod 1.0.4 available.

Download: http://db.tt/9XdT65Jc

View changelog within Aroma.

Also, please restore your build prop with your current tk mod prior to flashing. This will be the last time you need to do this with newer version. Thanks.
[Sprint Samsung Galaxy S III] Neverender326:
Sweet! What do the new init tweaks do?
[Sprint Samsung Galaxy S III] luis86dr:
Performance enhancements. Haven't noticed any loss of battery from it either. :)

If you would like a reference on what was changed navigate to /system/etc/TK/TK-SYSCTL

The mod has a 45 second delay so it can properly set the values after boot and not bump heads with any other scripts on boot. So after booting up, wait 45 secs and you can check the file for reference. :thumbup:
[Sprint Samsung Galaxy S III] bso44:
Has the build.prop been changed from 1.0.3-Rev 2?
[Sprint Samsung Galaxy S III] luis86dr:
Same one. But I would still recommend restoring your original build prop with rev 2 and reflash with 1.0.4. New coding which makes it more efficient.

Just to be a bit more detailed on this, the newer script creates a file in /system/etc/TK named TKBP. When opened you'll see either a 0 or 1. 0 = Build Prop not modified by us, 1 = Build Prop modified by us. The script basically checks this file to see if your on a modified build prop, and performs a clean install of the new build.prop when updates occur.
[Sprint Samsung Galaxy S III] bso44:
Gotcha.

---------- Post added at 08:51 PM ---------- Previous post was at 08:00 PM ----------

Flashed the SYSCTL tweaks along with the 1.0.4 build.prop. Smooth sailing so far :good:
[Sprint Samsung Galaxy S III] Maxamillion:
can I run the init.d tweaks with crossbreeder without conflict?
[Sprint Samsung Galaxy S III] luis86dr:
Using it now with Cross breeder. No issues on my end.
[Sprint Samsung Galaxy S III] Maxamillion:
Just flashed and so far so good. :)
[Sprint Samsung Galaxy S III] bso44:
No issues on my end with Crossbreeder either.
[Sprint Samsung Galaxy S III] Samurai7314:
Things are looking good.
[Sprint Samsung Galaxy S III] luis86dr:
Okay, going to try and explain again to sum up everything into one post about the new "Verification System" I implemented.

When flashing the new 1.0.4, a new directory will be created. Within this directory you will find a file called "TKBP". What "TKBP" does is specify wether or not your build.prop has been modified by our Aroma Installer or not. The values will show as follows within the "TKBP" file:

0 = Unmodified build prop by Aroma

1 = Modfied build prop by Aroma

This is where the verification kicks in. In my coding I have it check "TKBP" for either "1/modified" or "0/unmodified".

So for sake of example, If 1.0.5 was released with a ton of new build prop tweaks, this will save you the hassle of having to restore your original build prop, then loading up Aroma again to flash newly modified build.prop.

If Aroma detects that "TKBP" = 1. It will restore your original build prop for you, and install newly modified version for you all in one session of Aroma.

Else, if its unmodified (0), it will apply it normally.

The reason I'm asking you all to restore your original build.prop is so the files required are implemented into your systems. Once this is done, it will not be needed ever again. Once a new version of TK Mod is released with build prop changes, just flash them in Aroma and it will do the proper install for you.

Restore setting in Aroma will be left for the people who want that option available, but remember! IT IS NOT NEEDED WHEN UPGRADING BUILD PROP AFTER 1.0.4.

If your still confused on this, then feel free to ask questions. But this should be pretty simple to understand. :)

Also, with the SYSCTL mod.

MW and myself have worked on this today trying to fix a issue he was having where the system would collide with our settings on boot. Basically, these settings reset on every reboot.

So what we did was make use of init.d (aint it great? ;)) and have it set at boot automatically. Problem is on some ROM's it will try to load the "default" values at the same time as our init.d script kicks in, which will basically override our settings. So I set a 45 second delay which should give more than enough time for the system settings to kick in, and then our init.d settings to load up normally.

You can reference all file attributes changed by navigating to "/system/etc/TK/TK-SYSCTL". Open that file with a text editor, or you can do the following from terminal emulator:

su

cat /system/etc/TK/TK-SYSCTL

This will display a list of "Before" and "After" settings so you can see what exactly was changed.

So once again, feel free to ask questions guys. Im open for discussion.
[Sprint Samsung Galaxy S III] mw86:
I made sure to not adjust same parameters as crossbreeder for example so to enhance the phones but not effect or differ from mods like crossbreeder, so I left parameters such as write_wakeup_threshold and read_wakeup_threshold etc. As well as randomize_va_space and and others are left for mods like crossbreeder to do thwir job. I kept other mods in mind. :high five:
[Sprint Samsung Galaxy S III] bso44:
Very cool stuff. Thanks guys.
[Sprint Samsung Galaxy S III] daniel4653:
Hey, hows everyone's weekend going so far?
[Sprint Samsung Galaxy S III] mw86:
Great how about yours? Been helping Luis with tkmod and our other members hard at work at other aspects like TPR on ATT.
[Sprint Samsung Galaxy S III] iamikon:
[MENTION=1795813]luis86dr[/MENTION] hey just a thought but can't you run the init.d script as say 99_**** so it is the last one run instead of a time limit? Or are there other things besides init.d scripts that will overwrite/conflict with yours?

the devil's in the details....

ktoon sez rock that blurple gs3
[Sprint Samsung Galaxy S III] mw86:
We tried that, this presented the best solution. I tried zzz in front of it but the issue was when at boot we apply...
[Sprint Samsung Galaxy S III] luis86dr:
Yeah as mw said we banged our heads on this for quite a bit lol.
[Sprint Samsung Galaxy S III] ryandubbz:
So what's up with the init.d optionin the tkmod installer it says something about it being required. What do I have to do special for this option?
[Sprint Samsung Galaxy S III] luis86dr:
Nothing special, usually all ROMs come with init.d support. So I wouldn't worry about that.