yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] TotallyAnxious:
I was using the same settings. Now I bumped the minimum cpu frequency up, to help with turning my phone on faster and now I'm on asswax. I tried all the governors on the 4/26 build, and they all seemed the same.
[Verizon Samsung Galaxy S III] decimalman:
I still haven't figured out what's causing the freezes that some people have been getting, but there's new builds going up anyway.

AOSP Changelog:

Linux 3.4.90, synced with CM

By request, added BFQ v7r3

Replaced erandom with something better :)

Shiny new GCC trunk (it's calling itself 4.10 now) toolchain

I left erandom enabled (/dev/erandom and /dev/frandom), but /dev/urandom, /dev/isaac, and most of the kernel's internal random functions now use ISAAC. Depending on how you measure, ISAAC is 30-1200% faster than erandom ever was. :) The ISAAC source is still pretty rough, but it's been working pretty well for me for a couple days now.

TW 4.3 Changelog:

By request, added BFQ v7r3
[Verizon Samsung Galaxy S III] remotehugger:
did you add ISAAC to the TW kernel also ?

From my Giddy Thrive
[Verizon Samsung Galaxy S III] decimalman:
Not yet, but soon.

Once I'm satisfied that everything is working correctly, I'll port it over. The code is only a couple days old, and hasn't seen much testing yet.
[Verizon Samsung Galaxy S III] remotehugger:
cool - thank you -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Verizon Samsung Galaxy S III] bass0324:
Do we still have to flash the min zip if we want to undervolt?
[Verizon Samsung Galaxy S III] bmeek:
Good question, and is it necessary if you're setting voltages using Trickster MOD? I've been mindlessly flashing it after dkp for ages.
[Verizon Samsung Galaxy S III] decimalman:
The vmin zip is still required.

Turning off Trickster's "Override Minimum Voltage" will accomplish the same thing.
[Verizon Samsung Galaxy S III] TotallyAnxious:
The new kernel fixed the freezing issue, completely stable the past 2 days. I also noticed you can't choose the interactive gpu governor, it resets to the previous gpu governor. Not an issue for me, just something I noticed.
[Verizon Samsung Galaxy S III] decimalman:
Great! I just wish I knew what was causing it to begin with. :confused:

I never actually added the interactive GPU governor, so I'm not sure why apps show it.
[Verizon Samsung Galaxy S III] metalcated:
Not sure if this is kernel related but from 5/20 cm11 nightly I have had some hellish issues booting with this kernel loaded... Also random reboots which go into a battery pull of hell. I loaded stock and it seems better now.
[Verizon Samsung Galaxy S III] bmeek:
FYI, the May 15 dkp kernel for aosp 4.4 won't boot for me with the June 1 cm11 build.

I noticed a pretty long list of commits for the d2 kernel in the cm11 change log.
[Verizon Samsung Galaxy S III] decimalman:
New AOSP build is going up! I haven't changed a lot, but I did sync with CM, so this build works with recent (6/1 and onward) ROMs.

Changelog:

Synced up with CM

Linux 3.4.91

Fixed a bunch of compile warnings that were bothering me

250 commits from CM in the last two days! :eek:

Does it still happen on the 6/2 build? I was seeing similar heat problems occasionally on the 5/15 build, but I haven't seen it since. Or are you running TW?
[Verizon Samsung Galaxy S III] bmeek:
Seems to be working flawlessly with the cm11 June03 nightly build.

Thanks so much!
[Verizon Samsung Galaxy S III] decimalman:
It hasn't been mentioned here yet, but the normal download server is acting a bit funny at the moment. I don't have an ETA on a fix, so I'll resurrect the old MediaFire mirror. The last two AOSP builds are available at http://www.mediafire.com/?jlehejjarshqd

I can't mirror TW at the moment, but I'll get to it later today.

EDIT: Forgot I was supposed to upload TW. TW 4.1 & 4.3 are up at https://www.mediafire.com/folder/9nc6cmdzmb8km/dkp
[Verizon Samsung Galaxy S III] bmeek:
I'm curious: are any kernel-related enhancements coming along with the next cm11 refresh (android v4.4.3)? If I'm not mistaken, cm11 was still v4.4.2 at the time of the last sync / dkp build...
[Verizon Samsung Galaxy S III] SpudsterZ:
DKP running smooth on 06/09 nightly (4.4.3) Carbon.
[Verizon Samsung Galaxy S III] decimalman:
Nothing Android-related yet, even on Gerrit. CM has been pretty quiet lately.
[Verizon Samsung Galaxy S III] decimalman:
There's a new AOSP build up on MediaFire. Changelog:

Synced with CM: tons of updates from CAF, also switched to the ND8 (Sprint KitKat) 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.
[Verizon Samsung Galaxy S III] TotallyAnxious:
Only problem I have is slow read/write speeds on my external sd card. Still usable just slower than they should be by around 40-50%.
[Verizon Samsung Galaxy S III] decimalman:
Give this test build a shot. I'm seeing a ~2.2x increase in performance with the creaky old SD card I'm using at the moment. If you run into any stability issues, let me know.
[Verizon Samsung Galaxy S III] TotallyAnxious:
I'll have time to test it out this afternoon. But since you're one of the friendliest kernel developers, I was wondering if you could look into this new governor and if it would be worth adding for our device. http://xdaforums.com/galaxy-s3/development/info-cpu-governor-zzmoove-t2326544 I think the biggest challenge would be changing the quadcore settings to work for dualcore.
[Verizon Samsung Galaxy S III] bmeek:
storage I/O benchmark results...

Hi there, I don't often look at benchmarks, but I thought I might help by downloading a random test app and sharing results. I installed Qualcomm's Vellamo app and ran it with the 07/05 kernel (which I have been running with the latest cm11 nightlies), then I loaded the dkp 07/06 test kernel and reran the test.

FWIW, the storage I/O portion of the Vellamo benchmark saw no real difference...

With the dkp 07/05 release kernel:

Storage I/O score: 147 (13 seconds)

has_o_direct: 1.0

rand_read_iops: 2949.0

rand_write_iops: 484.0

seq_read_mbps: 53.32

seq_write_mbps: 8.56​

With the dkp 07/06 test kernel:

Storage I/O score: 147 (14 seconds)

has_o_direct: 1.0

rand_read_iops: 2620.0

rand_write_iops: 472.0

seq_read_mbps: 53.25

seq_write_mbps: 12.87​

I gather that it might have been better to run the test several times on each kernel and report an average for each, but they seem pretty close - the greatest difference being that the test kernel's seq_write_mbps score was about 30% better.

EDIT: After posting I realized that I hadn't allowed TicksterMod Pro the time to apply my typical kernel settings for the test kernel (which include a max clockspeed boost from 1532 mHz to 1620). I re-ran the benchmark and the test kernel's write scores improved a bit:

Storage I/O score: 158 (13 seconds)

has_o_direct: 1.0

rand_read_iops: 2940.0

rand_write_iops: 559.0

seq_read_mbps: 53.31

seq_write_mbps: 11.74​
[Verizon Samsung Galaxy S III] decimalman:
Looks interesting. I'll look into it further once I'm done playing with the external SD stuff.

AFAIK, Vellamo only tests internal storage, which isn't affected by the change I made (don't worry, I'm looking into potential changes for internal storage as well :)). However, I've been running a more complete set of benchmarks this evening, and performance is mostly similar between the 7/5 and test builds. A few specialized tests show substantial improvements, but other tests like sequential read/write don't show much improvement (and are generally close to the limits of the card anyway).

After I posted the test build last night, I continued to experiment with other ways of correcting the issue that appears to be causing the SD performance problems. Using a slightly different approach, I'm seeing more widespread gains. One card is showing small but significant improvements across the board, while another is showing huge improvements, especially in write speed.

Once I'm done experimenting, I'll put together a new build.
[Verizon Samsung Galaxy S III] bmeek:
Vellamo referred specifically to testing "external storage bandwidth", but I wondered if that was really the case (given the virtual /sdcard view of the internal storage)...

Oh well. In any case, I sure do appreciate your efforts with this kernel.
[Verizon Samsung Galaxy S III] TotallyAnxious:
So the external sd card speed improved on both fronts, it's not an issue for me since it's still usable but it's not what it could be. It's not at all an issue for me. I'm just curious as to what factors would allow your "creaky old SD card" to have a 2.2x improvement and my sd card to not even be at 100%. This is the sd card I have http://www.amazon.com/Samsung-Electronics-microSDXC-MB-MGCGB-AM/dp/B009SK57ZQ

Read 53.08 mb/s Write 11.13 mb/s

I was wondering if this kernel has the SlimBus overclocked, it increases audio quality. And does dkp have NEON implemented?

With the intelliactive governor, it seems to heat up the device but only with this kernel. I have had this problem since you added it to the kernel. It seems to work amazing on the Quantum Kernel, (look back to the 6/28 Quantum Kernel, that's when it worked beste before the dev had to do a bunch of bug fixes, if you want to compare).

And I apologize if I'm overloading you with requests or anything, totally not my intentions.
[Verizon Samsung Galaxy S III] decimalman:
I haven't played with Vellamo recently, so recent versions might check external as well.

SD card: I'm having fun playing with it. :) The improvement I saw was on a pretty specific, "real-world" benchmark, and the improvement didn't really show up on the generalized, synthetic benchmarks I tried afterwards.

SlimBus: I don't remember whether or not I OC'd it. I'll look into it sometime.

NEON: you mean the fancy new kernel-mode NEON stuff that CM recently added? I'll get it next time I merge.

Intelliactive: I grabbed the most recent source I could find, but it wasn't optimized for our phones. I changed some of the defaults to work better, but a properly tuned version might help with the heat. I'll take a look.

I don't mind being overloaded. I've mostly run out of interesting things to play with, so suggestions are welcome. Otherwise, I end up doing nothing but resolving merge conflicts trying to stay up-to-date, and that gets boring fast. :(
[Verizon Samsung Galaxy S III] TotallyAnxious:
This NEON I think, http://www.arm.com/products/processors/technologies/neon.php, I'm not sure if that's the same thing you're talking about.

I've seen some people backport features from the 3.8 kernel source, so you could just backport features that would be useful for our phone. Here's what I'm talking about http://xdaforums.com/moto-x/orig-development/kernel-007-kk442-gsm3-4-hybrid-oc-t2645356

Oh and I believe our phone will soon have f2fs support, people on the at&t quantum thread have been working it out, and I think it's just a day or two away, so you could add f2fs, which I think is just modifying the update script to read the f2fs partition correctly.

I just dropped out of art school (moving onto the fun of anthropology lol) so I've been looking more into the core stuff of android and playing with java a little to keep me busy (if anyone else if curious about learning here's the site I'm using http://www.learnjavaonline.org/), so I can totally see how boring the merging can be, so I'll let you know whenever I see something interesting for the kernel.
[Verizon Samsung Galaxy S III] decimalman:
Boring ol' NEON? That's supported. I think I saw some changes recently that allow the kernel to use it as well, which is what I was thinking of.

f2fs should already be supported, and dkp doesn't use any scripts that would be affected by a change in filesystem. In theory, it should work fine once ROMs switch over to f2fs, as long as your recovery is recent enough to have support as well.

Learn by doing--find an interesting project and it'll make learning a programming language much more engaging. :)
[Verizon Samsung Galaxy S III] draexo:
When I install DKP and I start to move over stock MHz my phone freaks. I mean it reboots repeatedly. I've always run it at 1728 with other kernels. I tried the min volt at 1050. Any suggestions? It seems fine if I leave it at stock MHz.
[Verizon Samsung Galaxy S III] vmancini3:
Anything above 1512 MHz and you're gonna have to overvolt past the stock voltage of 1150 mV.... Try 1175 mV or even 1200 mV and see where that gets you! If it stops freaking out on you, then you can start to lower the voltage again....little bit by little bit of course!
[Verizon Samsung Galaxy S III] bmeek:
Once again, although the cm11 changelog shows lots of d2lte kernel updates since the most-recent build of dkp for AOSP ROMs, dkp is working fine.

I'm still looking forward to an update of course, but it's pretty cool the way things are :).
[Verizon Samsung Galaxy S III] bmeek:
This is no longer the case. Apparently the 7/24 cm11 nightly included some WiFi-related changes that are kernel-dependent.

Summary: the dkp AOSP build from 7/5 no longer supports WiFi in the current cm11 nightlies (from the 7/24 build onward).
[Verizon Samsung Galaxy S III] decimalman:
Yup. CM finally disabled kernel modules (they've been talking about it for ages now), which means the wifi driver won't even get loaded on newer nightlies.

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
[Verizon Samsung Galaxy S III] bmeek:
So far, so good. I'll play with firing up the access point later, but basic WiFi is working as expected. Running the latest cm11 nightly and the 7/26 dkp kernel:
[Verizon Samsung Galaxy S III] Mystique:
Is there anything here worth gleaning?

http://xdaforums.com/galaxy-s3/development/kernel-archikernel-v1-0-power-hands-t2785337

Looks like it..
[Verizon Samsung Galaxy S III] Mystique:
SlimKat 6.8 weekly

This introduces the cm 'death to all modules' commit.

I'll try and update tonight and report about the new kernel.

Thank you in advance for your work..
[Verizon Samsung Galaxy S III] Mystique:
Thank you for your patience..

Slimkat 6.8 and 0726 dkp, playing nicely together..
[Verizon Samsung Galaxy S III] Mattish13:
I'm actually getting wifi not turning on with same set up. Sounds like I need a kernel built after 7/27 to fix this, right?
[Verizon Samsung Galaxy S III] decimalman:
There's a few things I should grab. Recently, I've been busy working on GPU stuff, but I'll take a closer look when I get a chance.

The commit in question ("spring break '98, going moduleless!" :p) happened on 7/23, and the 7/26 dkp build includes it. The commit breaks wifi on older ROMs though, so build 6.8 is the only Slim build that will work with the 7/26 dkp build.

As long as I'm here, I could use a few more testers for some very experimental changes I've been working on. There's a new test build for AOSP ROMs built after 7/23 available as a direct download or on MediaFire. Feedback of any kind would be appreciated. Off the top of my head, here's what's new:

GPU OC is available in Trickster. 480, 533, and 600 MHz steps are available. As with CPU OC, higher frequencies may be unstable, and I haven't found any way of stabilizing them. Benchmarks are a mixed bag, with some only showing a couple percent improvement, and others showing as much as 35% improvement at 600 MHz. Subjectively, real-world performance seems better.

Overhauled GPU frequency governors. ondemand and simple both use lower frequencies when appropriate, and I've made some changes to keep things responsive.

New GPU governor that I've been playing with. It's still very experimental, but I like it so far. Trickster calls it "interactive" because I couldn't get it to show any other names.

Optimizations, bugfixes, and other good stuff. :) I think there's a small bug or two left, but the build should be pretty stable overall.
[Verizon Samsung Galaxy S III] Mystique:
Do you have any suggestions for keyboards..

Possible settings that might help lagging..

Currently hating all keyboards for phones..

---------- Post added at 07:25 PM ---------- Previous post was at 07:11 PM ----------

Boots, slimkat 6.8

Running stock settings - except tcp congestion.. I'll let you know.
[Verizon Samsung Galaxy S III] Mystique:
I will be more conscious tomorrow.. But battery life seemed better than usual.
[Verizon Samsung Galaxy S III] bmeek:
Thanks for sharing. The only feedback i can offer is no feedback (no news is good news?). I've been running your test build all day with the 8/4 cm11 nightly with no troubles.

I don't use any apps that really exercise the GPU, but I bumped the clock up one notch and all seems well.
[Verizon Samsung Galaxy S III] remotehugger:
http://xdaforums.com/showthread.php?p=44170372

over 100 themed google keyboards here - top notch work -

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Verizon Samsung Galaxy S III] Mystique:
Had this issue before this version..

