yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Xx_silenzer_xX:
Im running it with no problems the 12/1 build :)
[T-Mobile, Samsung Galaxy SIII] if6was9:
I have not had any issues with the 12/1 update (so far).
[T-Mobile, Samsung Galaxy SIII] ckisgen:
it booted for me initially but gave me some strange errors in the notification shade I'd never seen before and was locked up to the point that I had to hard reboot with the hardware power button.

I'm on Doc's 4.3 leak #2.. maybe because it has SELinux removed on the ROM side?

I immediately flashed back to 11/28.
[T-Mobile, Samsung Galaxy SIII] imilleson:
I am rocking 11/28, super stable and I am loving the battery!
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
I don't know if anybody is getting this but when I play Dead Trigger 2 my phone losses FPS... I mean I can walk for like 5 seconds then it will drop down to 1 FPS.... I was using FPS Meter to find what's happening to my FPS...
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] 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.
[T-Mobile, Samsung Galaxy SIII] 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
[T-Mobile, Samsung Galaxy SIII] cashmonkey:
Will this kernel work with CM11 Unofficial 4.4 by jermaine151 (beta7)
[T-Mobile, Samsung Galaxy SIII] :
Does anybody know how we can toggle fast charge on the TW kernel? Thanks.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Probably. Only one way to find out. :p

I've heard that the 4.4 build is a little rough around the edges, but I haven't gotten around to fixing it up yet. TW 4.3 is keeping me busy.

Most kernel tuner apps have the option. I know some people don't like it, but Trickster MOD is my official recommendation. I think there are a few fast charge widgets on the market as well.
[T-Mobile, Samsung Galaxy SIII] ad.hoc:
I've been running the 4.4 kernal for a couple of days and I haven't noticed any issues. Battery life is as great as the 4.3 kernals and my phone never randomly restarts or freezes, but of course, other people could have other experiences.
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Thank you decimal! Running 4.3 kernel on the latest cm10.2 nightly and NO kernel tweaks since installing it
[T-Mobile, Samsung Galaxy SIII] popimp315:
Tw 4.3 here. 2nd core never comes on with 12/05. Having some serious lag here. May need to go back to 11/28 but 11/28 stays locked between lowest and highest. Won't allow me to underclock. I can drop it to 54 but cant drop max to 1134. Its pretty stable though.
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's a new TW 4.3 test build up. It fixes a bug that could potentially crash the display hardware, probably taking everything else with it (thanks, Samsung).

Changelog:

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

EDIT: Dev-Host is pretty flaky at the moment. There's a temporary mirror here.
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
Im running the newest build, every time I play Dead Trigger 2 the game freezes (Not the system, just the game. This also happens to old builds)
[T-Mobile, Samsung Galaxy SIII] decimalman:
Does it work with a stock kernel? I don't have a working one handy to test with (Sprint's is pretty broken unless you're running KNOXed firmware).

I recompiled with a bunch of extra logging enabled, but I still haven't seen anything suspicious happening in the kernel.
[T-Mobile, Samsung Galaxy SIII] imilleson:
That is weird, I have been running the 11/28 build since it came out and its ramping perfectly. What kernel config app are you using ?

Thank you so much bro! I am about to flash this one from 11/28 build. Mad respect
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
Yes it does work with stock kernel sir.
[T-Mobile, Samsung Galaxy SIII] _-..zKiLLA..-_:
Downloading the 4.3 test kernel. Will report back with results

---------- Post added at 10:52 AM ---------- Previous post was at 09:59 AM ----------

What's a good governer to use for best battery life?
[T-Mobile, Samsung Galaxy SIII] :
My favorite governor is "Freelunch" as it shuts down one of the two cores when not in use.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I got DT2 working by re-enabling some debugging bloat. Turning it back on makes the kernel substantially larger and potentially a bit slower, which IMO is unacceptable. Once I track down whatever it is that keeps DT2 from working without the bloat, I'll get it fixed and get a new build out.

EDIT: Something strange is happening. I played a mission or two on a mostly-stock kernel, and after that, it worked on any kernel I threw at it. I cleared its data, and now it won't work on anything except stock. WTF?
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
Thanks man, take your precious time.
[T-Mobile, Samsung Galaxy SIII] _-..zKiLLA..-_:
What kinda app do you use to control your kernel? I usually use setcpu but sometimes i feel like the app itself is using battery and have always wondered if theres a better option
[T-Mobile, Samsung Galaxy SIII] :
I'm currently running LiquidSmooth (AOSP) so I just use the built in Performance tuner. However, if I'm on TW (which I use when I travel since I need wifi calling), I use No Frills CPU.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Good news for anyone running AOSP 4.4: new test builds are going up. I haven't spent much time with the code yet, so there isn't a lot of new stuff. Mostly, I got sidetracked and wrote a new novelty. :D If you hate it, you can disable it in /sys/kernel/dkp.

