yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
The latest PAC build is now April 19. If your running an earlier version then cam may not work. It is working in latest build. I can't speak for latest dkp kernel on PAC but would be interested to know if anyone is testing that combo.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
I've already backed up PACs kernel and I'll give it a shot as soon as my battery charges enough... [MENTION=4932679]decimalman[/MENTION] - any chance you could update/fix dkp so that the issue with the battery saver doesn't recur? (sorry for asking)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
I am on April 19 PAC and stock camera is not connecting after each snap same after flashing dkp too and open camera works but not connecting to front camera and giving error something as camera in use by other applications

Edit:- I have disabled stock camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Sorry, I'm confused... Camera did not work on pac with and without dkp?

---------- Post added at 07:39 PM ---------- Previous post was at 06:54 PM ----------

To answer your question: yes, camera does work with dkp on BUT I do see a performance issue that seems to have been fixed on your latest in regards to the camera that comes back with dkp. If you need more details feel free to ask, but I think dkp might need to be updated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Oh yeah, I was supposed to be working on this. Sorry everyone.

How's this? Unless there are other issues that I haven't spotted yet, it should fix battery saver. As always, feedback is appreciated. :)

Battery saver silently switches to freelunch when enabled, but freelunch is really, really broken on 5.1. I have no idea why. :confused: Anyway, I disabled freelunch completely, and modified the battery modes to reflect that. As a bonus, I fixed up the modes in general, so switching modes won't eat whatever settings you had applied: performance won't lower your maximum frequency if you're overclocked, power save won't raise your frequencies if you're underclocked, and balanced will restore whatever custom settings you had.

Oh, and as a second bonus, this build has the latest camera commits from CM, which means that the stock camera should work on recent ROMs. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Anyone have a mobile friendly link for the 5.0.2 variety?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
All looks good! Thank you sir! On a side note I did run into a "can't connect to camera" error on first boot up. Cleared cache and data from camera app, reboot and all is good. In regards to the battery saver it's looking good too! Cheers!

---------- Post added at 05:06 AM ---------- Previous post was at 05:04 AM ----------

The link is mobile friendly, just make sure you always pick the browser to open links/download instead of a download manager software... I just downloaded it from my mobile using Chrome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Thanks! I'll flash this later today and report back with impressions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Beat ya too it, lol:p its been 2 hrs or so, but all is good! I've had no issues, all the previous problems seem to be resolved!?

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

[MENTION=4932679]decimalman[/MENTION], with the selinux switch being removed from the latest versions of kernel adiutor, what's the best way to get permissive to stick thru reboots? Man I really miss that switch...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
MediaFire is the only download location. If it's not working with the browser you're using, try Chrome or Firefox instead.

I'm sure there's a more elegant way, but the easiest way I can think of is an initscript. In /system/etc/init.d (or /data/local/userinit.d if your ROM supports it), create a text file named e.g. "10selinux", set its permissions to 755 (rwxr-xr-x, or whatever as long as it's executable), and write the following into it:

#!/system/bin/sh
setenforce 0

Reboot, and you should be in permissive. The regular init.d way won't carry over when flashing a new ROM, but the userinit.d should (unless you wipe /data).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], thanks for the info & the directions! It works great with the ROM I'm on! Appreciated bro!:D;):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Front camera still not working unfortunately (using latest 04-21 build)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
I too confirm that front camera is not working after flashing latest dkp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Does it work with the stock kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Dang it... I just realized that the same was happening to me (not much of a selfie pic taker) - I restored the PAC kernel and it works fine with it... Sorry [MENTION=4932679]decimalman[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi... Yes its work with stock kernel on my side
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Alright, I'll look into it later today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New AOSP 4.4, 5.0, and 5.1 builds are going up now. :)

Changelog:

Synced 5.1 with CM. Camera works on recent ROMs!

Fixed a bug that broke the front camera on 5.1.

Disabled freelunch on 5.1, since it's very broken and causes freezes and glitches.

Overhauled performance profiles/battery modes. Balanced will save and restore custom settings, performance won't lower your frequencies if you're overclocked, and battery saver won't increase your frequencies if you're underclocked.

Removed DT2W and S2W. It takes ages to register the initial touch, so I don't think I can get them to feel natural.

Built with a shiny new toolchain based on GCC 4.9.3.

A few small changes and optimizations.

EDIT: My build script misbehaved, so the original builds were missing some commits. I've taken the old builds down, and new builds will be up shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Re: [KERNEL][AOSP4.4/5.0/5.1] dkp - d2att - 4/10/15

What's the recommended governor now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi with this last update cant connect camera ....camera error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dyn4myT:
Same thing for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Bizarre, it was just working before I rebuilt. I'll get a fixed built out shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Thanks for your fast respond. I like use dkp kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Apparently, my build script was misbehaving and didn't pull in the new commits. Oops. New builds will go up shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Fixed builds are up.

I stick with tierservative, but asswax, intellidemand and intelliactive are pretty popular as well. Unfortunately, I just noticed that asswax has developed a new bug. You might want to wait until the next update to use it.

EDIT: asswax seems to work fine. I'm not sure why it crashed on me a few minutes ago. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Thanks decimalman now all is working good.?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EGM92:
Awesome work. Thanks. Just curious if your latest build is compatible with 5.1.1 based roms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spartan268:
Yes, I'm on 5.1.1 and so far so good.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hmm... Tempted to go back to dkp for the better battery life, but I've gotten used to the stability of the stock 5.1.1 kernel. Can anyone confirm that battery saver no longer causes the phone to lock up? That was my main issue in the previous dkp release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dyn4myT:
Everything is perfect now, thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
[MENTION=4932679]decimalman[/MENTION] testing 4/25 on my latest d2att PAC build. Kudos! I believe you nailed 5.1.1 with your latest release. Well done!!

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Last version work great on 5.1.1 thanks a lot, great job!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Latest version is running great so far on 5.1.1. Using Asswax governor with Zen scheduler. Thanks for all your work once again, decimalman!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The freeze bug is still happening in that build, it's just less common with freelunch disabled. It appears to be caused by CPU hotplugging with the CPU boost thingy enabled.

There's a new 5.1 build on MediaFire. I disabled CPU boost, enabled freelunch, and patched mpdecision back in. Call me crazy, but I'd rather have functional CPU hotplug than yet another battery-eating CPU boost thingy.

EDIT: freelunch is still a bit wonky, but I haven't seen it crash yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hm, okay. I'll flash that version and give it a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I had to restore a backup today. Battery got to 10% turned on battery saver for a few seconds before remembering this could be an issue still (build 4/25 PAC ROM) then my battery went dead after a while. Wouldn't boot past the Samsung logo. Hot to recovery and after getting it charged to about 50% tried again. Vibrate once, Samsung logo then blank screen then repeat and repeat some more. Restored nandroid. The kernel also deleted itself once after accidentally over clocking to like 1900 or some such (damn touchscreen :))
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Damn. Battery life on this build has been fantastic, especially when idling. Was it the re-inclusion of hotplugging that made the difference? I'm running it with the 4/22 build of matrixzone's unofficial CM12.1 build at the moment, and my phone is lasting all day with plenty to spare before I go to bed. Great work.

I'm going to hold off on upgrading to the official nightlies until there's a dkp release to go with them. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dunkin11:
I am using this kernel with the official nightly. I haven't experienced any issues so far. Camera works. Awesome kernel btw!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Eh, I wouldn't. Right now changes to the stock CM kernel for d2 devices are coming in pretty frequently, so I'd always rather have a dkp build that's the same day or newer than the CM ROM I'm running. That way I can ensure that it's synced with CM and not missing any important commits.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dunkin11:
I'll take my chances. With Flashify, it's relatively painless switching the kernel. I do full backups before flashing a new nightly just in case things get really hosed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
dkp falls back to auto-hotplug when mpdecision isn't available, so hotplug was happening already (it was just really buggy because of the CPU boost). I suspect that mpdecision does a much better job (both in terms of power saving and performance) than auto-hotplug, which would explain the difference in battery life with the latest build.

I can't figure out why ROMs removed mpdecision (CPU boost bug notwithstanding). On newer CPUs with fancier power management, it's probably fine to leave all cores powered on all the time. On our hardware, it's not. The only deep idle state available on our CPUs is disabled for stability reasons, leaving only high-power idle states. That means that unless an idle core is hotplugged out, it'll sit in a high-power idle state, doing nothing except wasting battery. Without hotplug (or at least a deep idle state), battery life is going to be awful.

Incidentally, in dkp the deep idle state is fixed (I think :fingers-crossed:) and enabled, and hotplugging is always enabled (except with the performance CPU governor). Sometimes I wonder whether dkp is living up to the claims I make about battery life, but then stuff like this happens. :laugh:

I suppose I should post new builds. I haven't made any changes since the last build, but nardholio has been committing like a madman. I don't think any of his commits are critical, but dkp has fallen pretty far behind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
The only kernel commit as of late that caught my attention was the one that speeds up boot time. I'm fine waiting a while for the commits to slow down, though. No sense in you trying to keep up with every single change made by the CM maintainers at this point in time. My 4/22 build is running great alongside your kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Eh, I was too weak. I heard that YouTube playback had been smoothed out in the latest nightlies, so I flashed the 05/01 build of CM12.1. I'll stick with the stock kernel until the new dkp build drops, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Lies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
He just said your commits aren't critical. You gonna sit there and take that?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Pistols at high noon then, nardholio? :p

By "critical," I just mean that I don't need to drop everything to get a new build out. Commits required to support ROM changes or close exploitable security holes are critical, everything else isn't. I'm lazy. :)

I just finished merging everything, so there should be new builds out sometime this afternoon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New builds for AOSP 4.4 and 5.1 just landed. I'm dropping support for 5.0, since very few people are using it.

Changelog:

5.1: Synced with CM

5.1: Disabled CPU boost (it's interfering with hotplug), re-enabled freelunch, set up the installer to patch mpdecision into the ROM

4.4: Fixed mpdecision not starting

I still haven't tracked down the boot issues on 5.1, but I'm working on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Aww, snap. Gonna flash that right now.

Also, I decided to send a little cash your way as a thanks for continuing to support the S3 with your kernels. I've been using yours for quite some time now, so I figured a donation was long overdue.

Confirmation number: 9LG25396N8860874D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks! :good:

EDIT: Just added you the OP. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Tried latest build of dkp with Official CM12.1 Nightlies 5/03 build and it wouldn't read my ext SD card. Removing and reinserting the card didn't help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Does it work when you're using the stock CM kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
I am also using LS LP Rom with DKP 2nd May build on my d2tmo and not having any issues in reading SD card So may be this issue is released with Rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Weird... Im on CM nightly from 5/2 using dkp and have no issues at all... Either its that nightly or... Did you fix permissions after flashing dkp? There should be other issues for not doing that but...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
I reflashed my ROM and the dkp kernel and the SD card is working again. I'll report back if I find anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
What's the lowest anyone has clocked their phone and had it remain stable? I have it at 270 MHz at MV. Works like that 100%. Don't want to push it and have unexpected consequences. Running this on official cm 12.1 and other than the fact that if it has an unclean shutdown you have to reinstall the kernel (takes like 2 min and doesn't mess things up) it works great! I got it oc to 1566 cuz I'm not into changing my battery too much ;) (I now have 3 of them due to eBay and some mah bs)

To elaborate on that, if you want to buy a battery, if its not bigger than the origional, its 2100 mah. I don't care what they tell you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
[MENTION=4932679]decimalman[/MENTION]

Glad to be back on dkp. Didn't have much time for phone things, but clean first flashed official cm12 nightly by Dan last week and now some dkp 5 minutes ago. Feels good! :cool:

Saw the kernel defaults on tierservative and you'll excuse me for not paying attention, but is it ready for prime time? I remember when you added it last year, but you're still putting a lot of effort on freelunch. Simply wondering if you suggest sticking to tierservative or switching to freelunch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
[MENTION=4932679]decimalman[/MENTION] & all,

I've been running into a signal drop from my provider since the very beginning of lollipop being ported to our device - all ROMs and kernels have done the same, so far from pin pointing this to dkp, but maybe have some direction or input from others on this...

Long story short, the signal "randomly" drops and comes back in a few seconds in an area where I have good signal. I have noticed that maybe is during transition from LTE to 3G, etc, but I might be wrong. I reported the same issue on another thread but it was somewhat disregarded due to the fact that I have an I747M and "things might not work properly on this phone" since CM is building for I747. Oddly enough right after someone else with an ATT phone reported the same exact issue, but it died there.

Is this a known issue and would it have anything to do with the radio/bootloader versions used? I don't think it's a wide spread issue, so I'm wondering what can I do to stop this...

Details:

Radio/bootloader: MK5

Provider: Rogers

Note: as soon as I flash KK the issue no longer occurs.

Thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I have an i747 and had similar experience. In addition, I would loose LTE completely and have to toggle LTE to get it back. All seems to be resolved by removing all APNs except the one I need. This also dramatically improved battery life!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Thanks for the reply.

I had tried that in the past and I believe the issue persisted, but just in case I just repeated the process - APNs come back after flashing ROM's

I'll report back.

Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I've noticed a few times now that my phone won't boot into CM12.1 when running the latest dkp after a reboot or shutdown. Whenever this happens I need to boot into recovery and then reboot my phone from there. It isn't doing this on stock CM kernel, so I'm pretty sure it's related to dkp.

I'm running the latest dkp with the 05/03 build of CM12.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Been reported already. He's working on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Oh, okay. I've been following the thread closely, but I guess I failed to notice that being mentioned before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Issue persists after removing the other APNs... :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
I think it was the sprint board that reported it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
54 MHz should be perfectly stable, but as you go lower, governors will start to act funny. You can probably reduce the voltages quite a bit as well, but that will cause instability if you go too far. For me, 54 MHz is 100% stable at 730 mV, and I think I've pushed it down below 700 mV without too much instability.

I targeted tierservative more towards replacing interactive as the default governor, so my goal was for it to feel smooth in every possible situation, without resorting to tricks that eat battery. With freelunch, I was aiming for battery life at any expense, including letting it work poorly in certain situations. If freelunch works for you, you'll probably get better battery life out of it.

This probably isn't kernel-related. AFAIK, managing the modem is mostly handled by the ROM, with the kernel just moving data back and forth. Of course, I'm not very familiar with the connectivity stuff, so I could be totally wrong.

I'd recommend getting a logcat while it's happening and sending it to the dev, along with an explanation of what's happening. I wouldn't mind getting a copy as well, since I'm curious.

I have no idea why this is happening. It seems like something is crashing very early during boot, before RAM console (AKA last_kmsg) starts recording debug information. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
[MENTION=4932679]decimalman[/MENTION]

Thanks a lot for the prompt answer. So far, tierservative seems alright, although I'm getting a slight hiccup sometimes when going back to homescreen and opening my app drawer. Just a tiny tiny bit of lag. Hard to describe.

I'll try freelunch nonetheless and if both are similar in performance for what I do then hey, more battery for me. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Thanks for that - I just installed the latest bootloader/modem available ( flashed stock from sammobile, root, etc ) just to get that out of the way... I am now booting to PAC-ROM with your kernel and will test it out - if it recurs I'll definitely provide a logcat. Again, thanks! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I get twice the battery life from this than with stock cm 12.1 official kernel.

Min: 270 MHz

Max: 1577 MHz

D2att

NJ1

---------- Post added at 08:17 PM ---------- Previous post was at 08:14 PM ----------

Voltages
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Just did this last night. Just a little bit but alarm rang and everything works like this. Just checking it out real slow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Just installed with cm12.1 but I don't known wish setting is the best ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
[MENTION=4932679]decimalman[/MENTION] - Unfortunately it seems that the issue is recurring... I notice "less" drops (referring to the signal icon on the statusbar) but they do still exist. Oddly enough, while before (on the 4.3 bootloader and radio) I never noticed calls not coming through, since updating to the latest bootloader/radio for my device (OBI1), just in less than 24 hours I've had 4 missed calls. I gathered this logcat from 5 minutes prior to the call being received until about the time that I got the text reporting the missed call (hopefully it'll have the disconnect/reconnect and some info on why this is happening...)

https://docs.google.com/file/d/0B87tXCW0uM9IMVZLaUMtS2xET1U/edit?usp=docslist_api

I'll also submit the logcat to [MENTION=4478916]manfromgta[/MENTION] but, as I told you, i747m is not supported by PAC ROM and on top of it I'm still on his unofficial release, so I'm unsure if he will take a look at it.

I appreciate your help on this - thanks a bunch!

Edit: here's a shorter logcat from just a few minutes ago. I just saw the signal drop visually on the statusbar while just closing all background apps and opening ktweaker (no changes were made).

https://docs.google.com/file/d/0B87tXCW0uM9IN1RneUN0OXMtX3M/edit?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
If you wanna get technical, the download number showed 0 when i pressed the button :p

On or off doesn't seem to make a difference. Running nanolunch and it's hotplugging fine for now.

Whats the difference between freelunch and nanolunch? why would I chose one vs the other?