yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
Tried the latest. Still can't reduce the minimum frequency without having to reboot the phone. Using performance control, if that helps. Seems to be smoother. Will run it today to see how the battery life is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Will hold on until the missing apps issue is sorted out..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Everything works fine for me. I've had no problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Disabling SELinux is a temporary fix for apps disappearing. It's just not the ideal solution and I'm not happy about it.

The permanent fix is to apply security contexts to apps that don't have one, and there turns you to be a really easy way to do that. Next build will do it automatically when flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
UKSM isn't a wakelock issue anymore. This build seems to handle system animations more fluidly. "Phone wakes up with crust around its eyes".... I remember reading that somewhere in the bms thread, I think it belongs here too :) Enabling a 32 bit color depth rather than the stock 24 bit really adds the punch into color when it comes to amoled screens....

I laughed when I was looking for the debug and saw

/sys/kernel/dkp/dont_touch_my_****

Made my day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Decimal I miss your work bro. Would love to see ya build a 4.4 kernel with Freelunch.

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Nice. I'll have to change the defaults for the other builds then.

dont_touch_my... enables some logging that was handy for tracking down troublesome apps that changed settings. It seemed like an appropriate name. ;)

I'll have to grab an unofficial CM11 build then. TW 4.3 has been keeping me busy, but it shouldn't take much work to get 4.4 up and running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I can get you a nice new untouched CM11 ramdisk if you help me get some overclocking action in my kernel ;)

Can't wait to see what you got in store for 4.4 man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
dkp doesn't include a ramdisk, so that won't be a problem. I just want to make sure it boots before I release anything.

As for OC, I'll put together some patches. My to-do list keeps getting longer, so it might take a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Well here's a ramdisk I spilt from a build of a CM11 boot.img

http://www44.zippyshare.com/v/7259150/file.html

Amazingly enough I split the image on my phone ;) Oh well, if I'm doing it wrong I'm sorry... I had my fun messing around with boot.img's before haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Not too shabby, but I'll do you one better. :D Open up a dkp zip and look inside the "rd" directory. Every time you flash dkp, "repack" rips the ramdisk out of the existing kernel, builds a new boot.img with it, and installs it. In 9 KB. :cowboy:

EDIT: Forgot what I was talking about for a bit.

Oh, while I'm here:

Builds are coming along nicely. If all goes well, expect builds to pop up a few minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's here!

New test build for AOSP 4.4 is going up. Feature-wise, it should be identical to AOSP 4.3, though I did throw in a couple tweaks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Up and running with Pwns latest build!

Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
That's the beauty of compatibility ;)

Anyone have the rgb values for trinity colors? I'm too lazy to look up old source code from git... And Google hates me today. I know I know.... Since cm implemented gamma control (screen color temperature... not really full control over gamma/contrast) into their source code it's kind of obsolete just having a single screen rgb value change... But I'm old fashioned and too impatient for trickster mod to change my screen post boot.

Now if Samsung could release their sources for the kernel.... it would make my life easier. And a proper Linux distro on an actual computer..... my phone gets too hot running a Linux vm. Sad face.... I beat the crap out of my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Im on CM 10 nightly build 12.2.13 this will work? or is it as titled for TW roms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
CM's "color temperature" is a lie; it's just the trinity colors offsets multiplied by different amounts. Trinity isn't actually an RGB adjustment, it's a modification to the magic numbers that calculate screen voltage. You can enable it with "echo 4 >/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors". I think. It might be 0 instead of 4.

Sprint MK3 sources are out. It's what I'm building with. I don't know what you're planning, but it sounds dangerous. :D

It's only for TW.

I haven't been updating AOSP as much as I should lately. I've been working on rewriting a lot of code, but I won't be able to release small updates. I'm hoping the wait for the (eventual) major update will be worth it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Oh I have some plans... ;) Hmmm.. I'm trying to create something as close to stock as possible. But with just a few personal changes. 32 bit color depth set as default, trinity colors (unchangeable, because I'm old fashioned), security changes and commits, not really tweakable in that sense. I was just getting tired of seeing my boot animation look like crap.

It's pretty boring if you ask me, but I haven't seen any developers make a stock Samsung kernel with just a few changes to the screen. Really :/ I honestly prefer touchwiz over aosp when dealing with Samsung hardware. I like my camera, stability and reliable non-choppy Bluetooth.

Edit:

Besides all that, are you considering adding in the Westwood tcp protocol into the next build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
You'll be surprised how hard it is to stop making modifications once you start. "Close-to-stock" kernels never stay that way for long. :)

Westwood is an easy addition. I almost enabled it and a few others a while back. I don't remember why I didn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Maybe it's a a sign... the latest touchwiz kernel I'm getting 5 hours, plus a little more of screen on time... asswax and row all the way.

I don't normally enable motions on touchwiz... But I felt like an idiot today showing off to an iPhone dude to realize some motions don't work... I'm thinking it's kernel related, but I could just have my head up my ass.

But I digress... I can't make up my own mind sometimes trying out newer firmware and never stuck with a perfectly good build... Even if it was bleeding edge, two hours later a new commit would be uploaded to git and my curiosity kills the cat... haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Some motions are broken in dkp. Apparently, I slightly broke the low-level driver that communicates with the motion sensors. It should be fixed in the next build. Hopefully the iPhone user was still duly impressed. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
That's all your fault! How do you sleep at night?.... jk He was still impressed though ;) Once you get a phone with an amoled digitizer, the relationship with lcd isn't there anymore.... Then there's knox :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Pfft. I sleep like a baby knowing that the change that broke it also decreased touchscreen latency something like 50%. :p

I don't think I've ever seen an LCD that looked better than "okay." The only thing the screen on the S3 needs is an overhauled panel driver that supports full color controls. I'd love to write one, but I don't really know enough to do it.

EDIT: I really shouldn't be able to sleep at night. The bug is caused by a spectacularly dumb mistake on my part.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Which commit broke it? I was trying to read your github but....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
LOL it'll take a while to find it if you're using GitHub's web interface. It's caused by this obviously incorrect change. Somehow, I didn't notice which loop the break was inside of. :o

EDIT: I guess the change that broke it isn't the same one that massively reduced touchscreen latency, but it's related anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's time for another TW 4.3 test build. There aren't many dramatic changes, but I did fix a few bugs. Probably the biggest change is a fix for the disappearing apps phenomenon, which means that it's safe to turn SELinux back on.

Changelog:

Fixed the disappearing apps bug

Enabled SELinux again

Added several TCP congestion control algorithms

Fixed a silly mistake that broke several motions

Cleaned some code up, removed a few useless drivers

Compiled with a shiny new toolchain
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
This build it's flawless. Really, I'm impressed. But for now, I'm disabling mpdecision and using your freelunch governor because performance is outstanding.... and I think your auto-hotplugging governor is better than qualcomm's.

When I tried reading your github, I almost had a brain aneurysm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's a mess! But everyone's is so no worries. All 4.4 builds working fine over here. I'm jealous of your hotplugging decimal :p

You running 4.4 as a DD yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
No not yet.. 4.3 touchwiz all the way. I'm enjoying all the good features of my phone now. Now I can sit back, relax, and just enjoy the firmware instead of messing around with it....

I'm honestly trying to stay away from that version of android because every released is getting more difficult to obtain root.

And another thing.... Github should be a black website... my eyeballs can't stand their heaven like backgrounds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's better than bitbucket! And I can't stand Touchwiz, I hate the icons and the lack of a decent UI in my opinion. I can deal with issues up to a certain point. Not like I'm a CEO or anything :p How does it feel to be non-flashaholic again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I can actually sleep at night :P I've actually grown to like the touchwiz icons and user interface... It was kind of like a love-hate relationship at first. Nothing too serious apktool can't fix if I don't like an icon ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's a new TW 4.3 test build up. It fixes a bug that could potentially crash the display hardware, probably taking everything else with it (thanks, Samsung).

Changelog:

Turned compiler warnings back on (Samsung disabled them :mad:), and fixed the zillions of issues that the compiler warnings were designed to highlight in the first place

Fixed a major bug in the framebuffer driver

Major cleanups to the rotator driver (the name is misleading; it's mostly used for video playback)

Renamed a few devices to hint at what devices they're compatible with

Tidied up a bit, removed a couple unused modules, switched to (smaller, faster) XZ compression
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Could you please upload it to a mirror? Something is wrong with dev host right now.

Edit:

NEVERMIND
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I did anyway. Dev-Host has been flaky lately.

http://www.mediafire.com/?7t4fnm94vurfz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Yes it has. Every second page I surf is "oops, there was an error". Other than that... this update is quite different. I just don't understand why Samsung took out display options from the settings on the gs3.... The international version has it though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I found some bread crumbs leading to frandom... correct me if I'm wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Good news for anyone running AOSP 4.4: new test builds are going up. I haven't spent much time with the code yet, so there isn't a lot of new stuff. Mostly, I got sidetracked and wrote a new novelty. :D If you hate it, you can disable it in /sys/kernel/dkp.

Changelog:

Synced up with CM

Rolled up a handful of changes from TW

Added a fancy gimmick
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Frandom?....

Performance is unmatched with other kernels I've tried.

Have you considered providing a tweaked touchwiz ram disk with your kernels?... My phone would be in heaven lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I briefly described the stuff I did with frandom (erandom actually) in the OP. frandom, erandom and urandom all point to the same code, which is a customized version of erandom.

I've had customized Sprint ramdisks available for a while now, and I do builds that include them for a few Sprint ROM devs. Unfortunately, I'm pretty sure that 4.3 ramdisks aren't completely compatible between carriers (feel free to prove me wrong, though!). The SELinux policies appear to be tailored to each carrier. I don't really want to maintain a ramdisk for each carrier if that's the case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
As long as I'm playing with the LEDs instead of doing anything productive (like putting together those OC patches pwncakes193 asked about), there's a new AOSP 4.4 test build on the way.

The new softkey backlight settings can be changed in /sys/kernel/dkp for now. Eventually, I'll try to get Trickster to show settings for them.

Changelog:

Animated the on/off transition on the softkey backlights. It's glorious. :D

Added customizable brightness for the softkey backlights

Changed how a few things come out of standby

Fixed a few small issues in the graphics drivers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
Last 2 kernels have caused a green screen when playing videos. I have to pull the battery or force a restart to get rid of the green screen. Would love to use this kernel again but this issue force me away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osker83:
I'll try it out :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
AOSP 4.4, I'm guessing? When was your ROM built? If it was built before 12/13, it might be missing some updates from CM. This early in the 4.4 development cycle, major changes that break compatibility are going to be pretty common.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
I'm running BAM 2.0 dated 12/13. I also run Quantum kernel. Running Quantum 12/15 currently without issue. No issues with it. I prefer your kernel for all the extra features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Was it just specific apps doing it, or was it any video? If you don't mind being a guinea pig, I'll revert a few things and send you a build later today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
It seems like just the Viggle app doing it. Don't have the issue with any other apps. Tried Vine and Youtube to test other apps. I don't get it. I will to test whatever you need tested. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New TW 4.3 test builds are on their way! I fixed most of the problems I've been hearing about. Dead Trigger 2 still doesn't work, so there's probably still a couple bugs left in the video drivers.

Changelog:

Added a fancy blacklist that prevents thermald and mpdecision from modifying your min/max frequency when they shouldn't.

Fixed up some CPU power management stuff. mpdecision should stop whining and do its job.

Added fancy animations for the notification LED and softkey backlights.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
I love the animations for the notification LED and softkey backlights. Thanks a lot! Any way to make the notification LED brighter? On my phone it is a little too dark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
TW likes to dim it. I brightened it up a little to make the animations look better, but I could definitely keep the LED at full brightness instead.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New TW 4.3 and AOSP 4.4 test builds are up! Bugfixes all around.

TW changelog:

Softkey backlight settings actually work

Fixed a silly bug in the rotator driver

AOSP changelog:

Cleaned up the softkey animation code and fixed a small glitch

Cleaned up the notification LED animations

Fixed a silly bug in the rotator driver

EDIT: Forgot to brighten the notification LED on TW. I'll take care of it for the next build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Just thought id throw in my findings on thr latest tw4.3 build. Everything works but the phone has become VERY laggy from unlocking the lock screen to even typing this msg. I am underclocking and undervolting not sure if it would make this much of a difference but it wasn't happening like this on 12/9 nor can I recall it happening on previous 12/17 build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Four new test builds are going up (AOSP 4.3 & 4.4, TW 4.1 & 4.3). Clearly, I've lost my mind. :p The new builds should fix the sleep of death bug and the strange softkey behavior. The notification LED and softkey backlights are a bit wonky on TW, but they shouldn't be severely broken. If there's still any major bugs, let me know.

Changelogs:

AOSP 4.4:

Synced up with CM

Fixed a few bugs in the suspend/resume code

Adjusted the softkey animation a little bit

AOSP 4.3:

Added notification LED and softkey backlight animation

Reduced UKSM's default aggressiveness

Optimized and stripped a few drivers

New toolchain, cleaned up compiler optimizations

TW 4.3:

Fixed a few bugs in the suspend/resume code

By request, brightened the notification LED (makes the animation smoother too!)

Adjusted the softkey animation a little bit

TW 4.1:

Added notification LED and softkey backlight animation

Fixed up the frequency control interface and fixed a bunch of bugs

Enabled a few extra TCP congestion control algorithms

Reduced UKSM's default aggressiveness

Optimized and stripped a few drivers

Patched in and switched to XZ compression

Removed a ton of bogus stuff

Fixed a zillion compiler warnings and a few obvious bugs

New toolchain, cleaned up compiler optimizations
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Thanks for brightened the notification LED.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxoooo:
Will it work on i747M? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Yup im running latest 4.3 tw no problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Tried latest 4.4 on gummy rom and it reboots if you try to benchmark using antutu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Try benchmarking again, wait until reboots and grab the last kmsg. Post it here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's working for me on (slightly outdated) CM11. I haven't flashed Gummy recently, but it's been pretty stable in my experience.

My guess is that your processor doesn't like the relaxed voltage limits in dkp. The vmin zip in the OP should help. If it doesn't, send me a last_kmsg and I'll look into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Getting random reboots alot all of a sudden on the latest build any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Emailed you last kmsg. Only thing I could make out was some kind e of error on cpu1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The kernel automatically reboots when it detects a L1 cache error. Even if I disabled that, it's unlikely that your phone would keep running after such an error.

Did you flash the vmin zip before that log? Are you overclocking or undervolting? You shouldn't see errors like that if you're running with stock voltages (which is what the vmin zip does) and stock frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxoooo:
T y :)

Battery life is better? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
I am running mp decision off with the free lunch kernel. I have not adjusted the gpu kernel or the colors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New test builds are up for all four active versions. I haven't made any dramatic changes, but the softkey backlights should behave much better now. If they're still acting funny, let me know.

Changelog:

Fixed the softkey backlights again

By request, enabled TCP YeAH
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Will try it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Thanks, I'm noticing better network performance with YeAH. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I've also noticed that after flashing the kernel it destroys the battery stats in settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
What ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Any touchwiz Rom as far as I know.

[MENTION=4932679]decimalman[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I think it's caused the workaround that keeps SELinux from exploding. The workaround shouldn't be needed anymore, so I'll remove it in the next build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Could you remove UKSM as well? It still remains a problem for me, still turning itself back on.

Happy new year :)

Edit:

Fixed the uksm problem I had. I left an old script in my init.d folder that kept enabling it when ram was low. Silly me.

I'm going very far when I say this though, ever since I've flashed your kernel and used it with my set up, performance to battery ratio is jaw dropping when paired with a zero lemon battery and using your freelunch governor. You should be crowned one of the kings of the kernel devs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
What's your set up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Private message me to prevent non-related talk to development
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
Looking forward to using this kernel. Are your stock voltages already UV?

-J
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
So it's official, I'm moving from 4.3 touchwiz to 4.4.2 SlimKat now. I'm only missing one thing.... sad face. Hopefully there's an update to your aosp kernel. I'll try to grab some last_kmsg's for you because I'm getting a few random reboots here and there.

Edit:

Excuse me for my complaining. ART is still buggy. Kernel works perfectly fine on dalvik mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
Hi decimalman,

I am having bluetooth connectivity issues with DKP 12/26 and stock kernel from CM11(d2att) Nightlies. I have tried BMS 12/30 and dont have any problems. I am connecting with a BMW interface which, in the past, has required some old compatibility code to remain.

Basically it either doesn't connect, or connects then disconnects, and requires bluetooth to be shutoff then restarted. Let me know if I can help provide additional information for you. I love dkp/freelunch, but love my BT connection better.

thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Good bye XDA for several days/weeks

I am not going to flash anything new for quite some time. Been running Pwncakes 12/30 build with 12/26 DKP kernel with some tweaks since that day. Not even single FC/crash since then. Running absolutely smooth/fast. On top of all, Here are screen shots of my battery usage.

Simply Awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
I don't think there's a discussion thread for this kernel so I'll post here. What are some governor tweaks you guys are making with freelunch for optimizing battery?