yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] balpreetsaini:
I tried an old build, the sammy 8-11 build and I verify I still have audio crackling at voltage lower that 980mv @ 384, This being the issue am I better off using the stock kernel for battery life or does this kernel have other feeatures built in that help perserve battery life other than undervolting. on the bright side being over clocked at 1.809 ghz I do get a quadrant of 5600
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Warrior1975:
Just flashed this a little while ago...wow

...insanely fast. Thank you for sharing!!

¶0w3®3d b¥ @OK¶™...GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] michaeldotson817:
Do you guys use different settings in the kTweaker app? Like the smartass governor? Just trying to get a little better battery life while keeping it smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
I'm having a bizarre issue with the latest AOKP by KT (8-28) and the 8-28 CM10 official version. If I set them up without the KT Kernel, everything works fine, including wifi, but then when I try to set up the KT Kernel, there is a problem.

I did everything like I always have, which always got the kernel and everything else to work. But when I go back into system after the reboot, my wifi doesn't come on like it always does. When I go to the wifi screen to activate it again, I click the wifi on button and it switches back to the off position and says that it's trying to connect to the wifi.

I've never seen it do anything like this before, and I haven't seen anyone mention it in this thread since the 8-28 versions came out, since I made sure to look before I posted! Wifi worked fine before that though. I tried it a couple of times on the CM10 and then once on the KT AOKP. Finally decided to redo everything and keep the KT AOKP on my phone since it is vastly faster than CM10 right now.

Anyone have any ideas, hopefully without busting my hoo-ha about it? :P

---------- Post added at 02:45 AM ---------- Previous post was at 02:44 AM ----------

From what I've read in the thread, people seem to have a lot of luck with the SmartassV2 governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
EDIT: MY WIFI ISSUES MIGHT HAVE BEEN RESOLVED WHEN I MOVED MY WIFI ROUTER TWO INCHES TO THE LEFT. LOL

I've had similar WiFi issues recently. It will often take forever before turning on after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
So you have the thing where it does that with the toggle too? But it eventually works? How long does it take?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
i feel like if i use the touch booster and change it to any mhz it always keeps my phone at 1500mhz when i touch the screen. idk if its a bug or not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
same with me, i set it at 1080 and not once has 1080 ever been used on cpu spy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
Did you try downloading the kernel again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
I'm on Rogers, using WanamLite ROM and KT's Sammy kernel. Am able to undervolt to 805 at 96mhz with no performance issues at all, and the audio sounds great. Can't recommend this combo enough- my phone feels snappy & light, and battery lasts & lasts- roughtly 30hrs per charge (including 8hrs while asleep).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Probably have to do a wipe, no problems here and of course I am using task and I AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Wound up restoring the Wanam/ICS backup. AOKP wasn't more buttery than my Wanam+Sammy combo, battery life wasn't as good, and it wasn't as stable- in addition to the exchange issues and the too-strong haptic feedback, Contacts would crash everytime I went to use the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
No, didn't think downloading the same kernel again would change anything.

---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------

Only thing is that the problem happened after fresh wipes and installs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
No issues to report using with current nightly build of CM 10 great job ktoonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dante2512:
I had the exact same issue. What happened is when ktoonez first released this build his script didn't include WiFi drivers. Try redownloading and reflashing. It worked for me. The old file was 6.05mb new one was 6.95mb if that helps. Good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Ooh ok! I wasn't aware that he updated it, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aalh:
even if there were no changes, more than once I have gotten a bad download, not often but it does happen (for any rom or kernel, not just this one)

so always try the option of deleting the file and re-downloading it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dssking:
I personally have not. All I did was drop the CPU to 1050 (or thereabouts) and decrease the voltage by 25mv. I can't say I've seen a difference

in 2 days of doing this. I'm running the stock Rogers rom with teh sammy kernel (Ktoonz).

So...I"m eagerly awaiting advice from users, or worst case, I have a 4400 maH battery and cover in my briefcase that I'll have to run.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
That was the problem, I downloaded the update version and it's fine now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
So this new JB kernel is awesome....running CM10 8/28 nightly and it's noticeably a little bit snappier. Good job
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dssking:
Seems like im going backwards. Voltages decreased bt 125 ... And cpu 1050...

I am at 35% with only 1.5 talk and 1 hour o screen....

Something usnt right.....

Help.?.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] truongoi:
I searched this thread and found nothing about Android File Transfer (AFT) for Mac.

I tried this kernel with tMIUI rom and CM9 rom and both time the AFT says: No android device found.

