yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Latest kernel is running fine with CM11 M11, in case anyone was wondering. It was built around 9/30 or so, so there shouldn't be any compatibility issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NikoZBK:
Gonna give this kernel a try :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Yes Task is gone for long time and the Task650 AOKP ROM is basically done with now...still my all time fav S3 daily ROM..but yeah, last couple had issues.. Anything 8/10 and earlier has been rock solid..and FINALLY a kernel (this one) that rocks with it! Over a week on Task 8/10 release and this kernel and not a single issue or freeze/reboot.

Have tried so many ROMs recently..almost all being CM based and they all have some major inherent issues but previous task builds as stable as I can ask for..and a TON of customization options..used to use KToonsez kernel with it but started having issues over past 6-12/months so have been stock (non tweakable) kernel for while..but not anymore..this one is solid

Thanks

PS..and unlike many cm ROMs..my Bluetooth is 100% working..GPS locates fast and easy..no reboots on video..WiFi no prob...and data radio works! (That being the latest thing I've noticed on many kernels and ROMs..real pain but a-ok here..only thing is right after initial flash of ROM and then kernel..seems to take about a min to connect to LTE..but after that..instant every time)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Fixed. New builds are on their way. Thanks for reporting this. :good:

Edit: Builds are up now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
no problem at all! Nice to have it working again

---------- Post added at 12:52 PM ---------- Previous post was at 12:26 PM ----------

Everything is working here. Thanks for the speedy updates. Goes a long way.

for curiosities sake, what rom do you normally run?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Just doing my job. :good: It was a pretty easy fix to track down (only took about 5 minutes), and nobody wants a malfunctioning phone.

I usually stick with a ROM for about a month and then move on to something new. Currently I'm running PAC-Man. d2spr doesn't get as much ROM development as other carriers, and our PA dev retired (or switched carriers or phones or something) so I hadn't seen how far hybrid mode had come. I didn't realize how much I missed hybrid mode until I started playing with it again. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Hey Decimalman the latest nightly gave me the unresponsive black screen. Phone works.. I can feel feedback but just a dead screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
CM introduced some changes to the video driver. If you have the absolute newest CM (possibly from CyanDelta), you'll need today's build of dkp or your screen won't work. For any other ROMs or older nightlies, you can't use today's build of dkp or your screen won't work. I'm going to add a notice in the OP on the subject.

I hate it when CM does stuff like this. It means that I'm probably going to have to build two versions of dkp for the next month while ROMs slowly get updated. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
I kind of figured lol

But I didn't see a notice so I gave it a go but unsuccessful haha. No problem!

I can't use anything besides AOCP so I'll use an older version. Thnx for the quick reply :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Download the test build. Running amazingly for me so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
4/19 test build running great with Deviant 4/21 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New 3.4 stable builds are going up! I'm planning to backport a few changes and do a new stable 3.0 release soon, since I know there are still some users that don't like 3.4.

Major features since the last stable release: lots of stuff. If your ROM hasn't merged in the CM video driver changes yet, your should ask the dev merge them so you can upgrade. :)

Notable changes since the last test builds:

Newest CM commits integrated. They've been hard at work causing merge conflicts. :p

At user request, the AssWax governor has been added (and works!). It has an extra interaction mode to support dkp's interaction hints.

Kernel-wide erandom finally works on 3.4

New CPU load interface with much higher precision than the existing one, plus two new governor variations to take advantage of it

Trinity colors setting takes effect instantly. Now I just need to get apps to show a setting for it. :( Want to try it temporarily? Enter 'trinity' in a terminal emulator.

Cleaned up some touchscreen code
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Do we still need to flash the trinity enabling zip or is it on be default now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's not the default. I guess I could make it the default, but I didn't think to change it since I personally think it's just too blue. Unless you wipe /system or flash a new ROM, it'll stay enabled across versions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
No problem just double checking. I use cyan to flash nightlies and I have to make sure that I include both when i update or I have to go back and do it again. Waiting on the page update now.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
They're done uploading, so they should show up any second now.

On CM, you should be able to copy the 90dkp-trinity initscript from /system/etc/init.d to /data/local/userinit.d (I think this is the right path) and it'll stick until you factory reset. I don't think many other ROMs support this, but I'm 99% sure CM does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I'll just keep flashing the script, it's automated.

in the mean time... F5 F5 F5 F5 F5 F5 F5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
LOL

...It appears that either Dev-Host or my upload script isn't working. Derp.

Edit: Manually uploaded and all the install zips are up. Dev-Host is really slow today, and they're not showing the uninstall zip. First world problems...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
First!!!! Running Nanolunch. Any suggestion on a scheduler? I am running Zen as of now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
2nd core isn't hotplugging with asswax. both sitting at 384
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
That's not good. I think I know what the issue is, since I've run into it before. AssWax doesn't hotplug, so mpdecision probably isn't doing its job. If you have Trickster, does the "Specific" screen show MPDecision on or off?

Give me a few minutes to work on a new build that should fix it (assuming I'm on the right track anyway).

First across all devices even.

I don't have any real preference, so whatever scheduler works for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
shows as off. I flipped to on and toggled but It didn't seem to make a difference. Gonna try turning it on and a reboot while you investigate. Asswax is worth it, don't give up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Most likely Android can't find the mpdecision service. Certain modifications will do this. I'll put together some code to get it started even without the service.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
Are you talking about TASK FW 8.10 + this kernel dkp-aosp44-20141002.zip ?

If yes - please check on your phone:

- is auto brightness working ok ?

- is Compass working ok ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Installed Slimkat7 rom & running dkp10/02 kernel & everything is going well.

Edit: I spoke too soon, I have no data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itzamistry:
I flashed this kernal after I flashed cm11 and it didn't boot. It booted I could do everything but the screen was still on the boot logo. Help please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Reflash CM11. Fixed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itzamistry:
after i flash the kernel then reflash cm11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Well that was instructions to get it back to working state, not to magically fix your incompatibility.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itzamistry:
Oh. How can I flash the kernal then? I tried 3 different kernals all resulting in the same outcome
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
What are the build dates on the kernel and ROM you're using? That sounds like severely mismatched kernel and ROM video drivers to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I think it's time for a new build. I'm not 100% satisfied with the new changes to tierservative (battery usage has definitely increased), but a new build is way past due.

New AOSP build is up on both mirrors. Changelog:

Lots of changes to tierservative

Changed balanced performance profile (i.e. the default) to use tierservative

BFQ v7r6

A shiny new GCC 4.9.2 toolchain with some new Krait-specific tuning

Feedback on the changes to tierservative is encouraged. They definitely increased battery usage a bit, but also smoothed out performance considerably.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itzamistry:
i am running att galaxy s3 cm11 version 11-20140217-NIGHTLY-d2att february 16 build date. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I don't remember exactly when it happened, but there's been at least one compatibility-breaking update to the video drivers since then. You'll either need to use a kernel that was built back then or update to a more recent ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itzamistry:
Hmm alright thanks. Do u know if there is a newer cm11? If not i will just flash a more recent rom. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
CM merged all the US S3 variants, and now calls them d2lte. There's downloads at http://download.cyanogenmod.org/?device=d2lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itzamistry:
Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I've been running this build along with CM11 11/01 nightly without any problems so far. Battery life and performance have been great using the tierservative governor and Multicore Power Saving set to 1.

I wasn't using tierservative on any of the previous dkp builds, so I can't make a comparison between this iteration and earlier ones. I just know that it has become my governor of choice, usurping Intellidemand's spot at the top of my list.

Thanks for continuing to support this excellent kernel. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Does this work with f2fs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
I don't have device so I can say FOR SURE but it appears so. It's in his source. One config didn't use it but the other did and it appeared to be newer so I'm willing to bet it absolutely does support f2fs. Can't see going through trouble of adding to source and not using. I went out of my way to add it to my kernels. Just to be clear I'm going with yes lol. And [MENTION=4932679]decimalman[/MENTION], this is really nice. That source of yours is LOADED. Seriously, you're the bomb and it's Linux 3.4+. Wow. Hats off to you Sir. My n2 dual boot kernel, I'm still using same 3.0.31 version as Sammy. Is it worth the trouble to update that far? Issues I should know about ahead of time if I did update? LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Well I tried it and it works on f2fs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Huh, apparently f2fs is supported. I knew it was enabled, but I've never actually played with it. Does f2fs make a noticeable difference?

Thanks, I don't deserve the credit for 3.4 or f2fs. My AOSP source tracks CM pretty closely, and they were the ones that handled the update to 3.4 and added in f2fs.

The N2 is totally unfamiliar territory for me. It's Exynos, right? I'm not sure how much advice I can give you, since I'm only familiar with MSM kernel source (Qualcomm maintains completely separate kernel source for MSM devices).

Because S3 kernels need so much MSM-specific modification, they're difficult to update. CM had to start fresh with Qcom's 3.4 source and manually port over all the drivers, boardfiles, etc. I'm sure it was a ton of work. If Exynos uses less architecture-specific modification, you might be able to upgrade fairly easily, but it probably isn't worth the effort. AFAICT, 3.4 doesn't really have any dramatic changes to make it worthwhile. IIRC, CM had to update to 3.4 because Qualcomm stopped maintaining their 3.0 source, otherwise we'd probably still be using 3.0 kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
F2FS is great! To me the biggest difference is in app load times, but everything feels snappier with it.

I would say try it yourself to really see/feel the difference, but I like it a lot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Is anyone able to record video with Google Camera in CM11 while running the latest dkp? I'm getting a Can't Connect to Camera error every time I try, and then the camera app won't work again until I delete the resulting video file from the Gallery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hadn't tried till just now but yeah I'm getting the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
It's an issue with Google Camera. If you can somehow roll back to the 2.3.019 release it will work fine. You probably have to (backup your pictures and) delete the /sdcard/DCIM folder as well. Google must know about the issue because they've quietly released 2-3 versions ever since the problem arose on 10/31.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omega Hunter:
Random noob question of the day:

Can an AOSP 4.4 kernel (namely, this one) be installed (and actually boot) on a 4.3 ROM? Lol, I'm pretty sure the answer is no but I just want to be sure. I've gotta go back to a 4.3 ROM and don't feel like using yesteryear's kernel. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I'd highly recommend using a kernel from the time that whatever ROM you're installing was built. If you don't, you will likely run into an assortment of issues or just won't be able to boot at all. Why do you have a problem with "yesteryear's kernels" if you're okay with going back to yesteryear versions of Android?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omega Hunter:
Lol, fair enough. My main problem was just that the old DKP kernel doesn't have some of the features and governors and I'm used to, but I'll deal.

[Edit]: On a side note, I would rather stay with current ROMs. I've been using Dirty Unicorns 8.1 for a while and it runs great. The ONLY reason I'm going back to 4.3 is because, for some reason that I haven't been able to figure out, my battery will never read properly on a 4.4.4 ROM since the day I updated to the NE4 firmware.

By which I mean I can charge it overnight and it'll drop instantly to around 60% when I unplug it. Or if it does stay at 100, it'll decrease normally to about 89, drop sharply to around 75, and hold there for the next 6 hours before dropping another 40% and holding. And when it "dies", I plug it up while it boots and it'll show around 45% left and has run off that for another couple of hours. The only way I've got it working is to go back to stock (not really an option) or stick to 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Sounds like your battery may be going out. My Droid X used to do the same thing. Replaced the battery and now it's stable (using it as a media player).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omega Hunter:
I thought so too but I've been on two new batteries since then and no dice. I've also tried my batteries in another S3 and they worked fine. Lol, I bought a 7000mah battery last month just to get normal battery life whereas trying the same battery on 4.3 will get me almost 48 hours of life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] butthurtlocker:
Will this kernel work with TW 4.4 roms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Nope, waiting for [MENTION=4932679]decimalman[/MENTION] to show some tw 4.4 love
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
So I noticed the dkp AOSP lollipop test build in the d2vzw thread & I'm curious if it will work on other d2 variants as well? Thanks in advance!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I don't see why not. I was waiting for some more feedback before posting it in my other threads, but AFAIK it's working fine on d2vzw and should work fine for everyone else.

For anyone curious, the Lollipop build is available on MediaFire.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Sweet! I thought so just wanted to be sure thanks man! Appreciate it ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], I was running CyanideL v4.0 on NJ1 for about 12hrs. decided to flash dkp LP test kernel & after flashing lost baseband? I wish I would've grabbed a log but unfortunately I did not. Not sure why just wanted to report it, also not sure if it was rom issue or kernel issue. Others in cyanide thread have confirmed other kernels working, however I didn't try any as I really wanted to use dkp! Restored my nand backup of another LP ROM & all is good. Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks for reporting this. :good: Cyanide L isn't available for d2spr (all we have is unofficial CM and LS), but I'll take a look around and try to figure out what's going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Hey man, thanks for looking into it! Love dkp! Can't wait to get dkp in the driver seat of my d2att & running my LP roms again! If there's anything I can do to help with dkp on d2att, just shot me a PM! Thanks again bro ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
So apparently it's been like 4 months since the last official build came out. Oops.

There's two new builds up: a new build for AOSP 4.4, and a new (and very experimental) build for AOSP 5.0. The xstefen.net mirror has been taken down, so update your bookmarks.

Changelog for 4.4:

Updates to tierservative

BFQ v7r7

A couple new tweaks and optimizations

A couple updates from CM

Changelog for 5.0:

Fixed (I hope) a subtle bug from the previous 5.0 build, so this build should be more stable

Everything from 4.4

Lots of commits from CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Wonderful! Thanks! Will report back soon!

Sent from my OctOS d2att

Beware "The Kraken"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Thanks for remembering us little people, decimalman! Just flashed the 0301 kernel on my recent CM11 nightly. Smooth sailing so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], OK dkp 5.0 running great! Been running over 14 hrs lime a champ! Nice to be back on dkp!! Thank you! ??? This is the top "DAWG" IMHOP!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hey decimalman,

I've noticed this slightly annoying problem with the last couple of builds of the kernel. I am running the latest with a CM11 nightly from 0301 (if I recall), and whenever I reboot the phone the screen will fail to wake if it falls asleep on its own after the reboot. If I keep the screen awake until Trickster Mod has finished applying my kernel settings, however, I can then safely sleep the screen and it will wake properly.

If that's hard to follow here are the two scenarios:

Won't-Wake Scenario

- Reboot phone

- Phone boots up and I don't touch it

- After 30 seconds or so the screen sleeps. This is before Trickster Mod has loaded its settings.

- After the screen has slept, I press the Home button and/or power button and the screen will not wake.

- Only resolution is to power the device off by holding down the power button.

Will-Wake Scenario

- Reboot phone

- Phone boots up and I unlock it.

- I use the phone to keep the screen awake until Trickster Mod has finished applying settings on boot.

- After this is done, I can safely lock the screen or let it idle asleep.

- I can successfully wake the phone with either the home or power buttons afterward.

I have tested with other kernels (such as stock CM and LeanKernel), and they don't have this issue currently. I had this issue way back with the previous 10-2014 build of dkp as well. I love this kernel above all others for the S3, so I was wondering if you might have an idea as to why this happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], I just noticed after flashing the kernel, my splash screen still says booped by BMS, fixed by reflashing ROM & kernel, just thought I'd let you know, it'd be it'd be sweet as hello to see a dkp splash! [emoji12] just a thought, 3 days now on latest LP build & !perfection! Is all I have to say!