Changelog:

Synced up with CM

Rolled up a handful of changes from TW

Added a fancy gimmick
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
So I reverted back to the 9/26 TW kernel cause of the lock ups I was having and I just hit 4hrs and 40 minutes of screen time with a stock battery! Excellent work my man.

This is why I haven't upgraded to 4.3 yet. Things are running so smooth now.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Camera froze on newest version
[T-Mobile, Samsung Galaxy SIII] decimalman:
I'd highly recommend giving 4.3 a try. I generally can't handle TW for more than a week at a time, but I (voluntarily) ran 4.3 for three weeks straight.

TW 4.3 has definitely had a rocky start, kernel-wise. I think I've fixed the worst of the new bugs, though there's still a couple that I'm working on. From what I gather, AT&T and TMo have seen the fewest bugs of any carrier (with Sprint getting the most).

Assuming you're talking about last night's AOSP 4.4 build, can you get me a last_kmsg? I haven't had any issues with the camera, so I don't know what the problem could be.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
No the newest slim best build... Maybe that's why. But I'll flash back over the kernel and give you that if you tell me how to.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Assuming your phone reboots after the crash, you can use a file manager to copy /proc/last_kmsg to your internal storage.

In the unlikely event that your phone keeps running after the crash, you can get more complete debug info. Open up a terminal emulator (I think Slim still comes with one) and enter "su -c dmesg >$EXTERNAL_STORAGE/dmesg.txt". It'll ask you for root and then save a log to dmesg.txt in your internal storage (funny that $EXTERNAL_STORAGE points to your internal storage, right? :p).

In either case, the log should be small enough to attach to a post here, or to upload to pastebin. The log won't contain any personal information, so it's safe to post publicly.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
http://pastebin.com/KZdu1cFM hope that's all of it!

---------- Post added at 01:10 PM ---------- Previous post was at 01:06 PM ----------

Also here is another log with a crash using an app called vsco cam https://www.dropbox.com/s/u7mkqrtu5c5p8v0/dmesg.txt
[T-Mobile, Samsung Galaxy SIII] decimalman:
As long as I'm playing with the LEDs instead of doing anything productive, there's a new AOSP 4.4 test build on the way.

The new softkey backlight settings can be changed in /sys/kernel/dkp for now. Eventually, I'll try to get Trickster to show settings for them.

Changelog:

Animated the on/off transition on the softkey backlights. It's glorious. :D

Added customizable brightness for the softkey backlights

Changed how a few things come out of standby

Fixed a few small issues in the graphics drivers
[T-Mobile, Samsung Galaxy SIII] popimp315:
Is anyone else getting lag on the two kernels after 11/28? Seems like the 2nd core never comes on.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
See what the issue is with the cam? I didn't notice the led animation till just a little while ago... Beautiful I must say love that effect!
[T-Mobile, Samsung Galaxy SIII] decimalman:
On TW 4.3 you mean? Sorry, I can't keep all my build dates straight. :o

I've seen a few reports of mpdecision misbehaving lately. I recently changed how it gets set up initially, and it's possible that it's not always starting up correctly. I'm supposed to fix a few related problems, so I'll look into this while I'm at it.

Wait a minute. The LED stuff is only in the 4.4 kernels. I thought Slim was still on 4.3? Or is Sprint's just out of date?

I don't see any obvious "camera driver: I hate you and I'm crashing now" messages in the logs you posted. I'm not entirely sure what's going on, so the best I can offer is wild conjecture. :eek:

It looks like SELinux might be interfering with access to the camera hardware and/or the camera service. That's strange, since 4.3 shouldn't enforce SELinux. :confused: Off the cuff, I'd suggest checking the SELinux status in About Phone (it might cause problems if it's "Enforcing"), or possibly reflashing ROM and kernel to make sure your SELinux policy isn't corrupted or anything.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Slim is now on 4.4 there released it last week
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Should I bother installing dkp on latest cm11 nightly and running it stock? Is it worth installing If I have no need for overclock or undervolt? Thank you!
[T-Mobile, Samsung Galaxy SIII] decimalman:
Ooh. It's available for Sprint too. :D I'll flash it later today and see if I run into any problems.

I tried not to go overboard with the LED effects, but I really like the smooth transitions. The LEDs just switching on and off always seemed out of place on an otherwise slick phone. Turns out that the hardware is perfectly capable of smoothly transitioning the notification LED and fading the softkey LEDs, it's just that nobody wrote the code to do it.

