yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I had the same thing last night. Glad youve found a solution; you can try Greenify and see if it helps you find your problem:

Slept like a baby in a matter of seconds after I shut off the screen and set slacker to hibernate.

I've got some ideas as to what it might be but I want to try getting some sched stats to see if I can get a better idea before I start blaming things lol. I'll do what I can to keep you posted, but if you don't mind, I would also like to see what wakelocks you have (if any) on greenify.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
How to get the best battery with this kernel. Ant preferred settings?
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
Version running great on my ATT S3. Looking forward to the next update :)
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
I really don't like asking but this is the only kernel that gave me awesome battery life. Is it still be updated?
[T-Mobile, Samsung Galaxy SIII] matrixzone:
+1

Next update based on cm stable if possible would be awesome
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Sorry folks, I was (and still am, somewhat) on a bit of a hiatus from android development and the XDA Community. Part of me felt like I learned too much in too little time (I released my first source-built rom on April of last year [with no prior experience] to give you an idea as to how long I've been taking development [somewhat] seriously) and the latter was due to me being sick of certain ideals that were condoned in parts of the XDA forums.

I plan on continuing development soon, but I've aso got a bit of cleaning to do with the current source (locally). After that, I will see to reviewing and merging in CM's changes.

I'm hoping to get back to everything sooner rather than later. :good:
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Thanks for the update. Take your own time :p at the same time waiting for the next release :good:
[T-Mobile, Samsung Galaxy SIII] lostboykev:
Great job on this kernel. My 3DMark score overall has jumped up by 200 points. Lock screen wakeup is much quicker, fluidness in launcher. Less misc errors and artifacts. I have the 6/7 version. Please keep it going! This has been the only kernel to satisfy my battery, performance and stability requirements.

Do you have a way to donate for your efforts?
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Paypal id is mentioned in his profile:thumbup:
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I thought I'd leave a little test kernel here for ya.

I haven't run it for very long; and due to my lack of sleep all this last week, I am just not feeling like weeding out a changelog :/ (esp. since I rebased onto CM, with some parts removed). Though, I'll try and get one for everyone either later tonight or early tomorrow. In the meantime I just kinda quickly came up with a small list of changes:

- rebase about 90% onto cm-10.1 (to try rooting out a buggy commit)

- merge edft branch from sched-deadline (edf adjustments to rt)

- updates to ondemand

- include zen-tuning for interactivity

- more (full changelog to be posted soon, view source in the meantime to review changes)

***TO-DO***

- tune auto-hotplug, ondemand, maybe more

- re-add SLQB (?) [req. further testing]​

And I've also rebased my (important) topic branches onto cm, so anyone using the d2 kernel as a base for their kernel can (somewhat) easily merge in sched-dl and misc changes. Might run into a few merge conflicts when combining topic branches... but those conflicts aren't anything major (and my jb-mr1 source can be used as a reference)

Download: http://d-h.st/SuV

Source [again] (for anyone interested): https://github.com/SyNtheticNightmar3/android_kernel_samsung_d2

Enjoy. Have an awesome weekend folks. Mine is going to be spent trying to catch up on sleep :p
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
My God I just googed. Thanks!
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
Just want to say newest version running great on my att s3 running slim. Quick and great battery. :)
[T-Mobile, Samsung Galaxy SIII] matrixzone:
What will be the best settings(gov,scheduler) for getting the max battery?
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
This will be different for every device. There is no universal settings. As for me, I flash it and go. I don't touch it.
[T-Mobile, Samsung Galaxy SIII] lostboykev:
Just flashed your test kernel. Nothing to report yet. User experience is still the same. I will test is out for a few days as report back. Nothing technical just my everyday experience with it and problems.
[T-Mobile, Samsung Galaxy SIII] kiden:
Thank you! Going to flash this now and I'll report back how it runs over the weekend. :)
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
lol :highfive:

I've been messing with ondemand recently and have created a powerHAL to work along with it; which controls powersave bias between screen on and off (battery life has shown some improvement with little impact on performance; mainly in benchmarking, but I only care so much about benchmarks). I'll post a zip for that whenever I get another build out.

Works for me, since most of it was just a rebase onto CM anyway. So long as nothing is broken.

Oh and here is that changelog I never came up with :( ...

- Merge branch 'rebase-onto-edft' into jb-mr1 [earliest deadline first adjustments for sched-rt]

- cpufreq: ondemand: Disable freq sync feature in store_powersave_bias

- cpufreq: ondemand: Fix locking issue in store_powersave_bias

- cpufreq: ondemand: change freq sync code to use per-CPU kthreads

- msm: Synchronize CPU frequency on thread migration

- zen-tune: Implement zen-tune ([more] simplified version)

*VM dirty ratio: 50

*VM dirty background ratio: 20

*Ondemand downsample factor: 10

*Scheduling latency: 3 ms

*Minimal granularity: 0.3 ms

*Wakeup granularity: 0.5 ms

*CPU migration cost: 0.25 ms

*Bandwidth slice size: 3 ms

- arm: compressed: define CPU architecture

- mm: removed SLQB

- auto_hotplug: remove some tunings

- remove some -rt patches​
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I know it's been a while since I posted a release (after the test) but thats only because I wanted to make sure everything was in tip-top shape and with the amount of adjustments made between then and now, I wanted to have something that was working nicely before releasing. I don't want to say I'll do nightlies, weeklies or even monthlies, due to the fact that I try testing things as intensively as I can and because kernels can take some time before they "settle." But I do want to try releasing more often.

As stated, I've pulled in and made a couple of changes since the test, and there are a few I wanted to touch on and possibly ask your opinion about...

1. I have included the tripndroid iosched by TripNRaVeR. It's based on noop, deadline and vr and meant to have minimal overhead. I would like to know if it would be preferred in place of zen.

2. Harkness is now being compiled using -O2 with Sourcery CodeBench Lite's gcc-4.7.3 toolchain (compiles -O2 cleanly and at the speed of the gcc-4.8 toolchain I was testing out). I went with this one because a post by ezekeel some time ago debunking the effect of optimized toolchains in benchmarking, it seemed this one actually made somewhat of a difference. Though, I have also read that previous revisions of this toolchain can be buggy with neon if I remember right, so I'd like to see if there are any problems with this revision of the toolchain (but after a few days, I've yet to see anything wrong on my current rom).

3. Off this last charge cycle, I've gotten ~20.5 hours with about 5 hours and 16 minutes screen time (screenies at request; they're on my device). Which is something my d2tmo hasn't done before. At least not in recent memory. But that is not the point... I had forgotten to turn off proprietary mpdecision (and raise my auto_hotplug settings for testing), so I'm thinking it's working well enough to do away with auto_hotplug, but I'd like to know opinions on the current implimentation and how it works for you, any preferred settings and whatnot would also be appreciated; that way if it does stay, I can have an idea on some tunings that work (because I can't seem to find a satisfactory one).

Unfortunately, the ondemand/powerHAL combo will have to wait until I get to test some things, but this last cycle worked well with CM's defaults, but the good news is, I've gotten this source to compile with ZER0 warnings. :cool: remove-warnings branch has been added to OP if any dev is interested in getting rid of some useless common warnings on cm source.

Ack. Too many words for a forum post. I think that's the important stuff I wanted to cover lol.

Changelog: http://pastebin.com/xMvAXbmQ

07/24 Download: http://d-h.st/Pmr
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
I didn't even notice the new IOsched. I'll try it out today. I've been running it since yesterday with zero issues. Very smooth, very good battery life.

Just for a basis, I use the Carbon nightlies.
[T-Mobile, Samsung Galaxy SIII] neim81094:
My current kernel, let's hope the latest update fixed the bugs I have been seeing :D
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
Been running this now for 24 hours with the new IO sched. Gotta say, pretty nice. No noticeable battery drain and everything is smooth. :fingers-crossed:
[T-Mobile, Samsung Galaxy SIII] kiden:
So I totally forgot to report back. And now there is a new one! Been running it for a while and no issues yet! Thank you!
[T-Mobile, Samsung Galaxy SIII] Xx_silenzer_xX:
Downloading now :)
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
Hey Man, any plans to continue this once CM 10.2 comes along?
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I don't have any plans to discontinue this...at least for now. Just been busy with another project :) I may not release everything on XDA, but I do still consistently help existz co-maintain aokpx.
[T-Mobile, Samsung Galaxy SIII] ingram10:
I use this on my d2att and what can I say, very good battery life and I've tried pretty much every available kernel thank you
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I was able to make a quick build today and try out some cm-10.2. This update has all the recent kgsl updates so keep that in mind when trying this on your rom. I've been running it on the most recent cm nightly and it's been working fine so far. If you're running this, get some undesirable behaviour, and suspect it is because of the kernel, please include logging of some sort in your report. Thanks :)

Changes:

- merged in cm/cm-10.2

- merged in proxy exec structures from sched-dl V8

- reinclude -mtune flag for Cortex-A9 (showed steady performance increases overall)

- remove __cpuinit function (https://lkml.org/lkml/2013/5/20/589)

Also, I'm likely to stop supporting 4.2.2 in the very near future, because I already feel I have enough to maintain and after a while of focusing on Harkness, I broke inline kernel compilation with my rom (well I didn't break it, but it won't boot when compiled inline lol and last_kmsg's didn't point to anything directly), so I'm weeding that out in my mainline jb-mr2 branch while maintaining a jb-mr2-exp in parallel, at least until I can get a cleaner branch that is up to date with jb-mr2-exp.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
With the new CM11 builds being churned out, I decided to give the 12-08 nightly an install. I had also seen that Juri (jlelli) started up a branch for a new sched-dl ABI on the current Linux mainline kernel, so I decided to work on bringing that over and running my own kernel on top of things. I managed to get a full implementation of -deadline this time around so I thought I'd share.

This build doesn't have all the stuff from the prior version but a handful of things from the previous version(s) got merged this morning (still includes fauxsound, fast charge, off the top of my head).

I'll try getting something more formal out soon as well as redoing the OP with the proper details, etc.

Here's this morning's build if you want to try it out.

http://goo.im/devs/aokpx/Harkness-Kernel/Harkness-kernel-d2att-2013-12-09.zip

Source:

kitkat branch

new sched-dl branch
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
This is awesome :) loved your kernel. Going to give it a flash now and report back
[T-Mobile, Samsung Galaxy SIII] dieselford:
Is this compatible with 4.3 as well? Didn't know if all linux 3.4 builds could use it
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
The major factor in compatibility with older builds is the display drivers. I haven't looked at what all changed in that aspect between cm11 and the last cm10.x build, but it might work if its recent. If thats the case, you can try giving it a shot and see how it goes. If it doesn't work, you could always simply reflash your kernel or dirty flash your ROM's zip to restore the stock kernel.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Good news, after long time :good:
[T-Mobile, Samsung Galaxy SIII] dieselford:
I would imagine it would be okay then. BMS is compatible with both and I'm sure any others should be as long as they are synced after CM's graphic driver change from a month or so ago. Thanks for the info
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
The update is official. Uploaded my build for this morning, updated the OP, now for a changelog:

- Started over w/ recent CM kernel as a base (includes recent merges from Kernel.org and CodeAurora)

- Fully implemented shed-deadline's new ABI

- Updates to MSM's cpufreq driver from CAF

- Re-branded for axDev

- Re-stripped some modules

- Re-included FauxSound, VoltageControl, FastCharge, -O2/Cortex-A9 optimizations

- Re-implemented patches from TripNRaVeR, franciscofranco, Linux Mainline, ARM, imoseyon, faux123, and plenty more

(I also removed a commit from the last build that seemed to cause some problems with lowmemorykiller after some runtime)
​

I cut it short since, excluding the new sched-dl, there's a lot of the same (with a good bit removed) and as usual, you can check out github. Gonna try steering clear of a few things this time around, for the sake simplicity and not subtly breaking things.

Download - 12.10.2013:

GooManager

DevHost

Yeah. I had too much going on so I had to step back for a bit.
[T-Mobile, Samsung Galaxy SIII] Sajoeee:
going to try this with the new pa 4.0 on my d2att. need to check the gs3 tmo threads more often. (: thanks.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Normally, I wouldn't post an update after I just asked for status on power consumption without giving everyone a chance to do a good power cycle, but I woke up last night after a couple of hours of sleep and saw I was only up to 96% charge due to charging in low power mode on my stock charger. I think CM might have re-disabled power collapse in an attempt to fix it, but I went ahead and imported some updates to our battery driver from the Samsung 4.3 update just to be safe. So far, my device is charging the way it is meant to (and no low power mode traces from msm_otg yet either). Hopefully, we can get some more accurate results on how well Linaro's unbound wq's work after getting a good night's charge next power cycle.

12-16-13 Download:

goo.im

d-h.st

Not too many changes in this one:

- Merge in changes from CM (CAF merge, kernel.org merge, disable power collapse)

- Update Samsung battery driver
​

EDIT3: Made up my mind. It IS a bug. And I fixed it (this probably should have been done when CM did its apexq bring-up). Also, I've managed to port over dkp's cool new light features ("breathing" notification light & touchkey backlight animation/touchkey brightness control). This will all be in the next release.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Got an upload for today onto goo. I'll make the mirror to dev host soon... maybe. Files there normally end up going away though.

12-17-2013 Download:

goo.im

Changelog:

- Ported over dkp's awesome LED "breathing" notification & touchkey backlight animations (fixes and all)

- Got rid of OTG checking for charging status (gets rid of OTG low power mode when plugged into charger)

- Picked a fix-up to remove the stupid vdd min causing voltages to not properly set to voltage tables (faux123)

- Linaro cpu topology modifications for Cortex-A9 & enable arch dependent cpu power functions for sched

- cpu policy matching improvements from LeanKernel

- Inline some functions for acpuclock-krait (stratosk)

- Revert a change to interactive, causing it to stick at sync_freq on occasion (kt)

- smp patches from 3.5 (motley)

- Clean up some cflag optimizations
[T-Mobile, Samsung Galaxy SIII] OffDatGoGo:
I am about to download this right now. Never mind my sig, I'm currently running LiquidSmooth 2.10 & stock kernel with no other mods. I'll let ya know how it goes after flashing. Thanks for the kernel [MENTION=3875215]Synthetic.Nightmare[/MENTION].

UPDATE: Guess I have to flash a different ROM b/c this version of LS doesn't like any kernel upgrades. Ugh!

DEVICE: SGH-T999 + ROM: LiquidSmooth v2.37 + KERNEL: KT747 + MODS: TKMOD 2.4 = A FREAKIN' BEAST!
[T-Mobile, Samsung Galaxy SIII] jukiewalsh:
Can you confirm this working on D2att? I get nothing but bootloops after flashing over both clean cm11 and quantum

Edit: sometimes it will go as far as a black screen and say systemui has stopped
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Friday morning build...

Added a bit more to the OP

12/20/2013 Downloads:

goo.im

d-h.st

Changelog:

- More uses for power_efficient workqueues [pe_wq]

(Linaro pushed some updates using pe_wq in different areas)

- A couple of sched updates from Linaro

(a couple of things that should help pe_wq work better on dual cores)

- Implement less deprecated Linaro topology implementation with cpupower driver

(the last implementation used a generalized freq table, this one includes a platform-specific config & dual-core specific driver)

- Import semaphore-n4's ondemand cpufreq driver

(cleaned up of a lot of PowerHAL-reliant stuff & tweaked by stratosk w/ input tunables, see OP)

- Set sched_mc_power_savings to 2 by default

(to take advantage of cpu_power driver)

- Merge in cm-11.0

(smart dock changes)

- Increase max readahead to 1024

- Optimize for Cortex-A15 & neon-vfpv4

​

Strange.

It should work on d2att as long as it's a recent build. The config is set to build for d2att to begin with.

Hard to tell for sure without logs though.
[T-Mobile, Samsung Galaxy SIII] jukiewalsh:
[/QUOTE]

Strange.

It should work on d2att as long as it's a recent build. The config is set to build for d2att to begin with.

Hard to tell for sure without logs though.[/QUOTE]

I would post one but to my knowledge you can't logcat during boot can you?
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
No but if you install the kernel, let it boot up/fail, then right after go into recovery and flash a working backup kernel afterwards, you might be able to catch a last_kmsg [last kernel message] (only thing a logcat might do is tell me whether or not its your ROM thats the problem... And that depends on how far it boots). I use an app called SysLog for quick and easy access to any type of log if you want to try that out and not have to take logs manually.

Also I was almost certain there were a couple of people on d2att that were using this at some point and might still check in. Hopefully they can provide some feedback as well.

If all else fails my gf has a d2att, but she's still running one of my old jelly bean builds on it. Once she gets back home from out of town, I can try setting her up on a kitkat build for some tests.
[T-Mobile, Samsung Galaxy SIII] jukiewalsh:
https://docs.google.com/file/d/0B_eFS8Sv1_BBbUVBZnBvVkNzcHc/edit?usp=docslist_api

edit: nevermind I messed it up i think
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Ah okay. Don't mind the request then lol. I had a minute to spare so I was gonna look into it really quick. You can also copy and paste the contents to pastebin and post the URL. I'd understand if you don't want to be booting over and over though.
[T-Mobile, Samsung Galaxy SIII] jukiewalsh:
I'm at work now I'll try it again later when I get home and send a pm. All that was in this one said "main grepped for"
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Sounds good. Also, next time you take a log, don't mess with the grep stuff, that's only if you want to search the logs for a certain word or phrase. Just check the log you want and hit the button.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Happy Holidays!

Unless one of my remotes pushes any major updates, this could be it until the holiday season is over.

Enjoy.

12/23/2013 Downloads:

GooManager

Dev-Host

Changelog:

- Update toolchain to Sourcery CodeBench Lite GCC-4.8.1 EABI

- Optimize for size again (-Os) (-O2 wasn't working so well with CM's current code & gcc-4.8 )

- Updates to ROW from CAF (mainly wanted to clear up some warnings)

- mpdecision: Increase hotplug delay to 2 seconds

- Ondemand: Hack to disable hotplugging while accounting for touch_load (because we don't always need that big of a boost)

- Get rid of cpufreq sibling policy sharing

- Update touchkey backlight animation stuff to dkp-4.4

- Updates to lowmemorykiller from msm-3.10 (6e567541)
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Thanks for the updates. Happy holidays and merry Christmas..
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Finally got around to installing kitkat on my gf's d2att and had the same problem on a clean install [MENTION=5441030]jukiewalsh[/MENTION].

I had to install my rom and gapps first, let it boot, then reboot and install the kernel. CM11 on our devices is buggy on init and I'm thinking that may just be a part of it. Afterwards, it worked as expected.

So now that I have 2 devices to test on with varying usecases, I can find out about things I broke sooner.

And while out of town, I found out my commit for touch_load caused some deep sleep trouble (on occasion, it would get cpu0 as offline and set it that way while the ondemand driver checked the cpu). So I've got a quick update that will likely fix the issue:

12-27-2013 Downloads:

goo.im

dev-host

Changelog:

- ondemand: only account for touch_load when cpu0 is online

- Update led touchkey animation to current dkp-4.4 (just because I was here doing things already)
[T-Mobile, Samsung Galaxy SIII] jukiewalsh:
[MENTION=3875215]Synthetic.Nightmare[/MENTION] Okay I'll give that a shot right now. Thanks!
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Found a few more rough edges to iron out (before I find/make more lol)

One more before the new year...

12/29/2013 Downloads:

GooManager

Dev-Host

Changelog:

- sec_battery: Do not update UI for soc at 100% (Woke up to my charging LED sticking at full charge when unplugged)

- drivers: power: Updates from 4.3 source drop (Because overnight charging hasn't been doing as well as I feel it should; 2ea42d4)

- ondemand: simplify when to account for touch load (gets rid of using lame get/set_online_cpus function; which was causing problems on wake/sleep)

- sched/rt: add missing rmb() (adds missing memory barrier read function; also changes [w/r]mb to use smp)

[Let me know if this helps that initial drain after charging overnight at all]
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
Not getting deep sleep on this one