yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Updates! I've gotten a few major bugs fixed for TW, made a few changes for AOSP 4.2, and noticed enough 4.3 ROMs coming out to finally release for it. That means three new test builds today (and maybe another round tomorrow with a shiny new toolchain). They'll show up over the next hour as I get them built.

TouchWiz:

Fixed a handful of bugs. Frequencies should apply properly. I think there's still a few quirks to work out, but nothing that will ruin your day.

Updated most everything from AOSP.

AOSP (4.2):

Updated to Linux 3.4.56.

Made some changes to the voltage interface. A few more apps should be compatible now, and hopefully I haven't broken any that worked before.

A handful of new optimizations: compiler optimization hints, cleanups in the video driver, and a huge speedup in touchscreen handling.

AOSP (4.3):

Merged in CM's commits for SELinux and updated drivers.

Everything from 4.2 came along for the ride.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hungmung:
Trying the 4.2 new testing kernel and getting a nasty screen flicker when idle.

Sent via carrier pigeon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
4.3- changing overclock instantly reboots the device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Looking into these now. This is what I get for merging stuff immediately before releasing. :( Hopefully, I'll get new builds out shortly to fix them.

Edit:

The OC issue is on 4.2 as well. I've got it fixed already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
Have you adjusted the thermal throttling in your touchwiz kernel? I dont like a hot phone:p so far its been better then other kernels for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
In order to change the maximum frequency, I had to neuter thermald (the service that does thermal throttling). It should still do its job, but dkp sometimes lies to it to keep it from causing problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
Well it's running 10 degrees cooler then stock kernel so thanks for that! Any recommendations for amount to undervolt? I'm at -50 across the board right now, will I see a benefit going further?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Probably not. You might be able to get away with -75, but that's pushing it.

In other news, there's new 4.2 builds coming. I had to go back to Linux 3.4.53 and disable an optimization, but it's better than nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
The newest build of 4.2 (08/11) causes some flickering, and I also noticed nanolunch is gone. Flashing 07/21 revealed the same thing, so I flashed 07/04 to get it back. I'll just stick with this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I merged nanolunch back into freelunch, since it seemed to behave well.

Are you getting flickering even with the newest build (the more-reverts one)? I reverted a bunch of stuff that should have fixed it--I haven't seen any flickering since I flashed it. If it's still there, I'll have to dig a bit deeper to track it down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
So nano settings are in free? Didn't realize this. Is there a newer changelog than one in OP?

I see you uploaded a newer version of 08/11 after I downloaded the first version. I'll flash that and see what happens.

Love your work! Thanks.

-----

The 08/11 build with reverts seems fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Yep. nanolunch was supposed to be a quick experiment to make sure everything worked, but I never got around to merging the changes back into freelunch. Oops.

I usually update the OP for "stable" builds (which usually turn out to be incredibly unstable :p). For test builds, I usually just include the changelog in the post where I announce the build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
I just flashed the Test build DKP 4.3 uploaded at 16:55 on Pwncakes 10.2 8/12 build and she wouldn't boot. Stuck in a bootloop at initial boot.

Should I try the other test build? Is anyone having success with the 4.3?

Thanks by the way!! My device runs really well on Freelunch.

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
No problems here boots with pwncakes 8/12 10.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Appreciate the response sir. I'm up and running now. May have just been a bad flash.

Love me some Freelunch!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Finally looked through PwnCakes193's thread. Glad to see you got up and running. Someone on VZW mentioned that disabling HW overlays helped with the graphical glitches. I'm in the process of building with the latest CM commits to see if it helps any. New test builds soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New 4.3 test builds! I merged in the latest CM commits, which seems to fix the screen barfage on newer ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Thanks man, honestly your kernels are simply amazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Screen barfage is now fixed.

Thank you sir!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
What are you're settings? (;
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Here ya go.

Normally I don't OC this much just but wanna see how fast I can make this puppy move. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
in trickster mod, under info, how hot does your cpu temp get after a good amount of use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Average is around 90 degrees.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
Celsius?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Nooooo... Fahrenheit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbaler:
Hey decimal man, I got a random reboot on the newer 8/11 kernel, I have yet to flash the newest but here's a last_kmsg because I don't know if it got fixed in the newest

http://db.tt/nzEgRdF7

Edit: running the newest on the paranoid android 3.96 I am now getting the screen 'barfage' you guys were talking about, I tried disabling the hardware overlays to no avail, going to have to revert back to 8/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
Trickster mod show it with a c though right? Mine gets up to 65 or 70 under heavy usage, cpu temp, battery stays at 40
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
You're better off staying on the older build until the next PA build comes out. The new build fixes the bug on newer ROMs and causes it on older ROMs.

The last_ksmg you posted points to an issue with the ROM not handling the camera correctly, which is an ongoing issue on 4.3 ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Since you don't over clock I just kept the min and max stock. But changed everything else. Should I go with yours? Or stay stock. Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Another round of new AOSP builds! I think I've gotten the flickering fixed for everyone now. 4.3 builds are up now, and 4.2 builds will be up shortly.

Reminder: 4.3 ROMs built before 8/13 are only compatible with kernels built before 8/13; 4.3 ROMs built on or after 8/13 are only compatible with kernels built on or after 8/13.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
TBH with ya that's impossible to answer. Every device acts a little differently when it comes to kernel settings. Some devices can OC up to 2000, while others have freezes and or reboots.

Some devices can Undervolt while others will not be able to wake up from sleep.

I can go on for a while but I'm sure u get the idea. :)

---------- Post added at 04:12 PM ---------- Previous post was at 04:10 PM ----------

Yeah but I check my cpu temp with a System info widget.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Loving this kernel. (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Flashed your TouchWiz Kernel earlier today, I like it so far, everything seems to be running good. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Lost torch on pwncakes 8.14.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Awesome kernel! Loving the battery life. Using the freelunch governor & it's working great!

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
What is the minimum CPU frequency available on this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
384

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Is that the default or the absolute lowest the kernel allows? Ktoonsez's kernel has 384MHz as the default but there are lower frequencies you can select(down to 81MHz).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yeah. It's the lowest. There aren't any frequencies below that. The kernel runs good though. I'm getting the best battery life with this one. I've also tried bionic sheep & BMS.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Alright, I'll consider it. I want to upgrade to CM10.2(from 10.1) but I want to stick with a custom kernel for the huge battery life improvements.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
use the freelunch gov, and row. and you're battery life will be at best.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New TouchWiz builds! sbattosai pointed out that Samsung open-sourced their exFAT driver, so I decided to throw a new build together.

Changelog:

Finally added Mike Kasick's ram_console and hardboot patches. last_kmsg will actually work now.

exFAT support for 64 GB SD cards. The exFAT driver seems to work on CM10.2, but I haven't tested it thoroughly, and I haven't tested it at all on TW. If you have an exFAT SD card, you should backup any important data before flashing.

The exFAT driver works fine on AOSP as well, but I'm not sure what (if anything) needs to be done to get ROMs to use exFAT SD cards. If anyone has a spare SD card (I don't) and wants to test, PM me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update, but after flashing the kernel mobile such at Samsung s3 screen.... Had to flash another kernel fit booting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Can't get enough of this amazing battery life ! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Can you share your settings, please :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Rom: Quantum v1

Gov: Freelunch

Sched: Row

Voltages Upped 50 from stock (the uV was too much for my phone to handle)

rest is stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks for letting me know. I'll flash to TW shortly and see what's going on.

In the meantime:

New AOSP builds are on their way. It looks like AOSP 4.3 (and possibly 4.2 as well) should handle exFAT automatically, so if you a) have an exFAT SD card, b) are using the newest test builds of dkp, and c) have made backups of anything important on said exFAT SD card (the driver hasn't gotten a lot of testing yet), you should be able to use your SD card without any headaches.

Changelog:

Added Samsung's GPL'd exFAT driver.

On a side note: I'm not a lawyer, so I'm not terribly familiar with the implications of Microsoft's patents on exFAT. My understanding is that in order for Samsung to redistribute the code under the GPL (which it is), it must be royalty-free for anyone who "receives a copy" (GPL parlance :)), and so it should be okay for us to use. Anyone with a legal background care to comment?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
decimalman, you're a kernel god. downloading now and gonna flash. but do you mind sharing ALL you're kernel settings? :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
teh kernel's read ahead buffer size is 128, is it supposed to be that low? other kernels have it as 1028 right? just curious because im a noob, why is it that and what does it do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
Latest kernel has weird screen choppiness on pa
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Once the kernel settles in, everything is smooth as silk on stock TW. Thanks for keeping us stock users in mind, DM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The readahead buffer controls how much extra data is read whenever a file is being read. Having extra data waiting means the app doesn't have to wait to read more, but it eats up system resources to read the extra data.

128 is the mainline Linux default, and I haven't changed it. Tuner apps that can change it are readily available, and the ideal setting depends on which I/O scheduler you're using. deadline and similar tend to respond best to small values, while cfq and similar like larger values.

I did some quick testing with the deadline and cfq schedulers this morning. deadline saw ideal performance at 256, and cfq seemed to like 2048. deadline saw very little performance increase. cfq saw more improvement, mostly because it doesn't handle the default setting very well.

EDIT:

I'm guessing (since you didn't provide much detail) that you're running PA 3.9x. dkp builds from 8/13 onward require some commits from CM that the PA dev apparently hasn't merged yet, so you'll have to use the 8/11 build of dkp. Also, consider nagging the dev to update--the commits in question improved performance noticeably.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Thanks for the explanation!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
On TW, using Trickster, should I leave mpdecision enabled? I know the OP says it is automatically disabled, so does it make any difference either way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Doesn't make a difference if you're using freelunch. With other governors, if you'd rather use auto-hotplug, disabling mpdecision will automatically enable it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
I need some help with a minor issue of overheating for my phone with this kernel :/ since it doesn't have gpu frequency idk how to calm this thing down from heating up with light usage.

