yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I have no clue what is up with that Benchmark app. Antutu is a little more reliable as far as repeatability as of late. Some phones just dont benchmark well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
You should probably try reverting to default setting (after saving current settings, of course). and seeing if you still have the problem (and it's stutter, btw; slutter is much dirtier)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
For sure... I tried all that been testing this kernel with the same rom for months...

Only started stalling since 8-30 release, I wiped ktweaker data clean, revert to kernel default and it still crashed and rebooted many times... very unstable.

Maybe its time to try a new rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drakeymcmb:
Will there ever be gpu overclocking in this kernel thanks ktoonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Did some more tweaking... Been running this all day with no problems.

*knock on wood*

1728 MHz - 1090mV

1674 MHz - 1075mV

1512 MHz - 1065mV

1458 MHz - 1050mV

1404 MHz - 1040mV

1350 MHz - 1025mV

1296 MHz - 1015mV

1242 MHz - 1000mV

1188 MHz - 990mV

1134 MHz - 970mV

1080 MHz - 950mV

1026 MHz - 930mV

972 MHz - 910mV

918 MHz - 890mV

864 MHz - 875mV

810 MHz - 860mV

756 MHz - 845mV

702 MHz - 830mV

648 MHz - 815mV

594 MHz - 800mV

540 MHz - 790mV

486 MHz - 780mV

384 MHz - 770mV

192 MHz - 760mV

144 MHz - 750mV

96 MHz - 740mV

Ktoonserative / BFQ

Touch Boosters = default values

Screen Off Profile = 486 MHz

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
:o i just realized ur a mod lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Thanks man, I'll give those a shot...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I enabled it for next build just for the fun of it. Trust me when I tell u you will not see any improvement in Benchmarks at all. I already had it in the kernel for 2 weeks, several weeks ago and none of us saw any improvement. So I just added it for all the people that missed out on it so they can see first hand. It will be overclocked to 480000.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MCKang25:
What about GPU undervolting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
There is only 4 steps, no need to undervolt and cause issue with redraw. If one day, I make it into 8 steps or something it might be worth a little.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
I'm running the latest jb kernel on aokp and I cannot get my overclock settings to stick. I set them, put the phone in my pocket for half an hour and when I unlock the phone the clock settings are back to stock. I've tried clearing data for ktweaker and not closing ktweaker with no luck. Is there something I'm doing wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Check the Lock Frequencies box, that is why it is there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Not wrong necessarily ...just not right lol. Check the lock freq box in ktweaker and reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
u get ur lte fixed up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
I've tried that but my settings still revert back to stock after the screen has been off for a while. I'm using the ondemand governer set to 2100mhz. I guess I will try and lower the clock speed a notch and see if that is the problems. The kernel is awesome by the way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Try to uninstall KTweaker, reboot once fully. reboot again and install my latest kernel again and see if that clears it up. If it still persists, its the ROM that is screwing up the locked files or something along those lines.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
Thanks for you help. I'm trying this now. I'm on the latest aokp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Hell no. I'm calling the orange and blue when I get into work tomorrow
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Interesting - what will the Gators do for you? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Man I love football season...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Thinking if I can get a reprovisioning on the network I can fix it. Or so I hope lol

---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------

I like the cheerleaders. Does that count? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
So far this appears to have worked. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dh2225:
So will this kernel work on stock At&t Galaxy S3, out of the box rom that is rooted?

I want to see if overclocking can fix the slow framerate in games like NOVA 3 and Asphalt 7.

I can't believe that the GPU is not good enough to run those games well.

If anyone has a way to fix low framerate in those games can you share what you did and rom you're running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
... And has CWM installed. :p

Just make sure to pick the right one from the OP.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Absolutely...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Warrior1975:
Running your kernel the last few days on AOKP, d2tmo, man this thing flies. Thank you so much Ktoonsez. Love this kernel. Full OC and not one issue...doesn't even run warm. Amazing.

¶0w3®3d b¥ @OK¶™...GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Question for those of you who have undervolted and have a screen off profile (with a low speed like 192 or 384)

Is your notification led working at those settings ? I'm still trying to tweak my settings but my led seems to break whenever I set a screen off profile. Currently using the latest version of the kernel and I'm on cm10 clean install. My 384 is undervolted to 825mV and 192 is at 805
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanmaini:
Hi

Not sure if it has been reported. The wifi signal is am getting is very poor. On stock rom and a stock kernel I was getting a 2-3 bars in a location where I am not getting any signal. Not sure if it's the rom or kernel.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
Settings wont stick.

For anyone running this kernel on AOKP how are you guys getting your settings to stick? I've tried rebooting, clearing ktweaker data and uninstalling ktweaker rebooting the phone and then reflashing the kernel(this actually worked until I changed the clock speed to save some battery and my new settings then wouldn't stick).

