yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
I added it a little while back, but didn't make a big deal out of it. It "works," but not as well as I'd like: performance varies a lot between games, and the higher frequencies are unstable for some people. As far as I can tell, there's nothing I can do about either problem. :(

Me too. :)

I'm thinking about making it the default in the next build. I made a bunch of changes that made it more responsive (but reduced battery a little bit), and I think most people would have a hard time telling it apart from interactive.
[Verizon Samsung Galaxy S III] MrBrady:
Next build? [emoji15]
[Verizon Samsung Galaxy S III] decimalman:
I suppose I ought to just release it already, but there's not much new except the changes to tierservative, and I'm not satisfied with them yet. There's a small bit of logic that I know is wrong, and that I think is causing the increased battery usage, but I can't figure out how to fix it.
[Verizon Samsung Galaxy S III] MrBrady:
Take your time man. I trust your judgement. Too bad my emoji didn't come across on XDA web (I posted via Tapatalk). I didn't mean that as an ETA, I meant that as an OMG!
[Verizon Samsung Galaxy S III] decimalman:
Don't worry, I took it to mean excitement. I'm looking forward to getting the new build out and getting some more feedback on tierservative. I keep delaying for one reason or another, and now I'm getting impatient. :p
[Verizon Samsung Galaxy S III] decimalman:
What the heck, I'll put the new build up. tierservative is still using a little more battery than I think it should, but it'll be another month before I get that figured out.

New AOSP build is up on both mirrors. Changelog:

Lots of changes to tierservative

Changed balanced performance profile (i.e. the default) to use tierservative

BFQ v7r6

A shiny new GCC 4.9.2 toolchain with some new Krait-specific tuning

Feedback on the changes to tierservative is encouraged. They definitely increased battery usage a bit, but also smoothed out performance considerably.
[Verizon Samsung Galaxy S III] tvl76:
Running on Slim, the new build definitely uses moe battery. Appears it does not to go into deep sleep.

I switched back to the previous build for now.
[Verizon Samsung Galaxy S III] sbattosai:
I'm getting massive reboots which ultimately end up in a bootloop. Tried Omni rom and dirty unicorn, same result. Old kernel from 10/02 is more stable. Thanks anyway!
[Verizon Samsung Galaxy S III] thelangosta:
Strange, I'm not having any reboots. You may need to raise the voltages a bit.
[Verizon Samsung Galaxy S III] aromig:
Sooooo...... any chance we could talk you into a Lollipop version of your kernel? I've been missing your Tierservative governor, as well as Westwood (no idea why this isn't more popular/common).
[Verizon Samsung Galaxy S III] decimalman:
YGPM. :)
[Verizon Samsung Galaxy S III] Deliquified:
Ooh, pick me! :)
[Verizon Samsung Galaxy S III] decimalman:
YGPM. :)

Anyone else?
[Verizon Samsung Galaxy S III] HikingMoose:
Is the new CM build as smooth as the linaro kernel?

Sent from my SCH-R530 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] decimalman:
It should be exactly the same, it just has the new CM driver commit included. OTOH, I've heard reports that the new drivers are a bit rough around the edges, but I haven't actually tested for myself. Us poor d2spr users just got our first ROM with the commit today and I haven't gotten around to flashing it yet.
[Verizon Samsung Galaxy S III] xHoLyx:
Longest I've been on a single kernel since I got this phone.

Looking forward to future updates.

Thanks a lot [MENTION=4932679]decimalman[/MENTION]
[Verizon Samsung Galaxy S III] trvbone:
Woohoo trickster mod just added faux sound control !
[Verizon Samsung Galaxy S III] m-cat:
Hey,

So I flashed this last night and ended up odining back to ICS. Not sure what happened...I downloaded the 3.4 version and followed all directions completely. Any idea what may have happened?
[Verizon Samsung Galaxy S III] decimalman:
I need more information. What ROM are you running, and when was it released? Were you previously running a different kernel? What was the date (or branch name) on the dkp zip you flashed? What did your phone do when you tried to turn it on?

Without more details and/or a last_kmsg, all I can do is throw out some general speculation. Android versions before 4.2.1 aren't supported, but good luck finding an AOSP ROM that's still based on 4.1.2. Most AOSP ROMs are currently running 3.4 kernels, but if you're using an older ROM it may need a 3.0 kernel instead. I think you'll get bootloops with the wrong kernel version, but I haven't checked. Check your ROM thread for details on which kernel version to use. If your ROM uses 3.4 and was released before 4/19, it won't work with the newest test build (20130419 "cm-nightly") due to some CM changes to the video drivers. With the wrong video drivers, your phone will boot (you'll see charging LED and touchkey lights), but the screen won't come on.
[Verizon Samsung Galaxy S III] decimalman:
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. :p

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
[Verizon Samsung Galaxy S III] trvbone:
I don't see a 424 build in testing are we just to use the stable version now
[Verizon Samsung Galaxy S III] decimalman:
I haven't found any new bugs lately, and as far as I know everything works the way it should. I decided the new build is stable enough for the stable folder. :D
[Verizon Samsung Galaxy S III] HikingMoose:
So if my ROM is two days old (jellybam) it probably won't boot huh?

Sent from my SCH-R530U using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] m-cat:
I was on Sons of Android b4, it was released on 3/29 and the kernel version was 3.0. I flashed the stable 3.4 kernel, and after the flash it would vibrate, show the Samsung logo then nothing.
[Verizon Samsung Galaxy S III] decimalman:
It should. Most ROMs had the new drivers integrated by 4/20 or so. If not, you can always flash back to whichever kernel you're running now.
[Verizon Samsung Galaxy S III] borxnx:
What's the difference between the new nano- prefixed governors and their counterparts (e.g. nanolunch and nanoactive vs. freelunch and interactive)?

I really like your kernel! Been lurking and running it for a while! Thanks for the d2usc love!
[Verizon Samsung Galaxy S III] decimalman:
The freelunch and interactive governors use the traditional CPU load interface. Its readings are measured in increments of 10 ms. The nanolunch and nanoactive are experiments that use a new interface that I threw together. The readings are measured in 1 ns increments (hint: 10 ms = 10,000,000 ns), which should be much more accurate when sampling every 10 or 20 ms. My hope is that they'll do a better job of estimating CPU usage and be both slightly smoother and slightly better on battery life.
[Verizon Samsung Galaxy S III] borxnx:
Thanks for the quick reply!

That sounds awesome. I really like the way my phone balances performance and battery saving on freelunch, it's a great governor. And now nanolunch seems like it'll be even better!
[Verizon Samsung Galaxy S III] masri1987:
So we don't have to do nada to enable trinity colors?
[Verizon Samsung Galaxy S III] decimalman:
I didn't think to make it the default, so you still need to flash the zip whenever you flash a new ROM. It'll stick between kernel flashes though.
[Verizon Samsung Galaxy S III] GideonX:
Hey DM, props on getting asswax to work. :good:
[Verizon Samsung Galaxy S III] decimalman:
Ehh, it doesn't quite work yet. I missed a bug that causes a NULL deref, but I've got it fixed and I'll push it later on. Thanks though! :D

Edit: Fix is pushed. You're welcome to grab my sources, but you'll need to remove all the interaction stuff to get it to compile.

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.
[Verizon Samsung Galaxy S III] krazie1:
I can't seem to find the build, can you direct me to the download link?
[Verizon Samsung Galaxy S III] LLStarks:
Sure, I'd like to try it
[Verizon Samsung Galaxy S III] alado221:
If you want to i can try it. Any specific rom build in mind?
[Verizon Samsung Galaxy S III] aromig:
Running like a top on Mastamoon's latest unofficial cm12 nightly. That stock kernel was so incedibly boring. And with Westwood, pictures actually load at a prompt speed again in my Tapatalk car forums. Gratuitous thank-yous my friend!
[Verizon Samsung Galaxy S III] decimalman:
Thanks for reporting back. :good:

For anyone else who wants it, the build I've been sending out is available on MediaFire. It hasn't gotten much testing, so please report any issues.
[Verizon Samsung Galaxy S III] MrBrady:
Not asking for ETAs, but I was curious if you're still working on tweaks for the tierservative governor. Your last post mentioned it was using more battery than it should, so I am curious if any updates are planned. Love this kernel! Thanks for keeping our SGS3s running smooth!

EDIT:

Also, just noticed the xstefen mirror listed in the OP is empty. http://download.xstefen.net/decimalman/dkp

EDIT2:

I see a little gem living in your scary tests folder. Decided to try it out and so far it boots and runs fine on Mahdi 2.9 (Android 4.4.4).
[Verizon Samsung Galaxy S III] decimalman:
My main goal is for tierservative to feel as responsive as interactive, without using battery-draining shortcuts (e.g. without jumping to 1134 MHz instantly). With the last build, I made a few changes that (IMO) mostly achieved that, but also increased battery use a bit. I've been working on reducing the battery use again, but I've only made a few subtle changes so far. The build you stumbled across should include those changes.

I really need to update the OP. xstefen took his hosting down, so MediaFire is currently the only dkp mirror. :( I'm working on finding another mirror.
[Verizon Samsung Galaxy S III] MrBrady:
Thanks man! The latest one rocks so far. Battery life seems pretty good too!
[Verizon Samsung Galaxy S III] Krystalmyth:
So far so good on Liquidsmooth's 5.0 build on the latest version of DKP. Governors working great but can only say I've tested Freelunch. Sorry the name was far too tempting, I had to do it. c:

Sadly I've had some random hard freezes with this kernel that require a hard reboot (power home vdown) to escape, upon launch the kernel would then refuse to reach the boot animation and would hang in the splash screen. I have not attempted to change the splash image. Reflashing dkp fixes the issue. I've had it happen twice in about a week, but rock solid once it boots. It literally will just suddenly freeze. No real warning. No slowdown or overheating. If anything the only thing I can remember is that it was during a back function. This happened once on both Nova Launcher and Smart Launcher 2 respectfully.

Hope this was helpful. Its way too kickass for me to not reflash anytime it happens. So I'm not too worried it won't be resolved eventually. If there is anything I can do to help, like a log or something let me know where to look or what to do if bit happens again, etc. c: <3
[Verizon Samsung Galaxy S III] decimalman:
I made a few crazy changes in the Lollipop build. I spotted a few issues with the code that could potentially cause problems, though I haven't had any problems myself.

I'm working on fixing the changes up. Once I'm happy with everything, I'll post a new build. Hopefully it'll sort everything out for you. :)
[Verizon Samsung Galaxy S III] sjpritch25:
Only problem I had was flashing the kernel. Phone didn't boot. I had to dirty flash my ROM & install the kernel for my phone to boot. Rom is the latest vzw liquid build
[Verizon Samsung Galaxy S III] griz.droidx:
First thanks for sharing your work. I too wanted to chime in on the lollipop build from 01-10 , I've used it on both aicp and liquid with no issues. I never even tried the default kernels. I set my clocks to 216-1728, and used tierservative. Smooth as silk. Thanks for your work I appreciate it as I'm sure others do too. This has been my go to kernel for a while now.

Thanks again for you hard work.
[Verizon Samsung Galaxy S III] griz.droidx:
Hey, I'm just wondering, and I know NEVER ASK FOR ETA"S.. but I'm wondering if decimalman is continuing his development of the kernel for lollipop. Right now it seems only he and Ed Chen are working on it. And I guess the maintainers of the roms, and CM, I don't know.. But customwise, they seem to be the only ones. I've been using DKP for a while now for the tierservative governor and his stock undervolting which happens to work great on my device. Just wondering if Decimal is still going to release kernels every now and then for lollipop for the S3.

Again, please don't take this as asking for an ETA, I don't need an ETA, and I know Dev's like anyone else have other things to do in life other than work for free to nothing on something they simply get a thanks click for ..

I for one still appreciate it.. I'm sure others do too.
[Verizon Samsung Galaxy S III] decimalman:
I'm haven't abandoned dkp, I just haven't been spending much time on it lately. On top of that, I'm still running KitKat full-time, so Lollipop hasn't been getting enough of my attention.

I don't mind people asking for status updates. I won't usually give an ETA, but I'll happily discuss what's happening on my end. Also, I regularly forget what I was supposed to be working on, so reminders can be helpful. :p

The previous Lollipop build included some changes that had a subtle bug that (I think) was causing most of the issues people were seeing. I think I've finally gotten everything fixed up. I haven't flashed Lollipop to verify, but everything seems to be working well on KitKat. There's a new build up on MediaFire with the fixes and some updates from CM.
[Verizon Samsung Galaxy S III] MrBrady:
This should work on both 4.4.4 and 5.0, correct? Just tried using it with Mahdi 2.9 (4.4.4) and got a ton of force closes on startup. Previous 5.0 kernel worked fine.
[Verizon Samsung Galaxy S III] decimalman:
I haven't tried it. CM has been hard at work on the 5.0 branch, and it wouldn't surprise me if some of the new changes cause problems on 4.4 ROMs.

It seems like we're overdue for a new 4.4 build (has it really been 4 months?!), so let's do one. Off the top of my head changelog: updated BFQ, changes to tierservative, a couple new tweaks and optimizations, and a couple new commits from CM. MediaFire link
[Verizon Samsung Galaxy S III] MrBrady:
Awesome, thanks man! Downloading now.
[Verizon Samsung Galaxy S III] MrBrady:
The 4.4. build is giving me the same force closes on boot.
[Verizon Samsung Galaxy S III] griz.droidx:
Wow that was fast. I just downloaded them but haven't tried them yet. I'm seriously considering going back to a Kitkat, because lollipop seems to be eating my battery alive. Or it could be placebo.. I haven't touched the kernel settings but, with the old build from Jan, I didn't get any FC's out of the ordinary or random reboots.

Thanks for the latest and greatest.
[Verizon Samsung Galaxy S III] decimalman:
Can you get a logcat? I haven't seen any misbehavior on CM11 nightlies, so I'm not sure what's going on.
[Verizon Samsung Galaxy S III] MrBrady:
I was going to pull a logcat, but then I decided to start fresh. Previously I was running Lean Kernel, which maybe has residual files that were causing issues.

I wiped system and caches, then re-installed the ROM and latest GApps (3/1), along with the DKP 3/1 kernel. Smooth sailing! No more force closes!
[Verizon Samsung Galaxy S III] decimalman:
New AOSP 4.4 & 5.0 builds are going up! Changelog:

Synced with CM

Fixed a longstanding bug I accidentally caused in intelliactive, and cleaned up asswax a little bit

Fixed rotation for SPH-L710T (triband) devices

Added new builds that support older KitKat ROMs. dkp causes problems (GPS, sync, etc. not working) on ROMs built before October 2014 or so. Builds listed under "dkp for AOSP 4.4.x (old ROMs)" should fix these problems.
[Verizon Samsung Galaxy S III] MrBrady:
Wow, even supporting 'old' 4.4.x ROMs! Impressive! Thank you!
[Verizon Samsung Galaxy S III] MrBrady:
Holy cow, this kernel is fantastic! Running on the Dec 14 PacMan release (4.4.4).

I'm having a heck of time trying to get the audio screeches, buzzes and pops to go away.

Flashes the vmin zip with 1050 but it doesn't seem to adjust the voltage in the rom, even though the zip said it was successful.

Changing it in Trickster doesn't seem to have any affect either.

Any idea what I should try to adjust this?

Edit: It seems to happen more often when I have ViPER4Android drivers installed.

Edit2: I still can't seem to adjust the voltage, but moving viper4android from system/priv-app to system/app seemed to fix the audio issues!
[Verizon Samsung Galaxy S III] MrBrady:
I take that back - I'm still getting tons of pops and buzzed with this kernel. Doesn't seem to change when I flash the vmin zip or even manually change the kernel vmin to 1050. Even when I try to change it in Trickster, it doesn't stick.

PacMan ROM 4.4.4
[Verizon Samsung Galaxy S III] griz.droidx:
Hello Brady, I know this is of no help considering I'm on a different ROM but with nameless I haven't had a hiccup. Perhaps toy could try the older 444 kernel. Decimal posited. Just a thought man hope you get it lined out
[Verizon Samsung Galaxy S III] MrBrady:
It does appear to be ROM-related. PacMan 4.4.4 includes Init.d tweaks. When I disable the MinFree Memory and Kernel tweaks, the buzzing and popping goes away when using ViPER4Android. Smooth sailing now and great kernel, as always!
[Verizon Samsung Galaxy S III] decimalman:
I just uploaded a new set of builds. They include a change that is known to cause problems. I think I fixed the cause of those problems, but I can't be sure without some more people testing. It's possible that these builds will cause random reboots and/or touchscreen weirdness. If you have any issues, let me know.

Changelog:

Added a build for AOSP 5.1

Synced with CM

Improved support for Kernel Adiutor. If you haven't tried it, you should. The latest beta build even has an Override Minimum Voltage setting! :)

Changed a bunch of power management stuff. Battery life should be a bit better for it.

Fixed a bug in the touchscreen driver that caused e.g. Sweep2Wake to gobble battery.

Added Sweep2Wake and DoubleTap2Wake. I'm not sure why Trickster doesn't show the settings, but Kernel Adiutor does. DT2W can be kind of stubborn, but S2W works well. EDIT: Enabling either option on these builds will eventually hang the touchscreen. I should have fixed builds out later today.

EDIT: It's been longer than I thought since the last build. These builds also include more optimizations to UKSM scanning; scanning is ~40% faster. They also fix a bug in ISAAC that can cause problems in some games.
[Verizon Samsung Galaxy S III] MrBrady:
So far so good on PacMan 4.4.4 Jan. 2015 build. Thanks!
[Verizon Samsung Galaxy S III] DubleJayJ:
Looked all around in Kernel Adiutor but can't find the settings for S2W or DT2W. Where are they located?
[Verizon Samsung Galaxy S III] decimalman:
"Wake Controls," but don't enable them. Really. They randomly freeze the touchscreen, and they don't work very well yet anyway. :(

I'm working on a bunch of changes to make them work better, but it's slow going. The code runs in a weird semi-suspended state where everything behaves in unexpected ways.
[Verizon Samsung Galaxy S III] DubleJayJ:
Still a no go for finding them. I hope I'm just blind or something, but I'll take your word for it and wait a bit on trying them out when I do find them.
[Verizon Samsung Galaxy S III] decimalman:
New AOSP 4.4, 5.0, and 5.1 builds are going up now. :)

Changelog:

Synced 5.1 with CM. Camera works on recent ROMs!

Fixed a bug that broke the front camera on 5.1.

Disabled freelunch on 5.1, since it's very broken and causes freezes and glitches.

Overhauled performance profiles/battery modes. Balanced will save and restore custom settings, performance won't lower your frequencies if you're overclocked, and battery saver won't increase your frequencies if you're underclocked.

Removed DT2W and S2W. It takes ages to register the initial touch, so I don't think I can get them to feel natural.

Built with a shiny new toolchain based on GCC 4.9.3.

A few small changes and optimizations.

EDIT: My build script misbehaved, so the original builds were missing some commits. I've taken the old builds down, and new builds will be up shortly.

EDIT 2: New builds are up, and they actually work this time.
[Verizon Samsung Galaxy S III] Deliquified:
Latest 5.1 build seems very stable and solid with CM 12.. Just wanted to report back to anyone who's curious.
[Verizon Samsung Galaxy S III] decimalman:
New builds for AOSP 4.4 and 5.1 just landed. I'm dropping support for 5.0, since very few people are using it.

Changelog:

5.1: Synced with CM

5.1: Disabled CPU boost (it's interfering with hotplug), re-enabled freelunch, set up the installer to patch mpdecision into the ROM

4.4: Fixed mpdecision not starting

I still haven't tracked down the boot issues on 5.1, but I'm working on it.
[Verizon Samsung Galaxy S III] DubleJayJ:
So it's not just me not being able to boot? I thought maybe my phone was trying to boot the new microSD I put in it. For a temporary fix I've found that booting straight into recovery then booting system works
[Verizon Samsung Galaxy S III] Deliquified:
If all else fails, reflashing the kernel will make it boot
[Verizon Samsung Galaxy S III] decimalman:
New builds just went up.

Changelog:

Synced with CM: 5.1 got lots of interesting stuff, 4.4 got a couple small fixes.

Fixed a bug that breaks boot. Rebooting from recovery shouldn't be needed anymore. :D
[Verizon Samsung Galaxy S III] bgorrell:
Thanks! I was having a problem where my phone died and wouldn't boot unless I plugged into a computer USB and rebooted to recovery first. The update seems to be working so far. Normal booting.
[Verizon Samsung Galaxy S III] Bort76:
Kernel Panic

Loving the kernel so far!

Buuuuuut... I've been having some random freezing since moving to this kernel. The phone will black screen and be totally unresponsive. I don't know if it is the kernel, since usually the last_kmsg file is blank after I pull the battery and restart. This time, think I may have caught something.

I've attached last_kmsg, with the panic occurring around 8539 seconds. Think you could have a look?

I'm on CM11, Nightly 4/12. dkp kernel 3.4.104 (May 8th).

Thanks.
[Verizon Samsung Galaxy S III] decimalman:
Pulling battery will wipe last_kmsg, but holding power to reboot usually won't.

I don't even know what to make of that last_kmsg. I see a few common errors, along with several bizarre errors that I've never seen before. :eek:

The panic looks to have been caused by your CPU going off the rails and landing in a bogus area of memory. Are you undervolting or overclocking? That's the sort of misbehavior I'd expect to see from an unstable processor.