yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] nikolkang:
I flashed latest test today and it hung up during boot. I hard shut down and started back up and then it loaded up just fine on the second go. Its been running smooth since...

I was getting screen flicker on the lockscreen with the carbon halo experimental rom but your latest update fixed all that.

Your kernel has been solid as always with amazing battery life. :thumbup:
[Sprint Samsung Galaxy S III] decimalman:
Good stuff. :) Does that mean that data is working for you as well?

This test build of dkp is the only 3.4 kernel that hasn't given me crazy 3%+/hr drain in standby, so I'm excited to get the last of the kinks worked out. From what I gather, drain like that is pretty rare, but it's still nice to see my phone last 24+ hours like it used to (I'm at 23 hours with 1:30 of benchmark-heavy screen time, and still at 55% :D).
[Sprint Samsung Galaxy S III] nikolkang:
Yep, data is working! :thumbup:

Glad to hear you've got the kinks worked out. I've been getting similar results so no complaints. My setup is just nanolunch noop under clocked to 1242. I leave most radios on (WiFi only when needed) and disable GPS unless needed. Pretty basic... Location services I disable again unless needed and I use greenify for Facebook and such.

Best thing for me about your kernel is how I get zero lag with noop and your governors rock. Its nice to get good battery without sacrificing performance. You nailed it. :thumbup:
[Sprint Samsung Galaxy S III] Android Attack:
Hey mate :D sorry I been outta the Android game lately. Not much free time on my hands. I'm currently running Slim build 6 with your latest test of 3.4 :) haven't had a full run through my battery cycle yet, but I'm not getting stats quite that great. What governor you using? And what scheduler? I been using the 3.0 version of your kernel for a while and I got great battery life with heavy usage. I appreciate your work mate :) thanks!
[Sprint Samsung Galaxy S III] decimalman:
Sounds like there's a few kinks left, but otherwise I'm actually considering sticking with AOSP for a while. The biggest reason I started working on TW was because I wasn't satisfied with the battery life I was getting on 3.4 kernels. I'll definitely get a TW kernel out (and hopefully soon), but I prefer AOSP as long as my phone lasts all day.

Apparently, I'm using nanolunch/row. I wasn't paying attention to the I/O scheduler or I probably would have changed it to noop. Usually row prevents me from getting any deep sleep whatsoever. It's worth noting that I'm using a recently-flashed ROM with most of my usual apps missing, and I don't think I even have an email app syncing. I'd probably have more reasonable stats if my phone were actually doing anything. :)
[Sprint Samsung Galaxy S III] Android Attack:
Hahah :p what ROM ya on? Not sure if it's just me but my performance settings have been going crazy on Slim since build 5! I can't get a max frequency to stick on any kernel haha :p
[Sprint Samsung Galaxy S III] nikolkang:
Just as an FYI I also have exchange syncing 24/7 for work. So no problems there either... Below are some screenys using your 3.4 from awhile ago. Again using noop with settings listed above... All vary depending on signal quality since we all know CDMA phones suck more juice in low signal areas. But they were all on your kernel with real world use. Not disabling data and such...

EDIT: Ignore the pic 3rd up from the bottom at 29 percent. I missed the first pic and it won't let me edit... But you get the point.
[Sprint Samsung Galaxy S III] Android Attack:
Thanks for the pics :D what ROM ya running?
[Sprint Samsung Galaxy S III] decimalman:
Since RootBox is finally supporting d2spr, I decided to give it a try. I'm pleased so far.

Nice. It's been a long time since I actually ran my battery all the way down, but I'll have to see how it goes now that standby drain isn't murdering my battery. Of course, that'll be after I get jfcooley and das_webos_transformer's issues sorted out. Development is a harsh mistress. :p
[Sprint Samsung Galaxy S III] nikolkang:
Haha nicely put.. I can only imagine. :D
[Sprint Samsung Galaxy S III] decimalman:
I enjoy it, but it's tough to balance playing with my phone with having a working phone (and fancy new optimizations with having working data :p).
[Sprint Samsung Galaxy S III] mikedavis120:
How can i unlink cpu0/cpu1 to run different min/max and governors? I played with an init script that echos to cpu0 and cpu1 but when the script echos settings for cpu1 they overide cpu0 and then there both the same. any ideas? Heres what I'm trying.

