yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Did you use an app to adjust tunables without resetting mpdecision afterwards? Also check your apps with greenify and let me know if there's anything there with a lot of background run time. I know slacker for sure is a real resource hog after a couple runs without watching it (I've experienced deep sleep issues with this app in particular both on harkness and cm). If anythings causing deep sleep issues, its not ondemand (or at least it shouldn't be). The change I made got rid of my last changes and simply adds an "if" block around the touch load stuff, only allowing it to boost when cpu1 is offline (since once cpu1 is online, ondemand can do some load balancing). More details would be appreciated though.

EDIT: all things considered though, harkness does seem a bit more sensitive to apps like this and I might know why. Would you mind testing something for me later?
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Tapatalkd...

Edit.While I'm here, happy new year everyone. Starting off the year with yet another overhaul of harkness (this time with tons of scheduler updates from linaro; my goal is to keep us as close to linaro's sched branch as I can. To do that properly, I'm going to start at the root.) Note; branches WILL be rebased. Test vigorously if using any source.
[T-Mobile, Samsung Galaxy SIII] _-..zKiLLA..-_:
Sweeeeeeeet
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Keep it coming.. Awesome
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I've got most of what I wanted merged in without breaking sched_mc_power_savings and after a bit of testing, nothing else seems to be broken, so it feels like a good time to drop a release. Changelog below is

extremely

shortened. The initial sched/topology imports start on page 7[github] if you want details.

For now, I'm building off of this branch, until I get things finalized (axdev-2014-review)

Downloads:

GooManager

d-h.st (so many ads nowadays; considering going to googlecode for main downloads [and support] w/ goo.im for mirrors)

Changelog:

- Started off clean on cm-11.0 (only new thing there was a warning fix for interactive)

- Sched/topology/cpuidle: Tons of patches from kernel.org/linux-linaro-sched (enough to get us as inline to linaro's sched branch as I could without screwing up sched_mc_power_savings)

- Sched: Updates from said sched branch (patches for differentiating idle cpu's using latency)

- Implement zen-tuning v3 (Modified to be a bit more relaxed on CFS, rather than really aggressive)

- No longer included (for the time being at least: sched-dl, a whole lot of misc/deprecated scheduler/topology/vm patches, sec_battery/driver updates (will likely re-apply in parts) [I'll add more as I remember, feel free to remind me of anything if you notice it]

(I want to run our current sched implementation as-is before trying to bring over sched-dl)
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Need to post another update before I lose track of changes.

Should be finishing up with the review branch pretty soon before bringing it over to main.

I noticed the LoUIS stuff while browsing linaro and remembered seeing about it in the mako forums, but I don't think I saw it applied as much as it is in linaro. Due to naming inconsistencies, I'm not sure if I got all of them, but I'm pretty sure I got most of the ones that matter to us. Feedback would be appreciated as I try finishing up on my wip branch.

01/05/2014 - Downloads:

GooManager

Dev-Host

Changelog:

- sched: Split cputime code from core and update to lsk (linaro-stable-kernel)

- random: Updates from Kernel.org linux-3.13-rc7

- msm_rng: Add bus bandwidth support to PRNG & IOCTL support to disable the bus bandwidth (msm-3.10)

- sched: Updates from linux-3.13-rc7

- math64: Add mul_u64_u32_shr() (used in sched_fair time accounting rework)

- cpu/arm: introduce and use clear_tasks_mm_cpumask() helper (helper function that properly clears tasks' mm_cpumask)

- smp: add per-platform SMP operations & convert MSM(M2) to SMP ops

- mm: implement LoUIS (Level of Unification Inner Shareable) API for cache maintenance ops (includes patches to use API in various places)

- arm/clockevents: Add & use generic timer broadcast receiver/support

- ARM: smp: misc updates from lsk

- sched: core: set sched_mc_power_savings to 0 (not really needed anymore, fell free to adjust to your liking)

(NOTE: a lot of lsk stuff may very well be upsteam linux as well. lsk was just my ref.)

(github's got it all, as usual)
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Thanks for the update!! Just flashed the update on latest Slim Weekly, will share my experience tomorrow

Hope we have to keep the default settings and are not required to tweak any kernel settings.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I'm mainly looking for behavior; which should be about the same no matter the tuning. Though anything else you find, I'll look into as well. Things breaking that weren't broken before, etc. I can only test for so much with the minimal setup I run.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
I am happy with the performance of the phone after flashing the Kernel. No reboots, lags or any issues with the Kernel. Can't commit on the battery as of now because of the stupid "msm_otg" wakelock which got activated randomly after battery charging. Will report about battery tomorrow, if that wakelock does not get activated again.

Overall, will highly recommend the kernel for d2att users.

Suggestion: Please move this thread to the AT&T - d2att thread instead of the current T-Mobile section. Most of the d2att users are not aware of this wonderful kernel
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I booted up my latest build from USB and my d2 was still able to sleep on unplug. There weren't any changes to msm_otg specifically since that release and now. Could you get me a dmesg or try to give me an idea on how to replicate it?

And since my device (and the one I had before) is a T-Mobile device, I thought I'd post here; making it easier for those who enjoyed my previous works to find me. Beside the fact that I know of 2 d2att's that can't boot this properly on a clean install and no d2tmo, I can really only consistently test on my d2tmo. Though I do appreciate the thought and will consider it, since I can test d2att.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Sorry for any confusion, msm_otg wakelock happens with my phone randomly and is not related to your kernel. The wakelock generally happens after phone charging and reboot fixes the issue
[T-Mobile, Samsung Galaxy SIII] mr.denis:
Flashing now to give it a try! Thanks.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Beyond some sched tunings, I've been testing this recent implementation for a few days. So hopefully, it's stable enough to uphold the axdev-4.4 branch label.

01/14/2014 Downloads:

GooManager

Dev-Host

Changelog:

- Merged cm-11.0 (bcmdhd updates; ROM must have compatible changes for WiFi)

- smp: misc clean-ups/updates fom Kernel.org

- clocksource: Add generic dummy timer driver (decouples dummy timers from broadcast code/local timers)

- smp: Updated to include smpboot and all(?) self-parking CPU thread-related commits/fixes

- oom: Updates from Kernel.org

- hashtable: introduce (and use) a small and naive hashtable [workqueue, cgroups, ksm, block/elevator]

- fs/locks: Clean ups and fixes from Kernel.org [really only done in an attempt to use the hashtable here, but the API changed]

- cpufreq: initial cpu utilization should be 0 (stratosk)

- ksm: optimizations from ktoonsez (more pages per batch; more time between batches)

- iosched: Set Deadline to default & inherit Deadline tweaks from aospX

- readahead: Updates from Kernel.org

- rbtree: Updates from Kernel.org (lots of patches/optimizations/fixes to the rbtree [used by CFS; and others])

- PM/Sleep: Fixes from Kernel.org (also allows for freeze timeout to be modified [/sys/power/pm_freeze_timeout] DEFAULT = 10000

- mm/sched: Revert zen tune & implement AxDev HT (High-Throughput) Tuning (see Kconfig for details)

(Still a bit of a wip as I research/adjust for our devices)

- sched: Re-enable GENTLE_FAIR_SLEEPERS

More @ github
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
Flashed on d2att. Jesus is this smooth. Keeps getting better and better. Great job :thumbup:;)
[T-Mobile, Samsung Galaxy SIII] bosna110:
First of all before I get cranky, damn what an awesome kernel :) i'm not half of smart as you.

Now for the crankiness :P what is the best setup for the kernel when it is installed, voltage, gpu speed, gpu governor, cpu speed, cpu governor, and so on, i am curious about what others use to make it buttery smooth and fast without draining like 10% in like 20 minutes. Thanks to all :) once again thanks for one awesome kernel :) just awesome awesome awesome :D :D :D
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Lol with all those smilies its hard to tell where the crankiness begins and ends.

As far as battery life goes, harkness should be just about on par with cm in terms of screen on time. With the current sched adjustments, I got about 4 hours (a little more) with at least 16hrs usage throughout the day (_plenty_ of awake time due to playing or streaming music). And for settings, I usually just run stock unless I'm running ondemand, since it normally keeps the device a little cooler (sometimes I'll change the sampling tunables to caf's settings, too).

Long story short, it's been working for my usage but I can try changing a few things. It should all balance out a little better once you get some idle time mixed in.

Edit: you can also try enabling sched_mc_powersaving (easiest way is through tricksterMOD). I had it enabled before by default but it wasn't working too well with zen tuning and the way I had things before (at least for me and I hardly ever get enough feedback to adjust based on user input). I'm still trying to get my scheduler changes thoroughly tested, noted and finalized as I go but I wanted a release compatible with recent cm.
[T-Mobile, Samsung Galaxy SIII] bosna110:
I dont say it is crankiness. I am a mobile wireless sales rep, so I thought maybe to show off what an awesome kernel this is to help me boost sales and maybe donate 40% of my commission if you'd help me get this kernel going in beast mode
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I guess... That's not really my drive for doing this, though. Im going to try improving it regardless :p

Also just found out sched-dl hit mainline about a week ago with a handful of fixes. So I'm strongly considering bringing it back on top of our sched backports. :) Oh and I'm cleaning up my trees one last time because cm unified a whole lot of d2 stuff. Repo will be cleaned and reorganized by topic (meaning more branches, but this will make things easier to track and merge for everyone). Stay tuned.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Update! Lots more in-tree than in this condensed changelog.

I'm also going to change the title of this to reflect the d2 changes. While I can't test on other devices, the recent changes by CM SHOULD make this kernel compatible among all d2 variants, so feel free to try at your own discretion.

Thanks.

https://github.com/SyNtheticNightmar3/android_kernel_samsung_d2

01-23-2014 Downloads:

GooManager

Dev-Host

Changelog:

- Merge in CM (CAF update, fix for boot freezes, unified a lot of board specifics for d2)

- Sort, clean, & Rebase prior work on top of new CM HEAD

- Import some dkp fixes for touchkey backlight/notification LED

- Backport sched-dl & newer fixes from mainline

- Compress using lz4 (very fast compression/decompression; lower compression ratio than XZ)

- Set sysfs color panel to coolest colors by default (should help a bit w/ screen on battery drain)

All my current branches have been reorganized; so if you need to look up patchsets specific to a topic for whatever reason, this should def. be a lot of help.
[T-Mobile, Samsung Galaxy SIII] phoenix2217:
Everything working great so far on my end. Well done. :thumbup:
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Made a few minor, yet nifty changes that I thought were worth releasing.

01-26-2014 Downloads:

GooManager

Dev-Host

Changelog:

- Merge in CM (mainly just a small fix to sysctl)

- Modified GPIO debounce time for vol. keys (changed from 5ms to 12ms; reduces sensitivity for long volume key presses)

- Increased touchscreen sensitivity (tested on the game Dumb Ways to Die [a game with terrible multitouch] and gameplay was significantly improved since I last tried it; though I'd like to get more testing done on it, so I know it's not just me)

- Got rid of cpuidle latency patches (caused battery stats to in/decrease unnecessarily often)

- conservative: Imported some fixes/improvements from semaphore n4

- conservative: Use morfic's tuning for up/down threshold (so it's not so bad performance-wise... keep in mind, it's still conservative)
[T-Mobile, Samsung Galaxy SIII] poondog:
[MENTION=3875215]Synthetic.Nightmare[/MENTION]

I tried building my One kernel with your commits for LZ4, including in the defconfig

Spat out this error, Image compiled fine obviously

LZ4 arch/arm/boot/compressed/piggy.lz4
/bin/sh: 1: lz4c: not found
make[2]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2
make: *** Waiting for unfinished jobs....

Thanks
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
You need lz4 on your build machine.

I built and installed it manually from the ppa. You can try

sudo apt-get install liblz4-dev
[T-Mobile, Samsung Galaxy SIII] poondog:
Thanks, you mean build a lz4.o? I have it now, what do I do with it :D
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
No. To be exact you need the executable binary "lz4c" (as shown by your compile error). Your kernel may be capable of using different types of compression to build (in the source code), but you need a version of the actual compressor on your machine to compress your kernel image to that format. (Think of trying to compress a file to 7zip without having 7zip).
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Recently, I've seen a few of my branches used around other device forums, so I've created another repo for finalized work for this project; so it's a bit more clear to see what's experimental and what I have (sort of) finalized.

https://github.com/SyNtheticNightmar3/CM_Harkness_Kernel

Also, I've been using a really cool compile caching feature from MentorGraphic's awesome toolchain. I'll leave some notes on it in the OP soon for anyone interested. It's pretty freakin' sweet. Compile times on this slow laptop I use to build Harkness went from ~32 min to ~7 min (make mrproper && make -j4)

And I've seen a lot of reports on orientation stuff breaking after the board merge, so I just went ahead and imported the d2att values for that. GSM devices using that board should have orientation working. So I should probably go back to tagging this as tmo/att. Though I'd prefer to work with someone who would be able to help fine tune these values (for d2spr/vzw) and maybe find an optimal setting for all m2 devices.

[Scratch that. CM fixed this upstream it seems.]

Feel free to ask about any changes... there've been quite a few and I wouldn't be surprised if I lost track of some of them, myself.

02/18/2014 Downloads:

GooManager

DevHost

Changelog:

- Revert back to to CodeBench gcc-4.7 toolchain (-Os, cs compile cache)

- Removed idle and smp merges (I'll likely revisit the smp branch)

- Misc. clean ups (I thought some things the CM kernel had only pertained to Harkness)

[Note: I removed some module cleanups, so the kernel might be a little bigger, will revisit.]

- Merge in cm-11.0 (Updates to interactive, merge to linux-3.4.80, merge in some CAF, etc.)

- Merge in axdev/next-spinlock (Updates to spinlock & prefetchw support from mainline/caf-3.10)

- Merge in axdev/next-time (Updates to tick/nohz)

- Merge in axdev/generic-rwsem (asm-generic implementation of R/W semaphores)

- Re-merge axdev/next-oom (lmk/oom updates from mainline)

- sched: Merge in some patches from upstream I missed & from nvidia

- Fix mismatch in panel color shift sysfs

- board-m2: Clean-ups and set orientiation/charger pdata values to that of the att board

- input: touchscreen: Update d2_fw firmware & reduce touchscreen sensitivity some

- cpufreq: interactive: Stop boostpulse from doing the same thing twice

- m2-display: Increase panel bandwidth (based on m7)

- power: fuelgauge: Stop capacity from raising sporadically & use reset_cmd value from ML1

- acpuclock-krait: Updates from caf/msm-3.10

- anything I might have forgotten from github
[T-Mobile, Samsung Galaxy SIII] matrixzone:
The best kernel for aosp....
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Thanks for the kind words. :)

Meant to get an update together sooner, but I was out of town this weekend. And I ended up fooling around with some bcmdhd and mutex stuff last night, instead of releasing (like I planned to). It's run well for me so far, let me know how it goes in comparison to the last release (really anything to do with wifi, since I changed up a few things in the bcmdhd driver).

03/04/2014 Downloads:

GooManager

[mirror is WIP]

Changelog:

- Updated updater-script (with parts from anykernel and a bit of relevant fallout dialogue)

- Merged in cm/cm-11.0 (Reverts my compass sensor changes to the board for CM's, let me know how it works, I'll revert if I need to)

- Merged in axdev/next-mutex (update mutex spinners to use an MCS lock based implementation: 2758e25)

- Merged in updates from mainline to sched-dl

- Reverted dkp's bcmdhd driver kang & implemented a more stock-like bcmdhd driver (with mods from ezekeel & imoseyon)
[T-Mobile, Samsung Galaxy SIII] winga45:
Just tested that didnt work keep rebooting on 4.4
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
What ROM/version? I'm on last nights cm nightly and its working fine. No kernel updates to cm since.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
... okay, guess you resolved it.

Update time. I'll post some documentation on building using the mentioned script if desired (should be fairly simple).

03/14/14 Downloads-

GooManager

Dev-Host

Changelog:

- Merged in CM (caf update, 3.4.83, etc.)

- Re stripped some modules/debugging

- Re-merged axdev/next-smp (updates to SMP from upstream)

- Merged in axdev/next-rbtree (post-order iterations support)

- Merged in axdev/sched-dl (updates to sched-dl from mainline)

- Merged in axdev/next-sched (fix double normalization of vruntime)

- Re-do some optimizations [vfp&graphite] (more info)

- Added build script to source

- wireless: bcmdhd: Fix BCMDHD_WIFI_PM config for BCM4334

- Imports from Motorola's msm kernel source:

* always update vfp_current_hw_state when forcing reloading

* fixup to allow sched to play nice with CPU_HOTPLUG

* Krait memutils

* acpuclock-krait: init to max speed (improve boot time)

* lmk/compaction: updates to allow improved/stricter memory management
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Thanks for the update. .
[T-Mobile, Samsung Galaxy SIII] kingston73:
Thanks for this, all seems to be working well so far. Are there any issues or special instructions switching from this kernel to another, or flashing this kernel after using another?
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
Coming to Harkness, If the kernel used before replaces the ROM's boot.img, you may need to dirty flash your ROM again to get that one back (older ramdisks might not work too well on newer builds), but that shouldn't be necessary if the kernel's included ramdisk has been updated to be in sync with the one used in your ROM. This kernel might cause you terrible, similar problems as the one before if this were the case. Beyond that, there shouldn't be a problem going to/from Harkness that I can think of, since we flash the kernel (zImage) into the boot.img using anykernel.
[T-Mobile, Samsung Galaxy SIII] kingston73:
Thanks for the answer. I don't know why I never used this before, it's giving me some insane battery life and great performance, very smooth.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
I was told in the t999 cm11 thread that this kernel comes optimized out of the box and doesn't require configuration. Is this correct? If so, what are the advantages of this kernle over stock cm11 kernel? Are there any objective quantitative comparisons? Are there any reasons not to use this over stock cm11?
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
You can use it as you please. There's a good bit of info in the op and I try to keep it updated as I make key adjustments.

I dunno what else to tell you. This is just an exp kernel I like to work on, I try not to compare it to other works (unless bugs are involved) or worry about benchmarks, so I usually just test in realtime, as I run my device throughout the day and make it work the way I want it out of the box for myself.

This probably has similar advantages to using any other custom kernel. Although, I'm sure your results would be a lot more accurate to you, if you tested it on your device, rather than me tell you how it runs on mine.

Sorry if I didn't answer anything at all.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
i appreciate the feedback. i'm not exactly a developer.. just a modder. so a lot of the details are too technical for my understanding.. usually the correct answer to such questions is "try it and see" so perhaps i will
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I understand, but its hard enough for me to explain things like unbound workqueues to the average person without feeling I'm getting too technical. A lot of the stuff I normally strive for is scheduler improvements, and that part itself is quite intricate, alone. Feel me? Maybe I just suck at explaining things.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
ya that's understandable, sounds good!
[T-Mobile, Samsung Galaxy SIII] PhrostB:
So I installed the kernel and it seems to be running fine. Is there no interface app for it? (I actually prefer it with no customization if that's the case).
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I normally just run it with tricksterMOD for some tuning. Works well enough and exposes most of the goodies in sysfs.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
ok i'll try it... 60% after 3 hours... all because of mozilla stumbler...