yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] shekinahsmoke:
Newest one didnt boot for me :( sorry .. it stuck on the splash screen for a loooong time.
[Sprint Samsung Galaxy S III] Swamphound:
Test 10/9 will not boot. Does not get past gs3 splash. I only had Killjoy mod running and and uninstalled/rebooted prior to flashing 10/9. I apologize but I've never posted a last_kmsg or kernel logcat and am at work but will bone up and post asap. Question: if the phone did not boot will a log even be possible?
[Sprint Samsung Galaxy S III] iamikon:
Did you wipe caches and fix permissions?
[Sprint Samsung Galaxy S III] shekinahsmoke:
wiped caches... didnt fix permissions tho...
[Sprint Samsung Galaxy S III] twister99403:
latest didn't boot for me either and yes wiped and fixed permissions
[Sprint Samsung Galaxy S III] decimalman:
Ugh, I only changed two lines of code! I'll look into it tonight.
[Sprint 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.
[Sprint Samsung Galaxy S III] shekinahsmoke:
here we go [insert budweiser gif]

just as a help.. i'd remove the one that doesn't boot... :D
[Sprint Samsung Galaxy S III] Swamphound:
Newest build seems to be doing well. Uninstalled KilljoyRC7>reboot>flashed 10/9(redux)>wiped cache/dalvik>fixed permissions>reboot>flashed Killjoy>reboot>enabled KJ>set trickster colours @20.

If any of these steps are unnecessary please let me know.
[Sprint Samsung Galaxy S III] shekinahsmoke:
so i did all this... this looks like this will be awesome.... :good:

[MENTION=4932679]decimalman[/MENTION] .... does this/could you include init.d support for this kernel?
[Sprint Samsung Galaxy S III] decimalman:
dkp itself doesn't include init.d support. If you flash it over another kernel that does (perhaps freeza's excellent stock optimized kernel?), init.d support and any other ramdisk goodies will carry over.
[Sprint Samsung Galaxy S III] davelikestacos:
So anyone have any IMEI wipe issues with the latest TW or AOSP kernel?

Last time I flashed an older build of this it wiped my IMEI and I could not activate my phone.
[Sprint Samsung Galaxy S III] twister99403:
No but if your worried do an NVBACKUP before you do any flashing :)
[Sprint Samsung Galaxy S III] shekinahsmoke:
anybody else's phone taking three taps to respond to touch?
[Sprint Samsung Galaxy S III] Swamphound:
Not me, but as I posted earlier I did have a IMEI wipe issue too. Definitely do an NV backup. It saved my a**!
[Sprint Samsung Galaxy S III] wilderckw:
I have a weird issue using the TW test build. I set my gov. To freelunch and min 384 and max to 1512 and it keeps going back to 1134 right away. Any suggestions? Thanks
[Sprint Samsung Galaxy S III] davelikestacos:
Did you edit the governor's max speed to 1512 in the governor options?
[Sprint Samsung Galaxy S III] decimalman:
Which frequency is changing?

If it's the minimum frequency, it's a known issue that AFAIK affects all TW kernels. 384 is actually applied, but it displays wrong in apps. I haven't found an elegant way of fixing it yet.

If it's the maximum frequency, I'm more concerned. It doesn't sound like the thermal throttle. What ROM are you running? A few include scripts intended to save battery, which might be changing your frequencies. What files are in /system/etc/init.d?

EDIT: Looks like I forgot a few people.

[MENTION=5055816]davelikestacos[/MENTION]: Do an nvbackup--one day, you'll be glad you did.

[MENTION=3836275]shekinahsmoke[/MENTION]: Is the triple-tap thing consistent when you're running a particular build? If so, which?
[Sprint Samsung Galaxy S III] shekinahsmoke:
Im running Dandroid 3.9.5.... just started when using the new test kernel.. MAYBE user error... but it's happening when installing/updating apps and tapping on widgets
[Sprint Samsung Galaxy S III] twister99403:
Mine is doing the same on Wicked Sensations :)
[Sprint Samsung Galaxy S III] wilderckw:
It's the max. I'm running wicked 5.0..ill look in the folder
[Sprint Samsung Galaxy S III] davelikestacos:
I did an EFS Backup with Andromizer. I'm guessing that's the same thing as using the NVBACKUP method?

Last time it happened, I had no idea what to do. My phone would not activate through Sprint's network no matter what I did. So I flashed the stock unrooted tar through odin and used Triangle Away to reset my flash counter before bringing the phone to Sprint and paying $50 for a new GS3.

