yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] simarr:
I am using cm offical 2/20 d2lte. Everything works, even lte. My modem is mg2. At first, it could only pick up h+, but after 30 mins or so, it connected as lte. I had to download the nightly using a pc instead of cm updater. Flashed rom first, then cleared cache, then flashed kernel. Only thing I noticed that was odd is the model number under about phone is unknown, I'm sure this has to do with the new unified d2 build. Hope this helped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Ktoonsez. Did you tweak the screen driver at all? Maybe I'm nuts but my screen looks clearer. Also, lte working fine with a dirty flash of 2/17. So far butter. Thanks for your work on the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes there were some changes to the display driver :thumbup::thumbup::thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Um, I noticed. My phone is clearer than my TV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VR32:
the pulsing blue light was cool, it came on during boot. but it didn't stop. I didn't find notifications of any kind, nor could I stop the light. sorry I don't have any logs to offer, but is that anything I am missing? I reverted back to 1/28, which is brilliant. thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
My issue with LTE turned out to be a bad flash and/or download. Re-downloaded 2/20 nightly and flashed, and all is well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
+1^^^. It indeed is much clearer!! :good::good::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
This is off topic, but CM has now merged all the s3s. I was wondering why no nightlies since the 17th. You need to get the d2lte nightly from the site. If you're on a version released on the 17 or before, your phone won't show updates. Just wanted to let you know.

---------- Post added at 02:09 PM ---------- Previous post was at 01:50 PM ----------
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
This happened to me too, but for Quantum kernal. I noticed it stopped if I plugged and unplugged the phone. To fix it I just dirty flashed my rom and the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Got an assert failed message when I tried a dirty flash. Clean install of ROM and kernel flashed fine.

For some reason, my LED settings in ktweaker look like this:

If I tap on the lines it brings up the options and I can change them, but I have no idea which one will come up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I saw the Assert failure. So I confirm. Needed Clean flash of Rom and wiping Cache just BEFORE flashing the kernel cleared it.

I have the same issue with the LED Option. No Clue what the Menu is supposed to do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The LED options have nothing to do with the S3, those are for S4, your LED stuff is the stuff from CM and not sure where you can control them from CM .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisn812:
USB tethering doesn't recognize the connection. Compass works great now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
It seems like I'm the only one experiencing this:

Using the latest CM11 nightly, and flashing the latest kernel I get bootloops. If I dont flash the kernel its fine. After flashing I will get into the "optimizing apps" and then after its finished with that and says "starting apps" It will freeze and then reboot. When it reboots it will start to bootloop after the CM bootanimation.

I've downloaded the kernel 3 times. The thing is. It worked once, but after trying three or four more times it does the same thing. I don't know whats going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niphoet:
You using Dalvik or ART runtime?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Dalvik
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi guys. No matter what I do. Even a clean install, I cannot get the new kernel working for me. using CM11 2/13 nightly and 1/28 kernel things are fine. Stock CM11 Nightly works, but if I flash this Kernel on 2/20, 2/21, or 2/22 hasn't worked for me (havent tried any other build yet). After Optimizing Apps phone goes into a bootloop. I think I'm going to have to stop flashing this kernel and stick to the stock CM kernel cause it seems its only affecting me. Some of my device info:

I747M

