yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] decimalman:
Dev-host is down, and it looks like they might be down for a while. They haven't even posted an update on Twitter about whatever is going on. A temporary MediaFire mirror has the newest test builds.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
---------- Post added at 06:47 PM ---------- Previous post was at 06:43 PM ----------
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test builds are going up now. The boot issue should be fixed.

Changelog:

The boot freezes should be gone. Let me know if you're still seeing them.

Linux 3.4.48, lots of CM commits, and a few new GCC compiler updates

Added UKSM
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Boot freeze? I've had nothing at all.. This is the most stable 3.4 kernel there is .. Not one reboot not one lock up someone mention Bluetooth was fudged on last release although i cant confirm that. Thanks decimal
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test builds are going up. BT should be working--I'm able to FTP to another device and transfer files, but I don't have any other BT devices to test with. Anyone who's been having issues, please let me know if you're still having issues on the new build.

Changelog:

Disabled an optimization in the dhd module. BT appears to be working.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Thanks decimal

absolutely not infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] decimalman:
Exciting news: I'm doing two releases today!

I've decided to release a new stable 3.4 build. It's not much different from the latest test build. Off the top of my head, these are the only changes since the last "stable" build:

A few new CM commits, Linux 3.4.49, etc.

Reversed the Trickster "Override Minimum Voltage" setting. I actually read the description and realized the previous logic didn't make sense. Now, turning the setting off correctly allows lower voltages.

Actually boots, BT works, and all the other exciting fixes I've made since the previous "stable" build. :D

As usual, downloads are linked in the OP.

I'm also releasing a very, very experimental TW kernel. It's so experimental that I'm not even going to link to it in the OP (also, I'm too lazy to bother :p). Previous versions didn't brick testers' phones, but I guarantee that there are bugs. Here's what to expect:

Basically everything from 3.4 has been ported, but very little has actually been tested.

GCC 4.8, -O3, LTO, and all the other optimized fanciness included in 3.4 dkp builds. Performance isn't quite where I'd like it to be yet, but it's certainly not awful.

Crazy bugs. Something is setting the minimum frequency to 1026 MHz during boot (which you should change back to 384 MHz!), there may be issues with calls on some carriers (please let me know, and if possible provide a logcat and/or dmesg!), freezes might happen, and I'm sure there's more bugs I haven't even heard about yet.

Downloads are available here.

Edit: Just realized I didn't tell my build script to make a release, so builds were uploaded into the experimental downloads instead. Real release builds will show up in the stable downloads page shortly.

Edit 2: Release builds are up in the stable downloads page.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Ooo your playing with twist kernels now. Cool cool

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
Yep. There's been a few requests, and I've been sitting on the code for a while. It's been like a month since I sent out test builds to a few people. I got a couple issues fixed earlier today and decided it was time to put up a public test build. There's still a few obvious issues though, so it'll be a while before it's ready for daily use.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Well that's good. Im sure it will be good man. If u need any input give me a shout. Latest cm kernel running smooth..

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] garz:
Dumb question, and can't find an answer.. What's the uninstaller file?
[T-Mobile, Samsung Galaxy SIII] decimalman:
It cleans up a few extra files that dkp creates. It's not really needed anymore, but my build script still generates and uploads it automatically.

In the 3.0 days, I used to overwrite a couple ROM files in order to get everything set up correctly. Unfortunately, the changes I made weren't really compatible with other kernels, so I decided to make an uninstall script to restore everything.
[T-Mobile, Samsung Galaxy SIII] garz:
Gotcha.. glad I asked.. Thanks, again for the sweet kernel. It's BUTTER!
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Decimal what are you currently using for read ahead? Im used to running 2048 but i saw default was much much lower. Any particular reason or benefit to a lower read ahead?

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
I haven't made any adjustments to the default read ahead. Flash memory is fast enough these days that I don't really notice much difference from tweaks like this. FWIW, literature on the subject suggests that the ideal tuning for read ahead is largely dependent on I/O scheduler, with deadline (and similar) responding well to high settings and cfq responding well to low settings.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Right.. I've done some reading on the subject but i as well notice negligible difference between real world or benchmarks so i was just curious as to lower vs higher settings. Thanks for the input

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test builds are up! They're not in their usual location. I decided to re-arrange the upload paths on dev-host, so (for today anyway) uploads will be going here. I'm probably going to change the paths again in the near future, but I'm hoping that it will be much easier this way.

Changelog:

Merged a zillion CM commits

Linux 3.4.51

Disabled auto-hotplug during boot
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Oh sweet

Edit. Battery seems good. Smooth as normal no artifacts or glitches no reboots audio is good Bluetooth seems to pair. Good release man. But you already knew that

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test builds! I haven't added anything new, but that's no reason not to upgrade.

Changelog:

