yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[/QUOTE]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.[/QUOTE]

Sweet! Thanks man, you rock! Its been so long since I ran this kernel as I've been on lollipop ever since November lol! Its awesome to have it back & kickin' on LP! Thanks again bro!!???

Sent from my OctOS d2att

Beware "The Kraken"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
No need to wait. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KentuckyGuy447:
Just now seen that and I guess its working because MCPE is running a lot faster, way more fps espically around thick forestes! Phone is also running noticeably faster but battery is draining faster(understable because GPU has to work harder.) Great kernel friend! Already my favorite by far and hope to see it grow!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Negative. Stock battery as mentioned. I do have greenify running, but aside from that nothing at all... I do pay attention to certain details that are known battery drainers and have some tasker rules setup to turn off wifi, lte etc, but nothing fancy like underclocking etc. I've achieved 6h+ back on 4.3 with AOKP+KT combo..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
hi,

can new kernel be used for S3RX 4.0 TW or TMS3KK 3.1 TW 4.4.2?

or it's only for CM11+

tnx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
AOSP ROMs only, for TW try neocore TW version

Sent from my OctOS d2att

Beware "The Kraken"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Just wanted to confirm that dpk is running smoothly on CyanideL 5.02 RC 7.1 (as expected)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodstorm666:
Hmmm. The latest build is force closing apps on startup. I've cleaned the cache and dalvik.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New AOSP 4.4 & 5.0 builds are going up! Changelog:

Synced with CM

Fixed a longstanding bug I accidentally caused in intelliactive, and cleaned up asswax a little bit

Fixed rotation for SPH-L710T (triband) devices

Added new builds that support older KitKat ROMs. dkp causes problems (GPS, sync, etc. not working) on ROMs built before October 2014 or so. Builds listed under "dkp for AOSP 4.4.x (old ROMs)" should fix these problems.

Can you get me a logcat after an FC? I haven't had any issues like this.

If you've been using another kernel, you could try reflashing your ROM to clean up anything it left behind. Another user reported similar problems, and reflashing fixed it for him.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
How does this compare to Shift that comes with CyanideL?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
I let Shift run for a couple of days and I can't say I saw anything special with it... DKP has more to offer IMO and it's my favorite for a while now. Battery goes fast on CyanideL with either one, but that's due to the issues with the wakelocks from Google play. Since I fixed that, on a standard battery, I'm getting an average of 1.1%/hr on deep sleep and over 4 hours screen time. Running stable, no FCs or anything like that... The only issues I have come upstream from CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodstorm666:
Reflashing my ROM cured the problem. Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chalky7880:
[MENTION=4932679]decimalman[/MENTION] don't your kernels usually have selinux set to permissive?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodstorm666:
Fast charge is not enabling? How do I fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Dude, your posts are extremely vague... People here are not fortune tellers, we can try to help but you gotta give more info than just "this isn't working, how do I fix it?"... Here's a solution to all of your non descriptive problems: go back to stock and stop flashing stuff on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodstorm666:
Dang dude you don't have to be so hostile. Fast charge does not enable whenever I try and enable it with the quick toggle. I'm using the latest build of this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
"it's not working"..."be more specific about the problem"..."oh! It doesn't work when I click on the button"... - You see where this conversation is going?...

Change it with something else than the quick settings button, like with trickster mod... What happens?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodstorm666:
OK it seems to enable when using trickster MOD, thanks. But why won't it enable using the quick toggle? Is this kernel incompatible with that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Just the TW kernels.

