yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
changing hispeed_freq bug

I think I may have found a bug with the interactive governor. I like to change my hispeed_freq from 1134000 to 810000. Everything runs fine but then when you return to ktweaker you get the pop up warning that your settings don't match save settings and when you hit yes to apply saved settings it appears as though the max frequency gets set to whatever you have saved in the hispeed_freq field. forgive me if this has been covered before. attached is a logcat and last_kmsg if they help. thanks.

EDIT: Also I'm running CM 10.1 RC3 with the 5/29 kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsyl:
Simple: after you've changed the hispeed_freq you're constantly restoring your saved settings. Press no when you see to apply saved settings and backup your prefs to your sdcard. You won't get anymore issues :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Sd cards will mount faster and read/write speeds will increase.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Ok so that works for that current boot. Once you reboot regardless of whether or not you visit ktweaker the hispeed_freq is reset back to 1134 and that seems to be the max frequency period. To fix it I have to open ktweaker, select no at prompt, set set on boot to no, and then reboot. Following that, if I reapply those previously saved settings I instantly get the same behavior. So then I would have to force stop ktweaker, clear data, then reboot, and then manually apply the settings. All other kernel settings are fine it only occurs when doing governor settings, hispeed_freq is the only one I change so I'm not sure about the other settings. Guess for now I will not change any governor settings or try a different governor. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Touchwiz test for the people having KTweaker issues:

http://www.mediafire.com/?me7waak8fwpxu7z
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jde984:
Success! Well done sir.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
WORKS!!!! Well done bro!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
If you have System Tuner, or any other CPU managing app installed, it may be interfering with KTweaker. Go to Settings/Superuser and remove rights to any other installed CPU app and problem solved... if that was the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
i have no other cpu apps installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log

1. Updated KTweaker to not get screwed by the Touchjizzer ROMs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Dude, you scared the crap out of me when I saw the thread title changed dates. Good thing it was a TJ update so now my poor little ticker can stop beating so damn fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Likely what you are seeing seems to be from sitting inside the app as it normally doesn't run. You could try clearing it from recents list. See normally it takes zero resources but on the general screen in ktweaker it provides info as mhz currently and cores active etc. This can take cpu time and is not a oart of normal ktweaker operation just using phone so perhaps that is why you saw that in battery stats. The throttle control screen is the same providing temps etc.

Normal setup ypu dont ever see ktweaker in any battery stats.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsyl:
Ya but did you backup the prefs to sdcard when you changed the governor settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
yes backed up after governor changes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
Thanks ktoonsez! You kick ass! Have a great weekend :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Zero issues with 5/29 on CM's RC4. Runs beautifully on every ROM I've tried it on.

Thanks KT!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I wouldn't expect anything less.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Guys somebody clear this up for me the 5/29 update is the latest update for AOSP and 5/31 is the latest update for TouchWiz correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Yup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
What's to clear up? lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, what are the new settings in extras tab?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
https://www.dropbox.com/s/dt9fhutqpxnn427/last_kmsg

Running newest task and went into quiet hour and changing times caused a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polsonov:
same here. Just flashed KT's kernel this morning. Now I'm asking myself why the hell did I wait so long. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
Sdcard read speeds and GPU governor are the big changes along with the ability to great logcats and last dmesg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Ktoonsez i miss your kernel and want it on cm10 :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
What is the purpose of posts like these? What do they have to do with this kernel? Do you think posts like this will make him work faster?

I'm sure he will make one for CM10 in due time. Being demanding is not going to make it happen sooner.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chopard:
If I don't want to use cpu/vc what are the default settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Am I the only one with the status bar icons going crazy on the new 7/19 update? I cleared all caches and even fixed permissions....btw

*Edit...reflashed 7/18 and all is well again. My widgets wouldn't load either...fyi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated: (Added back in govs/scheds to AOSP version and try to fix adb remount for Sammy)

SAMMY VERION: Download CWM flashable zip kernel

http://www.mediafire.com/?4g2ecftsu5s7zlh