Synced up with CM and Linux. Newest CM commits are included, as is Linux 3.4.52.

Finally updated my toolchain. A month's worth of Linaro and GCC commits shouldn't hurt performance any. :)
[T-Mobile, Samsung Galaxy SIII] ssjgotengt:
Ktoonz kernel isnt as good as expected... is this a stable kernel? and will it work with LiquidSmooth 2.7?
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Yup an yup

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Funny. I've never seen the nanolunch and free lunch govs before. After using them I wonder why it's not more successful and common in other kernels . Good job and thank you. Running well on Liquid Smooth 2.8
[T-Mobile, Samsung Galaxy SIII] decimalman:
Glad to hear they're working well for you. freelunch is a pet project of mine, and not a lot of people know about it since (AFAIK) it's only available in dkp. nanolunch is actually just an experiment, and I'm going to merge most of it into freelunch in the next round of builds.

The biggest reason that other kernels don't have them is that they require a few extra features that are specific to dkp. There's no reason that other devs can't port the extras over, but it would take a lot more work for them than most other governors.

There's also the issue of hardware compatibility: currently, they only work on dual-core Krait CPUs. I've been meaning to rewrite them to work properly on other CPUs (and fix a few things that have been bugging me), but I haven't gotten around to it.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New TW builds are going up! I might have forgotten that I was working on TW for a while. :o 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:
[T-Mobile, Samsung Galaxy SIII] jdidtht:
I'll let you know.

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Just flashed on T999L running pacman nightly 7/13. No issues so far. Using nanolunch/zen. No over clock.

Any recommended under volt settings? Usually I try-25 each step and test, then go 25 more. But I'm new to the gs3 and my understanding is that people are able to uv as much as 200mV on some steps?!

Sent from my T999L on PACman
[T-Mobile, Samsung Galaxy SIII] decimalman:
The usual warning still applies: all devices are different, and some will respond better to undervolting better than others. Since you're new to the S3, you may not have read up on the quirks of the processor. I don't think there's a concise introduction to stuff like this, so hopefully I can save you a lot of searching. :)

A few processors won't tolerate low voltages (i.e. anything below 1150 mV), and get crashy and/or glitchy on most custom kernels. If you're up and running without needing the vmin zip, you probably don't have one of those processors. The vmin zip neuters undervolt support, so if you flash it the voltage table will mostly be meaningless.

There's also three processor bins ("PVS"es): "fast", "nominal", and "slow". The PVS name doesn't actually correspond to speed, just the voltage the processor needs, so there's a separate voltage table for each PVS. Some kernels just use one table, which means that depending on which PVS you have, voltages might start out higher than the stock values. dkp (and probably others) use the specific table for each PVS, so voltages will effectively start out at stock values.

You can probably decrease the voltages on the lower frequencies further than the upper ones. On my phone (a fast PVS that undervolts pretty well, from what I gather), I can't undervolt 1674 MHz at all, 1512 MHz will tolerate -75 uV, and 384 MHz will run just fine at -150 uV.
[T-Mobile, Samsung Galaxy SIII] ryandubbz:
Does mpdecsion smd.exe, smd, and qosmngr all have to have .bak added to them to disable these with this kernel? I'm runninglatest moar rom and it's 4.1.2 also where do I get the app to mess with over clocking and under volting thanks this kernel is butter smooth and great battery
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
You brother just made my day..

anthrax infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] garz:
You and me, both. THANKS, decimalman!
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Latest kernel on illusion ROM. Won't charge to 100% stops at 99% I'm also having some abnormal drain while kernel is sleeping.. Not on liquid but on illusion.. I killed any scripts in illusion in sys/bin and initd but didn't help. I flashed another kernel and on illusion it is fine. Now on liquid smooth dkp runs fine.. What if anything on the kernel side wouldn't play well with that ROM?

Edit I ran BBS just showed some kernel wake locks but nothing looked to crazy to me. I'm back on liquid but was just curious.

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] decimalman:
Strange. I'll look into it. I won't be able to do any actual bug fixing for a few days, but I'll have plenty of time to flash stuff and test.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
No worries its running good on liquid.. But it is weird. Could be the ROM.. I deleted cron and all that from sys/bin and initd and left it in and i flashed another kernel and that was fine with illusion no abnormal drain or anything except reboots so I just flashed liquid and running dkp again all is well.

infected sgh-t999

---------- Post added at 07:03 PM ---------- Previous post was at 06:14 PM ----------

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] neim81094:
Keeping my eye on this Kernel :D
[T-Mobile, Samsung Galaxy SIII] popimp315:
This is a beast of a kernel on Illusion. Thank you
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Beastly on every ROM

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
I'm seeing both cores stuck at 384 when it dips down at rest. Hot plugging isn't working on the 3.4 aosp kernel edit

Its seems hot plugging does work but I'm catching serious flickering black bad flickering while device is at idle..only does it when one core ****s down. Voltage doesnt fix

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] decimalman:
Bizarre. I had my phone plugged in while testing, and it never happened. I unplugged just a minute ago and it started flickering, and stopped as soon as I plugged back in. I'll see what I can do about it.
[T-Mobile, Samsung Galaxy SIII] atlharp:
+1 on the flickering. I was in Trickster mod about to change settings when it flickered into a RR. I am running the 4.2 AOSP kernel. I loaded the kernel with a cache and dalvik wipe. Thanks again!
[T-Mobile, Samsung Galaxy SIII] jdidtht:
He's fixing it up for everyone as we speak..

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
Nice updates especially for 4.3

Is both 4.2 and 4.3 flickering

diseased Galaxy
[T-Mobile, Samsung Galaxy SIII] decimalman:
I'm curious myself. There's not a lot of 4.3 ROMs for d2spr yet, so I haven't personally tested yet.

That said, new 4.2 builds are coming as soon as they're done building. Overclocking won't cause reboots, and the flickering seems to be gone. I had to got back to Linux 3.4.53 and disable an optimization, but it's better than nothing.

Edit: The flicker isn't happening on 4.3.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New 4.3 test builds! I merged in the latest CM commits, which seems to fix the screen barfage on newer ROMs.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Lolol screen barfage

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] decimalman:
It's the best description I could think of. :laugh:
[T-Mobile, Samsung Galaxy SIII] twoxa:
4.3 still flickering.

performance issues... installing true skate and having lags all over it. it's super smooth on stock kernel.
[T-Mobile, Samsung Galaxy SIII] ckisgen:
no flicker here. latest 4.3 test kernel running first official CM10.2 Nightly (last night).

full wipe.

no lag for me, either.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Yeah I too had flickering and I had one random reboot on the first nightly by CM. It was a fast kernel though. Back to stock for the time being.
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] mt3g:
Flashed the newest 4.3 over the official cm nightly released last night and I don't see flickers or any hiccups yet. I'll report any oddities here in this post.

Edit:

Battery went from 100 to 92% in 30 minutes this morning with no unusual wakelocks or anything so gonna play more today later and see if I can pin point the issue.
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] decimalman:
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?
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Sammy releases under GPL so open source away. I personally wouldn't worry about it one bit. There is no way ms will do ****

Obviously zero legal background just a dude that likes to type. Good work BTW.. Appreciate

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
Thanks for the updates. I usually depending on the rom switch back and forth between this and my diseased kernel. You do awesome work my friend.

diseased Galaxy
[T-Mobile, Samsung Galaxy SIII] J-ROCK:
Your TW kernel has been amazing on my phone! Keep up the good work!
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I've no legal background but I think as far as GPL goes, if you don't break any licenses in place, post changes and release source, you should be good to go.

Github has recently created a page dedicated to helping users choose their type of licensing (it also contains a lot of helpful information in regards to how each license is claimed, what it covers, etc.).

http://choosealicense.com/
[T-Mobile, Samsung Galaxy SIII] djtheraven:
Is there any way you could add to oc gpu? On tw
[T-Mobile, Samsung Galaxy SIII] decimalman:
For the time being, no. From what I've seen, there's very little performance to be gained without a few other modifications, and I haven't gotten in touch with the wunderdev who knows what those modifications are. Social phobia... :(

As far as GPL is concerned, I'm sure I'm in the clear. I'm more concerned about Microsoft's patents. Everything I've read suggests that patents shouldn't be an issue, but I haven't seen anyone with a legal background weigh in.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
You are back, any surprises?:thumbup:
[T-Mobile, Samsung Galaxy SIII] decimalman:
Nothing at the moment. I haven't been terribly motivated lately. :( I have a few ideas I want to play with, but they're still in their early stages.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
What I meant was since the driver is released under GPL (and remains under GPL), I don't see why the patents would be a concern. Besides, I would think this driver in particular would fall more under Samsung's OSRC, rather than Microsoft's patents.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
I couldn't see ms coming after individual devs ya know. That isn't happening. And if ya catch a cease an desist than well cease. Lol

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New, fixed builds 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.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New 4.2 stable builds are going up now. After this, I don't plan to continue 4.2 work, since CM isn't updating the 4.2 kernel. Compatibility shouldn't be an issue since there aren't likely to be any further kernel updates from CM, and I don't expect to make any earth-shattering changes in the near future.

Changelog since last stable build:

Fix OC frequencies not sticking.

Fix UV interface for a few apps.

Fixes for automatic auto-hotplug.

A handful of optimizations.

Lots of CM commits.

Merge nanolunch back into freelunch.

Fancy new compiler.

The flicker in recent test builds should be gone. If not, let me know.