#!/system/bin/sh

LOG_FILE=/storage/sdcard/cpu.log
rm -Rf $LOG_FILE

echo "Starting cpu mods at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
sleep 10
echo "Set MIN Scaling Frequency core0" | tee -a $LOG_FILE;
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "Set MAX Scaling Frequency core0" | tee -a $LOG_FILE;
echo "1350000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "Set MIN Scaling Frequency core1" | tee -a $LOG_FILE;
echo "384000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo "Set MAX Scaling Frequency core1" | tee -a $LOG_FILE;
echo "1728000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo "Set governor core0" | tee -a $LOG_FILE;
echo "freelunch" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "Set governor core1" | tee -a $LOG_FILE;
echo "performance" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
#UV_BEGIN#
echo "Set UV" | tee -a $LOG_FILE;
echo "1350 1325 1300 1275 1250 1237 1225 1225 1212 1212 1200 1200 1187 1187 1175 1175 1125 1125 1100 1075 1025 1025 1000 1000 975 975 925 925 900 900 875 875 850 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
#UV_END#
echo "Finished cpu mods at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
clear
exit
[Sprint Samsung Galaxy S III] decimalman:
Currently, you can't. I added the link since lots of tuner apps won't touch cpu1. It won't take much work to add a setting to disable the link, I'll get something put together soon.
[Sprint Samsung Galaxy S III] decimalman:
Dev-host is down, and it looks like they might be down for a while. They haven't even posted an update on Twitter about whatever is going on. A temporary MediaFire mirror has the newest test builds.
[Sprint Samsung Galaxy S III] das_webos_transformer:
From 30seconds ago. Maybe just you? Its done weird stuff to me before too.
[Sprint Samsung Galaxy S III] decimalman:
They finally came back up sometime yesterday evening. They've been down a lot lately, and I'm thinking of switching to mediafire once I put together a script to upload automatically.
[Sprint Samsung Galaxy S III] shekinahsmoke:
Go mediafire for sure

sent from the galaxy via tapping and talking
[Sprint Samsung Galaxy S III] das_webos_transformer:
I didn't know you could do that?
[Sprint Samsung Galaxy S III] decimalman:
Officially, you can't. My build script scrapes some values out of the dev-host upload page and then uploads with curl. It makes it very easy to upload test builds and such--'./massbuild.sh -Ccfu' will clean, configure, build (in parallel), flash (with confirmation & automatic device detection) and upload (with confirmation) kernel builds for each supported device. I absolutely love my build tools. :D

If I decide to do make a script to handle MediaFire, I'll need more than a shellscript to handle it. It has a fancy API that will need at least Python to properly deal with. If I get a script put together, I'll probably switch, or at least upload to both. I really don't like MediaFire's web interface (or its shoddy Linux desktop client), so I don't want to deal with it for every single build.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Media fire is just shady in general if you ask me.
[Sprint Samsung Galaxy S III] JLine05:
Im going to try this out, I'm running liquidsmooth 2.5 and the battery sucks. I remember getting insane battery a few months ago with blackbean 5, I wonder what happened to change everything? Anyways, going to try the test build and let you know how it goes.
[Sprint Samsung Galaxy S III] decimalman:
3.4 kernels happened. Supposedly 3.4 has better support from Qualcomm, but battery life has definitely taken a step backward.
[Sprint Samsung Galaxy S III] JLine05:
So I can install your 3.0 kernel and get back the battery life?
[Sprint Samsung Galaxy S III] decimalman:
You'd need a ROM that uses a 3.0 kernel, and I don't think there's many left. 3.4 has come a long way, but the battery life still isn't quite on par with 3.0. I'd recommend giving custom kernels a shot. Until the most recent (but sadly not terribly stable) dkp test build, I had been getting terrible battery life, but I'm actually pretty satisfied at this point.