Basically, I just wanna make sure that an EFS Backup through Andromizer is enough to keep this from happening again.

EDIT: Flashed 9/26 with no issues :) Is there anyway to get the GPU overclock to stick? If I try to set it to 480, it reverts back to 400.
[Sprint Samsung Galaxy S III] tlrsax54:
Hmm...maybe I'm doing it wrong but latest test kernel on MOAR can't seem to replicate this triple tap thing...everything is fine here!
[Sprint Samsung Galaxy S III] davelikestacos:
I can second what was said here. Although, my "max" doesn't revert to 1134 right away. At some point it does, but if I relaunch Trickster after setting my min/max, it'll still say 1512 but if I check it later, it'll revert to 1134. Running the latest TW test kernel and it's running smooth as butter, especially considering it's setting my max to 1134 constantly. Interactive Governor and SIO i/o, if that makes a difference.
[Sprint Samsung Galaxy S III] decimalman:
I haven't been running TW enough to reproduce the triple-tap bug or track down what would be changing the maximum frequency, but there's a new TW test build going up anyway.

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.
[Sprint Samsung Galaxy S III] shekinahsmoke:
why are you so awesome???
[Sprint Samsung Galaxy S III] davelikestacos:
Anyone to get GPU over clocking to stick? Trying to change my GPU speed to 480mhz but it keeps reverting to 400.
[Sprint Samsung Galaxy S III] decimalman:
GPU OC isn't supported. I'm not sure why Trickster shows a 480 MHz setting.
[Sprint Samsung Galaxy S III] davelikestacos:
Bummer, I really like the GPU OC options of LK and Anthrax.
[Sprint Samsung Galaxy S III] iamikon:
Latest release seems less stable than the last ones. I've had some lock ups that force me to hard reboot. Not quite sure what it is yet but only difference is the new test kernel (tw)
[Sprint Samsung Galaxy S III] decimalman:
I didn't expect it to be completely stable. The Linux update was just too big for everything to work perfectly. I'm distracted by another project at the moment, but eventually I'll flash over and try to track the lockups down.
[Sprint Samsung Galaxy S III] Naddict:
FWIW, yes, I have noticed some "freezing" even if temporary, too. not a huge deal, still love the product and the battery life. Thanks
[Sprint Samsung Galaxy S III] shekinahsmoke:
I'm running a never ending logcat so if I get any freezing I can provide you with a source
[Sprint Samsung Galaxy S III] shekinahsmoke:
Here you are ... Entire UI froze upon entering My Cloud Player app from lockscreen .

