yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahfu25:
Hey wassup ktoonsez. If I restore from a nandroid backup that has the stock rooted kernel do I still have to install the drivers afterwards if Im coming from your sammy kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No nandroid overwrites everything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bigwill63:
My wifi is not working on the latest build, it boots and everything else seems good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahfu25:
Muchas Gracias! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Reboot to recovery, wipe cache/dalvik and fix permissions again - reboot, then after it's all the way up, reboot again. Bet it helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
Bet it doesn't. No wifi here either. Running very smooth otherwise.

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kurant1:
8/27 Kernel, 8/26 AOKP, fresh install. AOKP booted with wifi working on initial setup. Went back, installed kernel and wifi was not working. Also, did fresh install and installed both together before initial boot, wifi didn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Reuploading, be back up in a minute, for some reason, the drivers didnt copy in. Thats why the wifi isnt working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Modules are missing. I'm sure ktoonsez knows and will get it fixed for you guys soon. ;)

---------- Post added at 09:15 PM ---------- Previous post was at 09:15 PM ----------

;) "stuff"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
Hmm. I keep getting ktweaks has been granted su permission.

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Didn't follow my long steps because I'm at 5% battery, wifi also won't turn on, going back into recovery and wiping cache/dalvik didn't fix it so there is something there... edit, i see...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fatboy547:
Will this work on T-Mobile aokp? Will it mess up rotation? Or anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Lol my WiFi is working perfectly.....

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Mine works :confused: and before anyone says it I installed the newest jb kernel....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes

---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------

You can look for yourself. But the zip ktoonsez posted doesn't have any modules in it. So it sounds like you got lucky and some let over bs might have stayed in you system. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
Lol. That wouldn't be the case. Wifi module usually only works with the kernel its compiled with.

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Not doubting what your saying, just that mine worked. Maybe it'll work twice as good after he uploads a new one :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Back online
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Lol. It could definitely be the case because I'm using the latest kernel with the modules from the last release just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Most people that were already on my kernel would have been fine, its people coming from another kernel or an old old version of mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
Ok

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BoostRoid:
My phone is waaayy too fast now! It just slipped out of my hand! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Sounds normal to me.

If you don't like seeing that notification, then go into SuperUser or SuperSU (whichever you use) settings and disable repeat notifications. It's what I always do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
I did.

Wifi was kinda working. Just shut off and won't come back on.

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Mine also said it for some reason and I keep SuperSU to grant and never notify... even double checked after I granted it's permission...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Redownload, my script didnt put the modules in the zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
I grabbed the new zip. I reboot and it seems to be fine. This is the smoothest kernel by far. Thank you for your work

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
SuperSU was always flaky for me with notifications. Even after telling it to not give me repeat notifications, it often still did.

I went back to Superuser for this reason. Superuser works better for NOT giving repeat notifications.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I've kinda noticed that, but I bought it, so might as well use my money...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidRC1:
I want to try this kernel on my T-Mobile sgs3 running AOKP..but I read if I go back to stock kernel my WiFi won't work unless I get the new WiFi drivers..so where do I found this or can I just reflash ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeyinid:
Just flash the rom

Sent from my AOKP'd GS3...#ftw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
You would just re flash your stock Tmobile kernel... Sure someone in your dev section has it posted. Or flash a stock rom image with the kernel included.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
go to whatever rom you are running (you said aokp) and grab the drivers from system/lib/modules ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
I just have to say it again, best kernel ever! I love the frequent updates and optimizations! And the tweaker is the best kernel app I've ever seen!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mike216:
Is superstar goddess likes it it must be good. She's a androidholic like myself
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidRC1:
So reflashinh ROM is okay?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mike216:
Just flashed and took my first look at the tweeker. It took me 2 seconds to see it ****s on set cpu. For us at least! Set cpu is good for general use but this monster has more tweaks then all the junkies down the street. There's a lot of them out there