Hopefully I'll get the last of the crazy bugs worked or in the next couple days and get a more stable build out.
[Sprint Samsung Galaxy S III] JLine05:
Ok, I actually had to just nandroid, the 3.4 test build was causing reboot issues. I'll wait for a new stable. Thanks.
[Sprint Samsung Galaxy S III] decimalman:
Reboots aren't on the list of known bugs. It's possible it's caused by the lower voltages used by custom kernels. I'd advise flashing the vmin zip in the OP after flashing dkp to restore the higher stock voltages. If that doesn't help, any details you can provide (or even a last_kmsg) would be greatly appreciated.
[Sprint Samsung Galaxy S III] JLine05:
Ok i will give it another go tomorrow and flash the vmin zip. I was coming from the stock kernel that came with liquid smooth. I believe is lean kernel.
[Sprint Samsung Galaxy S III] crossen0:
My phone loves it some FreeLunch!
[Sprint Samsung Galaxy S III] chriswbush:
Should mp decision be enabled or disabled in trickster mod? I finally got this kernel not to boot loop by DL trickster as soon as it booted up and disabled the minimum voltage option in trickster and for some reason that stopped all the problems I had xD and now I can say damn this kernel is beautiful especially free lunch governor thanks dude
[Sprint Samsung Galaxy S III] das_webos_transformer:
Yes it should be on, see what I've been telling you? If these finalls finnaly end happy today its gonna be building by the weekend guaranteed. Gonna fire up some gentoo for the next machine, optimize everything I can in it, and call it golden.
[Sprint Samsung Galaxy S III] decimalman:
On the latest test builds it shouldn't matter. Auto-hotplug should take over if you stop mpdecision.

The vmin zip in the OP will do the same thing as disabling the minimum voltage in trickster but it'll keep your phone from rebooting before trickster gets a chance to change the minimum voltage as well.
[Sprint Samsung Galaxy S III] decimalman:
New test builds are going up now. The boot issue should be fixed.

Changelog:

The boot freezes should be gone. Let me know if you're still seeing them.

Linux 3.4.48, lots of CM commits, and a few new GCC compiler updates

Added UKSM

Edit:

I added a setting to control this. You can unlink the cores with

echo 0 >/sys/kernel/dkp/link_core_settings
[Sprint Samsung Galaxy S III] das_webos_transformer:
Just a query. Tw builds?
[Sprint Samsung Galaxy S III] decimalman:
On the to-do list. I think I've gotten most of the deal breaking issues worked out, but I've been too focused on getting AOSP working to flash TW and make sure. Assuming nothing else is broken on AOSP, I'll be working on TW for the next couple days.

Related:

Is anyone having Bluetooth issues? A user in another thread mentioned that devices weren't pairing. I don't have any BT devices to test with, so I have no idea whether its a kernel problem or what.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Okay thanks. I switched back to touch wiz, I need 4g or 3g not 1x. Might find a way to get signal to hold better.
[Sprint Samsung Galaxy S III] ksmullins88:
Thanks for fixing the boot freeze issue! ! :thumbup::o. I had no idea it was the kernel I thought my phone was on its way out.

I'll test Bluetooth for you in a bit then report back. Thanks for all of your hard work man!
[Sprint Samsung Galaxy S III] decimalman:
Nope, it was just me writing some buggy code. Oops.

Thanks for testing. I'm going to pore over the BT code. The data bug was caused by a bogus section of code that doesn't cause any bugs until GCC optimizes it certain ways. I'm guessing that I'll find some similar garbage in the BT code, since it looks like more of CAF's spaghetti code.

Edit: It looks like the BT code should dump some interesting info, so a dmesg would be excellent. Can you grab one if you're having issues?
[Sprint Samsung Galaxy S III] ksmullins88:
I tested pairing Bluetooth with a pair of headphones I own. The phone paired nicely and played music and made a call. When I went from the call to the music, it wouldn't play over the headset. Then when I tried to turn off the Bluetooth, it gets hung on this (picture)

I'm not sure how to give you a dmesg file, but I'll gladly give you one if I can figure it out.

Edit:

Is this it?

http://pastebin.com/ryjyEPRf
[Sprint Samsung Galaxy S III] decimalman:
Interesting. Thanks!