Could ROM CONTROL be interfering with ktweaker? At this point I'm just throwing crap at the crap at the wall to see what sticks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
I recommend not undervolting. I believe that was the problem to my touchscreen stopped working that I had to do a restore. I only undervolted to that startoff point too!

---------- Post added at 11:20 AM ---------- Previous post was at 11:12 AM ----------

You could use KTweaker and make it to lock frequencies and make sure you set it to set on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Mine is the same as always. Most likely it is nothing really to do with kernel or ROM. Its just week signal from hardware to hardware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
Ktoonsez can you help me with my touchscreen freezes with the latest kernel or AOKP rom i'm not sure which is causing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I'm on the road for work man. Did u do a full wipe? I'm on the same thing as u and all is perfect
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
I did full wipe and found out that it was ktoonservative... Something must be wrong with the governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Not something wrong necessarily - works fine for me - just your phone doesn't like it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Seems to be working quite well for me too. Getting a reboot whenever I take it off the charger, but that barely counts as a nuisance. Not sure if its governor, kernel, ROM, or the idiot pushing the buttons anyway.

Not to mention, I got pretty aggressive with minimum and screen off frequencies.

---------- Post added at 06:53 PM ---------- Previous post was at 06:43 PM ----------

Anything that sets at boot will interfere. The way I understand, even if its been uninstalled. So you have to get rid of the old boot profiles of setcpu and stuff too. It also works much better if you don't use the performance settings in ROM control.

There was a post on it a few pages back, but I can't find it now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Or phone just might not like it or u manually set some bad parameters. I am also using my gov
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Been using your governor since release ktoonsez, no issues here either. Been flashing to much to get a good battery scale, but stable as a mofo. Not one reboot, and smooth as anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
I have had a couple of reboots not sure if it was ktoonservative or screen off profile

Been using pegasus gov. And haven't had reboot since...fingers crossed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
I flashed the 8/31 Sammy today and ktweaker force closes. I had to roll back to 8/24 to stabilize the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sultanqasim:
I'm currently running your 8/31 AOSP JB kernel with CM10. When I first upgraded to 8/30 from 8/27, I kept my (completely stable) voltage and performance settings from 8/27. I started noticing random reboots, and thought a new bug had appeared in your kernel. I tried ktoonservative and got a slightly higher frequency of random reboots. Then I reverted KTweaker to default settings and found the phone became rock solid stable. It turned out that my phone was able to stably handle undervolting down to 815 mV with 8/27 but I had to raise the minimum to 860 mV with the newer kernels.

I'm currently running ktoonservative and noop with my reduced undervolting from 192 MHz to 2106 MHz with superb performance, stability, and battery life. Thanks once again ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
Same thing is happening to me, random reboots... I re download 8-31 and re flashed and its still the same, receiving phone call crashes even.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
I had a couple of crashes receiving calls. Set the voltages back to default and reduced everything by 10mv and using noop I/O and pegasus gov. So far so good. Maybe that will help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Anyone else having their phone get as hot as kate upton since flashing the newest update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Whos kate? And its supposed to do that. Your using all the resources on the phone when flashing a new rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Okay i wasn't 100 % though just because I just upgraded the kernel, not the whole rom. Plus now it's been 3 hours since then and it gets really hot, really fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
I'm on the stock rom and all of your kernels before the latest ran fine. 8/31 causes the phone to become unstable. I've done the cache/dalvik wipe and fixed permissions. The phone just doesn't like 8/31.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Just read thru the last 5 pgs and didn't see a thing bout WIFI. I was running 8/31 CM/AOKP with MIUI and I was getting WIFI disconnections about every 20 to 30 mins. I tried numerous settings..... from stock to changing Governors, Scheduling, Undervolting and Overvolting. I grabbed WIFI Fixer from the Market. Still no dice. Just in case it may have been ROM related I switched to AristodemosII but still was getting the WIFI drops.

I switched to faux's latest Sammy kernel and haven't had a WIFI drop for about an hour now. I'm not complaining, just reporting my issue. If anyone has any suggestions I could try, or have an idea on what my problem could be, would appreciate the feedback.

For now I'm just gonna go with my phone doesn't like 8/31 and revert back to 8/24 and see if the issue remains. I didn't have any WIFI issues with 8/24, but also didn't see anything in the changelog that has to do with any changes with WIFI in the changlog for 8/31.

Love KTweaker and the enormous amount of options with KT'S work..... hate to run any ROM without it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Did you try other modems? Might not help, couldn't hurt to try...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Nah..... since I changed to faux's and not having the WIFI drops I just gonna figure my device doesn't like 8/31.

Just weird how these things go tho. I understand every device is different when it comes to different settings...... but I haven't seen one person have an issue with WIFI.

Appreciate the feedback bro.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Same here, I still just can't get it to stick no matter what.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Never seen that app before. Try stock kernel and see if it comes out the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Cool and thanks, would love to see someone do this on stock kernel too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Just some good info

I flashed back to stock for the next hour or 2 just to test battery and right off the bat I can report this:

1. SetCPU and Voltage Control both do the wierd thing where it reports min and max Mhz at 1512 randomly. Must be a compatibility issue with our phone. So anyone worried that it was just my kernel, it is not, it is the app misreporting it.

More to come after 1 to 2 hours on battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
y u take peoples ability to blame you for something that happens on stock too? they need someone too blame dude. :highfive::D:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Yes that's what mine does stock not even rooted yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What is your scheduler and governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
i went ahead and bought setcpu had no need for it until now, cappy used nstools, but after a rom flash, nstools decided it was gonna install itself, and running stock kernal i knew it would just sit there and didnt bother to remove it... when opened tho, it only had the sammy options like you said, performance and deadline... after flashing ur first kernal, i opened it up, it had more options... i wonder is it compatible...

---------- Post added at 01:37 PM ---------- Previous post was at 01:08 PM ----------

an hour has passed, only one rogue phone call lasted bout 30seconds...

dropped from 66% to 56%....

not on DietICS like before, on kyanRom...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Went back to your first release and everything seems fine now. No drain :D. It's been an hour now. Using on demand and bfq.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Sorry, hadn't been home for a while and just nandroided back to stock before seeing this message. For reference, I was using 7/7/2012b, but it exhibited this behavior on both kernels yesterday (the only two I tried).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Xdenwarrior:
Little offtopic question will installing this kernel wipe out all settings, apps, data, media etc i already have on my phone? My quess is it wont, but should i worry and back things up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
No it will not wipe anything

"All this knowledge is giving me a raging brainer!"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
I just woke up. Having the same issues as some of the others. Here's what I plan on doing:

This is the stock ROM I'll be using

Device: SGH-I747

Region: ATT (AT&T USA)

Version: I747UCALEM

1. Flash stock with Odin (and do factory reset and whatnot if necessary)

2. Leave it on stock settings (don't disable wifi/4g/whatev)

3. Log battery drain after an hour or two

4. Root

5. Install your kernel with whatever governer/scheduler settings you want (in SetCPU)

6. Leave the settings the same as what I used in step 2.

7. Log battery drain after an hour or two

Not gonna start yet because my battery is too low....but I'll do it sometime. Any advice as to what to change in my process?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks good. When you switch to my kernel, use SetCPU to set scheduler to deadline and governor to performance. That way the 2 kernels will run with the same settings. Thanks for the info and feedback.

Also, you had said everyone else. We have over 400 downloads so Im not sure how many people are seeing the crappy battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
So...by default, the Stock ROM will have those settings too?

I didn't mean for it to be offensive. I have the same problems everyone else is posting about** :D

Also, I bought SetCPU strictly because of this kernel. I haven't used any of this stuff prior to using your kernel (I'm saying I'm ignorant and want to do things correctly). It's a very polished app. After setting the scheduler to deadline and the governor to performance, do I need to restart or do anything else to make sure the settings stay?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
i too had crap battery on this kernel with diet ics. dont get me wrong i really appreciate your work here, just letting you know my experience. phone 100% to dead as a door knob in 7 hours, with little to no use[hour screen on, 20 min pandora]. also checked to see if i had the cell standby bug causing drain, which i didnt. flashed back to stock via the cwm zip a few pages back for the time being as i need my phone to last through work atleast. i will be back for this though when it matures, or maybe when i have time to test.

thanks again for the kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No problem, just dont want others to get confused when they read your statement. They might assume all 400 people are having extreme drain, thats why I needed to say that. Anyway, yes scheduler to deadline and the governor to performance matches what the stock is by default. DO NOT reboot after setting the scheduler and gov, that way you dont have to have it set on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtcarey:
I had really bad battery with this kernel... went back to rooted stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I just want to thank you ktoonsez for all your work past,present and future. What ever little issues are going on im sure will be resolved. Ktoonsez is one awesome dev and glad he's here.

Zepp's V6 SuperCharger...I put that **** on everything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sblees:
Thanks for the reply. Unfortunately the stock kernel does not output phone audio through the car dock. Maybe someone will modify a kernel that has this feature. Hint hint. Lol

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KryptosXLayer2:
Was having issues with the phone not keeping clock speeds, but fixed it by all the normal steps people have said a dozen times on here already - remove SetCPU's "enable on boot" setting, locking KTweaker's speeds, etc....

my REAL issue was all the lag on 8/31! I literally could not drive down the road with Google Navigation and Google Music running, and flipping through emails when stopped at a light! The music kept breaking up, sounded like I was making my own remix every time I scrolled on the phone!

Reverting back to 8/24 for now, hopefully just a small bug that needs to get fixed, 8/24 was great for me though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1

Gone back to 8/24 as well. All other conditions set equal, it's much snappier and feels lighter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
Good I'm not the only one noticing a little bit of lag!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Your phone (its hardware) is a rare one...for sure as 80%+ will never function (stable) at voltages that low..no way at all. You're very lucky to be able to function at all with that voltage table.

My (main) phone too is a rare one and can handle great oc and UV but even I can't get that low! Wow. Under 800mv all the way up the first six clock steps....incredible. I guarantee that most users here that try this will report failures.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I'm having no issues with his table... really glad he posted it, I didn't want to continually test UV settings...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
I've been running the same table, with slightly lower voltages up top, without a reboot yet either. Thanks a lot!

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
hey do you mind posting your table? i'm really lazy man...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Google that. Lol. I'm running the ktoonservative gov and it has been great. No lag. No freezes and no reboots. Good batt life and responsive when I need it to be.

---------- Post added at 12:30 AM ---------- Previous post was at 12:28 AM ----------

Just use ktweaker. You cant use both. Clear cache in ktweaker and lock frequencies and reboot and fix permissions then go in and relock it and see if that works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
So I have to test my own UV settings like everyone else? but.. but I'm really lazy man.... :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
That's how it works. Lol. It would be cool if someone could write a script that applies all settings. I mean I know we can save prefs and restore but something a little more quick where we can have multiple settings and we can all test each others UV and oc settings.

Edit. This post made me a senior member again since I lost it on my old account. :) :thumbup::):D:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
Sometimes Small Lags

Overall 8-31 kernel is flawless the only thing I am experiencing is some lag here and there, sometimes I have to reboot the phone to bring everything back to normal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lunercrab:
Oddly enough my phone likes 31 release. Last one it didn't have a problem with was 8/3. But I'm bummed I really can't undervolt at all. If I go below 384/925v on the lower end my audio becomes extremely distorted :( but other then that my phone has seen no lag or major issues so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Hit some idle time and started playing with the "reboot on unplug" thing. Looks like, on my phone, it was just a matter of using any I/O scheduler BUT cfq with ktoonservative. Left min freq and screen off at 96mhz and the voltages the kernel shipped with, just changed scheduler.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s2556:
I got lucky with mine. I am running it about 25mv lower than his and its working great no audio glitch or reboots or anything. Also no issues with overclock either. Unfortunately I cracked the screen on it last night :( so I have to decide going through insurance and probably getting a worse chip in the new phone or replace the glass my self :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Dang... so no way to post your table for me then... j/k... that does suck though man I managed to get a good one too... wouldn't want anything to happen to it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
bah anyone else having troubles with their LED notifications not appearing when they set a screen off profile?