yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] omair2005:
Use chrome to download or download from PC.. Works fine here
[Verizon Samsung Galaxy S III] vmancini3:
UPDATE: It won't flash in recovery, none of my apps can open it, windows built-in zip file handling can't open it, 7zip can't extract files from it and I downloaded it from my phone using the stock browser AND chrome, as well as downloading it from my PC using IE AND chrome....it just won't work....

[MENTION=4932679]decimalman[/MENTION] If it helps at all, when I tried to exctract the contents of the zip on my PC with 7zip, it allowed me to extract the META-INF folder and the system folder, however the PNG's were not viewable and 7zip gave an error that said something to the effect of "compression method not supported"
[Verizon Samsung Galaxy S III] remotehugger:
can i ask why you want to unzip it ? its a flashable zip
[Verizon Samsung Galaxy S III] decimalman:
I'm guessing the download got cut off or corrupted. Do the MD5s match (81984c9ecdee40ad386319a27cbe194e for TW or c02610b34131e550c7c89ac8b7e0cc9f for AOSP)?

I think the download server might have been a bit overwhelmed earlier today. Downloads have started to level off, so it's probably a good time to clear your browser cache and try the download again.

Incidentally, I removed all the scripts from the installer, so your script shouldn't conflict with anything.
[Verizon Samsung Galaxy S III] vmancini3:
I know it's a flashable zip, I dig through everything....it's how I teach myself!
[Verizon Samsung Galaxy S III] vmancini3:
The download page shows a different MD5..

I also just cleared everything that can be cleared in the browser and still....no go:(
[Verizon Samsung Galaxy S III] decimalman:
Not much to be seen in the latest installer. Everything is handled internally by the update-binary.

Derp. I'm not sure why I thought I was in the AT&T thread. :o

That MD5 doesn't match with my local copy. I'll upload the build again in a minute.
[Verizon Samsung Galaxy S III] vmancini3:
Thank you sir!
[Verizon Samsung Galaxy S III] decimalman:
Fixed it. Thanks for bringing it to my attention. :good:
[Verizon Samsung Galaxy S III] vmancini3:
No problem...and just sent another donation your way! Thank you for the continued support!!!!
[Verizon Samsung Galaxy S III] decimalman:
Thanks! :good: I'll update the OP when I get a chance.
[Verizon Samsung Galaxy S III] beepea206:
So before I download and ash, is wifi still broken on the new build for aosp?
[Verizon Samsung Galaxy S III] vmancini3:
I gotta say....after more than a year of flashing different kernels and screwing around with governors, voltages, etc...this is why I love this kernel... I always use Es file explorer and there's a particular folder that has a ton of pictures in it that I'm constantly scrolling through...and after flashing this newest build I definitely notice how scrolling is MUCH smoother! Also smoother on my Facebook news feed as well! I just left the kernel at the default settings and let 'er rip! Everything is nice and smooth! Excellent job [MENTION=4932679]decimalman[/MENTION] ! :thumbup::):beer:
[Verizon Samsung Galaxy S III] rodawg71:
It's GTG!
[Verizon Samsung Galaxy S III] omair2005:
Is there anything to delete if coming from lean?
[Verizon Samsung Galaxy S III] Mystique:
I'm waiting for a bone stock 4.3 build tbh.

I moved my work phone to clean Rom; eh..

So the wife and I are personally doing 412 still, fwiw.

New build with entropy loaded, thank you. Will report back.

Thank you for your efforts.

And what's the deal with the Simple GPU governor? Vs on-demand..
[Verizon Samsung Galaxy S III] remotehugger:
200 dwnlds of TW 4.3 already - very nice -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Verizon Samsung Galaxy S III] decimalman:
Yep. It was a silly oversight that broke wifi. I just had to remove a couple lines of code to fix it.

As far as I know, you don't need to delete anything.