CPU revision: 0 (I mention this because S3's with CPU revision 0 have a bug where it cannot run NEON code properly)

Bootloader: MK5

Runtime: Dalvik

Will miss you all. Happy Flashing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Did you try doing a complete fresh install?

Titanium backup all your user apps and data to external sdcard

Copy/backup all files you dont want to lose from internal memory to ext sd

Wipe data

Format /system

Flash rom

Flash GAPPS

Wipe Cache/Dalvik

Flash kernel

See if it boots then restore your user apps from titanium.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Yup. I have. Also. I found something interesting. After I flash the ROM and use it for a while, maybe for a few hours, then go back into recovery and flash the kernel it works fine. But if I flash the kernel right after flashing the ROM it does the bootloop thing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
FWIW - installed over quantum 3.45 and working just fine on my side - no bootloops nor flashing blue lights.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
[MENTION=4289019]Epikarus[/MENTION], you will need to wipe Dalvik + Cache after kernel flash for good measure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I do. I wipe dalvik and cache all the time. I've done a clean install and everything. The only way I got the kernel to work is to flash the kernel after I've used the phone for a few hours. This is so odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 02.24.2014

1. CM sync so you guys are up to date (87 updates) as of 02/23

2. Linux 3.4.79

3. Linux 3.4.80

4. Linux 3.4.81

5. Linux 3.4.82

Enjoy!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kdp162:
Bootlooped running AOSB 1.30
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
me too. Its not like my previous boot loop. This time it wont even go into the Kernel Boot Logo screen. The screen will stay black and sometimes it will flash the Samsung logo for a brief millisecond. I downloaded the kernel twice just incase of bad download but both dont work for me atleast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Same thing on Quantum v3.45
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
same for me with 2/24 release. flashed back to 2/20. I'm running latest gummy rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T_D_H:
same bootloop as well on quantum rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Hey ktoonsez, decimalman pointed me to increasing ramdisk address and offset to fix it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Same bootloop on Slimrom 4.4.2 build 3.2, flashed with cache/dalvik wipes on CWM 6.0.4.7.

Thanks to you guys, I had made a fresh nandroid backup first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Bootloop on latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
So I am guessing that no one got it to work???

Here is a new one to try:

http://goo.gl/hklXni
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kdp162:
Flash failed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Try clearing dalvik and cache before flashing.

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

Works. Now if the cm people would get off their asses and fix the lte bug we'll be good!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kdp162:
Cleared davlik and cache, flashed fine running smooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Does last night's CM nightly and this kernel fix the bootlooping with ART?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Hey kt,

I've been tracking your aosp4.4 branch (maintaining my own changes) and as of the latest commit (5baebe35d0020eac53be92d1c2c310f56dce21de) I've got the boot loop everyone's been mentioning. Can you tell me what you changed to fix it? Or is it just waiting to get pushed out? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
This update fixes the boot loop. But strangely the led notification does not stop even after the phone boots. Reverting back to stock kernel..

Hope this is fixed soon. Even disabling the led notification didn't helped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I had to kill all the crap from yesterday. Do this command:

git reset --hard 02e89e1fd83f46419c52ed62564aed0c8da2ba23

I will update github right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Ah, not sure which upstream change in particular caused it? I'll start applying them one by one to see if I can replicate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I would just do what I did. I pushed the overwrite up and added all the important stuff. Its all up on the github now :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok guys, here is another test with all the latest stuff, same link as before but updated:

http://goo.gl/hklXni
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Oh, solid. Thanks ktoonzes.. pulled and building! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LARMYV:
I tried your test link and the phone still bootloops :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
The first 2/25 you posted works great. This one bootloops again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You try my test build yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
I was about to say the same thing. :p

I reset, remerged and rebuilt, but the new kernel is still boot looping. I tried reverting the sec-battery change and caf/kk_2.7-stable, but neither seemed to help. Hmmf.

EDIT - Tried your test build; same boot loop.

btw .. know any way to get a serial console on these phones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Crap, so the problem is one of the new ones I merged in today again. U got time to start reverting 1 by 1 of the ones from today to see which one it was? I never looked into serial console.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Yup, doing it now.

EDIT - Found it! :good:

3162697b384f7c1918a3252544b90f1d68f45bec - Merge "Merge "Merge "wcnss: Trigger WCNSS driver on first open."""

Seems to touch a lot of arm memory management code during init. No idea what it does. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AWESOME!!!!!!!!!!!!!!!!! Ill build up right now and see what the others are getting :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok, test number 2 for today guys, same link and file name, let me know:

Download

http://goo.gl/hklXni
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
on the first test build i got the black screen of death. reverted to 2/20
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Download link right above your post, download and it should be good to go :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
saw that, trying now. thanks kt

edit: status 7 trying to install second test build

tried redownloading.. same issue. status 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
[MENTION=4325945]ktoonsez[/MENTION] It worked solid for me no bootloop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sweeeeeeeeeeeeeeeeeeeeeeet :good:

Big thanks to [MENTION=1107425]lambgx02[/MENTION] for taking the time to revert 1 by 1 until the bad commit was found!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Works great! You guys rock!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 02.25.2014

1. Removed commit from CM that was causing the boot issues. (thanks [MENTION=1107425]lambgx02[/MENTION] for finding the bad commit)

2. Same one as the one from 30 minutes ago so guys that are on the one thats booting do not need to redownload.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Confirmed working fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
any ideas to remedy the status 7?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Wipe Cache before flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
that worked. thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
what was the fix for again for preventing the LED (s3) for constantly blinking....

edit - knew i read it somewhere - plug it in or it get interrupted by a notification lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1

---------- Post added at 08:38 PM ---------- Previous post was at 08:27 PM ----------

Actually, first SMS that just arrived cured the flashing notification light
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bit1:
I'm using the TW 4.3 version but I don't see the file to remove when using the kernel qosmgr. Did that mean it was removed by the builder of the ROM or is it moved from system/bin? Using srx 3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Could have been removed by the builder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
Regarding the wifi, any chance of your kernel working with Tasks's AOKP that he's started dev'ing again? (haven't had time to try it myself yet)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
I've tried it and wifi is broken. However, I read something on Tasks G+ page thats it's in the works for 3rd party kernels. Fingers crossed. Right now with stock kernel, aokp running blazing fast on my phone so I'll wait for things to get worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Tried it, Wifi is broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I've heard GREAT things about this kernel and I'm excited about the potential battery savings. However, I just flashed this kernel with stock settings and now my phone is randomly freezing and rebooting. How might I troubleshoot the cause and take the necessary corrective actions?

