yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] vmancini3:
[MENTION=4932679]decimalman[/MENTION]

What's going on dude? I just had to say that I'm still rockin the 6-16 test kernel...and doing pretty darn good with it! How are things coming along with a new build? I hate to be "that" guy that can't wait...but I have to say I AM patiently waiting! Trust me....I have 4 kids and work approx. 60 hours a week...so I totally understand that there's this little thing called "life" that we need to attend to! Anyway...I'm sure that the new build, whether it be a new test build or a stable version will be kick-@$$! I'll be ready for it when it arrives!
[Verizon Samsung Galaxy S III] trvbone:
There's a 7/4 test build
[Verizon Samsung Galaxy S III] tvl76:
I'm running the 7-4 test build.

No problems, runs great with Slim build 7.
[Verizon Samsung Galaxy S III] vmancini3:
Thanks guys...but I'm talking about TouchWiz...
[Verizon Samsung Galaxy S III] Cruiserdude:
The 2nd best TW kernel for me (and first best you'll find here) is LeanKernel if you're looking for something stable and tweakable, give that a try if you want a stable daily kernel for now.
[Verizon Samsung Galaxy S III] decimalman:
I played with GPU OC a bit a while back and wasn't impressed with it. I've been meaning to look into a few related changes that might make GPU OC worthwhile, but until then I don't have any plans to support it.

Oh yeah, I was working on a TW version. :o I got bit distracted when some AOSP issues showed up, and I've been running CM ever since.

I haven't made any earth-shattering changes since the previous TW build, so I haven't had much reason to put out a new test build. I suppose I'm overdue to upload something new, but it would still have the freeze bug. I've gotten a bit closer to figuring it out, but I still haven't fixed it.

I'm grabbing a shiny new TW ROM now, and I'll do some work on the TW version over the next few days. Hopefully having fresh eyes will help with the freeze bug.
[Verizon Samsung Galaxy S III] decimalman:
Have a reward for your patience! I'm building something new for TW now. I merged in everything from AOSP, including some changes that haven't even made it into the latest AOSP test builds yet. From what I can tell, everything is more stable than the last build was.

Downloads are available via the link in the OP. Incidentally, does the new layout for downloads make more sense to everyone? I'm open to suggestions about better ways to organize the downloads, since I updated my build script to handle pretty much whatever layout I decide to go with.

Changelog:

UKSM: this was probably the only AOSP feature that wasn't present on the last TW build. It's merged in now.

Pulled in Samsung's latest code from the MF1 source drop (there's only a couple lines of changes compared to MD4, but whatever). I'm going to look into merging Linux 3.0.86 eventually, but this build is as up-to-date as any other TW kernel at the moment.

Rewrote the interaction code. The old code was unsafe and probably a bit slower than it should have been. The new code is written in assembly and is also safer.

Disabled SEC_DVFS. I haven't had much time to test, but this appears to fix the 1026 MHz bug, and will probably improve battery life.

Lots of freelunch changes: I haven't heard any complaints, so I merged most of the changes in nanolunch back into freelunch. I also made a small change that might make freelunch more suitable for gaming, and hopefully won't affect battery life or smoothness otherwise. nanolunch is gone, since it was a (successful) experiment anyway, and it'll disappear from AOSP builds shortly.

New toolchain fanciness: I haven't seen any freezes in the few days I've been running TW, so it looks like the new compiler I'm building with is pretty stable.

Regarding the changes in freelunch: I'd love to hear some feedback regarding battery life. A few settings have changed, but it's possible to switch back to "classic" freelunch: setting interaction_panic and hispeed_divisor to 0 will effectively switch back to the old behavior. I'm curious whether the changes I made will have any substantial effect on battery life, so reports are encouraged. :good:
[Verizon Samsung Galaxy S III] mickskillz:
I've actually switched now to TW... I was waiting on this kernel, b/c my phone loves nanolunch/freelunch. Thanks for all your time.
[Verizon Samsung Galaxy S III] vmancini3:
DUDE......THANK YOU!!!!! I'VE BEEN PATIENTLY WAITING FOR THIS!! SWEEEEEET!!!!!!
[Verizon Samsung Galaxy S III] philseven:
Okay I am jealous illusion rom and your test kernel now I am looking for an update

lol lol great work keep it up thanks for everything.
[Verizon Samsung Galaxy S III] Cruiserdude:
Awesome! Glad to have a great xda option for TW kernels from a proper dev! Looking forward to seeing these latest merges and fixes in the CM-compatible kernel, thanks for the quality work.

:thumbup:
[Verizon Samsung Galaxy S III] pocii29:
Hey everyone how goes it in here. Work has hit me like no other! I'm still running dkp and carbon with no problems! I'll try to do some test runs off latest builds!

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] decimalman:
After much dragging of feet, I'm finally uploading a new AOSP build. I won't be around for most of the day to offer support, but after five minutes of testing, everything seems to be working.

Changelog:

Lots of CM updates, including CAF stuff and SELinux support

Rewritten interaction hints code.

Merged nanolunch back into freelunch, including some optimizations that might make it perform better for gaming. As with TW, let me know if battery life and/or smoothness are affected.
[Verizon Samsung Galaxy S III] masri1987:
Can't Charge while phone is off

AOSP
[Verizon Samsung Galaxy S III] decimalman:
Strange. I just tested, and it's working fine for me. Can anyone else confirm?
[Verizon Samsung Galaxy S III] masri1987:
I'm on liquid smooth 2.9 btw
[Verizon Samsung Galaxy S III] bmeek:
Stock battery?
[Verizon Samsung Galaxy S III] krazie1:
I tried right now and mine is normal
[Verizon Samsung Galaxy S III] masri1987:
Yes stock battery, checked on bms and kt and it's working fine.
[Verizon Samsung Galaxy S III] vmancini3:
Did you already try flashing the stock kernel and then reflash the dkp kernel? Its worth a shot.
[Verizon Samsung Galaxy S III] masri1987:
Haven't tried that...

Gonna look for stock kernel.

Edit: I'm at work, tried to search but couldn't find. Can anyone link me plz
[Verizon Samsung Galaxy S III] smitty4_4:
Just wipe cache and reflash your ROM...that's the easiest way assuming you still have the ROM on your phone

Edit...unless your ROM comes with a custom kernel to begin with
[Verizon Samsung Galaxy S III] jdidtht:
I just came off liquid 2.9 and had no issues.. Just wipe dalvik reflash dkp and fix permissions.

anthrax infected sgh-t999
[Verizon Samsung Galaxy S III] masri1987:
So I tested it another OEM battery same results.

I did receive this device from asurion. Should I Odin back to stock and test it there?
[Verizon Samsung Galaxy S III] jdidtht:
If its doing it on the stock kernel on the ROM liquid or whatever you are running then I would restore a backup and see if its doing it on the backup and if it is still then I would Odin back and then if it was still then I would return it back to asurion for a new device. If youve already tried a different kernel with same results and different ROMs with same results I'd get rid of it.

anthrax infected sgh-t999
[Verizon Samsung Galaxy S III] masri1987:
Was thinking of doing the same @ Odin. Thanks guys for your help.
[Verizon Samsung Galaxy S III] vmancini3:
Hope you get it worked out....there is only so much that can be done to test things at the software level...until you come to the conclusion that it is in fact a hardware problem...
[Verizon Samsung Galaxy S III] masri1987:
So I flashed official cm nightly with dkp and it charges just fine when it's powered off. Per process of elimination has to be a the rom then
[Verizon Samsung Galaxy S III] jdidtht:
Weird but glad you got it sorted out. I had better battery with liquid than illusion but terrible data speeds with liquid. Showed I was on correct network and all build prop lines were the same and everything I could think of but 5mbs a sec differece between the two.. Thought I was slightly losing it but I flashed back an and forth a few times before sticking with illusion..but one thing stayed the same.. Dkp is a badass kernel

infected sgh-t999
[Verizon Samsung Galaxy S III] masri1987:
Yeah my battery with liquid and dkp yesterday lasted 14 hrs on heavy moderate usage with mixed wifi, I'm gonna wait til illusions updates.
[Verizon Samsung Galaxy S III] posaune76:
I got pointed here after asking about Bluetooth trouble on Liquid; my Bluetooth gets stuck "turning off" after having been connected to something (my car usually, but that's not the only device). Got hopeful and flashed dkp 7/21 testing with Liquid 2.9. Sadly, same behavior.

Am I missing something that I should try, or should I use a different dkp build?

Thanks, and happy to provide whatever info is needed, once I figure out how. Kernel noob.

--

Edit: I'm only having trouble after playing media. Without playing anything, it seems like I can connect, disconnect, turn off and on all day long.
[Verizon Samsung Galaxy S III] decimalman:
Interesting. Without actually investigating or anything, it sounds like the ROM isn't letting go of the BT connection like it should. I'm not terribly familiar with the ROM side of things, but I'd be curious to see a logcat from when it's not turning off.
[Verizon Samsung Galaxy S III] posaune76:
Thanks for getting back to me.

I'm going to assume I can figure out how to do that by flashing dkp-debug_v1.zip from post 3 (?). First time I've had to do such a thing.

I should have mentioned (sorry) that this is an AOSP-only issue. I've never had the problem on TW: neither stock nor any other ROM. I have had the issue on all AOSP ROMs, including AOKP Milestone 1 (the 4.1.2 one, not jb-mr1).

I'll try to generate a log and get it to you. Basic instructions, if you have the time, would be handy, but I'm familiar with using Google. :)
[Verizon Samsung Galaxy S III] ThunderRootedDragon:
I have the same behavior with BT and I'm on stock kernel. Not sure why you would be pointed here - I always pegged it as a rom issue or a tasker app issue, annoying but I never tried troubleshooting.
[Verizon Samsung Galaxy S III] posaune76:
I reported the issue on the Liquid thread, and a user there (don't remember who right now) seemed to think that others with the same issue had solved it with dkp.

I use Tasker too, but I've had the problem both when Tasker manipulated BT and when I did it myself. Don't remember whether I had Tasker running at the time I did it myself, though. Something to try when getting the logcat, I guess.

Not having problems on a TW rom right now, running dkp & using Tasker. Would like to get back to AOSP if I can...
[Verizon Samsung Galaxy S III] decimalman:
The zip will do the trick. I'm actually also interested in some information that the zip doesn't collect as well, so I'll PM you with some details.

[MENTION=3517420]mikedavis120[/MENTION] FYI I'm interested in the output from lsof.

Thunder: It's probably not a kernel issue, but I'm too curious to ignore it. :)
[Verizon Samsung Galaxy S III] EnemasRfun:
Whoops! That was me, I wasn't sure if the BT issue was the same as the one you are having, I just remembered there were some BT issues that were resolved by dkp a while ago, so I sent you here in hopes they were!

[MENTION=4932679]decimalman[/MENTION] rules so hopefully he'll be able to help you anyway :fingers-crossed:
[Verizon Samsung Galaxy S III] david_hume:
DKP for touchwiz works like a charm. Better battery life than what I ever got before. :)

sent from my GS3 from the Infected Army
[Verizon Samsung Galaxy S III] aj8600:
7/21 3.4 kernel killed my data, anyone else?

No No Kernel Optimized Galaxy S3
[Verizon Samsung Galaxy S III] coldconfession13:
I wonder how 10.2 is coming along for our device
[Verizon Samsung Galaxy S III] LegoFarmer:
Let's hope awesome lol. I'm excited. It is looking like Samsung is updating ours for 4.3, which means some sick TW roms, too.
[Verizon Samsung Galaxy S III] Eyalkn:
[MENTION=4932679]decimalman[/MENTION] You probably already know but the new CM10.2 doesn't work with the regular 3.4 kernel. Already missing your smooth kernel.
[Verizon Samsung Galaxy S III] decimalman:
I've seen some activity on a few new CM kernel branches, but haven't built any of it yet. I'm expecting a few more commits from CM, but once they merge everything into the cm-10.2 branch, I'll take it as a sign that I should merge. If they start putting out nightlies before then, I'll definitely merge everything myself and get a build out ASAP.
[Verizon Samsung Galaxy S III] Eyalkn:
:) I am on their nightly now. They started today.
[Verizon Samsung Galaxy S III] decimalman:
Strange, I'm not seeing any 10.2 nightlies yet. I'll get to work anyway. :)
[Verizon Samsung Galaxy S III] Eyalkn:
You were right. I am on the unofficial build. Thank you for always delivering the smoothest kennels.
[Verizon Samsung Galaxy S III] pocii29:
The rest of the gs3 people really don't know what they are missing in here

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] vmancini3:
Oh on the contrary... I do in fact know what I'm missing:D....but I know that devs like [MENTION=4932679]decimalman[/MENTION] have a lot on their plates and I will consider myself privileged when he releases another TouchWiz build! I'm not gonna rush him. I am not going to bash anyone's opinion on what type of ROM they like to run, and at the same time that everything and anything AOSP is really cool....I've come to learn that its just not for me....so I'll be patient and have faith knowing that a sweet new (stable) dkp kernel is right around the corner!
[Verizon Samsung Galaxy S III] dincdoes.me:
Touchwiz build works great so far for me oc. fast charge. No reboots that's all I want so far.
[Verizon Samsung Galaxy S III] jdidtht:
I've tested the hell out of your release man. For me on my rev0 device and my girls rev4 6/14 cm build gives us both almost double the battery life on comparison to the later releases.

infected sgh-t999
[Verizon 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.
[Verizon Samsung Galaxy S III] gzsmooth:
Having bad screen flicker w your newest test build on Dirty Unicorns. Disabling HW overlays took care of it
[Verizon Samsung Galaxy S III] decimalman:
New builds coming soon. I reverted an optimization and went back to Linux 3.4.53, but it's better than nothing. The flickering seems to be gone, and overclocking doesn't cause an immediate reboot.
[Verizon Samsung Galaxy S III] thelangosta:
No issues with the Twiz kernel that I have found so far on CR7. 21 hours and counting at 39%battery remaining and a little under 3 hours screen on. Good job.
[Verizon Samsung Galaxy S III] vmancini3:
Wish I had good service at home to be able to let my phone idle for decent periods of time....at work where the signal is very strong, my battery drain is VERY minimal! Although with the most recent tw kernel...I was able to pull off over 4 hours screen on time and I was on battery for just under 14 hours and I also had an hour of voice calls!!!:cool:
[Verizon Samsung Galaxy S III] thelangosta:
I'm a stay at home Dad. Wifi=good. I left the house for about 4 hours today but the rest of the time I was on wifi. Spent way to much time on xda because the kids were entertaining each other.:D
[Verizon Samsung Galaxy S III] sbattosai:
Hi Decimalman, sorry if you answered that question already but I can't seem to find it. Is your TW kernel compatible with ExFat SD cards? I am running stock right now but wouldn't mind trying your new kernel if ExFat is supported...

Thanks
[Verizon Samsung Galaxy S III] 0xScott:
AOSP 4.2 8/12 build is giving me really bad screen flicker, even with disable hw overlays set. I'm on the latest nightly CM build from yesterday.

I'll have more time to test it tomorrow. I pulled copies of several older builds to try in the morning.
[Verizon Samsung Galaxy S III] 0xScott:
The 8/11 build (more reverts branch) seemed to stop the flicker for now.
[Verizon Samsung Galaxy S III] tampaboy1984:
Running the new Test Build on TW Rom Bone Stock 3.3, using trickster mod for kernel control. So far everything runs smooth. Are there any setup suggestions for min 384 - max 1836000, setup?

Which i/o scheduler should I use?
[Verizon Samsung Galaxy S III] neh4pres:
Any change log for the new release?

Via my Google Galaxy S3 running magic beans
[Verizon Samsung Galaxy S III] tampaboy1984:
Kernel settings keep reverting back to stock setting after reboot. :-/
[Verizon Samsung Galaxy S III] thelangosta:
I like freeluch/zen combo but I don't over clock/undervolt. More worried about battery life and smoothness than all out speed.
[Verizon Samsung Galaxy S III] RoboJoe:
So, I installed this kernel on my VZW GS3 running 4.3 PA and it booted and in the process of my apps starting up (The ones that autostart, like Tasker) the phone crashed, then froze at reboot, causing a corrupted /data/data partition, which required me to have to Odin back to stock to fix.

Annoying, sure, but these things happen-- my question is whether that was just some freak occurrence, or if there's something I need to do to stop that? Is this what the extra zip file in the OP is for? I consider making it past the kernel screen to be a "boot", which it did, so I'm not sure if "use this if your phone fails to boot" applies.

Thanks!
[Verizon Samsung Galaxy S III] steve97ta:
Trying out the test build and using this as well. No overclock or undervolt. Pretty darn smooth

---------- Post added at 12:51 PM ---------- Previous post was at 12:47 PM ----------

using rom toolbox myself and they are sticking for me
[Verizon Samsung Galaxy S III] griz.droidx:
Man, I just installed it on Slim 4.3 and it didn't do that. I'm using the latest build BTW. Downloaded today. It may have been a few days old, I can't remember off hand. I'm glad my phone didn't do that, Shew thats a lot of work. Couldn't you get into Recovery or would it just not help?
[Verizon Samsung Galaxy S III] RoboJoe:
I tried running e2fsck on the data partition but it didn't help-- it either crashed TWRP or stalled in process and adb wouldn't find the device. It was undoubtedly due to the crash in the middle of the booting process that did it, not the kernel itself-- I just wanted to know if it was some known issue that I could work around, or if it was just random dumb luck that caused the crash itself.

Seems like random dumb luck to me, since this thread isn't full of "my phone keeps rebooting" comments. :)
[Verizon Samsung Galaxy S III] decimalman:
I haven't done any work to support exfat, so the exfat module isn't likely to work. I've been spending a lot of time recently on TW, so it's something I can look into at least.

Strange. I've been running the 8/12 build for 24 hours or so without any sign of flickering. Does the 8/11 "more-reverts" build flicker?

I cleaned up my source a little bit, but didn't make any changes worth noting. Apparently, I may have re-introduced the flicker on some ROMs though, so I'll have to test. Feedback would be appreciated.

This is an app issue. If you're using Trickster, it sometimes does this until you adjust the grace period.

Ouch. ext4 turns out to be surprisingly unreliable when unexpected things happen (recently lost some data myself :crying:). Crazy failures like this are certainly not a known issue, or I would definitely remove the builds. I'm leaning towards this being a freak occurrence, especially since 4.3 in general is so new and unpolished on the S3, but I'm still worried.

The vmin zip adjusts the processor's minimum voltage. I would define "won't boot" to mean that your phone isn't stable for long enough to unlock, open a tuner app, and increase the voltages yourself. If you haven't needed the vmin zip previously, or have been able to run other custom kernels, the minimum voltage probably isn't the issue.
[Verizon Samsung Galaxy S III] 0xScott:
I've been running the more-reverts build all day without a single flicker. The 8/12 version was like a strobe light.
[Verizon Samsung Galaxy S III] bmeek:
I'm running the same "more-reverts" CM10.2 build by Mastamoon. After flashing the latest dkp kernel, I initially got what I assume is described as "screen tearing" while scrolling through Settings (checking the "disable hardware overlays" option made this go away).

Things seem smooth now :).

Thanks!
[Verizon Samsung Galaxy S III] vmancini3:
I didn't know what any of you guys were talking about because I've been running TouchWiz and on the latest kernel I have more than 80+ hours of uptime, no flickering, or any other issues for that matter! Settings stick just fine using SetCPU and the battery life/responsiveness of my phone is just out of this world!!!! WINNING!!!!!
[Verizon Samsung Galaxy S III] steve97ta:
Yup no probs here on bone stock 3.3. Using rom toolbox pro all settings stick on reboot.
[Verizon Samsung Galaxy S III] decimalman:
Good news, then:

New 4.3 test builds! I merged in the latest CM commits, which seems to fix the screen barfage on newer ROMs.

Still not sure what's giving 0xScott grief, though. :(
[Verizon Samsung Galaxy S III] 0xScott:
I loaded the latest nightly CM with no problems (no flicker or anything), then installed the 8/12 build. My phone started constantly flickering. I disabled my tasker profile that sets "disable hw overlays" and rebooted to see if that had any effect. While scrolling through the settings menu, my phone froze for a couple minutes (this was the previous behavior and the reason why I set up the profile in the first place).

I'm running XPrivacy / XPosed framework, SwipePad, and Tasker, though I don't think any of those are the problem. My phone doesn't randomly reboot, so I'm not sure last_kmsg would help.

I'll check through the thread tomorrow and see if there are any applicable troubleshooting suggestions. If there's something specific I can do that might provide additional information for troubleshooting, I'd like to help.
[Verizon Samsung Galaxy S III] RoboJoe:
With the 8/13 test build for VZW 4.3 AOSP, I get screen overlay animations that are "jittery" (notably, notification pulldown). No combination of settings in the developer's menu makes it smooth again. The last rev did not do this.

Reverting, but I can reinstall if you need some information from me while running the new build.

Edit: In case you're wondering, reverting to the last build resolved the issue.
[Verizon Samsung Galaxy S III] Chitala383:
same here
[Verizon Samsung Galaxy S III] minnysota:
Love your kernel decimal! Just wanted to try and offer some help on the flicker issue. Gideon posted this in Mastamoon's unofficial thread: http://xdaforums.com/showpost.php?p=44594784&postcount=1176

I'm not sure how it works with using another dev's fix (or maybe it was simply a recent CM merge), but I wanted to bring it up just in case. Forgive me for the development noobishness! :eek: Thanks again for a great kernel.