You can grab a dmesg with adb with 'adb shell 'su -c dmesg' >dmesg.txt' or with a terminal emulator with 'su -c dmesg >/storage/emulated/legacy/dmesg.txt'.
[Sprint Samsung Galaxy S III] ksmullins88:
There's a file in my previous post for paste bin and here's this...

http://d-h.st/oE4

I'm sure one is correct lol

Lemme know if that helps!
[Sprint Samsung Galaxy S III] decimalman:
That gives me a very good place to start. Thanks! I'll explore a bit and if I think I've got something worked out I'll send you a test build. Might be a little while though, since I'm off to work at the crack of dawn tomorrow. :(

Edit: As long as I'm here, TW is working nicely, but it doesn't like -O3 optimizations. I may push a test build out soon, although I'm disappointed with the lack of optimization.

More edit: Just checked your previous post and the pastebin link has dmesg included. It's all the debug information I could ever ask for. :)
[Sprint Samsung Galaxy S III] decimalman:
New test builds are going up. BT should be working--I'm able to FTP to another device and transfer files, but I don't have any other BT devices to test with. Anyone who's been having issues, please let me know if you're still having issues on the new build.

Changelog:

Disabled an optimization in the dhd module. BT appears to be working.
[Sprint Samsung Galaxy S III] jfcooley:
Everything great. Thanks.
[Sprint Samsung Galaxy S III] nyles:
I just wanted to thank you for such an awesome kernel. Best battery life I've ever gotten. This was only my first full battery run. Looking forward to seeing how good it'll be after the kernel settles in. Btw, running slim 6 with the latest test kernel. Free lunch is amazing.
[Sprint Samsung Galaxy S III] hayzooos:
DecimalMan - Just decided to give your kernel a shot (I think the 5/31 one) and I'm still running the weekly Slim 5.5 as it's stable as all get out from my perspective. I've heard good things about your kernel (and especially the free lunch gov) so I'm looking forward to trying it out! Thanks for your effort, always good to have more devs out there.
[Sprint 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.
[Sprint Samsung Galaxy S III] samcintron:
My phone wouldn't boot using the latest 6/14 build.
[Sprint Samsung Galaxy S III] decimalman:
Which build? The stable from the OP or the TW test from my previous post? What ROM?
[Sprint Samsung Galaxy S III] CyberGmonster:
Nice! No awake barely. What is your setup BTW? Are you using BBS?
[Sprint Samsung Galaxy S III] nyles:
Thanks cyber, i do use bbs, but i didn't get a screen shot of that battery run. I have the kernel uv as well as uc. I think i have the cpu max at 1026. It still runs very smooth with no lag at all. I even play a few light games such as subway surfers and hexagon, and get no lag. Like i mentioned earlier, this is the best battery ive ever seen. My max screen on time could barely get to 3 hrs, with the same uv and uc on a different kernel. Granted, it was on an older liquidsmooth rom and not 3.4. Needless to say, I am very happy with my current setup ( thanks again decimalman) . Btw, just flashed the latest 6/14 kernel and have no problems so far
[Sprint Samsung Galaxy S III] jfcooley:
Everything smooth as silk with nightly Rootbox.

No issues at all.

Battery life at home has bee great. At work it will suck, but its due to the building I work in and signal.I'd go into airplane but I need it to pick up when I'm not in cooler/freezer. Always afraid something will happen and wife won't be able to get me.

Love this kernel. Been great since the first 3.0. Thank you, very much.
[Sprint Samsung Galaxy S III] samcintron:
Stable. I'm using LiquidSmooth 2.5.
[Sprint Samsung Galaxy S III] ilive12:
On the latest stable build with CM10.1 RC5. Running pretty well so far.

Sent via my AOSP-based 4.2 ROM, from my Galaxy S III (D2SPR)
[Sprint Samsung Galaxy S III] decimalman:
LS is always causing problems. Thanks for letting me know. :highfive: I'll look into it.
[Sprint Samsung Galaxy S III] nyles:
Ive been on 6/14 since yesterday. Everything is running great including bt. However, i can't seem to get my cpu max setting to stick. It was working fine on 6/11 with trickster, but not the slim performance setting. Now, neither the performance setting on the rom, or trickster is able to keep the cpu underclocked. It keeps reverting back to 1512. Any ideas? Thanks in advance.
[Sprint Samsung Galaxy S III] chris-allen:
Hey..this ie the smoothest kernal iv yet to use on 4.2.2.... i do have one question ..im not a noob but i dont mess with adjusting kernals and such.. My phone runs awsome at 1.7ghz but anything higher it locks up...should i adjust voltage also?? Or leave it?
[Sprint Samsung Galaxy S III] decimalman:
You'll need to manually increase the voltages for frequencies that are locking up. Be aware that dkp allows you to push more voltage across your processor than it was designed for. Small increases in voltage should be very safe--your processor might heat up a little faster than it would normally, but otherwise there shouldn't be any consequences. Larger increases could potentially do some damage, so dkp enforces a 1400 mV limit on voltage.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Yea I'd say bump up the voltage. I never have felt the need to overclock on this device. Just bump it up maybe 10-15mv slowly. Or I might have posted something I did that worked for an example.
[Sprint Samsung Galaxy S III] chris-allen:
Got it working now...i did a benchmark and got about 5600!+ @1.7ghz..

Sent from my SPH-L710 uk tsing xdapp-developers app
[Sprint Samsung Galaxy S III] ksmullins88:
LS has options that I cant find anywhere else!

But I flashed stable 6-14 and it hung on reboot really bad where I had to wipe everything and start over! I'm on LS 2.7 and I reverted to 6-11 test I'm about to try 6-14 test and see if it reboots properly!

Regardless, still my favorite kernel!
[Sprint Samsung Galaxy S III] decimalman:
Strange. I haven't been able to duplicate the boot issues. LS 2.5 and 2.7 are both booting fine for me on the 6-14 release. Any additional details that you or samcintron can provide (especially other kernels/boot splashes/whatever that you've flashed) would be greatly appreciated. I'll try to figure out what's going on, but it's pretty hard to track down early boot issues if I can't duplicate the issue. :(

As always, I appreciate the report. :good:
[Sprint Samsung Galaxy S III] Rxpert:
Getting nearly 10%/hr screen on time. Great job

But im always looking for more :cool: Any chance of being able to underclock the min?
[Sprint Samsung Galaxy S III] mikedavis120:
Why would you set your minimum frequency low? I would suggest you look at your voltages, no matter the processors speed value, the voltage the processor is pulling is what impacts battery life. Example, Your cpu voltages, if untouched by decimalman in whatever build your on, should start at 900mV @ 384mhz only steping +75mV's upto 702mhz. Now, I understand undervolting is not for all, and everyone's phones different, but, try to set your voltages for 384-648mhz all to 900mV's and then set your minimum speed to 648mhz. If your phone handles what mine is capable of, you should be able to run that fine, your processes trying to run at min speeds in the background will run twice as fast and that will net you even better battery life. Try cpu spy to see if your cpu is doing what your tellingn it and still getting to deep sleep mode.

You can nab the download for my zip file and watch my video in post 2 of this thread and you will be seeing 20 hours screen on time with 48+ hours of standy with low usage. Dont be afraid to undervolt. Just dont set the boot options till your sure the voltages work on your phone. Stability test apk is great for testing voltages.
[Sprint Samsung Galaxy S III] chris-allen:
Hey quick question.... Seems like the more i overclock, the laggier the device becomes? Not a big deal, just i like to show off to my freinds who own other decives.... Is there a reason for this or should i be adjusting something else along with the cpu speed? Btw im using cynogynen RC5 ...
[Sprint Samsung Galaxy S III] Rxpert:
I do have 1 bug to report. On both of the latest cm10.1 nightlies media stored on the device plays at full volume through headphones. You can only shut the volume off, or have it at 100%

ROM cm10.1 night lies

Music player: Google music

Music location: external sd

Played through: headphones

It works normally after a ROM flash til I flash the kernel. It also does not work normally with speakers