yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
Strange. The last two test builds shouldn't have any issues with this. I haven't had any freezes since I posted the 6/9 test builds. I'll flash LS tomorrow and try to track down the issue.

As for schedulers, I don't really have much preference. Go with whatever works for you (assuming you can get the kernel to boot anyway).
[Verizon Samsung Galaxy S III] Eyalkn:
It works for me but I always flash the vmin zip with it, try that and see if it solves your issue.
[Verizon Samsung Galaxy S III] Dearborn1977:
The vmin appears to be part of the kernel, at least there's a vmin init.d script placed in my init.d folder whenever I flash dkp. Is there something else you're referring to?
[Verizon Samsung Galaxy S III] trvbone:
Newest test build running great with your suggested interactive row settings
[Verizon Samsung Galaxy S III] Eyalkn:
Maybe he already implemented it in the new test kernel. There is a Vmin zip in the OP.
[Verizon Samsung Galaxy S III] pocii29:
[MENTION=2757884]decimal[/MENTION]

Is there any way you could provide me with documentation on what exactly some of the governor adjustments mean? Like hi speed freq. Sample freq. The whole shabang. Thanks!

Also a quick report on this nanolunch munchies... The balance on this is incredible guys. When I'm on the phone, it's full force performance and not any stuttering. But when it's in deep sleep it's not even dropping a percentage.. Absolutely beautiful. Wish I could post you guys stats, but I'm not even half way through a charge :)
[Verizon Samsung Galaxy S III] trvbone:
There's a governor scheduler thread on XDA that is very informative try search for that otherwise I'll try and dig up the link here you go

http://xdaforums.com/showthread.php?t=2017715

[GUIDE] Android Governors Explained [Update 1/13/2013]
[Verizon Samsung Galaxy S III] decimalman:
The zip actually removes the initscript. The script is responsible for reducing the minimum voltage below the stock setting. I'm actually considering removing the script and requiring trickster instead.

In the works. There's a lot of extras that really need to be documented. The information in other threads is still correct, but it'll be missing lots of dkp stuff.

Sounds like you might just make it to the weekend.
[Verizon Samsung Galaxy S III] masri1987:
I flashed the vmn file with the kernel and still doesn't boot. Ah, I want nano lunch munchies dam it
[Verizon Samsung Galaxy S III] pocii29:
I have an idea about the actual governors. But what I'm curious about is the actual tweaks inside trickster mod
[Verizon Samsung Galaxy S III] masri1987:
Got it working, had bad download.

One request, can you add 189 and 135 mhz slots?
[Verizon Samsung Galaxy S III] decimalman:
Glad to hear you got it working.

You've previously made this same request, and I replied with a quote from a previous post in this thread explaining why I didn't include such steps. I've been meaning to do some testing with Trepn, but until I have actual measurements on this, I stand by my previous remarks.

Developers get no real-world reward for their time and effort (except the occasional donation), so the only reward that we can expect is for users to express appreciation for our donated time. Asking questions that have previously been answered several times sends the message that you don't value the developer's time. I appreciate your interest in my work and I welcome feedback, but posts like this are the reason so many developers on XDA have bad attitudes and complain about users not searching.
[Verizon Samsung Galaxy S III] trvbone:
I was going to post that the freq steps requested has been addressed already but my signal at work of horrible so I couldn't back you up decimal. But as always great work the latest test build seems to be your best build yet! Very pleased! Whenever someone asks about a good kernel you're my first suggestion! Kt747 is great but it gets weird and bogged down at times I'm not sure what's up but my memory usage always send super high on stock RootBox kernel (cm based) and on kt747. I gave up on lean kernel when the initial 3.4 kernel issues were happening. Seems he was building like 3 versions a day to fix the problems and that was shortly before the time I found your amazing kernel and never looked back I swear it's the most stable custom kernel I've seen!
[Verizon Samsung Galaxy S III] masri1987:
Sorry decimal man, short term memory lol, either way running great on nanolunch and row.

Thanks again for your response
[Verizon Samsung Galaxy S III] decimalman:
I might have gotten a bit ranty yesterday. Sorry about that. :o

