yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] 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

I think all the changes I mentioned were back in 2013 or so. I've made a few small changes to the wifi driver since then, but nothing terribly interesting.

If dkp is more stable than stock CM, I mustn't be trying hard enough to break things. If you'd like, I can send you a build from my development branch. It'll crash every 24 hours like clockwork. :laugh:

I decided to make westwood the default in this build. Last time I checked, it was working the best for me, though I don't remember how I determined that. That's one of the perks of being a developer--I can make my personal settings the default. ;)
[Verizon Samsung Galaxy S III] AyUaxe:
@decimalman is the greatest!

[MENTION=4932679]decimalman[/MENTION], you are definitely the greatest kernel dev! I can't imagine being able to tolerate this phone without your kernel, but with it, she flies!

Max cpu o/c at 1782, min. 54, dkvmin 800, then lately tried a global offset -20, still stable and responsive, temps @ 31*C. She'll run pretty stable a couple of mhz steps higher, but something happens that prevents apps from updating from play--guessing some form of data corruption must occur that prevents the updates from downloading properly. But at 1782, no problems of any kind. Would it help, do you think, if I rolled back voltage a little more for those high speeds or should I bump voltage up at the ghz speeds?

BTW, updated kernel is especially welcome, b/c the D2 is about to become my DD again, due to my son's cratering his MotoG--so he's getting my XT1254. As great as the D2 is working now on 13.1 with your kernel, I'm almost happy to get rid of the big ole XT1254.
[Verizon Samsung Galaxy S III] decimalman:
The default voltages for OC frequencies are very conservative and known to be unstable, so your best bet is to manually raise the frequencies for the steps above 1782 MHz. The upper frequencies are very hungry for voltage, so you'll probably need to raise the voltages progressively more at each step. dkp won't allow more than 1400 mV, and I'd recommend keeping the voltages below 1300 mV for daily usage. Still, that should be enough for a couple more steps.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks very much for clarifications re: oc voltages. [MENTION=2194886]183[/MENTION]6, 1215mv she's stable and updates from play which she would never do at this clock speed and any lower voltage. More to come!
[Verizon Samsung Galaxy S III] YabbyYou:
[MENTION=4932679]decimalman[/MENTION] I second AyUaxe's statement, your work is greatly appreciated by the d2vzw community! I will give this updated kernel a try in the next few days on my daily driving d2vzw!
[Verizon Samsung Galaxy S III] AyUaxe:
Now max'd @ 1944 MHz , 1280 MV, stable and crazy fast for all routine tasks. Play updates a little janky, but the last 5mV bump seems to have fixed that, too. Temps in low 30s while streaming audio, browsing. Will try more demanding video and report. BTW, I'm on cm13.1, 7/10 build. Tried 7/28 and 8/3, but got random reboots and neverboot syndrome. In hindsight, 7/10-11 were snapshot quality builds. Glad I had back ups.
[Verizon Samsung Galaxy S III] YabbyYou:
As always, your phone seems to be so stable at those higher MHz. I flashed the latest build onto my d2vzw yesterday. I am running at 1620Mhz, no voltage bump. Phone was stable last night but this morning while listening to music it rebooted. It felt hot, so maybe that caused it to reboot. Which CPU gov are you running?
[Verizon Samsung Galaxy S III] AyUaxe:
I've tried freelunch and tierservative. Latter seems best. Also use deadline i/o, w 640 or 1048 read ahead.

Though the phone semed stable at 1944, after several hours, having multiple opera browser tabs and viper audio open caused crashes/reboots. YuBrowser wouldn't load any page beyond home. While instantaneous app launches and pic loads are cool, I'm back down to 1782, where it's reasonably fast, cool, and rock solid. Battery life is, of course also better.
[Verizon Samsung Galaxy S III] 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

freelunch hasn't aged well. I should probably just remove it, but I think there a few masochists still using it. :eek:
[Verizon Samsung Galaxy S III] AyUaxe:
It's worth it just to be able to say, "oh yes there is freelunch!" Tierservative is awesome, though.
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=4932679]decimalman[/MENTION], just so I understand because I don't see anything explaining it in the OP. What's the difference between the zips that have 3.4_X.X?
[Verizon Samsung Galaxy S III] decimalman:
The "dkp-3.4_X.X" at the end of some builds is the source branch they were built from. My build script automatically adds it to all builds since it's helpful information for me. Normal release builds are always built from one of the "dkp-3.4_X.X" branches, so I usually just remove it when I upload. All the "dkp-3.4_X.X" means is that I forgot to rename the file. ;)
[Verizon Samsung Galaxy S III] AyUaxe:
Flashed to cm13.x 8/14 build with 8/1 dkp and she's smooth and fast. I've rolled back max CPU to old reliable 1782, 1175mV (stock tiers from 800 min, I think). Lil d2 that could blazed at 1890 after some voltage bumps, but downloads, including play store upgrades/installs almost always got corrupted. I wonder if I'm hitting a hard bus limitation at speeds >1782? Downloads are on WiFi, as I did not reactivate 4g service after all. Tried Westwood algorithm, but Illinois is still clear subjective winner for me. I presume YMMV depending on your network. Im on the most archaic cox network, though local hardware is good Docsis3 stuff.
[Verizon Samsung Galaxy S III] dvschnk:
Just out of curiosity, what is your CPU freq/voltage list?
[Verizon Samsung Galaxy S III] decimalman:
A new build is up for 6.0 ROMs. Nothing major has changed, but recent ROMs require one of the commits from CM.

Changelog:

Synced with CM

Checksums:

df5b1f2a43514b4fc6a0c7d7675e47fd dkp-aosp60-d2-20160820-dkp-3.4_6.0.zip
[Verizon Samsung Galaxy S III] AyUaxe:
Voltage chart

Sorry, busy times at work. See bottom and to frequencies in attached screen shots. The middle seems to fill in automatically, based on vmin (800 in my case) and any global offset (-10). Frequencies above 1728 are boosted on trial and error basis. Most of the time I keep 1782 as max, bc i get pretty fast performance wo corrupt downloads. Hope this helps.
[Verizon Samsung Galaxy S III] dvschnk:
Thanks AyUaxe. I'll give these a try. I tried to mess with the voltages randomly, but my phone was not having it. I hadn't messed with the CPU voltages and freq since I was on 4.3.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey [MENTION=3316305]dvschnk[/MENTION] , just be aware, [MENTION=3056030]AyUaxe[/MENTION] has a frankenstein CPU in his d2vzw. His phone stays stable at some ridiculous CPU freq's and voltages. I am always super jealous when he posts the freq he's running at. I can not get my d2vzw to stay stable anywhere near the levels he reaches. Give it a try though, hopefully you can reach those levels too!
[Verizon Samsung Galaxy S III] dvschnk:
Yeah, I forgot about that until I read your post. I tried AyUaxe's settings...no dice. The best I can go is 384-1620Mhz, global -10mV with tierservative. And that gets a little unstable sometimes too. I'm sticking to stock freq. and voltages for now. I use kernel adiutor as my kernel controller, and i've been messing with some of the other settings for now like I/O scheduler, KSM, and LMK...been running pretty well.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Anyone had success with this mixed with CM13? Does it improve performance over their kernel?
[Verizon Samsung Galaxy S III] AyUaxe:
Yes! Yes!
[Verizon Samsung Galaxy S III] AyUaxe:
8/20 build works fine with [MENTION=2385005]invisiblek[/MENTION]'s unofficial cm14 build!
[Verizon Samsung Galaxy S III] decimalman:
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.

Let me know how the new build works. I haven't seen a Sprint CM14 ROM yet, but I'll have to give it a shot next time I feel like building a ROM.
[Verizon Samsung Galaxy S III] J-Lindo:
I'd actually been meaning to comment that the 8/20 build definitely wasn't working well with my phone, particularly as it shut off any connection to Verizon (the little signal icon showed an empty triangle, without so much as the carrier name under it in the pulldown menu). But I am happy to report your 10/13 build is running splendidly on my phone (I'm on CM build 10/12). Your updated work is much appreciated :D :good:
[Verizon Samsung Galaxy S III] 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
[Verizon Samsung Galaxy S III] GeTex:
So i am trying your Kernels out with much sucess except i appear to have lost USB support... I haven't tried an OTG yet but my laptop nolonger see's the phone and the phone nolonger see's it's connected

is this a result of turning on USB fast charge?

EDIT: Yup, fastcharge
[Verizon Samsung Galaxy S III] 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
[Verizon Samsung Galaxy S III] 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
[Verizon Samsung Galaxy S III] borxnx:
I'm amazed that there is continued support for this device. [MENTION=4932679]decimalman[/MENTION], you are the MAN!
[Verizon Samsung Galaxy S III] GideonX:
Good deal, I'll check it out later tonight. :thumbup:

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] masri1987:
This
[Verizon Samsung Galaxy S III] trvbone:
First page under downloads Lol

Crap they disappeared
[Verizon Samsung Galaxy S III] masri1987:
Couple requests. Can you add a 192 or lower MHz slot? And can you also add the fifo scheduler? If not that's fine.
[Verizon Samsung Galaxy S III] decimalman:
Initially the builds weren't marked public, but they should be visible. Dev-Host has been slow and unreliable all day. :( I had to upload the first set of builds four times, and even then not all of the zips showed up.

There's still a bug or two in AssWax, but I'm working on getting it working perfectly.

d2vzw build / mediafire mirror

d2usc build / mediafire mirror
[Verizon Samsung Galaxy S III] dablitzkrieg:
The build broke the WiFi on my Verizon s3. Running latest nightly from rootbox

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] decimalman:
There's a user on AT&T who's having the same problem. I suspect it's recovery-related, since I changed how I packaged up the kernel. What recovery are you using? Version? My guess is that the kernel modules (including wifi driver) didn't install correctly.

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.
[Verizon Samsung Galaxy S III] masri1987:
Also deep sleep isn't happening.

I'm experiencing flickering a lot, switched from kt kernel where there was no flicker
[Verizon Samsung Galaxy S III] dablitzkrieg:
Newest cwm
[Verizon Samsung Galaxy S III] decimalman:
fifo: sure. 192: no. From a few pages back:

I've yet to run into any problems with either. Can you PM me a logcat and/or dmesg from the time either issue is occurring? Otherwise I can't effectively track down the issue.

That's two for CWM and none for TWRP. I'll go back to packaging the way I used to until I can sort CWM out. New fixed builds will be up shortly.
[Verizon Samsung Galaxy S III] clothednblack:
Flashed latest usc all good here

Thanks for the continued support

Edit:WiFi would not turn on
[Verizon Samsung Galaxy S III] GideonX:
To make 192 work correctly, you need to change the value for pll8 in clock-8960.c. It's set to 384 by default, so all the sub 384 slots you see using pll8 are not done correctly. They're still running at 384 with the wrong label.

Ps: didn't mean to poke my head in here, I got auto subscribed from my earlier reply. I'll shut up now :)

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] clothednblack:
Does a kernel have any WiFi control? Flashed today's and WiFi wouldn't toggle, flashed back to previous and it worked. Strange!
[Verizon Samsung Galaxy S III] decimalman:
Did you get the most recent builds (about an hour and a half old)? I repackaged them so the wifi module should get extracted correctly. If you did, I'll try to track down the issue tomorrow. It's past my bedtime. :silly:
[Verizon Samsung Galaxy S III] nicklovell23:
I flashed the latest build for d2usc WiFi is good...
[Verizon Samsung Galaxy S III] masri1987:
i'm gonna retry to see if getting on today's nightly fixes the issues i've had. i'll report back.
[Verizon Samsung Galaxy S III] masri1987:
Reporting back, not sure why but the 384 MHz slot was active a lot overnight. On new 4/24 liquid build.

The better battery stats is since unplugged
[Verizon Samsung Galaxy S III] clothednblack:
WiFi issue fixed, I flashed 4/24 test, stable was the one that worked
[Verizon Samsung Galaxy S III] decimalman:
I haven't touched any of the pm/wakelock code, so there shouldn't be anything interfering with deep sleep except ordinary wakelocks. Any idea what deleted_wake_locks was? Based on the duration and the counts, I'm guessing it was wlan_rx_wake but was deleted when you turned off wifi. The crummy dhd wifi driver abuses wakelocks and tends to cause all sorts of deep sleep issues.

