yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ssurell:
I hear this often (mostly Mozilla forums), but there are obviously 2 divergent schools of thought in regards to operating systems.

- The security holes are greatly exaggerated and can be patched with xposed module.

- Along with the 'latest features' gimmick to get you to use a ROM with less versatility or options for the power user/tweaker/modder. If it's a feature worth using, it's already been implemented in a custom ROM (On-The-Go Mode) or xposed module, with the exception of screen pinning.

- Every ROM has bugs that never get fixed while developers move to the next new thing. Version after version, it never ends.

- Carbon was one of the fastest, most stable ROMs built during the 'golden/AOKP era' of Android developement. I have it on an L5 and now the SIII, everything is working. Every custom ROM has minor bugs that can usually be worked out by modifying the system, no need to harass developers if you know what you're doing. But this is less possible with every new version of Android.

- The thing I hated about Android 5.1 was that it was less compatible with pretty much everything I do. Xposed is finally getting some modules for it, though nothing epic.

I just flashed a modified stock ICS ROM on an HTC 3D that simply blew my mind. The UI was nearly indistinguishable from KK with all the eye candy, and every app I use was compatible. If I wanted Terminal to be a system app, bam. New app, old app, did not matter; I could integrate into the system.

The trend that I've seen is in limiting control and access in every new version of Android. From practical dark themes to white menus and backgrounds, popping colors using enough power to fry en egg on your AMOLED. Nevermind the diminutive 3 hardware buttons, we're going to have an extra large banner with nothing more than a 3-dot icon, and a navigation bar. So, it uses 25% of the screen realestate but at least it's more like an iPhone. Maybe add sophisticated gestures and all kinds of UI layers so you'd need to be sitting stationary, at a desk, with the device properly docked, without too much glare, and have a quality scribe to not fat-finger some undesired task.

Android was standardized with the most efficient mobile experience before the Apple lawsuit, there have been relative minor improvements since then with a lot more foolish gimmicks for the sake of sales hype.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
I totally get your point.

There are dark themes, you know. Check out "Dark Regression " with the Arcus alternative black theme.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ssurell:
I actually love the the look of the Material design and ability to theme is more stable. But for me, utility comes before style.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Use whatever you want. Thats ehat this whole community is about. If you wanna use Doghnut, then by all means, use the most modded to your perfection doghnut you want! Whatever you like is personal to you, thats one of the reasoms none of us are on iphones today. Rock on. I dont like selinux one bit. And everytime you get an update something super convienient and usefull dies off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ssurell:
Best ROM/kernel for this device for speed, stability, customization IMO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unimatrix725:
First Off Thanks!

I have a couple ?'s please. It may be buried, but cannot find answers.

1. What is the difference in 4.4 and 4.4 Legacy Kernels?

2. What is Error Status 255?

This does not happen with normal 4.4 (always used) from 12-2015 or even the legacy version. I wanted to use/try newest kernel before re-flashing a rom.

PS: Could you put answers in 1st page for reference? I downloaded on computer and mobile and both have the same md5sum, but IDK if original w/ server?

I noticed update-binary is ~37K in 2016 zip and 90K in 2015. If it matters, assumed it was optimization form a newer gcc?

LastLog

-- Installing: /storage/sdcard1/CWM/CMX-12_Kernels/DKP_Kernels/dkp-aosp44-d2-20160805.zip

I:skiping set_bootloader_message: no /misc

Finding update package...

I:Update location: /storage/sdcard1/CWM/CMX-12_Kernels/DKP_Kernels/dkp-aosp44-d2-20160805.zip

Opening update package...

Installing update...

E:Can't run /tmp/update_binary (No such file or directory)

E:Error in /storage/sdcard1/CWM/CMX-12_Kernels/DKP_Kernels/dkp-aosp44-d2-20160805.zip

(Status 255)

E:Installation aborted.

press any key to continue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Your post didn't get lost, I'm just not around to answer questions as much as I should be.