I sat down yesterday and started writing out some documentation on the stuff that's unique to dkp. It's still pretty crude, but it should be better than nothing. Check out the last sections of post #3. Let me know what parts could be described more clearly.
[Verizon Samsung Galaxy S III] pocii29:
This is exactly what I've been looking for, thanks so much. I'll be sure to look it over and fire back some questions at you.
[Verizon Samsung Galaxy S III] decimalman:
Exciting news: I'm doing two releases today!

I've decided to release a new stable 3.4 build. It's not much different from the latest test build. Off the top of my head, these are the only changes since the last "stable" build:

A few new CM commits, Linux 3.4.49, etc.

Reversed the Trickster "Override Minimum Voltage" setting. I actually read the description and realized the previous logic didn't make sense. Now, turning the setting off correctly allows lower voltages.

Actually boots, BT works, and all the other exciting fixes I've made since the previous "stable" build. :D

As usual, downloads are linked in the OP.

I'm also releasing a very, very experimental TW kernel. It's so experimental that I'm not even going to link to it in the OP (also, I'm too lazy to bother :p). Previous versions didn't brick testers' phones, but I guarantee that there are bugs. Here's what to expect:

Basically everything from 3.4 has been ported, but very little has actually been tested.

GCC 4.8, -O3, LTO, and all the other optimized fanciness included in 3.4 dkp builds. Performance isn't quite where I'd like it to be yet, but it's certainly not awful.

Crazy bugs. Something is setting the minimum frequency to 1026 MHz during boot (which you should change back to 384 MHz!), there may be issues with calls on some carriers (please let me know, and if possible provide a logcat and/or dmesg!), freezes might happen, and I'm sure there's more bugs I haven't even heard about yet.

Downloads are available here.

Edit: Just realized I didn't tell my build script to make a release, so builds were uploaded into the experimental downloads instead. Real release builds will show up in the stable downloads page shortly.

Edit 2: Release builds are up in the stable downloads page.
[Verizon Samsung Galaxy S III] Dearborn1977:
6/14 running like a champ. Your kernel is great! Really need to get the word out about dkp!
[Verizon Samsung Galaxy S III] pocii29:
Alright everyone so the time has come to give you the verdict on the nanolunch/zen stress test on the zero lemon... I'll let the pics do the majority of the talking.

So let me give you a bit of a background on what I was doing... I had been on the search for the perfect balance governor. I had previously been on pegasusq/zen with kt747. The problem was, while the battery life was good. Performance wasn't up to my standards. I could still feel a tiny stutter in normal app and home screen interaction. So after discovering free lunch, which then led me to nanolunch. I was eager to give this a go.

So here's my setup through trickster. Obviously nanolunch governor and zen scheduler. I then undervolted everything by -25 and set the max clock speed 1350.

Lastly I tweaked the sampling rate to 25000.

My goal was to simulate the use of what I would normally do on the stock battery in a day. Which was roughly 2 hours on screen out of a 15 hour charge.. I clearly failed or else I would have hit the 5 day mark. Unfortunately I had a surgery on my hand and got bored so I was playing on my phone for an extra 2 hours... But I technically would have under my schedule :).

The verdict: if your looking for something that sleeps like a baby on scotch. And throttles up to speed like a Ferrari. This is the governor for you. This bad boy did not skip a beat for me... And it's definitely not the lunch yo mama packs you ;)

I would like to thank decimal for allowing me to fall in love with this governor and for all his time he puts into this.

I would also like to thank SwiftKey Flow for helping me do this post with one hand haha.

That's all folks. I'll continue to read up on the tweaks decimal linked me so I can further tweak this bad boy.

I apologize for any grammatical or spelling errors!

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] thelangosta:
Nice write up. I wish I could run dkp on twiz. Hint, hint...

I know decimalman was talking about making a twiz version but, then ran into the issues with the aosp version.

So are you still thinking about making a twiz version decimalman? No rush of course. Just curious.
[Verizon Samsung Galaxy S III] PaulG1488:
Read a few posts above yours.
[Verizon Samsung Galaxy S III] thelangosta:
Oops, somehow skipped right over that. Yay!
[Verizon Samsung Galaxy S III] TheBurgh:
This kernel is like snoop dog....my phone is sipping on gin n juice.
[Verizon Samsung Galaxy S III] decimalman:
Test builds will be happening regularly, and I'm currently running TW full-time until everything works as it should. Unfortunately, there's still a lot of things that don't work. Since posting the builds, I noticed that nanolunch (and probably freelunch as well, assuming the issue is what I think it is) are causing freezes. I'm going to try to get everything sorted out tomorrow.

