yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
I'm running S3Rx 1.8, which is 4.1.2. Haven't updated to 4.3 yet.
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
Why Not? 4.3 is awesome.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Yeah, awesome in eating away battery life. It's worse than 4.1.2.
[T-Mobile, Samsung Galaxy SIII] decimalman:
It's been a while, so let's do some new builds for both AOSP 4.4 and TW 4.3. Still no love for TW 4.1 (are enough people using 4.1 to justify continuing support?), and I still haven't fixed up the bluesleep driver that's been causing bogus wakelocks on AOSP (it really needs to be rewritten).

EDIT: Wifi isn't working on the AOSP build.

EDIT 2: Fixed builds are up!

TW Changelog:

Major overhaul to erandom, msm_rng, and all things entropy:

A new entropy daemon, plus a new touchscreen entropy source

Major speedup for erandom

Bugfixes and a major speedup for the hardware random number generator driver

Cleaned up (among other things) erandom initialization

Enabled network block devices

Swapped in a new splash screen

AOSP Changelog:

Synced up with CM, Linux 3.4.82

Major overhaul to erandom, msm_rng, and all things entropy (everything from the TW changelog is included)

Added code to save some entropy across reboots

Enabled network block devices

Swapped in a new splash screen

If you're not sure what network block devices are or why you'd want them, you probably don't have much use for them. I enabled them at the request of Phil_Suz, who's been working on an interesting multiboot system (there should be a thread in the General subforum for your device). NBD support opens up some very interesting possibilities, especially when paired with multiboot.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
4.1.2 is still my go-to nandroid ROM due to battery life and it runs with virtually no lag with your kernel, Interactive+ROW, and running the Lagfix app (TRIM) from time to time. I mean, I don't blame you if you want to discontinue 4.1 support, but just letting you know since you asked, lol.
[T-Mobile, Samsung Galaxy SIII] kingston73:
I just want to double check before downloading, the 2/26 AOSP kernel is the fixed kernel and wifi works, right?
[T-Mobile, Samsung Galaxy SIII] decimalman:
I haven't heard many other people mention 4.1 lately, but it shouldn't take a lot of extra work to keep it updated. Later today, I'll merge in the last couple months of changes and get a new build out.

It's fixed.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
Same here. Haven't jumped to 4.3 yet. And I agree 100% with the battery comment. DKP added 30% or more to my screen time so I'm a fan.

I generally think most of the great battery comments in all the ROM threads are placebo effects, but I've gone back and forth several time between DKP and the stock kernel and it's fairly repeatable. DKP gets me more screen time.

With that said, I have to admit I've been fighting the urge to move to 4.3 just because.

I'm also thinking of upgrading my Commodore 64 at home to something a little newer...
[T-Mobile, Samsung Galaxy SIII] tdotdot:
I don't know about stock kernel, but with DKP and ktoonsez' kernel, I get the same if not better battery with 4.3. Greenify was a big help.
[T-Mobile, Samsung Galaxy SIII] popimp315:
Dunno what it is but the kernel has my phone heating up quickly. Undervolted with lowest 750 and under clocked at 108-1134....confusing
[T-Mobile, Samsung Galaxy SIII] chui84:
hmm i am on Dandroid and the same thing happned on the 20140216 build as well
[T-Mobile, Samsung Galaxy SIII] decimalman:
Long-overdue updates for both AOSP 4.4 and TW 4.3 are up.

AOSP Changelog:

Merged CM's latest changes

Added the ability to keep the existing splash screen*

Changed the power save performance profile to use freelunch and simple CPU and GPU governors

TW Changelog:

Fixed fast charge for MHL cables

Added the ability to keep the existing splash screen*

Added init.d support for ROMs that don't already support it

* In internal storage, create a directory named "dkp", then create a file named "skipsplash" in the new directory. Eventually, I'll make the process easier.

Strange. Is there an app going crazy and using 100% CPU or anything?
[T-Mobile, Samsung Galaxy SIII] barmanham:
Anyone else having incall sound issues with this kernel some calls just sound bad
[T-Mobile, Samsung Galaxy SIII] decimalman:
Are you running TouchWiz 4.3? In order to fix Sprint's call issues on 4.3 (the dialer was crashing the hardware :mad:), I had to rewrite one of the drivers. Someone else mentioned a similar issue, but I haven't gotten any debug information to work with.

If you get a chance, can you get me a log from when you're having issues? After a problematic call, open a terminal emulator and enter "su -c dmesg >/sdcard/dmesg.txt" (all one command), and send me the dmesg.txt it creates in internal storage.
[T-Mobile, Samsung Galaxy SIII] barmanham:
I'm running on T-Mobile 4.3 ya next time it happens I'll do it. I tried changing the baseband to see if that'll fix it no luck also installed the ROM I'm using with no sound mods also didn't fix it.Hope it can be fixed because the only kernel right now for 4.3 besides this is ktoonz and that kernel is to laggy

---------- Post added at 04:16 AM ---------- Previous post was at 04:02 AM ----------

I have the file just let me know where to send it.I called an automated msg and it was going nuts thinking I was talking but I wasnt saying anything and no noise anywhere
[T-Mobile, Samsung Galaxy SIII] pgg285:
Is anybody else having trouble flashing the KitKat version on SlimKat? I've tried a couple of times and the flash failed. I don't think it was a corrupt/incomplete download ...
[T-Mobile, Samsung Galaxy SIII] thelazy8:
I'm flashing 3/20 version just fine over slimkat 3.10
[T-Mobile, Samsung Galaxy SIII] pp085ster:
I've given it a few updates to see if it solves the problem but it hasn't so far [MENTION=4932679]decimalman[/MENTION] : with this & other custom kernels I get audio skips and pauses every once in a while, while on stock I dont get these at all. It is highly annoying and destroys the listening experience but i really do like ur kernels so any chance u cld look at that when u have the time? :)
[T-Mobile, Samsung Galaxy SIII] tdotdot:
What's your min freq? Sometimes if it's too low, the music starts skipping. Also try changing your read-ahead to 1024 or higher.
[T-Mobile, Samsung Galaxy SIII] pp085ster:
Thanks for the suggestion but i seriously tried everything I cld to get it to work and those two things were some of the first things I tried. I wldnt have posted otherwise. The problem I think is that I play DJ grade music files from 10-20mb/song and somehow the stock kernel handles that better :(
[T-Mobile, Samsung Galaxy SIII] decimalman:
I think I finally sorted out the installer issues. :fingers-crossed: I fixed half a dozen bugs that were triggered by strangely formatted ramdisks, which (hopefully) means that the installer will work for everyone.

Anyway, there's a new AOSP build up. Mini-changelog:

Linux 3.4.86

Synced with CM

(Hopefully) fixed the installer once and for all
[T-Mobile, Samsung Galaxy SIII] pgg285:
This fixed installation for me, but the undervolt zip still doesn't flash. (I'm on the latest SlimKat and TWRP.)
[T-Mobile, Samsung Galaxy SIII] kingston73:
Should mp decision be on or off if I'm using freelunch kernel?
[T-Mobile, Samsung Galaxy SIII] decimalman:
If you're using Trickster, the "Override Minimum Voltage" setting on the "specific" page does essentially the same thing.

Doesn't matter. dkp automatically freezes mpdecision when it's not needed.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
Hey Decimalman, just wanted to stop in and say hi, the only downfall of the Note3 is there is no kernel that is even comparable to this ? I miss this so damn much I'd buy you a note3 if I had the money. Miss my freelunch...

InfamousRom: Powered by ColonelX
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Was that cancelled? I don't see that on the download website. :confused:
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
Just look in the op under "old downloads"...

You have mistaken your stupidity for my sarcasm...
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Um, yes, a January 26th build which is older than what the post I quoted...hence my quoting.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
That's the last one he built...

Powered by: ColonelX
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
I tried that January build but it locked up on me. I ended up going back to the september build. That one seems to give me best battery and is most stable. Not sure what the differences between that one and the December build are other than the led but I feel like september works better for me. I miss the led fading in/out though.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
The newer one may be based on newer firmware/base... also, seeing as most Have updated since then, there aren't many new add in since then...

Powered by: ColonelX
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Um, yes. Did you read what I quoted and the date of his post?