I'm planning on putting together a new build for 4.1 sometime soon. It sounds like there's still some people who prefer 4.1 over 4.3.

I don't actually know much about the simple GPU governor (I added it by request). It looks like it behaves similarly to the conservative CPU governor, i.e. slowly increases and decreases frequency. It theory, that means it's a bit better for battery.
[Verizon Samsung Galaxy S III] Mystique:
Anyone else having trouble getting a full charge?

My last post till now I got 98%..

What 4.3 tw build is everyone else running?
[Verizon Samsung Galaxy S III] remotehugger:
I am running stock/deodexed MK5 build by [MENTION=5076590]jdsingle76[/MENTION] - no problems getting 100% charge w/ latest dkp -
[Verizon Samsung Galaxy S III] Mystique:
One random reboot today. Clean Rom 8. About 15 hours before reboot.. Phone was literally doing nothing when it rebooted..
[Verizon Samsung Galaxy S III] tburns:
I'm running omni 4.4 and I my phone wouldn't charge. Went back to original kernel and it charges fine. Not sure what happened.
[Verizon Samsung Galaxy S III] bmeek:
Hmmm. I'm running latest cm11 nightly with the 2/26 dkp. Charged fine overnight, and has been running great on battery all day. 10 hours 40 minutes on so far and I'm seeing 50% remaining.
[Verizon Samsung Galaxy S III] Neverender326:
A guy in the BMS thread said the same thing. Probably the ROM
[Verizon Samsung Galaxy S III] beepea206:
I noticed better savings in the deep sleep, than was previously occurring with the 4.4 builds, but we saw in 4.3. Looks like the kk rooms are coming up to snuff with jb.
[Verizon Samsung Galaxy S III] Bamdroid:
Been searching for a more updated kernel these days and decided to run with this one and see how it goes with liquidsmooth..how's the freelunch gov? Hope it's tasty..
[Verizon Samsung Galaxy S III] borxnx:
Freelunch is the bomb.
[Verizon Samsung Galaxy S III] savagebunny:
Having problem with freelunch right now, My phone won't go into deep sleep at all :/

Don't got any wakelocks either 2/26 build on 3/01 Nameless build
[Verizon Samsung Galaxy S III] countryfolk07:
No problems here on the latest. Running Slim 3.2
[Verizon Samsung Galaxy S III] Mystique:
What is the gpu set to? I found simple was not a fan of my phone.. switching back to OnDemand things went back to normal for me.

Did the latest version for tw stop doing binary mpdecision?

I'm running a new Rom and it seems like trickster can't keep it enabled..
[Verizon Samsung Galaxy S III] borxnx:
Yeah, trickster hasn't been holding my settings through reboots for a while.

What app are other people using to adjust kernel settings?
[Verizon Samsung Galaxy S III] remotehugger:
I'm using ROM Toolbox Pro - settings are sticking after reboots -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Verizon Samsung Galaxy S III] borxnx:
I think Greenify was my problem. If you greenify TricksterMOD it will not set kernel settings at boot. I un-greenified it and it works fine now.
[Verizon Samsung Galaxy S III] RCOVA:
Does anyone else's phone produce an echo on the other person's phone when calling? Alot of people have complained about an echo and I changed back to Scott's stock kernel and there's no more echo.
[Verizon Samsung Galaxy S III] bmeek:
Why do you blame freelunch? Does your phone deep sleep if you select another cpu governor?

Fwiw, I'm seeing rapid drops into deep sleep whilst running dkp/freelunch with the latest cm11 nightlies.
[Verizon Samsung Galaxy S III] savagebunny:
I never directly blamed freelunch, I stated I was having issues with freelunch and going into deep sleep. And yes my phone does go into deep sleep on another gov like asswax. Was curious if there was any settings I should change to allow freelunch go ease into deep sleep.
[Verizon Samsung Galaxy S III] Bamdroid:
Happened to me as well with freelunch on LS 3/3 d2lte. As far as responsiveness it was flawless...just wouldn't go into deep sleep at all (used wakelock detector and was awake 94% of the time during a 9hr period). Went back to stock and it went into deep sleep.
[Verizon Samsung Galaxy S III] NMEAGENT:
Im planning to flash this kernel first thing tomorrow but i had a few questions. Im planning to tune the kernel just like in the video in the OP so would I need to download and flash "dkp-vmin-XXX.zip: rename this to e.g. "dkp-vmin-700.zip" (which would apply a 700 mV minimum voltage) and flash to change the minimum voltage. This is required if you plan to undervolt"? Im going to change the minimum and every other one by -50mv....i was just confused because the person didnt say If you had to flash this before hand, and if i do what should I rename it too?
[Verizon Samsung Galaxy S III] Mystique:
You do not need that for normal purposes..
[Verizon Samsung Galaxy S III] NMEAGENT:
Ok Thanks! So to avoid misunderstanding you're saying I dont need to flash the dkp-vmin-XXX.zip and i can just follow the video, correct?
[Verizon Samsung Galaxy S III] beepea206:
If you want to undervolt, use an app like trickster and scale down - 25 until you get to a voltage you want.
[Verizon Samsung Galaxy S III] Mystique:
I find that the kernel is already under volted and that I do not need any further under volting..
[Verizon Samsung Galaxy S III] beepea206:
Same here. When I under volt, I get screen lock issues.
[Verizon Samsung Galaxy S III] Travisholt92:
you click the settings button in trickster, it should have a menu appear on the right side of the screen, at the top it will say "set on boot" and will by default have "notifications" checked in, just put a check mark next to kernel and you shouldn't have issues.

Issue im having is, i can't make a single kernel change (not just with dkp) but any kernel, the phone fails to boot afterwards and can only be fixed by a factory reset... :/ sad face. im running carbon rom D2lte 3/3
[Verizon Samsung Galaxy S III] SpudsterZ:
Bummer. I'm using the same build with trickster and dkp - no issues. I have trickster set to apply settings 1 minute after boot, though.
[Verizon Samsung Galaxy S III] Travisholt92:
ahhhhh, that would probably fix the issue. lol
[Verizon Samsung Galaxy S III] decimalman:
I try to keep dkp compatible with everyone's phone, even if I occasionally break things in the process. :angel: If you figure out what's causing this (or would like help in tracking it down), definitely let me know.

Builds from the last month or two are no longer undervolted by default. The voltage table doesn't reflect the minimum voltage, so voltages are silently increased to at least 1150 mV (i.e. stock) across the board. I haven't found a good way to make the minimum voltage more obvious without breaking apps.

Using the vmin zip (or Trickster's Override Minimum Voltage setting) is the easiest way to lower the minimum voltage, allowing voltages below 1150 mV.

Are you running TW4.3? I use a rewritten voice processor driver on TW4.3, and it hasn't seen as much testing as I'd like. It seems to be working well for Sprint, but I haven't heard much feedback from other carriers. It's definitely possible that it's causing issues.

TW4.3 is a pain. You'll need a patched ramdisk that supports insecure adb. I'm sure there's one kicking around the VZW development forum somewhere.

I'm not sure why mpdecision wouldn't be running at boot (unless you flashed dkp over another custom kernel, which might cause such problems), or why you're getting denial errors trying to start it.

TW4.3 added a lot of new stuff to the firmware, TZ, etc., but obviously it's a bad idea to fully update your firmware. A few background services will periodically try to use the new firmware stuff and spit out a bunch of errors when they can't. On Sprint, we get a similar error from the missing firmware, but I've never had any issues from it. I wouldn't worry too much about it.
[Verizon Samsung Galaxy S III] RCOVA:
Yeah TW4.3
[Verizon Samsung Galaxy S III] decimalman:
Any chance you can send me a kernel log from after it happens (run "su -c dmesg >/sdcard/dmesg.txt" inside a terminal)? I left a bunch of debuggery in the driver, so it should get pretty chatty if it notices a problem.

I'll switch non-Sprint devices back to the old driver for the next build, but I'd like to get the new driver working eventually.
[Verizon Samsung Galaxy S III] beepea206:
Fwiw, I always have that box ticked and I've been losing my kernel settings on reboots too with dkp.
[Verizon Samsung Galaxy S III] rodawg71:
It might be Trickster (ijs) I was having the same issue (running LS latest) Uninstalled and using the baked in kernel tweaker with no problems.
[Verizon Samsung Galaxy S III] borxnx:
It's probably Greenify, or some other app that stops processes at launch. If you greenify/restrict Trickster at boot, then it won't automatically restore kernel settings. I had this problem also, then allowed Trickster to do its thing and A) battery is the same, it doesn't need to be greenified and B) applies settings every reboot.
[Verizon Samsung Galaxy S III] Neverender326:
Also could be another app like system tuner setting something for the CPU or RAM on boot. That makes trickster default to interactive/row
[Verizon Samsung Galaxy S III] Seraph552:
I really want to try this kernel out, but every rom I try to install the Aosp version on (Carbon, slimkat, cm11) I get reboots almost as soon as I manage to boot it up. It just won't keep running. Anyone have any ideas?
[Verizon Samsung Galaxy S III] decimalman:
Long-overdue updates for both AOSP 4.4 and TW 4.3 are up.

AOSP Changelog:

Merged CM's latest changes

Added the ability to keep the existing splash screen*

Changed the power save performance profile to use freelunch and simple CPU and GPU governors

TW Changelog:

Fixed fast charge for MHL cables

Added the ability to keep the existing splash screen*

Added init.d support for ROMs that don't already support it

* In internal storage, create a directory named "dkp", then create a file named "skipsplash" in the new directory. Eventually, I'll make the process easier.

The default settings ought to be stable. Do you have anything running on boot that could be changing settings?
[Verizon Samsung Galaxy S III] TotallyAnxious:
Just an idea. You could make two zip files. One that just flashes the new kernel and doesn't change the splash screen. And then one that flashes the kernel and a random splash screen.
[Verizon Samsung Galaxy S III] decimalman:
Not a bad idea. The option of a smaller zip would probably be convenient for a lot of people.
[Verizon Samsung Galaxy S III] Seraph552:
Not that I know of. I simply install the ROM (clean flash) then gapps. I have tried both slim gapps and regular. The reboots only occurred when I installed dkp. I can run lean and kt no problem. I'll try this newest version, hopefully I'll have better luck!
[Verizon Samsung Galaxy S III] remotehugger:
flashed latest dkp - seems good so far - I did notice that entropy isn't pegged at 4096 anymore, but at 3848 instead - not sure what could cause that - also, how do I pick the splash screen I want ?

edit : entropy at 4096 again - still wondering about splash screen though -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Verizon Samsung Galaxy S III] Mtsprite:
you unzip the kernel, take out the splash screens you want, then zip it back up and flash that. That's how i did it,

EDIT: Alternatively you can create a directory called "dkp" in your internal storage and place the file in there (be sure to rename the picture to "splash.png"). this way it stays constant each time you flash it.
[Verizon Samsung Galaxy S III] bmeek:
I am convinced that the relatively low level of activity on this thread is due to the reliable and smooth performance of the dkp kernel. There just aren't any issues to report.

Thanks decimalman!
[Verizon Samsung Galaxy S III] TotallyAnxious:
And your assumption is correct! DKP rocks.
[Verizon Samsung Galaxy S III] tvl76:
DKP is the only kernel I run. It does indeed rock...
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
I think I will flash this tonight. I have not updated my phone in a while and am on an older kernel and ROM...so this should make it run a lot better than it has been. What ROM do most use with this kernel?
[Verizon Samsung Galaxy S III] Eyalkn:
If you are looking for the smoothest rom with lots of features it is Commotio which is a modified Vanir Rom.

In this link you can read about all it's features. It has nightly builds here.

Second best Rom is Validus.

Each rom has its own Google+ page that has all the information and download links.
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
Thanks...doesn't look like either of those are Verizon GS3 compatible though?
[Verizon Samsung Galaxy S III] Eyalkn:
I am on Verizon S3 and they are since they are for the unified D2 (D2LTE) meaning all US S3s
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
I see. I think I will flash one of them and see how I like it, I've got nothing to lose. Thanks for the suggestions!
[Verizon Samsung Galaxy S III] snoop5:
are the gapps included in this rom
[Verizon Samsung Galaxy S III] bmeek:
Yeah, it seems we have a bunch more ROMs to choose from since cm11 went to the unified d2 builds. Thanks for the pointer.

Although i had never noticed it before, I went ahead and successfully dirty-flashed from cm11 to the commotio vanir variant, and it is pretty slick!

Seems there's a pretty complete carryover from the cm11 feature set (plus a good deal more).

I used trickster mod to restore dkp kernel and get it setup, then noticed that the built-in "performance control" is setup by default to apply other kernel configuration settings, but that was easily sorted...
[Verizon Samsung Galaxy S III] decimalman:
I think I finally sorted out the installer issues. :fingers-crossed: I fixed half a dozen bugs that were triggered by strangely formatted ramdisks, which (hopefully) means that the installer will work for everyone.

Anyway, there's a new AOSP build up. Mini-changelog:

Linux 3.4.86

Synced with CM

(Hopefully) fixed the installer once and for all
[Verizon Samsung Galaxy S III] bmeek:
I've got no problems to report while running the latest dkp kernel with the latest cm11 nightlies. Just wondering what's happening in decimalman's playground...
[Verizon Samsung Galaxy S III] decimalman:
Not a whole lot, sadly. I've been dealing with some personal stuff lately, and haven't been able to work on dkp.

New builds for AOSP 4.4 and TW 4.1 & 4.3 are on their way up.

AOSP Changelog:

Synced with CM

Added intellidemand and intelliactive governors

Updated to a shiny new toolchain

TW 4.3 Changelog:

Added intellidemand and intelliactive governors

Updated to a shiny new toolchain

I merged everything from TW 4.3 back into 4.1. Off the top of my head, that means:

All of the above

Fixed fast charge on MHL

Overhauled erandom and the hardware RNG driver

Added simple GPU governor

Added sioplus I/O scheduler

Fixed a bunch of small bugs

Switched to the new installer (I don't think previous builds used it?). On TW 4.1, custom splash screens need to be saved to <internal storage>/0/dkp/splash.png.
[Verizon Samsung Galaxy S III] vmancini3:
[MENTION=4932679]decimalman[/MENTION] Thank you for the continued support dude! We all understand that life always comes first! I say...you do what you can when you can!
[Verizon Samsung Galaxy S III] lexluthor:
Which file exactly do I use for my Verizon Galaxy S3 running TW 4.3?
[Verizon Samsung Galaxy S III] OMG_VTEC:
decimalman, is there anyway to add the hispeed tcp congestion? or is there a better one you recommend?
[Verizon Samsung Galaxy S III] TotallyAnxious:
YEAH is "YEt Another Highspeed" tcp.
[Verizon Samsung Galaxy S III] moeduss:
You can find that in Android tuner, I am using this kernel and I can change that through Android tuner.
[Verizon Samsung Galaxy S III] OMG_VTEC:
youd think i would have saw that while googling about them...i do tend to be a little blind though:p
[Verizon Samsung Galaxy S III] remotehugger:
OK....this is very odd and maybe hard to explain - running latest TW dkp - no undervolt - and it does this with all scheduler/governor combos so far - after powering down phone, whenever I turn it back on, if I don't unlock screen as soon as it comes on, the phone goes black - I have to hold power button for about 40 seconds and then it will vibrate and turn back on - but again, I have to unlock the screen as soon i can or it does it again ?? make any sense ?

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Verizon Samsung Galaxy S III] Mystique:
What scheduler are you running? I've seen things like that with fifo.. (different kernel..)
[Verizon Samsung Galaxy S III] TotallyAnxious:
So I've noticed a CPU frequency bug. My max frequency always switches to 1026000. I use trickster and set it to 54000 and 14040000, when I boot up the settings apply properly but eventually the max gets switched to 1026000. I'm using the latest Beanstalk if that matters. Oh and intellidemand is my governor.