Waze, GPS program

Will suddenly go black.

Need to three button reboot or battery removal..
[Verizon Samsung Galaxy S III] pyrite123:
So far so good. I've been using this kernel lately on some of the latest ROM updates. SOKP, Schism, Spirit, and now DU. This is the ONLY kernel that, since I've been using, I have not had a SINGLE random reboot/crash. I will have reboots in each rom's default kernel but once I flash this baby my phone becomes a playground. Thank you for your quality work, mate.
[Verizon Samsung Galaxy S III] LegoFarmer:
I'm unable to connect to WiFi on Pac and other 4.4.4 roms when I use this... Do you have the same issue?
[Verizon Samsung Galaxy S III] thelangosta:
Check out the experimental version Decimalman posted a couple pages back. I think it was from around 8/5.
[Verizon Samsung Galaxy S III] decimalman:
There's a new AOSP build up on both mirrors. Changelog:

Synced with CM, and got Linux 3.4.103 in the process.

Fixed mpdecision detection. It was causing mpdecision and auto-hotplug to continuously fight.

Added a bunch of tiny optimizations that shouldn't have much noticeable effect.

Possibly updated some stuff related to GPU OC? I don't remember what was included in the last build.
[Verizon Samsung Galaxy S III] MrBrady:
Thanks for the update. In Trickster, should MP Decision be enabled or disabled?

VZW SGSIII
[Verizon Samsung Galaxy S III] decimalman:
It's fine to leave it enabled. dkp automatically switches between mpdecision, auto-hotplug, and governor hotplug as needed.
[Verizon Samsung Galaxy S III] tvl76:
Happy to see the update.

Running great with Slim8.0
[Verizon Samsung Galaxy S III] MrBrady:
Thanks for the tip!

The kernel is running great on Task650's 9.10 AOKP build.
[Verizon Samsung Galaxy S III] decimalman:
Apparently, I didn't post this in all my threads. Oops.

The most recent AOSP build has an issue that causes reboots, especially with BT audio. This build should fix the issue for anyone having problems.
[Verizon Samsung Galaxy S III] decimalman:
I promised a user I'd put out a new AOSP build today, so I guess I will. It's up on both mirrors.

Changelog:

Merged the latest commits from CM: Linux 3.4.104 and a fix for the BT headset issue

Built with a shiny new GCC 4.9 toolchain

Added a new, wildly experimental CPU governor that I've been playing with for a couple days*

Switched to 120 Hz timer frequency as an experiment

* The new governor is called "tierservative" because it's vaguely similar to conservative, except it uses frequency "tiers," and I'm not at all creative. :p It's nowhere near finished, but I expect good things from it in the future.

EDIT: Looks like MediaFire just took down the latest build, and I can't get it uploaded again. :mad:
[Verizon Samsung Galaxy S III] MrBrady:
New Governor is super smooth! Let's see how it holds on battery.

Thanks!

VZW SGSIII
[Verizon Samsung Galaxy S III] decimalman:
I'm pretty excited about it. It's still not consistent enough for me (sometimes, it stutters for no good reason), but I think the ideas I'm playing with should make for an excellent governor. With some improvements (the CPU usage statistics are still very primitive), I think it should be both very smooth and very easy on the battery.
[Verizon Samsung Galaxy S III] remotehugger:
now just need a TW 4.4 kernel !!!!! lol - hey, its my story, I can tell it how I want - haha !!

VM GSIII/jdsingle76's deodexed NDC 4.4.2/stock kernel ?
[Verizon Samsung Galaxy S III] aromig:
Thanks so much for the update, loving the new governor! Can't wait to see how your ideas evolve it.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] decimalman:
So I've been playing with tierservative some more. I removed a bunch of stuff that didn't make sense (ramp delays), was completely useless (hotplug notifier), or actively hurt performance. There's a new AOSP build up on both mirrors.

No, you just need an AOSP ROM. :p Sorry, I couldn't resist.
[Verizon Samsung Galaxy S III] sbattosai:
I am having the best battery life ever with your latest kernel on liquidsmooth. Truly a fine piece of work this new governor! Thanks Decimalman! By the way, do you post on G+?
[Verizon Samsung Galaxy S III] decimalman:
I haven't been able to improve it since the last build. I guess that means it's doing its job pretty well. :)

I'm not the sociable type. ;) XDA is the only place I post regularly.
[Verizon Samsung Galaxy S III] sbattosai:
I understand. Could you maybe just tell us what are you 2-3 favorite roms for the d2lte or what's your daily driver?

Thanks!
[Verizon Samsung Galaxy S III] decimalman:
CM, CM, and sometimes CM. :p

I don't flash ROMs very often anymore. AOSP has been stable for me lately, and I never really used the features of other ROMs, so I don't have much reason to switch.
[Verizon Samsung Galaxy S III] razz1:
I just realized we have GPU OC on dkp?? Guess I should keep up on things better. Just want to thank you for continuing your work on this kernel after all this time. It's much appreciated DM!
[Verizon Samsung Galaxy S III] griz.droidx:
No one asked me. But my favs have been nameless and slim. But nameless for the last few months. It has the best combo of features for me without any crap that I personally don't use like halo and related stuff. But to each their own. I won't take anything away from any ROM. That's what's special about android/Linux there's something for everyone. You just need to find what you prefer. I've used them all at some point. Cm aokp carbon liquid paranoid slim ose. Ose was based on slim last I checked. It was nice too.

And I've been using dkp at default voltages with a min of 216 or so and stock Max at 1512. I have been using the OCef GPU at 480. Nothing huge there. I'm also using the new governor from decimal man the new ....verative. It has been performing great and getting awesome battery life.

So at least for me it's nameless and dkp all the way. Oh and PAgapps on fresh installs. But lately I've just been clearing dalvik and flashing. So far so awesome!

Again your mileage may vary try a few there's some new cool looking ROMs out like spirit that looks cool feature wise. Again it's all up to the user because as everyone would agree the phones could be a bit different and each user uses their phone differently.

Good luck. Thanks to dkp for his awesome kernel's.

Edit. Just wanted to say the same thing as decimal. I seldom flash as much as I used to. I'm usually on a build for at least a week or two then I'll update. Usually when I check change logs and see something that could help our devices.
[Verizon Samsung Galaxy S III] tvl76:
Lovin the new governer. [emoji106]

Sent from my SCH-I535