yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwmike:
Thanks for the quick response! My original msg was wrong in that it was the lowest possible scan delay (100ms) rather than 1 ms. I just now updated to the latest Kernel Adiutor - Mod from the app forum rather than

the one from the play store and it seems to have resolved item 1. As for item 2 I was trying higher scan delay settings ie greater than 1000 ms and the fact that they were ignored when >1000 was why they wouldn't stick across boot. General conclusion - this is all Kernel Adiutor related and not DKP kernel. Thanks for getting me on the right path!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Hi

Will you be releasing a new 5.1.1 kernel update?

I messaged you but no reply
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
No problem. I should probably change the scan period setting so that when a larger setting is applied, it uses 1000ms instead of ignoring the new setting altogether.

I'm a bit behind on my PMs. Oops.

I've been meaning to put out an update, but I haven't gotten around to it. I switched my toolchain to the latest version of GCC, and it's showing a ton of new warnings. I'd like to get them all fixed before the next update since most of them are obvious bugs, but it's slow going. In the process, I managed to cause a new bug that's currently ruining my battery life. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Oh wow.. hope it sorts out for you.. sorry to hear that [MENTION=4932679]decimalman[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
Hey, so I heard about the battery drain bug. Is it still present? This kernel is the only kernel that has working overclock values on CM13.

I tried using the KT747 kernel but the kernel doesn't have oc values. And the kernel editor is pretty buggy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's a new build for 6.0 up. I didn't do updates for 5.1 or 4.4, but I can if there's still interest.

Changelog:

Synced with CM, Linux 3.4.112

Updated to GCC 6 and fixed a zillion new warnings (a few of which were obvious bugs)

Removed the profile switch script and bundled mpdecision: the profile switch script doesn't work on MM anymore, and mpdecision is already included in ROMs

Fixed (for the 173rd time :crying:) falling back to auto-hotplug if mpdecision is disabled; tweaked auto-hotplug defaults

Switched UKSM to a deferrable timer, which might make it a bit easier on battery

Tweaked GPU frequency sampling

Fixed a few minor issues that interfere with deep sleep

I have a few more changes in the works as well. Hopefully, it won't be another 8 months before the next build.

Checksums:

0855f52701abbd1909b62c0663ccac19 dkp-aosp60-d2-20160801-dkp-3.4_6.0.zip

You mean the issue I posted about a few posts up? I never released a build while I was dealing with that. Also, it turned out to be completely unrelated to dkp. While tracking the issue down, I noticed a few minor issues, so my loss is your gain. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
Yay. Thx for the update, This kernel is the only one that actually worked on 6.0.1 for over clocking properly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4932679]decimalman[/MENTION], Thanks for the build update! Glad to see you active again! Welcome back ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
I was getting atrocious battery life (with an extended battery) on CM13 (totally not Pokémon Go). The battery was draining as I was using it. I was also getting the landscape keyboard bug, burning hot bottom half, and empty cell triangle (side effect of having a Bell version on AT&T)?

I Googled "cm13 d2att bugs" or whatever and it said the fireball bug was no longer happening in dkp. I thought… Gosh, that wasn't updated in a while… it probably is a better idea to stay on a more up-to-date kernel. I went to this thread and low and behold, a build was just released! Just in time.

Wowwwwww… Talk about a coincidence!

As soon as this is gone:

I will tell everyone how it is running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Im am still interested in a 5.1.1 kernel! please let me know
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
I tried it on S3 as I was interested in the overclocking capabilities that this kernel has. My phone got extremely unstable while using the default settings, charging didn't do anything, the battery drained faster than it charged (And I have a fast charger so Damn) I switched back to the kernel I was using previously KT747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
You got it. :)

Due to popular request, I'll continue to release builds for 5.1 and 4.4. New builds are up for them. The changelogs are basically the same for these builds as for the 8/1 build.

dfae019aea16db3eeac0ad28c82e9891 dkp-aosp51-d2-20160805-dkp-3.4_5.1.zip
2c002573e01190efee89525f5234013d dkp-aosp44-d2-20160805-dkp-3.4_4.4.zip
84f45bbbf2b80d8c836b60951340964f dkp-aosp44-legacy-d2-20160805-dkp-3.4_4.4.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
[MENTION=4932679]decimalman[/MENTION]

Is it possible to have some display tweakables? Like under volt and decrease max FPS?

Also, could you add some governors from KT747?

Thanks.

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XaveT:
I just installed this for my 4.4.4 ROM (LS-3.2 Milestone). It seems really solid! Thank you for your work, especially in supporting on my outdated ROM's OS! :)

Randomly, it also vastly improved my GPS lock speed, but I have no idea if it could do that, or it just seems like a placebo effect and my hardware decided to work quickly now for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I experimented with the screen voltage a while ago, but I wasn't impressed. It screwed with the color calibration and didn't reduce power consumption. As for limiting the framerate, I have no idea how to do that, but I suspect it would be more complicated than it sounds. I'll take a look.

If there's a specific governor in KT747 that you'd like to have in dkp, I'll look into adding it. As a general policy, though, I prefer not to add oodles of governors. In particular, I won't add governors that don't work ideally with the S3's CPU or that are poorly written and difficult to adapt for the S3 and/or dkp.

Not a problem. It's not too much work to keep the older branches updated, and I don't mind doing it as long as people are still using older ROMs.

I don't remember doing anything that would affect GPS. I hate to disappoint, but it's probably just placebo/luck/unusually good signal. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XaveT:
You are correct. After a few reboots it's been backto its old 20min - 1hr to get a GPS lock (not kidding or exaggerating, I end up walking away or playing a few rounds of a game while I wait for GPS to come back up).

LOL. Someday I'll either get a new kitkat device, or N/O will come out and I can drop support to kitkat :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Loving the Aug 1st dkp build....with your optimizations and a little overclocking, this old SGS3 running CM13 feels as fast as my wife's oneplus one!

Can't wait to see what you have in store for the next dkp update...

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
I'm still having issues related to battery drain, lag? and certain graphical glitches
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
One device seems stressful enough, thanks for taking the time to keep us all updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Interactive hotplugs, but asswax still doesn't :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Im confused as hell. I always rename mpdecision so its never in use. Can I still use asswax with mpdecision renamed in my system/bin?

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'll look into it. I'm sure there's something obvious that I'm missing. It was working for me earlier, but now it's broken again.

Edit: AssWax is still a bit broken. I'll get it sorted out eventually.

AssWax doesn't hotplug on its own. It needs either mpdecision or auto-hotplug (which dkp doesn't currently have) or core 2 won't get hotplugged. It's safe to leave mpdecision untouched with dkp--it's effectively frozen when it's not needed, and re-enabled when it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Any one using this with slim bean or xone? I can't get WiFi to turn on. Getting stuck at turning on WiFi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Hmm. That's not good. I packaged the kernel differently in this release, so I may have stirred up some recovery-related problems. What recovery are you using? Version? My guess is that the kernel modules (wifi driver included) didn't install correctly.

In other news, there's one last round of new "stable" builds going up on dev-host now. They fix hotplug with AssWax, and allow AssWax to be set on boot without locking frequency at maximum. I think that's the last of the bugs. :fingers-crossed:

I'll mirror to mediafire in a few minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Using latest cwm. I'm going to install twrp, download latest and try again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Awax not sticking!!! Thanks dm!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
What app are you using to set it? When does it reset?

That's two for CWM, none for TWRP. I'll go back to the way I was packaging before until I get CWM sorted out. New fixed builds will be up shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Still isn't hotplugging for me :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Sorry, dm wish I would have reread my post. I meant it doesn't stay pegged at Max freq. Still not hot plugging for me also. But having great results with nanolunch. Next up is nanoactive. How is it different from Interactive?

Thanks for the hard work! I am using TricksterMod donate version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
same behavior for me. nanolunch yeilded me incredible deep sleep. 8 hours or more screen off while sleeping with a total of 0.5% batt drain/hr.

something tells me that nano active works like interactive but measures on the nano time scale, like nanolunch vs freelunch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Loving the new build, the colors on the d2att are def a little bluer but I'm already used to it, using the nano lunch and super impressed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Hmm. Do either of you have CatLog (or whatever else) installed? Will you try rebooting, setting AssWax, opening CatLog and filtering "MP-Decision"? I'm curious about why mpdecision isn't doing its job.

Don't mind me, I was pretty brain-fried last night. :o nanoactive is almost exactly the same as interactive, except it uses more precise CPU load stats. I can't tell if it makes any difference to smoothness or battery life.

Whoa. I expected it to behave better than freelunch, but that's crazy.

Bingo. I'm not sure whether or not I mentioned it in this thread, but the existing CPU load interface measures in increments of 10 ms, where the new interface I use in the nano- governors measures in increments of 1 ns (i.e. one ten-millionth as long as the old interface), without much if any penalty for the extra precision.

Trinity colors aren't for everyone. A couple people suggested making it the default, so I did. There's a zip in the OP to disable it if (like me) you think it's too blue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Going to try it now. I've never filtered for a term before so hopefully I can manage that.

Lately i've been averaging 1%-0.5% batt loss overnight during deepsleep, when I know i'm not using the phone. What I was really impressed with is that out of that 8 or more hours, the phone itself was only awake for a combined total of 8 mins. I got a few texts and a bunch of emails which is what generally explains that.

edit** Well I don't know what the deal is, but when I booted the phone interactive wouldn't hotplug but asswax is. Seems like it's working. I'm confused lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
CatLog has a box at the top where you can enter what service you want to filter. Thanks for helping track this down. :good:

I used to average about 1-1.5% per hour at night on 3.0, but 3.4 really doesn't like my phone. :( Deep sleep like that is impressive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I have a lot of stuff turned off and use greenify. The things I don't have turned off is syncing and whatnot. If my phone isn't going to notify me when I get something, well then it's not really doing it's job for me so I like to leave sync on. I do have wifi turn off on screen off though which helps A LOT

---------- Post added at 02:00 PM ---------- Previous post was at 01:52 PM ----------

So here is what i noticed. I set asswax and it was hotplugging like normal. I set on boot and restarted the phone. When it restarted i went into trickster to monitor the cores. it was no longer hotplugging. Opened up catlog and looked for mp-decision but there were no entries. Set to nanolunch and hotplugging resumed. Went back to asswax and was hotplugging like it's supposed to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks. That tells me exactly what's happening. I'll put together a test build later today and PM you to see if it helps. :good:

I might have to check out Greenify. I can't live without push email so I keep sync and data/wifi on all the time. Unfortunately, I don't get very good signal at home, so I have to use wifi overnight. The wifi driver is horribly misbehaved and takes way more wakelocks than I think it needs...definitely not good for deep sleep.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Greenify is great. It makes apps behave like iOS. It hiberates apps of your choosing so they are not constantly running in the background. It will cause issues if you hibernate apps that you want push notifications from because you will stop getting them.

I use tasker to automate my wifi. When i turn the screen off it checks to see if there is any data being transfered in a 30 second interval. If there is no transfer it turns wifi off. If there is data being transfered via wifi it will attempt to turn off again in 2 more minutes. This way anything you are downloading doesn't get interrupted. When I turn the screen back on it auto connects back to wifi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Isn't this the same as changing the setting in Wi-Fi/advanced to turn off Wi-Fi when screen is off??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
CM13 and/or a bad battery.

Which governor and clock speed?

Say… black squares on rotation?

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
Battery Drain:

No, Cm13 is not the cause and my battery is the stock OEM battery that came with the phone 2100mAh.

Lag:

Governor: Performance (for gaming) & ondemand when not gaming.

Clock Speed: 1.8Ghz max & 0.7Ghz min

Graphical Glithes:

No, in the recent apps screen sometimes squares of recently open apps disappear (mainly in the corner of those apps)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'm playing with a few changes, but I don't think they'll be ready for the next build. There's a commit from CM that I think is required on ROMs from the last few days, so I'll probably just sync with CM so I can get the next build out more quickly.

I can't fix "battery drain", "lag", or "certain graphical glitches", because those are all very general terms. More information would help isolate individual problems that I might be able to fix.

What are your current settings? Did you flash dkp-vmin-XXX.zip? Do the problems continue even with the default settings, i.e. when not overclocked, and not using the performance governor? Have you verified that the issues are specific to dkp and do not affect the kernel included with your ROM? Is there anything concerning in dmesg or logcat, particularly error messages that repeat frequently (feel free to PM me a dmesg if you're unsure)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
I did not flash the vmin-xxx zip and default settings have this issue. The default kernel that comes with the ROM does not have any of these issues. So idk anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Battery drain: Under what circumstances are you seeing excess battery drain (e.g. screen off/on, when running certain apps, whatever)? After it's been draining for a while, grab a dmesg and logcat and PM them to me.

Lag: Unless there are specific circumstances that trigger "lag", I won't investigate this. I'm not trying to be a jerk, but "lag" means almost nothing from my perspective. Unless I can reproduce it for myself to see what's happening, there's no way I can figure out what's causing it and fix it.

Glitches: I'll look into this. I can't remember which glitches regularly happen for me on the stock kernel. I'll compare dkp with stock and re-evaluate my GPU-related changes to make sure dkp isn't causing any new glitches.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
A new build is up for 6.0 ROMs. Nothing major has changed, but recent ROMs require one of the commits from CM.

Changelog:

Synced with CM

Checksums:

df5b1f2a43514b4fc6a0c7d7675e47fd dkp-aosp60-d2-20160820-dkp-3.4_6.0.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
Thank you sir... Downloading now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
remember for 5.1.1 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
He didn't change anything really significant; it was just that there was a necessary change for CM13 in order for it to work right. There is nothing different that you are missing out on.

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]

---------- Post added at 10:54 AM ---------- Previous post was at 10:39 AM ----------

Well no duh you are getting drain!

Setting a higher minimum clock speed does next to nothing for lag and just kills battery. Common misperception.

The way it works is this:

With the exception of performance, governors are smart.

They ramp up the clock speed when it needs it or when you touch the screen, and lowers the speed when it doesn't need it to save power.

They react fast enough to jump to the proper speed when needed.

By setting a higher minimum, you lose all advantages of the years of work put into these efficient governors. It is like not giving breaks to your employees. Yeah, they can get more done, but they tire out and end up not working as well.

I suggest messing with the governor settings, specifically hispeed_freq (interactive) or optimal_freq (ondemand). And use interactive instead of ondemand. Ondemand was designed for desktops and laptops; interactive was made by Google specifically for Android.

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
[MENTION=4932679]decimalman[/MENTION] did you get my PM?

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
Devs don't usually read PMS very quickly..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
I know.

[font="Fira Sans,Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Oops, I forgot all about it. It's been a chaotic week. I'll take a look sometime this weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I still play with this phone. I got this message here,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
You need to flash the one from the first link.

That is if you want to undervolt, and it requires a specific file name.

And BTW, I still use this phone as my daily driver. [emoji14]

Long live the S3!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I have an on5, so you got the better deal!

Carriers , you know how it goes.

Wow, you know, i lectured a dude aboit reading before acting not 30 min ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Hey, I also want to let you know that, looking at the screenshot, you are running an old TWRP. You can probably update TWRP to 3.0.2-0. It is a huge update, and it has a new look, a real terminal, and some other good improvements.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Nice recovery. Thanks for the info!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
All I can think of is a mean recovery. A.K.A. Android System Recovery <3e>, or more commonly known as Stock Recovery.

The 3e stands for 3 errors:

[FONT="Droid Sans Mono,Roboto Mono,Consolas,monospace"]E:failed to verify whole-file signature

E:signature verification failed

Installation aborted.[/FONT]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ssurell:
wifi issue Carbon 4.4.4

Resurrected good old CARBON-KK-NIGHTLY-20140707-1036-d2lte for shear performance and utility, but having a hard time finding a custom kernel that doesn't kill wifi or display. Any particular version or suggestions appreciated.;)

Here's the complete ROM and backup of working boot partition:

https://drive.google.com/open?id=0Byr3wbxh35NbWkNJdHRvZVRHQUU

Updated to CARBON-KK-UNOFFICIAL-20150712-1319-d2lte and works flawlessly with dkp-aosp44-d2-20160805 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Dude[tte], that's OLD. You probably shouldn't be using it.

You have to make decisions.

Older ROMs:

+ May be more stable

+ Often have better performance

– Have (sometimes serious) security holes.

– You miss out on latest features

– Sometimes have more bugs that will never be fixed

– Nowhere to go for support

Newer ROMs:

+ Guaranteed compatibility

+ Latest security patches

+ Latest features

+ Most bugs are temporary

+ Active support threads

– May have performance/battery issues