yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Lol, I know, I know :D. Im an Unrecognized Developer, LMAO. :cyclops: :p :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Good job ktoonsez. I can't wait to under volt this baby :D

Don't care about over clocking it since it has more than enough speed.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Thanks for the quick reply. It may be that I'm just Doing It Wrong™. ;) That's always a possibility. I'll do more checking and see.

On another note, I don't have experience with anything you've developed until now (was on a CDMA HTC Hero for the last 2.5 years), but I have to say you're one of the most communicative folks I've seen on here. It is very much appreciated, and I'm looking forward to testing out anything else you produce.

Side note: Unrelated to this thread, but my only annoyance thusfar is that, much like you ktoon, I live in a _very_ sunny place (Albuquerque) and can't read my S3 in direct sunlight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man. I came from the AT&T SGS2 forum. I have 4 kernels in that forum and 2 ROM's, MIUI and AOKP that myslef and task650 work on together.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shabbypenguin:
from my understanding they had rec dev ages ago and recently changed it around so that themers and contributors and so on can join in. people like myself who got in on the old program are part of the rec dev group but you guys share all the same benefits. im pretty sure there is a post somewhere that explains how to jump titles tho :)

edit found it http://www.xda-developers.com/announcements/xda-recognized-developer-program-expansion/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Indeed. I've gathered that by reading this thread. Looking forward to it. :)

Also, for the people having trouble getting Windows to detect the SD card, no reboot of the phone or PC is required. It's as simple as toggling the USB mode from Media to Camera on the phone when connected to a Win 7 Pro PC. Works every time!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
I'm actually hoping that you and task may help with a CM9 port rather than AOKP. Just always preferred CM9 for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
no cm9

yes aokp :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Not in our eyes, and that's what counts!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meleii:
Lol ktoonez so far you have your own sub forum. How would an unrecognized developer do such a thing. *sarcasm* :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Lol, I know, I just went back to the main SGS3 to see what was going on with the breakout of the forum and saw that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Lol @ this the only thread in the new forum. Rightfully so....its been the only REAL developmwnt so far on this device. I'm as flash happy as the next guy, but i WILL NOT flash any of the current "Roms" out cause simply....I dont trust them. Most are first time devs, some dont own the phone or have just got them, and when they do get the phone they brick them! lol no thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
I'm certainly no authority here, but I was thinking that charging from your PC was always slower than from an AC outlet. Whenever I'm connected to PC the phone charges very slowly. idk, could be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I would try one if it had anything beyond debloating/deodexing (with a nandroid first) - as it is I'll wait for Task or PG if he decides to jump in (well, if he has time :D).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Exactly....they do more harm than good at this point. One could easily debloat through TB and not worry about bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
You are correct. When AOKP comes to this phone, it will probably have the fast charge option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
can't seem to find out steps how to install a kernel. I have only ever installed ROMS.

It looks like thesea re the steps though

Wipe Data / Factory Reset

Wipe cache

2. Wipe dalvik cache

3. Install rom and gapps

advanced => reboot recovery

7. Flash kernel

8. Wipe cache and dalvik cache, and fix permissions

9. Reboot system

I am currently on AOKP newest update with its gapps.

So does this mean I can jump to step 7? If so, do I just install zip via sd card and then those next steps?

Thanks, just don't want to brick phone

PS I also assume I download KT747 Kenel AOSP JB ATT 10-16-2012 since i have newest AOKP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes on you have the right kernel downloaded and yes do Steps 7, 8, 9:good:. ENJOY THE GOODNESS:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Ahhh you lucky dog! everyone says it's super awesome.

This is how i imagine everyone who's running this 10/16 kernel.

OH HEY Ktoonsez, check this out....

Nice score, thanks for all your work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerrygooch:
Yeah, I figure I'll just manually install the kernel after the fact. the values bellow have been the settings I've stuck with the last few days. I haven't had time to really tweak each speed to it's absolute minimum UV.. that's on my todo list and I feel its going to take at least a week or two to tweak each value to a stable minimum. My next goal is to learn how to tweak the I/O Scheduler and Governor for a good balance of performance and ultimately killer battery life.

Mhz - mV

2106 - 1185

1998 - 1160

1890 - 1135

1809 - 1110

1728 - 1085

1674 - 1060

1512 - 1060

1458 - 1035

1404 - 1035

1350 - 1010

1296 - 985

1242 - 985

1188 - 960

1134 - 935

1080 - 910

1026 - 910

972 - 885

918 - 885

864 - 860

810 - 835

756 - 810