Holy **** its buttery!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Thanks ktoonsez!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yeah.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidRC1:
K. Antutu isn't working for me when I do a test it just closes on me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats a sign that you dont have enough voltage for whatever Mhz you are using. Also it usually closes on the first try anyway, waaaaay to many bugs in that app. Task will confirm too :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
Hey ktoonsez,

Awesome kernel! Running smooth, quick, great battery life and your app is beautiful

Are you thinking of implementing a +/-12.5v button to the voltage table? Would make undervolting much easier !

Thanks a lot again !

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidRC1:
Aight thanks I oc'd at 2.1 and it closed but 1.7 ran but close half way o well..this kernel is fast (too bad it doesn't solve my WiFi problem) but I'm happy with the kernel so far great job
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That app will force close and do weird things. Don't trust it. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
IMPORTANT

Probably shouldn't use the Screen Off Mhz thing, it seems that the android system is killing my Screen On/Off intent after an hour or 2 with screen off so the Mhz never gets set back to the original Scaling Max. Nothing to worry about, your phone will just be super laggy until you raise it back up mannually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mike216:
So if never set anything then we should be ok or should I remove the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you leave it at "Selected Scaling Max" you will be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mike216:
The UI moves insane on this monster!

I haven't seen any earthquakes on this speed demon neither. I just pray battery holds up ok. I don't even care if it's not great, (however I hear it is) I just want it to get me through the day. So far I'd say it's perfect. Very happy with first impressions. Good night!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidRC1:
Here is a benchmark I did for people who like seeing them...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alex2x3:
I get so excited about every new release its ridiculous. :p haha

But for some reason this new kernel doesn't boot for me. I wipe cache, dalvik, and fix permissions and it gets to the updating apps, and then gets stuck at "starting apps"

Tried three times, and made sure that the download was not corrupt by downloading it again and checking that the md5 match up.

Any reason for this? Could it just be my phone doesn't like this release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Dang got excited til I saw it was jb only update. Lol. Plan on bringing the new linaro code to ice sometime in the future ktoonsez?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
I'm not running Set CPU or any other CPU app.

I went ahead and wiped everything. Flashed CM10 instead of my usual CM9. And the 8/27 version of this kernel.

Then set my CPU overclock again. It still doesn't stick. I have to go back into the Ktweak app and click "ok" to where it says my "min/max doesn't match the settings".

No problems here with AnTuTu btw. Got a 81xx score.

Not sure why AnTuTu says my CPU is 1512mhz though.

I was overclocked to 2.1ghz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] appdroid:
times like this is when i feel like noob!!! Can't wait for OC!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
Oc not working. Shows the Frequency in setcpu but it never goes to it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
Yeah, the OP said he was having trouble with this in his first or second post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Installed and running flawlessly. Not gonna screw with governors or whatever yet. No real need to.

Edit: So I noticed the battery started draining much too fast while not in use, so I flashed back to the stock, insecure kernel, and then wifi stopped working, so I had to flash back to this to have it again. I'll probably just flash back to stock, reroot, etc and wait til this kernel matures a bit more. Seems very promising.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Horrible battery, stock settings lost 10% in an 10 min screen in time back to stock kernel. I'm in diet ics going to revert to rooted stock if it continues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bravomail:
battery life is bad. but kernel still a keeper! just let Ktoonsez fix the bugs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
Agree^^^ +11000000000

Stock AT&T SGS3 rocking KT747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
A few posts back they were trying to nail down the cause and several had the diet ics rom installed. May or may not be the root cause, but a lot less complaints with stock rom and ultimatum rom. 2cents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradld:
It's not Diet that is the sole cause. I am on stock and battery life remains horrible. Kernel needs battery work otherwise it's great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
That's why i'm rooted but just staying on stock for awhile. I wanna let the devs do their magic. The phone just came out so I have to be patient while our devs work hard. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamesbra:
I'm on diet 7.4 and an having no battery problems aside from an occasional rogue app. Xda has been the biggest problem so far. Switched to tapatalk and fixed the problem. Fwiw I was having the usb mounting problems intermittently and fixed it completely by uninstalling the Sammy drivers and letting windows use its finder service. Now it mounts every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
I must know, what have you modded to not have the AM/PM at the end of the time, and to get the Blue Text as well as back to the H+ icons instead of AT&T's 4G?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
If you want to go back to the XDA app, the battery drain issue has been isolated to the ads. Either use the premium version of the app or install ad free, the excess battery drain should disappear after that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iBotPeaches:
Ahh, just bought premium. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Sorry for not using BBS, or anything more definitive, but I took the phone off the charger while I slept and turned off mobile data. Here is what I got:

It should be noted that I do not have lte in my town, but this never happened on the stock kernel o_0

I like the feel of this kernel, hopefully these bugs get DDT'd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Thanks for all your hard work, op. :)

Just to add, I installed the latest kernel last night, switched to ondemand/noop to standardize with you, then switched the stock rom's phone settings selector to Power Save: OFF (in case that was creating a conflict), and charged my phone overnight. This kernel takes much longer to charge than stock, for some reason.

I woke at 7:00AM MST, unplugged the phone, and left it on but didn't use it a single time for 2 hours exactly. My battery was at exactly 80%. It drained 10% an hour from doing nothing but deep sleep (97%).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok, thanks for the feedback. Looks like this kernel is garbage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Similar story here ...

I have a similar story. I'm using a stock Rogers ROM, and when I normally go to bed, around midnight, it generally loses 5-8% overnight. During this time it's in airplane mode. No data, no wifi, pretty-much nothing is on.

This morning I woke up and I had only 6%, and it was about 96% at 11:30pm last night.

Now that's horrid!

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KryptosXLayer2:
Not directly attributing this to the kernel because I think things were a little screwy before, but has anyone seen weird stuff going on with the SetCPU widget? Once you click on it to open the app, everything looks normal, but sometimes my widget displays things like 0 max and 0 min, or will randomly display my min to be at least 1GHz! I click on it and it shows the min being set correctly to 384MHz, but what good is the widget if I can't see that there isn't an issue with the processor speeds being incorrectly adjusted higher than they should be?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Do you have a free hour or 2 to test with stock scheduler and governor? If so, set this:

1. Scheduler to stock "deadline"

2. Governor to stock "Performance"

3. Note your battery

And lets see if it does the 10% again. Also are u using 7/7/2012b or 7/7/2012?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
I'm still amazed at how smooth and stable this is with the high levels of oc and sweet ability to heavily UV!

I can run the 2.1Ghz step but not yet 100% stable so I'm more then fine with 1998 and every other clock works perfectly! And my battery life is just amazing with the UV I can do.

My levels are as follows:

96 min - 1998 max

780mv min to 1185mv max w/ variances of -55mv to -135mv below stock on all the steps in between. This = incredible! Sweet performance AND battery life = :)

I've got this thing as low as using only 14mA during deep sleep! I use a 4300 mAh battery now so that's only 1% every 3 hours. So I basically only use 2% when I crash at night and get up the next morning. And I now easily get 2-3 days with fairly heavy use and that includes 7-8+ hours of screen time. Heck, at these low levels I could technically be in standby for almost TWO WEEKS! (Actually 12.5 days or 307 hours). That's amazing!

I'm now getting the performance and life I should be and have always wanted on these things so thanks again and keep up the good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
My settings in ktweaker don't stick either unless I open it after reboot, I thought maybe that was kinda a failsafe lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Try checking the lock frequencies box...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BoostRoid:
That's frigging insane dude...wow

Sent from the best smartphone in the world!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rfb813:
The Kernel has been great. Good battery life. I have been conservative and only oc to 1674 and min of 384. Will try a few voltage options. I am having a problem with what the touch boosters are doing; I have left them at the default. Has any body tried different settings and how have they responded. Any recommendations or clarifications?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Aww, hee hee, thank you! This really is an amazing kernel! I need to learn more about voltages though, since I just leave then on default since I haven't read up on that yet. I'm sure that it would be even more amazing once I get that all figured out.

