yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] wetbiker7:
Mokee is solid ROM. I ran it for a few days w/o any issues.

I decided to flash back to Liquidsmooth and see if I could get the DKP kernel dialed in. I'm stoked! It looks like I've found the right combination of settings. These results are with the 7K mAh ZeroLemon extended battery. Not bad huh? :D
[Sprint Samsung Galaxy S III] Awesome Donkey:
Working fine in AICP running 5.1.1.
[Sprint Samsung Galaxy S III] decimalman:
dkp has fallen pretty far behind CM, so it's time for a new build. Unfortunately, I still haven't tracked down the battery drain issue that's been affecting some people. :( Since nothing has changed for 4.4, I'm only doing a 5.1 build.

Changelog:

Synced with CM: lots of cleanups, fixes and optimizations.

AFAIK, there's not an elegant way. I'm not aware of any apps that support mDNIe settings. You can play with the settings in /sys/devices/virtual/mdnie/mdnie, but they'll reset as soon as you turn off the screen. That's probably fixable, if you're interested.
[Sprint Samsung Galaxy S III] The_Anomalist:
The new 5.1 build will install but it don't show it still stays it the may 8 build? And I had one more question do u support the note 2 I see there is not a "good" kernel for 5.1 for it and I was wondering if u could possibly build one? I will make a donation if u could and I only ask cuz your kernels are amongst the best out there:):D
[Sprint Samsung Galaxy S III] wetbiker7:
I'm showing the new kernel in my settings. The kernel is running great too.
[Sprint Samsung Galaxy S III] The~Skater~187:
That's it, I'm digging out my s3, updating it to lollipop and test driving this sexy kernel. Lol.

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] wetbiker7:
LOL! Get-r-done bro! The new kernel is running like a champ and we have some new ROMs too.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] The~Skater~187:
I will :D Just got to get it back from my brother. He's been using it till he got his New phone two days ago. I just haven't had the time to go get it. I wish we had dkp on my S5 and n7

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] techdog:
[MENTION=4932679]decimalman[/MENTION]. I just noticed on one of the KT747 threads that someone suggested a 20% undervolt of the LCD (in our case it would be the OLED). Seems the developers on their previous phone, a Galaxy S WiFi, had done that and it had a huge impact on battery usage.

Any thoughts on 1) whether that would be possible on our phone or 2) whether that would be of interest?

Just throwing it out there.....

Thanks.
[Sprint Samsung Galaxy S III] decimalman:
I can't do a kernel for the N2, sorry.

Even though the N2 has a lot in common with the S3, it's a very different device under the hood. The N2 uses an Exynos SoC instead of a Snapdragon, so it uses a very different kernel. Most of my changes in dkp won't apply easily to the N2 kernel, if they apply at all. On top of that, not having an actual N2 to work with would make it very hard to do any actual development for it.

You buy me an S5 or N7 and we'll talk. :laugh:

I got a similar question in my AT&T thread. I responded here. I'm going to try tweaking the voltage regulators, but I'm not optimistic about the results.
[Sprint Samsung Galaxy S III] The~Skater~187:
I will see what I can do. :D

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] I Brick Phones:
Just tried out this on my S3 running the latest Cyanogenmod 12.1 nightly. Overclocked to 1.782 and set the governer to freelunch.

I have to say battery life is greatly improved and with the ability to overclock the overall responsiveness has improved as well.

I'll keep testing it out, but looks great so far! thanks
[Sprint Samsung Galaxy S III] wetbiker7:
I'm running Freelunch too and getting the same results. Definitely a great gov.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] wetbiker7:
Here we go
[Sprint Samsung Galaxy S III] The_Anomalist:
Darn that sucks lol. What version of s5 cuz the one I'm getting is not the note but the sprint s5 I just said note 2 cuz its kinda cheap and it packs a "better" processor.
[Sprint Samsung Galaxy S III] decimalman:
New builds are up. I was playing with the toolchain I use for dkp, and discovered a handful of interesting optimization possibilities. Everything seems stable, but it's possible that some new issues will pop up with the new optimizations.

Changelog:

Synced 5.1 with CM

Updated to BFQ v7r8

Reworked some hotplug infrastructure in preparation for a project I'm planning

Overhauled auto-hotplug: it's now more efficient and much more aggressive

Enabled -ftoplevel-reorder, allowing LTO to do a better job optimizing

Specialized some LTO behavior to further improve optimization

Added a few smaller optimizations: inlined spinlocks, improved optimization for CPU hotplug, etc.

Normally, I'd just describe optimizations as "...and I optimized some stuff," but I'm pretty excited about the new optimizations in this build. The benchmarks I usually use to evaluate changes are all showing 5-10% improvements, and battery life over the past 24 hours has been noticeably better. Not too bad, considering how little I actually changed. :D
[Sprint Samsung Galaxy S III] SuperGoober:
Nice , what rom is that hooked up with ?
[Sprint Samsung Galaxy S III] The~Skater~187:
Here ya go, lol

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] wetbiker7:
Thanks. That was with OctOS.

Hey...... That's cheating! This is the S3 section buddy. LMAO

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] The~Skater~187:
Sorry, had to. I bet if I could figure out how to port decimalmans kernel tweaks to my s5 kernel, it would even beat this score.

I miss this kernel.:(

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] The~Skater~187:
What is dkp getting in antutu on lollipop?

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] wetbiker7:
I wish we had it for my Asus tablet. I get good scores on it but like you, I know it would be able to post a BLAZING score.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] The~Skater~187:
I'm going to see what I can do about brining dkp, to the 2012 n7

Sent from my kltespr using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] wetbiker7:
I know you're section would greatly appreciate it if you were able to do so. Best of luck my friend.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] techdog:
Using it with SlimKat 9 and everything is working great. Battery is better. Performance is better. Bluetooth battery usage is also better.

Thanks for all of your hard work.
[Sprint Samsung Galaxy S III] Issam00:
Hey guys how are you ?

Can I use this [KERNEL][AOSP4.4/5.1] dkp - d2spr - for my android 4.3 GT-I9300 ??!!
[Sprint Samsung Galaxy S III] madbat99:
This is for sprint sph-L710. And it clearly says 4.4/5.1 aosp, so you asked if it works on a different model S3 running touchwiz 4.3? Short answer, no. Wrong forum.
[Sprint Samsung Galaxy S III] decimalman:
Don't do it!

The i9300 is very different from the US S3s that this is intended for. Kernels aren't compatible between them.
[Sprint Samsung Galaxy S III] Issam00:
Thank you
[Sprint Samsung Galaxy S III] XxTeXx07xX:
Anyone else getting a battery percent of like 194828% is what my battery says after i flash this kernel. Tried a few times. And its the correct file for this Triband model. Any ideas???
[Sprint Samsung Galaxy S III] monsterpenguin5:
I've been playing around with this lately. The first couple days I use it seem pretty good, but then it seems to have heat issues. Even if i turn down the max speed, it seems unstable. Not sure what I could get for you. Some kind of logcat or something? Does it matter if the ROM running is from a date after this was made? Does the ROM date need to be the same as this one? Or can we use more current ones? I've tried both AICP and Exodus with it and both seemed okay at first and then hot and unstable.
[Sprint Samsung Galaxy S III] maheboi:
Does anyone have this working with aicp?
[Sprint Samsung Galaxy S III] zhiwlin:
Yes all good
[Sprint Samsung Galaxy S III] madbat99:
Yep. Works great.
[Sprint Samsung Galaxy S III] ksmullins88:
Keep coming back to this kernel... most responsive and the best battery with nano lunch and sio.

Just wanted to show some love!
[Sprint Samsung Galaxy S III] CyberGmonster:
Same here. On the latest CM. Under clocked/volted on nano/row with zero issues. Its either this or the forbidden for me ATM.
[Sprint Samsung Galaxy S III] nikolkang:
Any new test builds on the way? :D.

I jumped ship temporarily because the latest CM/CAF kernel commits fixed screen flickering for me on task AOKP.

Miss your kernel already...
[Sprint Samsung Galaxy S III] das_webos_transformer:
Those issues have been gone for me too, the way his kernel works it uses a portion of the already included kernel, so really, flashing this shouldn't bring back those issues. Im on PAC from 5/13 right now, need to fix my boot loader before I can update, thanks CyanogenMod...
[Sprint Samsung Galaxy S III] decimalman:
Your wish is my command. :p

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: as das_webos_transformer mentioned, dkp reuses your existing ramdisk. Reusing the ramdisk is nice for me since it means I don't have to stay up-to-date with CM, but it means that other kernel's boot splashes and ramdisk tweaks will carry over to dkp.
[Sprint Samsung Galaxy S III] nikolkang:
I can understand that... I know this is not your full time and really appreciate the great work you have put together here!

Good to know about the ramdisk I had no idea. :D
[Sprint Samsung Galaxy S III] CyberGmonster:
Just tried BMS and guess what I'm back to?;)

So how does nano active differ from nano lunch?

Finding the perfect shoe for CyanogenMod!
[Sprint Samsung Galaxy S III] das_webos_transformer:
I think nano active is the more precise nano version of interactive.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Since you can't add pictures through the app :I
[Sprint Samsung Galaxy S III] decimalman:
Yep. It's currently broken (sticks at max freq), but I keep forgetting to disable it. It was just a test for the nanosecond stats anyway.

That's not good. Dev-host has been pretty flaky lately. If you're still having trouble, let me know and I'll mirror to mediafire.

I hear good things about BMS, but I've never actually flashed it. Glad to have you back. :)
[Sprint Samsung Galaxy S III] das_webos_transformer:
Dev host loaded right up about a minute and a half later, I noticed nano active was weird ha. Thought "hm what's this do?" And it a little min max action when I toggled the screen(I was in system tuner). Oh well ha
[Sprint Samsung Galaxy S III] ilive12:
So what's the difference between freelunch and nanolunch, and which one gives better battery life?

Also, which I/O scheduler should I use for best battery, SIO or ROW?

Thanks!
[Sprint Samsung Galaxy S III] decimalman:
nanolunch uses more precise (but less accurate) statistics. I don't know if there's a major difference in battery life between them. nanolunch was mostly something I thought was interesting enough to release. :)

I don't like ROW, so I'll point you towards SIO. For some reason, ROW has never impressed me.
[Sprint Samsung Galaxy S III] grifforama:
Is it just me, or is screen flicker something we are having to put up with on 3.4 kernels?

I get it on all non stock kernels using liquid or carbon

---------- Post added at 01:11 PM ---------- Previous post was at 01:11 PM ----------

And it's way more likely to happen with the pop up notifications that overlay the screen?
[Sprint Samsung Galaxy S III] jfcooley:
Disable overlay in system/dev options.

Haven't had it though on newest carbon nightlies with newest test.
[Sprint Samsung Galaxy S III] nikolkang:
I had screen flicker on the action overflow menus and toast messages but that is all gone in the latest test. Using tasks AOKP.

My fiances s3 never had the screen flicker so it all depends on your hardware.

Like mentioned before.. If all else fails disable the overlays. There are some build.prop tweaks you can apply to keep it persistent through reboots.
[Sprint Samsung Galaxy S III] kris54241:
Stock battery , using lux too
[Sprint Samsung Galaxy S III] das_webos_transformer:
Oh really?

I've been using nano lunch, I can't really tell the difference. Might be nothing. I like the idea, this kernel is awesome. I've had OK luck with row. I used noop yesterday cus my battery was gonnne, you can tell the difference. I've never been a fan if it. But it helps battery.

[MENTION=4932679]decimalman[/MENTION] have you ever heard of lion heart? That's the given or I use in my tab, drop the freq down too and its still fast and gets good battery life, I'm not sure of the exact tweaks made to the specific kernel, the guy who made it was a real Linux but and knew a bunch if tricks and stuff I still don't understand.
[Sprint Samsung Galaxy S III] mikedavis120:
Installed most current and it boots to splash1 and then blackness.....

thats all so far going on like 5 mins, five more and i give up.

Is this normal?
[Sprint Samsung Galaxy S III] CyberGmonster:
Nope! I only use this kernel with all aosp ROM's!:)

Finding the perfect shoe for CyanogenMod!
[Sprint Samsung Galaxy S III] monsterpenguin5:
What build date for aicp?
[Sprint Samsung Galaxy S III] maheboi:
07-07-2015
[Sprint Samsung Galaxy S III] madbat99:
7/7 here too. But there is an update this morning.
[Sprint Samsung Galaxy S III] maheboi:
Is front camera suppose to work yet? Does it work on your aicp?
[Sprint Samsung Galaxy S III] madbat99:
Nope. Some have had luck with third party cameras. I never use front camera. Hangouts video chat works fine.
[Sprint Samsung Galaxy S III] akaTRAP:
This kernel + CM12 7/19 Nightly = amazing battery life so far.
[Sprint Samsung Galaxy S III] monsterpenguin5:
Thanks for the info. I think my phone is failing at a hardware level. It's getting very hot during the boot up and basic things like texting or web browsing are generating notable heat. Good news for this kernel though, since it shouldn't be the cause.

Anyone notice any better success with particular governors? just going with default settings? other stuff?
[Sprint Samsung Galaxy S III] madbat99:
Freelunch governer. That's the only change I made. Great battery life.
[Sprint Samsung Galaxy S III] akaTRAP:
Still on 7/19 CM12.1 Nightly. 93% battery, 1 day 20 hours left on the battery. I have achieved the holy grail of battery life for my S3 lol
[Sprint Samsung Galaxy S III] techdog:
I love the Freelunch governor. I have tried other governors with this kernel and gotten good performance and battery life - I have even tried the tierservative governor. However, I always come back to freelunch as the BEST governor, at least for this kernel, for both performance and battery.
[Sprint Samsung Galaxy S III] ZipAddict:
check your cpu usage in info tab in kernel tweak app. sounds like high cpu usage because of governor or system process. if you see core 2 using more than core 1 and the second one {EDIT} is never {EDIT} going to 0% sometimes then it might be system process. trickstermod info tab tells me this. i use trickstermod because the developer recommended this and adiutor. i dont like adiutor because it has too many options which is normally a good thing but im afraid the Lspeed mod i use or other things i tweak in buildprop or scripts will toggle some of those advanced settings and not save because it will revert back on boot because of app saving previous settings on boot. but i could be wrong about this but i used it before and had trouble. trickstermod is a lil more basic and the only settings i want saved on boot are my frequencies and governors basically.

this is how i have it set up on trickstermod although this may not be best for everyone. its based on my usage and the fact that i want this phone to last forever...

everything i dont mention i left the same except i flashed min voltage zip after renaming to 800 because lowest frequency for me runs at 800

i/o control - 2048 and fiops

cpu freq. - min=162000 and max=1620000 and freelunch governor

gpu freq. - 533

battery runs cooler and longer than ever before.

hope this gives you a couple ideas to fix your overheating.
[Sprint Samsung Galaxy S III] decimalman:
So dkp is embarrassingly out of date, and I haven't dealt with any bug reports in the last month and a half. Oops. :( I haven't been working on dkp as much lately, and when I do, I'm hung up on improving the optimizations from the last build. I haven't gotten very far with that, so I'm putting it on hold to get a new build out. Not a lot has changed on my end, but there's new builds up on Mediafire.

Changelog:

Synced 5.1 with CM. The new screen color controls are supported, and there's been plenty of other updates as well.

Switched to a shiny new toolchain based on GCC 5.2. Performance seems similar, but it's making much smaller kernels.

Added an option to disable standalone power collapse. See below.

Added new builds that disable dkp's optimized spinlocks. See below.

Changed some build settings to take advantage of GCC 5, improve optimization, and make dkp easier to build.

Probably some other stuff, but it's been ages since the last build and I don't remember.

The standalone power collapse and spinlock stuff is to help track down a few issues. If you aren't getting random freezes/reboots with the previous dkp builds, you don't need to worry about this stuff; just flash the regular (not "revert-spinlock") builds as usual.

If you've been seeing random freezes (possibly with a black screen and/or tons of lag right before), try flashing one of the revert-spinlock builds. Whether or not it helps, please let me know.

If you've been seeing random reboots, try disabling standalone power collapse. I'm not sure it's the actual issue, but it's worth a try. To disable SPC, either open /sys/kernel/dkp/spc_enabled and change the "1" to "0", or open a terminal app and enter "su", followed by "echo 0 >/sys/kernel/dkp/spc_enabled". If it helps, let me know and I'll figure out an easier way to disable it.

Finally, there have been several bug reports involving the battery/charger stuff. I don't see any differences between dkp and CM that would cause it, but I'm going to take a closer look when I get a chance. If I find anything, I'll send out some test builds.
[Sprint Samsung Galaxy S III] ZipAddict:
[MENTION=4932679]decimalman[/MENTION] im down to help! Sounds awesome I cant wait for next build! Thanks for your hard work and im glad there is someone smart building this kernel! That changelog is quite advanced stuff!
[Sprint Samsung Galaxy S III] Travisholt92:
Thank you for continuing to build amazing kernels. I personally haven't used it since 4.4.4 first came out (that was the last time I owned an s3).

However 2 years later you're still puttin out the goods. I installed it onto a friend's phone today to show him what his phone can really do. We were both very satisfied with the results.

Also, what toolchain are you using for building? A good friend of mine was building using SaberMod toolchain with o3 optimizations and a lot of other optimizations while keeping coding at a minimum, on standby with his kernel I was getting 0-1% battery drain in 8 hours while sleeping with data turned off.

I'm just wondering what optimizations you use. I'm going to be building myself a ROM/kernel for this device and my moto G LTE.
[Sprint Samsung Galaxy S III] decimalman:
I build my own toolchain specifically for dkp. It's mostly based on vanilla GCC and Linux binutils, with a few changes to support kernel LTO and generate better machine code. SaberMod, Linaro, etc. don't currently have any changes that I want for dkp, so I don't use their source.

Compiler optimizations (-O3, -fwhatever, etc.) are easy to add, but they're pretty limited. They'll usually create machine code that runs somewhat faster (and probably uses marginally less battery because of that), but still does what the source code says to do. If the source code does things in an inefficient way, the machine code will too, even with -O3. In the best case, -O3 might improve performance by 30%, but it's usually much less. All that said, the compiler flags I use for dkp are here if you're curious.

If you can program, it's a lot more interesting to improve the source code itself. Fixing inefficient code will have a much bigger effect than anything the compiler can do.
[Sprint Samsung Galaxy S III] techdog:
Downloaded and installed it over the weekend.

Running great for me on Slimkat 9.

Thanks for all of your work.
[Sprint Samsung Galaxy S III] ZipAddict:
[MENTION=4932679]decimalman[/MENTION] im testing several things this week including new kernel so it might be weekend before i can go through everything and give my input on kernel and other things. Thanks for ur hard work on this. My question is are there any disadvantages of the revert spinlock patched version vs reg? Could u explain a lil more? I believe spinlock is take a number and wait so this spinlock revert is not. Could u tell me what affects on perfoance,multitasking,battery these have versus eachother? Thanks bud sorry if this is confusing question the way i wrote it
[Sprint Samsung Galaxy S III] decimalman:
Spinlocks are used to queue things up so tasks don't fight over who's using certain data. They're the kernel's lowest-level, stupidest way of doing that. Because they're flexible and lightweight, they're used a lot throughout the kernel.

dkp's optimized spinlocks are (almost) exactly the same as the kernel's regular spinlocks, except they're considerably faster. Benchmarks that hit the spinlock code particularly hard show significantly higher performance with the optimized spinlocks, but I don't think that carries over to everyday usage. Even though they're used a lot, spinlocks don't use enough CPU to make a visible difference to performance or battery life.

Unless you're getting random freezes, the regular build (i.e. the one with optimized spinlocks) might be marginally better, but it doesn't actually matter. Use whichever one you want.
[Sprint Samsung Galaxy S III] 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.
[Sprint Samsung Galaxy S III] ZipAddict:
[MENTION=4932679]decimalman[/MENTION] have u gotten any feedback on revert spinlock edition yet? Or any of the other suggestions u made for black screen or battery issue? I can try it on wifes phone and see differences between our logs to help?
[Sprint Samsung Galaxy S III] decimalman:
I've gotten a little bit of feedback--one person said the revert-spinlock build fixed the freezes they were seeing, but I haven't gotten any conclusive feedback on disabling SPC. Logs won't show anything related to either, it's just a matter of whether or not the changes fix things for the people that were having issues.

At this point, I don't think there is a battery issue. Until someone shows up with logs showing different charging behavior between the CM kernel and dkp, I'm going to assume that the issue is just aging batteries and/or low-quality aftermarket batteries. AFAICT, dkp's battery and charger code is functionally identical to CM's (aside from fast charge), and none of it has changed in the last year. Any recent change in behavior isn't coming from the kernel.