702 - 785

648 - 785

594 - 785

540 - 785

486 - 785

384 - 760

192 - 735

144 - 735

96 - 735
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
I'll ask again, is that your c6 kt?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, thats awesome, its all 8's :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, never saw it the first time. Yep, my baby:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
My max mhz is 1512..do we have a differnet phone?

PS. Everytime I click on IO scheduler my phone freezes..is this my fault?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Your middle name must be horsepower, if you tweak kernels like this i can't imagine the trap on that run

Sorry about the again, i asked that like a month ago and was always curious
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
thanks for the update KT..zero problems with your and tasks aokp and tonights extreme kernel running great..last few kernel releases have been untouchable...so fast..completely stable...thanks for all your and tasks work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Read the OP. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Still getting flicker but I didn't UV anything below the touch booster 1134 value, am I doing something wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
So what all should I be looking for when testing stability at voltages I am testing?

I am coming from OCing computers, and there its just a crash or an error in a stress test. For some reason my phone seems slower after running Stability Test. The test doesn't give any errors, but everything feels slower. From how it works on computers, slowness isn't something you get from undervolting... A little clueless here.

I am on the Task650 AOKP with the post 10/14 kernel on an I747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Wow.. I love this kernel. No lag in scrolling. I used to have it on tweet lanes. Now it's gone. So smooth and fast.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Maybe your s3 doesn't work we if it is stressed, try giving it some Valium :p.

He he! Seriously your phone can get slow if you uv'd too much or if you use a schedulor or governor it doesn't like. But if you say it only happens after a stress test I'd consider trying another app or to reboot after your test.

Edit: feel free to go here: http://xdaforums.com/showthread.php?p=31539830

If you feel like talking about ktweakers settings and what others set their S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
Sorry I did. Cant find why my phone freezes when I click on scheudlerr or even the koonservative or any other option. I have to pull out battery to restart.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Does it flicker on complete stock voltages?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yo, i came from computers too... the S3 has a thermal regulator, when the cpu gets hot it turns a core off. So benchmarking with something like Antutu while Overclocked will often yield lower scores than while at stock frequencies.

try system tuner from the play store, you have to download a seperate notification package from settings to get status bar cpu temp updates. that way you can monitor cpu temps and such. also cool tools shows the load per core in a little scalable movable window that overlays ontop of everything. both those are very helpful for judging exactly what your phone is doing while overclocked.

If you want to seriously benchmark toss your phone in the freezer for awhile, i've had the battery temp read -20 Celsius and cpu temp at -9 Celsius, no negative effects for me. benchmark scores were super high when it was in the freezer.

we don't have the benefit of water/air cooling in this little S3. only contact heat dissipation. the cpu heat sink is right below where your thumb hits the middle of the keyboard. that's the hottest part when benchmarking.

If you're concerned about the voltage stability of each step set the max frequency to that step and run a test, if the phone reboots that step needs more voltage. keep going up through the steps if you want to be absolutely perfect/stable.

or you could do like me and just figure it's only gonna be under major cpu load at high frequencies, it should scale up to a high frequency depending on the load so at low loads/frequecnies you won't need as much voltage accuracy. it doesn't have enough load to screw up the calculations at low/mid frequencies if they are undervolted a bit too much. the most important ones are the screen off max frequency, and max clock frequency.

Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Leandre20:
how can i go back to stock kernel with all of the correct drivers, now i tried to flash the file in the first quote and now just my menu and back button glow up but stays on. So i tried to flash the overclocked kernel cleaned cached, cleaned delvik, and fixed permissions and im back to the same situation with the buttons glowing up but thats it.

im on the cm10 nightly m2 rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No flicker with Task's stock ROM, but I am getting a good bit with the 10-16 speed kernel... drag.

No UV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you want att stock kernel with stock drivers. I know where to find it.

http://db.tt/59g9USUj

Edit: this is a stock rooted kernel :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Nah. I didn't really test it for very long but I don't think it's present at complete stock voltages. I think it might be the "super fast" one that did it because it was good on the "10/14" build (the one you posted before "super fast") but others are reporting flicker at stock voltages on the super fast build.

P.S.: Name change successful, sorry I didn't go with "yankees4life" :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Your undervolted to much... You don't have to pull battery, just hold down power button for 10 sec and it will restart.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
thanks, i fixed it. I was going through AOKP settings not the ktweaker.

oh another question. How is that your max is in the 1700 mhz but mine is only 1512?

Another quesiton, do i set these options on boot? I adjusted my voltage as the same as yours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javadahutch:
I would like to see an update checker/ota updater in ktweaker.... would make things easier...in app change log maybe? And no it isn't too much to check this thread... ;p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
Hi, I flashed the latest AOKP (Jellybean 4.1.2)Task & Ktoonsez (10/16) (AT&T/Rogers), and gapps, did it all by the book, and then I flashed this kernal (KT747-Kernel-AOSP-JB-ATT-10-16-2012). Everything went well, but when I rebooted system, it booted up to a point where only the two bottm led menu lights were lit up. I did it twice to make sure it wasn't a fluke.

Anyway, I was able to flash the kernal I was using prior to that, which is KT747-Kernel-AOSP-JB-ATT-10-09-2012, and everything is fine again.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Did you full wipe? The 10/16 kernel only works with aokp & cm after 10/14 so a full wipe might be needed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
That wouldn't really be worth much, though, considering you have to boot into recovery anyways to flash KT747 so it's not like it would make it a one-step process. Sure, it'd save a few minutes, but it's not like the AOKP updater which would has updates every couple of days and is a lot more convenient with an OTA updater.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
Yea, I did a full wipe. I did it twice, and am using the newest AOKP which is post 10/14.

All that happens is the two bottom led menu lights become illuminated about 20 seconds after a system reboot and stay illuminated until I reboot again, where it repeats.

Using any of the buttons at this point does nothing to get me out of that, and the only way to recover, is to flash the previous kernal.

I am on track now, but I really wanted to give that kernal a run and see how it was. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Whatever AOKP you are using (obviously not mine and tasks since we are are 10/16) is not updated to the newest CM10 code. That is the ONLY reason you will get a black screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wavrunrx:
i cant remember; does this kernel support OTG or not ?

do i need a 3rd party tool like stickmount ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
aokp_JB_d2att-ota-eng.task650-ktoonsez-10.16.2012

Is the rom I am using. Downloaded from your thread.

And this is the kernel I flashed:

KT747-Kernel-AOSP-JB-ATT-10-16-2012

It may just be my luck. I dunno. Hah...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You have to be picking the wrong file in recovery then if you downloaded the proper files. Both kernel and ROM should be from 10/16. Got over 600 downloads of the "crazy super fast edition" kernel already so you have to be overlooking something :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
I am very new at this, so I am sure it is on my end. As mentioned in another thread, I am almost blind(progressive). :cyclops: Hah...

If I go completely blind, the way I look at it is, I have seen enough. :D

Thank you so much for your patience and responses. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No problem man, Im sure u will figure out what went wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
I think I just did figure it out. I put a Slim Bean rom in the folder I was gonna flash last night with this kernal.

So I flashed Slim Bean by accident, and then this latest kernal.

Oops.

Hahaha... Feel free to laugh. :D Boing! o.O
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Interestingly, I managed to preserve most of my 10/9b uv settings in the 10/16 (original) kernel. So apparently, for whatever reason, I can now UV with non-O3 kernels?

Maybe 9b broke my phone in a good way, lol.

I flashed the new hot rod 10/16 kernel, and being the wiseass I am, promptly knocked off another 25mv across the board and have started (conservatively) monkeying with the ktoonservative governor settings.

I'll report back if I don't blow anything up :)

Thanks KT!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
http://bit.ly/QskBrx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
http://bit.ly/rrOIwf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
If you go into ktweaker..general...click on "Enable OC Steps" Then you can OC. Might depend on what governor your using not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
i'm having the exact same problem with Ktoonsez rom & 16/10 kernel. It's like if the flickering fix that is included in the rom is not included in the kernel ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Acutally I have no idea what you are asking. Is the screen on or off? If its on and is flickering then its too much UV or your phone doesnt like the kernel. And the post you quoted has already been resolved, he wasnt flashing AOKP, he flashed SlimBean which wont work with 10/16.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
I guess my phone doesn't like this kernel because I didn't touch the UV, in fact I didn't even open Ktweaker or the performance menu. It does the same thing as the rom before the flickering fix (10/13)

and after installing the kernel i did wipe cache/dalvik and fix permissions

nvm: ill figure it out on my own... thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thejust:
Try raising your clock to 384 happens to me if idown clock to anything under 384mhz but i deal with it by disabling hw overlay
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
We would help if you would tell us what is happening. The details that you have given imply that either your screen is blank or you are running ok but with screen flicker.

Also, I was having screen flicker with this kernel with stock voltages. BUT I had lowered my CPU to 192MHz. Appearently I have a phone that doesn't take kindly to setting down the idle speed. No flicker at all at stock speed, like with Task's kernel.

