yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] decimalman:
Super-duper experimental builds for TW 4.3 are going up. I haven't run into any issues yet, but I've only got everything building an hour ago. Feedback is greatly appreciated, especially since it's Thanksgiving and everyone has more important things to do. :p
[Sprint Samsung Galaxy S III] rompnit:
Loved your kernel on MD4! Question.. is your 4.3 TW test Knox free? Thanks for everything that you do!
[Sprint Samsung Galaxy S III] decimalman:
The scary parts of KNOX are in the new firmware, and it probably won't be safe to flash it anytime soon (if ever). The kernel has some new code that interacts with KNOX, but I'm pretty sure I disabled it all. The new kernel code is responsible for crippling a few things (e.g. WiFi), but it's not the bricks-your-phone, voids-your-warranty, kicks-your-dog part of KNOX.

I also accidentally disabled SELinux. If you were running in permissive mode anyway, it shouldn't make much difference. As long as it doesn't cause any issues, I'll probably turn it back on eventually.
[Sprint Samsung Galaxy S III] CNexus:
Not sure if you found it or not, but check my commit here for enabling exfat, otherwise it gets left out of the build because Samsung is a huge troll

https://github.com/cnexus/kernel_tw_43/commit/75f9e924c28a9d88cfe9b9c9b477c0c68621a87a
[Sprint Samsung Galaxy S III] tlrsax54:
Running the new 4.3 TW...free lunch lagged a little during one of my games so I am just leaving it set to On Demand...no issues here :)
[Sprint Samsung Galaxy S III] decimalman:
Another round of TW 4.3 test builds is on its way. There's a lot of bugs fixed, and I'd recommend everyone update. I enabled SELinux, but I'm open to the idea of disabling it again since it can be troublesome. If you flash over a kernel that boots in permissive mode, it'll carry over.

Changelog:

Re-enabled SELinux

Fixed frequencies not changing correctly

Fixed several bugs in the thermal throttling code

Fixed a few shortcomings in the hotplug management code

Fixed CPU initialization code not using the correct frequency

In the near future, I'll port most of these fixes to the 4.1kernel as well.
[Sprint Samsung Galaxy S III] kaos420:
[MENTION=4932679]decimalman[/MENTION] I'm on CNexus 4.3 odex rom i flashed his wifi fix kernel and your permissive ramddisk you had posted in that thread awhile ago. thats all. today i flashed the - 12.01kernel I can't get frequently to stick keeps dropping back to 1512" using trickster mod
[Sprint Samsung Galaxy S III] kaos420:
kinda at a loss. i made sure to rename

gsiff_daemon --> gsiff_daemon.bak

mpdecision --> mpdecison.bak

smd --> smd.bak

smdexe --> smdexe.bak

all in stock 4.3 bin folder.

even have system/etc/init.D all renames to bak

still cant get settings to stick.
[Sprint Samsung Galaxy S III] kaos420:
OK so I switched from trickster to Android tuner settings seem to be sticking now finally. Over all I'm impressed running great. I know score. Mean nothing but I've never gotten over 7000 since owning my phone or O.cing in the past.
[Sprint Samsung Galaxy S III] decimalman:
TL;DR: There's a new TW 4.3 build up and I'm disabling SELinux.

A few people found that after flashing the 12/1 TW 4.3 build, lots of apps disappeared. I did some experimenting, and discovered that if you have been running with SELinux disabled (permissive mode may even be enough to cause problems), switching to enforcing mode is likely to cause apps to disappear and/or crash. I think I know what's going on, but even if I'm right, it's going to take a few days to put together a fix.

All it takes to convince SELinux to eat your apps is a trivial change in the ramdisk, which means than changing kernels or even ROM versions could cause problems. This is a no-win situation for me: keeping SELinux enabled means that switching to dkp might hide your apps; disabling it means that switching back to another kernel could hide them. For the time being, I've reluctantly decided to disable SELinux. In the future, one of three things will happen:

Someone will put together a flashable fix for apps disappearing and I'll embed it in the dkp zip

I'll bundle dkp with a custom ramdisk (I really don't want to do this), forcing SELinux into permissive mode

Virtually all ROMs will switch to permissive SELinux, making it safe to enable it in dkp

Questions, comments, concerns? Fire away.

With all that out of the way, there's a new TW 4.3 build up. I fixed a bunch of bugs, and this build is noticeably smoother than the previous build.

Changelog:

Disabled SELinux

Fixed (I hope) reboots when underclocking

Fixed frequency boosting not working

Fixed a couple new bugs in the thermal throttling code

Reduced UKSM aggressiveness by default

Disabled some useless or TIMA-related stuff that I missed

EDIT: I think I found a way to fix the missing apps. I'll get a test build together tomorrow.
[Sprint Samsung Galaxy S III] carole6m:
So I flashed this on TW 4.3 d2spr and some motions don't work anymore. Direct call and double tap to scroll to top are the 2 I noticed. Anyway to fix this? Thanks!
[Sprint Samsung Galaxy S III] decimalman:
Strange. I never enable motions, so I hadn't noticed. I'll take a look tomorrow.
[Sprint Samsung Galaxy S III] carole6m:
Thanks! I switched back to the stock based kernel with wifi fix and now both motions work. Will wait for the update if it can be fixed :)
[Sprint Samsung Galaxy S III] decimalman:
New test build for AOSP 4.4 is going up. Feature-wise, it should be identical to AOSP 4.3, though I did throw in a couple tweaks.
[Sprint Samsung Galaxy S III] Mr. Struck:
Very exciting, downloading now and can't wait to try it out! By far the best kernel for 4.3.x, been eager for a 4.4 version. Keep up the great work my man!
[Sprint Samsung Galaxy S III] Keldig:
phone reboots when i drive in this one area (everytime)

I have this weird issue, when ever I drive in this one area my phone reboots. It's drving me crazy. I'm on Sprint and I know they are upgrading there towers but wanted to know if anyone else has this issue and if i just need to update my radio or something? Im currently on dkp-tw41-2013-11-21-testing

Thanks!
[Sprint Samsung Galaxy S III] Mr. Struck:
So paired the newest 4.4 test build of dkp with the 11/28 unofficial CM 11 on my phone last night right after this newest dkp was released. Undervolted to my normal amounts (-75 across the board) with freelunch and zen. When I plugged in USB connection to my computer, phone was not recognized. Went into Trickster Mod and toggled Fast Charge on and off, no luck. Then, next time I needed to reboot after doing some things in recovery, boot would hang about 5-10 seconds in. Restored my most recent backup with stock kernel and everything was back to normal-phone connected to computer via USB just fine, and no boot issues. I assume this was all kernel-related since that was the main change I made right after creating the backup to which I restored. I do realize this is a test build, just wanted to share my initial experience with this latest version. Still the best kernel out there by far!
[Sprint Samsung Galaxy S III] decimalman:
Thanks for reporting this. It could very well be kernel-related.

I didn't really get a chance to look through all the changes in 4.4, so it wouldn't surprise me that there's some new bugs. Unfortunately, 4.4 is currently at the bottom of my to-do list, behind getting TW 4.3 working better and updating the AOSP 4.3 and TW 4.1 builds. Once there's an official CM11 out, 4.4 will be top priority.
[Sprint Samsung Galaxy S III] Mr. Struck:
No problem, definitely take your time. I certainly appreciate what devs like you do, I have zero knowledge to do the work you do, just appreciate the results. This will always be my kernel of choice, stable build for 4.3 AOSP has been awesome for me on Carbon ROM so far! Excited for official CM 11 for sure since development should explode once that happens. Thanks again.
[Sprint Samsung Galaxy S III] decimalman:
It's time for another TW 4.3 test build. There aren't many dramatic changes, but I did fix a few bugs. Probably the biggest change is a fix for the disappearing apps phenomenon, which means that it's safe to turn SELinux back on.

Changelog:

Fixed the disappearing apps bug

Enabled SELinux again

Added several TCP congestion control algorithms

Fixed a silly mistake that broke several motions

Cleaned some code up, removed a few useless drivers

Compiled with a shiny new toolchain
[Sprint Samsung Galaxy S III] kaos420:
cool dling now. will report back at end of day. ive only had one reboot ever so far on any of the kernels. but that was my fault from pushing o.c up to high.
[Sprint Samsung Galaxy S III] bog3nator:
New dkp loaded fine. No missing apps to report
[Sprint Samsung Galaxy S III] duce415:
I'm on the 11/28 build of this kernel using static v2. Things are working great for me but was wonder if I should update to the newer kernel? Is there a big difference between the 2?
[Sprint Samsung Galaxy S III] bog3nator:
12/5 works perfect on v2. That's what I am using
[Sprint Samsung Galaxy S III] kaos420:
So far so good smooth as glass all day.
[Sprint Samsung Galaxy S III] Domminater:
I can't download, DevHost gives me an error. :/
[Sprint Samsung Galaxy S III] enzoevo:
Does this kernel enable non samsung boot animations?
[Sprint Samsung Galaxy S III] meyerweb:
I'm using a non-stock boot animation, so I would say yes.
[Sprint Samsung Galaxy S III] enzoevo:
bootanimation.zip not working for me. Want to confirm the kernel supports it.
[Sprint Samsung Galaxy S III] decimalman:
Boot animation support requires a modified ramdisk. I don't include a ramdisk with dkp, so you'll need to flash a modified ramdisk to get it working.

EDIT: Tapatalk apparently doesn't like links. Custom ramdisk at http://d-h.st/BRp
[Sprint Samsung Galaxy S III] enzoevo:
Thank you for the clarification.
[Sprint Samsung Galaxy S III] nick benedetto:
WARNING: TW 4.3 is not stable at all. Wait for dev to update it so it won't crash every 5-10 minutes. Great start though dev.
[Sprint Samsung Galaxy S III] decimalman:
Currently, there are a few known issues that affect all custom kernels for TW 4.3. Aside from those issues, I'm not aware of any major issues like you're describing.

If you're not going to provide any information whatsoever to help me track down the issue that you're having, please keep your FUD out of my thread.
[Sprint Samsung Galaxy S III] noles4life50:
I ran it for awhile and had no problems with it at all... Must be user error
[Sprint Samsung Galaxy S III] MikeWjF:
Not one problem here running TW 4.3 with this kernel.
[Sprint Samsung Galaxy S III] enzoevo:
Running for two days now. Undervolted by 75mv. Rock solid, smooth. Love it.

Only instability I had was introduced when I flashed the ramdisk to enable custom boot animations. Massive FCs and general wonkiness ensued. Nandroid recovered and all is good again.

I may try the ramdisk again when I get some time.
[Sprint Samsung Galaxy S III] tlrsax54:
Ran the latest update yesterday, still haven't seen an issue. Switched governor to free lunch for today I'll see how it goes :) haven't UV/oc yet
[Sprint Samsung Galaxy S III] bog3nator:
Been running dkp since tw 4.3 came out. Can't get better battery life or be more stable. Great kernel man
[Sprint Samsung Galaxy S III] koop1955:
Add my voice to the chorus of those not having any issues.

"Not stable at all" seems rather pointless to post without any support. Like what ROM are you running, are OC or UV, any other factors.
[Sprint Samsung Galaxy S III] TheBritton:
I am on Virgin Mobile Galaxy S3 build MK5 (4.3) with the Knox bootloader.

Is it safe to assume custom kernels are safe with the Knox bootloader? I am new to the Knox stuff and I'm not sure how it reacts to custom kernels. I would just hate to end up with a brick so just checking to see what the general consensus was here first.
[Sprint Samsung Galaxy S III] bog3nator:
Last thing I read was no custom recoveries with the new bootloader work. Which means no flashing. I could be wrong though
[Sprint Samsung Galaxy S III] TheBritton:
Well right now I'm using a custom recovery and I used the custom recovery to flash SuperSU.. all while having the Knox bootloader. It just tripped the Knox counter. When the Knox bootloader trips it just disables the Knox security apps. And from my understanding once you have the Knox bootloader you can't downgrade to a non knox bootloader.

Don't want to take this thread in a knox direction but I was just curious if anyone who has the Knox bootloader have flashed this kernel. I'm just double checking that it is safe.
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
Been working great on TW 4.3 the last couple of days, too.
[Sprint Samsung Galaxy S III] Mr. Struck:
Close but not quite; as Britton mentioned, it is a matter of whether or not you care about tripping the Knox flag. Also as Britton mentioned, Knox only truly cares about an attempt to replace it with a previous bootloader, at which point you will get a paperweight that even a JTAG cannot repair (i.e. DO NOT push a stock .tar file via Odin if it contains an old bootloader, as in pre-Knox). My current understanding is that Knox looks for kernel modifications in order to determine whether or not to trip the flag from 0x0 to 0x1, so flashing a custom kernel *should* be the same difference as flashing a custom ROM-Knox will trip to 0x1, but nothing more.
[Sprint Samsung Galaxy S III] TheBritton:
Thank you very much. You just confirmed my thoughts on this.

Lastly, I am looking into downgrading from 4.3 to 4.2 via flashable zip. I assume that would generally be safe as well?

Thanks again. As you mentioned, I do not care about tripping knox because I do not have a need for the security feature although I do see it's purpose. But I do care about making knox unhappy and unleashing its wrath ;)
[Sprint Samsung Galaxy S III] Mr. Struck:
Flash (and that is the key, as opposed to push via Odin) any ROM you want-4.1.2, 4.2.2, 4.3.x, or 4.4.x, there should be no bootloader issues involved. The danger, and then the wrath, involves trying to change the entire firmware.

P.S. you know me as struckn over on Android Forums FYI
[Sprint Samsung Galaxy S III] TheBritton:
Ah! Of course!
[Sprint Samsung Galaxy S III] jtheis23:
Just want to say thanks again the 12/7 tw kernel is running great still
[Sprint Samsung Galaxy S III] MikeWjF:
Where is that?
[Sprint Samsung Galaxy S III] jtheis23:
http://xdaforums.com/showthread.php?p=48226744
[Sprint Samsung Galaxy S III] MikeWjF:
That's the ROM, I was asking about the 12-7 kernel.
[Sprint Samsung Galaxy S III] jtheis23:
If you can't figure it out that's just to bad
[Sprint Samsung Galaxy S III] MikeWjF:
Got it.
[Sprint Samsung Galaxy S III] MikeWjF:
I went back to 12-5, I was having some graphical problems and random freeze ups with 12-7.
[Sprint Samsung Galaxy S III] kaos420:
really thats strange. considering the 12-7 you tried is exactly the same as 12-5 kernel. only difference is some call tweaks. which has nothing to do with graphical.

see post 788 where i asked the dev specifically if there was any major changes. with that said i havent a single issue on this kernel. running at 1782mhz smooth as butter.

http://xdaforums.com/showpost.php?p=48268646&postcount=788
[Sprint Samsung Galaxy S III] marcran75:
I know that Virgin Mobile S3's can run Sprint ROM's. Is this kernel also compatible with MK5 build?
[Sprint Samsung Galaxy S III] kaos420:
well if its running a sprint rom you would be running mk3. i believe this is built of samsung 4.3 source. you could always nandroid then test it out. if it doesnt boot then restore your nandroid.
[Sprint Samsung Galaxy S III] MikeWjF:
Are people doing anything with the DCP Congestion control? I notice a lot more options than I'm used to seeing.
[Sprint Samsung Galaxy S III] kaos420:
i suggest you re read my comment there was no sarcasm involved. you asked a question i gave you a solution to test.this is after all the sprint forum. so i suggest you tone it down alittle bit. not everyone is out to be confrontational.
[Sprint Samsung Galaxy S III] decimalman:
That sounds like a voltage problem, but if that were the case, you'd see it on 12/5 as well. :confused: As kaos420 mentioned, the 12/7 build doesn't have any changes that would cause either issue.

From what I can tell from the source, kernels for d2spr and d2vmu are essentially identical, and dkp should therefore be 100% compatible.

I've been getting PMs asking about this a lot since 4.3 came out. Unless someone reports that they're incompatible, I'll probably change the "d2spr" in my downloads to "d2spr-d2vmu" to make things clearer.

The default setting works well (it's used on probably 99.9% of all Linux systems) and there's no compelling reason to change it. On the other hand, there's no compelling reason not to. :D IIRC westwood performs nicely on 3G, and should do well on LTE as well. You'd be hard-pressed to notice the difference though; congestion control mostly affects upload speeds, not download speeds.
[Sprint Samsung Galaxy S III] Mr. Struck:
ROM and modem are independent, so actually no, running any custom Sprint rom leaves whatever modem is currently on the phone intact. Ditto for bootloaders. Virgin and Boost are just able to use custom Sprint ROM's by modifying the assert lines, flashing these ROM's has no effect on the modem or bootloader. My current setup is MG2 bootloaders and MK5 modem, and I pretty much only run Sprint ROM's, currently first official CM 11 nightly.

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

Been using dkp for several months on a Virgin Mobile SGS3 (mainly Carbon 4.3.1), and works flawlessly. 100% compatible.
[Sprint Samsung Galaxy S III] marcran75:
I know this is off topic but you say you only run Sprint ROMs. Have you been able to get MMS to work? I've searched and searched and haven't been able to find a fix for my MMS not working.I'm running MK3 everything. If I flash MK5 modem would this help?
[Sprint Samsung Galaxy S III] TheBritton:
Mr. Struck has a how-to guide for modifying Sprint roms for Virgin Mobile. It might be better to ask him this question over there:

http://androidforums.com/showthread.php?t=791952
[Sprint Samsung Galaxy S III] noles4life50:
After a few fill battery cycles this is the battery life I'm getting with this kernel! I can easily push 24 hours with 4 to 5 his screen on with this! 4.3 tw is much better on battery for me than 4.1.2 was (and I was getting pretty decent life with that also) no renaming of any files like we did on 4.1.2 and this is with no extra tweaks, not UV or anything everything is left alone after flashing the kernel... Everything default settings standby dropped only 3 percent over night and screen on is amazing also [MENTION=4932679]decimalman[/MENTION] you're off to a great start on this kernel man, keep up the great work
[Sprint Samsung Galaxy S III] Mr. Struck:
Feel free to PM me here on XDA or over at Android Forums, or check out the link to my tutorial that Britton provided in this thread.
[Sprint Samsung Galaxy S III] meyerweb:
Geez, I don't get anywhere clo0se to that. Are you using the stock battery? What sorts of things do you use your phone for? Can you post the main battery screen?
[Sprint Samsung Galaxy S III] noles4life50:
On this run Facebook, tapatalk, browser, and hangouts mostly... And yes, stock battery that came with the phone
[Sprint Samsung Galaxy S III] tlrsax54:
Ever since I dropped my phone and had to get a refurb the battery has sucked...I get maybe 1.5 hrs screen time on stock kernel and a bit over 2 with dkp...I'm slightly jealous haha
[Sprint Samsung Galaxy S III] decimalman:
There's a new TW 4.3 test build up. It fixes voice on d2spr for anyone who hasn't found the 12/7 build yet. It also fixes a bug that could potentially crash the display hardware, probably taking everything else with it (thanks, Samsung).

Changelog:

Built d2spr with the correct voice processing firmware, fixing voice volume, dialer lag, and any number of other bad things

Turned compiler warnings back on (Samsung disabled them :mad:), and fixed the zillions of issues that the compiler warnings were designed to highlight in the first place

Fixed a major bug in the framebuffer driver

Major cleanups to the rotator driver (the name is misleading; it's mostly used for video playback)

Renamed a few devices to hint at what devices they're compatible with

Tidied up a bit, removed a couple unused modules, switched to (smaller, faster) XZ compression
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
I've been using 12-5 all day today but then tonight the display wouldn't turn off at all. Everything else was ok. Is this what you mention here about the display crashing? I'm flashing your new test build now. Hopefully this is the one. :good:
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
Wow, I was checking the thread at the right time! ;) THANKS!
[Sprint Samsung Galaxy S III] kaos420:
Seems the dl location is all messed up
[Sprint Samsung Galaxy S III] B5Z:
Thanks a lot for this!!! I was having issues with making & receiving calls with the people on the other end not being able to hear me. I posted this issue in another thread and [MENTION=2560614]roirraW "edor" ehT[/MENTION] directed me over here. (Thank you roirraW "edor" ehT)

This solved the issue for me - Great job & thanks again for sharing your work!!!
[Sprint Samsung Galaxy S III] enzoevo:
I thought the framebuffer issue might be related to undervolting. So maybe not? I've updated to 12/9 kernel and will see what happens.

Edit: As soon as I hit post, the phone spontaneously rebooted on me. Resetting voltages to kernel defaults. Hopefully that's the culprit.
[Sprint Samsung Galaxy S III] decimalman:
I guess it's time for Dev-Host's weekly outage. They've been flaky lately. I keep meaning to switch to another host, but everything is either sketchy or doesn't handle automated uploads well.

The new builds are mirrored here.

It's a different issue. As far as I know, the current drivers aren't triggering the framebuffer bug. It's ridiculously easy to trigger it though, so it seemed worthwhile to fix it before it became a problem.
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
You're very welcome, friend. Isn't it amazing what these devs do!? :)
[Sprint Samsung Galaxy S III] marcran75:
I've been running 12/7 with no issues so far. Should I update regularly or just stick with what's currently working?
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
I don't know if this is kernel related or not so if it's not I apologize in advance. Today I've found that when I go from roaming back into a 4G area, my phone goes to 3g but won't go to 4G unless I reboot. Afterwards it's fine. I'm on the 12-9 release.
[Sprint Samsung Galaxy S III] kaos420:
I had that when I had a bad flash of rom. Tell me when you go to recovery and wipe cache and dalvik when you reboot does phone reboot after optimizing all apps? Before finalizing boot?
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
No. In fact it seems to have corrected itself now. Not sure what was causing it. Heck it could have been just a network issue.

Thanks for the reply!
[Sprint Samsung Galaxy S III] arrogant437:
Mine does this...what's it mean?
[Sprint Samsung Galaxy S III] kaos420:
Bad flash. It shouldn't do that. What you need to do is odin the pit and md4 . after it starts up update profile and prl then go into dl mode odin recovery and upgrade. It shouldn't do this. Mine did that and my wife's. Both times I had issues after redoing pit and md4 boots smooth. You have a bad flash or corrupt partition
[Sprint Samsung Galaxy S III] arrogant437:
So I should revert to the MD4 firmware/modem via odin and then flash an mk3 tar in odin?

I was already planning on refreshing the Deodexed mk3 Rom
[Sprint Samsung Galaxy S III] kaos420:
No don't flash mk3 tar. Do it from recovery with CNexus version.

Pit and mk4 tar and odin are in my files here.

http://www.androidfilehost.com/?a=show&w=files&flid=8857

Any? PM me let's not clog the thread