Sent from my OctOS d2att

Beware "The Kraken"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Thanks for updating the kernel and revising the OP. Running smooth on KK - 5h+ of screen time on stock battery and I would say around 1.5%/h on sleep. All with stock settings. Great job! Cheers

I'm unsure you followed post #3 on this thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
5h+ of screen-on time? Surely you're using an extended battery of some sort.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KentuckyGuy447:
Hi got a couple of noob(ish) questions, firstly will this kernel work with unified CM11 nightlys(d2lte) build. Secondly I can't seem to download the latest 4.4 build from mediafire, it'll download like 35-90 KB then say the download is conpleted. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
DERP! I guess I missed it, thanks for pointing it out, its been quite awhile sense I read the op I forgot about a few other things as well.

Sent from my OctOS d2att

Beware "The Kraken"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
That's really bizarre. :confused:

What settings is Trickster applying? I haven't been able to reproduce this, so I'm guessing that it's a specific setting that's causing this.

Yep, it'll work fine.

Sounds like MediaFire is being wonky, as usual. :( I mirrored it to Dev-Host for now: http://d-h.st/yOE2

There's a bunch of user-created dkp splash screens floating around. I'll collect a few up and post them when I get a chance.

EDIT: I zipped up all the splash screens I had handy, but I think I missed a couple. They're up on MediaFire.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
The only settings I have it applying in Trickster Mod are changing the governor to Intellidemand, scheduler to Zen, enabling Fast Charge and Temperature Throttle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'll bet it's a change I made to intellidemand a while ago. When I get a chance, I'll work on a fix.

EDIT: Yup. Applying intellidemand with the screen off hangs the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KentuckyGuy447:
Thanks! Also is GPU over clocking supported? Would really like to see a kernel that supports it as I've not yet seen one for 4.4.4. Not ridulous OC but to 600MHz would be nice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Yes, but GPU OC isn't as amazing as you'd hope. Performance is somewhat inconsistent (some games are noticeable faster, others aren't), and 600 MHz doesn't work for everyone. I haven't found any solution for either problem. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Awesome. Good to know the culprit. I'll just switch to another governor until a fix is pushed. Thanks, man!