yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] bryank29:
I read that article last night, thank you. It was very interesting.

I did use the Battery Recalibration app (root) last night by charging to 100% and beyond, than recalibrating which is supposed to delete some info from the phone about the battery. I did find I was holding a better charge last night. It dipped about 3 hours to around 92%, and I went to bed not charging it in. About 5 hours later it was at 91%. The only way I can tell how long my phone has been "on" is going to Cell Standby. Time on: 10hr 28m. I am sitting at 85% right now, so I have used 6% since waking up, but that involves Reddit app, checking instagram, and basically having the screen on doing various activities.
[Verizon Samsung Galaxy S III] bryank29:
Been running Zen for both internal and external. So far it's running pretty good.
[Verizon Samsung Galaxy S III] AyUaxe:
Purely out of curiosity, did you ever try deadline?
[Verizon 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.
[Verizon Samsung Galaxy S III] AyUaxe:
Flashed the latest regular build, everything else as before and seems like battery life improved. Thanks a ton, [MENTION=4932679]decimalman[/MENTION]!
[Verizon Samsung Galaxy S III] gadgetguy08:
Thanks for this. I have had a few freezes and reboots (2 or 3 per week so nothing too noticeable and nothing really reproducible). I disabled the SPC and things have been stable, but it has only been 14 hours and a few hours of screen time, so it is a bit early to tell.
[Verizon 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.

Keep me posted. :good:
[Verizon Samsung Galaxy S III] gadgetguy08:
I had a soft reboot yesterday and may have a log -- work and a family situation have prevented me from investigating.

I will get the latest version and load it later today. Thanks for that.
[Verizon Samsung Galaxy S III] AyUaxe:
new thermal throttle

Anyone have tips about what temp to set the thermal throttle to in the 7/29 dkp? Seems odd not to have a stock or preset thermal protection. Not seeing any problems, though.

I've had the thermal throttle threshold set at 56C for about 36 hrs and don't think it's kicked in yet. Not much heavy use though.

Almost a week and some fairly heavy navigating in nasty hot NYNY. Got a little hot, but never into 50s so far as I could tell. Mostly hovering around mid-high 30s. 54-1782 MHz, vmin-810. Updated to 8/5 nightly a couple of hours ago and saw some display hypersensitivity weirdness, but seems to be settling in now.
[Verizon Samsung Galaxy S III] griz.droidx:
Decimal you're doing great. You have a life too and I for one don't expect you to be able to stay on top of things 24/7. I'm just immensely grateful that you're still supporting this old beater of a phone.

Thanks man
[Verizon Samsung Galaxy S III] Jeremy.Stewart85:
Woot. Was on vacation for a week, nice to come back to this. Giving it a shot now with the Jul 28 revert-spinlock build on CM12.1 Aug 4. I will report back with what I see. Thanks for sticking with it!

Leave all settings at default at first for a few days

If a reboot/black screen is encountered then disable SPC

If no further reboots seen then see if undervolting and clocking are stable

Profit
[Verizon Samsung Galaxy S III] Jeremy.Stewart85:
Just a quick status update. I've been pretty rock solid since flashing the revert-spinlock on 8/4. On saturday I felt confident enough to lower voltage by 25mV across the board. Had one random freeze up that required a reboot but I'm about 99% sure it was because facebook choked on a video, no other problems to report so far. Battery life is improved vs. the stock kernel but I haven't had enough time with it to really feel the difference. If I get a chance this week I might try to install the default kernel to see if my old problems come back.

[MENTION=4932679]decimalman[/MENTION] what exactly does the revert-spinlock take out?
[Verizon Samsung Galaxy S III] decimalman:
Spinlocks are used throughout the kernel to guarantee that only one task can access a resource at once. That way, tasks don't interfere with one another.

Regular (i.e. non-"revert-spinlock") dkp builds use faster code for manipulating spinlocks. The speedup is tiny (around half a nanosecond per spinlock), but spinlocks are used a lot and that time adds up. Many kernel-oriented benchmarks show a modest improvement in performance.

Unfortunately, there seems to be a bug buried in the dkp's spinlock code, which is causing freezes for some people. I might have accidentally fixed it in the latest build, but I'm not sure yet. The "revert-spinlock" builds use the vanilla kernel's slower spinlock code, since I know it works correctly.
[Verizon Samsung Galaxy S III] MPTP:
I have experienced freezes (black screen, phone still on requiring a 10 second press of the power button to reboot) for all CM builds after 10.1.3 regardless of the kernel used. I'd assume the random (or not so random for me) freezes are not exclusive to the DKP kernel.

80% of the freezes on my device are while running navigation and 80% of those are while also charging. I'd chalk it up to an overheating issue except that it seems to strike at random, even with an ice cold device. Most of the other freezes occure while I'm actually using the phone as a phone.. The call continues as normal but the screen will remain black and the phone unresponsive.

I have been using the revert spinlock build since the 29th and clean installs of the latest CM nightlies and there has been no change in the frequency of freezes. I switched back to the regular build on Sunday and have experienced the same behavior. Also note that my device is rock solid on any CM or TW build (up to 4.3) with no crashing or freezing issues.

It could be that my device just hates 4.4+ but I refuse to go back to TW, and DKP is certainly superior to the stock CM kernel, so I'd just like to say thanks for all of your hard work!
[Verizon Samsung Galaxy S III] AyUaxe:
Trying the splc revert with 8/12. Wasn't having any significant freezes etc. Just thought id try. Does seem a bit less snappy, but stable.

Entropy-wow! Had no idea about this, did a little research, doubled the stock settings and boom, every thin is noticeably quicker after just a few minutes. Can't tell yet about battery or temp. Might raise CPU load some, but cool thing to be able to tweak. Thanks ubermuch, [MENTION=4932679]decimalman[/MENTION]

Update: went back to nonrevert version. Lag in spinlock revert build too irritating. Saw no positive diff in reliability. On cm 8/14 build and very smooth/quick. Battery life doesn't seem as good, but doubt that's kernel's fault.
[Verizon Samsung Galaxy S III] Jeremy.Stewart85:
Captain's log, day 5: Updated to CM12.1 8/17 for stagefright patches. Switched to using the non-revert dkp kernel at the same time and have not seen a deadlock since! Whatever magic you did in the last build seems to have been the silver bullet for the issues I was experiencing before. Undervolted -50mV at the top end and -25mV below 600MHz to try and avoid stalls while idling, running great!
[Verizon Samsung Galaxy S III] Fenix2002:
First up, I want to apologize if this has been covered elsewhere in this thread. I searched with no luck.

I'm working with an MVNO S3 (Straight Talk SCH-S968C) which is d2tfnvzw. Runs on Verizon towers, same hardware as d2vzw, accepts recoveries/ROMs/etc. from d2vzw. For all intents and purposes, it's a d2vzw. =P

I've used dkp 5.1 with CM12.1 on this device successfully before, with no issues. Last night I rocked my phone back to CM11 (Snapshot M3), for my own reasons. Now, when I install dkp 4.4 from TWRP, it boots, except the splash screen never goes away. I can boot dkp 3.4_4.4 successfully, but it changes my splash screen, and I don't want that.

Any explanations on why dkp4.4 won't work, why dkp3.4_4.4 does work, and how to stop it from updating my splash screen? Any help is appreciated.
[Verizon Samsung Galaxy S III] Droidriven:
As for the splash, that can be changed, its slightly more troublesome than changing boot ani I think(never personally changed splash so I don't know the steps).

Look into and see what you come up with.

Also, did you try wiping system partition before rolling back and flashing the kernel?
[Verizon Samsung Galaxy S III] griz.droidx:
Someone mentioned wake locks a while back but I hadn't seen any recommendations except greenify which is nice and the privacy manager. I noticed at work the other day my battery was dropping like a rock. I always check the wake time vs screen on time by clicking the graph in the battery stats section of settings. Mine was staying awake. Instead of using a bunch of battery apps, I just use privacy manager to prevent apps from waking especially play services. I also enable it first thing b after a data wipe and ROM install for all apps so I can tell each app what it can or can't access. Such as location. The only other thing I use is autostarts to prevent crap from starting for whatever reason. Just be careful because you can limit an apps "features" by doing this. For example I use it on titanium k9 mail and Twitter because I can check email when I want Twitter when I want and most apps don't need to start for this or that reason. Just use common sense and you'll be fine. This works and has worked for me for a long time. I'm on aicp with dkp. UV by 25 across the board and oc to 1758 I think it is. Min is around 216. My phone isn't very stable at 54 min frequency. But I'm working on that. I use tierservative and 2048 read ahead for internal and external. Different values give better or worse results depending on the file size being transferred or read. You can select a value and test the times or performance in ROM toolbox. Good luck.
[Verizon Samsung Galaxy S III] AyUaxe:
DM, still loving the 7/29 build, but just out of curiosity, is kernel dev for d2vzw done? I hope not, since you've been improving the devices function consistently, but if we've reached a practical limit, that's understandable. Thanks again for the awesome kernel! Cheers!
[Verizon Samsung Galaxy S III] SilentDude56k:
I've been loving this kernel too. If it's not too much trouble I'd love to see an update with the recent CM kernel updates included. If not, it's fine, this phone is really getting up there in age now. I'll figure out how to build it myself if that's the case.
[Verizon Samsung Galaxy S III] AyUaxe:
If you do decide to try a build, please keep us posted on results. It was community involvement that started lollipop development for d2 and kept it going until CM and [MENTION=2044079]Nardholio[/MENTION] (PBUH) picked us up. [MENTION=4932679]decimalman[/MENTION]'s responsiveness has been great--with cm and dkp my phone is as up to date and runs basic tasks as well as a stock Shamu.
[Verizon 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.

If you're at all familiar with git and C programming, it should be pretty easy to update dkp yourself. I think I fixed the last of the issues that required custom tools, so you shouldn't need much other than a Linux VM with a bunch of standard tools and a Linaro toolchain installed.
[Verizon Samsung Galaxy S III] SilentDude56k:
Thanks for the update! I'm sure I can speak for the few of us remaining and say that we really appreciate it.

I'll mess around with building this week. I have a Linux VM for dev work already, so I should be able to hit the ground running. If I end up doing builds it'll probably be limited to syncing with CM, but we'll see.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks the most, [MENTION=4932679]decimalman[/MENTION]! Hope what's taking your time is making money! DLing and flashing now.

Running for a little over a week and except for some audio strangeness/ unresponsiveness, that may be rom, viper, or some combo of causes, this new build is great. Seemed to need a little "burn in" period right after first install, but thereafter, smooth, stable, and good battery life. Thanks again!
[Verizon Samsung Galaxy S III] MrBrady:
Just revisited this thread because your kernels were always fantastic and was happy to see this update. Just installed the 10/4 version over the Dec. '14 Mahdi 4.4.4 build. For some reason the phone isn't sleeping (see attached). Prior to installing the kernel it slept great.

Governor: tierservative

Scheduler: fiops

EDIT: May not be the kernel. Dirty flashed the ROM to roll back the kernel, then threw on Better Battery Stats. It'd showing System Update is keeping the device awake nearly 100% of the time.
[Verizon Samsung Galaxy S III] AyUaxe:
The 10/04 dkp is for Lollipop 5.1.x. There are KK builds linked in OP, but don't know if they're still getting updated. Can recommend 10/14 cm12.1 lollipop build of you're open to updating ROM and using this kernel.
[Verizon Samsung Galaxy S III] MrBrady:
Looks like 4.4 versions have been updated too. https://www.solidfiles.com/folder/2c84317650/
[Verizon Samsung Galaxy S III] MrBrady:
Delete
[Verizon Samsung Galaxy S III] AyUaxe:
So, [MENTION=2535561]SilentDude56k[/MENTION], wondering if you tried a build and if so, how it turned out?

Mighty silent, dude. Feel like I'm whistling past a graveyard.
[Verizon Samsung Galaxy S III] Master Cylinder:
Thanks a million for the builds, man. Solidfiles is pretty crappy, though I got the files. Had a chat with a sexy babe for a few minutes, though, if she wasn't a robot.
[Verizon Samsung Galaxy S III] Root Wizard:
Does this work with SafeStrap 4.00 and SUPERLITEROMv5.0-DEODEXED? The rom is here ->http://xdaforums.com/galaxy-s3-verizon/development/rom-superliterom-v1-0-i535vrudne1-t2805797
[Verizon Samsung Galaxy S III] SilentDude56k:
Looks like I missed my notification email! Sorry about that.

I tried building after my last forum post and ran into issues with LTO using several different versions of the Linaro toolchain. I gave up for the night, and I guess I forgot to continue working on it :(

I do have some good news though! I managed to successfully build, flash, and run the current 10/4 revision of dkp just a few minutes ago with LTO disabled using a Linaro 5.2 toolchain build from October.

I'd still like to get LTO working, if possible. I've tried 4 different versions of the Linaro toolchain so far: 4.7, 4.8, 4.9, and 5.2.

4.7 compiles, but bombs out during LTO.

4.8 and 4.9 bomb out immediately. It seems that something is broken in Makefile.lto.

5.2 also compiles, but bombs out during LTO like 4.7. However, unlike 4.7, it gives a warning for every object file. For example: "init/calibrate.o: plugin needed to handle lto object"

[MENTION=4932679]decimalman[/MENTION], do you do anything special to get it working or do you disable it like I did?
[Verizon Samsung Galaxy S III] sshafranko:
Found it
[Verizon Samsung Galaxy S III] Deliquified:
Perhaps Perseus could give you a point in the right direction. He builds KT kernel on the side of working on Slim and likely has ran into this
[Verizon 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

LTO kernels are pretty tricky. I sent him some information by PM about it.
[Verizon Samsung Galaxy S III] AyUaxe:
Woohoo! Close enough to Christmas for me! I tried cm13 12/24 with dkp 10/04/15 and saw no kernel issues, but didn't keep cm13 for long enough to try much (phone, WiFi, and lte worked well, but couldn't read sd card, so glad i had backup).
[Verizon Samsung Galaxy S III] SilentDude56k:
I've been running the 12/27 AOSP 6.0 build on the CM13 12/31 nightly today and so far, so good. Thanks for the update!
[Verizon Samsung Galaxy S III] Master Cylinder:
Man! I'm sooo glad he's still putting out kernels! Awesome!
[Verizon Samsung Galaxy S III] griz.droidx:
Me too master cylinder. Decimal is the man when it comes to kernels IMHO. Been using them forever. Still using them on the latest mm aicp nightlife as well.
[Verizon Samsung Galaxy S III] Master Cylinder:
I had no doubt! :sly:

I'm just about to install the kernel on the latest AICP myself to see if it might solve a problem I'm finding only with AICP. Button issues .
[Verizon Samsung Galaxy S III] unimatrix725:
Nevermind found out its related to DNS/INETD in KitKat and above. Just thought it was odd. Will leave this in case someone else asks.

I have searched and only found that there is network mods for the kernel. What I need to know is why the Kernel needs to access the Internet? This is suspicious and being paranoid, I keep it blocked in firewall. I am trying to fund the log file for my firewall. Using AFWall+, it has option checked. When I do find it I will trace addresses. Some information on this would be helpful, especially facts. I occasionally see a toast popup, blocked xx.
[Verizon Samsung Galaxy S III] AyUaxe:
Any update on the internet access issue, [MENTION=373411]unimatrix[/MENTION] ?

Paging [MENTION=4932679]decimalman[/MENTION]! Hope you're well. You are missed.
[Verizon Samsung Galaxy S III] decimalman:
I generally don't touch any of the kernel's network code. It's horribly complex, and I don't see any reason to change it. I've made a few trivial optimizations to the wifi driver, fixed a small bug in the modem driver, and enabled a few additional congestion control algorithms; I haven't made any changes that require network access.

Unrelated to dkp, there are reasons why the kernel might need network access, most obviously network filesystems. If you're not using such features, then there's no harm in firewalling the kernel. AFWall's kernel rule appears to pick up a lot of non-kernel activity as well, but apparently I've had it blocked for years and never even noticed.
[Verizon Samsung Galaxy S III] unimatrix725:
Thanks for clarification and the killer kernel. I ended up WHOIS'ing the blocked addresses from the log. Apparently Google is using the kernel for something over encrypted ports. Makes me suspicious about the whole thing. I feel better knowing you have nothing to do with this strange behavior.

Maybe someone can chime in on what's up? I would post the result, but I'm a packet sniffing n00b.

Here are the addresses:

Total Packets Blocked:	188

[TCP]172.217.1.193:443(39)

[TCP]172.217.1.1:443(48)

[TCP]216.58.217.170:443(7)

[ICMP]64.233.177.127:48132(3)

[TCP]172.217.1.193:80(12)

[TCP]172.217.1.14:443(46)

[TCP]172.217.1.1:80(9)

[TCP]216.58.195.138:443(18)

[TCP]172.217.4.74:443(6)
[Verizon Samsung Galaxy S III] decimalman:
You can get a bit more detail about the logged packets in a terminal:

su
dmesg | grep AFL | grep -v UID

The "| grep -v UID" bit filters the list so only packets from the kernel are shown. On my phone, I'm only seeing TCP ACK FIN, which are part of the sequence of packets that close a TCP connection. EDIT: I'm not at all familiar with the kernel's TCP stack, but I assume it's handling closing connections without involving whatever was using the connection, hence no UID on the packets.
[Verizon Samsung Galaxy S III] AyUaxe:
Are any of these changes incorporated in a build after 12/27/15? Also want to say how very very much I appreciate your work. DKP makes my D2 fly and gives me excellent stability and battery life--substantially better in every category than the stock CM kernel. I especially appreciate your inclusion of the Illinois network congestion control algorithm. Subjectively, it makes web browsing noticeably faster with any/every browser. Best of the best to you and yours!