I'd love to get some feedback, if you're feeling brave enough to flash the test build.
[Verizon Samsung Galaxy S III] thelangosta:
Dl'd and ready to flash. I'll put it on tonight and see how it goes.

---------- Post added at 12:53 AM ---------- Previous post was at 12:19 AM ----------

So it booted up fine on the latest MOAR. I set it up with Zen/freelunch and it seems fast and smooth. I did notice the min.frequency was high when I first went into Rom toolbox but it immediately went down to 384 on its own. It seems to do this every time too. I go in and it shows 1026 and then immediately drops. I then tried YouTube because that seems to break easily. Videos were playing at double time(just a guess but it was going fast) and there was no sound. Then I tried Google play music and no sound there either. Netflix was smoother than YouTube but was playing fast as well and again no sound. I played with the volume on all of those apps and could not hear anything. I'll leave it on over night and see how it idles and try to remember to report back in the morning. Battery at 84% now in case I forget.

Edit: Just a quick update this morning. When I woke up the phone was off because the battery had drained while it was idle. I took a dmesg using the KTweaker tool this morning in case you can use that decimalman. I can put that on Dropbox or Drive if you would like. Anything else I can get for you? I did try to call myself this morning from the wife's phone and it did not ring. I will need sound(that means going back to KT for now) at some point today as I have to call my Father and wish him a happy Father's day. Now, time for cinnamon rolls and coffee for my Father's day!
[Verizon Samsung Galaxy S III] prototype7:
Little nitpicky thing here, could you space out the download links in the OP a bit? Hard to hit the right one on the app. Thanks! :):thumbup:
[Verizon Samsung Galaxy S III] jakereeves31:
Get some smaller fingers:P
[Verizon Samsung Galaxy S III] decimalman:
LOL

I'll space everything out a little bit more. Links in the mobile app are a pain to begin with, and having them all sandwiched together doesn't make it any easier to deal with.
[Verizon Samsung Galaxy S III] decimalman:
I'm uploading new test builds. Apparently, I somehow disabled a fairly important driver on all non-d2spr devices, and naturally I didn't realize it. I flashed the d2vzw build this morning, and it wouldn't play videos, open the camera app, play any sounds whatsoever, etc. I enabled the driver that was missing, and everything seems to work fine. Hopefully the new builds will be better-behaved.

If the missing driver was causing other sections of the kernel/ROM to misbehave (which is likely), your crazy overnight drain is probably just another symptom of that issue. If you see drain like that with the new build, I'd love to get a dmesg from midway through the drain.

New (TouchWiz only!) 20130616 builds will show up here shortly.
[Verizon Samsung Galaxy S III] trvbone:
Hey anything I can do to stop memory bog? Seems like in the past I could run for days without a reboot now I gotta reboot everyday I think it's been since we moved to 3.4 kernel base.
[Verizon Samsung Galaxy S III] thelangosta:
Phone is charging now. I had some weirdness after flashing back to KT to get sound back. I had what seemed like a SOD but, it would not reboot without pulling the battery first. I knew the phone was on because I was getting notification sounds and the LED was flashing but, the screen would not turn on. I just dirty flashed MOAR back on itself and left it with their tweaked stock kernel for now. I will be DL'ing the new TW build after the kids are in bed.

So the missing driver made a difference. Sound and video both appear to be normal. Phone is draining slower than yesterday so far. Camera works fine. I did just have a lockup while trying to open an app. That lead to the black screen and a battery pull just like on KT so it could be Rom related. I am going to let the screen time out and see if I can get it to wake up.
[Verizon Samsung Galaxy S III] Cruiserdude:
Love the way this kernel has been running, really top notch work and attitude man, thanks a lot.

I am having an issue at the moment where the latest builds (6-14, 6-16) won't boot on Slim 6.2 or 6.5. Just stays at the boot animation forever. Going back to an earlier build (as recent as 6-11) boots just fine. I don't think it's a specific CAF merge or CM change, as I just flashed BMS 6-16 and it's working fine, though I do miss this.

Any ideas what could cause this, or anyone else getting the same or a similar issue?
[Verizon Samsung Galaxy S III] decimalman:
Sounds like you're grabbing the TW test builds. I keep forgetting to mark the links to TW builds as such. The newest AOSP build is the 6/14 stable build linked in the OP.

I'm lucky if I can even stay on the same ROM for a few days, so I didn't even realize there was an issue. :p I don't have any ideas off-hand, but I'll try to resist rebooting next time I'm running a 3.4 kernel.
[Verizon Samsung Galaxy S III] Cruiserdude:
Oh wow, haha, how's that for a brain fart and a half? :p Completely forgot you said you were building a TW kernel, but yeah I had indeed grabbed the wrong kernel!

Thanks for the quick feedback, embarrassed but glad to be back to your kernel!

:D
[Verizon Samsung Galaxy S III] decimalman:
It certainly doesn't help that the filenames are all cryptic jumbles of letters and numbers. :p There's actually some organization, but it's not really apparent to anyone but me. I should really re-think the way everything gets named and organized on dev-host.
[Verizon Samsung Galaxy S III] TheDriller:
Definitely need a TW version lol
[Verizon Samsung Galaxy S III] pocii29:
Here are the test builds.

http://d-h.st/users/decimalman/?fld_id=16850#files

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] Mattish13:
I almost made the same mistake by flashing 6/16 tw kernel to my aosp Rom but saved myself the headache when I read the file name in recovery. Phew!
[Verizon Samsung Galaxy S III] TheDriller:
Makes sense to me. I get it
[Verizon Samsung Galaxy S III] thelangosta:
Makes sense to me too. I just look for either the TW or 3.4 and that tells which one I am about to flash. You could probably trim out some of the numbers(time?) and that might help.

So I ran TW 6/16 all night last night and had 10% battery drain. Not bad considering the build with the driver issue drained the phone completely. My two highest ranked "drainers" were Android system and Android OS according to Gsam. As I was about to write this my phone rang and after I hung up it locked on the contacts page and became unresponsive. I had to pull the battery to get it back up and running. Kinda hard to get a logcat on such a random issue. It is possible that I have a Rom problem since my lockups have happened on two kernels. It might also be time to wipe everything and start fresh. I haven't wiped internal in a long time and there are probably some leftovers lurking around in there.
[Verizon Samsung Galaxy S III] pocii29:
Putting nanolunch with some tuner tweaks to test on the stock battery for those of you not using zero lemons. Will report back later :)

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] decimalman:
The test builds are (as far as my build script is concerned) no different than the builds that I flash to my phone when I'm working on dkp. It's handy for me to be able to keep a zillion builds around, which is why there's so much information packed into the filenames ("dkp-<kernel version>-<device>-<date>-<time>-<git branch>.zip"). If I can convince curl to rename the files when uploading, then I'll trim everything down.

If you were running freelunch/nanolunch, it's the governor that's to blame. I haven't sorted out the exact reason, but they're causing the input drivers to deadlock.

10% isn't the end of the world, but it could certainly be better. It sounds like the kernel is at least partly to blame, but hopefully as I sort out the other issues, the kernel will behave better in terms of battery drain as well. It probably sounds bizarre, but the issue causing the freezes could potentially cause additional standby drain.
[Verizon Samsung Galaxy S III] david_hume:
Loving this kernel right now. Awesome work!

sent from my GS3 from the infected army
[Verizon Samsung Galaxy S III] thelangosta:
I have not had so much as a stutter all afternoon on nanolunch/zen. I made at least two phone calls, texted, checked email, and swtiched my TiBu directory to my external sd. The phone has been idling nicely in between all that.

10% was not bad at all. That is more in line with what I would get on an AOSP rom but, is acceptable to me for a work in progress. I think the best I ever had was 4% over night.

I understand that the freezes can cause drain after owning this Transformer tablet through the last couple of years. It is stuck on the 2.6.39 kernel because it is old and 2.6.39 is stable and does not seem to cause the battery draining SOD's that some were having on experimental 3.x kernels. So that means I am running CM10.1 on the 2.6.39 kernel and it seems to work pretty well. Sorry, I wandered there a bit, this home brew from my brother in law is making me chatty.
[Verizon Samsung Galaxy S III] decimalman:
I think that's the sign of a good beer. :)

I've been meaning to rewrite the section of code that I think it's causing all this, so this should be a good motivation. I got a bit distracted today, but it shouldn't be terribly complicated to get everything fixed up.

I haven't heard any other issues, so either nobody is feeling daring or I'll be able to focus on tracking this down. :D
[Verizon Samsung Galaxy S III] jdidtht:
God damn your thread over here is popping. I see a bunch of friendly faces here. Sup guys?

Absolutely Infected SGH-T999
[Verizon Samsung Galaxy S III] thelangosta:
Right before you posted this I had another lockup. This only seems to be happening after I hang up the phone(both occasions I received the call, when I made 2 calls earlier it did no happen) and it takes a battery pull to fix it. So something to do with the cell connection maybe not wanting to let go after a call. Other than that everything seems fine. Don't know if it matters but I am on the mb1 aio modem/radio. Thanks.
[Verizon Samsung Galaxy S III] Dearborn1977:
Fortunately dkp is like methadone to the Infected masses running AOSP!
[Verizon Samsung Galaxy S III] decimalman:
Hmm. I might need to reevaluate then. Modem issues are certainly possible, and it's possible that the TW drivers are different enough that some of what works on 3.4 won't work. I'll keep you informed.

On an unrelated note: it looks like not only can I get my build script to rename builds when I upload, I can also set it up to organize them much better. I'll probably switch to a more sensible setup from here on.
[Verizon Samsung Galaxy S III] pocii29:
I'm hoping my stress tests will get more thread attention :)

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] thelangosta:
I am expecting two phone call this morning and will try to grab a logcat. I was typing this on the phone but it locked up while typing. If I turn the screen off now I will have to pull the battery so I am going to see if it times out and that makes a difference.

It lost exactly 10% last night so it is at least consistent. Again not a big deal to me.

Edit: Screen never timed out so it is definitely locked up. On another note I am going to try out some benchmarks in a little bit just to see where the kernel is at even at this relatively beta stage.
[Verizon Samsung Galaxy S III] pocii29:
Here's the stock battery stats with some of my tweaks. Keep in mind I did have sync on. Or else it would have been different.
[Verizon Samsung Galaxy S III] masri1987:
What are these tweaks??
[Verizon Samsung Galaxy S III] pocii29:
My bad thought I posted them

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] what be up:
What's the name of that app?
[Verizon Samsung Galaxy S III] decimalman:
It's Trickster. The new update has theme options.

I'll look into this. Thanks for continuing to test and provide feedback. :thumbup:
[Verizon Samsung Galaxy S III] thelangosta:
No problem and thank you for working on a TW kernel. I ran some benchmarks with various gov/sched combos and had no issues with lockups. Made and took calls without issue. I'm currently on row/nanolunch and it is running nicely.
[Verizon Samsung Galaxy S III] kinnerful:
Will the TW kernel come with frandom/erandom support?
[Verizon Samsung Galaxy S III] trvbone:
Not to be a whiner, but could we get a secondary thread for TW specific kernel support/talk? This thread looks like it's going to get very fragmented and confusing with many people asking wth kernel is being discussed.
[Verizon Samsung Galaxy S III] PaulG1488:
Not necessary most kernels here have both tw/aosp in the same thread. As long as people do some reading it'll be very easy to figure out what's being discussed.
[Verizon Samsung Galaxy S III] pocii29:
Well since this was an aosp thread before... All you tw losers can get lost!

Jk

I don't think it will be an issue. It's pretty easy to tell whether someone is talking aosp or tw. If not, your probably just not familiar with the roms and what they are using

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] decimalman:
It already has it. I don't recommend using entropy apps though, since on dkp the entropy pool should never deplete. The only way such apps will improve responsiveness is by keeping the CPU frequency higher than it otherwise needs to be.

Maybe. I'll decide what to do once I get a bit closer to a stable TW build.
[Verizon Samsung Galaxy S III] thelangosta:
Actually the TW Kernel feels really stable except for my one lockup per day. These lockups are totally random and only seem to happen once and then the phone is stable for the rest of the day. My battery life also feels like it it's getting better every day. I don't think you are too far off decimalman.