yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] decimalman:
Choices are always good. I just pushed the fix, so help yourself to the source. :good:

New fixed stable builds are up!

Issues fixed:

If the ROM doesn't start mpdecision correctly, interaction and asswax will leave core 2 online forever. dkp will now start mpdecision if needed.

mpdecision is fussy and I hate it. I think I managed to get it to stop whining.

Trinity colors now defaults to on. I'll get a zip up shortly to disable it.

AssWax causes reboots. Fixed.
[T-Mobile, Samsung Galaxy SIII] nicksmizzle:
sweet!
[T-Mobile, Samsung Galaxy SIII] cLogic:
thanks for the concise answers ... as a programmer this tells Me a lot :D :good:

I will download and try the kernel tonight .. since I am now back on My laptop and that mediafire doesnt work from phone

regarding your A2 ... "tweaking is half the fun of a custom kernel" ... first thing that came to mind was, "yeah, its half the fun of a thermonuclear device also" lol

I know all about governors and voltages and such, but the closest I've ever come to "tweaking" a kernel was modifying the make file just before building a new zImage ,, lol

so ... regarding the lollipop "heat" issue ... that has to be handled by undervolting and/or reducing extended use of high MHz frequencies, right?

fyi ... I've noticed that simply charging the phone heats the battery area a bit ... but if I use the device to play a game WHILE its charging, the battery area ALSO gets hotter ... not just the cpu area

not sure if this helps at all .. but I thought it was important since it is kind of odd cuz altho the charging should continue longer due to use of the device, it almost seems as if the charging is pulling more mAH or working harder

.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Nardholio says he broke dkp again, so new builds are going up. :laugh: If you're using a LP nightly from 7/26 or earlier, you should stick with the previous build.

Changelog:

Synced 5.1 with CM. There's a new thermal throttle.

Fixed the new thermal throttle, and added an awesome new bug in the process: as long as the thermal throttle is active, you can "overclock" as far as you want. :p

Optimized some stuff.

I should really pay more attention to LP. I wasn't even aware that there was a heat issue. Anything you can do to reduce CPU power use will keep the phone cooler, so undervolting, underclocking, and/or a less aggressive governor should help.

Phones don't dissipate heat very well, and between charging the battery and running the CPU/GPU hard, they can generate quite a bit of heat. Weird that it doesn't affect charge time, though.
[T-Mobile, Samsung Galaxy SIII] cLogic:
I guess I wasn't clear .. I'll elaborate ..

I was reporting the heat issue cuz it is a lollipop thing and I thought that you should know

personally, I don't care if the phone bursts into flames, as long as I get cpu/gpu performance when I want it, lol

battery charging duration IS affected, of course, if playing while charging

I was reporting that battery area (mid-bottom) gets even hotter when playing while charging .. as if it is pulling higher mAh .. which shouldn't actually be possible

thanks for your work and latest update

back to laptop to download from this mediafire crap, lol
[T-Mobile, Samsung Galaxy SIII] mc00:
A charger with 2.0amp and higher will help keeping up with demand. is surprising how many people don't know that. I use s3 as a AP and boy it will get hot suck up power.
[T-Mobile, Samsung Galaxy SIII] jaysix79:
I'm trying this kernel on my T-Mobile s3 with att ROM (cyanide 18). Anyone know a reason why I'm getting signature error code.
[T-Mobile, Samsung Galaxy SIII] anil2653:
I am using this kernel on most of lollipop roms and never had any issues

Try redownloading
[T-Mobile, Samsung Galaxy SIII] jaysix79:
Thanks man tried re downloading now it works
[T-Mobile, Samsung Galaxy SIII] sylikc:
Brightness is lower than 0608 build

Hi, I flashed the latest 7/29 build and I've noticed that the max brightness is significantly lower than the 6/8 build that I was running previously.

I'm on FlexOS 5.1.1.

So, begrudgingly I went back to the 6/8 build (I do a wipe cache/dalvik each time) and the brightness is back to max (it's visible in daylight).

Did something change between the builds with regard to brightness?
[T-Mobile, Samsung Galaxy SIII] sylikc:
Freezes with screen blacking out but touchlights stay on

While I'm at it, in the 6/8 build, I had an occasional problem (really only when Ingress was in the foreground) where a lockup would happen

Screen blacks out, touchlights stay on solid. 10s power button to power off was the only way to recover.

Wondering if anyone else has seen this happen. I used to be using tierservative, now using intellidemand hoping it would be better (simpler governer). I'm not overclocking. I found it happens less if I disable KSM (but that's just anecdotal evidence, because the lockups are random).

That's why I'm eager to get the 7/29 build working, ... but the screen backlight thing makes the phone unusable during the day.

Thanks for your hard work on dkp. feels like the only viable kernel left on the S3
[T-Mobile, Samsung Galaxy SIII] leolawliet:
Ever since I've last updated my kernel with this one, I've had nothing but horrific lag and the same problems you described, all nonstop. I haven't been able to use my phone as an alarm, haven't been able to place calls, or let alone do anything without my device crashing.

Edit: I rolled back to the 0608 update and everything works fine.
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's new builds on both MediaFire and a new mirror, solidfiles. Hopefully solidfiles will be less awful than MediaFire. :fingers-crossed:

I don't know how often I'll be able to update dkp in the future. I've been having trouble finding the time to keep up with development and support lately, and that won't change anytime soon. If anyone wants to fork dkp and keep it updated yourself, please do. If you need help getting set up, I'll try to help.

Anyway, new builds! Changelog:

Synced 5.1 with CM. I have no idea what changes I picked up. There are just too many.

Updated tierservative. I removed a ton of logic and fixed a lot of misbehavior, particularly during moderate usage.

Fixed a tiny bug.

CM has been working on some new color control stuff that might be affecting it. My CM12.1 backup is still running the 7/29 nightly, so I have no idea if there's a setting somewhere to fix it or what.

As for the freezes, use the revert-spinlock build instead. This is a known issue that I haven't figured out yet.

Also, on GitHub, you mentioned that intellidemand was simpler than tierservative, which isn't the case. Based on lines of code, it's actually the most complex governor in dkp.
[T-Mobile, Samsung Galaxy SIII] sylikc:
Well, it was worth a shot. I finally got around to testing this build. It exhibits the same dimness behavior as the previous one. No other CM-based build with kernels exhibit the behavior, so I'm not sure what it could be.

Anyways, have to stick with 6/8 build then for the brightness. I can't really test the freezing thing without being able to see the screen during the day ;)

Good luck on your future projects!

I'll keep that in mind. I'll swap back to tierservative back on 6/8 build
[T-Mobile, Samsung Galaxy SIII] xdamember143:
Hey guys I don't know if its this kernel but after I install this my s3 it starts lagging alot ?
[T-Mobile, Samsung Galaxy SIII] decimalman:
New builds are on their way up. I haven't changed much, but there's been some changes from CM for all versions.

Changelog:

Synced with CM.

Tweaked the tierservative defaults to (hopefully) fix stuttering music playback.

Made a tiny change related to the spinlock issue. Hopefully, it'll finally fix the issue. :fingers-crossed:

Merged in CM's MM branch. :)

I haven't tested the MM build at all, so it may or may not work. I haven't seen any major changes that would cause problems, but I haven't been watching very closely.

Checksums:

8b186c3f3f432d333422ba476d3c1f0b dkp-aosp60-d2-20151227-dkp-3.4_6.0.zip

5e4a55863cf15049ca987c7f6552b4a2 dkp-aosp51-d2-20151227-dkp-3.4_5.1.zip

5b6aa43374101aabd9556d6aad17f8d6 dkp-aosp44-d2-20151227-dkp-3.4_4.4.zip

39dc9217321fcd0d75b61233ab43ca3f dkp-aosp44-legacy-d2-20151227-dkp-3.4_4.4.zip
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's a new build for 6.0 up. I didn't do updates for 5.1 or 4.4, but I can if there's still interest.

Changelog:

Synced with CM, Linux 3.4.112

Updated to GCC 6 and fixed a zillion new warnings (a few of which were obvious bugs)

Removed the profile switch script and bundled mpdecision: the profile switch script doesn't work on MM anymore, and mpdecision is already included in ROMs

Fixed (for the 173rd time :crying:) falling back to auto-hotplug if mpdecision is disabled; tweaked auto-hotplug defaults

Switched UKSM to a deferrable timer, which might make it a bit easier on battery

Tweaked GPU frequency sampling

Fixed a few minor issues that interfere with deep sleep

I have a few more changes in the works as well. Hopefully, it won't be another 8 months before the next build.

Checksums:

0855f52701abbd1909b62c0663ccac19 dkp-aosp60-d2-20160801-dkp-3.4_6.0.zip
[T-Mobile, Samsung Galaxy SIII] decimalman:
Due to popular request, I'll continue to release builds for 5.1 and 4.4. New builds are up for them. The changelogs are basically the same for these builds as for the 8/1 build.

dfae019aea16db3eeac0ad28c82e9891 dkp-aosp51-d2-20160805-dkp-3.4_5.1.zip
2c002573e01190efee89525f5234013d dkp-aosp44-d2-20160805-dkp-3.4_4.4.zip
84f45bbbf2b80d8c836b60951340964f dkp-aosp44-legacy-d2-20160805-dkp-3.4_4.4.zip
[T-Mobile, Samsung Galaxy SIII] stephenseiber:
tried it with latest CM build, CM had more issues then usual but cm's battery drain is too much trying with Oct-M right now and will try with PAC-ROM when i can download it. only want to overclock to smooth out the OS... stock was fluidity but samsungs touchwiz is nauseating as well as 16gb isnt enough storage. with Marshmallow sd and internal are for all intense and purpose one giving me 42gb but sadly there is only 3 roms and OC kernel i have found.
[T-Mobile, Samsung Galaxy SIII] stephenseiber:
so far it seems far more stable with oct-m... have my processor set at 1.836 and gpu set at 530. there is still an occasional hang or reboot... and unlike CM it actually charged while tethering to my PC... still more testing needed but it appears to have a more normal battery drainage compared to CM... which is funny cause oct-m is based on CM.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I didn't realize there were any TMo users left, so I stopped posting updates to this thread. I guess I'll have to start again.

Looks like newer ROMs won't work with the current dkp builds, so it's time for new builds. I haven't changed anything, just synced with CM. Since nothing changed on 5.1 or 4.4, I didn't rebuild them.

Changelog:

Synced with CM.

Built for AOSP 7.0. I haven't actually tested it or anything, but not much has changed in the kernel between 6.0 and 7.0, so I don't expect any problems.

Checksums:

c0cfd71dde752c20d0b7e48e748b76a8 dkp-aosp60-d2-20161013-dkp-3.4_6.0.zip

712abb7f194c38b1c67655b9c99c30ac dkp-aosp70-d2-20161013-dkp-3.4_7.0.zip

Out of curiosity: at the request of a user, I threw together an option to limit the screen's framerate, but I haven't merged it yet. Is anyone interested in this? The requesting user's S3 died recently, but if anyone else is interested in such an option, I can certainly tidy up the code and merge it. The user also put together a fancy app to control the framerate; if I merge the code, I'll try to get the app released publicly.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New builds are up for AOSP 7.0, 6.0, 5.1, and 4.4. Not much has changed, but I'd strongly recommend updating. All builds incorporate a fix for a major security vulnerability ("Dirty COW").

Changelog:

Updated to Linux 3.4.113

Synced 6.0 and 7.0 with CM

Checksums:

d23ddc003ce67883c36e94ebd0f4f218 dkp-aosp70-d2-20161104-dkp-3.4_7.0.zip

f840e736de3bde47a8e4c8d6a7bffc94 dkp-aosp60-d2-20161104-dkp-3.4_6.0.zip

3b0831a5aa69639fe62f846ac5a1a514 dkp-aosp51-d2-20161104-dkp-3.4_5.1.zip

48ea09bb35e53a73fe3663ae7a082bfb dkp-aosp44-d2-20161104-dkp-3.4_4.4.zip

a06d296fe1a2e7f84f3d6af92f647eea dkp-aosp44-legacy-d2-20161104-dkp-3.4_4.4.zip
[T-Mobile, Samsung Galaxy SIII] Newman xd:
s3 error

Why my battery says-1096157884 %
[T-Mobile, Samsung Galaxy SIII] Hayo Tee:
Very stability and smothly kernel. Wil you update it for 7.1.2? Will you add support hotplugs and more governors?
[T-Mobile, Samsung Galaxy SIII] Lonelyskatter12:
[size=+2]Unofficial Update

Nougat Only

[/size]

Changelog:

* Synced with LineageOS.

* I couldn't get LTO to work. So I used optimizations from my kernel as a replacement.

* Compiled with a cortex-a15 optimized Uber 7.x toolchain.

* Beautified Dkp name in kernel lol.

* Other than that, source is completely untouched. :good:

* Thanks [MENTION=4932679]decimalman[/MENTION] for letting me post this. :highfive:

So here you go guys. Enjoy! :good:

Download Link
[T-Mobile, Samsung Galaxy SIII] decimalman:
After lots of laziness on my part, there's finally a new official build out. Thanks to [MENTION=6249123]Lonelyskatter12[/MENTION] for putting together an update in the meantime. :highfive: I was hoping to get a few more changes merged, but I ran into some stability and battery drain issues. Once I get those issues sorted out, I'll release a bigger update. In the works are improvements to the tiered GPU governor, a complete rewrite of ISAAC, additional optimizations, and a fix for cpufreq_limit.

To simplify things, I'm only building for AOSP 7.1 for now. If anyone needs a build for a previous version, let me know and I'll make it happen.

Changelog:

Synced with LineageOS; disabled cpufreq_limit because it's causing problems.

Switched to a newer compiler and fixed all the new warnings that appeared.

Changed how LTO gets set up, so it should work with an off-the-shelf toolchain. If anyone is interested in playing with the dkp source, this should make it much easier to get started.

Replaced a spinlock optimization that was causing freezes with something less dangerous.

Added a few small optimizations and bugfixes; they shouldn't have any noticeable effect.

Checksums:

71152cf98cfab160d05fb37f73bbd60b dkp-aosp71-d2-20180204-dkp-3.4_7.1.zip
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
https://xdaforums.com/galaxy-s3-att/development/lineage-15-1-build-t3793126 can any one help please????
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
is there any fix for Sudden Death problem after flashing this kernel ? and there is black rectangle on the screen when i open recent apps switcher and while taking screenshots
[T-Mobile, Samsung Galaxy SIII] nxb:
Latest 7.1.x - Error in zip (status 255) Installation Aborted when flashing :(

It only flashed when I stole the update-binary from another one of your releases.
[T-Mobile, Samsung Galaxy SIII] mika152:
Does this work with t999n ?
[T-Mobile, Samsung Galaxy SIII] ayysir:
Hmm ass wax uses mpdecision. I use auto-hotplug
[T-Mobile, Samsung Galaxy SIII] niphoet:
I don't see this release on the stable download page. Am I missing something?
[T-Mobile, Samsung Galaxy SIII] decimalman:
Should work for both. AssWax still a bit buggy, but I'm working on figuring out the issue is.

The downloads weren't marked public when I first posted, but they should be visible now.

dev-host mediafire
[T-Mobile, Samsung Galaxy SIII] doubleohseven:
Flashed this kernel and I now have an unresponsive screen, bottom lights come on when I press buttons and when holding the power button I feel a little vibrate like the phone is on and working, but the screen won't turn on. Reflashed and wiped davlik as usual. Any ideas why this is happening?

EDIT: I see it may be some video driver/CM merges that aren't incorporated in my ROM yet??
[T-Mobile, Samsung Galaxy SIII] decimalman:
Your ROM doesn't support the newest CM display driver update. If your ROM does nightly builds, try grabbing the newest one. Otherwise, give me a while to finish up working on a bug in AssWax and I'll get a build posted without the driver update.

For now, you'll want to flash back to the kernel you were running before, or re-flash your ROM (dirty flash is fine) to get your phone running again.
[T-Mobile, Samsung Galaxy SIII] doubleohseven:
Thanks for the quick reply, got it working.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Glad to hear it. :good:

There's one last round of new "stable" builds going up on dev-host now. They fix hotplug with AssWax, and allow AssWax to be set on boot without locking frequency at maximum. I think that's the last of the bugs. :fingers-crossed:

I'll mirror to mediafire in a few minutes.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Crazy test builds are going up soon! If you flash, expect bugs and be prepared to flash an old version! I only just got wifi working again (took 3 days to track down the issue :(), and I expect more issues to show up.

Changes:

Link-time optimization! I expect this to cause problems, but I think I've sorted most of the crazy bugs out already.

Fancy new toolchain with the latest Linaro and GCC commits

Linux 3.4.43 and CM's latest commits

A few odd fixes and cleanups

Edit: My build script blew up, so this round of test builds is using the old naming system. Sorry for the inconvenience.

Edit 2: Fixed my build script and rebuilt using the right toolchain. New builds are up.
[T-Mobile, Samsung Galaxy SIII] niphoet:
I've been using the new build for about 3.5 hours and no craziness so far.
[T-Mobile, Samsung Galaxy SIII] decimalman:
That's a relief. :good: I uploaded new builds basically as soon as I got wifi working. Prior to that, even data didn't seem to be working, and my phone was pretty unstable.

It was a huge pain to get LTO working. Just to get the kernel to build, I had to modify most of my build tools, plus track down all sorts of obscure bugs in undocumented code. It took another 3 days to iron out the really obvious bugs that made the kernel totally unusable. :( I really like LTO for performance-critical stuff, and I hope it's actually making a difference here. I'm sure I'm biased, but I think it's noticeably smoother.
[T-Mobile, Samsung Galaxy SIII] niphoet:
Cool, man. Just out of curiosity, what scheduler and governor do you run personally?
[T-Mobile, Samsung Galaxy SIII] decimalman:
Usually nanolunch and sio. I've been playing with zen recently, but I could take it or leave it.
[T-Mobile, Samsung Galaxy SIII] decimalman:
faux updated the sound control interface. The new update isn't actually written for d2 devices, but I merged it anyway. New builds are going up now.

The builds also include a new toy I threw together earlier this evening. I'm calling it "auto-auto-hotplug." If you have mpdecision running, it'll let mpdecision do its thing. If you disable mpdecision (or are running task's AOKP), auto-hotplug takes over. If you set Trickster to apply at boot, it should work perfectly, but if you decide to switch later you'll need to change governors before everything will get sorted out. I've only given this 5 minutes of testing, so let me know if it gives you trouble.
[T-Mobile, Samsung Galaxy SIII] scream4cheese:
Will we be able to use the new build with the latest Liquidsmooth rom?
[T-Mobile, Samsung Galaxy SIII] decimalman:
Nope. They still haven't updated since the CM commits came out. 4/17 is the latest that will work.
[T-Mobile, Samsung Galaxy SIII] doubleohseven:
Latest kernel is working with LiquidSmooth. OP isn't updated yet but 2.3 official is up, and they work perfectly together.
[T-Mobile, Samsung Galaxy SIII] Ch4m3l30n:
I'm running dkp-3.4-d2att-d2tmo-20130424 on aokp_d2tmo_nightly_2013-05-06 and it's mostly going fantastic, but I did have a kernel panic crash yesterday as a result of a stuck CPU core... last_kmsg here:

http://pastebin.com/CSqag4hG
[T-Mobile, Samsung Galaxy SIII] decimalman:
That's a high-quality bug report. :good: That last_kmsg shows a lot of bad things happening in the kernel, which isn't great for you, but is very helpful for me. Thanks! :highfive:
[T-Mobile, Samsung Galaxy SIII] Ch4m3l30n:
Just wanted to report that this has been the only crash I've had on your kernel after more than 1d9h45m of fairly hard use. It's very nice having this stability after the severe instability I was suffering on the recent AOKP nightly kernels.

Glad my 10+ years professional experience as a software test automation specialist has indoctrinated into me the importance of quality defect reporting. :cool:
[T-Mobile, Samsung Galaxy SIII] Ch4m3l30n:
It crashed again not long after I posted above. I was asleep, so it didn't affect me negatively.

New log below; Seems to be the same issue.

http://pastebin.com/9kHBakYf
[T-Mobile, Samsung Galaxy SIII] decimalman:
I haven't had much time recently to look into this. I've got nothing else happening today, so I'll try to track down what's happening. There's definitely a few lines in this new log that worry me a lot.
[T-Mobile, Samsung Galaxy SIII] Ch4m3l30n:
Cool... Here's 2 more recent logs. The last one looks like a different problem. :eek:

http://pastebin.com/AfRutKKH

http://pastebin.com/t8r4zS5N
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test builds will be going up shortly. I haven't had much time for dev work (IRL stuff :(), so not a lot has changed. There's a few bugfixes and the latest CM commits, but not much else.

Edit: in case anyone is worried, I've been discussing Ch4m3l30n's issue by PM and it shouldn't affect anyone else.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New stable 3.4 builds! It's been way too long since the last stable builds. There's not a lot of dramatic changes since I've been busy IRL and have been working on a TW port of dkp.

Changes since the last stable:

Bugfixes: better overclocking support, better hwrng support, etc.

Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface (Settings->Advanced->Screen color temperature)

Automatic auto-hotplug. If your ROM doesn't have mpdecision or you've disabled it, auto-hotplug will take over. Settings for auto-hotplug can be changed in the governor settings menu of tuner apps.

New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain

Edit: New builds pulled until I get data sorted out.
[T-Mobile, Samsung Galaxy SIII] munkyvirus:
No data here as well.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Something strange happened with the release build. It looks like one of the new optimizations is breaking communication with the modem, but I didn't catch it when I released. I'm working on tracking the issue down now.
[T-Mobile, Samsung Galaxy SIII] decimalman:
It shouldn't take much effort to fix, but it will take a while. I just need to sift through a few recent changes to track down which one is causing the problem. Unfortunately, it takes 20 minutes to rebuild to test on my device, and almost an hour to rebuild all four devices once I fix everything. :( Link-time optimization is a pain.

Edit: Fun fact: with the optimizations the new stable build uses, RAM usage while building peaks at 6 GB (750 MB per thread). Building dkp is the only time I've seen more than half my RAM in use.

Edit 2: ...and then I ate my words. :( Something else is happening here. I don't know what's going on, but it looks like this might take a while.
[T-Mobile, Samsung Galaxy SIII] bosna110:
I don't seem to find the test build 5/29 build anywhere with 3.4.47 kernel
[T-Mobile, Samsung Galaxy SIII] decimalman:
I took all the new builds down until I can get data sorted out. Last night I think I figured out what's going on, so hopefully I can get fixed builds out soon.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Let's try this again. I just fixed the issue that's causing broken data, so I'm going to upload test builds.

I'm going to bed. Hopefully I'm not just exhausted and hallucinating the 3G indicator. :p
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Its working