yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
freelunch didn't make the transition to 4.3 very gracefully. I haven't gotten a chance to investigate what changed to break it, but even interactive is getting better battery life. :( I think it just needs to be re-tuned a bit, though that's probably a bit intimidating given the gazillion tuners it has. If I find some settings that work better, I'll update the defaults.

Dev-host is back up. It figures they'd go down while I was away from my computer and couldn't mirror the builds anywhere else. :(
[Verizon Samsung Galaxy S III] annoyingduck:
Current test build has been running great on cm10.2. I've been running freelunch and row.
[Verizon Samsung Galaxy S III] kinnerful:
Hi decimalman,

Thanks for the great work! Been running TW builds for awhile and all is good.

Do you recommend deleting some of the following files in /system/bin/ ?

gsiff_daemon mpdecision qosmgr smd smdexe

Saw this tweak in the Team Kernelizers thread and they seem to suggest that deleting some of them is good for other TW custom kernels as well.
[Verizon Samsung Galaxy S III] aypeeootrek:
Just dropping in to give you a thanks. 4.3 test build is running great with the latest bean stalk
[Verizon Samsung Galaxy S III] decimalman:
With dkp, I would specifically recommend keeping mpdecision, since dkp will take care of it on its own. The other four supposedly cause wakelocks, settings not sticking, demonic possession of your phone, and possibly nuclear war. If any of these happen, then I'd recommend that you remove the files. Otherwise, I don't see much reason to delete stuff from your ROM.
[Verizon Samsung Galaxy S III] vmancini3:
Holy crap.....this post just made my night!!!! I actually was just lmao!!!!!:thumbup::p:D
[Verizon Samsung Galaxy S III] kinnerful:
Same here... Thanks again decimalman!
[Verizon Samsung Galaxy S III] draexo:
lf I have a rev0 I should not undervolt, correct??

Sent from my Carbonized S3!! via Tap Talk
[Verizon Samsung Galaxy S III] Masterx9:
This kernel kicks assss:thumbup::D:thumbup::thumbup::D:thumbup:
[Verizon Samsung Galaxy S III] ACLakey:
I installed this on my USCC S3 with Hyperdrive ROM. I went through the setup video and it is running very well. I will see in a few day how the battery fairs.
[Verizon Samsung Galaxy S III] pimpmaneaton:
+1. Beat battery life with this kernel and performance is awesome.
[Verizon Samsung Galaxy S III] RCOVA:
I couldn't change governors on this kernel. It would just reboot. Does that mean I have to flash that additional zip in the OP?
[Verizon Samsung Galaxy S III] vmancini3:
This is the kernel I've been using with Goodness! Like you said....great battery life AND performance!!!
[Verizon Samsung Galaxy S III] decimalman:
It's been too quiet in my threads lately. I guess I'll have to shake things up a bit with a new 4.3 test build. :)

Changelog:

Improvements to the color temperature setting in Trickster. Also, the enable setting actually does something now.

Removed tons of debug stuff from the wifi driver.

Some housekeeping and bugfixes. Nothing dramatic, just tidying up.

Synced up with CM (mostly), merged Linux 3.4.65.

EDIT: Oops, forgot about you, RCOVA.

Sorry for the delayed response. :o

I've never run into that before. Which build are you running? You could try the vmin zip, and if it doesn't help, will you PM me a last_kmsg?
[Verizon Samsung Galaxy S III] annoyingduck:
Sweet, downloading now...

Thanks decimalman
[Verizon Samsung Galaxy S III] MrBrady:
I noticed there was a TW 10/9 test build, but now it's gone. Were there issues with that kernel?

VZW SGSIII
[Verizon Samsung Galaxy S III] decimalman:
Nothing catastrophic, but I uncovered a few bugs in freelunch. I was hoping to get them fixed quickly and get new builds out, but it's taking longer than I expected. :(
[Verizon Samsung Galaxy S III] decimalman:
I finally got the bugs sorted out, and freelunch should sip battery like it used to. New test builds for 4.3 and TW are going up.

AOSP 4.3 Changelog:

Bugfixes for freelunch

TW Changelog:

Bugfixes for freelunch

Added color controls to Trickster (20 = trinity colors)

Stripped touchscreen and wifi drivers

Fixed a few miscellaneous bugs and potential bugs
[Verizon Samsung Galaxy S III] vmancini3:
[MENTION=4932679]decimalman[/MENTION] I've been working crazy overtime and have been out of the loop for a little while now. I noticed in the "stable builds" folder on dev-host there are 2 stable builds with the same date (9-26), but one has way more downloads....is that one the newest version and just dated wrong?
[Verizon Samsung Galaxy S III] MrBrady:
Just tried flashing the TW 10/9 test kernel and phone wouldn't boot past boot logo. Running Clean ROM 7 with full odexing. MD5 matched. Reverted to 9/26 Stable and it booted fine.

VZW SGSIII
[Verizon Samsung Galaxy S III] decimalman:
It's in the test builds folder, and rightfully so.

I only tested the changes on AOSP, and apparently they break on TW. :( I'll look into it tonight.
[Verizon Samsung Galaxy S III] vmancini3:
:confused:I'm sorry, maybe you misunderstood my question (maybe I should've worded it differently)...:confused:

This is what's in your "Stable Builds" folder....and I was just wondering what the difference is between the two dated for 9-26
[Verizon Samsung Galaxy S III] annoyingduck:
Latest test is running smooth (aosp) since this morning. Had an initial freeze on the initial boot, but after a battery pull it fired right up.
[Verizon Samsung Galaxy S III] decimalman:
I think I did misunderstand. :o IIRC the first build had some issues booting for some people, and the second one fixed it.
[Verizon Samsung Galaxy S III] bigbear6708:
Just loaded on slimbean first cycle is going fine so far
[Verizon Samsung Galaxy S III] decimalman:
New (fixed) TW test builds are on their way up. I actually tested them this time.

Changelog:

Fixed the freeze during boot.
[Verizon Samsung Galaxy S III] vmancini3:
Are there any outstanding changes in the brand new test builds?
[Verizon Samsung Galaxy S III] MrBrady:
Running great so far. Thanks! :good:
[Verizon Samsung Galaxy S III] vmancini3:
[MENTION=4932679]decimalman[/MENTION] Seriously, you're a freakin magician dude! Running the 9-26 stable build....so far 7 hours on battery, 2 hours on screen time and I'm at 68% battery!!!:thumbup: And freelunch is behaving nicely! Even the newsfeed on Facebook is pretty smooth, definitely smoother than previous builds!!!! Excellent work bro!!!!
[Verizon Samsung Galaxy S III] RCOVA:
Thanks man. Let me try your latest kernel and I'll let you know. I'm on Carbon. 10-09 nightly. But it's been happening on past versions too.
[Verizon Samsung Galaxy S III] RCOVA:
So on your latest my phone reboots when I try to overclock. Using Trickster Mod. Nbd because asswax makes it really smooth. What settings do you use decimalman? Scheduler/IO etc.
[Verizon Samsung Galaxy S III] Droid316:
I installed this kernel correctly and can under clock and over clock and no reboots or anything,I followed the directions and all is running great.Imagine that.

™ Sent From My Slimrom 4.3 Rom Running BMS Kernel With Killjoy Script Powered By 7000MAH Of Battery Power™
[Verizon Samsung Galaxy S III] RCOVA:
Hmm... Maybe it's Carbon then... Whatever. I like Carbon way too much to let it go.
[Verizon Samsung Galaxy S III] vmancini3:
Did you try upping the voltage just a little bit for those overclocking steps?

Edit: on a previous build I tried overclocking just a little up to 1728 MHz and it would just reboot immediately.... Then I looked and the preset voltage for that clock speed was 1175 mV, so I upped it to 1200 and it never rebooted again!
[Verizon Samsung Galaxy S III] moeduss:
Any chance of getting the kernel sound drivers for faux sound added or flash able zip made to work with the Verizon test build? Thanks
[Verizon Samsung Galaxy S III] decimalman:
Sound control is included already, but apparently I never updated the TW kernel with the latest update. I'll update it and get a new build out soon.

It's your voltages. The overclocked voltages are on the low side by default, so some phones will need a little extra voltage to OC to 1674 MHz. You'll need progressively more voltage as you OC higher.
[Verizon Samsung Galaxy S III] annoyingduck:
I haven't been able to get a log of this issue because it's random... Running cm10.2, latest test build, row/freelunch/Oc 16200. Phone will randomly enter an unrecoverable sod. Pulling battery is the only way to get out of it + when trying to reboot it gets to the splash screen and freezes. Have to wipe caches in recovery to achieve boot.

Reverted back to stable 4.3 and have not had it happen yet.

Any ideas on how I can recreate the issue to capture a log?
[Verizon Samsung Galaxy S III] mbarry55:
Just switched to this kernel using free lunch and this is the best battery life I have seen on this device yet. Fantastic kernel.
[Verizon Samsung Galaxy S III] annoyingduck:
FYI, don't run any custom kernels on 4.3.1 that aren't set for it - if you do, "you're gonna have a bad day"!
[Verizon Samsung Galaxy S III] Quie2TP:
Running this on Eclipse build 6 and loving it so far. Full day tomorrow will be a better indication.
[Verizon Samsung Galaxy S III] pocii29:
I too been stuck in the work loop. But I wanted to bump this and let everyone know that I am still getting the best performance to battery life balance with a couple of my own tweaks

:)
[Verizon Samsung Galaxy S III] HikingMoose:
10-4 Clothednblack! Flashing now.
[Verizon Samsung Galaxy S III] HikingMoose:
So far it's fairly smooth. I like it. Should I disable MPDecision? I can't remember what it is (even though I did look it up before, but can't remember if it was good or bad).
[Verizon Samsung Galaxy S III] decimalman:
I don't give that much notice when I post builds. I'm not that organized. :p I'll usually post about new builds while they're building and uploading, so you'll probably only get about 10 minutes notice before a new build comes out.

3.4 doesn't have erandom. I can add the official frandom code in to support CrossBreeder. Eventually I'll try to track down the issue that's preventing 3.0's erandom code from working on 3.4 and get it merged back in.

I wouldn't worry about mpdecision. The code in the most recent builds I uploaded will automatically freeze mpdecision when you're using a hotplugging governor. mpdecision is an Android service that automatically turns core 2 on and off when it's needed, but it gets in the way of hotplugging governors so it's often recommended to disable it on other kernels.
[Verizon Samsung Galaxy S III] juancaperez2000:
can someone share which is the most resent d2vw test build, thanks in advance
[Verizon Samsung Galaxy S III] srs731:
Wow great kernel so far. Just loaded it. Transitions are fast and smooth again. Phone is dead so know nothing about battery. First kernel to get me off KT. After the 3.4 my phone kept overheating on his.

I am on the latest governor build I guess it is?
[Verizon Samsung Galaxy S III] clothednblack:
How does the "multi core " option in trickster MOD work with this? Trying to see if there is a booster option based on touch or always on as needed.

SG3 slim and DKP
[Verizon Samsung Galaxy S III] clothednblack:
Going on day 3 and I may have found the easiest way to set this up and gain hours of juice without compromising performance. I will update this later today if it goes how I believe it will :thumbup:

SG3 slim and DKP
[Verizon Samsung Galaxy S III] zetsumeikuro:
It's been there even in the 3.0 kernels and so far the only fix is to check disable HW overlays. I have read it has to do with the OS having issues selecting what renders the UI/animation (cpu or gpu) hence the stutters. Even with the overlays disabled it's still there, but no where to the degree as before.
[Verizon Samsung Galaxy S III] decimalman:
New 3.4 test builds coming out soon! I'm still playing with compilers, so today's compiler nerd-speak is: Linaro GCC 4.8.1-dev with graphite. :p

What's new:

Linux 3.4.40 (not many changes that affect us, but why not?)

New CM/CAF commits

Reworked some cpufreq code to be less ugly. The performance governor is only useful for benchmarking, so now it locks core 2 online.

Fixes to the overclocking code, plus a small fix for msm_thermal when overclocking

New, hopefully more obvious naming system for test builds: dkp-3.4-(device)-(date)-(time)-(branch).zip

Compiler bragging rights! :D 3.4 finally benchmarks the way it should.

There's two more things I want to add to 3.4, and I'll backport some fixes and features to 3.0 and release new stable builds.

Edit: clarified the performance governor thing.
[Verizon Samsung Galaxy S III] luv2increase:
What do you mean the second core is only good for benchmarking? Are you sure you know what you are doing? :(

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] decimalman:
I mean the performance governor is only good for benchmarking.
[Verizon Samsung Galaxy S III] clothednblack:
Dang typos lol

http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/ClothedNBlack.png
[Verizon Samsung Galaxy S III] trvbone:
Running great!
[Verizon Samsung Galaxy S III] HikingMoose:
Any chance of getting a 192 step? Would that be hard to implement? I also want to vote for your custom governor to get a touch boost and some settings. It's a great governor and I really like it. But my phones scroll choppy, and it might help if I could turn on a touch booster and set it to max speed for both cores (your kernel will jump to max on one core, and sometimes put the second core online a little, but not fully. Please understand these are merely questions/suggestions. I truly do love the kernel. Best 3.4 kernel I've used.
[Verizon Samsung Galaxy S III] trvbone:
I concur I don't have choppy scrolling but I do get touch issues at times I have to touch more than once for the input to take. Not complaining or demanding just things I've noticed. I believe you've got the best kernel right now! No issues compared to all the other 3.4 kernels that I've tried and according to the forums for the others people are still having probs.
[Verizon Samsung Galaxy S III] decimalman:
192 step: no. The only way to run the processor slower than 384 MHz is to keep an additional timing source powered on and using battery, defeating the purpose. The bottom frequency steps on other kernels (often labeled 81, 96, or 192 MHz) actually still run at 384 MHz, and it's not possible (in practice, anyway) to change that.

Touch boost: sure. I had a few ideas about this a while back but never got around to trying them. My goal with freelunch is to avoid running both cores at max frequency when it's not needed but to still feel reasonably snappy. Freelunch can be tuned to run fairly smoothly, but for absolute buttery smoothness, I need to add some extra code.

Edit: Before I get any skeptical comments, flash another kernel and test for yourself. Grab a tuner app like Kernel Tuner that will let you configure both cores (not all apps set core 2's frequencies, so if it turns on it'll skew your results), and set your minimum and maximum frequencies to the minimum step. Run Linpack. Set you minimum and maximum to a frequency around 384 MHz. Run Linpack. The results will look way too similar for the processor to have been running at 1/4 the speed.
[Verizon Samsung Galaxy S III] trvbone:
Wholly awesomeness just tried oc on newest test build d2usc I can get 1620 my sweet spot w/o

Hot booting!!

Up to 1728 no hot boots! Shall I press on anything above 1800 before didn't work!
[Verizon Samsung Galaxy S III] clothednblack:
Downloading now
[Verizon Samsung Galaxy S III] HikingMoose:
This kernel is awesome. I did not know that about the kernels that run below 384 (but I have noticed that battery life doesn't seem to improve when using the lower clocks, so that makes sense).

This extra code for the buttery smoothness you speak of, does interest me. Probably only me. Which stinks. But if it doesn't sacrifice a lot of battery, I'd love to test a build with your buttery smooth tweaks! I've owned and tried a bunch of S3's and every single one, when you are slowly scrolling the screen hitches, and hesitates, and doesn't follow your thumb. I don't see how everyone doesn't notice it. I've seen it on 11 of them. all 11 did it. The one that does it the least is a D2SPR that a friend gave me.

This kernel is the smoothest of all the 3.4 kernels. So don't think I'm complaining at all. I just figure there must be a way to make the CPU keep up with my thumb. Either scrolling slowly, or flicking my thumb to scroll quick (also choppy).

Thanks for everything you do, and the great work, and your masterful understanding of kernels!
[Verizon Samsung Galaxy S III] trvbone:
Yeah I get this choppiness mostly in chrome though or when it involves pulling info from the web?
[Verizon Samsung Galaxy S III] mbarry55:
[MENTION=4932679]decimalman[/MENTION] do you have 4.3.1 in the works? I stopped doing nightlies until your kernel is updated, it's that good
[Verizon Samsung Galaxy S III] decimalman:
Update away--existing builds already support 4.3.1. The only changes on 4.3.1 are to the ramdisk. dkp doesn't include a ramdisk and reuses what's already installed, which makes it mostly ROM-agnostic.
[Verizon Samsung Galaxy S III] mbarry55:
OK thank you for the reply. A lot of people were reporting bootloops with custom kernels on a few roms that moved up to 4.3.1. Glad to hear.
[Verizon Samsung Galaxy S III] draexo:
Cool. This will work with 10/15 of PACman then??

Sent from my PACmanized S3!! via Tap Talk
[Verizon Samsung Galaxy S III] drecu:
Yes it will.
[Verizon Samsung Galaxy S III] draexo:
Working so far so good

Sent from my PACmanized S3!! via Tap Talk
[Verizon Samsung Galaxy S III] decimalman:
New TW test builds are going up.

Changelog:

This happened.

Fixed the bug where frequencies show incorrectly. I think.

Finally updated FauxSound to the latest version. I forgot about TW when faux updated it.
[Verizon Samsung Galaxy S III] Masterx9:
Hey has anyone experienced their system clock going in and out if sync by chance?
[Verizon Samsung Galaxy S III] kimber45:
All good here. Running latest TW testing build on d2usc/ modified stock rom.
[Verizon Samsung Galaxy S III] WhiteBoy997:
Wow this has to be the best kernel I've ever ran on my phone. I unplugged my phone this morning at 9. And normally I would be at 85% but I'm only at 95%. Says I have 3 days 6 hours until my phone dies. :D

Keep up the work!
[Verizon Samsung Galaxy S III] Mystique:
Kernel loaded ;)

TW experimental version.

According to trickster, it looks to already be under volted..

Looks like minimum Cpu is 384, and it also looks like there are a lot of steps..
[Verizon Samsung Galaxy S III] Mystique:
So, using the default Whistle notification..

Sounds like there is an echo or reverberation (reverb) with the sound..

Just me?
[Verizon Samsung Galaxy S III] decimalman:
CM updated the video drivers again. New test builds are going up, and the usual warning for updated video drivers applies: if your ROM hasn't merged in the updated drivers, do not flash this build; wait a couple days for your ROM's next build to come out. Anything built on 10/19 or later should be fine.

Changelog:

Synced up with CM
[Verizon Samsung Galaxy S III] Masterx9:
Hmm I'll give the updated d2vzw one a try then.
[Verizon Samsung Galaxy S III] Mystique:
So, only had one random reboot.. (TW)

But I was messing with msm governor quite heavily, so I'll take credit for that..

So far looking good.

Under volted msm.. nice.
[Verizon Samsung Galaxy S III] Mystique:
trying to do my own postmortem..

but it seems that last_kmsg does not exist..

root@android:/ # cat /proc/last_kmsg

/system/bin/sh: cat: /proc/last_kmsg: No such file or directory

What might possibly make that go away?
[Verizon Samsung Galaxy S III] Mystique:
Does anyone use CrossBreeder with this kernel?
[Verizon Samsung Galaxy S III] TotallyAnxious:
I do. I use the 10/9 test build.
[Verizon Samsung Galaxy S III] decimalman:
I'd like to address a few issues related to the most recent TW and 4.3 builds.

The most recent TW build includes a massive update from Linux 3.0.31 to 3.0.100. It exposed a number of bugs, mostly affecting the GPU driver. I am aware of them, and am working on them. In the meantime, I recommend not running the most recent build! The previous build is dramatically more stable.

The only change in the most recent 4.3 build was to support the updated, unstable drivers in the recent nightly builds for a few ROMs. These updated drivers break a few transition animations and cause frequent GPU crashes that require a reboot to fix. No other changes were made in the most recent build, and therefore the only reason why you should update is for compatability with updated ROMs. Please do not request that your ROM devs merge in the updated drivers. Asking your ROM devs to break their ROMs in order to support an otherwise identical kernel build is senseless.

This thread is specifically for dkp. Please keep discussion of other software elsewhere, perhaps in a thread in the General section or the thread for the software in question.
[Verizon Samsung Galaxy S III] Mystique:
I see that this kernel has erandom in it, The OP of the thread wish it to be known that speaking about other modules will be sacked...

I was asking as I didn't see a negative impact of erandom and that other mod that shall remain nameless.. but it is duplicating effort.

I wanted to mention that I saw a very noticeable battery life improvement by not duplicating effort; I thought freelunch was great before..

Also "recent" and "previous" are relative to "now".. (all those variables..)

So are you saying "I recommend not running the dkp-tw41_2013-10-16_testing build! The dkp-tw41_2013-10-09_testing build is dramatically more stable."

(as you know there are two different 2013-10-09 builds.. dev-host shows two different md5s.. if the previous statement is true; which md5 should we go by?)

Or something else?

Mynd you, møøse bites Kan be pretty nasti...

Thanks in advance for taking the time to read this..
[Verizon Samsung Galaxy S III] Mystique:
I noticed that I had a ton of modules in /system/lib/modules from the other kernels that I had flashed..

I had to go into recovery and fire up and adb session and mount /system and delete/mv/backup /system/lib/modules..

then reflash dkp-tw41..

I then only had 11 modules..

ymmv..

Also not sure what the init script is for:

10dkp-cpufreq

for mod in /system/lib/modules/cpufreq_*.ko

do modprobe `basename "$mod" .ko`

done

There are no cpufreq modules in this kernel (10-16-2013) or in the 'stock' MF1..

#confused

bizzare..

the update-binary in the same kernel fails on my wifes phone.. updating the update-binary fixes it..
[Verizon Samsung Galaxy S III] decimalman:
Mystique: Although I welcome discussion, bug reports and questions, this is still a development thread. Keep your posts clear, concise and on-topic. Referring to off-topic subjects as "that other mod that shall remain nameless" after a request to stay on-topic is outright disrespectful. Going forward, I won't hesitate to involve the moderators in any further off-topic, rambling or disrespectful posts.

As for CrossBreeder, there's a reason that I consider it off-topic. Most of the changes it makes (DNS caching, ad blocking, etc.) are entirely unrelated to the kernel. Entropy daemons (as found in Seeder or CrossBreeder) are kernel-related, but completely irrelevant to dkp. With dkp, the entropy pool is almost entirely unused, and therefore available entropy has no bearing on system responsiveness.

To answer the few relevant points you've raised:

last_kmsg is causing issues on TW, so it's disabled.

I've removed the older 10-09 build.

The 10dkp-cpufreq initscript doesn't do anything on public builds. During development, I build a few governors as modules and need the extra script. I use the same build script to create both development and public builds, and the script carries over.

I'll grab a more recent update-binary.