Also, I have been trying out all of the different governors, some I have used before and some I haven't. That's the other amazing thing about this kernel, it has a million governors in it!

---------- Post added at 07:17 AM ---------- Previous post was at 07:14 AM ----------

Same here, that seems to be the only problem with this version, but I'm sure it will be fixed soon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d3athsd00r:
I do believe that when I have to upgrade (2 years?), I will only go to the phone that task and/or ktoonsez pick up.

Keep up the good work. 8/27 version running perfectly with the 2.1 OC and the UV posted in third post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baseballkyle:
KTweaker crashing

KTweaker crashes ("Unfortunately, KTweaker has stopped") now post 8/27 kernel install on latest AOKP by Task650 & Ktoonsez. Yes, I cleared cache, dalvik and fixed permissions after install. Anyone else running into this? Thanks! :cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neubauej:
I just thought I'd mention that if I mess with the touch boosters on my device I get random reboots but if I leave them stock I don't.

Playing with the voltages doesn't seem to make a difference but the higher I put the booster MHz the more often it random reboots.

Thanks for the excellent kernel an app!

Edit; I'm currently on the Sammy version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkeaver:
ok this last release (not that the rest of them didnt) deserves some HUGE props!!

Confirmation number: 80479327T35080408

here is my thanks to you for all you have done:cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks bro, nice :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You have to be on the latest CM10/AOKP for the JB kernel to work. This has all the latest audio patches in it and will hang on Starting Apps or boot loop's for breakfast without the newest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
no thanks. i would like to run something touchwhiz with the new JB kernel. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
MALO! Stuff!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Did anyone ever figure out why the kernel settings won't stick yet? I'm sure the dev is working on it, just seeing if anyone has a way around it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They stick just fine, no one has given me any screen shots, what ROM they are one, what the toast messages say. Works perfect on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidRC1:
Sticking good for me

---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------

What governor everybody using? I've never seen so many lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
no need to fix something thats not broken. they stick just fine. ;)

i would clear data for the tweaker app, then boot into recovery, wipe caches, and reflash the kernel for good measure. the resetup you kernel settings and see if they stick after that. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecoach1999:
Followed OP instructions, and all working fine. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ForcedZucchini:
I'm getting this also. I'm on 8/28 nightly of CM10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
I got that too. I cleared data for ktweaker with titanium backup and it was fine after that. This release is butter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Clear data on my app and see if that clears it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bigwill63:
Followed the instructions in the OP. Still getting call echo during normal handset calls, flashing back to stock CM10 fixes the issue. Made several attempts. Wondering if anyone else has the issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Is it intentional that when trying to select the mHz for the screen off profile, all the values end in three extra zeros?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Thanks, that worked! Not sure what happened, I'm sure that when I first installed it that I wiped caches and all that. Must have been a fluke! All good now though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alucardis666:
Anyone got a good voltage table going they'd like to share to give me a baseline of what's possible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerrygooch:
I should have a new voltage table once I get my phone to a fairly stable state. So far my phone seems to handle undervolting pretty well. A few days or so more and I'll post. Class and work make it difficult to play with my fancy phone ;)

**oh and great job as usual ktoonsez! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
There is an older table in the third post.....personally I've dropped mine 75mV across the whole table with no issues, but, each phone will react differently. Some won't handle undervolting very well.

Noob question alert lol. Running two different frequencies with the same voltage use the same amount of power. Example 384 @ 825 mV use same power as 486 @ 825 mV. In the voltage table the bottom 5 freqs are the same voltage, so will a freq of 96 MHz use the same power as a freq of 486 MHz set at the same voltage. I think I read somewhere that the power consumption would be the same but would like to make sure from the people that know :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Hi, I've attached screenshots of the issue.

Had it on CM9/AOKP and now on CM10/AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aalh:
now we do know

grabbed 8-27 today and still cant get past upgrading 4 apps before it freezes and reboots:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alucardis666:
Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d3athsd00r:
Ondemand...always

Ktoonsez, do you ever change any of the settings for the ondemand governor or just run with the stock settings?