Edit: I switched back to freelunch and that fixed the problem. So it looks like it's an intellidemand bug.
[Verizon Samsung Galaxy S III] remotehugger:
I usually run sio but checked with almost all other schedulers and it still happened -

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Verizon Samsung Galaxy S III] Mystique:
[MENTION=306204]jenny[/MENTION]

I found much love for asswax because of decimalman.. Minimal tweaking and I feel great about it..
[Verizon Samsung Galaxy S III] TotallyAnxious:
It's better at saving power when the screen is off and seems to use it a little quicker than freelunch when using the phone. It does feel snappier and more responsive though.
[Verizon Samsung Galaxy S III] decimalman:
YeAH is a pretty popular choice. One thing to be aware of: congestion control only affects outbound traffic, so it generally won't have a dramatic effect on network performance.

That's an intellidemand thing. The newer versions change the maximum frequency on the fly. You can change the frequency limits with lmf_..._freq in the governor's settings.
[Verizon Samsung Galaxy S III] bmeek:
I've read that Intelliactive is the designated successor to intellidemand... Are you using Intelliactive now, or are you sticking with freelunch?
[Verizon Samsung Galaxy S III] :
Anyone using this successfully with CM11 M6 Snapshot D2LTE? How's battery life/performance vs included kernel if so? Any issues?
[Verizon Samsung Galaxy S III] TotallyAnxious:
The newest 4.4 dkp hasn't been stable for me. Freezing, getting stuck on the kernel boot screen, and random reboots. I flashed back to the old one. Everything works fine.
[Verizon Samsung Galaxy S III] lieffring:
What do you guys use for a set up on the 4.3 TW kernel for speed and battery life just want to know what you guys are running vs what I run since I just switch from lean
[Verizon Samsung Galaxy S III] bmeek:
That's interesting. I've noticed no such difference, although I've seen cm11 updates hang on reboot when initiated with the latest dkp running.

Of course, this happens after dkp has been replaced by the native cm11 kernel, and I wouldn't even mention it if I hadn't seen a similar issue when I tried the kt747 kernel... Something about how the kernel installation affects the boot configuration?

But anyway, the 4/26 build has been operating reliably for me since... 4/26.
[Verizon Samsung Galaxy S III] TotallyAnxious:
It might be rom related, but I'm not 100% sure. I clean flashed everything again last night and had the same issues this morning. So I flashed to the second newest dkp. If they keep happening then it must be a rom issue, but so far everything been running smoothly since changing to the older kernel.
[Verizon Samsung Galaxy S III] metalcated:
You guys are not alone. I am also seeing the same issues. Complete freezes and stuck at boot screens. Battery pulls etc. Stock cm11 kernel is fine. I'll flash back to see as well it helps better.
[Verizon Samsung Galaxy S III] TotallyAnxious:
It looks like whatever the problem is, it is from the 4/26 dkp build. I'm 100% stable with the previous build. There's even better battery life on the older build.
[Verizon Samsung Galaxy S III] bmeek:
Forgive the obvious question, but are you using the same settings otherwise? With the newer build I was running the Intelliactive governor for a while but now I'm back on freelunch and more moderate UV settings.