I faced some graphical issues from time to time along with strange locks. I had to go back to 11/21 (I think that's the date) build. So by his post I was expecting a newer build.

That's up to him. Hence why I quoted him, to hopefully know what happened to that upcoming build.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
Look man, Decimal has been mia for a bit, (hoping everything is alright) I'm sure you noticed... I'm just trying to help you out with what I know, no one else is answering questions, so no need to be an a$$. I don't know what happened to Decimalman, or why the build never got finished, or if he is still even supporting the project. Sorry for trying to help you out chief, have fun on your own, I'm out.

Powered by: ColonelX
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I'm sorry but I disagree with you. I wasn't being an ass. Just being honest since I made a valid post and I'm not demanding anything from the developer, just hopefully waiting for that build he was (I think?) about to make. If I get a reply good, if I don't, good. Peace.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
Sorry, I mistook the attitude of the post... I used to use this kernel on my s3, it's by was by far the best one I had used up until I bought my Note3, and I still miss the performance of it... have you considered upgrading the phone to use newer firmware and kernels?

Powered by: ColonelX
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Yes, but I always fall back to my stable 4.1.2 custom-made ROM. Been facing random reboots or other kinda minor issues in AOSP ROMs, so I'm giving an extra month of time to developers to see if the ROM gets more stable hopefully. I know these things can take long months to stabilize. The ROMs on my past Samsung Vibrant took long too. I too have tested 4.3 TW firmwares, only to find out they're battery hogs, and I even use Greenify and am conscious of which CPU governors I use, and my phone cannot handle undervolting well unlike my old Vibrant. So until KitKat gets rock solid (100% not 98% or less)...I still have that trusty old but very fast and functional for what it is 4.1.2 TW ROM.

Edit: About firmware, I'm using the latest NC2 bootloaders.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
The best set up I had was the pure aokp rom and his kk kernel, was averaging around 18 hrs, with 6 screen a charge. But I keep sync and location off unless needed, greenify, lux, deep sleep, and cpu sleeper... I always used freelunch, and deadline.

something a little Tweaked; Powered by ColonelX

---------- Post added at 08:38 PM ---------- Previous post was at 08:21 PM ----------

And honestly, if you are running the newest firmware and bootloader, that may cause problems too. I can't say for sure or test, as I no longer have the phone.

something a little Tweaked; Powered by ColonelX
[T-Mobile, Samsung Galaxy SIII] decimalman:
Not canceled, just heavily delayed. I've been dealing with some personal stuff lately, and haven't been able to work on dkp.

I just finished merging everything. Assuming everything everything is working, I'll have a bunch of new builds out later today.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
No worries, XDA can wait, life can't since it's your future. Take your time, and hey, thanks once more for the excellent job!
[T-Mobile, Samsung Galaxy SIII] decimalman:
New builds for AOSP 4.4 and TW 4.1 & 4.3 are on their way up.

AOSP Changelog:

Synced with CM

Added intellidemand and intelliactive governors

Updated to a shiny new toolchain

TW 4.3 Changelog:

Added intellidemand and intelliactive governors

Updated to a shiny new toolchain

I merged everything from TW 4.3 back into 4.1. Off the top of my head, that means:

All of the above

Fixed fast charge on MHL

Overhauled erandom and the hardware RNG driver

Added simple GPU governor

Added sioplus I/O scheduler

Fixed a bunch of small bugs

Switched to the new installer (I don't think previous builds used it?). On TW 4.1, custom splash screens need to be saved to <internal storage>/0/dkp/splash.png.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
New TW 4.1 build has been very smooth for me. It's showing wakelocks like crazy though.

Is it possible something changed in how awake time is reported?

I first noticed the wakelocks with the 12/26 kernel. Flash back to the 9/26 kernel and things look nice again. I'm wondering if the wakelocks have been there the whole time but just not reported on older kernel builds?

My wakelocks that appear are UlrDispatchingService and the Tasker monitor service by the way.

Edit

So it seems like one of my profiles was the culprit of the Tasker wakelock. I have one that changes led color based on battery level while charging. Disabling the profile doesn't change anything. But if I delete the profile the wakelock disappears. Not sure why it behaves differently on this version vs the 9/26 version but it does.
[T-Mobile, Samsung Galaxy SIII] Perseus:
@decimalman, may I suggest including this kernel into the DEV: DB for this device ? Here'a link,.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Tested the new 4.1.2 kernel for several days with the new Intelliactive+SIOPlus. Wow. Never before my phone has had such battery life and performance. Especially considering my battery is 1.7 years old so yeah, I'm supposed to replace it really soon although weirdly I haven't noticed any degradation in its performance. Oh and this newer kernel doesn't show the graphical glitches previous one showed. I'd even dare say it's fitting to be the very last 4.1.x kernel. It's that good. Great job, [MENTION=4932679]decimalman[/MENTION]! :highfive:
[T-Mobile, Samsung Galaxy SIII] decimalman:
New AOSP & TW builds are on their way up.

AOSP Changelog:

Linux 3.4.90, synced with CM

By request, added BFQ v7r3

Replaced erandom with something better :)

Shiny new GCC trunk (it's calling itself 4.10 now) toolchain

I left erandom enabled (/dev/erandom and /dev/frandom), but /dev/urandom, /dev/isaac, and most of the kernel's internal random functions now use ISAAC. Depending on how you measure, ISAAC is 30-1200% faster than erandom ever was. :) The ISAAC source is still pretty rough, but it's been working pretty well for me for a couple days now.

TW 4.3 Changelog:

By request, added BFQ v7r3
[T-Mobile, Samsung Galaxy SIII] Xx_silenzer_xX:
Thanks for the update I love your kernel ♡♡♡
[T-Mobile, Samsung Galaxy SIII] ckisgen:
TW 4.4 kernel please..? [emoji41]
[T-Mobile, Samsung Galaxy SIII] decimalman:
In good time. I'm pretty much starting from scratch on TW4.4, so there's a lot to do before I have anything ready.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New AOSP build is going up! I haven't changed a lot, but I did sync with CM, so this build works with recent (6/1 and onward) ROMs.

Changelog:

Synced up with CM

Linux 3.4.91

Fixed a bunch of compile warnings that were bothering me
[T-Mobile, Samsung Galaxy SIII] SportingChap:
Upgrading from 5-15 kernel, mine never got past the "Galaxy S III" screen. It came up, the LED flashed light blue like normal, but then it never moved on to the ROM boot up animation (C-RoM). It just hung on the bootloader screen, then eventually went all black. Had to hard reboot back into TWRP to flash 5-15 back.

Is this one not backwards compatible with AOSP builds older than 6/1?
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Yes not backwards compatible
[T-Mobile, Samsung Galaxy SIII] SportingChap:
Heh. It's ok, guys! I did the guinea pig testing this time for all of you who didn't know that already. (Like me.) :silly:
[T-Mobile, Samsung Galaxy SIII] decimalman:
It hasn't been mentioned here yet, but the normal download server is acting a bit funny at the moment. I don't have an ETA on a fix, so I'll resurrect the old MediaFire mirror. The last two AOSP builds are available at http://www.mediafire.com/?jlehejjarshqd

I can't mirror TW at the moment, but I'll get to it later today.

EDIT: Forgot I was supposed to upload TW. TW 4.1 & 4.3 are up at https://www.mediafire.com/folder/9nc6cmdzmb8km/dkp
[T-Mobile, Samsung Galaxy SIII] Soul0Reaper:
Just wanna say this is quite a smooth and capable kernel. Love the temperature throttle toggle. Helps so much to disable it when I'm using the phone as a gps.
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's a new AOSP build up on MediaFire. Changelog:

Synced with CM: tons of updates from CAF, also switched to the ND8 (Sprint KitKat) wifi driver

Re-enabled some GPU settings that disappeared a while ago

Rewrote my changes to the wifi driver to support the new code. If anything (wakelocks in particular) misbehaves, let me know.
[T-Mobile, Samsung Galaxy SIII] JustZaphod:
Random reboots with recent 4.4 Kernel

I'm getting random reboots as I flashed (dkp-aosp44-d2-20140705) while using the most Recent PACROM..

I reverted back to the 6-02 Kernel and all is back to normal..
[T-Mobile, Samsung Galaxy SIII] nirogu325:
DKP bug

[MENTION=4932679]decimalman[/MENTION] - I want to report a bug using a last_kmsg but I can't using the following command: "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" it says "No such file or directory" when entering through Terminal Emulator. I'm having a bug on the GS3 T999, Android 4.1.2 with your latest DKP kernel from April. Sometimes the touchscreen will not answer at all. I've changed both governors and schedulers to no avail. Since the touchscreen did not respond, I had to reboot. How can I properly report this to you? Surely a logcat wouldn't work since I had to reboot. This issue happens ocassionally, same with a friend who's using the AT&T variant of this phone with the same kernel version. Anyways, since I couldn't use kmsg, I used dmesg. Here it is, I hope it can be of some use to you.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
That was happening to me too with both the April and January TW 4.1.2 kernels. I'm back on the one from last December now. That one and the September one are most stable for me.

Pretty sure last kmsg doesn't work on the TW kernels.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Hopefully decimal finds something from that log that can help. It is the only issue the kernel has, thankfully it is occasional but sometimes it happens frequently.
[T-Mobile, Samsung Galaxy SIII] JustZaphod:
Thanks so much for the 7-26 update.. It fixed my broken WIFI issues with the latest version of Carbon 7-24 nightly..

I was worried for a bit, thinking I had to swap out for another rom..
[T-Mobile, Samsung Galaxy SIII] decimalman:
Hey! I haven't even announced that build yet! :p

I finally got everything merged and working again (some weird compiler misbehavior was preventing everything from building), and there's a new AOSP build up on MediaFire. Changelog:

Merged everything from CM. This includes changes to the wifi driver that probably won't work on ROMs before 7/23!

Linux 3.4.99 and BFQ v7r5

I though I replied to this, but apparently I never did. Sorry about that.

Unfortunately, TW doesn't have last_kmsg support (it seemed to cause problems for some people, so I removed it). logcat and dmesg are both reset when rebooting, so last_kmsg is really the only way to get debug information after a reboot. That makes it pretty difficult to get debug information when the touchscreen is misbehaving.

Just reporting what's happening is often enough to get a bug fixed. In this case, I have a pretty good guess as to what's causing problems: dkp normally runs the touchscreen way out of spec, and it wouldn't surprise me that some phones don't handle it well. As a test, I put together a build with the default settings. I haven't actually tested it, but it's available on MediaFire. Let me know whether or not it helps.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Huge thanks. I shall test for a month or so and will report back about my phone. Same with my friend's GS3.
[T-Mobile, Samsung Galaxy SIII] JustZaphod:
At about this time of the month, I check your page almost twice daily.. :good: :highfive:
[T-Mobile, Samsung Galaxy SIII] anil2653:
Hi

I flashed 7-26 on my sgh-t999 over beanstalk 4.4.4 but WiFi is not getting on

Any advice
[T-Mobile, Samsung Galaxy SIII] matrixzone:
7/26 kernel is meant for ROM built after 7/26. Beanstalk was built before that and is the reason of broken wifi. Try older build of the kernel or newer rom
[T-Mobile, Samsung Galaxy SIII] nirogu325:
[MENTION=4932679]decimalman[/MENTION] - As promised, a report on the TW 4.1.2 test kernel. Both me and my friend think we finally (after weeks of testing) nailed the issue with the random freezing touchscreen: NoLED. That old app we still used from the Vibrant/Captivate days. I was suspecting it because it interferes with the touchscreen for icon notifications and on top of that we forgot it hasn't been updated for years. Ever since we uninstalled it, no more issues. I may even dare to go back to the normal version. We are both using Intelliactive as the governor. ROW on my T999 as scheduler, and for his AT&T unit, I don't remember. Solid kernel. Once more, thanks a lot! :D
[T-Mobile, Samsung Galaxy SIII] runawaybayeh:
Thankyou decimalman. Im using your kernel with quantum 5.2 and it is working nicely on my SGH-I747M.

Smooth. Thank you.

Any pointers for trickster mod settings for this ?

---------- Post added at 08:51 PM ---------- Previous post was at 08:40 PM ----------

Sheesh, now I read further on your intro page, you have stuff there about trickster, pardon my blindness .
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's a new AOSP build up on both mirrors. Changelog:

Synced with CM, and got Linux 3.4.103 in the process.

Fixed mpdecision detection. It was causing mpdecision and auto-hotplug to continuously fight.

Added a bunch of tiny optimizations that shouldn't have much noticeable effect.

Possibly updated some stuff related to GPU OC? I don't remember what was included in the last build.
[T-Mobile, Samsung Galaxy SIII] rener78:
First of thanks and I don't think it's me, but it says that the file is blocked for violation of the term of use. I'm saying it's not me cause I barely use and or go on mediafire
[T-Mobile, Samsung Galaxy SIII] decimalman:
Strange. I'll look into it when I get the chance. For now, try the other mirror in the OP.
[T-Mobile, Samsung Galaxy SIII] rener78:
I tried a little later and it worked sorry about that.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Apparently, I didn't post this in all my threads. Oops.

The most recent AOSP build has an issue that causes reboots, especially with BT audio. This build should fix the issue for anyone having problems.
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
Nope, same thing happens. Boots fine starts to load, freezes then guess into bootloop.

---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------

Thanks by the way!
[T-Mobile, Samsung Galaxy SIII] decimalman:
That sounds like a different problem than what other people were seeing.

What ROM and version? How far does it boot? Any chance you can get a last_kmsg? I'm not sure about CWM, but I think TWRP's file manager will let you copy /proc/last_kmsg into /sdcard to save it.