ROM: S3Rx 3.0

OS: Android 4.3

Carrier: AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Wipe Dalvik and Cache in Recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I did but I'll try it again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
If you have tried it before, do factory Reset as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thanks. I just reflashed the kernel twice and wiped Dalvik twice... still freezing. A factory reset is my last option then it's back to stock if freezing still occurs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
I am pretty sure that ktoonsez has told me AOKP will not be compatible with other kernels unless they make it that way. It is not a kernel issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
^This. AOKP uses a custom WiFi driver, or so i've heard, making it incompatible with other kernels. Factory Reset won't help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MCFADONNA:
I'm using it just fine

---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------

I had problems before until I loaded the updated bootloader , modem etc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
It's still freezing and rebooting after a factory reset. Unfortunately, I guess it's back to stock for me...

EDIT #1: I just did a 2nd factory reset and the phone has only rebooted once so far. Previously, it has not gone this long without freezing or rebooting. I'm keeping my fingers crossed...

EDIT #2: I spoke too soon! Stock kernel, here I come... :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Damn I just flashed task rom getting lag like hell. And was thinking about flashing ktoonz aosp but I'm guess you can't cause task is AOKP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Did you try older version of KT747 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
No, because it seems like I'm the only one having these problems. I figured my phone is just not compatible for some strange reason. My phone also has a few issues with decimalman's kernel but it runs smoothly with the stock kernel. Go figure! :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I am willing to give that a try considering how much people love this kernel. Where can I find the older 4.3 versions? Is there a particular one you recommend I start with? I must have missed them in the OP.

I really appreciate your help in my pursuit to get this working for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xzil3d:
KT747 normally works on Task aokp. I too have immense lag issues with Task650 despite clean installing. I decided to flash this kernel and the lag issue is seemingly gone, however, as was previously mentioned, WiFi no longer works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MCFADONNA:
Try flashing gapps again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 65coupei6:
Since you are running S3Rx 3.0. There are many kernel options built in with Aroma?

Did you try using the KT kernel that was included?

Here is a link to the 4.3 KT747's : http://ktoonsez.jonathanjsimon.com/sgs3/tw/?C=M;O=D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thank you for posting the link to the archives. I did not find it in the OP.

Yes, I initially tried the KT kernel that's included with S3Rx via AROMA which caused my phone to freeze so badly I could barely use it. That's what led me to come here and download the kernel directly. I'll check out one of these older options and hopefully I will find one that works for my obviously "special" phone. :silly: Based on the features, I know it will save me some battery juice!

