yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
Probably. My first suggestion would be flashing the vmin zip in the OP, which will switch back to stock voltages.

I was opening an image attached to an email. The screen went black and everything froze. I don't think it's the same issue that's causing thelangosta so much grief, but it's a major issue nonetheless.

Thanks. Any info at all will help. It's pretty tough to track down bugs that only seem to happen every other week.
[Verizon Samsung Galaxy S III] Droid316:
Itching to try the 6/16 TouchWiz kernel but I don't see Alot of people talking much about it.
[Verizon Samsung Galaxy S III] Dearborn1977:
decimalman, quick question on the ramdisk (search is down - sorry if asked already). Is it stock or does your AOSP kernel come with a modified one? I'm thinking of flashing back over to dkp from a different kernel but don't want to create any crazy issues, and am concerned if my current kernel modified the ramdisk dkp might have some issues if it is not flashing its own ramdisk. Perhaps I'd need to find a copy of the latest "stock" CM kernel and flash that first?
[Verizon Samsung Galaxy S III] vmancini3:
Every time you see me talking about how I can't get my phone to freeze or lock up or anything.....that's exactly the kernel I'm talking about...its been running great for me since Friday night...only problem I have is the min and max speeds are a little uncontrollable, however with that being as it is I am STILL getting excellent battery life! And if you want realistic usage.....we're talking about roughly 20-21 hrs. on a single charge and that's with a total of anywhere from 3 1/2 to 4 1/2 hrs. screen on time!!!

EDIT: 2 things....my "realistic" usage is me REALLY using my phone... and also keep in mind that what works for one person may not work so great for the next person...just make a nandroid if you're worried about anything...
[Verizon Samsung Galaxy S III] Droid316:
I loaded it up.Let's see how it goes.Noticed like you did the voltages are backwards.any fix for that?
[Verizon Samsung Galaxy S III] mmikeee:
just wondering if i can flash crossbreeder or if you already implemented the entropy tweaks? I see the kernel will use erandom instead of crossbreeder's frandom function.
[Verizon Samsung Galaxy S III] vmancini3:
Yeah....don't use SetCPU... the only app that I suggest using with this test build is AnTuTu CPU Master... but your results might be different than mine...
[Verizon Samsung Galaxy S III] SpudsterZ:
Been using CB with this kernel for awhile with no noticeable adverse behavior. I am interested in what DM thinks, though.
[Verizon Samsung Galaxy S III] decimalman:
I don't recommend Crossbreeder, but it should work fine.

I did some testing a while back, and determined that adjusting the write_wakeup_threshold is all it takes to prevent the entropy pool from depleting (dkp includes this modification). Since entropy and frandom were such a big deal a while back, I also heavily modified the kernel entropy system to almost entirely use erandom ("economical" frandom).

Personally, I use Trickster, but any app that's not SetCPU should work fine. :p
[Verizon Samsung Galaxy S III] vmancini3:
Ok...so far today..on the 6-16-13 test build of dkp, I was streaming Pandora via Bluetooth ALL DAY...no issues at all! Last night I played Minion Rush for about an hour and since Friday night I've also played a TON of Candy Crush.....still no freezes, lockups, reboots, etc...
[Verizon Samsung Galaxy S III] jdidtht:
Next release should be badass..

Absolutely Infected SGH-T999
[Verizon Samsung Galaxy S III] decimalman:
Every release is. ;)
[Verizon Samsung Galaxy S III] TheDriller:
Actually it wasn't 6 days it was 6 hours screen time. 27 hours unplugged. I was on TW (the best) and undervolted by -25, pegasusq governor and zen scheduler. Nothing crazy conservative. Most users of my bins get around 5 hours screen time with my tweaks
[Verizon Samsung Galaxy S III] Cruiserdude:
Touché! I had something else to add, but I'm watching "Butter", and just saw Olivia Wilde as a stripper, so, uh, there went my train of thought...
[Verizon Samsung Galaxy S III] jdidtht:
Lol ..

Absolutely Infected SGH-T999

---------- Post added at 12:21 AM ---------- Previous post was at 12:16 AM ----------

[QeUOTE=decimalman;42956877]Every release is. ;)

This is true man.. I keep forgetting to check my posts over here.. I should just subscribe here instead of t999 area..

Absolutely Infected SGH-T999
[Verizon Samsung Galaxy S III] pocii29:
Oh well Damn that's a huge difference. I can get between 4 and 5 on a stock battery for aosp. But I'd rather sacrifice an hour and not be on tw. TW to me is super ugly and doesn't seem as responsive as aosp.. Even with beans

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)

---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------

@decimal for some weird reason after my first reboot of reflashing the kernel, it shows the kt747 boot image. Any ideas on how to remove this?

I am also trying to restore my nanolunch test settings in trickster. But when I do reboot, it is just on the stock interactive settings

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] Dearborn1977:
Hey dec, I saw another kernel dev saying he didn't want to include various non stock governors and schedulers because they were not Krait cpu optimized. Thoughts on that and is freelunch/nanolunch krait optimized?
[Verizon Samsung Galaxy S III] Dcox28:
I am running Notta's latest release of Paranoid Android. I've been on it for a few days now with no issues. I just now installed the 3.4 dkp kernel (stable version from 6/14/13). I also watched the video in the OP and almost did exactly like in the video except I only underclocked down to 1350 and then undervolted starting with 1350 and then went all the way down and undervolted everything by -25. I applied changes and then set to force on boot. I am running the Zen scheduler and Nanolunch governor. after rebooting I am getting a pretty big screen flicker, especially when in the app drawer and scrolling through the apps. Normally in other roms i've flashed I know when this happens to check Disable HW Overlays. I did check this but it didn't help, the flicker is still there. Any suggestions? Did I do something wrong in my voltage setttings? Thanks in advance.

Edit - Maybe I should just chill out and let the kernel settle? I starting noticing the flicker immediately and then posted on here about it. It is still happening but perhaps the kernel just needs to settle for a while, i'm not sure?
[Verizon Samsung Galaxy S III] jdidtht:
Bump your voltages back up man. I would have just left them stock which is still much lower than stock Sammy tables .. I've never had a flicker if flicker or issues still persist after moving voltages back up flash the dkpvmin zip and if it still persists flash the the debug zip follow op instructions and grab some possible info for him. But im pretty sure if you keep your voltages dkp stock the flicker should go bye bye

Edit im a rev0 device running voltage as normal with interactive /sio on jellybam 8.2 and get 13hrs battery with 2.5 screen on with no problem without even trying. A couple syncs on nothing greenified and im a heavy user.

Edit IMO super low voltage is overrated too low causes issues.. Flicker glitches. Feed the beast just make sure the beast gets its sleep. A deep sleeping beast that falls alspeep fast equals battery life without sacrificing performance

Absolutely Infected SGH-T999
[Verizon Samsung Galaxy S III] Dcox28:
Thanks, I will give that a try and bump the voltages back up.

Edit - That was definitely it. I bumped voltages back up +25 and now the flicker is gone.
[Verizon Samsung Galaxy S III] jdidtht:
Sounds good. I reedited my post a few times. Sorry bout that.

Absolutely Infected SGH-T999
[Verizon Samsung Galaxy S III] decimalman:
TW needs an "I know how to use my phone so quit nagging me" option, but otherwise it doesn't bother me that much. Battery life is only a little bit better anyway. I've been away from AOSP for long enough that whenever I grab a new ROM, all the new stuff takes me by surprise. :D

dkp doesn't include its own ramdisk, so ramdisk tweaks (like the boot splash) will carry over. I've been meaning to update my flashing script to fix up the ramdisk, but I haven't gotten to it. In the meantime, you'll need to flash a kernel with a stock ramdisk and then flash dkp. Unfortunately, that pretty much means reflashing your ROM, gapps, etc.

EDIT: Trickster can be fussy about applying settings on boot. It sometimes won't apply until you adjust the "Apply Grace Period" setting.

I'm glad I'm not the only one that doesn't want to include every governor in existence. :) dkp doesn't include any governors that can't properly manage a Krait CPU, and I've also added some code to work around the incorrect assumptions that many tuner apps make. freelunch and nanolunch are optimized for Krait to the point that they won't work on any other processors without being completely rewritten.

Thanks for replying while I was away. That was exactly the response I would have given. :highfive:
[Verizon Samsung Galaxy S III] jonesj8:
Does the i535 have a krait CPU?

Sent from my Infected i535
[Verizon Samsung Galaxy S III] decimalman:
Yep. All current Snapdragon devices have Krait CPUs. S3, S4, HO, etc. all have Krait CPUs.
[Verizon Samsung Galaxy S III] jonesj8:
Thank you and I forgot to ask does this kernel support exfat SD cards

Sent from my Infected i535
[Verizon Samsung Galaxy S III] decimalman:
Nope. The AOSP version never will, and I don't plan on supporting it on TW.
[Verizon Samsung Galaxy S III] decimalman:
New test builds are up! They're not in their usual location. I decided to re-arrange the upload paths on dev-host, so (for today anyway) uploads will be going here. I'm probably going to change the paths again in the near future, but I'm hoping that it will be much easier this way.

Changelog:

Merged a zillion CM commits

Linux 3.4.51

Disabled auto-hotplug during boot
[Verizon Samsung Galaxy S III] vmancini3:
Seems this is for AOSP only...is that right? I'm not trying to be impatient...I know you're probably just very busy with life too..lol
[Verizon Samsung Galaxy S III] bmeek:
So far, so good. I've been running the phone through its paces and it appears to be flawless.
[Verizon Samsung Galaxy S III] decimalman:
I'm working on a few things on TW at the moment, and a TW build in its current state wouldn't run very well. I've been slacking and haven't gotten much done lately. :o The new test build was mostly to get back in sync with CM--they merged some audio stuff a while back that was causing a bug on newer ROMs.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Well I was about to look around and see which aosp kernel I should flash but considering all the familiar users in this thread, looks like I'm testing this one... lol
[Verizon Samsung Galaxy S III] countryfolk07:
Yes. It's a very nice kernel. No frills. Does the job, with excellent battery life.
[Verizon Samsung Galaxy S III] vmancini3:
^^ +1!
[Verizon Samsung Galaxy S III] pocii29:
It's a diamond buried underneath all this other jibber jabber

Carbonized and powered by dkp's nanolunch munchies... (this ain't the lunch yo mama packed you)
[Verizon Samsung Galaxy S III] gzsmooth:
Hi guys, I downloaded dkp newest exp kernel for verizon and Im running Slimbean 6.9. I cant get any of the settings to stick after a reboot? I dont usually mess w underclock or undervolt but after watching the vid in the OP I thought Id give it a shot and see if I can get some battery improvement. Any suggestions? Btw I used Trickster and Rom Toolbox pro
[Verizon Samsung Galaxy S III] jdidtht:
What specific settings? I use trickster mod and everything sticks for me. CPU /voltage/ you name it it sticks..

infected T999
[Verizon Samsung Galaxy S III] gzsmooth:
None stick.... Governor changes from dance dance back to interactive. Max profile changes from my set 1242 to 1512. And I undervolted -50 and it all changes back. Maybe I should just clear app data and un-install and try again
[Verizon Samsung Galaxy S III] trvbone:
Are you sure you have the set at boot checkbox check I know it may be a dumb question but just asking. Also you may want to set a five second delay before settings are applied. You may have some init.sh files applying at boot. Also make sure when you adjust something you click on the check mark in the top right corner of the trickster mod so it applies the settings.
[Verizon Samsung Galaxy S III] philseven:
just wondering if anyone has try'd this kernel with liquid I did and got reboots any help would be appreciated :beer:
[Verizon Samsung Galaxy S III] gzsmooth:
Thanks for responding but after clearing app data and doing another clean rom install all is well. The only suggestion I hadn't tried was the 5s delay. I didn't think about the init.sh file applying at boot
[Verizon Samsung Galaxy S III] Eyalkn:
Download vmin from the op and flash it.
[Verizon Samsung Galaxy S III] philseven:
thanks for the help didn't work
[Verizon Samsung Galaxy S III] Eyalkn:
I just came from liquidsmooth 2.8 with the latest kernel and it worked without any issues.
[Verizon Samsung Galaxy S III] philseven:
did you have that kernel controller app enabled
[Verizon Samsung Galaxy S III] Eyalkn:
No
[Verizon Samsung Galaxy S III] philseven:
Maybe that is the problem going to try without in rom kernel enabled.
[Verizon Samsung Galaxy S III] thelangosta:
What's up decimalman. Justed wanted to stop in and say that dkp is still my favorite aosp kernel too! I flashed an aosp rom on the way home from vacation and of course put dkp on right a way. Fast, smooth and stable with great battery life on MROM 6/29. Thanks
[Verizon Samsung Galaxy S III] decimalman:
New test builds! I haven't added anything new, but that's no reason not to upgrade.

Changelog:

Synced up with CM and Linux. Newest CM commits are included, as is Linux 3.4.52.

Finally updated my toolchain. A month's worth of Linaro and GCC commits shouldn't hurt performance any. :)
[Verizon Samsung Galaxy S III] jdidtht:
Thanks DC you the man. Best kernel on xda hands down. Thanks for the July 4th present!

infected T999
[Verizon Samsung Galaxy S III] decimalman:
Around here, all the good celebrations happen on the 3rd. Happy Independence Day everyone!
[Verizon Samsung Galaxy S III] jonesj8:
So if I am using the free lunch gov should I disable mpdecision? Got kind of confused about the hot plug settings. Thanks all
[Verizon Samsung Galaxy S III] Cruiserdude:
This and all other custom kernels are making my phone reboot whenever something tries to get a gps fix on LiquidSmooth 2.7 and 2.8. :(

My only guess is some new CAF or CM merges don't get along with older ones in the rom? I don't know, anyone else using that setup and NOT having my issue?
[Verizon Samsung Galaxy S III] EnemasRfun:
I'm on LiquidSmooth 2.8 and that GPS hotboot issue doesn't happen for me.... Though I am getting a reboot on using the front-facing camera (but only on certain camera apps like CameraZoom FX). Didn't have any issues with the setup on 2.7 either..... That being said, can't wait for the next stable build of dkp! Literally, I can't wait. Where is it?? ;)
[Verizon Samsung Galaxy S III] TheBurgh:
Have you tried the latest test build? Working great for me
[Verizon Samsung Galaxy S III] thelangosta:
Yep, latest testing build running great here too. I just used gps and strava and had no issues at all on Mysterious AOKP. Well, no problems, except for the whole running outside in the heat and humidity part and still sweating 45 mins later.
[Verizon Samsung Galaxy S III] OMG_VTEC:
decimal, is this updated to fix the mf1 camera issues? no one seems to mention your kernel. i think its one of the best ones out there...
[Verizon Samsung Galaxy S III] decimalman:
No need. dkp automatically freezes mpdecision when it's not needed. In fact, dkp guarantees that only one thing is trying to hotplug at a time: governor, mpdecision or auto-hotplug.

Can anyone get me a last_kmsg for this (getting a logcat via adb during the crash would be handy too)? I think I still have LS2.7 on my SD card, so I'll try to duplicate this on my end too.

That's this commit, right? I've got a d2spr, so I don't know exactly what the issue with MF1 was (is?).

I try to stay up-do-date with CM, and the latest two or three test builds should all have that commit merged.

EDIT:

Strange. Can you get me a last_kmsg? I've had to patch the code for the front-facing camera a few times now. It seems like it breaks every time I upgrade my compiler. :(

Probably soon. There's a few outstanding issue that only seem to affect a few people. I'd like for the next build to be "stable", not just "stable enough" ;) but I might have to settle. The previous stable build is old enough that it won't work well with newer ROMs, so it's definitely time to update.
[Verizon Samsung Galaxy S III] jdidtht:
Last test release on latest 8.4 jellybam working well nothing to say bad or negative. Sorry. Lol revo d2 jellybam 8.4.. On the 3rd? Lol yea not here man 4th is where its at..

infected T999
[Verizon Samsung Galaxy S III] neh4pres:
Decimalman, I get strange behavior in system tuner when using freelunch. System tuner usually shows cpu load as a percentage of 0 to 100. As soon as I click freelunch, and watch for a min I get radical numbers. Like -240 and numbers above 100%.

Via my Google Galaxy S3 running magic beans
[Verizon Samsung Galaxy S III] decimalman:
HIDE tags work just fine. Thanks! :highfive: I'll let you know what I find.

EDIT:

Strange. Unfortunately, I have no idea how exactly it's trying to calculate CPU load, so I have no idea why it isn't working correctly.
[Verizon Samsung Galaxy S III] jdidtht:
I like to use trickster mod.. Or more recently the cracked faux tuner app that's free instead of 5bucks.. Both are decent

Absolutely Infected SGH-T999
[Verizon Samsung Galaxy S III] guywmustang:
I'm running nanolunch and I had to bump up the gpu to 200 cause it was just too slow. I put it on the ondemand scheduler. Is that more power conscious than performance?
[Verizon Samsung Galaxy S III] Cruiserdude:
dkp doesn't have gpu overclock yet, so you should leave the max frequency at 400 unless you enjoy lag. The performance gpu governor doesn't take noticeably more battery than ondemand to me, and speeds things up even more. Obviously if you're doing everything you can for battery life, however, you'll want to stick with ondemand.

As far as schedulers, use whatever works for you. We aren't using hard disks, there isn't gonna be much if any difference in battery life in any of them, so go with whatever you prefer.
[Verizon Samsung Galaxy S III] decimalman:
Nope, I just use it and hope I spot bugs before anyone else finds them. :p Let me know how it works for you.
[Verizon Samsung Galaxy S III] trvbone:
Which one are you testing?
[Verizon Samsung Galaxy S III] mademan420:
http://d-h.st/Oat

freelunch/row
[Verizon Samsung Galaxy S III] trvbone:
Gotcha
[Verizon Samsung Galaxy S III] juancaperez2000:
Are u planning to get the new release today or going to be tommorrow?
[Verizon Samsung Galaxy S III] decimalman:
There's a bug that I think I'm hallucinating. If it turns out that I'm just crazy and nobody else runs it on the new experimental builds, then I'm probably going to build a release in a day or two.
[Verizon Samsung Galaxy S III] clothednblack:
Yep, that's what I am using

SG3 slim and ktweaked
[Verizon Samsung Galaxy S III] trvbone:
Is there a gpu or animation issue on every 3.4 kernel or is it just me? Like back when you always had to set disable hw overlays. Sometimes setting disable hw overlays along with force GPU rendering helps and other times it don't. I get inconsistent animation rendering. For example sometimes when I back out of an app it's real smooth sometimes it's not. Idk if anyone else experiences this but almost every gov and sched I try it does it.
[Verizon Samsung Galaxy S III] decimalman:
It's not just you. That was my first reaction when I switched to 3.4. Disable HW overlays seems to help for me, but it's still not perfect. I don't think there's any way to completely fix it, and I don't know what's causing it either. I'll investigate a bit, but I doubt I'll uncover anything.
[Verizon Samsung Galaxy S III] trvbone:
I'm pretty sure it has to do with Samsung hasn't released 3.4 kernel base for our phones if I understand from others input. But I'll tell you right now this has no lag compared to the last 5 lk kernels I tried. I'm glad I'm not the only one with the weird animation thing. I'll be flashing to the new kernel build to get your added governors in the morning.... Great stuff
[Verizon Samsung Galaxy S III] trvbone:
Hey I hate to be greedy or demanding, BUT is there maybe a way you would assign possibly a build date or simple number or version sequence so it's easier determine which kernel is which? For instance dkp-4.3exp480 or for the non 480 builds just dkp-4.3.4.14 with the last part being the date Idk. I don't want to make it any harder for you, so what ever you think works best I'll figure it out. Just thought once everyone jumps on this kernel it will reduce a lot of which version etc questions. Gonna flash new now! Thanks again!
[Verizon Samsung Galaxy S III] trvbone:
Update: I've got disable hw overlays enabled and force GPU rendering checked, using trickster I've changed GPU to performance governor enabled, zram on and set multi core to 1. Running sio and freelunch. On the linaro 481 most recent exp build on d2usc. This has eliminated animation issues as far as I can tell.
[Verizon Samsung Galaxy S III] decimalman:
I do that for the stable builds. While I'm developing, it's helpful for me to be able to keep a bunch of builds around while I'm testing, so I have to use a different naming scheme. The experimental builds are essentially just development builds as far as my build script is concerned, so they get named differently from the stable builds. It's not exactly obvious, but there's a lot of information in the filenames: development branch name, device, and build date/time are all there.

This is all done automatically by my build script, but I can look into making the filenames a little bit more obvious for builds that will be uploaded.

How buggy is the linaro481 build? Any data issues? I didn't intend to upload anything using that compiler yet, but another user was having some issues with the previous d2usc version and I forgot to change compilers before I uploaded.
[Verizon Samsung Galaxy S III] clothednblack:
This is running great for me, loosing data after the flash was a coincidence (us cellular shut my phone off) they screwed up my billing date lol.

SG3 slim and ktweaked
[Verizon Samsung Galaxy S III] trvbone:
Running fantastic! No data problems here! Since this has erandom I think that's the term, will this work with cross breeder?
[Verizon Samsung Galaxy S III] decimalman:
Disregard that last PM then. I really need to check my threads more often.

Good. I started rewriting some stuff last night and I was afraid that I let some crazy bugs slip in when I built it. On the other hand, it's built with Linaro 4.8.0-r197974 with graphite optimizations enabled, and should benchmark like a MF.
[Verizon Samsung Galaxy S III] HikingMoose:
So a few D2USC users have convinced me that this kernel is the way to go. Where do I find the absolute latest build?
[Verizon Samsung Galaxy S III] decimalman:
http://d-h.st/1rE

Newest updates will be in the "Testing 3.4 downloads" link in the OP.
[Verizon Samsung Galaxy S III] HikingMoose:
Sweet, thanks. Is there a new build coming out today? I just don't know if I should flash that one, or wait for a new one.
[Verizon Samsung Galaxy S III] clothednblack:
There was a mix up in communication between the dev and I, flash that one. Updates are easier to flash than the OTHER kernel we were using :D

SG3 slim and DKP