yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Because when your phone is in deep sleep (what it should be doing when your screen is off) the CPU is shut off and frequencies/voltages have no affect on battery. The issue with having your min freq set too low is that when your phone needs to wake up (with screen off) and perform tasks in wakelock, it will actually take longer to finish them since the CPU is running slower which means your phone is outside of deep sleep for longer, which means more battery drain.

I don't have the math offhand, but there have been quite a few tests done on this and typically the lowest min frequency you should have set is 192.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I just tried to dirty flash the 4/19 build with the 4/19 task AOKP and Im stuck in a bootloop now :/ I thought the 4/19 builds were supposed to be compatible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Also, a screen-off frequency lower than 486 makes a lot of people's phones not wake up from deep sleep. Every phone is different of course.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You did something wrong then, you probably flashed the wrong file or need to clear cache and dalvik. Over 3000+ downloads of ROM and kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lisek99:
KTweaker is missing from 4/20 release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No it's not. Did you even bother to look inside the kernel zip?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Just installed and set up. Its definitely there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey Ktoonsez,

I couldn't get 4/20 or 4/19 to boot on Slim build 4. I always wipe caches and fix the perms too. I don't know when Slim did a repo sync or freeze or whatever but something isn't compatible

:/

Maybe it's time to try out AOKP again :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Guess you missed the big red letters, lol, those will on work with CM nightlies 4/19 and newer and tasks AOKP 4/19 and newer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yeah I had figured that meant all AOSP newer then 4/19
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
All kernel released after 4/19 are compatible with latest releases based on recent changes in ROM. I doubt built 4 will work, try kernel released before 4/19
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yeah I'm on 4/11, but thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, it usually takes 2-8 weeks for all the others to catch up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Try re-downloading and flashing. You are using the right stuff. They do work together.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
4/20 installed without hiccups KT always on top of his game thanks for the update!! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
4/19 should work on slim build 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
4/20 worked, so far at least, it's still running through cache optimization or whatever it's doing after wiping the caches.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
4/20 3.4 is running amazing on Slims newest 4.1 build.

Just don't know how this combo can get any better..

Thanks KT.

:good: :beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
I used to run 2.1ghz over clock before 3.4. Now I get reboots on anything past 1.9. Making me crazy. I hate 3.4 lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sulpher:
If you read the thread you'd know why...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
You were never at 2.1, there was some math wrong in the OC tables.

---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------

KT, you need a kernel animation like Task's underwear for the AOKP ROM. We need some ktoonsez flavor on the boot screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That would be awesome if someone want to make one, I suck an graphics stuff, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
You need to tell us your vision. I am sure that someone here can make it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Maybe something from here with my "ktoonsez" or KT-747 mixed in there somewhere:

http://www.talkandroid.com/81949-get-cool-boot-animations-for-your-galaxy-nexus/

These look cool:

1. Galaxus:

2. WarpVortex:

3. MachineAzul:

:good: :D :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
KT as you're well aware the latest release with Task's latest has put my phone into absolute beast mode. Thanks for that. I was wondering if it would be possible to have the Fast Charge toggle work with your kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man. You have to use ktweaker to enable it and it works like a charm :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Do you have any preference over any one of the three? I'm gonna give it a go, and I can't decide which one I want to try first, haha. If anyone else wants to throw in a vote for one of the three that'd be cool too. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
MachineAzul was my favorite if somehow one of the rotating objects could be the words or adding one for that matter :D :good:. This will be sweeeeeeet, Ive always been a sucker for an awesome boot animation.

WarpVortex would be my second choice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
What about this one? :P

http://www.youtube.com/watch?v=dQw4w9WgXcQ

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
MALO!!!!!!!!!!!!!!!!! Too funny :silly: :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hahaha :) I was pretty hesitant about posting that... I'm glad you laughed

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Lol rick rolled
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Yesterday's build is unreal with Task's latest, KT. Seriously! At 13 hours uptime with 2 hours screen time and still at 50%! :D:thumbup:

This is the best Android experience I've ever had, period.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'll just leave this here. I got about 20 more minutes of screen time after the screenshot. Most of the screen time was streaming anime too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Care to post your KTweaker settings, governor adjustments, under-volts, etc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
http://db.tt/MXRmQkcn

That's my Ktweaker settings file!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Wish I could take away 10 "Thanks" from you for that one! Now its stuck in my head! LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dankoman:
[MENTION=4325945]ktoonsez[/MENTION] will you continue kernel development for the i9500 exynos and/or the i9505 snapdragon (and if so, which?) on the galaxy s4? i'm thinking about getting one, but only if there's going to be a solid group of reputable kernel developers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Havent decided yet. I wanted Exynos 5 Octa 5410 so bad and then they stiffed us in the U.S. Whats weird now is I just pulled up full specs on the i9500 and it claims to be LTE complaint, can anybody explain that? Im guessing its LTE from countries other than U.S.? I'd hate to get the i9505/SGH-I337 and have to deal with Crapcomm chipset and Crapdreno GPU again. So thats where I am at right now, just hoping for a miracle on the i9500 so we can have LTE and Exynos 5. The Exynost 5 my Nexus 10 has is just simply amazing, eveything is just so fast and instant, best example I can say is: nandroids take littleraly about 15 seconds and opposed 1.5-2 minutes on SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
The exynos is fully compatible with lte. Here is is the issue. Only the Korean S4 will have Exynos and LtE and only korean lte frequency. The international i9500 could of been Lte capable but they did not put a lte modem in so it will never have lte support. So yeah the screwed us... only i9505 will support all US lte.

The article and tweet from samsung was vague and only meant exynos (could be) lte compatible. Sad! Im still getting i9500 but it is a shame no LTE. I am getting it only because of the Exynos which will be mind blowing in performance. Im one of few who have not experienced lte and will not in my area for more than a 2 year contract.... my clear choice is i9500. Like KT said the Exynos is unbelievable. Just sucks LTE just wont happen for i9500 us users...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
What's so bad about Qualcomm? The AnTuTu scores are pretty much neck-and-neck and Qualcomm's SoCs traditionally have better support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DKaine:
So considering the big red letters and all... This maybe a silly question. Does this kernel no longer work on ParanoidAndroid? I know the most recent release for the SGS3(i747) came with KT747 built in, and I'm currently running KT 4/06. I was hoping to update to the newest kernel (just because I'm a crack-flasher and want the latest/greatest), but got stuck in a black screen. When I reflashed the older version of the kernel, phone worked just fine.

Anyway, like I said, maybe a silly question, but I had to ask.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
There are display commits that have been added to the more recent builds. The ROM has to be updated for compatibility. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Row/ktoonservative

Screen off is noop/ktoonservative with max at 378Mhz.

Governor adjustments are the same as ktoonsez, i don't know enough to tweek those.

Min is 189Mhz (anything lower makes the CPU frequencies jump up and down constantly)

Max is 1134Mhz (yes 1134) For 90% of what I do, this frequency max is sufficient. I think this saves me a lot of battery. Although my phone is stable at 1998Mhz, I think the power savings at 1134 is awesome. Things are smooth and if i ever need more power i can just up the max to 1512Mhz or even 1998Mhz if I wanted. I think compared to most people here my voltages are much more undervolted especially 1134Mhz and below. I may be able to go lower, but I haven't tried, too scared to.

2106Mhz - 1350mV

1998Mhz - 1275mV

1809Mhz - 1225mV

1728Mhz - 1150mV

1674Mhz - 1125mV

1512Mhz - 1100mV

1458Mhz - 1050mV

1404Mhz - 1040mV

1350Mhz - 1040mV

1296Mhz - 1025mV

1242Mhz - 1000mV

1188Mhz - 975mV

1134Mhz - 950mV

1080Mhz - 925mV

1026Mhz - 900mV

972Mhz - 900mV

918Mhz - 875mV

864Mhz - 875mV

810Mhz - 850mV

756Mhz - 850mV

702Mhz - 825mV

648Mhz - 800mV

594Mhz - 800mV

540Mhz - 775mV

