yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] decimalman:
You'd be hard pressed to get less than 10%/hr with the screen on. I'd estimate that the screen uses as much power at low brightness as the CPU does under heavy load. You'd have to either dim the screen until you can barely read it or neuter the CPU in order to make any major improvements.

As for lower minimums, I've been meaning to actually measure the effects of changes like this. I've answered this question more times than I'd like, so here's the deal: in most other kernels, this "feature" is at least partially BS. To my knowledge, there are only two devs who are currently using code that works correctly, and I'm trying to get into contact with one of them.

EDIT: I finally got around to doing some testing with Trepn. Here's the result: lowering your minimum frequency does not save power, unless you lower it so far that system stability is affected. I have no plans to support tweaks that result in unstable phones, so I won't add underclock frequencies. My source is available, and anyone is free to build it for themselves with lowered frequencies.

As you overclock, the processor generates exponentially more heat. To prevent damaging your processor, there's a safeguard in place that reduces the processor's speed when it gets too hot, which is probably what's causing issues for you. While it's possible to disable this safeguard, I don't intend to fry anyone's processors by doing so.

Overclocking is great for scoring a few extra points on benchmarks (if you can keep your processor cool enough anyway), but it's not terribly realistic to use all the time. It's reasonable to overclock to 1674 MHz or so all the time, and you shouldn't have any major problems with heat, but overclocking much beyond that (especially with the interactive or ondemand governors, which like to run at the highest possible frequency) is likely to trip the thermal limit regularly.

Thanks for the detailed report. I've been focusing on TW lately, so AOSP hasn't gotten as much testing as it should. I'll flash CM today and try to track this down.
[Sprint Samsung Galaxy S III] chris-allen:
Gatcha...thanks for the responce..u sound like a great dev. :)
[Sprint Samsung Galaxy S III] Rxpert:
Thanks for the feedback

I know there is (a Dev) who runs the tw kernel at 81mhz (and I'm sure you know them as well).

But anyway I love your current aosp offering (haven't tested your two kernel.

The only issue I have is with that media playback as I mentioned before.

Sent from my SPH-L710 using Tapata
[Sprint Samsung Galaxy S III] decimalman:
I'm always glad to hear that my work is appreciated. :good:

For some reason, Google Music is using what looks like a lineout audio device instead of the normal audio output. I have no idea why, but I'll continue to look into it. If you're just playing local media, Apollo should work fine (although I don't really like the interface much :().

I'll keep my comments regarding the 81 MHz frequency to myself.
[Sprint Samsung Galaxy S III] Rxpert:
No problemo sir. Was only asking. If underclocking min is not something you think would be beneficial end of story

:thumbup:
[Sprint Samsung Galaxy S III] wallythander:
I have never really noticed any benefit from underclocking to 192 as opposed to 384mhz. I love this kernel. Great work. I am on the most recent build, the battery life is great. Everything works for me, I don't use Google Music so I can't comment on that. I really like the Nanolunch governor.
[Sprint Samsung Galaxy S III] Android Attack:
Hey everybody! :) It's been a while since I've changed anything on my phone.. I've been on vacation and I needed a stable phone for a while! But I'm ready to start flashing again! I just flashed latest stable dkp on Slim build 6. Battery life isn't too great though :( could someone help me out with undervolting? I am using trickster mod. I can put 384mhz-1134mhz all at 700mv and my phone still runs. I don't think that's right at all. I'm not sure what I'm doing wrong, I just can't seem to effectively undervolt. I've looked at some other posts in this thread, but it still seems like nothing is increasing battery life. The default voltage for 384mhz is 850mv. Sorry if I'm not too clear about my intentions, I'm exhausted! Thanks for the help :)
[Sprint Samsung Galaxy S III] tlrsax54:
I've been having hell getting anywhere near decent battery life with aosp roms...heard a lot about this kernel and gave it a shot yesterday, simply amazing! Made it through the day with no problems, awesome work decimalman! :good: :highfive:
[Sprint Samsung Galaxy S III] das_webos_transformer:
I haven't ever gotten good battery life on the stock cm kernel. Only once and the ROM came with a tweaked version. My only complaint from this kernel is I think it affects the Tue 3g/4g tradeoff somehow and makes me get kicked to 1x(3kbs/second) and it doesn't like to toggle off. Back to 3g. But as you can imagine, that's extremely tollerable since I get bad battery life on anything else.
[Sprint Samsung Galaxy S III] cl0ck_w0rk:
I can also reaffirm the volume issue..it's either on full volume or off completely..running on jelly am...other than that very solid kernel.
[Sprint Samsung Galaxy S III] Rxpert:
Thanks for confirming that.

Unfortunately its a deal breaker for me. I listen to music/podcasts all day at work with my headphones and its wayyy too loud.

Agreed, other than that its a killer kernel though. Will be my daily whenever he gets it squashed.
[Sprint Samsung Galaxy S III] mikedavis120:
Battery life seems decent. I don't even know what version of your kernel this is.

On paranoid android rom with heavy usage.
[Sprint Samsung Galaxy S III] decimalman:
Do you have the vmin zip installed? If so, it will interfere with undervolting by raising the minimum voltage limit. Trickster is able to change the minimum voltage (look for the "Override Minimum Voltage" setting -- it has to be off in order to undervolt), but doing so will eliminate the stabilizing effects of the vmin zip. If your phone isn't stable at low voltages, you may need to increase the voltage for the lower frequencies.

Sorry for taking so long to respond. Distractions, distractions everywhere!

Are any other apps doing it? I've been running TW lately and only flashed AOSP for long enough to test Apollo and Google Play Music.

I don't know enough about Android's audio stuff to track down exactly what the issue is. I haven't even made any changes to the kernel audio stuff, so I don't know why GPM would suddenly be using the wrong audio device.
[Sprint Samsung Galaxy S III] cl0ck_w0rk:
Are any other apps doing it? I've been running TW lately and only flashed AOSP for long enough to test Apollo and Google Play Music.

I don't know enough about Android's audio stuff to track down exactly what the issue is. I haven't even made any changes to the kernel audio stuff, so I don't know why GPM would suddenly be using the wrong audio device.[/QUOTE]

The only thing I can think of is some conflicting script, or one of the sound mods not working well with the kernel maybe? Some guy reported the issue on cm10, and I'm running jellybam. Sound was confirmed to be working before I flashed this kernel. The funny thing is, every kernel I flash after that still has the volume problem. The only way to make it go away was to factory reset and install jellybam again. The volume keys work and I see the bar moving on the volume panel, the volume is just either the loudest possible, or not on at all. Other than that though I got 3 hours of screen on time with 30% left with poor service all day, my phone never lasts that long.
[Sprint Samsung Galaxy S III] tlrsax54:
Such a bizarre problem :( Can't seem to replicate the issue on RootBox...maybe it is only certain ROMs?
[Sprint Samsung Galaxy S III] decimalman:
I think I have source repos for RootBox and CM sitting around. I'll update them and see what they're doing differently.

Thanks for the info, it should make it much easier to track this down! :highfive:
[Sprint Samsung Galaxy S III] tlrsax54:
If it matters, I'm on 6-18 nightly...haven't updated in a bit...
[Sprint Samsung Galaxy S III] Lolanerd:
I've been running 6/11 along with jellybam and I've gotta say great work man. Battery life is definitely comparable to voldemorts kernel (you know) on aosp. Plus you're not a sellout, and that in itself is awesome lol
[Sprint Samsung Galaxy S III] cl0ck_w0rk:
Wait...You're on jellybam with the 6/11 kernel? The 6/14 had the sound issue with me; is yours working correctly with a previous version of this kernel? I'm gonna flash the 6/11 and see if it had it I guess, I really wanna use this kernel.
[Sprint Samsung Galaxy S III] mawst95:
I have an issue. I'm on the latest slim bean weekly. Noticed that when I listen to Pandora and play scramble with friends, the music playback becomes choppy. The graphics also becomes glitchy in terms of responsiveness. Tried ROW with freelunch and asswax. Am not underclocked or undervolted. Stock slim kernel doesn't have a problem. Muting the in game sounds had no effect. Doesn't happen with local music playback just streaming via Pandora.

Oh I should say music choppiness happened when I touched the screen playing the game. Wifi and 3G.

Let me know if I can help diagnose.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Changed your I/O
[Sprint Samsung Galaxy S III] decimalman:
It looks like the day after I most recently synced with CM source, they added a few bits and pieces to the audio core. I'm guessing that's why audio has been wonky lately. I'm syncing with their source now, and I'll push new test builds ASAP.

Strange. I'll give it some thought and send you a PM when I think of something to test. Thanks for reporting the issue. :good:
[Sprint Samsung Galaxy S III] bmeek:
cool. looking forward to it!

I had noticed a good deal of kernel-related updates in cm10.1 since your last update on 6/14, and was wondering what you were planning... Also, over on d2vzw we've had a firmware/modem update since then.

Nonetheless, everything seems to be running fine with dkp 6/14 and the latest cm10.1 nightlies on d2vzw.
[Sprint Samsung Galaxy S III] decimalman:
I usually check up on CM's source on my phone, but I've been flashing between ROMs and haven't ever restored my OctoDroid backup. Oops.

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
[Sprint Samsung Galaxy S III] jfcooley:
Downloading now.

As always, thank you.
[Sprint Samsung Galaxy S III] Rxpert:
I'll test for sound as well

---------- Post added at 07:40 PM ---------- Previous post was at 07:35 PM ----------

Sound bug gone!!!!! :thumbup:
[Sprint Samsung Galaxy S III] mawst95:
Will test as well

---------- Post added at 10:42 PM ---------- Previous post was at 10:14 PM ----------

Unfortunately problem still exists and now Pandora only plays out of one side of my headphones. Other song apps play okay. Bummer.
[Sprint Samsung Galaxy S III] falconator:
Been off the charger for 16 hours, 4% battery and just shy of 5 hours screen on time, plenty of 3g, some nav the works. On liquid smooth 2.7, latest stable build, best combo I've tried to date. :D
[Sprint Samsung Galaxy S III] Lolanerd:
Hey, sorry for the late reply. I'm still on 6/11 with jellybam 8 and I don't have any sound issues as far as I can tell.
[Sprint Samsung Galaxy S III] magnumstg16:
Spent the last 20 minutes searching and attempting the previous fixes by my MMS still will not send after flashing this kernel. I'm on CM 10.1-20130627 nightly and 3.4.49 DKP 6-14-2013 kernel. I AM using Gosms and I've tried the mms.apk app fix here. So in between changing kernels from the stock CM kernel to DKP's I lose MMS capabilities. Please someone save me from this torture.
[Sprint Samsung Galaxy S III] decimalman:
I don't think there's been any crazy changes from CM that would break MMS sending, but I'd recommend updating to the newest test build before continuing. It's not in the usual location, since I'm working on making my downloads more obvious.

Once you're on the latest test build, the usual MMS troubleshooting applies. Is data turned on? Does data actually work (there were some issues with it recently)? Failing that, I'll need some more debug info. Will you flash this, try to send an MMS, open a terminal emulator app, and run:

su
dkp
[Sprint 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. :)
[Sprint Samsung Galaxy S III] jfcooley:
As always, thank you.

Been running on Rootbox nightlies, no issues.
[Sprint Samsung Galaxy S III] jfcooley:
Got some serious lag when scrolling launcher and selecting just about anything. Same settings as previous builds. Have gone back to previous test build and so far everything is better. Need more time to see though.

Don't know if this was related to kernel as I haven't tried since going back but charged very very slow.

Rootbox 7/3 nightly.
[Sprint Samsung Galaxy S III] Xynche:
I've been having a problem with random reboots. I've installed the debug zip and have the log Here.

I have undervolted by 50, I'm new to this so I'm not sure if this is the cause. It happens often in powersaver and conservative. Running on Pac nightlies, I'm behind a few days though.

I'm new to flashing and utilizing kernels so go easy on me.
[Sprint Samsung Galaxy S III] das_webos_transformer:
I bet its your under volt.
[Sprint Samsung Galaxy S III] jdidtht:
Yea man don't under volt it anynore.. As long as your phone is sleeping quickly that 50 isn't going to make that big a difference.

Absolutely Infected SGH-T999
[Sprint Samsung Galaxy S III] Xynche:
Arlright, I just switched to rootbox and reflashed everything. No undervolt this time and everything seems okay, was just trying to squeeze as much life out of this guy as I can.

Thanks for the help guys.

EDIT:

I have mistaken, no undervolt and still getting random reboots on a new rom.
[Sprint Samsung Galaxy S III] decimalman:
How's this for going easy on you: getting lots of details from you and having you work on your own to rule out other possible causes is a kernel dev's dream. :good:

It looks like you're running a fairly old build (CM keeps updating things, so anything built more than a week or two ago is "old"). I'd recommend updating to the latest (7/4) test build. It looks like the shiny new video drivers included in your ROM are causing issues with the older drivers included in the kernel build you're running.

If that doesn't help any, let me know.
[Sprint Samsung Galaxy S III] jfcooley:
Anyone have any idea why my device charges slowly, very slowly when in deep sleep.

I plugged in @ 71% around 10:00pm and was at 81% by 4 am.

Use the device and it charges at a normal rate.

Have logs while running, will get logs after a full night in morning.

Meanwhile any ideas? (Used multiple stock and aftermarket batteries and chargers)

http://db.tt/O3t9OfiR

Current plugged and awake logs.
[Sprint Samsung Galaxy S III] Xynche:
I switched to rootbox nightlies and still have the issue without the undervolt running the 7/8 build. It happens very rarely with most governers but powersaver and conservative make it happen within a few mins.

I checked and it looks like I downloaded an older kernal by accident, I reflashed the newest build and I still getting reboots. Now within the first 60 seconds on freelunch. I rushed in and changed governer to performence to see if low clock speed was the problem and didn't get a reboot. Changing it to powersave gave me a reboot within seconds.

So, I'm not sure but it seems like when it hits the low clockspeed it reboots. I don't know if that helps but that's all I really know how to test.
[Sprint Samsung Galaxy S III] phyba:
I had the same problem. Not sure why. I ready something bout rev0 phones not playing well but I could be wrong
[Sprint Samsung Galaxy S III] decimalman:
I had assumed that the warnings in your kernel logs were probably related to the issue (they probably weren't helping any, anyway). As phyba hinted at, not all rev 0 processors will take kindly to one of the tweaks that most (all?) custom kernels use. Since you've mentioned that you're having trouble especially with governors that use lower frequencies (and therefore lower voltages), the reboots you've been getting are probably caused by the processor not getting enough voltage.

Normally, the kernel guarantees that at the processor will get at least 1150 mV. In order to properly undervolt, dkp disables this guarantee by default. Flashing the vmin zip from the OP will keep it enabled, which (assuming that voltage is the issue) will fix the reboots.

There's a few things to be aware of about the vmin zip. It gets reset whenever you flash dkp, so you'll need to flash it again whenever you flash dkp. You also won't be able to undervolt below 1150 mV (you can, but it's more difficult to do and defeats the purpose of the vmin zip).
[Sprint Samsung Galaxy S III] jdidtht:
I'm rev0 and have no issues but I do bump my mind. Voltage up from 900 to 925 or 950

Absolutely Infected SGH-T999
[Sprint Samsung Galaxy S III] Xynche:
The vmin seems to have solved the problem. However it says that the voltages are still as ow as 850 under set cpu. Does the vmin overide that to ensure the voltage is high enough??

Thanks for the help, loving the kernal.
[Sprint Samsung Galaxy S III] phyba:
Trying this kernel again and vmin has fixed my reboot issue so far. Wasn't there a zip to flash for trinity colors or how do I enable and disable them?
[Sprint Samsung Galaxy S III] Frostbiter:
Even with flashing the vmin thing all my phone does is freeze/reboot with this kernel now, it used to run fine but coming back to AOSP after a long time with TW.
[Sprint Samsung Galaxy S III] decimalman:
The minimum voltage is separate from the voltage table, so you'll still see voltages lower than 1150 mV.

Once upon a time, there was such a zip. There's now a setting in your ROM to configure it. System settings->Advanced->Screen color temperature.

I need more information. Can you grab a last_kmsg? Better yet, will you flash mikedavis120's debug zip from post #3 and use it to send some debug info my way?
[Sprint Samsung Galaxy S III] Frostbiter:
Here are the logs that you asked for, if you need more or something else just let me know.

Thanks,

Frostbiter
[Sprint Samsung Galaxy S III] nyles:
Re: [ROM][4.2.2][July 6th] Slim Bean-d2spr [build 7]

Hi everyone. I love this kernel. Best aosp in my opinion. I just noticed however that i am having problems playing audio through bluetooth. In both my car as well as my headphones, the music only comes out of the left side speaker

Edit: Flashed back to stable release and the problem is fixed. Thanks
[Sprint Samsung Galaxy S III] banccalif:
Kernel u mean?
[Sprint Samsung Galaxy S III] decimalman:
New TW builds are going up! I might have forgotten that I was working on TW for a while. :o I merged in everything from AOSP, including some changes that haven't even made it into the latest AOSP test builds yet. From what I can tell, everything is more stable than the last build was.

Downloads are available via the link in the OP. Incidentally, does the new layout for downloads make more sense to everyone? I'm open to suggestions about better ways to organize the downloads, since I updated my build script to handle pretty much whatever layout I decide to go with.

Changelog:

UKSM: this was probably the only AOSP feature that wasn't present on the last TW build. It's merged in now.

Pulled in Samsung's latest code from the MF1 source drop (there's only a couple lines of changes compared to MD4, but whatever). I'm going to look into merging Linux 3.0.86 eventually, but this build is as up-to-date as any other TW kernel at the moment.

Rewrote the interaction code. The old code was unsafe and probably a bit slower than it should have been. The new code is written in assembly and is also safer.

Disabled SEC_DVFS. I haven't had much time to test, but this appears to fix the 1026 MHz bug, and will probably improve battery life.

Lots of freelunch changes: I haven't heard any complaints, so I merged most of the changes in nanolunch back into freelunch. I also made a small change that might make freelunch more suitable for gaming, and hopefully won't affect battery life or smoothness otherwise. nanolunch is gone, since it was a (successful) experiment anyway, and it'll disappear from AOSP builds shortly.

New toolchain fanciness: I haven't seen any freezes in the few days I've been running TW, so it looks like the new compiler I'm building with is pretty stable.

Regarding the changes in freelunch: I'd love to hear some feedback regarding battery life. A few settings have changed, but it's possible to switch back to "classic" freelunch: setting interaction_panic and hispeed_divisor to 0 will effectively switch back to the old behavior. I'm curious whether the changes I made will have any substantial effect on battery life, so reports are encouraged. :good:
[Sprint Samsung Galaxy S III] j00manji:
Playing with this kernel for some time now, sorry if this sounds like a silly question: Can I use the ktweaker app to play with this kernel? the main thing I liked about it was being able to subtract or add voltages across the board. Might there be another app to do that?
[Sprint Samsung Galaxy S III] tlrsax54:
Check out Trickster Mod in the Play Store ;)
[Sprint Samsung Galaxy S III] shekinahsmoke:
can this work on a 4.1.2 rom? I thought the TW one did at some point? :confused:
[Sprint Samsung Galaxy S III] mikedavis120:
Hey everyone. I'm on vacation and unrooted stock md4 just so I don't feel the need to work on my phone and stuff while on my down time.

Quick request from someone that is on the TW Kernels that were just recently released. I would like the script I wrote to work on the TW versions, and it should no problems. But can someone install my debug.zip run the su dkp commands and upload the results so I can modify scripting If needed.

Thanks everyone.
[Sprint Samsung Galaxy S III] chris-allen:
Awsome spped ...usin the tw ver. With the blazer ROM ;)
[Sprint Samsung Galaxy S III] shekinahsmoke:
looking real good on the MOAR rom 5.02 beta on freelunch & row now
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
Has anyone compared this TW version kernel with Ktoonsez TW kernel? please give a detailed description of pros / cons between the two.
[Sprint Samsung Galaxy S III] shekinahsmoke:
#EtiquetteFail

sent from the galaxy via tapping and talking
[Sprint Samsung Galaxy S III] tlrsax54:
Comparisons are not allowed....give it a shot and try for yourself, its running fine here.
[Sprint Samsung Galaxy S III] Mr.Miyagi555:
sorry all, didnt know comparisons were not allowed .
[Sprint Samsung Galaxy S III] mikedavis120:
Can anyone flash the dkp-debug script and test it on a touchwhiz build, and attach the .tar file from the output folder here. Ill modifiy it if needed to work on the tw builds.

Thanks whoever helps.

I'm on vacation with an unrooted device rigjt now.
[Sprint Samsung Galaxy S III] shekinahsmoke:
Ondemand and row... Kinda cool

sent from the galaxy via tapping and talking
[Sprint Samsung Galaxy S III] Keldig:
ok fairly noob here please be gentle LOL

I have a L710.14 and installed dkp-3.4-d2spr-20130614 that wouldnt boot so i loaded dkp-enabled-vmin still no boot?

I have LJ7 Kernal with boot animation support Fixxed.zip file on my sd card so that worked and brought me back to Kernal version 3.0.31-329968 se.infra@sep-97 #1 SMP PREEMPT ??

any help would be gratefully appreciated.
[Sprint Samsung Galaxy S III] phyba:
Are u on aosp or touchwiz?