I'm confused. I'm on 4/17 CM10.1 and I couldn't boot work the newest experimental kernel. Did I do something wrong?
Sent from my SGH-T999 using xda premium
[KERNEL][AOSP4.4/5.1/6.0/7.1] dkp - d2tmo - 2/4/18
- Thread starter decimalman
- Start date
-
- Tags
- aosp battery development kernel
I'm confused. I'm on 4/17 CM10.1 and I couldn't boot work the newest experimental kernel. Did I do something wrong?
Sent from my SGH-T999 using xda premium
Derp. I posted the announcement literally 10 minutes after waking up, and failed to specify that it's only for the 4/19 nightly, which has some driver changes that will break existing kernels. Sorry for the confusion.
Sent from my SPH-L710 using xda app-developers app
So in other words, it won't be usable until the next nightly is released?
Sent from my SGH-T999 using xda premium
Sent from my SGH-T999 using xda premium
Derp again. I really need to stop posting before I've had my coffee. It looks like only d2att got a build with the changes and everyone else is still on 4/17.
Correct, the newest kernel won't boot until the next CM nightly.
Sent from my SPH-L710 using xda app-developers app
Last edited:
I updated via CyanDelta (just found out about it), then I was able to boot with the new kernel.
Interesting. I didn't expect CyanDelta to be more updated than the get.cm builds. Good to know. :good:
A d2att user reported that the first round of builds has broken USB: the phone won't boot when plugged in, and data transfer won't work. I fixed it and uploaded new builds, so you should grab one if you get a chance.
I can confirm no boot when plugged in. I'll download the new one shortly and report back.
mine boots fine plugged in with newest dkp kernel and latest 4-18/4-19 CM nightly
I am however getting a fair amount of screen flickering for the first time since the Jan/Feb nightlies ... wondering if its the kernel.
haven't had a chance to look at kmsg or logs. been on the road all day.
Sent from my SGH-T999 using xda premium
I am however getting a fair amount of screen flickering for the first time since the Jan/Feb nightlies ... wondering if its the kernel.
haven't had a chance to look at kmsg or logs. been on the road all day.
Sent from my SGH-T999 using xda premium
You probably downloaded the second build that had the USB bug fixed. As for the flickering, I haven't seen any all day. I'm not running the full driver update (I had to revert a commit to be able to use it with my current ROM), so it's possible there's an issue there. I'll grab my ROM's next nightly and look into it tomorrow. Until then, you might want to go back to an older CM with a more stable kernel.
You probably downloaded the second build that had the USB bug fixed. As for the flickering, I haven't seen any all day. I'm not running the full driver update (I had to revert a commit to be able to use it with my current ROM), so it's possible there's an issue there. I'll grab my ROM's next nightly and look into it tomorrow. Until then, you might want to go back to an older CM with a more stable kernel.
Its because display drivers has been updated by cm. New ROMs based on latest nightly will be ok
Sent from my SGH-T999 using Tapatalk 2
any suggestions to tweak freelunch? i'm mainly looking for battery life (i know every phone is different, just looking for a jumping off point)
I've been meaning to write up how freelunch works, but I keep getting distracted. Decreasing interaction_hispeed and interaction_overestimate_khz, as well as increasing hispeed_decrease should all increase battery life at the expense of some performance. You could also try tuning all the hotplug settings, since I don't think they're perfect.
New 3.4 stable builds are going up! I'm planning to backport a few changes and do a new stable 3.0 release soon, since I know there are still some users that don't like 3.4.
Major features since the last stable release: lots of stuff. If your ROM hasn't merged in the CM video driver changes yet, your should ask the dev merge them so you can upgrade.
Notable changes since the last test builds:
Major features since the last stable release: lots of stuff. If your ROM hasn't merged in the CM video driver changes yet, your should ask the dev merge them so you can upgrade.
Notable changes since the last test builds:
- Newest CM commits integrated. They've been hard at work causing merge conflicts.
- At user request, the AssWax governor has been added (and works!). It has an extra interaction mode to support dkp's interaction hints.
- Kernel-wide erandom finally works on 3.4
- New CPU load interface with much higher precision than the existing one, plus two new governor variations to take advantage of it
- Trinity colors setting takes effect instantly. Now I just need to get apps to show a setting for it. Want to try it temporarily? Enter 'trinity' in a terminal emulator.
- Cleaned up some touchscreen code
New 3.4 stable builds are going up! I'm planning to backport a few changes and do a new stable 3.0 release soon, since I know there are still some users that don't like 3.4.
Major features since the last stable release: lots of stuff. If your ROM hasn't merged in the CM video driver changes yet, your should ask the dev merge them so you can upgrade.
Notable changes since the last test builds:
- Newest CM commits integrated. They've been hard at work causing merge conflicts.
- At user request, the AssWax governor has been added (and works!). It has an extra interaction mode to support dkp's interaction hints.
- Kernel-wide erandom finally works on 3.4
- New CPU load interface with much higher precision than the existing one, plus two new governor variations to take advantage of it
- Trinity colors setting takes effect instantly. Now I just need to get apps to show a setting for it.
- Cleaned up some touchscreen code
appreciate the hard work!
Sent from my Nexus 4 using xda premium
dammit beat me to the asswax implement. good work man. don't mind if i cherry pick a few of your changes?New 3.4 stable builds are going up! I'm planning to backport a few changes and do a new stable 3.0 release soon, since I know there are still some users that don't like 3.4.
Major features since the last stable release: lots of stuff. If your ROM hasn't merged in the CM video driver changes yet, your should ask the dev merge them so you can upgrade.
Notable changes since the last test builds:
- Newest CM commits integrated. They've been hard at work causing merge conflicts.
- At user request, the AssWax governor has been added (and works!). It has an extra interaction mode to support dkp's interaction hints.
- Kernel-wide erandom finally works on 3.4
- New CPU load interface with much higher precision than the existing one, plus two new governor variations to take advantage of it
- Trinity colors setting takes effect instantly. Now I just need to get apps to show a setting for it.
- Cleaned up some touchscreen code
Go for it, but don't grab asswax yet. I need to push a bugfix first. You'll also need to strip out all the interaction stuff or it won't compile.
Choices are always good. I just pushed the fix, so help yourself to the source. :good:
New fixed stable builds are up!
Issues fixed:
- If the ROM doesn't start mpdecision correctly, interaction and asswax will leave core 2 online forever. dkp will now start mpdecision if needed.
- mpdecision is fussy and I hate it. I think I managed to get it to stop whining.
- Trinity colors now defaults to on. I'll get a zip up shortly to disable it.
- AssWax causes reboots. Fixed.
Last edited:
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
45Welcome to decimalman's kernel playground!
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
- Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
- Underclocking down to 54 MHz, with stability improvements
- Undervolting compatible with most apps
- Fast charge without unplugging first
- Glorious animations for the notification and softkey LEDs
- Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
- freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
- Automatic mpdecision and auto-hotplug are only enabled when needed
- Adjustable minimum voltage for stability on finicky processors
- Optimized UKSM to free up some extra memory
- Code optimizations for size and speed
- Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
- Nandroid!
- last_kmsg and/or logcat or it didn't happen.
- Other kernels have their own threads or forums. Discuss them there.
- Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
- Be silly. We're here to have fun.
Installation:
- Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
- Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
- Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.10It's time for another TW 4.3 test build. There aren't many dramatic changes, but I did fix a few bugs. Probably the biggest change is a fix for the disappearing apps phenomenon, which means that it's safe to turn SELinux back on.
Changelog:
- Fixed the disappearing apps bug
- Enabled SELinux again
- Added several TCP congestion control algorithms
- Fixed a silly mistake that broke several motions
- Cleaned some code up, removed a few useless drivers
- Compiled with a shiny new toolchain
9Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
- FauxSound support
- Strip more useless stuff
- A few bonus optimizations
- Port everything except erandom from 3.0
- Enhance cpufreq for easier configuration
- Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
- Lots of CM/CAF/Linux updates
- Working AssWax governor
- Trinity colors support
- sio, zen I/O schedulers
- erandom is back!
- Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
- Probably lots more, but there's hundreds of commits to sort through...
- Bugfixes: better overclocking support, better hwrng support, etc.
- Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
- Automatic auto-hotplug
- New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
- Bugfixes: fix several critical bugs in the 5/29 release.
- Fixes for OC, UV, auto-hotplug.
- A few new optimizations.
- Synced up with CM.
- Ported everything from AOSP to TW.
- Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
- Nothing interesting at the moment.
9Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
- Create a folder on your internal storage named "dkp"
- Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
- The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.Code:su dkp
sysfs:
auto-hotplug tuners:
freelunch/nanolunch tuners:
9Four new test builds are going up (AOSP 4.3 & 4.4, TW 4.1 & 4.3). Clearly, I've lost my mind. The new builds should fix the sleep of death bug and the strange softkey behavior. The notification LED and softkey backlights are a bit wonky on TW, but they shouldn't be severely broken. If there's still any major bugs, let me know.
Changelogs:
