yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] The~Skater~187:
Take your time decimalman, you'll it figured out. We all appreciate everything you do and have done for our phones. Just remember, "goosefrabba" lol.

Sent From:

PAC-Man4.4.2/DKP/MK3 using Xparent Skyblue Tapatalk
[Sprint Samsung Galaxy S III] decimalman:
It turns out I only needed two trivial changes to get everything working. :)

There's a new AOSP build up on MediaFire. Changelog:

Synced with CM: tons of updates from CAF, also switched to the ND8 wifi driver

Re-enabled some GPU settings that disappeared a while ago

Rewrote my changes to the wifi driver to support the new code. If anything (wakelocks in particular) misbehaves, let me know.
[Sprint Samsung Galaxy S III] The~Skater~187:
Just flashed thus puppy, testing now. I'll keep you posted decimalman.

Edit: Been running the new AOSP kernel for a few hours now. Seems to be running flawless. No Wi-Fi or wakelock problems so far. Thanks again for the update. Love having the GPU settings back btw.

Sent From:

PAC-Man4.4.4/DKP/MK3/MD4 F/W using Xparent Skyblue Tapatalk
[Sprint Samsung Galaxy S III] akaTRAP:
DKP got updated?! MINE! ALL MINE! Must download and flash!!!!!

................actually I'm going to go back to TouchWiz first, bone stock, clean everything and then go back. Something in the past month made my phone go "NOPE!!" so I'm going to do the "cleanest" wipe I can think of.
[Sprint Samsung Galaxy S III] The~Skater~187:
Anyone have any voltage recommendations for overclocking? I keep getting reboots when trying to overclock to anything over 1620.

Sent From:

PAC-Man4.4.4/DKP/MK3 Radio/MD4 F/W using Xparent Skyblue Tapatalk
[Sprint Samsung Galaxy S III] decimalman:
Anyone feeling adventurous? This test build includes an update to BFQ and a fix for sluggish external SD performance (I'm seeing a 2x improvement according to some makeshift benchmarks). The SD fix might cause problems for some people, so feedback would be appreciated.

Don't trust the default voltage table. I just filled in some numbers and hoped for the best. ;) As a starting point, here's a portion of my voltage table (keep in mind that I'm undervolted, so you'll need to adjust the voltages to suit your processor):

1998mhz: 1325 mV

1944mhz: 1275 mV

1890mhz: 1237 mV

1836mhz: 1200 mV

1782mhz: 1175 mV

1728mhz: 1150 mV

1674mhz: 1125 mV

1620mhz: 1112 mV

1566mhz: 1087 mV

1512mhz: 1075 mV
[Sprint Samsung Galaxy S III] The~Skater~187:
I'll try the test build as soon as i get home tonight. Thanks for the voltage reference.

Sent From:

PAC-Man4.4.4/DKP/MK3 Radio/MD4 F/W using Xparent Skyblue Tapatalk
[Sprint Samsung Galaxy S III] techdog:
I was all ready to test it out. Started downloading and noticed that it was AOSP. Sigh... :'-(
[Sprint Samsung Galaxy S III] The~Skater~187:
Just flashed the test kernel. Took a bit longer to boot, but seems to be running good so far. I'll keep you posted

Sent From:

PAC-Man4.4.4/DKP/MK3 Radio/MD4 F/W using Xparent Skyblue Tapatalk
[Sprint Samsung Galaxy S III] decimalman:
I run AOSP 99% of the time, so most of the wildly experimental builds are for AOSP. FWIW, TW isn't affected by the change I made anyway.
[Sprint Samsung Galaxy S III] akaTRAP:
So uhm, the latest kernel is..... Uhm, pretty fing amazing for battery life. Just sayin.

EDIT: For some reason the pics didn't get posted. Hold on.
[Sprint Samsung Galaxy S III] akaTRAP:
There we go
[Sprint Samsung Galaxy S III] ksmullins88:
I'm feeling adventurous!! Downloading now. I'll report back tomorrow and let you know how it goes. I'm on the latest c-rom with lean kernel(only while I wait for dkp:D:thumbup: )

Thank you brother.

Which ROM are you running, if I may? Just curious

Sent from the MotorCity
[Sprint Samsung Galaxy S III] cfli1688c1:
I have another kernel flashed on vanir, can i just flash this kernel over top? thanks.
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
Yes. Wipe cache and Dalvik after flashing, before rebooting.

[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors

Charging still shot

n00b-xda-disciple's Wicked X Video review

Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
[Sprint Samsung Galaxy S III] ksmullins88:
Had a couple reboots using the test kernel, but it could be just me undervolting too much. I'll keep tinkering tho and see what happens. I love it though. Working well for me besides those hiccups. Batt life real good.

Sent from the MotorCity
[Sprint Samsung Galaxy S III] prboy1969:
That could be the cause. Every device is different. Some do not take well to being UV'd, or OC'd. Try loading the Stock Voltage Table, and reboot. After that lower it by 5mV at a time till you hit the sweet spot for your device.
[Sprint Samsung Galaxy S III] ReapersDeath:
Mass power related issues with this kernel.. Phone refuses to charge at an acceptable rate. Plugged in, went to sleep, woke up 8 hours later at only 33%. Restarted and slept one more hour, woke up at 77%. Having to occasionally restart my phone to fix charging is not for me..
[Sprint Samsung Galaxy S III] prboy1969:
Try switching Batteries, Chargers, and Cable. Also make sure that your Rom is solid.
[Sprint Samsung Galaxy S III] ReapersDeath:
Already did. Happened a couple times only on this kernel. Flashed it again, and no change. Still occasionally happened. Went to my old kernel and instantly stopped. I was using default configurations. Didn't install any tuning apps.
[Sprint Samsung Galaxy S III] prboy1969:
It could just be that your device doesn't agree with this particular Kernel. As mentioned before every device is different. Have you tried the Kernel with a different Rom ?
[Sprint Samsung Galaxy S III] TheKryptonite:
Amazing kernel.
[Sprint Samsung Galaxy S III] TheKryptonite:
Does anyone else's device freeze when you try to overclock it at a certain number?

Edit: It seems to freeze up on No,Frills, but it doesn't freeze up on Trickster. Also, it seems to reverts back to the original settings, though (if I overclock it to 1512000). This is the testing build.
[Sprint Samsung Galaxy S III] prboy1969:
Some devices cannot be OC'd past a certain point, if at all. As for the settings, make sure to set them to apply at Boot. Test them before you set them to apply at Boot.
[Sprint Samsung Galaxy S III] mudflap2.0:
just curious

I wonder what the highest clock decimalman ended up getting to stay stable, then play a graphic intense game with?
[Sprint Samsung Galaxy S III] :
Aware of Wi-fi not working on 07-05? My Wi-Fi toggle won't switch to on and is currently frozen.
[Sprint Samsung Galaxy S III] AlienFreek01:
Just to make sure... Cm10.2.1 stable works on this right?
[Sprint Samsung Galaxy S III] bmeek:
The dkp kernel would need to be updated to support WiFi on ROMs built using cm11 nightly sources after 07/23.

---------- Post added at 10:26 PM ---------- Previous post was at 10:17 PM ----------

Decimalman hasn't been doing regular builds for AOSP v4.3-based ROMs for quite a while... You might find what you're looking for behind the link to "Really old builds" in the op.
[Sprint Samsung Galaxy S III] :
Sorry, noob to the thread. Just rooted my d2spr a few days ago.
[Sprint Samsung Galaxy S III] bmeek:
No need to apologize. I just discovered this on Thursday with my d2vzw running the d2lte versions of cm11 and the dkp kernel...

I was checking this thread to see if decimalman had made any comments (he originally created separate xda discussions for each of the GS3 variants, which seems unfortunate since the unified builds for "d2lte" devices began back in February).
[Sprint Samsung Galaxy S III] decimalman:
I finally got everything merged and working again (some weird compiler misbehavior was preventing everything from building), and there's a new AOSP build up on MediaFire. Changelog:

Merged everything from CM. This includes changes to the wifi driver that probably won't work on ROMs before 7/23!

Linux 3.4.99 and BFQ v7r5
[Sprint Samsung Galaxy S III] :
Dude! Phenomenal work on this kernel! Getting better battery life then my extended battery gets me!
[Sprint Samsung Galaxy S III] decimalman:
[MENTION=5809926]mudflap2.0[/MENTION]: So I was playing with GPU OC tonight, and it looks like I'm finally getting somewhere. :D I haven't tried any actual gaming yet, but synthetic benchmarks are finally showing performance improvements.

I'm a little surprised by how well the GPU handles overclocking. Even pushing it to 600 MHz doesn't seem to cause instability or glitches. I don't know how fast the GPU can actually run, but I'll continue to experiment. In spite of the supposed memory bandwidth bottleneck, it looks like performance should continue to improve if I push the frequency higher.

If you're running a recent AOSP build (i.e. one that works with the 7/26 dkp build), there's a test build on MediaFire. It has 480, 533, and 600 MHz frequencies available in Trickster, but still defaults to 400 MHz.
[Sprint Samsung Galaxy S III] decimalman:
No problem. I haven't really seen anyone complaining about it, but as a kernel dev I tend to hear about these things by PM a bit more than everyone else. 3.4 definitely had its problems when it first came out, but all the major issues that affected lots of users have been fixed. Now it's just the crazy problems that affect an unlucky 1% or so. :(
[Sprint Samsung Galaxy S III] das_webos_transformer:
So make freelunch default gov ? I'd be happy :)
[Sprint Samsung Galaxy S III] grifforama:
current stable (04/24) for 3.4 does not boot on Liquid Smooth.
[Sprint Samsung Galaxy S III] decimalman:
Liquid still doesn't have the new CM video driver commits. The 4/8 test build is the most recent kernel that will work with it.
[Sprint Samsung Galaxy S III] grifforama:
Actually, the 4/17 Linaro 481 build is working perfectly for me without issue. It's the most stable combination of anything I've run on this phone. So thanks for that....

:)
[Sprint Samsung Galaxy S III] decimalman:
Derp. That's the build I meant. I guess I've been looking at the stable downloads page too much if I'm mixing up the dates. Glad to hear it's working well. :highfive:
[Sprint Samsung Galaxy S III] das_webos_transformer:
Video drivers got merged 4/18 I think so anything before that will work. Onto the real reason I'm posting, I've had my drop onto 1x constantly, like just bad. Airplane toggle will fix and toggleing late will fix. I think there was an issue with data on the 4/19 nightly, so I have reason to believed it may be kernel related. I'm on black PAC, might also be a factor. I'm gonna flash again and go back to the included one(nandroids are for noobz :p) but I've had killllller battery life with freelunch

Edit

Could settings are troublesome to stick, that's the problem
[Sprint Samsung Galaxy S III] jfcooley:
Went back to tw for a bit, drove me crazy.

So back with this. Nanolunch? How is this different than freelunch?
[Sprint Samsung Galaxy S III] decimalman:
Welcome back!

nanolunch uses much more precise CPU load statistics. Otherwise, it's basically the same. To my eyes, it's considerably smoother.

In other news:

Crazy test builds are going up soon! If you flash, expect bugs and be prepared to flash an old version! I only just got wifi working again (took 3 days to track down the issue :(), and I expect more issues to show up.

Changes:

Link-time optimization! I expect this to cause problems, but I think I've sorted most of the crazy bugs out already.

Fancy new toolchain with the latest Linaro and GCC commits

Linux 3.4.43 and CM's latest commits

A few odd fixes and cleanups

Edit: My build script blew up, so this round of test builds is using the old naming system. Sorry for the inconvenience.

Edit 2: Fixed my build script and rebuilt using the right toolchain. New builds are up.
[Sprint Samsung Galaxy S III] jfcooley:
Running 5/1 test build on a carbon nightly. Really happy right now. Thanks.
[Sprint Samsung Galaxy S III] das_webos_transformer:
Also running it, I'm on liquid 2.3 and I'm happy. Had to get something good on battery life and stable, camping this weekend. :good:

On 5/1 screen flashineg on messaging and lock screen. Kinda pretty.
[Sprint Samsung Galaxy S III] nikolkang:
Rocking your test kernel with nanolunch and row. No issues so far and its been great!

Good work on this! Performs fast with excellent battery life. Running Tasks AOKP.
[Sprint Samsung Galaxy S III] nikolkang:
So far so good...
[Sprint Samsung Galaxy S III] decimalman:
faux updated the sound control interface. The new update isn't actually written for d2 devices, but I merged it anyway. New builds are going up now.

The builds also include a new toy I threw together earlier this evening. I'm calling it "auto-auto-hotplug." If you have mpdecision running, it'll let mpdecision do its thing. If you disable mpdecision (or are running task's AOKP), auto-hotplug takes over. If you set Trickster to apply at boot, it should work perfectly, but if you decide to switch later you'll need to change governors before everything will get sorted out. I've only given this 5 minutes of testing, so let me know if it gives you trouble.
[Sprint Samsung Galaxy S III] jfcooley:
Just throwing this out to see if anyone else has had it happen. Getting what was described on the GNex forums as "Black Screen of Death".

Running latest test build on Carbon Nightly.

Could be either ROM or kernel. Battery and every thing else is so good I don't think I mind.

Happens when I turn screen off with power and try to wake again quickly. Random it seems.
[Sprint Samsung Galaxy S III] nikolkang:
I have had this happen but on multiple kernels and aosp ROMs so I wouldn't say it is related to dkp kernel.

More so an aosp bug that's been present for sometime now.
[Sprint Samsung Galaxy S III] Jimmy_Christ:
I've seen that across multiple kernels as well. Usually if I've set my screen off profile too low.

Sent from a van down by the river.
[Sprint Samsung Galaxy S III] jfcooley:
No problems since updating Carbon. I noticed they mention a power button issue for d2sp in change log.

I had this problem with the GNex, but this was the first time with the S3 across several aosp ROMs.

Doesn't matter now. Kernel running great.
[Sprint Samsung Galaxy S III] Chocobubba:
I'm having trouble getting this working on CM10.1, If I flash the latest stable 3.4 version, it gets to the boot animation then freezes, (even with the v-min zip) and if I flash the 3.0 version, it doesn't even make it take far.
[Sprint Samsung Galaxy S III] nikolkang:
Not sure why it won't boot for you... but just to clarify really quick, the 3.0 version is not compatible with latest cm10.1 builds. What nightly of CM are you running?

If I were you I would try the latest test version. I know that on or around 4/19 cm merged new video changes with the 3.4 kernel. My guess is the latest DKP stable was previous to that driver change??? I'm only guessing so someone else will want to chime in.

Anyway, I have had zero issues with the latest test version for 1 week now. And quite honestly... I have never had battery life like this without UI lag.. whatever you are doing decman keep it up. :good:
[Sprint Samsung Galaxy S III] remotehugger:
man I miss your TW kernel - lol -

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Sprint Samsung Galaxy S III] Joffie87:
Hey there. I'm using your kernel on the VM GS3, and lately I've been having this issue where my cpu will ramp down to anywhere between 500-700mhz on both cores, and then regardless of load on the cpu or length of time, it will not go above that amount without a reboot. Am I missing some setting somewhere that's important? Using Kernel Tweaker in AICP rom. Thanks.
[Sprint Samsung Galaxy S III] beezie42:
Trying out the gpu overclock on the test kernel. Seems to work well, but is there anyway to adjust the voltage to the gpu?
[Sprint Samsung Galaxy S III] decimalman:
I really need to get back to work on TW. It's been entirely too long since the last updates, and I still haven't gotten much done on 4.4. :(

Strange. What governor are you using? I don't think there's a setting that would cause that, and it's much too low to be something like the thermal throttle.

LOL I'm pretty sure the 800 still performs better. OC might help, but it won't compare to a fancier architecture.

Last night, I tried to push it further, but even 667 MHz crashed instantly. I'll continue to look into it, but 600 MHz is already a huge overclock. If I ever figure out how to adjust the GPU voltage, it should help stabilize things.

Not yet. I haven't been able to track down how the GPU voltage is actually controlled. I'm sure I'm overlooking something obvious.

I'm currently working on a few ideas to better control the GPU frequency, which should both save battery and reduce heat. I was hoping to get a new test build out tonight, but then I got carried away and started writing a new GPU governor instead. Oops. :p
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
I had to laugh at that!

[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors

Charging still shot

Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v6.3, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
[Sprint Samsung Galaxy S III] Joffie87:
I've tried several governors, asswax, freelunch, interactive, intelliactive, ondemand, and performance. BTW, I switched to the gpu oc test kernel, and I still get the issue, but oc works fine up to 533 for me. Above that and I get freezing and fc's. Out of curiosity, are the temp settings modifiable so I can check?
[Sprint Samsung Galaxy S III] mudflap2.0:
Yeah I was expecting that, seemed to be unstable at 600, games would freeze at what seemed like minutes at a time then resume like noting happened, even Apps force closed, If e GPU crashes, it's much different than the CPU, because if the CPU gets oc'd I high then instant reboot, but at 600 when it works it seemed to be amazing, dead trigger ran at tegra 4 graphics, on this phone like it was ment to play on it, try bumping up the voltage to stabilize 600, or 533, because this is awesome

---------- Post added at 11:06 PM ---------- Previous post was at 11:01 PM ----------

Now I don't want to seem like I'm being a jerk, but why have 2.1 GHz as an option to have, if it is seemingly impossible to even run for a second let alone 30, even if you did manage to stay at that, Games wouldn't play, so is this an illusion of choice decimalman?, I don't want to come off as complaining as I love your work and would send you something if I knew your P.O box, but nobody seemed to explain this to me!
[Sprint Samsung Galaxy S III] decimalman:
Hmm. The most obvious cause would be something changing your CPU limits behind your back (intellidemand and the thermal throttle are known to do this, though they usually don't leave the limits lowered). Some tuner apps can mostly disable the thermal throttle (Trickster can, I'm not sure about other apps), but IIRC the throttle doesn't have any configurable settings.

It's getting late, but if I get a chance tomorrow, I'll send you a build with a lot of extra debug stuff added. It should help to track down whatever is causing issues.

I grabbed a few games tonight, and I'm having some issues with 600 MHz as well. Funny that benchmarks designed to stress the GPU didn't crash it, but games do. :( Oh well. GPU OC is still a work in progress, and the build from the other night was just the first of many test builds. In no particular order, here's what needs to happen before I'm comfortable calling it "stable":

Making sure things are stable. Clearly, 600 MHz has some issues. :( I just made a small change on a hunch, and 2 minutes of testing suggests that it might have helped, but we'll see.

Adding voltage controls. This should help stabilize higher frequencies, and GPU undervolting has been requested a few times now. Unfortunately, the usual method of tweaking voltages doesn't seem to apply to the GPU. :confused:

Fixing frequency scaling. Especially when overclocking, high frequencies are used too much for my liking. The GPU is rumored to be pretty power-efficient when it's idle, but I'd like to see what happens when lower frequencies are used more often.

Once I give the frequency scaling changes a little more testing, I'll release another test build.

Regarding 2.1 GHz, I don't want to put arbitrary limits on the settings available. My phone can just barely handle 2.0 GHz, so I assume that somewhere out there, there's a phone that can handle 2.1 GHz. I can't imagine why anyone would overclock that far, except to squeeze the absolute highest possible benchmark out of their phone. For everyday use, there's no reason to bother overclocking past 1.7 or 1.8 GHz anyway, since performance doesn't improve much after that.
[Sprint Samsung Galaxy S III] mudflap2.0:
I wonder how you managed 2.0ghz?, did you run antutu at that clock. Highest I managed with this phone was 1.89ghz, on ktoonez and overvolted,but it was useless because all APS force closed on that clock, [MENTION=4149147]1.8[/MENTION]3, things seemed more stable, but intensive APps force closed, like benchmarks, 1.78@1400mv seems to be the sweetspot, as for changing voltage for GPU, it may be that the CPU and GPU share voltage, it seems if I max out at 1400mv on 1780mhz, the GPU seemed more stable on demanding games like dead trigger and dead trigger 2

, because none of the freezing for minutes at a time seemed to happen, hope I help!

---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------

I don't know if there is a rivalry between you and ktoonez, but if you guys worked together and you tell him about GPU oc, maybe ther'll be a future?

---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------

Oh and while at 2ghz, how long did it stay on before it rebooted, did some APps force close, did you have any errors, run any benchmarks, I'm really fascinated about what you accomplished, if I knew about kernels I would call it red hot, cuz I'll I want is the fastest, well right now I'm running 1.78ghz@ 1400mv, gpu@600mhz, disable qualcom safety thingy majingie, and thermal throttling, no dev options enabled, and both CPU and GPU [MENTION=616579]performance[/MENTION] ,But quadrant still seems To think its slower than tegra 3 HTC one x, hmm dunno why, but used trickster mod

---------- Post added at 02:46 AM ---------- Previous post was at 02:37 AM ----------

Hey, do you guys hear a high pitched sound (very very low yet audible) when you put your ear against the micro USB port of your phone?(in a quiet room) I know its out of the blue, but if it seems so(and leave the phone for a while next to the ear, or you won't hear it!) , let a mod move this post!
[Sprint Samsung Galaxy S III] mudflap2.0:
And what ROM do you use dkp?, currently in on the 28nightly of cm(d2lte), thanks for answering my questions Bro!!, you one of the true devs that seem to always bring a smile on my face!, right now my phone is really stable@1.78 all day on performance with 600mhz, anymore, and problems arise. As for your 2.0ghz n front of the A/c, what that necessary?, if the phone gets to hot, do force closes and reboots normally happen?, I didn't think temperature had anything to do with the stability of a clock, obviously I know when it becomes to hot to bear with bear hands it's time to shut down and Cool down, as of now I can afford I run at performance ask day because of my 7000mah extended battery, just can't seem to kill it in one day, and it doesn't even get that hot as opposed to the stock battery, well good luck, and see if bumping up CPU voltage up seems I stabilize GPU, because it somehow does for me