486Mhz - 775mV

378Mhz - 750mV

189Mhz - 750mV

135Mhz - 750mV

81Mhz - 750mV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DKaine:
Aha, I guessed something was up, and the ROM needed to be updated. Thanks! Now to bother/donate the developer to push the newest changes into PA... sigh for not owning an "official" supported device... =D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
As long as this slight offtopic is not an issue it proves for now to be sort of true that the exynos and s600 cpu will be very close in the gs4. The s600 result is of a recent build of the s600 version but not authenticated. The exynos run was authenticated. The exynos version still may not be on the release firmware but could be case for both. This s600 bench is only one near this value all other well below around 24-25k..!? As time goes on both handset scores have been improving, though the exynos scores have not been below 28k from the start.

The highest scores i have seen for both are pictured below.

It is hard to say how both release firmware will perform by then as the Exynos software to manage the two processors inside is being updated even still. Apparently all Exynos on the big.LITTLE architecture can be multi processing capable having both quad core cpus active and choosing where its best to have threads calculate (on performance or power saving cores)

See this spoiler here to see two Samsung slides showing this capability that is not yet software enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Hey KT,

What is the cause for this with everything Bluetooth related off? Even bt frozen in tibu this constantly happens. Maybe I'm not understanding something but if Bluetooth is off why does this happen all the time?

04-22 17:38:27.233 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:38:27.233 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:38:30.296 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:38:30.296 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:13.526 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:13.526 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:19.493 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:19.503 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:25.689 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:25.689 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:28.613 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF

04-22 17:40:28.613 D/BluetoothAdapter(23207): 1098513312: getState() :* mService = null. Returning STATE_OFF
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That would be very very very very very odd and something very weird going on if they were neck and neck. Qcom will be around 12k where as the Exynos has been around 30k (28.5k-29k) in all the test I have seen. Might want to remember that Qcom based is supposed to be 1.9Ghz where as Exynos is 1.6 and 1.2Ghz. As far as issues/stability I was mostly speaking from experience in ROM and kernel development, Exynos is very easy to work with in development, and things can be brought up very quickly were Qcom/Adreno took us months just to get something resembling stable. But when I am talking about all these issues, I am refering to development on AOSP, so all Touchjizzers have nothing to worry about at all, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
From the looks of it, you have an app and or service that keeps polling bluetooth status over and over again. Could be a third party app or the ROM, never seen that in logcat before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Thanks for the reply. Guess I'll be wiping and installing apps one by one tonight to find out what's causing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The Qualcomm SGS4 is scoring ~25,000 on AnTuTu while the Exynos SGS4 hit ~27,000. I'm curious what the difference in battery life will be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Battery life will be interesting. I wonder what kind of magic they are doing on the benchmark to score that high since the CPU is almost identical to what we already have except it has 2 extra cores.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The new Krait 300 cores have various improvements besides the higher clock speeds(I think I read about up to a 25% increase in performance for the same clock). The Adreno 320 is running at a higher clock speed than it did in the S4 Pro devices(there may have been other tweaks) and I'm sure there are tons of tweaks to other parts of the SoC such as the RAM and buses.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z34370z:
Holy crap that's a serious under volt. My phone will reboot randomly any lower than 950mv Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This is the main page that gives me a glimpse of what it is compared to the new Exynos's (link below). Biggest disappointment is that they are still barely compatible with Cortex-A7 where as Exynos is up at Cortex-A15 which produce huge gains (like I said before, the Nexus 10 is just mind blowing). I'm sure they tried there best but just seems like this is not there strong suit at all. I can't remember do you use TJ or AOSP? Im sure all the diehard fans of AOSP will remember the months of troubles we had due to this platform, like the dreaded no-wake bug where you had to hit power button 3 times to make it wake up, the millions of complaints about screen flicker, and the list goes on......

http://en.wikipedia.org/wiki/Krait_(CPU)#cite_note-1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
You took words out of my mouth before they were formed malo. Exynos has more work put into chip and it shows, s600 has its benefits of being cost effective for mass production and a basic handling of the same tasks Exynos may do. But as in AMD vs Nvidia in pc GPU or Intel vs AMD cpus there is a product for every person. The top of the market costing a premium.