You absolutely should. I might be biased, though. ;)
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Can you elaborate a bit as to the advantages and disadvantages of installing the kernel and running it using the default settings?
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Just a note they just came out with 1.7 today so get that one...I'm going to flash your new kernel on it and run it for the day and I'll report my findings
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's more than just overclocking support on offer. Compared to the stock CM kernel, here's what you get without changing anything:

Improved performance: more efficient task scheduling and memory management, optimized drivers, and tweaks for better battery life and responsiveness.

Fancy new features: glorious notification LED animation and similarly glorious softkey backlight animation*; with appropriate apps, you'll also get fast charge support and fancy sound adjustment (FauxSound and compatible apps). I'm sure there's plenty more that's not coming to mind right now.

All the latest bugs: I've been known to break things from time to time. If there's a problem, I'll do what I can to fix it though.

* I know I sound obsessive, but it always bugged me that the lights didn't fade in and out. Now that they do, I can't stop playing with my phone. :p
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Thanks for the quick reply. Are there any disadvantages that you're familiar with? Are things like freelunch activated by default?
[T-Mobile, Samsung Galaxy SIII] :
Freelunch is not activated by default. You'll either need to go into Performance settings (if you're on an AOSP build) or get a CPU App (like No Frills CPU) and turn it on.

Trust me...Freelunch does AMAZING things for battery life!
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Interesting. If freelunch is as good as you say it is, shouldn't it be enabled by default?
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's no major disadvantages that I can think of. The worst I can come up with is the inconvenience of having to flash a kernel every time you update your ROM (and possibly also having to flash dkp-enable-vmin.zip from the OP, in the unlikely event that your processor doesn't like the reduced voltages that dkp uses by default).

Back in the good ol' days of CM10.1, freelunch was enabled by default, but it's not anymore. In order to make it the default, I'd have to include a ramdisk. Because I don't include one, I save myself a lot of headaches (MIUI support, ROMs updating and breaking compatibility, etc.). Also, I'm too lazy to maintain one. ;)
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Interesting. The ramdisk you're talking about sounds like a swap partition or swap file? So why is it that only the freelunch governor requires it? The others don't? And CM10.1 brought this change? Anything specific about the 10.1 update that led you to change the default behavior?
[T-Mobile, Samsung Galaxy SIII] decimalman:
The ramdisk is a collection of files that are bundled with the kernel. When the kernel first boots, the files in the ramdisk are the only ones it knows how to find.

Once everything has finished booting, a script in the ramdisk changes a few settings like frequency governor. I used to change that script so that freelunch was the default.

Eventually, I got tired of keeping the modified ramdisk up-to-date, so I started recycling the ramdisk from the previous kernel instead. It's easier for me, but it means I can't make freelunch the default anymore.
[T-Mobile, Samsung Galaxy SIII] Synthetic.Nightmare:
I think init.qcom.post_boot.sh (/system/etc/) is responsible for those settings (cpufreq gov and whatnot)... for us at least.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Oops. I don't know why I thought it was in the ramdisk. I'm glad one of us knows what they're talking about.

Now that I've been reminded, I stopped because if you flashed a kernel without freelunch, the modified script left the performance governor enabled and murdered your battery life. In hindsight, it'd be pretty easy to fix that.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Thanks again. I'll do some more research on the topic. :)
[T-Mobile, Samsung Galaxy SIII] superuser696:
With a straight foward response like this. I've got to hear about your tw kernel. I'm flashing it now. Expecting pure awesome! !!:highfive:
[T-Mobile, Samsung Galaxy SIII] decimalman:
New TW 4.3 test builds are on their way! I fixed most of the problems I've been hearing about. Dead Trigger 2 still doesn't work, so there's probably still a couple bugs left in the video drivers.

Changelog:

Added a fancy blacklist that prevents thermald and mpdecision from modifying your min/max frequency when they shouldn't.

Fixed up some CPU power management stuff. mpdecision should stop whining and do its job.

Added fancy animations for the notification LED and softkey backlights.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
I still can't seem to get my camera to work man..... I really don't know what it is
[T-Mobile, Samsung Galaxy SIII] decimalman:
I just flashed Slim 4.4 this morning. I haven't played with the camera much yet, but it's behaved itself so far. I'm stumped.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Maybe it just doesn't play nice on my phone... I just get a green screen and I have to reboot the phone... Oh well
[T-Mobile, Samsung Galaxy SIII] decimalman:
Wait a minute. Someone on another carrier reported a green screen when playing videos in a certain app. It sounds weird, but the two problems might be connected. I'm supposed to send them a build with a few things reverted, and I'll build one for you as well.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Sounds good thank you!
[T-Mobile, Samsung Galaxy SIII] decimalman:
If I had to guess, I'd say I broke the driver that does image scaling and colorspace conversion. You'd think I'd know by now not to touch anything that already works.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Well if it's only reported on two devices then it must just be bad luck for us. Everything else was smooth but the camera. You're doing a great job man
[T-Mobile, Samsung Galaxy SIII] dynas7y:
Everything working fine on the latest slim 4.4 build for me as well. And I must say, what you did with the LED lights is indeed glorious! :good:
[T-Mobile, Samsung Galaxy SIII] decimalman:
Pretty sure I fixed it. Give the new build a try and let me know if it helps any.

New TW 4.3 and AOSP 4.4 test builds are up! Bugfixes all around.

TW changelog:

Fixed the softkey backlights ignoring their settings

Fixed a silly bug in the rotator driver

AOSP changelog:

Fixed the softkeys staying active when the screen is off

Cleaned up the notification LED animations

Fixed a silly bug in the rotator driver
[T-Mobile, Samsung Galaxy SIII] serio22:
Wow the new LED animation is amazing! Looks very nice, I missed that from my moto cliq back in the days.. Smooth sailing here :cool:
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I am sailing back and forth from 4.1.2 to 4.3.1 to 4.4.2 and was looking for a stable kernel for my trusty 4.1.2 nandroid. I must say I am truly impressed with your work. With Freelunch+ROW without undervolting or underclocking, I'm only losing 1% battery per hour. Amazing work! I will definitely try your work once stable SlimKat builds begin release.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] popimp315:
I think that may be where my problem is. I underclock to 1134, but have been having some lag issues with freelunch. I've always used it and it was always enough power to do anything and everything. I may need to bump it back up. Not sure if the 2nd core ever comes on either still. We shall see.

Edit: i dunno what it is. I get lag on free lunch. It starts to pick up but goes back to lagging. Confused
[T-Mobile, Samsung Galaxy SIII] notufatjesus:
Using the latest kernel for Tw 4.3.

I cant lower voltages. N e ideas?

Voltage apps force close...I cant adjust voltage levels...please help. I found this helpful for battery life.
[T-Mobile, Samsung Galaxy SIII] popimp315:
Try trickstermod. Most CPU apps have voltage control built in. I used it yesterday and it under volted
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Good to go now man no camera issues at all.... 11 hrs 30 min battery 2 hrs 15 screen and an hr calling
[T-Mobile, Samsung Galaxy SIII] RoxAbout:
Camera problems

Take a look at your camera icon...

if its a silverish camera black lens....its older original camera/gallery combo from v4.1 the gallery is a yellow flower

if its a black camera with blue lens...its the newer camera/gallery combo from v4.3 the gallery is a lightning bolt in pink mist

the silver camera [at least for me] locks up in portrait mode but works fine in landscape.

the black camera is more like the nexsus with a round focus ring and less options..I dont care for it but at lest it doesnt lock up :/

Freeze the correct camera [thats not working] in TIB

Hope that helps :highfive:
[T-Mobile, Samsung Galaxy SIII] afwolfpacked:
I been running the 4.3 TW kernel, latest release, for 2 days now. Rom is 4.3 pure stock deodexed Knox free ciq free from Docholiday. OC'ed to 1.7 and have great battery life on my SGH T999L T-Mobile no fc's nor any app problems. Wifi is great as well as modem and camera.

If you take request for features only ones I can think of is more CPU governors ex: Smartass V2 and GPU overclocking.

This kernel almost doubled my benchmarks and the smoothness is outstanding. I use performance CPU with SIO as it is geared for performance and slightly better results over ROW. No modifications to voltage.

Great work Decilman.
[T-Mobile, Samsung Galaxy SIII] claucXC:
Anyone have issues with the back button not working or difficult to activate? On some apps I have to hit the menu first to get the back button led to light. I can then press it and it works. With other apps I have to press a few times in a little different area around the icon to get it to work. :confused:
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
Wait does this kernel have the thingy where you can change the screen to Cool, Warm, Cold, or Hot? Sorry Noob here.
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's a couple bugs in the new code to animate the backlights. :( Waiting for the animations to finish screws up the suspend and resume code, and I'm having a hard time getting it working right.

Yep. If you're using Trickster MOD, look in the color settings screen. The setting in the advanced settings screen works too, but it's harder to get to.
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
Try increasing interaction return cycles. I was getting lag on a game that this seemed to help. I figured it was dropping out of interactive mode on me.