I'm guessing your ROM is looking in the wrong place for the setting. It shouldn't be very hard to fix. What ROM are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bloodstorm666:
I am using beanstalk 4.4.4065.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
[MENTION=4932679]decimalman[/MENTION] - would it be possible for you to update dkp to 5.1 for the S3? There's quite a few ROMs out there updating to this version and I would like to try them out with dkp if it's not asking too much :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I second this request. I just switched over to the unofficial CM12.1 build, and I'd love to pair it with some dkp goodness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Working on it now. :) Git choked on the recent camera changes in a really bad way, so it might take a little while to get everything building again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Thanks a million man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's totally untested, but there's a build for 5.1 on MediaFire. I'd suggest making a backup before flashing it. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Tests with cm12.1 is working good only in performance app can't do to check memory setting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
What happens when you try? Can you get me a logcat afterwards?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
OK. When go to charge tap the program close I try with pacperformance and when go to memory tab the program close.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
No probs here, using kernel adiutor from play store! Which by the way is a bad @$$ app!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi I download the kernel adjutor from play store and the problem with kernel adjutor don't appear I think now the problem is performance control app and pacperformance app. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Sure, imho its the best kernel management app you can use for lollipop & the only one I use. Also has se-linux switch built in
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
What about Trickster Mod in Lollipop? It was always my go-to app for kernel configuration on Kit Kat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Plain ol' Performance Control (which I assume PACPerformance is based on) used to do this too. It's fixed in regular PC, but I guess PAC hasn't picked up that change. IIRC, it's something about the UKSM settings in dkp, which are a little bit different than normal UKSM.

If you'd rather not use a separate app, send me a logcat after the FC and I'll see if there's anything I can do to get it fixed.

It's definitely pretty slick. If it had a setting similar to Trickster's "Override Minimum Voltage", I might even recommend it over Trickster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
I've been using it on LP without any issues at all - its also my favorite. If you run into issues with it let me know and I'll try whatever you did on my side.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Thank My friend bit after install kernel adjutor the problem gone I can adjust now the low memory killer. Thanks for very good kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], the dev has a thread here on XDA & is open to suggestions as he's always trying to make the app better, especially suggestions from a kernel developer? http://xdaforums.com/showthread.php?t=2986129 check it out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Has anyone else noticed in 12.1 that the superuser icon permanently displays next to the signal and clock icons after launching Trickster Mod? It's a minor annoyance, but I'm wondering if it's just happening to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I just added a pull request, so hopefully this will get merged soon. :D

EDIT: It just got merged. I'm working on getting a few more options to show up in Kernel Adiutor, and I'll add a recommendation in the OP soon.

Just thought I'd offer. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], NICE! Thats awesome! This is gonna be great! Can't wait;):D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hm, I am having one decently major problem with the 5.1 dkp kernel at the moment. If I enable battery saver mode and locking the phone, after a minute or two goes by I can no longer wake the screen with either the home button or the power button. The battery light continues to blink, so I know the phone is still "on" behind that black screen. My only recourse when it happens is to hard reset. I can confirm that this does not happen when not using battery saver mode.

Also, it does not happen when using battery saver mode with the stock kernel. This is reproducible every time I turn on battery saver mode, lock the screen, then try to unlock it a minute later.

PS - it has happened when using different governors too (asswax and intellidemand in my case), so I don't this it's governor-specific.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Download sys log from the play store, reproduce the incident reboot & run sys log. Then use a PC or if on phone use browser to upload so [MENTION=4932679]decimalman[/MENTION] can take a look. Last kmsg, dmsg & logcat should be all he needs ;) :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, I'll post them next time it happens. I charged my phone for a while, and now I can't reproduce it as easily. I'll just upload the logs the next time it happens naturally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Uh oh. AFAIK, there aren't any 5.1 ROMs available for Sprint yet, so I might have to build one myself just to investigate this.

I'm stumped. I don't see anything that would have obviously broken the 5.1 build. A few questions, since I don't have any better ideas:

If you connect your charger when your phone won't wake, does the LED turn on? Also, does it happen with the charger connected?

Does freelunch cause similar problems with battery saver turned off?

Are you underclocked or undervolted?