I'm using freelunch with row and UV - 50 across the board with everything else stock. How can I not get it to heat up so much? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Raise your voltages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
How is your battery life?

With u being mostly stock and UV'ed, I'm thinking there may be a rouge app somewhere going nuts.

How is your data single or are u on WIFI? Sometimes if I have overheating issues it's my device struggling to find a good signal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
actually, my battery life is great, getting about 4+ hours screen time from one full charge. uhh the signal for me is pretty good, wifi is on sometimes. the UV was just applied AFTER i felt heating issues to see if I can cool it a bit, it seems to do no help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Working on optimizing battery life with Quantum. Not getting the kind of life that other people seem to be getting, and trickster is such a PoS kernel settings app.

row with read ahead buffer size 2048

freelunch

min/max is 384/1512 - when I change the max to something lower it always gets changed back even though I save.

MP-Decision on

I think OC +50, my 384MHz voltage is 900 and i think the default was 850

I may find another app for managing settings....this is buggin me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Best battery coupled with quantum.. Randomly stuck in boot loop in 1.11. Didn't have any issues with 1.10. Maybe due to kernel updates in 1.11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
battery pull and try again. if not re-download kernel. also the vmin file as well. flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Can the settings for dkp be set from the terminal and if so is there a faq/diy?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
I found that after the reverted 08/11 build settled in, that with freelunch (which includes nanolunch) the battery life was not good...nothing like with just nanolunch...both with row. So I flashed back to 07/04 and battery life is back to good again. In fact, I'm going to stick with this and Slim Build 8 for the foreseeable future until 4.3 is as reliable as this setup. I know others say 4.3 seems quicker, but I'm having no issues with 4.2.2 for what I do. And I like not having to tinker with dkp kernel settings to get good battery plus performance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
Anybody else is having a problem with gallery? Every time I open it hard reboots my phone, fixed permissions ...and no luck I flashed ktoonz kernel and it stop crashing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I have not been having any issues with gallery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ingram10:
Thanks for great kernel on screen time 3:45 17 hr's total
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
deleted - dev-host back up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
Carbon 8/19 us extremely stable. Just as stable as most 4.2.2 ROMs.

