yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'm still around, but I haven't had much time for XDA lately. :(

There's a lot of things I'd like to do with the 4.4 sources before I start merging in dkp stuff (e.g. merge in the last two years of mainline Linux updates, disable Samsung's "security" features, etc.), but nothing is merging cleanly, and I'm pretty sure I've already broken a couple things. I'll get a build out eventually...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
:( It's not working right? Ohhh... There's a pill that could help you with that to if you think the work load is too much to do it again....

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
No rush, decimalman! The most recent kernel is the best around for the S3, in my opinion. Completely stable, performs really well, and idles like a dream.

That being said, I'll be super pumped when the next release drops. Do you take any donations?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
:laugh: I just need a few days to get set up and get used to the new source. After that, I'll start merging and (hopefully) I'll get a proper build out by the time other carriers start getting the update.

Thanks! The desktop version of XDA shows a donation button under my avatar.

New AOSP & TW 4.3 builds are on their way up.

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
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Welp. Time to start obsessively checking and re-checking the thread.

Edit: Got it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hoke88:
Love your kernels but I'm not seeing bfq in TW kernel. Using trickster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
It's in the latest release, 5/15.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hoke88:
I downloaded twice 05-15.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I probably forgot to enable it or something similarly embarrassing. Oops. I'll try to get a fixed build out later tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hoke88:
Cool! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
My mistake. I didn't notice that you were talking about the TW version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Can u add the new congestion controls while ur at it please. Can't wait for ur tw 4.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Yep, I forgot to enable it. :o New builds are going up now.

EDIT:

Any particular ones? I'll get a new build out shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
How bout a dkp splash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I removed the splash screens after I got tired of uploading huge builds, but the installer can still do custom splash screens. Just save a PNG to /dkp/splash.png on your internal storage and it'll get converted next time you flash. :) Eventually, I'll add support for JPEGs and image resizing, but I haven't gotten around to it yet.

There's a bunch of dkp-themed splash screens here, if you're interested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
There was one called hispeed and a few others that I peeped on the kit kernel it was the 4.4 kernel tho so I'm not sure if it was specific to kit kat or not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Unless it's something that Google added (which is unlikely), there haven't been any new algorithms added in a while. There's still a few options I haven't turned on yet: H-TCP, High Speed TCP, TCP-Hybla, Scalable TCP, and TCP Low Priority. You probably don't want TCP-LP, but I can enable the others if you want to give them a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
There we go please enable away. Along with bfq. I'm back on 4.3 phone just don't feel right without dkp or s3rx lol. I see a few lines back u said there could be something wrong with the simple gpu, is that confirmed? Is there preferred settings for it or what gpu would u recommend for battery life?

---------- Post added at 10:53 PM ---------- Previous post was at 10:47 PM ----------

I notice the interactive gpu doesn't stick either I can use either simple or ondemand
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It might just be my phone getting old. I don't remember simple causing problems before, and I haven't heard anyone else mention any problems.

If you're going for battery life, lowering laziness would be a good place to start. The default ramp threshold might be a little high, but I haven't played with it enough to know what works well.

I'm not sure why Trickster shows the interactive GPU governor. It doesn't actually exist. :confused:

There's a build with all the congestion control algorithms enabled here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Thanks a lot deci, ill give it a full run tomorrow n see how it goes off a fully charged battery. Appreciate ur work have a good night. Waiting on that 4.4tw now lol great work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I was headed that way too, but I figured I'd post one last build before I did.

Anyone on TW who wants to play with ISAAC, there's a build here. Suggested benchmark: use a terminal emulator to dump 1 GB of random data from /dev/erandom and /dev/isaac:

dd if=/dev/erandom of=/dev/null bs=32768 count=32768
dd if=/dev/isaac of=/dev/null bs=32768 count=32768

If everything is working correctly, dd should clock erandom at around 35-50 MB/s, and isaac around 230-350 MB/s. Oh, and ISAAC is supposed to generate higher-quality random data, too. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
I'm game to try, so with this "issac" I should see greater data speeds? And just copy those commands to a terminal emulator n Bob's ur uncle? I trust u lol

---------- Post added at 11:54 PM ---------- Previous post was at 11:53 PM ----------

Is that terminal emulator command something I'd have to do on every boot or a 1 time transaction? Lol

---------- Post added 16th May 2014 at 12:03 AM ---------- Previous post was 15th May 2014 at 11:54 PM ----------

The Issac build doesn't have the new congestion controls enabled :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I would like to know why you believe this is necessary. Is it just because it's something more to tack on to the kernel or an actual need?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Issac or the congestion controls? Aside from what deci explained I knew nothing of Issac prior to, just that he went through the trouble of enabling it on the build he just put out right before the Issac build just wanted to have it on what will essentially be the last 4.3 release for awhile. As for congestion controls if u play around with em n find the right match for u ull notice an increase in data speed so consider it what u want but I was asking him specifically for myself
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Derp. Clearly, I was up past my bedtime last night. I must've reset the build config.

I wouldn't worry too much about missing out on ISAAC to play with congestion controls. TBH, ISAAC is just a toy at the moment, and I really don't expect it to have any dramatic effects. Mostly, I wrote it for my own amusement, and decided to replace erandom when I realized how fast it was.

The commands don't actually do anything, but they will measure how fast the generators can produce data. Also, you may have to change /dev/isaac to /dev/urandom to get that command to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
In all seriousness, here's a SlimKat build with DKP, Just Archi and all my settings with a little touch of me ;)

http://www.mediafire.com/?37a6241d5dfzcma

In terms of not derailing the thread, it contains all the newest commits of decimalman's kernel, Just Archi's adblock functionality and my "tweaks".

Anyways, sorry for the double post.

AFTER THE FIRST BOOT, REBOOT AGAIN THEN LET YOUR PHONE SIT FOR 10 MINUTES.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
apologies upfront for newb-ness. good to run with Quantum 4.1 ? :what:

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
If I were you I would try the download link I posted with DKP built in. It's pretty stable IMO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
There's a thanks button for a reason....

Make sure you thank all [MENTION=4932679]decimalman[/MENTION] 's posts too... as well as [MENTION=5161352]JustArchi[/MENTION] 's.....

EDIT:

If anyone is looking for mirrors, look at my media fire here:

http://www.mediafire.com/?hibw398775d2t

The only file I edited in the zip was init.dkp.rc. I added ramdisk support for the Supersu daemon so root access is kernel dependant instead of ROM dependant....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I just install the tw4.3 5-15-2014 over kt kernel.

1. What app is recommend to use with the kernel. I install trickstermod

2. How do I change the splash screen. It still appear ktkernel bootscreen.

I'm using s3rx 3.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Go to your sd card and make a folder called "dkp".

Should look like this:

/sdcard/dkp

Make sure your image is 720x1280 and it is in a .png format. Place it in that /sdcard/dkp and rename the image to splash.png.

It would like like this:

/sdcard/dkp/splash.png

Flash the kernel afterwards.

If anything, I recommend you reflash your ROM (clean flash) and start all over again.

The issue is with the ramdisk, ktoonsez uses a personalized one that would interfere with decimalman's kernel. Especially with init.d support.

I also recommend you use trickster mod to set your personal settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
thanks. had same issue/question. will start over with clean flash.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Thanks, since I'm using S3RX. I go to the rom custom setup and install kernel only. I choose dkp restart and then go to recovery again and install the 5-15 kernel. Now I don't see the kt splash screen.

What is the recommended setup in trickster mod. I use noop, freelunch, 1,024 read ahead. The mpdecision I need to use it on or off? The tp congestion what is recommended? I leave it the default one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I would use freelunch and the BFQ scheduler. For a good TCP control either try out westwood and yeah.

Since you're on touchwiz, I would actually recommend that you delete mpdecision from the system.... Located in /system/bin/mpdecision, use a root explorer to remove it. Then reboot.

I would keep your read ahead speed at around 512kb on each mount. Decimalman's kernel works best IMO when the read ahead speed isn't too much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thank you. Where do you set the read ahead speed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Copy and paste the following into a file. Throw it in your init.d folder and it will set all your mounts read-ahead speed to 512kb.

#!/system/bin/sh

for xr in /sys/block/*/queue
do
echo 512 > $xr/read_ahead_kb
done
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Wouldn't it be easier to do it in Trickster? Just for the sake of laziness lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Yes you could, but trickster mod only sets the read ahead speed on the sd card. Or you could throw the script in and forget about ever tweaking it again lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Was this for tw? And was it all just one long script? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I forgot to PM you about it, but the dkp installer can do this for you. If you copy init.superuser.rc into rd/ in the dkp zip, the installer will add it to the ramdisk and patch init.rc to import it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
You're talking about Koush's superuser support on touchwiz right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Anything that wants daemonsu to be started from the ramdisk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Service for Supersu:

# Supersu daemon
service daemonsu /system/xbin/daemonsu --auto-daemon
class core
user root
group root
oneshot

Service for Koush's superuser:

# su daemon
service su_daemon /system/xbin/su --daemon
oneshot

on property:persist.sys.root_access=0
stop su_daemon

on property:persist.sys.root_access=2
stop su_daemon

on property:persist.sys.root_access=1
start su_daemon

on property:persist.sys.root_access=3
start su_daemon

The service for Koush's superuser is written in "init.superuser.rc".

You're saying if I add in that init.superuser.rc file to the rd directory of your flashable zip, your update binary will add in Supersu's daemon service to the ramdisk as well?

I don't think touchwiz users would have any benefit to the persist.root properties in the ramdisk if Koush's superuser was preferred.... Correct me if I'm wrong here.

I tested what you had said about adding the file in your zip, and I don't see a service for Supersu anywhere on a stock ramdisk... I apologize if I'm misunderstanding what you're saying.

EDIT:

Slim Weekly 5.2 with my tweaks as usual:

http://www.mediafire.com/?hibw398775d2t

There are also mirror links for decimalman's kernel. Although the latest slim weekly already contains your latest kernel.

IT WILL TAKE A WHILE TO BOOT UP. Art mode is persisted through the build.prop, after first boot as normal reboot and let your phone sit for 5-10 minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
My installer is nowhere near smart enough to do all that. It'll naively copy whatever init.superuser.rc is in the zip into the ramdisk and add an "import /init.superuser.rc" line to init.rc if it doesn't already have one. It's probably the least elegant way to fix up the ramdisk, but if you're desperate, it should be sufficient to get daemonsu running during boot.

You're right, those property triggers probably won't be very useful. It's probably better to roll your own init.superuser.rc with just the relevant service definition.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
That's arbitrary. Seeming "desperate" to construe a provision which has been an issue of the past; adaptive and guaranteed root access seems logical to me if dependence becomes both kernel and ROM variables.

Comparable to a 50/50 lottery ticket: the jackpot is the daemonsu service whether it's open source or closed source to make sure writing to the system partition is always an option. From an elaborate angle with my brain working at maximum capacity:

Solution =

Edit init.dkp.rc and add daemonsu as a service and...

-TOUCHWIZ-

Add init.superuser.rc to the ramdisk (Koush's superuser) without persistent properties.

-AOSP-

Edit init.dkp.rc and add daemonsu as a service because init.superuser.rc already exists.

-----------------------------------------------------------

In reality, I'm joking around! I realized I over-complicated a problem. I misunderstood you, my apologies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GhostIsBaked:
What version of SlimKat is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
A "tweaked" version of 5.2 SlimKat weekly.....

Refer to this post:

http://xdaforums.com/showthread.php?p=52780526

Edit:

Sorry for the off-topic subject matter...

[MENTION=4932679]decimalman[/MENTION]

Ever seen Breaking Bad? Remember the green lights episode where Hank was in the interrogation room with the junkie trying to get a name from him?

"Is that your brain working at maximum capacity?"

"The guy definitely had tan pants....."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Hello. Where would I find your 5.2 weekly on the page the link takes me please. Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Right above your post...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
My apologies. I should have been more clear on my post. The link does not take me to a download page. The page has all kinds of info on it. Maybe my browser?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Read near the end, mediafire link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hoke88:
Which gapps do you use? Slimgapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Yes..... SlimKat..... slimgapps.... Really hard to put them together....

Anyways no more derailing the thread.

I don't own this thread, I simply add it to my regime of firmware that I use and support. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
In my opinion, you add a lot of value to this thread. Dkp plays a big part in the ROM you choose to use so to me it's all relevant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Noob Question

New DKP user here. So far so good. Just a quick question regarding the softkey animations. What are they and do they need to be enabled? I assume its similar to the slow fade of the notification LED, but I dont notice that on my device. Im running the latest CM11 nightly.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
I'm getting a bad download of the dkp4.4 for aosp the latest one, can someone upload a mirror instead if it's okay pls? Thanks

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Use the desktop browser, will work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Got it with chrome beta

Sent from my SAMSUNG-SGH-I747

---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------

What's the advisable OC voltage?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
It all depend. For example my first sgs3 I can OC with the default voltage table up to 1800. Then I change by warranty and my new phone don't OC more than 1600.

My answer to you're question all phones are different and is trial and error. Until you find the best settings for your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Is trickster the only compatible settings app for this kernel? Hoping not, even tho its highly used I'm not a huge fan but this kernel is rock solid
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Hey guys, I'm having a 5% battery drain overnight, is this normal or not? I'm using dkp with the latest slim weekly 5.2

Kernel settings are : yeah, freelunch, bfq, OC'ed at 1,622Ghz

Is there something wrong?

Btw i turned off LTE overnight

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Nope, nothing is wrong there. Use greenify if you're stingy saving battery power there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Thanks dex...

Now I'm on PA latest beta 6 and it works flawlessly with dkp nice...

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Any way to get the new kernel to include a splash screen? Going to confuse myself even more than usual seeing the KT one even though I'm using DKP.

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Where can I find information about the various GPU (not CPU) governors in Trickster MOD? Which one is preferred?

(The great Google has let me down.)

For some reason, my CPU governor choice (freelunch) scheduler (bfq) and 512 read ahead buffer size are not sticking on reboot. Kernel settings are set to "set on boot".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
So true. For this kernel on my first motherboard (same phone) I could attain 1728, but not stable. With the used one I bought and actually older, I can run 1800 stable. Different Kernels seem to matter too, probably as you stayed due to voltage table
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Sorry for taking so long to respond. Hopefully I didn't miss anybody. :o

I added a fade animation for when the backlights on the menu/back keys are turning on/off. The animation is always enabled, but I tried to keep it short and subtle.

Most kernel-agnostic tuner apps (e.g. SetCPU, Voltage Control, Performance Control, etc.) should work fine. Trickster does show a few extra settings that other apps don't, but nothing terribly important.

The dkp installer still includes custom splash screen support. Eventually, I'll write up some proper documentation for it. The basic procedure to install a custom splash screen goes like this:

In your internal storage, create a new folder named "dkp"

Find or create a splash screen you'd like to use, in either PNG or RLE format. PNGs would ideally be 720x1280 to begin with, since the installer can't resize them very well; RLEs have to be 720x1280, or they won't display correctly.

Copy the splash screen into the "dkp" folder you just created. For PNGs, rename it to "splash.png"; for RLEs, "splash.rle".

Reflash dkp

There's a handful of dkp-themed splash screens here. You can also pull the initlogo.rle out of a flashable splash screen zip and it should work fine.

The GPU governors aren't very well-documented.

performance: locks GPU at maximum frequency

ondemand: uses Qualcomm's magic to determine optimal frequency

simple: adjusts frequency one step at a time, somewhat similar to the "conservative" CPU governor

interactive: not actually supported; I don't know why Trickster shows this

Trickster sometimes refuses to apply settings after rebooting. Changing the apply delay used to fix it, but I'm not sure if that still works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Thanks! Worked perfect!

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
New slimkat weekly 5.6 wont boot up with dkp ?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Well, i guess we need a kernel update, slimrom team announced earlier for all d2lte users to be "cautious" in flashing custom kernels that are built before 6/1/2014

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
It seems there have been some changes in the latest cm nightlies 06/01, anything based on those won't boot without an updated kernel.
[AT&T, Rogers, Bell, Telus 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
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thantos:
Thanks for the update! One issue, I just tried a dirty flash of the newest kernel with beanstalk and it booted but screen was permanently off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Do not flash it with roms built before June 1, it does nit contain the latest cm changes

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Bluetooth freeze

Here's a new one- anyone experiencing a freezing dialer, but only when bluetooth headset is connected? It seems to freeze the dialing app, but only while connected to a headset via bluetooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Will you send me a logcat? I have no idea what could be causing this. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Thanks! https://www.dropbox.com/s/haskuzl58429w6w/Log_2014-06-04_11-03-15.txt