yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
OK fine you were both first. It only showed one download when I checked, so it was one of you two. :p

freelunch & nanolunch do their own hotplugging but interactive and asswax still rely on mpdecision. It looks like it'll be pretty easy to get mpdecision running without using the service.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Makes sense because I noticed interactive wasn't hotplugging either.

what i mean with the 2 lunches, is one of them more performance based and the other more conservative based? They both are close in setups.

I'll be waiting for the update and let you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The nano- governors use an experimental new CPU load interface. The traditional interface uses 10 ms increments, where the new interface I threw together uses 1 ns increments (hint: 10 ms = 10,000,000 ns) at the expense of a certain amount of accuracy. Since freelunch measures load every 10 ms, I don't expect the old way to be terribly accurate. I'm hoping that the increased precision will allow governors to make more accurate frequency choices, which should make them both smoother and better for battery.

I just broke something. AssWax won't stop misbehaving. Derp.

Edit: AssWax is working, but mpdecision is still acting up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Thanks for the breakdown! nanolunch it is until asswax gets worked out. Thanks for the hard work again :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Nice update, however, asswax caused my phone to reboot. Not many things do that. Any kernel is usually rock solid. Going to try the vmin zip and try again.I'll also try to pull a log cat as soon as I can.

*edit*

Nope, it's broken for me. Gonna pull a logcat after I get out of work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
AssWax currently has a bug in it. I somehow managed to miss it despite running AssWax for two solid days. I'm working on a new test build to fix the reboot and get hotplugging working for interactive and AssWax.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Tried freelunch...good battery but laggy and was getting "system stopped/wait or ok" errors on boot. Have switched ROMs, tried newest stable dkp build and nanolunch works well with good battery numbers and no lag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Strange. I've never run into errors like that. I suspect I know what's causing it, but it might take me a bit to get it fixed.

The new build has the CM driver commit, so you'll need to get your ROM dev to merge it in before flashing dkp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
No need. I commented out some pretty important code when I was modifying it to work on 3.4 and forgot to uncomment it. Derp. I've already got itt fixed and I'll have new builds up once I get mpdecision to behave.

What happens if you flash this?

Soon! Everything seems to be working except that mpdecision is fussy and there's no source available to see why it's not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Who is supposed to flash that? You quoted yourself ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Derp. I'm trying to juggle all my threads and fix a handful of bugs I missed. I guess I'm not doing so well. :p

Anyway, I'm curious to see whether it stops the error message that [MENTION=4709601]eduardo_b[/MENTION] is seeing. If it does, then I know what the issue is, and I'll get to work on a fix for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
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.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Have you considered using an alternative to mpdecision? A few other kernels use the thalamus hotplug driver and it seems to work really well. Admittedly, I know nothing about the code behind either one of these, but I figured I would ask.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Can't wait to try it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Trickster Mod says mpdecision is off. You want me to flash this zip anyway? Permanent, unitl reboot, until flashing kernel,...?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I haven't really considered it, but it's definitely a possibility. I know ktoonsez uses it, and it sounds like it's been stable and efficient for his users. I suppose I should consider adding it. The only problem I'm running into is that I don't know how to write Android apps, so there's not an easy way to configure the new settings I'm adding. Flashable zips work, but having to reboot into recovery to try new kernel settings is a bit absurd.

Nope. I assumed mpdecision was causing the problem, but if it's not running then disabling it won't help any. If you don't mind, can you PM me a logcat? It'd help track down what's causing it.

Edit: It's permanent until flashing a new ROM, but I also have a zip to re-enable it...in case you were curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Getting great battery life with nanolunch (with row) on both cores -- averaging 0.75% per hour, no lag, no flickering on Slim's latest. I do toggle off data, bt and wifi much of the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
still don't see them :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
For some reason Dev-Host didn't set them to be publicly accessible when I uploaded them. They're fixed now.

So much derp today. :(
[AT&T, Rogers, Bell, Telus 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

By design, tierservative is much less aggressive than e.g. interactive when it comes to increasing frequency. That occasionally makes it noticeably less responsive, but it also avoids using excessively high CPU frequencies.

I've got a CDMA device, so all the GSM-specific stuff is foreign to me. There's some curious things happening, but I'm not sure how much of it is significant. I'll keep looking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsilx:
Thanks

Wanted to say thanks I was tired of randomly having to go into recovery to reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Not a big deal but one q, I haven't updated to the latest update yet (will do tomorrow) but under clock won't stick on reboot. Everything else will and my voltages stay put but it clocks at 380 (or whatever stock) and 1577 (I oc to that, its snappy enough for me already)

Just wondering about that, I recently bought 2 new batteries (both are straight up garbage) and I swap out quite a bit.

Since I'm thinking of it now, anyone have battery suggestions? Seriously one came from eBay (and I now have two of those and they both charge to 89-94% because they are 3.7 volt batteries, exact replacement my @$$.

And one from amazon. Garbage yo. If you know something feel free to send a pm.thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
I've noticed this with both the 5/02 build and the latest build. After installing the kernel the Play/Pause button on my headphones no longer works, but the inline microphone is still functional. Anyone else experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I don't think you were alone. ;)

The kernel itself doesn't save any settings. It's up to the app to re-apply your settings on boot. It's possible but unlikely that the app is colliding with changing the performance profile during boot. More likely is that it's just not correctly applying the setting. What app are you using, anyway?

As for batteries, either pay out the nose for a battery direct from Samsung, or go back in time to 2013 when decent aftermarket batteries were still available. :( EDIT: Wait a minute, Anker still sells S3 batteries, and for cheap, too! :D

The only headphones I have with playback controls are the ones that came with the phone, and they're working fine for me. Can you provide some more details?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Internet:
Was going to PM, but I figured this may be useful to others...

After my OEM and 2 aftermarket batteries (Onite) all expanded from the heat on the beach when I was in Hawaii last year, I ended up buying a 2-pack of Anker 2200 mAh batteries with charger from eBay for $26 shipped. That was this past December. They are NFC enabled and are excellent in my opinion. I just recently got a G3 and will be looking to see of Anker makes them for this phone as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Kinda figured that. IMA go out on a long limb and get a big ole batry and see what it do. Thanks.

I'm using trickstermod. It applies all other changes on boot. I'm gunna be in WiFi later and update cm12 and your kernel. I didn't download or install the XXX.zip from the op. Is all that needed?

Sorry bout all the questions. Been doing this for a long time and still don't really know much but the basics.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
[MENTION=4932679]decimalman[/MENTION] and [MENTION=4478916]manfromgta[/MENTION] :

I've been going about finding what's up with that signal drop and I might have found a way of stopping it (not a solution,but a workaround). Long story short,I believe that the issue is not being widely reported because it might just be happening to people that have poor or inconsistent LTE signal. I've changed my preferred network type from LTE to 2G and haven't seen one single drop since then. It might be too soon to tell,but it might be related to the switching from LTE/3G/2G that makes the signal drop instead of the transitioning it without drop?..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
It seems to only affect my V-MODA 1-button Android cable. I got home and tested it with a Skullcandy 3-button Apple cable and it works. This is odd since the V-MODA cable works with stock TouchWiz and stock CM12.1 kernels. I guess this explains why the same cable doesn't work with my FiiO X1 digial audio player. Is there any way I can even send a log for this? And thanks for all the hard work! This audio cable thing is the only problem keeping me from running dkp as my DD.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
If you're thinking about one of those massive 7200 mAh extended batteries, people used to rave about them.

Weird, Trickster is usually pretty solid. I'll play with it a bit.

The vmin zip does basically the same thing as disabling the "Override Minimum Voltage" setting in Trickster or Kernel Adiutor, so you don't really need it. dkp's UV interface is very different from anything else, so whatever you're used to doesn't apply here. :)

You've pretty much hit the limit of my knowledge of cellular networks. It seems like something is handling your carrier's network configuration incorrectly, and your phone is switching to a (3G?) network that it shouldn't be using. Unfortunately, I have absolutely no idea what to do about that. :(

Does this build work any better?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
It's a common problem in all lollipop roms, I don't know why people are asking you about it. Kernel's usually have nothing to do with the modem other than passing info along.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
He mentioned it and it got me curious. I reserve the right to go off-topic in my threads sometimes. :p

BTW, thanks for helping people out in my threads. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
A whole new build just for me? You shouldn't have! I'll let you know tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Lol sure thing, I feel like a kid at Christmas every time you put up a new build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Just flashed the new build and, damn it sir, you nailed it. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
That's cause [MENTION=4932679]decimalman[/MENTION] is the shizznit;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So I've noticed that I keep getting worse battery life with dkp kernels lately than I do with the stock CM12.1 kernels. I definitely get better performance with dkp (even on all default settings), but for whatever reason my battery always ends up draining faster.

When I look in apps like Wakelock Detector while running dkp it doesn't show anything keeping the phone awake. I'm really at a loss here.

I'm not looking to have anyone help me diagnose this, I'm just genuinely curious if anyone else has experienced this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
http://xdaforums.com/showpost.php?p=60651252&postcount=1734

See if that fixes your problem. I find that it's usually a wash between stock and dkp, but I haven't played around with tierservative yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Sounds like that issue is ROM-related, though. If that's the case, it should happen with both stock kernel and dkp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
That issue happens with me on stock kernel too. Happens very sporadically however, so it could be a false positive with the dkp kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwmike:
LTE on ATT I747

[

[MENTION=4932679]decimalman[/MENTION] you are correct. It is not kernel related. Devs are aware of the bug and working to correct it. Some have success with flashing latest modem while others click between 2g,3g, 4g and it sticks. Still others delete all apns except their own. What is difficult on the d2 variants in particular is peeps flashing from one variant to another which also makes it tough to pinpoint. We'll get it eventually. Cheers! :)

There has been a temporary workaround found which goes like this. (cant find original post)

1. Set LTE in Preferred network type in settings/mobile network settings.

2. Go to dialer and enter *#*#4636#*#* . This will open a screen which has various hardware info. Select phone info. Scroll down to Set preferred network type:

Choose: LTE/GSM auto (PRL). Back out to home screen. This works 90% of the time for me. If it doesnt stick do it again.

General comments: a) Going to 2g is ok, however thats like going back to a 2400bps modem. Better to let the phone cycle 3g,H,H+ speeds if you cant get LTE to stick.

b) This is a carrier problem. I have two I747s originally from ATT both running nj1 modem, dkp, pacman5.1. One is still on ATT (contract over in July) and has the LTE not sticking problem. The second has been

changed from ATT to Cricket (which ATT owns and which uses ATTs network) and never loses LTE. In fact I have never set it at all, its always LTE unless there is no LTE tower available.

Hope this helps!

Best :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4294847]kwmike[/MENTION], same here! I own 2 Original At&t 16gb s3's both on NJ1. I use a Straighttalk so in both & LTE is always on. [MENTION=4932679]decimalman[/MENTION] latest dkp build is ballz to the wallz with OctOs 5.1.1! Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So I've been switching back and forth between stock CM12.1 kernel and dkp for the last four days or so, and I can say beyond a shadow of a doubt that my phone isn't idling/sleeping properly while running dkp. Problem is, nothing really stands out in BBS or Wakelock Detector. I just know that when I use dkp with these official builds my battery drains roughly 3-4 times faster while idling than it does on stock, and I have done this loose testing in the exact same conditions and usage patterns each time. In fact, if I use dkp for half of the day and then switch back to stock halfway through my battery life, you'll see the Awake bar on the normal battery stats screen start to become much less concentrated from the point where I switched back to stock onward.

I'm sad to say that I have no clues as to why this is happening as of yet, but at this point I am 100% convinced that it's not a false-positive. The last time dkp had better battery life than the stock kernel for me was the last build that decimalman pushed out before CM12.1 went "official." Not sure if there was a change made after that that is causing this idle drain.

I've also noticed that everything runs almost too smooth when using dkp as well. It's like all apps are running at full 60fps with no dips ever, which to me would have to mean that my CPU is running at max clock more often than it does on the stock kernel. Using stock everything is pretty smooth but with the occasional minor frame skips that you'd expect from our hardware. At first I just thought it was some kind of miraculous performance boost without the expense of battery life, but then after I noticed the drain I started to wonder if they were related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Are you using default settings on dkp? If you have the inclination, try changing governors and see if that solves the problem. At least that will narrow it down to a governor if it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I have been trying an assortment of governors to see if any of them made a difference, but so far there's no change. I've used tierservative, Intellidemand, and Asswax primarily. I also tend to use Zen scheduler if I change that setting. I never mess with voltages or anything fancy like that either. Just governor/scheduler selection.

I used all default dkp settings for my recent four-day comparison against the stock kernel, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Not a problem. :) I vaguely remembered a change to the detection routines for the playback controls, and figured that'd be the likeliest cause.

I'll revert the change, so future builds will continue to work.

Excellent. I didn't expect to be the one to figure it out, so I'm glad to hear that the real devs know about it. :)

This is the post I've been waiting for. You're not the only one to report worse battery life with dkp, but I've mostly written off the reports as 5.1 instability. Documenting that you've compared dkp to stock, and that there is a visible, measurable difference in their behavior makes it obvious that there's an issue, helps narrow down what it is, and makes it much easier to fix. Thanks! :highfive:

It sounds like the issue is that you get tons of spurious wakeups while running dkp. I'm running 5.1 for the day to see what pops up in the logs, and I'll see what I can do about it.

CPU governors shouldn't ever interfere with standby (and if they did, it would result in lots of very serious bugs). Regarding the unusual performance, it's possible that governors are being a little bit generous with CPU frequency, but the only battery-related side effect would be slightly increased power consumption while the processor is already powered on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
If it helps, I think that the 04/27 dkp build was the last one that had equal-or-better battery life than the stock kernel, judging by this old post of mine:

Every time I've tried a build since then I've noticed the increased concentration of wakelocks as compared to what I get in the stock kernel. I hope that helps. :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
I've been having amazing battery life using dkp with both the CM12.1 5/11 Nightly and with PAC-ROM 5/11 build. I'm running SIO and Tierservative with an aftermarket 2300mAh Onite battery which I purchased 3 1/2 months ago and have Wake Up, Keep Awake and Auto-Start turned off under Google Play Services in Privacy Guard. Other things that might affect battery life that I would like to note are that I'm using a live wallpaper, Material Design Live Wallpaper, and the Viper4Android Super Audio Quality driver.

On the CM12.1 Nightly running about 50/50 LTE and WiFi I got over 8 hours of moderate usage with 23% battery to spare. Screen-on time was maybe a little over an hour with 2 1/2-3 hours devoted to music playback with Viper4Android enabled.

The PAC-ROM 5/11 build I haven't street tested yet, but it idled on WiFi for 12 hours and the battery dropped 14% overnight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
****ING FANTASTIC!!! FINALLY! An up to date custom kernel for d2att I love you man! Okay nevermind fiops is there awesome, one feature away from being fully loaded besides optimizations if when possible, double tap to wake.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I added DT2W and S2W to a build a while back, but decided they didn't work well enough to keep around. Since our touchscreen doesn't handle DT2W/S2W internally, it has to wake up the CPU in order to handle it. Waking the CPU takes a while and makes the gestures finicky and unpredictable. :( I still play with the code now and then, so maybe I'll get it working someday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
Interesting, good to know, regardless the performance is wonderful with this kernel and has every feature imaginable, final clocks benching with Antutu was 324mhz min 1.674ghz<--1225mv max gpu clocks 480mhz. Not a very good overclocker but it's something, and on the smoothness of 5.1.1. Only thing left to wait for is Xposed and more optimizations. Bang up job!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
[MENTION=4932679]decimalman[/MENTION] So I've been running stock cm12.1 (latest nightly) and I noticed the same things that [MENTION=4570464]ScOULaris[/MENTION] did with idle times. Same amount of wakelocks and awake times but for whatever reason CM kernel dropped only 6% overnight while dkp dropped 15-20%. Not sure what's going on and sorry I can't be of more help. SOT time seems about the same with DKP coming in a tad higher with battery usage. CM has tweaked kernel settings for interactive on their latest nightly though, with go_hispeedload set to 810mhz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Dkp: 5/17 nightly will most likely break compatibility with kernels not compiled against the same userspace, fyi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
I'm running the 5/17 nightly with dkp and everything seems to be running smoothly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I'm on nightly 5/23 and is working perfect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Which version of dkp?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
We are on official CM12.1 nightly, so we are running dkp 5.1.x and I'm personally on the 5/08 build.

Sent from my Lollipopped Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
The 5/9 version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
dkp 5.1 working flawlessly with Cyanide L. Good work done OP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
dkp has fallen pretty far behind CM, so it's time for a new build. Unfortunately, I still haven't tracked down the battery drain issue that's been affecting some people. :( Since nothing has changed for 4.4, I'm only doing a 5.1 build.

Changelog:

Synced with CM: lots of cleanups, fixes and optimizations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
latest booted successfully on Cyanide L, so far so good, still rock solid and zero issue. This time running on 600mv minimum voltage. thumbs up [MENTION=4932679]decimalman[/MENTION]