I tried both connections MTP and PTP.

Any help?

Thanks! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LMAO, ya buy a PC, mac's are ment to do anything, just for play ****tune and drawing pictures :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] King Shady:
I'd shoot myself if I owned a Windows PC. While windows 7 isn't bad (windows 8 is horrible) prefer Mac and my beautiful retina macbook pro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Opposite here, I'd shoot myself if I had to use a crapintosh. They still boot off of cassette taps. Bad time to be talking about them too, since they just paid off the courts to get them 1 billion dollars from Samsung cus crapintosh thinks they invented the phone. :cyclops: ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeb101:
Hey man, I love this new kernel and ktweaker, super stable at 96 and 2100! I had this idea earlier and was thinking it would be awesome to have a slider in the notification menu to adjust the max frequency. Quick oc for gaming, or quick dc for battery save!

Another idea was having a slider in the volume slider, always accessible even in full screen apps and games.. AOKP feature with your kernel. lol

But to be clear, I'm not asking for anything, these are just random ideas. I don't code, just appreciate your hard work :)

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
I am having a hard time getting this or any Kernel besides the one that is actually flashed with the ROM to boot up. I have flashed CM10(which I am currently running) or your awesome AOKP ROMS. But, no matter what I do, after flashing the KERNEL, my phone refuses to boot. I have gone through the process noted by Bnaughty with extensive wiping of everything, I have "Odened" back to stock rooted and started fresh, all to no avail. I did notice after my 6 thousandth try that I always get

E:unknown volume for path [/sd-ext]

when choosing to wipe DALVIK. So I attempted to wipe it through terminal with the following

su
cd /data/dalvik-cache
rm *
exit

but no dice...

Any help would be greatly appreciated.

I did actually have it boot once but upon doing some Ktweaks it rebooted never to be seen again :(. It was so fluid that I MUST have it back. Thanks and sorry for the wall of text

E:unknown volume for path [/sd-ext]

rm: can't remove '/sd-ext/dalvik-cache': No such file or directory

Dalvik Cache wiped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
Replacement

Ktoonsez now I can conclude that every phone is unique in their own ways, I had a device that didn't want to take the kernel no matter what I did, I called AT&T and I told them I needed a replacement, I got my new device today & I am happy to say that this new phone took the kernel like a champ!! I am able to fully OC the phone to 2106mhz which made my DAY!! Great job on this kernel Ktoonsez!! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
E:unknown volume for path [/sd-ext]

when choosing to wipe DALVIK. So I attempted to wipe it through terminal with the following

that's normal I always get that... have u tried my steps with kernal included in them?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
I am glad for you, but saddened for me at the same time :cool::thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
There is no /sd-ext - you can ignore that message - it's just part of CWM that doesn't apply here. And note the post right under yours - some phones just WON'T take the kernel - if you saved a previous version or can get it somewhere you could stay back until a new one comes out. In my case I'm not running it right now either - it "works" but I was getting battery drain that didn't connect to anything, which I blame on the phone, not the kernel - so I'm waiting...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AWESOME!!!!!!!!!! Glad it worked out :good: ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] King Shady:
Why would it be a bad time? They are the biggest company of all time and if you deny that they make good products you are in denial. The S3 is a superior device than the iPhone, yes of course, however it is clearly evident that the first Galaxy S was a direct copy of the iPhone 3G/S. Apple makes quality products, and though some are overpriced, the support is the best of any company I've ever dealt with. I remember dropping my old 4 into the sink, I got a free 4 for free at the Apple Store; all of the employees are extremely friendly. Seriously, there are too many Android fanboys on here that don't give Apple any credit - without Apple there would have been no smartphone as advanced as our very own S3's. BTW my MacBook Pro runs just fine thanks and beats any laptop screen on the market (and is thinner and more powerful than most of them). So, that being said, did Apple get away with some unfair patents... yes of course they did, but they deserved to win this case. Besides the 1 bill doesn't even bother Samsung that much, because they are still the biggest Android OEM in the world and still continue to make quality products. They'll be fine. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deadlyrhythm:
how the hell are you doing that?!:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
My highest was 9367...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 8-30

1. Reverted compiler and changed opto flags

2. Updated KTweaker, Screen off Profile Mhz setting is working now.

3. Updated KTweaker, boot setting should apply now, added 5 second delay.

4. CM update for the Jellybean kernel

5. Many, many more.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xijar:
To be clear does this work with the cm10 night lies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] King Shady:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I only want to know about this one. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes, I am fully inline with the nightlys kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
MALO!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You've got monies!!

2L4600906Y6265532
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man :D Awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] King Shady:
Which device sparked the modern smartphone movement? Oh yea, the iPhone . Please.. palm is dead and HTC is struggling. I love when fanboys just deny that the iPhone revolutionized the modern day devices.

---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------

Love Mac bro. +1 to you for not being a fanboy like everyone else here.. and awesome username hahah
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
hey guys, this is a kernel thread. not very cool to clutter up ktoonsez's thread with this stuff. General or pm would take care of this. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alex2x3:
Thanks for the update! Just flashed, everything seems fine for now.

Any recommendation on how low to set the screen off profile? I'm trying 192mhz now and no problems so far. Just wondering though.

Also why did you revert to the old compiler, cuz yesterday the change log said that the it was 100 trillion times faster! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, the compiler was doing some really NOT cool stuff. If you flashed it more than 2 times it wouldnt boot half the time. I like the July one better and has been very good to me so far :D. Dont change what isnt broke. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
I will be getting a new phone from work tomorrow in the hopes that I can flash this kernel cause I am tired of not having oc. This phone just won't take to it no matter what.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
i want all of your opinions. :highfive:

Good job on the kernels dude. :D:highfive::victory::highfive::D:victory::highfive::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You complete me!!!!!!!!!!! :fingers-crossed: :good: :p :cyclops: ;) :cowboy: :victory: :silly: :eek: :rolleyes: :cool:

MALO
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
i told you. it's happening. i knew you'd come around. ;) :crying:

MALO!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ktoonservative Governor

For got to mention that I added a new governor that has been working really well for me the last day or so. It is an off-chute of conservative hence the name :D. It supports hotpluging unlike conservative and working really well. My next release will include a new set of values by default that have been kicking ass. Give it a try and tell me what you think.

Thanks to freecharlesmanson for all the testing and great tweak values!!!! Be sure to give him some thanks :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Forgot to answer the other part of ur question, I am using 486000, remember that your phone's screen goes off while in calls, so I choose that one for that reason, I tried 192 and did have 1 reboot while in a call. But like ive said a million times, every phone is different so it might work for others :D. Its all a brand new concept so we all will just have to experiment :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I found my phones weakness... 700Mv at 96Mhz... reboot... LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s2556:
So far so good with the new kernel! :D

something kinda odd has been happening. When I charge my battery it will only charge to around 90% (give or take) and then will stop and not charge further when left on the charger (which is the stock charger it came with). Also when I turn off the phone so it just displays the charging battery It will sometimes show around 60% sometimes 90% but I haven't seen 100% there either :confused:

I do have 2 extra batteries but I read that you do not have to wipe battery stats on samsung phones is that true? I tried wiping it anyway in CWM but nothing helped.

Does anyone know if this would be kernel or rom related? or something else?

its just kind of annoying not a huge deal as my battery life is not affected. just a little harder to tell when it is fully charged.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Yeah this is killing me. I've never had a phone that is this bad. I can't do squat. It will all be fixed at 3pm tomorrow :)

Sent from my AOKP powered S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
So far I've gotten down to 750mv and its stable... be honest though I really hate figuring out a phones optimal voltage... its gotta get done though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
I'm not afraid to push it. I can't even run stock with no oc stepping on ktoonsez kernel. Get black and white screen flashing fc and random reboots every thirty minutes....also I lose access to all my photos. I don't understand. It is definitely the phone not his kernel.

Sent from my AOKP powered S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Here's my phones clock/UV settings that some have asked for. And as always this shouldn't even need to be said but I'll say it anyways; what works for me may not work for you as all phones work/act different as the hardware from one to another handles things uniquely. Fyi I have 3 S3's and the all vary quite a bit in terms of the clocks they can handle and especially the UV they can withstand and run stable on. So I'll actually post the numbers for the two north American models I have and not the intl (as that's useless here).

These numbers are all with the latest Ktoonez kernel 8-24. I've posted the clocks and the default mv's and then my lowest stable levels.

MHz clock/default mv/my mv/-amount dropped (My other S3 mv levels also included and as you'll notice they're quite different but it battery life is comparible)

MHz/stock mv/my mv/-mv amount(2ndS3 mv)

96/925/785/-140 (825)

144/925/790/-135 (850)

192/925/800/-125 (850)

384/925/825/-100 (870)

486/925/845/-80 (880)

540/950/865/-85 (900)

594/950/875/-75 (900)

648/975/890/-85 (915)

702/975/895/-80 (930)

756/1025/950/-75 (980)

810/1025/955/-70 (985)

864/1050/970/-80 (1000)

918/1050/980/-70 (1005)

972/1075/985/-90 (1015)

1026/1075/990/-85 (1035)

1080/1125/1015/-110 (1075)

1134/1125/1025/-100 (1080)

1188/1150/1040/-110 (1100)

1242/1150/1055/-95 (1105)

1296/1175/1065/-110 (1120)

1350/1175/1080/-95 (1125)

1404/1185/1095/-90 (1150)

1458/1185/1110/-75 (1150)

1512/1200/1120/-80 (1155)

1674/1200/1125/-75 (1160)

1728/1250/1145/-105 (1200)

1809/1275/1185/-90 (1220)

1890/1300/1215/-85 (1250)

1998/1325/1240/-85 (1275)

2106-1350-1300(don't use this step not 100% stable) (1335 - this 2.1 step does work on the second S3 at this mv level)

This phone obviously is great at uv'ing! Its able to drop successfully by significant amounts while maintaining stability.

I always test my oc/UV settings with extensive real world use as well as: Stability Test, Battery Drain, NenaMark2, Vellamo, Antutu, among others...

And that's that. Hopefully this works for some of you and helps save some more battery. As mentioned before I'm now getting 2-3 days on my 4300 mAh battery with fairly heavy use, which includes 7-9 hours of screen time so I'm finally pretty happy with it now.

And once again, thanks Ktoonez, your kernel rocks and is now my daily. Next I'm going to start testing your jb kernel w/ your jb rom...looking forward to it. Keep up the good work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeb101:
With those voltages you have noted above, did you by any chance do any stress tests or stability tests on those frequencies? I've been playing with voltages also, I have my bottom set figured out (96 to 1.1ghz) and I am currently stress testing the rest 1.2 - 2.1ghz. i use StabilityTest on the "Scaling" option to add a load all frequencies in the frequency range. I use a range like that because you keep those steps more active, and you can get the phone to heat up more, so you can really see where you're at with your phone.

Once the burn in test completes, I drop everything 10mv in my range and start over. It's a long process, but you find the absolute your phone can handle.

This "First touch" booster pretty much eliminated all hangs or lag on the device. I'm currently running SIO / Adaptive. ~16 hours battery life with 3 hours screen time (auto setting in CFL light building), ~2 hours of Google Play Music Streaming, and about 80MB of mobile data. Pretty nice if you ask me.. My old iPhone would never do that. If I really stretch it, I've hit 33 hours with 1.5 hour screen time and ~45 mins of streaming.

Once I'm happy with my voltages I will also post them here for those of you who are looking for bare bones (for my device at least) voltages for your phones.

Cheers,

JEB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aalh:
every mac I have owned......runs Linux

never booted into MacOS

on a side note Ktoonsez, 8-30 still freeze-boots on my poor phone:crying:

running faux kernel, no problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Hey guys finally decided to flash this. Been holding off because I have no idea what to do its kernels. But seeing as I have a couple days off might as well play around with it ;)

I have a couple questions regarding undervolting. I understand that all phones behave differently. But can someone give a brief explanation as to how to test undervolting? e.g how can I tell whether the amount I've undervolted is stable or not? (aside from the obvious scenarios where the phone would crash or reboot) and what are some good practices as to finding the "optimum voltage" or is it all trial and error until the user is satisfied?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
Mac crap cleaned

Let's stick to the topic

This is a kernel development thread

Thank you for your cooperation

Friendly Neighborhood Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
2 posts above yours. Really, reading at least the previous two or three pages (and always the OP and next couple of posts) is a really good idea before posting a question :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
He's friendly again :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Like I said I am completely new to kernels. I've read the op already as well as the suggested readings in what a kernel is but those suggested threads there mostly mention about different types of governor and i/o but not so much on tweaking and undervolting.

Also I don't mean to sound rude or anything but all you seem to do is jump around the aokp/cm threads telling people to read op or post in the q&a rather than offering any actual help. It's cool that your trying to keep threads clean and directing people to the right places but I'm just simply asking for a brief explanation in layman term to help me get started. You can't really expect a newbie to completely understand some of the jargon being used (stability test, nenamark2 etc)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
Been trying to use this on cm10 on my tmo s3 always maxes at 1510. The kernel works great just no overclock.

sent via galaxy s3 on cm10 @ dual core 1.9ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Have you enabled oc frequencies in KT tweaker app?