AOSP VERION: Download CWM flashable zip kernel

http://www.mediafire.com/?iggq8x29ri7dq8v

Change Log for 7/19b

•Added missing govs/scheds to AOSP version

•Made change for adb remount on Sammy version

•Change volt table to support SetCPU
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
thanks for clarifying. I had assumed that he was referring to some other instructions, most likely in the OP rather than a suggestion for a fix in a previous post.

lol, of course you thought you were clear; otherwise you'd just be spouting nonsense. Again, when referring to "the instructions" generally i've found that those actual instructions are in the OP where the chance for them to go unnoticed is less likely. perhaps that is where the disconnect was.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Even after wiping cache, dalvik, and fixing permissions I still see changes in clock speed, governor, and scheduler on every boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
which version are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Sammy version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
the 7.10b, 7.18, or the 7.19?. So far i've tried 10b and 18 and settings don't stick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
So, try 7-19b? With tons of fixes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave2metz:
Question.. I know some ATT ROMS are compatible with T- mobile and vice versa. So can this Kernel be used with T- mobile? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dualmoon:
Probably so he knows that people actually want this for CM10 in case he wasn't aware that people are interested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fznwolf:
Quick question, I'm using the kyanROM.

Should i use the samsung or aosp kernel?

Also, if ive backed up using CWM do i have to install the restore tool in the description? Would a restore from the CWM provide me my old drivers back if i were to revert?

This would be my first kernel update.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
Check to ensure you do not have power saving enabled in settings...?

A) you need the"Sammy" version

B) I don't understand your second question...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Hey brother... What's up w/ the 100 thanks in the OP??? There should be like a bajillion by now:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeesubalpha:
kyanROM is just a mod of the stock ROM so use the sammy kernel. if you use AOKP or cyanogenmod use the AOSP kernel.

using a CWM restore will NOT restore your drivers. there is info on how to restore them in this thread somewhere
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Just a friendly reminder: be sure that when you are checking settings that Power Saving is turned off. Its easy to miss those things. I was on a goose chase earlier thinking that 1512 wasn't sticking, and it ws Power Saving was on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Draelith:
Having same issues with 7.19b. Also, occasionally the keyboard only partially draws.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeesubalpha:
my setcpu settings are not sticking either. the sliders were set at 192max and 384min (you read that correctly) when i launched setcpu for the first time with this kernel, but reading at the top indicated 1836/384.

i don't think i'm doing anything that would cause this..?

edit: thanks for the work ktoonsez... 2 updates in 1 day wow
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Suggestion toonz put your kt kernel app on the play store and sell it :)

Why? Because it's amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Oooh yeah! Create problems for people who download it thinking it'll work with any kernel besides KT747, and limit the utility of the kernel for everyone else! That sounds awesome! /sarcasm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Cool story bro. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
I think ktweaker will mostly work with other kernels except the custom parts involving thermal throttling, screen off governor, bt gov, gps gov, trinity color, uv, and maybe fast charge toggle
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I was simply suggesting a donation version that's all. Hundreds of $1s is better then sporadic $5 and $10s
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Maybe, just maybe in the future but since it's beginning, all the app does is FC on other kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
My phone refuses to be stable at 1998MHz. Is there any way to go above 1.4V?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Then lower your frequency by a step or 2.Your phone may not be able to handle the 1998Mhz..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
I am aware that it can not handle 1998 at 1.4 but it may be able to handle 1998 at a higher voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
The S3 is not made to clock that high safely. Sure you could up the voltage and fry the CPU, but now that isn't really what you want to do...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
I would monitor my temperatures of course. And maybe even come up with some cooling solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
With high CPU frequencies and high voltages you're likely to experience overheating, FC, and possible reboots but I guess it doesn't hurt to test and find out. Some phones can handle the load while others just can't at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
The ktweaker app has an option to throttle the CPU when it reaches a certain temperature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
Which is exactly why it would be okay to unlock voltages over 1.4

---------- Post added at 09:31 AM ---------- Previous post was at 09:19 AM ----------

Not really, high CPU frequency causes more heat and less stability. High voltage causes more heat and more stability.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Not always.. It can cause a significant amount of lag and/or crashes if the phone can't handle such high frequencies but like I said, some phones can handle it, others can't . Those that can will provide more stability. If yours is one of those phones then good for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
Your chip can always run faster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
no. it can't. A (another) chip can always run faster.

Your

chip can only run as fast as it can without burning up... also, these phones are pretty darn fast at 1800+MHz, why would you jeopardize your phone for another 10% speed that can't even be sensed in the real world?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
It could be an extra 1% and it would not matter, I just like getting the highest clock possible. It's just for the fun of the challenge.

"Your chip can only run so fast without burning up" then if I cool it, it will be able to run faster because it will not burn up.

I do not plan on doing this but I think this picture will make my point.

http://i54.photobucket.com/albums/g94/V2-V3/AMD Phenom II 940/HoursofBenching.jpg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
If you want to sit the phone on an ice pack like I used to do with my 2nd gen iPod when transferring movies just to get a record benchmark be my guest but your risking damaging the device for no point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Ok guys.. just let the man be and do as he pleases to his expensive toy. Lets get back on topic now, please and thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmobbjr:
The way I look at it is I spent $200 on the phone. I have already had 50+ hours of fun "putting my phone at risk". So far I have paid $4/hour for my toy and that price goes down every time I do some other idiotic thing with it. So really it is totally worth the risk just because of how fun it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsyl:
I always wind up back on your freaking kernel, ktoonsez.

I hate you.

You're too good.

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Ktoonsez, please make it so on voltages there is a set on boot check box. I find the other set on boot option quite annoying because you either don't or set it after a couple seconds but your phone may glitch after those seconds. Also, does the thermal control in extras use Fahrenheit or Celsius?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Just backup your Ktweaker settings then restore them after flashing a new ROM. You won't ever have to worry about touching the "option on boot" setting again, unless you're switching between TW and AOSP and adjust the settings manually, or stated otherwise by the dev. I only say this because with having the ability to backup and restore all of our kernel settings in one shot there's really no need to have any specific settings to set on boot when that one option will set ALL settings on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
that's not the best advice since the new ROM could have its own settings on boot or other changes that wouldn't work well with Ktweaker. You're better getting set up and being sure of the ROM (and turning stuff off if needed) before restoring settings (which might require clearing Ktweaker settings at that point).

Not that you're wrong, just that you're not giving a full picture to people who flash different ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yea. I edited my post lol but that's what I was referring to when saying, "unless switching between TW and AOSP and have to set the settings manually, or stated otherwise by the dev". You do indeed need to be sure you're good to go before restoring your settings.

Thanks for clearing that up though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeeahnick:
So i finally decided to install this kernel on my sgh-t999v using RootBox and this morning i was late to work because my clock was 25 minutes behind.... This has never happened before, any ideas?

ps. Actually the time it was showing on notification bar was wrong but in the settings it was at the right time but it was greyed out since i use automatic time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
What temperature is thermal control in? Fahrenheit or Celsius?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wi1son:
Celsius - The processor can get hotter than room temperature in March.

Sent by i535 with CarbonROM & KT747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Celsius my friend. Normally you would see numbers ranging between 40 and 55 before you go into CPU/GPU throttling and if that was in Fahrenheit measurements that would be too cold for your phone lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I had that before. Its you're launcher. Are you using apex? Reinstall it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeeahnick:
Im using nova launcher, it has never done that and ive been using for years and there hasnt been an update lately. If it does it again i guess i will reinstall it, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I can't believe how flawless my device is with your kernel and official AOKP nightlys from their site no issues no static screen no reboots. Thank you so much toonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No prob buddy :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Waze + KT747 Kernel issues

I've mentioned it before but didnt have any logcats or anything and still had tests to do...

So with KT747 stock settings (even tried with +25mv), im getting screen corruptions and short freezes in Waze.

It takes about 15minutes of usage before it starts doing it...

Same device, stock CM kernel, not encountering this issue.

Ive included a logcat with MANY errors in it...

A bug? Any idea? Am i doing something wrong ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I doubt that will show in the log cat. But if on stock cm kernel you don't see this issue I would look into your min/max freq and governor as well. you may need to increase your voltage more than 25mv, maybe not on each step tho.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I tried +75mv. Didnt help. I also got the issue while watching a video with vlc (hw decoding). Could this have anything to do with the GPU settings? Any suggestions for min max? I get the issue with stock kt747 settings but also with ktoon's setting from the third post.

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Let your max at 1512 and start with 378 and increase it one step at a time till you don't see it anymore. You could always try to disable hardware overlay in system settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I have a question, what happens if I have my phone set up to do back ups with tb and orange backup at 1am when I'm sleeping. With a screen off profile max mhz set
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Well what happened... did it back up or not?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Shouldn't be an issue. I have TiBu set to backup everything daily at 2am and Helium to backup to the cloud every other day at 3am. I offset so that there wouldn't be an issue but I don't think it would be a problem if they went together. I have my screen off max at 486. My backups go without a hitch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Any idea if this will help improve WiFi connectivity? Or do I have this totally wrong on this commit:

http://review.cyanogenmod.org/#/c/36122/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Probably not, they are just trying to use the code from the S4, it usually ends up causing more problems than it tries to fix/upgrade. But you never know. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aerdman:
Hey,

I noticed that the change log for the 5-17 build of AOSP-JB-3.4 mentions: "Fixed Bluetooth issue, where certain people could NOT connect to there device"

Is it possible that something in the 5-29 build has undone it? I can't seem to properly connect my bluetooth devices with the 5-29 build, but flashing back to 5-17 seems to fix it.

Is anyone else seeing this behaviour?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I'm not really having any problems anymore :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Bluetooth fix?

http://review.cyanogenmod.org/#/c/43830/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Same here somewhat. Connects fine initially but fails to connect automatically after a disconnect. Have to go to BT settings touch Uconnect, then pairs and works fine?????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I'm not usually someone that writes "me too" messages... but for bluetooth, yes I have the same problem.

I tried different things (leaving bluetooth on all the time, make sure to disconnect devices before shutting down bluetooth...)... and I eventually get the same problem that tallsilver and others have.

This is a clean flash or dirty flash of my ROM (Rootbox).

In the mean time, I'm using an other kernel (leankernel) with the same rom and it's working fine with this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Guys, this was merged in last night, next time KT has time to compile an update it'll be in there and should fix BT:

http://review.cyanogenmod.org/#/c/43830/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can't wait, op keep it coming
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Building up latest AOSP 3.4 to get you guys caught up :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
That's like 3 minutes ago.... what's taking so long???

Really, thanks man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
I know really it not like he supports like 3 or 4 devices some with 2 or 3 differerent carrier versions

Oh wait he does ( just joking sarcasm I know ur joking too )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 6.8.2013

1. Linux 3.4.48

2. Bluetooth patch from CM for people that cant get bluetooth to work

3. Updated wifi driver to version 1.61.47 from the GT-9505 source

4. Changed Trinity Colors to use CM's interface witht the 5 options. Still need to cycle screen off then on to take effect.

5. KTweaker: Trinity colors 5 options

6. KTweaker: TCP Options under "Extras" screen to tweak wifi driver. Experiment on your own to find best results :good:

ENJOY!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] picklerick:
I should be using cm version 6/8 or cm version 6/9 with kt's 6/8 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Doesn't matter. You can use whichever you like.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Toons, I still love you. Full homo of course. Justin, you can't have him. I have staked my claim.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I cheated on him with something leaner but I came back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Exactly why I staked my claim. Cheater. Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Awesome work as always, toons!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
New PA update and KT update. What a glorious day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Has anyone played around with above new addition yet? I can't seem to figure out any differences with changing this section. Any suggestions and what improvement should we see with this?