Its good both will be produced actually, it would just be nice if they had made it more appealing to go Exynos base by having lte on all of them....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The Kraits are heavily modified A9s. The result is pretty similar to the A15 in terms of performance. The A7s use the same instruction set as the A15 but are tuned heavily for efficiency instead of performance. Don't the Exynos phones have tons of issues with AOSP ROMs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I havent had any issues with the S2 I owned or the Nexus 10, Exynos works perfect with AOSP, mostly due to the ease of programming and a wide base of devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
If the exynos processor is so easy to dev for, why is there a rumor going around saying devs are leaving Samsung for their lack of source code for their exynos chips? Forgive me if I'm wrong...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
It was a Bluetooth toggle in widgetsoid. Figured it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
I have very similar undervolting as you but my cpu doesn't stay stable past 1809Mhz as antutu seems to crash right away. Oh well, happy with better powersaving over benchmark numbers:o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Ill never forget my s2 because of what you provided to us KT. First the ease of hellraising with flashoholics then the kernels. You were/are da man!!! The first person on xda I donated to was big KT. Thanks homie.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, yep we go waaaaaaaaaaaaaaay back :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Most of what people have complained about is the huge delays on new code when new Android revs are released. Since I have now been on the Exynos side and the Qcomm side, I see absolutely no difference at all in timing. Best example is: AOSP for our phone has been at 4.2.2 for months and months now and the poor Touchjizzers are still stuck on 4.1.1 due to no code from Samsung for ATT phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Thinking about giving a shot to this kernel but I got couple of questions though.

1. I'm running the newest build of Deviant Xone. So which version will be compatible?

2. What settings do you guys recommend?

I've been using BMS for the longest time, got no problems so far but just having that itch to try this one out :p

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
If you want that stable and yours at 1890 is not apply 1325mv it should pass and inch up by 5mv till it does if that was not enough.

---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------

Get used to using Ktweaker and you should love this kernel :)

Xone is what android version? Touchwiz or aosp? 3.0 linux kernel or 3.4 linux kernel as base?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Get the 4.2 JB version. (kernel 3.4)

Also, see post #3 for KT's settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
All that extra room down there kt, this would be cool, one less click to see what the processor is running at
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Like the idea. How about the top though lol

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Immmmmmmmmmmm baaaaaaaaaaaaaaaack :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tenkie:
yessssssss! I can't wait to see what you have in store for us!

How was your trip?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Speak of the kernel slum millionaire and he shall present himself get yo ass to work ! Haha jk hope u had a good trip I'd start working on jelly bean kernel *cough* it will be an update sooner than ya think ;) call it BeanzNThingz or something retarded lol btw the i777 ani mod semi works you can figure that out and err seriously I know the aokp updater works (tried) lol just make it for i747 :P back to making things now...lol

Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks guys, trip was good :D. Good to be back, got 3.0.37 in and starting to look at AOKP stuff. Be on the look out late tonight or tomorrow for an update :-)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jxs1984:
welcome back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
Juat a thought and something I observed on my phone...my clock freq. did not go over 1350 IF Power save mode was enabled. Once I disabled it, the higher frequency cpu settings were enabled and functional again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes, that is what happens in power save mode. It saves power by reducing the max ghz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
I feel like its constantly resetting itself even half way through a benchmark etc..

Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkeyman:
I mentioned it because there were several people who were mentioning their cpu clocks were underclocking and not sticking or staying at a specific freq. And sometimes the most simple solution or issues are overlooked. My two cents worth...for whatever its worth...2 cents? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated (AOSP Version updated)

AOSP VERION: Download CWM flashable zip kernel

http://www.mediafire.com/?eh2lpnnslozz5g5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Will this work with cm10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Dont know, give it a try. 99% sure it will work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbj13:
Does the aosp support overclocking?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Tested and it gets you into a bootloop on cm10 :/ oh well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwiing:
Works on AOKP so far...feels buttery smooth!