1. 4.4 "legacy" builds have a security feature disabled in order to support older 4.4 ROMs. In the 4.4 days, certain carriers weren't well-supported, so only certain (old) ROM builds could be used on obscure carriers; the legacy builds are intended to support those ROMs. If you're using a ROM from 2014 or so (I don't remember the exact date) and regular builds break your GPS, you probably need the legacy builds.

2. The dkp installer won't (intentionally) give an error 255; it's happening when your recovery tries to run the installer. What recovery are you using? To save space, the newest installer relies on the recovery to provide a bunch of code. If your recovery isn't providing everything the installer needs or it's configured slightly differently, it'll break the installer. I've only tested on the latest TWRP, so it's possible that other versions or other recoveries won't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Looks like newer ROMs won't work with the current dkp builds, so it's time for new builds. I haven't changed anything, just synced with CM. Since nothing changed on 5.1 or 4.4, I didn't rebuild them.

Changelog:

Synced with CM.

Built for AOSP 7.0. I haven't actually tested it or anything, but not much has changed in the kernel between 6.0 and 7.0, so I don't expect any problems.

Checksums:

c0cfd71dde752c20d0b7e48e748b76a8 dkp-aosp60-d2-20161013-dkp-3.4_6.0.zip

712abb7f194c38b1c67655b9c99c30ac dkp-aosp70-d2-20161013-dkp-3.4_7.0.zip

Out of curiosity: at the request of a user, I threw together an option to limit the screen's framerate, but I haven't merged it yet. Is anyone interested in this? The requesting user's S3 died recently, but if anyone else is interested in such an option, I can certainly tidy up the code and merge it. The user also put together a fancy app to control the framerate; if I merge the code, I'll try to get the app released publicly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pierre2324:
works with multirom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredy_pirineos:
hi there, good job.

One question, is it possible to enable more LTE Band (3 y 7) with this kernel and rom in a S3 i747 at&t?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New builds are up for AOSP 7.0, 6.0, 5.1, and 4.4. Not much has changed, but I'd strongly recommend updating. All builds incorporate a fix for a major security vulnerability ("Dirty COW").

Changelog:

Updated to Linux 3.4.113

Synced 6.0 and 7.0 with CM

Checksums:

d23ddc003ce67883c36e94ebd0f4f218 dkp-aosp70-d2-20161104-dkp-3.4_7.0.zip

f840e736de3bde47a8e4c8d6a7bffc94 dkp-aosp60-d2-20161104-dkp-3.4_6.0.zip

3b0831a5aa69639fe62f846ac5a1a514 dkp-aosp51-d2-20161104-dkp-3.4_5.1.zip

48ea09bb35e53a73fe3663ae7a082bfb dkp-aosp44-d2-20161104-dkp-3.4_4.4.zip

a06d296fe1a2e7f84f3d6af92f647eea dkp-aosp44-legacy-d2-20161104-dkp-3.4_4.4.zip

I'm not terribly familiar with the modem, but I don't think so. I don't think the kernel has any control over the modem's configuration; it's probably baked into the modem firmware instead.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Thank you!!!

But what is dirty cow??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
http://m.theregister.co.uk/2016/10/21/linux_privilege_escalation_hole/

http://m.theregister.co.uk/2016/11/01/docker_user_havent_patched_dirty_cow_yet_bad_news/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
Is Dirty Cow fixed in a specific version of the Linux kernel because I'm running a custom kernel running Linux 3.4.112?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Linux 3.4.113 includes the fix. CM also merged the fix about 2 weeks ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
Ok. Well if they merged the fix good. But didn't they merge it with their kernel? I'm running a custom kernel that's running 3.4.112 right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Instead of merging Linux 3.4.113, which includes the fix, CM only merged the single commit that fixes the issue. If your kernel synced with CM in the last two weeks, it's not vulnerable, even if it's still on 3.4.112.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
[size=+2]Unofficial Update

Nougat Only

[/size]

Changelog:

* Synced with LineageOS.

* I couldn't get LTO to work. So I used optimizations from my kernel as a replacement.

* Compiled with a cortex-a15 optimized Uber 7.x toolchain.

* Beautified Dkp name in kernel lol.

* Other than that, source is completely untouched. :good:

* Thanks [MENTION=4932679]decimalman[/MENTION] for letting me post this. :highfive:

So here you go guys. Enjoy! :good:

Download Link
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
After lots of laziness on my part, there's finally a new official build out. Thanks to [MENTION=6249123]Lonelyskatter12[/MENTION] for putting together an update in the meantime. :highfive: I was hoping to get a few more changes merged, but I ran into some stability and battery drain issues. Once I get those issues sorted out, I'll release a bigger update. In the works are improvements to the tiered GPU governor, a complete rewrite of ISAAC, additional optimizations, and a fix for cpufreq_limit.

To simplify things, I'm only building for AOSP 7.1 for now. If anyone needs a build for a previous version, let me know and I'll make it happen.

Changelog:

Synced with LineageOS; disabled cpufreq_limit because it's causing problems.

Switched to a newer compiler and fixed all the new warnings that appeared.

Changed how LTO gets set up, so it should work with an off-the-shelf toolchain. If anyone is interested in playing with the dkp source, this should make it much easier to get started.

Replaced a spinlock optimization that was causing freezes with something less dangerous.

Added a few small optimizations and bugfixes; they shouldn't have any noticeable effect.

Checksums:

71152cf98cfab160d05fb37f73bbd60b dkp-aosp71-d2-20180204-dkp-3.4_7.1.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
https://xdaforums.com/galaxy-s3-att/development/lineage-15-1-build-t3793126 can any one help please????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anderson987:
Hi, i Found some links that have some hotplugs and more cpu governors that I want you add.

https://github.com/Andromax-Devices...0f14eb1a5655b62755a30161aa02f7fe68?diff=split

https://github.com/vaserbanix/kerne...mmit/4d97a17d581ee3809f8de111f549b2ddaa44cce5

https://github.com/JDCTeam/android_kernel_samsung_jf/commit/8fa2ad10cd618904d6cf97d446c8cceb4abb3630

If you want please add some governors to the kernel and some hotplugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Look at the better battery log though. It's not actually turning off. WiFi is still on for much of that time causing wake locks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abulbulia:
Hot plugging does work but what I noticed is that once you go into trickster mod and change governors hot plugging stops. What I did was then in terminal emulator type in su enter stop mpdecision enter start mpdecision enter. That gets hot plugging going again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Ugh. I was hoping mpdecision wouldn't give me anymore problems with that. I'll add some code that should calm mpdecision down. It's usually caused by mpdecision noticing that something else turned core 2 on. A logcat will probably show "CPU[1] has been hotplugged outside of MP-Decision", "MP-Decision will be stalled until enabled".

Good thinking on the fix. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
This is the exact error in catlog. Same thing happens when I try to use terminal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
su
echo 0 >/sys/devices/system/cpu/cpu1/online

Or, grab Kernel Tuner from the market, open the CPU screen, and back out of it. It'll accomplish the same thing without so much typing.

I'll figure out a way to get mpdecision to stop doing this. Or, maybe I'll switch to auto-hotplug instead. We'll see.

Edit: F****** mpdecision. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
That worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Decimal, Gideon got asswax hotplugging and running perfect now. Maybe he can give you insight? Btw your a freakin genius to get asswax working on linux 3.4, so thank you so much for that. It did wonders for me on my battery on linux 3.0. So glad its working now on 3.4. All thanks to you bro. Thank you! Hope you get this headache smashed out. Also I don't think BMS kernel uses mpdecision for hotplugging, I forget what Gideon uses but Im sure he will toss it your way.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks! I know it's a popular governor, so I figured it was worth the effort.

I think dkp is the only kernel that still uses mpdecision. I think everyone else uses Thalamus' auto-hotplug driver. asswax isn't actually the cause of any of the recent problems with hotplugging, it's just that mpdecision doesn't work the way I want it to. :( I'm probably going to switch to auto-hotplug soon, since it'll be less of a headache than mpdecision. There's also some stuff I changed in asswax that probably isn't ideal, so I'm going to continue to work on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drpenguino:
Has anyone managed to get this running on slim bean 4.2? I'm using the newest 3.4 stable version and it fails to get past the boot logo. I had been using slim bean 4 with the compatible 3.0 kernel and was getting extremely good battery life and responsiveness of the device was blistering fast. I realize this may not be a kernel issue but unsure as where to post first. Any help would be great.:o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'll think I know what the issue is. I'm going to grab a copy of d2att Slim and tear it apart. Give me a bit.

Edit: No such luck. I thought blk_jack might be doing something sneaky that dkp wasn't expecting, but it looks like I have some debugging to do. I'll PM you tomorrow to try to get this worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abulbulia:
I'm using this kernel with slim. Working fine for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Here some battery screen shots as I mentioned. The better battery stats is just overnight monitoring but the others 2 are since a full charge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drpenguino:
Newest 4.2 ROM and 3.4 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
No way that's stock battery, is it? Also care to share your kernel settings? I'm wondering what are the idea settings for this Kernel. Seen some impressive standby time using freenlunch and default settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
It's the zero lemon battery. It's only 2300 vs 2100 so it's not that much better. Using nanolunch stock settings and noop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Ryan does that 2300 fit with the stock backing?

Deviance runs in the blood...

BMS fueled.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Sure does. Amazon. You get 2 batteries for $20 and a spare wall charger for the extra battery. Only downside is no nfc but I never used it anyways
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Crazy test builds are going up soon! If you flash, expect bugs and be prepared to flash an old version! I only just got wifi working again (took 3 days to track down the issue :(), and I expect more issues to show up.

Changes:

Link-time optimization! I expect this to cause problems, but I think I've sorted most of the crazy bugs out already.

Fancy new toolchain with the latest Linaro and GCC commits

Linux 3.4.43 and CM's latest commits

A few odd fixes and cleanups

Edit: My build script blew up, so this round of test builds is using the old naming system. Sorry for the inconvenience.

Edit 2: Fixed my build script and rebuilt using the right toolchain. New builds are up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Latest test build working great with task 5/2 build running nanolunch/sio.

Thanks dm!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Good stuff. :good: Only one user has found any crazy bugs, and they're not even the catch-your-phone-on-fire kind of crazy. I expected much worse.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Faux Sound change

I noticed a post on KT forum that new version of Faux Sound is out and requires new commit in kernel to use added feature -- headphone power amp control. All other features in new version still work with older kernel code. Just passing along link to new commit:

https://github.com/faux123/htc-m7/commit/acff15670bae39452662c641f46cd65ab670b927
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Merging now. I have some other in-progress stuff that needs to be tested, but I'll get a build out this weekend.

Edit: d2 has different offsets than the m7. That commit is unlikely to work for us. I can partially apply it and hope it gets the app working again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Just posted by ktsoonsez:

Even though its the wrong phone, I merged it (just need someone to test) since it looks like he just added a few tweak files to sysfs for the most part.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I just looked into the WCD9310 source, and there's controls that look correct at the new offsets, so it could very well work. :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Okay, let's give faux's commit a try. New builds are going up now.

The builds also include a new toy I threw together earlier this evening. I'm calling it "auto-auto-hotplug." If you have mpdecision running, it'll let mpdecision do its thing. If you disable mpdecision (or are running task's AOKP), auto-hotplug takes over. If you set Trickster to apply at boot, it should work perfectly, but if you decide to switch later you'll need to change governors before everything will get sorted out. I've only given this 5 minutes of testing, so let me know if it gives you trouble.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Faux sound working. Asswax is auto hot plugging on task 5/2!!!

Thanks dm!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
FTFY

Told you I'd get to it. I just get distracted easily. :o

Auto-hotplug's settings are tuneable and show up with governor settings whenever you're using a governor that doesn't hotplug. The defaults look fairly reasonable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Hey Decimalman,

Been running the latest test. Works well. Is there a specific day you release new ones so I can be sure to check out the thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I release test builds whenever I get an interesting feature working. There's no telling when that will happen though, since my work (and non-work) schedule is pretty erratic. Generally I bump my threads with a brief description of what's new, so there's no need to compulsively check for new downloads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New test builds will be going up shortly. I haven't had much time for dev work (IRL stuff :(), so not a lot has changed. There's a few bugfixes and the latest CM commits, but not much else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Dkp, as in, Dragon Killing Points? Lolol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Nerd. :p:p:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Kernel working solid with Task 5/17 & Liquid 2.4. Thanks dm!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New stable 3.4 builds! It's been way too long since the last stable builds. There's not a lot of dramatic changes since I've been busy IRL and have been working on a TW port of dkp.

Changes since the last stable:

Bugfixes: better overclocking support, better hwrng support, etc.

Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface (Settings->Advanced->Screen color temperature)

Automatic auto-hotplug. If your ROM doesn't have mpdecision or you've disabled it, auto-hotplug will take over. Settings for auto-hotplug can be changed in the governor settings menu of tuner apps.

New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain

Edit: New builds pulled until I get data sorted out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Awesome! I am sure you'll get sorted soon!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Let's try this again. I just fixed the issue that's causing broken data, so I'm going to upload test builds.

I'm going to bed. Hopefully I'm not just exhausted and hallucinating the 3G indicator. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I have been looking forward to this update and it's running great for me on LiquidSmooth 2.5. I think Freelunch is my new favorite governor. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Dev-host is down, and it looks like they might be down for a while. They haven't even posted an update on Twitter about whatever is going on. A temporary MediaFire mirror has the newest test builds.

Edit: By the time I realized that XDA rejected this post, dev-host was partially back up anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhanamjay:
freelunch governor broken?

This kernel was very good with battery life than latest LK that I have been using for a while. However I switched to "freelunch" and rebooted it, I could not boot this kernel any more. I flashed LK and back to this, but still not booting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Governors don't get applied until fairly late in the boot process, so freelunch shouldn't have anything to do with what you're seeing.

Are you running the latest dkp test build? Is your phone freezing at the splash screen (the "Galaxy S III" one, not the "Samsung" one)? If so, it's an issue I'm working on. It can usually be solved with a battery pull and possibly a hold-power-for-10-seconds reboot or two (obviously not a permanent fix, but if you rarely reboot your phone it's tolerable). If not, please send me some details. If there's another issue I don't know about, I'd like to get it fixed. :good: