yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
Sorry for that. I trying to say that I haven't found any stable release in download link for ASOP 4.4.x.

And now I understood kernel in test still. I'm waiting for stable as DD. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
What issues are you having? Decimalman could provide some help if you provide some logs. That will aid in the process of making this kernel stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Nor will you find them in "Stable". In the OP, decimalman states that when he classifies them as stable, they bug up. He names them test (trying to beat good ol' murphy and his "law" ;)), but they are very stable for daily driving.

Choose the best one for you and happy flashing. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
*I do not unfortunately* wish I could help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
I know it's not at the top of the to do list but any chance that GPU governor's will be added sometime? I like to underclock and use simple to gain more screen time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I can't resist (potentially) breaking things for long enough to get a stable build out. ;) Of course, Murphy's law does usually come into play when I do "stable" builds--after the first "stable" dkp build, I spent 12 straight hours debugging a handful of issues that popped up.

I've only got one BT device to play with, but I'll dig it out and play around a bit.

I think simple is pretty self-contained, so it shouldn't be terribly hard to add. I'll put it on the to-do list.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
I'm a bit confused also. The d2att version is from Dec 26. I don't see a new version for att.

J
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Right here:

http://d-h.st/users/decimalman/?fld_id=31838#files

You just have to look through his directory a bit more thoroughly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I like breaking them too, that's why the wife hates when i sit down with the phone in my hands :angel:

How can it not, It's Murphy...LOL...Ouch on the 12 hours debugging, but your hard work is appreciated by all and for that, THANKS (button hit too) ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
To tell you the truth, since I started using this kernel I haven't stopped! Screen latency is almost non-existent.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
Thanks mate. I know the truth, but there weren't any named as "stable".

I'll stick to the plan, Thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Anyone tried this kernel with PA 4.0?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Trying this on TouchWiz ROM, any recommendations on settings for governor and scheduler?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
After resisting for ages, I think it's time dkp got a fancy splash screen. I don't have any design flair whatsoever, but I'd love for someone to contribute something. If possible, it should be a 720x1280 PNG. Anyone interested?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
Don't we need any special symbol for it? I like this idea.

Tapatalk on i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's some awesomeness coming in the next build. That's all I'm saying. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
Packing device to send onto dance floor. :beer:

Thanks for the tip.

Tapatalk on i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's finally time for the new AOSP test build I've been teasing! I'm pretty excited about the new installer: it allows on-the-fly splash screen generation, ramdisk tweaks, and it's multi-threaded so it doesn't take forever to cook the new ramdisk.

There have been a lot of splash screens posted in the last couple days, and I can't pick just one. I rolled eight into this build, and the installer will pick one at random every flash. I'm thinking about changing the lineup every couple builds, so keep the splash screens coming. :good:

Downloads aren't going to the usual location! Dev-Host has been pretty unreliable, and when I heard that they're sneaking bogus APKs in with legitimate downloads, I decided I'm done with them. Downloads are up on Mediafire. I haven't been able to find an ideal file host, but Mediafire seems less awful than most. EDIT: Mediafire is acting up already. :( Direct link is here.

Changelog:

Ermahgerd splersh screrns*!

Updated to a toolchain based on GCC trunk (i.e. GCC 4.9 development)

Linux 3.4.79 and oodles of CM updates

Stripped a few useless bits from the board file

Fixed the power key not rebooting

By request, added simple GPU governor

Changed the default minimum voltage back to stock**

Lowered absolute minimum voltage limit to 600 mV for the few phones that can undervolt below 700 mV

* I included eight splash screens, one of which will be randomly picked at each flash. If you'd prefer, you can switch to a custom splash screen: extract the initlogo.rle from a splash screen zip to dkp/splash.rle in your internal storage, and it'll be applied automatically whenever you flash. Copying a PNG to dkp/splash.png also works, and I'll add support for JPEGs soon.

** The stock defaults are back. Too many of the issues being reported are (probably) caused by the lowered default voltages. There's a new (fixed) custom vmin zip here to lower the limit, Trickster's "Override Minimum Voltage" still works, and the old (lowered) default will carry over until you flash a new ROM. I'm considering adding an addon.d script so that a custom minimum voltage setting will carry over after ROM updates, but I haven't gotten to it yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Download is no good only getting 40kb

Edit looks like it may be a problem with chrome and the DL site. Tried the stock browser and it downloaded OK!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
Thanks for your hard work for us. Probably test this update.

Tip: try mega.co.nz if there's no other option. Working pretty good for me;still.

Tapatalk on i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Anyone try this kernel yet? How's consumption with screen on?

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
^its awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
For some reason on Quantum 3.3 after sitting idle for a while my screen is unresponsive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Did you UV? If so, raise your voltages a bit and check again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's a new AOSP 4.4 test build up on Mediafire. I haven't changed much, just fixed two silly bugs that might be causing problems with wifi wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
What do you think?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I was hoping to get some more clean designs like this. :good: Now I just need to decide which splash screen to swap out to make room for it. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
How about this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Holy cow, battery drained 100% over 2 hours of track practice non usage. Definitely will test out the new build and report back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Awesome work on latest build! Great battery life and still have lte! Flashed on newest HellKat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
I tried it without changing any settings and it still occured. I'll try the latest release to see if it's fixed. Hopefully it is. I really like this kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Any tw magic coming? Aosp is getting all the attention now the other children r jealous u gotta love us both equally lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I think I'm going to use the first one, but haven't made up my mind yet.

It's in the works. There's some misbehavior that I need to track down first. I also had to rewrite a driver to fix a long-standing bug that's hitting Sprint especially hard, and I want to make sure it's working well before I officially release it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New TW builds are going up! I think I fixed the misbehavior that was holding this build up, though I haven't heard back from all my guinea pigs yet. If this builds still misbehaves, let me know.

Downloads are on a new host generously provided by xstefen. I'm in the process of moving things over, and more downloads will appear in the coming days.

Changelog:

Splash screens!

By request, added simple GPU governor

Fixed (hopefully for good this time) the wifi wakelock going crazy

Wrote a new a2220 (voice processor) driver to fix some major issues plaguing Sprint. If it causes any call-related misbehavior, let me know.

Lowered the minimum voltage to 600 mV for anyone crazy enough to UV below 700 mV

Restored the stock (1150 mV) minimum voltage, you'll need to change it manually to undervolt effectively

To adjust the minimum voltage there's a new custom vmin zip here; rename it something like "dkp-vmin-700.zip" and flash. Trickster's "Override Minimum Voltage" still works as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Socomfort99:
Decimalman,

I tried to download the New TW 4.3 build but I'm getting a different MD5 than what the file host lists. My MD5 is 20551582d5d783475958399d3b9a6231.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The file host's MD5 (405fa4f1dec43efca141451022989516) is correct. Clear your browser cache and try downloading again, I guess. :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
So we have Decimelman kernel commit in today's nightly. Think CM team is happy with the development of DKP kernel:

http://review.cyanogenmod.org/#/c/59829/

keep up the good work!!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
It's a little disturbing to me that the user who added it into CM did so without understanding it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hi, I understand Decimalman's code perfectly. I'm sorry my commit message offended you, it was meant to be humorous. [MENTION=4932679]decimalman[/MENTION] great work, I'm very appreciative of the work you do and it's awesome you gave us pemission to use your wifi commits as well as the fading led. I'm aware it's GPL code and permission is not required, but it's always nice to have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Socomfort99:
I had to switch from dolphin to chrome to get the kernel to download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I use slim's stock browser... way faster than chrome or dolphin
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
I wasn't offended, just a little surprised someone was adding something they implied they didn't understand to the CM base. I didn't pick up on the humour / sarcasm. This internet thingie makes it hard to pick up on that stuff sometimes. Thanks for the work you do and share back with the community.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Has anyone been able to get to 2.1ghz? If so what voltage do you have set? I'm curious to see if mine can get there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's always a pleasant surprise to see you picking up my changes. :good: Regardless of GPL, a CC or comment like you've been doing is appreciated (especially if I misplaced the other half of a commit you're interested in :silly:).

There are probably very few phones that can go that fast, and those that can are guaranteed to need the full 1400 mV that dkp allows.

Beyond 1.9 GHz or so, things get unstable very quickly, and increased voltage doesn't improve stability much. Overclocking also tends to yield progressively less performance, so 2.1 GHz isn't actually much faster than 1.7 GHz. On top of that, the extra heat being produced means that the thermal throttle will kick in sooner, dropping you back to ~1 GHz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
[MENTION=4932679]decimalman[/MENTION];50468075 for the simple gpu governor tunables, what exactly do they do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The app you're using is bound to use different names for everything (I'm listing the in-kernel names here), but the tunables basically work like this:

laziness: controls how long it takes to switch to a lower frequency (lower will switch to lower frequencies faster)

ramp_threshold: controls how much the GPU can be busy without switching to a higher frequency (lower will switch to higher frequencies slower)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Hey just wondering what recommended settings, sched n gov for tw 4.3 I've been getting horrible battery life but the kernel plays nicely with my phone who wants to change lol. Also there's some other congestion controls not thrown in the rom. Can we get them n the led from ur latest aosp kernel added to the next tw release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Anyone using this kernel with the latest Quantum 4.4 rom? My screen kept locking up. Want to know if there is a solution. I love this kernel but the latest updates haven't been friendly with my phone and rom, currently Quantum 3.45. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miten_sheth:
Trying this out..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Turns out free lunch governor wasn't working well with the latest quantum rom. Now I'm on interactive and it's running great with pretty good batter life. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's been a while, so let's do some new builds for both AOSP 4.4 and TW 4.3. Still no love for TW 4.1 (are enough people using 4.1 to justify continuing support?), and I still haven't fixed up the bluesleep driver that's been causing bogus wakelocks on AOSP (it really needs to be rewritten).

EDIT: Wifi isn't working on the AOSP build.

EDIT 2: Fixed builds are up!

TW Changelog:

Major overhaul to erandom, msm_rng, and all things entropy:

A new entropy daemon, plus a new touchscreen entropy source

Major speedup for erandom

Bugfixes and a major speedup for the hardware random number generator driver

Cleaned up (among other things) erandom initialization

Enabled network block devices

Swapped in a new splash screen

AOSP Changelog:

Synced up with CM, Linux 3.4.82

Major overhaul to erandom, msm_rng, and all things entropy (everything from the TW changelog is included)

Added code to save some entropy across reboots

Enabled network block devices

Swapped in a new splash screen

If you're not sure what network block devices are or why you'd want them, you probably don't have much use for them. I enabled them at the request of Phil_Suz, who's been working on an interesting multiboot system (there should be a thread in the General subforum for your device). NBD support opens up some very interesting possibilities, especially when paired with multiboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update.

Quick Question(maybe newbie): To get the maximum benefit of this kernel, should we have to use only Freelunch Governor only? I face lagging on both TW/AOSP while using Freelunch.

So if I use "interactive" governor on this governor, will I still get the added advantage of the commits you have done on the default CM governor? Or I will be missing on the great work you have done on this kernel? For e.g. the msm_otg overhaul mentioned in the change log above is applicable for all the governors in the kernel or only to freelunch?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Not at all. freelunch makes a lot of sacrifices an effort to save battery, and it's painfully slow at times. It's completely separate from everything else in the kernel, so there's no need to use it if you prefer interactive.

EDIT: I'll be the first to admit that freelunch hasn't aged well. I've been working on its successor (I have a few ideas that seem to work pretty well :)), but there's still some issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Download is to slow. 4 unsuccessful download attempts..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
No problem downloading
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the clarification. Do you recommend any specific kernel for battery apart from free lunch? Or any specific kernel settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Throw this in your init.d folder with the right permissions. You'll see a little bit of battery savings, and your screen colors will be a little more... colorful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegasdiceshooter:
2-26-14 build won't boot on my phone any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Newest working well with latest Slim KK weekly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
What do you think? I like this splash image personally.... because I made it lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shiniyoyo:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Any governor other than interactive, ondemand, or performance should be easier on battery; asswax is definitely worth a look. I was supposed to add pegasusq as well, but it's not designed for Krait processors and I haven't gotten around to fixing it.

Lowering your maximum CPU frequency will improve battery, and won't hurt performance as much as you'd expect. Disabling UKSM (which Trickster can't do, for some reason :() might improve battery a little bit. Lowering your CPU voltages and/or minimum frequency might save battery, but might also cause instability.

To start with, I'd suggest providing some details when reporting a problem. What ROM and version? Any mods? How far does your phone get when booting? Does it reboot automatically or just freeze?

Ooh, glowy! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eddalysse:
what is UKSM? And how do I disable it?

Sent a long time ago, from a galaxy far far away . . .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for your response. So this applies for TW Kernel also, I keep changing my ROM AOSP/TW every week. So what will be the best way of disabling UKSM if that cannot be disabled through Trickster, any scripts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eddalysse:
Manage to disable it using the performance control app, under memory settings

Sent along time ago, from a galaxy far far away
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you share the specific settings. Can't find
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eddalysse:
Performnace Control - memory settings - Kernel Samepage Merging - Enable KSM (ultra KSM detected) uncheck box

Sent a long time ago, from a galaxy far far away . . .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegasdiceshooter:
phone wont boot:

I am running AOSB ROM no mods and it freezes at dkp boot screen, I have been running all your kernels the latest being 2-13 version, I never had a problem before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Look at the script I provided, it disables uksm.

#!/system/bin/sh

echo 0 > /sys/kernel/mm/uksm/run
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Just a question pertaining to ur script. Just wanna make sure im clear I can copy the contents n create a script from it in rom toolbox, set it to run at boot and bobs ur uncle?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Yes, yes you may.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Socomfort99:
Decimalman,

I loved your kernel on 4.1.2 but I'm fighting a wlan_wake issue on 4.3 that only seems to happen with your kernel. I've used shark to check out the packets that could be an issue causing the wlan to wake the device. One of the packets was a request for name from the router to my device and it was to a port that my s3 said was unknown. I don't know much about kernels and wlan but does the kernel have anything to do with what ports are open on the s3? Is there any firewall within the kernel that could block ports causing this packet to not be delivered? I maybe way off on this but just thought I would check. Thanks for all of your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Getting high wakelocks in latest tw kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
What tw rom are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
S3rX by enewman/loser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
Can anyone point me the latest build link for 4.1? I can't find it on the new host. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Did you wipe cache/dalvik?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phil_Suz:
Hi decimalman,

This new build is working perfectly for next multiboot features (still have some performances issues to reduce with qcow2 file format) .

Thank's for update.:good:

Philippe,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmasblade:
Can someone tell me how I can use this file and where is the init.d folder?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
If you're running an AOSP ROM, flash this at the end of my post. If you're running a touchwiz ROM, check to make sure it has "init.d support" with the ROM developer and ask in that forum. If it does, then flash this zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
I'm still looking for a 4.1tw dl link
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmasblade:
Okay thanks. Can I use dkp on Task650 AOKP ROM And the file you provided me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Yes you can :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmasblade:
Okay and if I flash the file you gave and then I want to flash a new kernel, will there be any problems or any special steps I would need to take?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Flash this before you flash another kernel. It will delete the two files the other zip placed in your system.

http://www.mediafire.com/?hedqkquzcca2vb8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmasblade:
Okay thanks. So this the first file you posted is supposed to save battery? By a lot or by a bit?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's a hint in the OP. ;)

There's not much I can do about bam_dmux. IIRC, it handles communication with (among other things) the modem, and usually acts up when something is going on with the carrier's network.

I reworked the wifi wakelocks recently, and I thought I'd fixed the last of the wakelock misbehavior in the 2/25 build.

One of the Linux kernel development rules is "mechanism, not policy." In this case, that means that the kernel supports a firewall configuration, but it's left to applications to configure that. If you're not running a firewall app, the kernel shouldn't drop your packets without good reason (e.g. nothing is listening on that port).

Thanks for the extra information. I haven't forgotten about you, I just fell off the grid for a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Just a little bit, but not much. You'll notice more battery savings in standby mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmasblade:
Alright thanks. I really want to optimize battery life, what other things should I do? MP-Decision off in Trickster? What governor should I use? Oh and undervolting an option for a beginner like me?