I'd be most interested in the last_kmsg, but it'll probably get eaten by the hard reset. :( The other logs could still be useful though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I wouldn't kill yourself trying to troubleshoot this if you'd have to go out of your way. It happened to me twice earlier, but I haven't been able to reproduce it since. Here were the circumstances when it happened:

- Phone switched to battery saver at 15%

- Phone was unplugged

- Was on either asswax or intellidemand (tried both)

- The low battery LED continued to blink even after I could no longer wake up the phone

- No under/over volting.

- ROW scheduler

- Fast charge enabled in Trickster Mod

But like I said, I'll wait and see if it happens again. If it does, I'll post the logs on here. Thanks for all of your work with this kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Alright, I was able to run into another battery saver-related error, even if this time it was a little different. I enabled Battery Saver manually through the quick title in the notification drawer even though I still had like 50% battery left. I tried locking/unlocking the phone, which worked fine this time. But then when I tried to use the quick tile again to set battery back to Balanced the icon would change but the phone remained in Battery Saver mode. When I tried to press the "Turn off Battery Saver" button in the notification for Battery Saver mode itself, the phone locked up and I was forced to do a hard reset.

I also notice that whenever this happens my preferred network is switched from LTE to 3G after the reset. I suspect this has something to do with Battery Saver mode not being terminated properly, and I worry that other settings aren't being properly reverted after the reset.

I've attached all of the logs that I thought might be useful. I'll just have to stay away from Battery Saver mode for now because I don't feel like flashing the whole ROM again just to get the stock kernel back. I don't feel like waiting for my ART cache to be rebuilt. Anyway, hope this helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
DKP Kernel for Lollipop 5.1 work great for me (with asswax CPU governor). Except for my front camera which is not working... Maybe something related to a new CM commit? I don't know I'm not an expert....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Unfortunately, I had to go back to CM original kernel (I'm using this CM12.1 ROM) I tried the last version of DKP kernel for Android 5.1, but today the battery got really hot and I found that mm-qcamera-daemon was running constantly, causing a huge battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I just uploaded a new set of builds. They include a change that is known to cause problems. I think I fixed the cause of those problems, but I can't be sure without some more people testing. It's possible that these builds will cause random reboots and/or touchscreen weirdness. If you have any issues, let me know.

Changelog:

Synced with CM

Improved support for Kernel Adiutor. If you haven't tried it, you should. The latest beta build even has an Override Minimum Voltage setting! :)

Changed a bunch of power management stuff. Battery life should be a bit better for it.

Fixed a bug in the touchscreen driver that caused e.g. Sweep2Wake to gobble battery.

Added Sweep2Wake and DoubleTap2Wake. I'm not sure why Trickster doesn't show the settings, but Kernel Adiutor does. DT2W can be kind of stubborn, but S2W works well. EDIT: Enabling either option on these builds will eventually hang the touchscreen. I should have fixed builds out later today.

EDIT: It's been longer than I thought since the last build. These builds also include more optimizations to UKSM scanning; scanning is ~40% faster. They also fix a bug in ISAAC that can cause problems in some games.

It's possible that the freeze was the same bug showing up in a totally different way. I have kind of a hunch about what's going on, but I don't have any idea how or why it would happen. I did some digging in the source, but I haven't found anything yet. 5.1 ROMs are finally starting to come out for Sprint, so I'll take a look sometime soon.

I'm guessing that freezing in the middle of disabling battery saver might have left a few settings in a weird state. I would think it would only affect a couple settings at the most, and shouldn't cause any serious problems.

I didn't want to touch the camera stuff until CM was done working it over, but it looks like they've slowed down a bit. Once I get my hands on a 5.1 ROM (I'm on Sprint, so I don't have a lot to choose from :(), I'll take a look.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Sweet! I'll DL & report back in the A.M. it's pretty late here in Alabama;) Thanks for the update, I'm on the previous build running flawlessly!:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, let us know how it goes. Specifically try out battery saver mode for a while and see if it locks up your phone. The previous build had that issue, so I was forced to go back to stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], [MENTION=4570464]ScOULaris[/MENTION],

OK, I've been running the new build for 6hrs & no random reboots, no glitches! Unfortunately battery saver mode still locks the phone up,:what: I was able to toggle the QS button & pull the battery b4 it completely locked up, so I didn't have to reflash ROM or factory reset, other than that its much better on battery & performance than the last build. I don't really use battery saver mode, so its not a deal breaker for me, I'm confident decimalman will figure it out soon;):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Ah, okay. The battery saver glitch is a dealbreaker for me at the moment because I use it all day at work, but as soon as it's ironed out I'll be hopping back on dkp for sure. Best kernel for the S3.

Thanks for testing it out and reporting back with impressions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
I'm actually getting amazing battery life with this kernel, better than I have ever had on LP, hence the reason I don't really need battery saver, however I realize every phone & user experience differs, but being on LP since Nardholio dropped the 1st d2att beta, best battery life yet! [MENTION=4932679]decimalman[/MENTION] Loving it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Can you tell me if the camera works? Hopefully you're using cyanogen camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Well I'm actually running a test build that hasn't been released yet with the latest commits to fix the camera. B4 flashing dkp, stock camera was working as well all 3rd party apps, after flashing dkp stock & 3rd party still work flawlessly ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Sweet, I'll go ahead and flash dkp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
If you backup your current kernel using flashify it'll be much easier to restore if need be, instead of having to reflash the ROM or wipe anything. That's what I do just a suggestion:D;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Did not know about this, thanks.

Also, dkp broke cyanogen camera. That was sad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
I hope that test build is on the ROM I'm thinking of and it gets released soon. I'm having withdrawals from it:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
You know it bud! ;) It's coming :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Confirmed latest DKP works as expected on latest PAC ROM, including camera full functionality.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just keep in mind that your phone might lock up when switching to battery saver mode. This will hopefully be fixed in a future release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Thanks for the heads up, but is it something intermittent? I just tried it and no lockups...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Lock your phone for about a minute or two after turning on battery saver, and then see if it will unlock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Done - no issues...

Things maybe worth mentioning...

i747m

Dirt flashed PAC ROM

LTE is off and I'm connected to wifi

No background

If you would like more info feel free to ask.

PS: scratch that...once I posted this and tried to get to balanced mode through the notification drop down the phone froze up... I'm unsure I'd that's what others are experiencing but its definitely an issue..lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spartan268:
Could you post your battery life results at the end of a day of use? Most interested in the screen on time before it dies.

Sent from my d2lte
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hah, there it is. I knew that edit was going to come eventually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tech128:
Unfortunately latest dkp with latest pac man rom 5.1 does not work 100%

The camera has major issues.

Sometimes when I open it it will work, other times it will not.

It will either say "Cannot connect to camera." or "Camera has stopped"

The front facing camera never works at all no matter what I try.

Do you need a logcat for this or is it something you're still looking into?

Everything else works great, thanks for putting such hard work into this kernel, it is appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Please read the posts right before yours from me...im running the latest from PAC ROM and everything is working as expected aside from power save mode. Check the PAC ROM thread, I posted my solution in regards to the camera issues there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
If someone has a mobile friendly link to this for 5.0.2 that would be cooool ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Use opera browser, that's how I DL it on mobile ;):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tech128:
Well I checked in the last few pages of the thread and basically what you're saying the solution is to be running the latest pac man rom and dkp kernel, then use a camera app from the play store.

Well I've tried all that already. Same thing.

So for me at least, it is not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Did you uninstall the stock camera?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Not working for me either, and yes I uninstalled the stock camera
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
I am also using latest pac with DKP Kernel on my t999 and open camera working for photos and videos but from camera can't connect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Sorry to hear that guys.. Aside from being on a d2can I'm also on MK5 baseband and modem (not that I believe that would have anything to do with it...) there should be no difference between our devices..

Here's exactly what I did, step by step:

In TWRP did a full wipe including internal storage.

Installed pac rom and slim full gapps.

Booted up, tested camera - didn't work.

In rom Toolbox pro I cleared cache and data on the stock camera, froze it and uninstall. Also uninstall all camera apps.

Reboot.

Installed Google camera.

Success.

Installed dkp.

Camera works.

I would say if you did anything different from this (for as small as the difference might be) try it the way I did it.

I'm unsure why it would work with me and not you guys, I might be one of the lucky ones... I can say that the camera doesn't work the same way it used to on KK and previous versions - takes longer to connect to the camera etc, but aside from that I can take pictures and video...

Again, good luck, and worse case scenario you might need to wait for further development of LP on our device...

Also, be aware that it seems that camera is broken again on the newer version of CM - I tested out CyanideL and CM a couple of days ago and the issue was back.

---------- Post added at 06:36 AM ---------- Previous post was at 06:21 AM ----------

I've been running for a few days now and I can tell you that screen time is about the same as the KK version,maybe a little better (got to almost 5 hours one of these days) - I won't post the results from any specific day because I use a lot of network intensive apps when using screen most of the time, and I also do a lot of conference calls on the phone, ruining the stats in regards of the "battery life with screen time". As surprising as the 5 hour screen time might be I do have a black wallpaper and a dark theme. I'm on the stock 2100mah battery (the one that came with the phone almost 3 yrs ago!!) .