It's overheating too btw.
[Sprint Samsung Galaxy S III] dannyboyex:
Rough start at first (hard freezing) but now it's working fine. Latest TW test build
[Sprint Samsung Galaxy S III] Swamphound:
Couple freezes here as well with new TW test. Nothing earth shattering but definitely not as smooth.
[Sprint Samsung Galaxy S III] davelikestacos:
So on the 10/09 TW build, if I set the max to anything above stock 1512 in trickster, it reverts it back to 1134. Set it to 1728, hit apply, close trickster, reopen and it's set to 1134 :\
[Sprint Samsung Galaxy S III] iamikon:
I've noticed battery took quite a hit too. I'll go back a version until you get the time to fix it :)
[Sprint Samsung Galaxy S III] davelikestacos:
Well, I switched to Android Tuner and my 1728 OC stuck. Looks like Trickster is responsible for reverting anything over 1512 back to 1134. Weird. Very stable at 1728 using MetalROM + 10/09 TW build :)
[Sprint 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
[Sprint Samsung Galaxy S III] iamikon:
[MENTION=4932679]decimalman[/MENTION] I can't get this build to boot. When the kernel boot image is supposed to come up I just get black screen that never goes away. I can get you a logcat if you need it.
[Sprint Samsung Galaxy S III] azdragon:
I can confirm the "black screen of death" problem described above.

Thanks for all your hard work!
[Sprint Samsung Galaxy S III] decimalman:
Sorry for the delay. I've been preoccupied with getting Omni running.

Hanging before the boot splash sounds like the installer ate your ramdisk, which shouldn't be happening anymore. What ROM are you guys running? Are you flashing over another kernel?
[Sprint Samsung Galaxy S III] davelikestacos:
I can attest to the 10/20 build working lovely on Carbon 10/20.
[Sprint Samsung Galaxy S III] iamikon:
I was running cnexus aokp but also tried on slim and carbon
[Sprint Samsung Galaxy S III] azdragon:
I'm running latest Slim build 1.9
[Sprint Samsung Galaxy S III] WindowsSucks:
Slim 1.9 won't boot the 10/20 kernel. It was synced and built right before the cm repo was synced. Next question what kernel did you flash it over?

Sent from my SPH-L710 using Xparent BlueTapatalk 2

---------- Post added at 06:37 PM ---------- Previous post was at 06:37 PM ----------

Sent from my SPH-L710 using Xparent BlueTapatalk 2
[Sprint 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.

I'm pretty sure CNexus's AOKP and Carbon should have updated drivers, so that shouldn't be a factor. I'll grab them and see what's going on.

EDIT: CNexus is using AOKP's kernel, which doesn't follow CM as closely. It doesn't look like it has the driver updates.
[Sprint Samsung Galaxy S III] iamikon:
I figured they would be too so I was not sure why it wouldn't boot. If you need any troubleshooting just give me a holler. Its rather easy for me to get logcats of boots etc.
[Sprint Samsung Galaxy S III] decimalman:
I think I tracked down the issue causing underclocking to get unstable. I've been running a minimum frequency of 54 MHz (at 725 mV!) for a few days now, without any obvious stability problems. Signal around here is awful, so I can't tell whether battery life has improved.

New 4.3 test builds are coming out. Feedback is appreciated, especially if extreme underclocking is unstable.

Changelog:

Underclocking (finally) added

Slightly tweaked freelunch defaults to work better when underclocked. Note that increasing overestimate_khz may prevent freelunch from using your lowest frequency.

Synced with CM, updated to Linux 3.4.67

Updated toolchain. I still haven't put my compiler laboratory back together, so it's still vanilla Linaro.

EDIT: Looks like I forgot to merge in the updated freelunch tunings. Oops.
[Sprint Samsung Galaxy S III] Circaflex:
So far its been good over 24 hours my phone hates under clocking too much so im still messing with that
[Sprint Samsung Galaxy S III] iamikon:
[MENTION=4932679]decimalman[/MENTION] would you post the updated free lunch tunables?
[Sprint Samsung Galaxy S III] decimalman:
Here's the settings I've been using:

hispeed_decrease decreased to 60000

interaction_hispeed decreased to 1080000

interaction_overestimate_khz increased to 225000

interaction_return_cycles increased to 6

interaction_return_usage increased to 175000
[Sprint Samsung Galaxy S III] TexasLTE:
decimalman - please confirm which of your kernels is the most recent that WILL work with ROMs that have most recent CM changes ( such as AoCP 6.4 ) ... 10/27 test ? or go with 9/20 Stable ? THANKS
[Sprint Samsung Galaxy S III] iamikon:
[MENTION=3938519]TexasLTE[/MENTION] if they have the recent cm changes then you need the most recent version. I know slimbean does not include the cm driver changes yet so you would want an older version for that.
[Sprint Samsung Galaxy S III] TexasLTE:
so for Slim I want to use 9/20 but for AoCP I want 10/27 ... correct ?
[Sprint Samsung Galaxy S III] iamikon:
I would download them both just in case but AFAIK yes that's right. I haven't followed aocp so I'm not sure what they have merged.
[Sprint Samsung Galaxy S III] TexasLTE:
What settings are most folks using ( I know every phone is a little different ) as far as Governor / I/O ?
[Sprint Samsung Galaxy S III] iamikon:
On AOSP I like noop/free lunch but I usually run noop/conservative lately.
[Sprint Samsung Galaxy S III] jhuff83:
[MENTION=4932679]decimalman[/MENTION], I just flashed your kernel and hope to get some great battery life. I changed the settings to mirror these on freelunch. Do I need to leave the frequency lock off for free lunch to still do its thing? I ask because when I rebooted the phone the frequency reverted back to 1512min and 1512max.
[Sprint Samsung Galaxy S III] joeyddr:
The latest testing I get reboots using latest liquid smooth, I was using the 9/20 but I can't use that anymore with the ROM, is the testing one undervolted?
[Sprint Samsung Galaxy S III] 1BadWolf:
You mean the 10/27 build, no? I've been running it since yesterday on the latest liquid smooth. The only time I had any problem was I tried to under volt too much and it rebooted. So I just reverted back to stock voltages and it's been golden ever since.

If I had a dollar for every time I said that, I'd be making money in a very weird way.
[Sprint Samsung Galaxy S III] joeyddr:
Not sure what's going on then.... Last version of liquid (2.10) with the 9/24 testing kernel everything was solid.
[Sprint Samsung Galaxy S III] 1BadWolf:
Yup, that's the same setup I had until updating everything yesterday. I clean flashed everything.

If I had a dollar for every time I said that, I'd be making money in a very weird way.
[Sprint Samsung Galaxy S III] jhuff83:
I'm getting some crackle on my sound without even undervolting now. On freelunch governor. I changed my tunable tables to what decimal did. Could that be the issue?
[Sprint Samsung Galaxy S III] jfcooley:
And that would explain it.

I'd blame my daughter being sick, or the 3 months of 6 day work weeks, but I'm afraid it was just stupidity that made me miss that.

My bad...
[Sprint Samsung Galaxy S III] decimalman:
I doubt it's stupidity. I know a thing or two about 6 day work weeks, and a sick kid on top of that leaves very little time (or brain power :p) for compulsive flashing. Hope your daughter gets better soon.
[Sprint Samsung Galaxy S III] shane6374:
Just wanted to comment that this kernel has given me the best battery life I've seen on this phone. The bad is the freezing. It seems to happen a few times a day to me on Carbon ROM.
[Sprint Samsung Galaxy S III] decimalman:
I haven't experienced any freezes on Carbon, but I'll try to figure out what's happening. What Carbon version? Kernel version? Anything seem to trigger the freezes, or do they happen completely at random? If possible, can you PM me a logcat and/or last_kmsg?

Have you had issues on other kernels? If so, your phone may not like the lower voltage table that custom kernels use, and flashing dkp-enable-vmin.zip from the OP should help.
[Sprint Samsung Galaxy S III] Android Attack:
Hey mate, just flashed dkp and I'm looking forward to running it for a bit. Thanks for the contribution! Do you have any free apps you can suggest that will manage this kernel well? I'm looking for a fast charge option, as Slim Bean does not have this built in. Thanks!
[Sprint Samsung Galaxy S III] decimalman:
TBH, most of the apps I've tried don't work as well as I'd like. Trickster MOD has a fast charge setting but doesn't work well otherwise. ROM Toolbox works nicely, except that it doesn't have an easy way to toggle fast charge (you can enter "ffc" into its terminal emulator, but it's not very convenient). Kernel Tuner does have a fast charge setting, but I don't recommend using it to set frequencies or letting it apply settings on boot.

Edit: tested Trickster a little more thoroughly and am not as impressed as I was. I'll have to try to figure out why it's acting strangely, since I really like it otherwise.

Edit 2: newest 3.4 builds have several fixes that improve support for Trickster. Overclocking, undervolting, and toggling minimum voltage are all supported. I like Trickster more than the other apps I've tried, so I'll try to support it whenever possible.
[Sprint Samsung Galaxy S III] Android Attack:
I've been experiencing with Trickster MOD and it seems to be working pretty well. Just one problem (not related to Trickster MOD): I am unable to charge while the device is turned off. I get the battery icon for a minute, then the LED Light goes off and the battery disappears.

ROM: Slim 4.2.2 v3.

I flashed dkp-release-d2spr-20130303.zip

Thanks mate!
[Sprint Samsung Galaxy S III] decimalman:
I'll look into that. I think a few other kernels had the same issue, and I don't remember what the fix is.
[Sprint Samsung Galaxy S III] decimalman:
I'm guessing you're running Carbon nightlies with a 3.4 kernel? If so, I'd recommend going back to experimental-1365096985 or earlier. Now that I'm not flashing a new build every 10 minutes, I'm seeing sleep of death issues continuously. Newer builds have a few CM commits that probably require ROM support, and a few changes of my own that may have unexpected consequences. I'm investigating now.

Edit: just wiped data, and haven't had any issues yet, even with newest kernel builds. I think this is a Carbon issue.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Hey, have looked into dropping the lowest frquencie? Might nudge battery life a little less

There's more than corn in Indiana!
[Sprint Samsung Galaxy S III] decimalman:
It's on my list of interesting ideas, but I'm not sure when I'll have code ready to test. I'm have some reservations about the code used in other kernels. YGPM.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Good luck!

There's more than corn in Indiana!
[Sprint Samsung Galaxy S III] decimalman:
Long-overdue releases are up for 3.0 and 3.4! :victory: Downloads in OP, changelogs in post #2.

Happy flashing!
[Sprint Samsung Galaxy S III] das_webos_transformer:
So what's this faux sound all about? Is there an app I can use?

There's more than corn in Indiana!
[Sprint Samsung Galaxy S III] decimalman:
There's a paid app in the market. It allows better control of sound hardware than Android has otherwise.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Ohhh thanks

There's more than corn in Indiana!
[Sprint Samsung Galaxy S III] Alias8818:
I've been testing the experimental 3.4s, just flashed your release.

Excellent job. All are working well.
[Sprint Samsung Galaxy S III] Papa Smurf151:
FYI...the 3.4 kernel works on pacman nightlies too. If you wish to update your op

Great work BTW...I'm loving the free lunch governor.

XDA Moderator
[Sprint Samsung Galaxy S III] decimalman:
Will do! I need to give PAC-Man a try. :)
[Sprint Samsung Galaxy S III] Papa Smurf151:
Wait till tomorrow...nightlies were broken but are fixed now and newest version starts up tomorrow morning

XDA Moderator
[Sprint Samsung Galaxy S III] Super Dave426:
I am running MOAR 6.1 and your kernel was suggested by the dev so I have been using the "dkp-tw41 2013-09-26 stable.zip" build. The problem I had yesterday was that I had a 2 hour road trip yesterday and ran Waze for the Police notifications but every time I tried to turn on phone rotation so I could landscape the phone it would be upside down. No matter what I did, even locking the rotation using Nova, the GPS would always flip, so I had to flash the stock kernel back. Things were working good until I needed rotation, something I hardly use, anyone else have this issue? Samsung GS3 with MOAR 6.1. Any ideas why it happened?
[Sprint Samsung Galaxy S III] HashTagHell:
I'm using the same setup as it was suggested and have not had this issue at all. All of my rotations work properly. Are you sure it isn't the app itself? Have you tried clearing data for the Waze app? Remember, all devices respond differently to certain mods.
[Sprint Samsung Galaxy S III] Super Dave426:
No it wasn't just Waze, Waze was the reason I turned on rotation. The entire phone was upside down, but with Nova I locked it in landscape but Waze over rode the lock and flipped upside down, so did Google Nav.
[Sprint Samsung Galaxy S III] HashTagHell:
That is strange. I'm using the same kernel, with no issues.
[Sprint Samsung Galaxy S III] decimalman:
Silly question, but are you sure you were using the d2spr build? The zip's md5 should be 3dbc4a6409c24cbbbcd6235f5d6f6412. The sensor for screen rotation on the Sprint S3 is different from other variants, so if you're running a kernel configured for another variant, rotation will be backward.
[Sprint Samsung Galaxy S III] Super Dave426:
I don't know now so I downloaded it again and will give it another shot after TiBU finishes backing up to DropBox.
[Sprint Samsung Galaxy S III] jhuff83:
I'm running Moar and continue to have problems with crackling sound. I'm not doing any undervolting whatsoever and running free lunch. I'm on stable 9-26. Any suggestions.
[Sprint Samsung Galaxy S III] decimalman:
I would guess that this is caused by the lowered voltage limits dkp uses. If other custom kernels do it too, that's most likely the cause. Flashing dkp-enable-vmin.zip from the OP will restore the stock kernel's limits, which (hopefully) will fix the crackling.