I am surprised that my phone seems to be the only one that is this "special". :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
The problem that you had is that the version of kt inckuded was configure for 1.8 ghz. Some phones just freeze is are oc. You can do 2 things first after install from Aroma go to Ktweaker app and reset to default values or just go directly and change the maximun value. I personally OC only one step or two.

Also reset the cpu voltage to stock table just in case it was changed too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thank you for your suggestions. I just reflashed the KT kernel that was included with S3Rx, ensured the max CPU was set at 1512 mhz, still used the menu option to set everything back to stock values, and it froze again (numerous times). I rebooted, set governor to ktoonservative and that made it worse.

Afterwards, I took the previous advice and flashed the older 1/15 kernel with the same results. Just for kicks, I flashed the latest 2/1 kernel with the same results. Maybe my phone just can't handle this level of awesomeness. :crying:

I'll revisit decimalman's kernel before I head back to stock again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
My last two suggestions is to up the voltage .25 at a time. To see if that stop rebooting.

The other option is clean install again S3RX 3.0 without anymod, don't install any app. Install latest Kernel and check.

If all are ok you can install the mods that you and if all are ok. Then install the app.

The last see you.:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Wouldn't overvolting erase any potential battery savings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wildnux:
I had similar problems before.. I tried cache, dalvik and data wipe and then reinstalled S3RX 3.0 with stock kernel. Then installed this kernel and now it works fine. I have even undervolted -150mv. I am using ktoonservative governer with row scheduler.

Hope that helps :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
WoW! I've tried everything you've mentioned with consistent freezing. Are you using the KT kernel included with S3Rx or did you download it from here?

​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
You're not the only one. I flashed a number of KT versions and got constant reboots. I noticed that changing ANY setting in KTweaker seemed to make it worse. I finally flashed the 2/1 kernel again (flash, wipe cache/dalvik, fix permissions) and didn't touch anything and it seemed okay. Not sure what, if anything, I did differently that time. After a couple days without reboots I started changing some settings one at a time and I haven't had any other problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wildnux:
I am using the one downloaded from here. I got problems using the one included in rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
For my last attempt, I am going to do a full wipe, flash S3Rx with no mods, flash 2/1 KT kernel, wipe cache & dalvik and fix permissions. If freezing or rebooting still occurs, I will bow out gracefully. I appreciate all of you for trying to help me and I will report back with my findings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Is it recommended to also format the system partition and the boot partition? Any drawbacks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
All of my effort seems to be in vain. I've executed all of the steps I mentioned above and my phone STILL freezes with this kernel, unfortunately. I'm off to DKP...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Maybe you should odin back to stock and root again and see if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thanks but nah... I'm done. I've already spent too much time trying to get it to work. I'm going to have to pass on all of the KT awesomeness.

The good news is the latest Decimalman kernel is running smoothly w/o freezing or rebooting! :good::good::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi. anyone have the January build? I think it was like 1/18 or 1/28 build? I accidently deleted it and I cant use the latest kernels cause they hate my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You can pick whatever you want anytime u want here:

http://ktoonsez.jonathanjsimon.com/sgs3/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Building up the latest guys :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Sweetttttttttttttt!

I'm back on s3 for couple days and I'm looking forward to get all the features I had on s4!

-Tunasty
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I'm crossing my fingers that my phone will mysteriously work with this build! :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 03.09.2014

1. Update Ramdisk for CMs new framework file to fix phone FC

2. A bunch of interactive governor updates

3. A bunch of ondemand governor updates

4. Lots of zcache updates/patches

5. remove extraneous loop in apexq camera driver

ENJOY !!!!!!!!!!! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
New tw build coming too or is the treat just for kk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing really new for Touchjizz right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
NO FAIR! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Unlike TW, there are constant updates to the AOSP Codebase. So that's why AOSP versions get constant updates. Most likely the next Touchwiz update may come when Samsung releases 4.4 source.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
All. Please understand this is off topic. Sniping and calling names doesn't help anyone. Please put an end. I have previously answered the question.