yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Links do work. If they don't work on your mobile, somebody posted an alternate on this page. If not, download on your computer.

[MENTION=371528]Everybody[/MENTION], what kind of battery life are you getting? I don't know if it's just me, but I'm finding that battery life is not the greatest. Any input?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Running latest PAC rom with latest (normal) dkp is showing good battery life.

Using free lunch/fiops, governor/scheduler ATM. All other settings on kernel are default.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] emilakd:
not download from the pc .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Anyone with a large aftermarket battery and charging issues;

I had them also. Seems like if I use force fast charge it works correctly.

Anyone wanna ccheck that out with me? I have a laza 4200 may battery.
[AT&T, Rogers, Bell, Telus 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.

Curious.That makes it sound like there's an internal charging setting that's not set right in dkp, but everything looks right. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
There is def something amiss. It happened on cm stock kernel (recently) and this. I have seen a post on here about the battery not charging properly.

I have had several bad experiences with aftermarket batteries, so don't rule that out at all. Not even if it happened to 16 different types of Chinese battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
For wiw, I'm on a CM based build from 8/08 & I'm still seeing charging issues on stock kernel. I can have it plugged in & it says charging but watching it, it actually goes down. This is on the latest sync too, r9 build num. LMY48I. I flashed 7/29 revert spinlock & have yet to see it happen. Keeping close tabs on it tho. [MENTION=4932679]decimalman[/MENTION], if there's any logs you need pulled or anything I can do to help just let me know man... :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Will I still be protected from stagefright bugs if I flash this kernel on the latest nightly of CM12.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
As I recall, Stagefright is an issue with the ROM, not the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Just a quick check in;

I have been using the 7/29 version of the "revert spinlock" version of this kernel.

I have used it with over a dozen cm12.1 night lies, and for the latest CyanideL.

I always give the new kernels a shot, (short, maybe an hour)

Always come back.

Thank you, [MENTION=4932679]decimalman[/MENTION].

Greatjob

Best kernel for my device.

(picky sob's)

D2att

NJ1

RENO

FIOPS

165 MHZ. (or whatever many)

2048mb readahead.

Trickstermod

Oh, and interactive.

Best battery you gunna get, that's one of those things!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thejust:
PING!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Socomfort99:
I've been using 7/29 with spinlock revert and had really good results. I've had two random reboots that I captures logs for. I'm using asswax with fiops governor and having awesome battery life. One thing I see in the log is selinux errors for mpdecision and wlan0 not sure if that matters. Let me know if you see anything.

https://drive.google.com/file/d/0B9e5wHRyaCBOOUkwblJ1dFI0V0k/view?usp=docslist_api

https://drive.google.com/file/d/0B9e5wHRyaCBOb1dwcXVBQVpXbzg/view?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
Could you update the kernel and add some extra features!

Will you add more hotplugs, faux sound, fast charge controls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeverSeparate:
It's usually considered bad forum etiquette to ask for updates and eta's. These guys don't get paid for this, unless you plan to donate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
I understand. The main thing was asking was with the features be added when it was updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
I'm sure he'll update when he see's fit. Right now there's a lot of changes on behind the scenes with d2 kernel. As for added features, its already crammed packed but ya never know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twobats1:
Do you need an update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
no ETA that's what i know, if you want to update then you update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 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.

I don't plan on adding any new hotplug stuff for a while. I've got an idea I'd like to play with, but I haven't had time for it. Faux sound is already supported, but Faux never updated it for our device, so it might not work with newer apps. Fast charge has been supported since early 2013.

Yup. I do this for fun. It's hard to look at all the bug reports (with workarounds posted two posts above :mad:) and requests and still feel like I'm having fun.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
Can one post in text or picture of you lowest voltage table! I want to know what the lowest you have gotten the voltages with full stability!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
Every time i flash the kernel the CPU governor settings never stick. Like when i change the settings they always revert back to the default settings. For example: When i change the up_threshold from the default settings it always resets to default.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
If you are using TricksterMod to set the governor or any other options, you must configure TricksterMod to re-apply the settings on boot. Otherwise it would go back to defaults of boot.

I use TricksterMod so I'm familiar with it, but I imagine the situation is common among other similar tools.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Jusus. Solidifies is really top of the line advertising bomb site.

Really kits through your ad blocking stuff. Gotta root kill to get back! Lolz!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Literally can't download this from either of these sites. Its comforting to know that media fire thinks my browser is obsolete, and thinks "internet explorer (you know, the big blue " e" that you avoid at all costs) is better and won't let me grey to the page that I can SEE being right there...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Edit: got it. I will let you know.

That was an ordeal!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
Everytime i put my settings in they still revert to default settings even if i set on boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi MaddMaxx...try use Kernel Auditor it work for me with no issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Press the controls button (top, right) then you'll see the "set on boot" options. Make sure you got the right options checked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Yup! Kernel Aduitor for the win! I've been using it since it first dropped on play. Imho it's the best hands down. Decimalman started using it as well & added commits to the app for compatibility with dkp awhile back. I have zero issues using KA ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
Ive been using Trickster Mod for years! So i know how to use it! [No disrespect] Everything i've tried to get the settings to stick using that is doesn't work! NOTE: The GS3 with this kernel and CM12.1 does not have the donation pack thing so i cant save the profile settings. Every time i change anything in the governor settings it always reverts before i can even change another thing or backing out of the CPU governor settings

Yeah! That app is awesome! I use it lightly with my LG G3 undervolted and overclocked to 2.88GHz!

The issue i'm having with that app is that i cant change anything without it reverting back to stock/default after after i either change something else or back out of the settings window.

I think its something wrong with this kernel and the stock CM12.1 kernel does the same thing! My LG G3 doesn't do any of this type of crap!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4602366]MaddMaxx636[/MENTION], Hmm? Odd, its working fine for me on d2att, d2vzw & grouper. All runnig our 10/17 OctOS weekly build. d2att stock OctOS kernel, d2vzw dkp kernel & grouper stock OctOS kernel. Not sure why you're having issues with it not sticking. Weird
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yenkoPR:
for anyone that is having problems with sidefile site that when downloaded it downloads as rar and exe file, use mediafire to fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] distorsun:
Try delay it for 10 sec after boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Thanks for that recent build, decimalman. It's running perfectly alongside my 10/25 nightly. Good performance and battery life with asswax + fiops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
[MENTION=4932679]decimalman[/MENTION] Hope all is well with you. Thought I'd ask the question that e1 is likely wondering. Do you have any plans to build dkp for MM. No e.t.a.'s needed. Just curious what projects you've been playing with lately. Thanks once again for all your contributions. Cheers!!!!

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
That would be awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
+1 :good:

it's hard to find modern substitution for S3 that has unlocked bootloader with MHL / HDMI support and will not overheat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'll probably try merging everything once I see a couple semi-stable MM ROMs. Unless something troublesome gets committed between now and then, I don't see a reason why I wouldn't support MM.

I don't really have much dkp-related stuff happening right now. I'm playing with some changes that might finally fix the spinlock thing, and evaluating a couple small changes to tierservative, but that's about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Sounds good my friend. I agree with you about waiting awhile for some stability. Thanks for the reply.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
What exactly is the spinlock issue? Was it a commit that was supposed to have performance/battery life gains but was causing restarts and stuff?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Pretty much. It's a more efficient implementation with better performance, but it's causing freezes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
One small problem I've had with all dkp builds for a while now is that if I'm in an area with little to no cellular reception for a few minutes my phone will randomly restart. It happens consistently and only when running dkp as opposed to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Weird. I have it on fairly good authority stock suffers this bug as well ;p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Ah, okay. Maybe I just notice it more when using dkp because I get a TricksterMod notification after a restart whereas I don't make any kernel setting changes to be applied at boot when I'm on stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirLaughsalot:
Throwing out a suggestion based on experience with the deathly kernel: I think Faux's intelliplug and the darkness CPU gov will be excellent additions to this kernel. Anyways, great kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Waancho:
Hi, sorry for noob quenstion, but can this kernel be flashed on top of a preexisting CM12.1 install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
If it's a d2att it can.

Sent from my Nexus 5 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reemobeens19:
i was referred here from the d2att pac rom thread and figured i would give it a go. my device is apparently one of those rare

devices that dont seem to see any of the common problems with twrp until now, or so i thought. tried to flash and twrp simply

quit and reloaded its self. tried redownloading and reboot recovery then install with the same results...started to research philz

and suddenly realized i havent tried a download from the pc.... sucess! im waiting for it to boot up at the moment and figured

i would make one request, can we get a check sum in the opening post? not trying to be funny by any means, ive read a lot of

this thread and you have gained a lot of respect from the people you develop for as well as my self. most of what i do is via

mobile connection(not by choice mind you). i like the way you handle business, thanks in advance and for the hard work bro!

i look forward to following your future projects.

--edit--

im loving playing with this, its been a long time for me... brings back memories of

building water cooled rigs in korea w my army buddies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 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

I leave my builds up indefinitely, so that would be a long list. :laugh: Instead, I'll post MD5s in the post where I announce builds. Good enough?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Nice Christmas present [MENTION=4932679]decimalman[/MENTION]. Going to test right away. Thanks mate!!!!

Sent from my Nexus 5 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Word! Best Xmas gift ever lol ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NJD316:
Booted up fine on d2att CM13 Matrix zone build with Open Gapps. Got it set on Free Lunch/Row and will test tomorrow. Deep sleep achieved right away. Thanks Decimalman, love your work!!!!

Edit - running very smooth all day with heavy use, great battery life and deep sleep. Had issue with stock camera freezing after flashing but Google Camera works perfect. Thanks again for the kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twobats1:
Running great on d2att Broken 3.9 for a couple days now. Haven't had any problems. Great job dkp. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
DKP rocking on 6.0 here, 32+hrs & solid. Thanks [MENTION=4932679]decimalman[/MENTION] for yet another killer update! MM is gonna be a blast with DKP!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Hey there, I tried flashing your kernel, but it just forces recovery to reboot. I didn't use a vmin version, I used the standard 5.1 12/27 build, however I noticed in kernel adiutor that the lowest voltage supported was 900mv. Should I reflash a vmin with that number? And also, what are the revert files needed for?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reemobeens19:
This reaction I've found out due to corrupt download, I had a download redownloaded multiple times with same results. Download with PC and verify md5 check sum... Also a copy to device can become corrupt too... It wouldn't hurt to download, copy to device then verify the check sum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Okay, that actually makes perfect sense. I left a part out, but I did attempt to use zip verification, and it did try to install, but couldn't verify the zip, so yeah. I didn't think md5 would've had anything to do with it since I didn't see md5 files, but I was assuming, and we all know what that does lol thanks for the help, I'll try that in a bit and let you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reemobeens19:
Twrp will look for md5 files and try to verify, if there are no md5 files available then you can copy and paste the md5 into an app on the phone... This is the way I tend to do it. Download your zip and put the md5 in a text file. Copy both Txt and zip. This way you can verify later in case of card corruption.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Sorry for the late response, but what app do you use for that? I'm not even sure how to phrase a Google search appropriately for that lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Awesome, I got it handled. I used the solidfiles link and the download was perfect. The other links give me empty zips, that was the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirLaughsalot:
Is it possible for a TW based 4.4 kernel to come around? There really isn't a necessity, but it would be very welcome :). Anyways, love the kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WontonNoodle:
So does this not work on d2can?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
I would nandroid and then try it if I were you. Little time consuming, but this way you won't brick your phone. To be fair though, bricking shouldn't be a worry. If it doesn't work, it'll either tell you or you'll go into a bootloop, easy fixes. But d2can and d2att are practically identical except for maybe the bootloader numbers, so it should flash and work perfectly fine. As I said though, you should make a nandroid backup beforehand.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
Im using the latest release of the kernel on the latest nightly of CM12 with a fresh flash and im getting the settings that i change in the CPU gov reset after i apply my one settings. (If i change anything in the CPU Gov controls it resets after i close it and reopen it) It still changes even if i save the changes that i made.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Try Kernel Adiutor from the playstore to manage & adjust the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaddMaxx636:
That is what i am doing. Im using both Kernel Adiutor and trickster mod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirLaughsalot:
That might be the problem. The app settings will conflict with each other if you have both running at the same time. Try uninstalling one of the apps, and make sure set on boot is disabled in the performance settings section if you have dev options enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Installing the 5.1 kernel on Oct os5.1 final crashed the camera. Anyone else have that problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
If you tried the latest version of dkp, try an older version of dkp that's closer to the date of the date of Oct-L M6 final build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Build date of the final is 12/29
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Hmm, well idk then. Strange
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] landroid2000:
Can I install this on d2att running octOS 6.0.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] viddy1355:
Yes. (Sorry Admin)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twobats1:
I've been running the 12-27 AOSP60 for several days now without any problems. Very smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
which rom are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twobats1:
I'm currently running the Octos 2-27 weekly. Previously on 2-20 weekly and others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] landroid2000:
Corrupt Zip file

Whenever I try to flash this in TWRP 3.0.0, it says, cannot flash, corrupt zip. Is anyone else having this problem? I'm running oct-OS 6.0.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twobats1:
Did you check your md5? You may just need to re-download it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] landroid2000:
How do I do that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twobats1:
Sorry, I forgot there's no md5 listed, just try downloading again or from the other mirror.

I get the following for both:

dkp60 md5: 8b186c3f3f432d333422ba476d3c1f0b

If it helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwmike:
Hi, Really appreciate the kernel.

Running it with Cyanogenmod 13.0. However have discovered two bugs in the Kernel same page merge (KSM) settings section.

1. With KSM disabled at boot the enable KSM setting remains on and active

2) any changes to the scan period are dropped leaving the scan period at 1ms

Both of these conditions flood the phone with KSM scan usage.

If the enable ksm setting is turned off after boot, the problem is stopped but any boot will cause it to restart.

I discovered this while running an interrupt trace which showed the KSM mod at very high levels.

Not sure whether this is a DKP kernel problem or a Kernel Adiutor problem

Any help/thoughts appreciated!

UPDATE: Installed Kernel Adiutor-Mod from app forum . Seems to have resolved item 1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
UKSM is turned off by default in dkp, so the first issue is coming from somewhere else. The most likely cause is a rogue app or initscript turning it on during boot. In the past, some ROMs also changed KSM settings during boot (including turning it on) without having an obvious way to change them back. I haven't played with CM13 much, so I'm not sure if it touches KSM or not.

The second issue is more puzzling. The default scan period is 100ms, so something must be changing it, but I'm not sure what would apply a period of 1ms. As you've observed, it'll cause excessive CPU usage with no real benefit and is pretty obviously not a good idea. Periods longer than 1000ms are ignored since they don't work ideally with the scan scheduler, but otherwise, there's no reason why your changes wouldn't apply.