infected sgh-t999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I am getting powermanagerservice wake lock with this kernel & latest Quantum rom. It isn't allowing my phone to enter deep sleep. I am not getting this on other kernels. Does anyone have any idea how to fix it? I looked in partial wake locks & it looks like mms connectivity is the one causing it.

Sent from my Galaxy S3 Tapatalk 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iCyanideS3:
Need help

Hey guys I've heard really good things about this kernel and I really want to give it a shot but I don't know what version is best for my device running cyanogenmod 4.2.2 the 8/11 nightly build. Thanks in advance for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Just use the latest AOSP version for 4.2, what's the problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jo_hammer:
Just flashed latest 4.3 and right away I noticed my screen lag I had with BMS kernel is completely gone. Well done OP. Thanks for your work

And bluetooth works flawlessly!!! This just made my week. My new favorite 4.3 kernel. Hands down. I love you OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Any update? (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
I want kernel

Can anyone give me a link to download this kernel i
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I recommend you check the OP instead of posting in all my threads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Quit the trolling and look in the op.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
Sorry I don't know wat op is I'm new to this can u explain
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
"Original Poster" or "Original Post", meaning the first post in the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
If you don't knot what the op is you shouldn't be on xda. Maybe you should Google also before posting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
I don't see a link on the opening post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Please leave xda. Did you even root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
Yes I'm running quantum rom I just don't know how to get this kernel it sounds amazing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Scroll down to Stable and Testing Builds. Click it. And you're downloads are there. I don't know how you even got to that ROM if you can't read instructions. Please leave this thread and troll somewhere else. If you don't know what to do, from what I just told you then rooting and everything on xda isn't for you. Please press CTRL + W on you're keyboard and that will solve you're problems. (: Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jacobz1996:
Thanks a lot I got it I'm kinda slow at things lol sorry:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
When I reboot the phone I don't have sound!?

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New AOSP 4.3 builds are on their way.

Changelog:

Disabled exFAT. It needs ROM support to be useful.

Synced up with CM.

Fixed a stray bug or two.

New toolchain. My compiler laboratory exploded, so it's lightly modified Linaro GCC this time around.

EDIT: Looks like I missed a bug that breaks hotplugging (and also everything) with some governors. I'll get new builds out tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Looking forward to that and new Quantum release. Great job man! You should update more often. Cause you're kernels are the bomb. And kernel.org and stuff is always getting updated. Just a thought though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
He can update as he's available. No demand of course. Anyways check the link, the build's been there almost since he posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
I know, I know. Not demanding. Lol. And, didn't even notice that it was up. Lol. Gonna flash this for tomorrow morning with a new ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update, was about to flash on Quantum. Will wait for the fix to be released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Good news! New, fixed builds are on their way.

Changelog:

Fixed a bug where applying certain governors repeatedly could cause major problems.

Improved automatic auto-hotplug. Auto-hotplug will take over if a tuner app breaks mpdecision.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Giving this a go. Everyone raves about freelunch so lets play. Loaded up the 9-2 test build and fiddling with settings now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Getting that reboot once I enter the gallery on the 9.2 build:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
what ROM ? Works fine for me on Slim beta 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
I'm Running Quantum v1.20
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Quantum as well here, but no such issues. Did you clean flash to see if that fixes it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
I'll try that. I came over from Illusion and did made sure to wipe/format everything.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
I came from illusion as well and having 0 issues at all on Quantum 1.20, and getting awesome battery life :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
With the recommended tweaks from the OP? I'm not sure it that's my issue. Guessing not as this was the only app that locked up.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hi Decimelman,

CM has just pushed 10.1.3 RC2, can we expect updates for the 4.2.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
Posted my settings in a recent page on Quantum's thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Facing terrible screen flickering on CM 10.1.3 RC2 with DKP 4.2.2 8/18 Test build. Any plans to update the kernel for the latest fixes in the CM 10.1 Branch? Don't think after this any changes would be required in CM 10.1 branch as 10.1.3 stable will be the last build

---------- Post added at 06:45 AM ---------- Previous post was at 06:36 AM ----------

Any plans for updating the TW kernel, the last update made the mobile unbootable?