Unfortunately, I don't have any easy fixes for why your phone didn't sleep well last night. :(

I guess I'll stick with packaging the kernel the way I used to then. It seems to work for everyone. :good:
[Verizon Samsung Galaxy S III] mickskillz:
adding govs

any chance of adding the new smartassH3 governor? I love this kernel, great work. Thanks
[Verizon Samsung Galaxy S III] decimalman:
Possibly. Last time I looked, it was causing problems on KT747, even with some 3.4 fixes borrowed from asswax. I'll look into it.

Edit: I just looked, and the source for smartassH3 is effectively identical to asswax, but with "asswax" changed to "smartass." Use asswax instead. It should be working perfectly (hotplugging included) in the test builds I silently uploaded last night.
[Verizon Samsung Galaxy S III] trvbone:
What's new in 4/29 the last 4/24 build is running awesome!
[Verizon Samsung Galaxy S III] decimalman:
I didn't do anything worth announcing or I would have announced it. I added the fifo scheduler that somebody requested, and I fixed up some mpdecision-related code so asswax should always hotplug correctly.
[Verizon Samsung Galaxy S III] trvbone:
Thanks carry on with your brilliant work!
[Verizon Samsung Galaxy S III] srs731:
Damn dude great job. 12 hours @ 50% with 1.5 hr screen on. Kernel is so smooth and great with battery. Thank you. Beer coming soon. Best kernel my phone has had on 3.4 based ROMs
[Verizon Samsung Galaxy S III] 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.
[Verizon Samsung Galaxy S III] 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.
[Verizon Samsung Galaxy S III] Rinkle McBally:
Can someone point me in the direction for kernel link for baked ROM 8 vzw
[Verizon Samsung Galaxy S III] decimalman:
IIRC, BB8 hasn't been updated with a 3.4 kernel, so here's the latest 3.0 test build for d2vzw: boink
[Verizon Samsung Galaxy S III] Rinkle McBally:
Thank you good man
[Verizon Samsung Galaxy S III] EnemasRfun:
Testing out this kernel on Liquidsmooth's 2.3 official, can anyone recommend a governor/scheduler combo for the holy grail (unrivaled performance & battery life for months)? ....or maybe just a good combination of the two
[Verizon Samsung Galaxy S III] borxnx:
I really like the nanolunch governor. It will get **** done but also calms down well. Good for games and also pretty easy on the battery when not in use. I'm using the row scheduler, but they're all good (depending on how you use your phone!)
[Verizon Samsung Galaxy S III] mickskillz:
is there a stable version coming or should I go with the test version from 5-3. I tried all other kernels and my phone lines this one the best. thx

Sexy gS3
[Verizon Samsung Galaxy S III] decimalman:
There aren't any recent stable builds. I'd recommend the newest test build, since IIRC it fixes a bug or two that I didn't catch in the stable build.
[Verizon Samsung Galaxy S III] dragontology:
Thanks for supporting the d2usc.

I'm here because Jellybam has flickering, and their people said a different kernel would fix that. Everyone on Google+ says ktoonsez's is the best. So I look that up on Team US Cellular, and the dev who ported that for us, and some others, said the dkp kernel is the best. I have an Anker 4400mAh, so I'm not too interested in saving battery, though I won't turn it down. Also don't really need overclocking. But if this kernel's more stable than the one that comes with Bam ( regular CM kernel, 3.4.41), I'll happily swap it out. Thanks again.
[Verizon Samsung Galaxy S III] mickskillz:
Love the kernel! Are you planning on merging in all the new commits that were recently pushed? It's been quiet in here lately. I hope you didn't jump ship to the sgs4

Sexy gS3
[Verizon Samsung Galaxy S III] 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: I haven't jumped ship. I'm on an MVNO, so I'd be paying basically full retail for the S4. Given my current finances, I don't think it's worth it to upgrade.
[Verizon Samsung Galaxy S III] mickskillz:
Take your time. Hope all is well, and can't wait for the new builds. Thanks for all the time you donate.

Sexy gS3
[Verizon Samsung Galaxy S III] mickskillz:
FYI.... New test build running smooth so far. It seems a little slower then previous versions. Using nanolunch/row setup.

Sexy gS3
[Verizon Samsung Galaxy S III] EnemasRfun:
flashed ktoonsez while waiting for the new stable for dkp and it seems battery life and performance both went downhill..... needless to say i am anxiously awaiting the new stable release
[Verizon Samsung Galaxy S III] decimalman:
Any day now. I've been playing with TW recently, but I have a new stable 3.4 build in the works as well. There's a few things I need to double check next time I flash AOSP before I'm ready to call everything stable.
[Verizon Samsung Galaxy S III] aypeeootrek:
Touch wiz? I like the sound of that