EDIT: Sorry for taking ages to respond. :(

EDIT 2: Sounds like this isn't the problem. I'm flashing over to TW to look into it.
[Sprint Samsung Galaxy S III] jhuff83:
No problem on the response time. I would really love to use this w/o the crackling since so many people are raving about it. Let me know what you find out. I flashed fresh 6.1 moar but I'm on stock kernel for right now.
[Sprint Samsung Galaxy S III] decimalman:
A few people have reported "static" or "crackling" audio on the TW builds. I haven't been able to reproduce this, so if anyone is having issues, a logcat and dmesg would be helpful to track the issue down.

I happened to notice that TW is a month behind AOSP features-wise, so clearly it's time for a new test build. There's also a new (hopefully) stable build for AOSP on its way.

TW Changelog:

Reverted the huge Linux update. I haven't tracked down why it breaks everything, so it's back to 3.0.31 for now.

Enabled underclocking down to 54 MHz

Borrowed a few CAF fixes for major security holes

Updated freelunch to the current AOSP version

AOSP Changelog since last stable build:

Enabled underclocking down to 54 MHz

Added "color temperature" setting in Trickster

Updated freelunch

Linux 3.4.70, updates from CM
[Sprint Samsung Galaxy S III] jhuff83:
Any recommendations on how to get that logcat as far as a program?
[Sprint Samsung Galaxy S III] decimalman:
There's a few apps for getting a logcat. I use CatLog, but its interface is a bit clunky.

As for the dmesg, AFAIK there's not a decent app for it. If you have a terminal emulator app installed, "su -c dmesg >/storage/sdcard0/dmesg.txt" will save a log.