Great job guys. Am glad you keep doing it for me (ok, us)!

---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------

Ktoon, which would be better on the battery, to lower idle to 192 and disable overlays, or to run at stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
any devs seen this? http://xdaforums.com/showthread.php?t=1930664
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Using the CM10 nightly build from 10/17, I get consistent screen flicker using ktoonservative and stock voltages. Undervolting and overvolting don't seem to make any difference. For now, I've been sticking with the 10/12 nightly and the previous version of this kernel from 10/9.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its the ROM. Not the kernel. I posted a build over there a little while ago for those guys that fixes the flickering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I'm in for a dollar...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Yeah, it's definitely reduced with your build, but still occasionally present. Thanks, I'll keep playing with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
ROM: Task & Ktoonsez 10/16

Kernel: Ktoonsez KT747 AOSP 10/16

Issue: Random reboot, followed by constant random reboots until reboot by user

So here's my story...

Just downloaded Flow Free (puzzle game) and played through about 20 levels. Phone rebooted (hot boot - just boot animation without SGS3 screen). From then on, I could only use the phone for a few seconds before it would hot boot again. The only way to get out of this cycle was to Power off and back on. I figured it might be my minimum frequency, so I upped it from 144 to 192.

Thinking it was a fluke, I went back to Flow Free. Got through about 10 more levels and it happened again. I attempted to extract the last_kmsg, but the phone would reboot before I could copy/rename the file. At this point I rebooted manually, and haven't had a problem since (because I haven't gone back to the game).

I've attached the last_kmsg. It's bloody long, and I have no idea what the important bits are. I recommend opening it in Word, because Notepad doesn't format it correctly. I hope this helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You will have to be patient on that one. It is ROM/Kernel interaction on the project butter code. Once the JB source finally drops for our phone, things like this can be resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
I have a question about kernels in general regarding the CPU steps and voltages. Since steps 96mhz-486mhz come stock with your kernel at the same 925mV does that mean that despite what step the CPU is at between 96mhz & 486mhz it is consuming the amount of power? If that's true, it would make sense then that setting 486mhz as your min. would actually consume less power as the phone would then complete tasks quicker running at a faster step.

Also, is this kernel UV'd at all to begin with like Siyah is for the gs2/9300? I was gonna attempt to UV some just to mess around and see what results I can get, but I wasn't gonna bother if it was already UV'd some.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
How are people getting the battery stats they claim? people have been saying they get 30-45 hours battery life with 3+ hours screen on time and with the setting im using which seems to be about the lowest i can go i can barely get 24 hours. just curious if its all BS or what but here is what im using.

im using Deadline As my I/O and Ktoonservative as the Governor And Screen off At 486Mhz, Vibe Set to 100 And the folowing voltages:

Mhz - mV

2106 - 1150

1998 - 1130

1890 - 1110

1809 - 1100

1728 - 1080

1674 - 1070

1512 - 1060

1458 - 1040

1404 - 1030

1350 - 1020

1296 - 1010

1242 - 1000

1188 - 980

1134 - 960

1080 - 940

1026 - 920

972 - 900

918 - 885

864 - 870

810 - 855

756 - 840

702 - 825

648 - 810

594 - 800

540 - 790

486 - 780

384 - 770

192 - 760

144 - 750

96 - 740

Also My CPU Is At 96MHz Min And 1512 Max
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It is not UV'd by default and all the lower steps are set that way so it doesnt crash the phone for people that cant UV much. It is up to u to UV as much as you like :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Ok answers one part thanks :)

What about the part with steps at the same voltages using the same amount of power?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes you were correct :good:.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Okay cool :) thanks!

Your & tasks ROM is the best. Nothing beats it...not even siyah and an aosp build on the 9300. Who needs a quad core exynos when you have two of the best devs in the community here :)

Software does matter ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GHOSTIVVI:
Running this kernel, fully tweaked out. Got 1 hour of on screen time, along with 1 and half hours of phone call, easly 9 hours on 4G and currently at 14Hours and 26% battery life left!! Amazing kernel!! I'm running the latest cm10 build as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
So I searched around, and just couldn't find an answer.

When I open up KTweaker, I get a notification saying "Your Frequency Lock does not match current, Apply Frequency Lock value?"

So I have found that checking the lock frequencies box remedies this, but what exactly does locking the frequencies do? I can read that it limits apps from changing the lock frequencies, but aren't they set to what you set anyways? If someone can set me straight, that would be awesome :good: