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.
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