yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here you go guys, let me know on those 3 items :D

http://goo.gl/NssyPe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
[MENTION=1107425]lambgx02[/MENTION]

I just posted a test kernel, I put your change in it too. So they will say if it breaks ATT and you can download to see if it fixes it for you :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamFan05:
Booted fine and wifi and compass working as they should. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NinetyNineNights:
All confirmed working on my end!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AWESOME!!!!!!!!!!!!!!! Gonna release it then, so you guys dont have to re-download :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 1.28.2014

1. CM commit sync

2. A couple Ramdisk updates

3. Remove CONFIG_RTC_INTF_ALARM and CONFIG_RTC_INTF_ALARM_DEV from defconfig

4. Compass patch for Canadian variant from lambgx02 :good:

ENJOY!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Did not like my Phone. Assert failure Error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Stupid server. It does only a partial download sometimes. I suggest after every download to open the file to make sure its valid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Ok Trying again.

EDIT - Worked fine second time.

[MENTION=4325945]ktoonsez[/MENTION], This assert issue started since 12-24 release. On Slim, we T-Mo users modify Build.prop to make the device back to SGH-T999. The kernel's been objecting to the T999. If I spoof my phone to be I747, kernel flashes fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Thanks ktoonzes! :)

I actually made another few changes in my local branch; I noticed that kthermal resets the max CPU frequency to 1.5ghz when it gets bumped (and only a reboot seems to fix it), and that the default max temperature is pretty low. I regularly hit it during boot-up, which slows things down quite a lot. Manifests itself as ktweaker OC settings not sticking (processor never OCs, even if ktweaker reports max as higher).

diff --git a/drivers/thermal/msm_thermal.c b/drivers/thermal/msm_thermal.c
index fb305ae..c566845 100644
--- a/drivers/thermal/msm_thermal.c
+++ b/drivers/thermal/msm_thermal.c
@@ -64,7 +64,7 @@ static int update_cpu_max_freq(int cpu, uint32_t max_freq)
{
int ret = 0;

- if (max_freq > 1512000) max_freq = 1512000;
+// if (max_freq > 1512000) max_freq = 1512000;

ret = msm_cpufreq_set_freq_limits(cpu, MSM_CPUFREQ_NO_LIMIT, max_freq);
if (ret)

That at least prevents the thermal throttle from resetting the max frequency below whatever the user has specified.

I set my thermal limits to 70C/75C a few months ago and haven't had any problems (OC @ 1890); I can't imagine it's outside of the chip spec, but I haven't checked. Anyway, that limit definitely speeds boot-up for me (kthermal.h).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks like you posted the wrong file and or patch. I dont use "drivers/thermal/msm_thermal.c" so that code would have no effect. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Hmmf. Nevermind then. Pure coincidence. :o

I wonder what it was that fixed it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
[MENTION=4325945]ktoonsez[/MENTION] Couple of scripts are complaining about lack of init.d support for the TW kernel. Can we have proper init support in the next tw kernel?

Thanks for your awesome work for our service...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Would something like this be in the works for tw?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Init.d support is already in the kernel, looks like your ROM cant handle it. Make sure it has the proper files and they r the correct ones:

/system/bin/logwrapper

/system/xbin/busybox
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Update is great kernel is great you're great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Both of these files are there. See attached screen shots..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
May be you have wrong version of them ? Best install busybox from Play store then try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Has there been any thought given to added "Charging Gov" and "Charging Sched" settings? I prefer to use KTweaker, but one of the things I like about SetCPU is the ability to use different governors depending on whether the phone is charging or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Have you looked at the Profiles in the Shop ? Several change either Governor or Scheduler when phone's on Charge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I looked at a few of them but didn't see any that did this. How is this possible without using scripts since the profiles just change existing settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi guys. Anyone else missing LED settings in the ktweaker app? I also cannot disable toast msgs as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LED settings are not supported on S3. If you selected disable then you turned of all messages that my app posts in toast. It does NOT disable toast messages from SuperSU, you have to disable them there if you want to stop those.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Oh. That's odd I had led settings in a previous release I didn't touch them cause I didn't know what to do with them but they were there. I guess that was just a fluke.

When I select disable it will still say enabled for toast msgs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The previous release did have the LED in there by mistake. For toast thing, something is not letting me save that option then or you need to clear app data and start again manually.

EDIT:

I think I see the problem with Toast, I will fix in next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
I'm running a 4.3 AOSP ROM. I installed the latest kernel which has exfat sdcard support. But my 64GB sdcard still can't be read:(. Help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If it doesnt read, its not ever going to. Some cheapy cards dont work with 3rd party exfat. Samsung card will work everytime.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
My card isn't cheap is the class 10 red and grey one. Cost me a good amount of money
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Errrm.. How come SlimBean is able to control LED just fine ?

The Ex-Fat Support is on Kitkat version of the Kernel not 4.3. Secondly, format the card to be FAT32 on Windows. Then put it in the phone, power on the phone and format the card again. This time for Ex-Fat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Because I wrote it for the S4 and the S3 cant do the things I did on the S4 so it would be complete new rewrite and have to have different variables and makes it messy :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Correct busy box is installed. Check the attached screen shot.. Just tested the init.d on TW lab kernel on the same rom and working without issues. I can't switch at the moment because i am getting good life with this kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Weird, must be something different that the ROM need instead of the standard lines, cant image what else it would want. Post a link to the kernel (boot.img) u r talking about and I will take a look to see if I can merge it without breaking all the other standard ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Ah I see. Yes that makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I have attached the boot image, hope you can crack the issue. I am using the best TW ROM Srx 3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Bad news :(. Ramdisks are identical so I dont know what that ROMs issue is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
This is what i have extracted from your kernel. Sorry for any confusion. What's the location of boot.img on my phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
This is the boot image which i have extracted from the ROM zip file

Hope this help this time

Edit: The md5 is different of your kernel and the ROM boot.img
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Screen shot attached of the two boot.img
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Flashing the 1.28 update. Hopefully will fix my issue with power button not putting my phone to sleep or waking it up and just overall really glitchy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
What's up with the "awake" and "screen on" bars?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
md5's are always different. Ill check out the kernels ramdisk to see if there is any differences.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here you go, try this, hopefuly it wont screw up everyone elses ROM:

http://goo.gl/ibIUmT

Let me know
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for putting effort, but still init.d support is missing..

Edit: I am using the killjoy init test script

http://www.mediafire.com/?97q4sh1wwcesois
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Well it matches the other kernels bizzare way of doing so nothing more I can do:(. I would double check permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Split the boot.img, edit init.rc and add these lines in the appropriate spot:

service sysinit /system/xbin/busybox run-parts /system/etc/init.d/
class core
user root
group shell
oneshot

I could provide you with a custom boot.img I personally use myself along with the modules, but it doesn't use the current kernel in this thread. It has init.d support and a fixed root (I hate it when root access is dependant on one little file in a Rom when it could be used for something else).

However this is off topic, pm me if you're interested... In no way am I a kernel developer, ktoonsez is the guy for that.

Disregard my post if you're not interested. I could also make a flashable zImage of this kernel if you prefer your own custom ramdisk...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The code you posted was exactly what I had that doesnt work on that guys ROM, I removed it and added what was in the kernel the other guy mentioned. Not sure what that ROM is doing. Here is what the other kernel had:

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

disabled

oneshot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here is another test for init.d:

http://goo.gl/4CWqA8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Finally we have the perfect init.d support. You are the man kt!!

Thanks for your effort
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AWESOME!!!!!!!!!!!!!! I made it so the rest of the ROMs wont loose it, I hope :D :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Bump.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
(re: TWRP errors) I actually get that from time to time as well; I find that wiping /cache (Wipe->Advanced Wipe) before flashing seems to resolve it for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
I don't use TWRP but was getting the same error message on CWM. I reflashed recovery and it seems to have gone away.

EDIT: Never mind, error message was back again when I just went into recovery to flash a volume mod.

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Purely out of Curiosity, [MENTION=4325945]ktoonsez[/MENTION], Why do you have two files in the init.d after flash ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Some whinny people didnt like using my app and didnt know how to write scripts so I had to include scripts that are disabled since they have an extension on them (removing the extension enabled them). 1 was for enabling OC and forget what the other was.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Oh Ok. Thanks for letting me know. So safe to say you can get rid them if you are using the App right ? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you want, they dont hurt anything and everytime you flash they will re-appear again, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galakanokis:
Are there suppose to be scripts in the script store in the tweaker? I see profiles (awesome by the way) but no scripts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No scripts built yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Sadly :(

I would really like to know the EXACT limitations of the ktweaker script on boot dealio, is it exactly the same as SManager's limitations? Because I know you can pull off a bit more with init.d scripts than you can with these scripts, but I also know that doesn't necessarily mean there's a workaround or what have you; I have like 6 "proprietary" init.d files (they were hand picked and tested with a thumbs up from me) will get condensed into a start-up script, at least the ones that would make sense to anyways.

But until then, I've been messing with the profile store..really like it and hope the script store is layed out the same, I love being able to not only download but also see a description (maybe add the option of pictures/logos/battery screenshots?) as well as a list of all the changes made, for scripts it would just be the script text. Some profiles I highly recommend checking out are:

3hands (supposedly a combination of ktoon's profile, balanced bull reloaded and project icarus - kamikaze)

Dead by April (a great battery profile, you'll notice that's a theme here....these are all conservative as can be profiles, there's no point in having great performance with a dead phone)

Moonlight (based on project daylight,1GHz is the highest voltage but there's some good performance here which is normal with KT's kernel :D)

Project Daylight v2 (similar to icarus, not underclocked as much as moonlight but still a good battery and performance profile)

Smooth Criminal (phone running smooth as ever, so smooth that it's criminal to get this great battery. "over 2 days on a charge with 6 hours of screen time running super smooth."..)

Super Battery Saver (just what it sounds like...1.1GHz underclock, not that bad for the S3 but a bit more of a decline with the S4 so when porting over to us maybe it should have been edited...125 CPU undervolt, this is a good one)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Luigi can answer some of these but I can answer the limitation part. It can only execute "echo" statements as far as I have tested. Things like for loops and sleep statements will probably do nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Bes if you post this on Luigi's thread. This thread is a Development thread and we really do not want it to turn into Shop discussion. That's what Luigi's thread for.

You are welcome to create your own profile based on these profiles and post in that thread for others to review.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Interesting that many of us have this. Including me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Have you wiped Dalvik +Cache before flashing ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Every rom flash full advanced wipe everything except ext SD. Keep no important files on internal.

Yet happens every time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
That's not what I menat. I meant, if you wiped Dalvik + Cache inside Recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Here's the balanced bull script....the original controlled CPU1 CPU2 and CPU3 while leaving Ktweaker to control CPU0 (like it normally does) however the script takes over for the other cores obviously. On this device we are much more limited, we have ktweaker and the already-ported profile controlling CPU0 and the script takes control over CPU1....but we can't put 3 awesome gov's on 3 more cores, just 1 on 1 more. So, really, the choice is between asswax and intellidemand, I will provide both and you can choose. Nobody seems to know anything about asswax lol but the thread that started all of this spent a lot of time with asswax cpu1 scripts for the gs3 ktweaker and there was no quad core phones to do it on. The addition of more cores added asswax to the 2nd, intellidemand to the 3rd and adaptive to the 4th, decreasing in the amount of settings with each.

Anyways here's the stock asswax controller for CPU1:

#CPU1
echo "asswax" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "594000" > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq
echo "1500" > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us
echo "1026000" > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq
echo "60" > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load
echo "48" > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load
echo "200000" > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step
echo "100000" > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step
echo "378000" > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq
echo "486000" > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq
echo "48000" > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us

and intellidemand:

#CPU1
echo "intellidemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "594000" > /sys/devices/system/cpu/cpufreq/intellidemand/boostfreq
echo "3000000" > /sys/devices/system/cpu/cpufreq/intellidemand/boosttime
echo "2" > /sys/devices/system/cpu/cpufreq/intellidemand/down_differential
echo "1350000" > /sys/devices/system/cpu/cpufreq/intellidemand/optimal_freq
echo "40000" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate
echo "70" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold_any_cpu_load
echo "70" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold_multi_core

No changes have been made except for making intellidemand work on cpu1 not the nonexistant cpu2 on the gs3 :P

I'm not sure how the values should be tweaked, I doubt they are optimal for the gs3 compared to the gs4 but having a place to start is all that is needed for people to start trying things out....for now, I'm sticking with trying dead by april.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galakanokis:
Anyone else having an extremely high msm-otg wakelock? Only thing I've changed in the past two days is fish the latest kernel. Never had this wakelock before, never used an otg either. Odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Probably have some junk in the chargin port. Spray it good sith some compresed air
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galakanokis:
I'll give that a try, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Yes. Before and after. Happens every time.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Wiping cache is only a temporary solution. After some moderate usage of the phone the recovery will show the same errors again. My conclusion is that some how the cache partition becomes read only. If the phone stays idle after the cache wipe and your boot back into recovery the errors will no longer be there but if you use the phone for about five minutes and boot back into recovery errors will be back. My mother has the same phone as me with cm11 on it and she does not get these errors. The only difference between hers and mine is mine is older and I'm on MK5 bootloader. So its either my cache is dying or MK5 is causing this. I dunno what it could be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I get them too, I'm on LK4 still actually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I haven't YET ran into the issue you guys are talking about but I'll keep an eye out.

As it is my phone needs to get opened up so I can see wtf is wrong with the power button, it's stuck down but the actual button can still be pressed and depressed, so i can press it but if i'm not pressing it and i put a battery in, it boots up automatically. My phone constantly is not in sleep mode because it's asking me to reboot menu or w/e...So....Flashing a rom and kernel is ****ing HILARIOUS, I'm spamming the power buttin and the slide to unlock thing, wiping everything, flashing quantum, 0day gapps, kt kernel (duh) and after a few minutes of sweating you can boot into it...as long as you spam the power button from the second you hold it down until you get to the lock screen. Freakin NIGHTMARE. Download mode? talk about freakin' anxiety, the phone can randomly shut off at any time and so that's useless.

Once i get that sorted I suppose I can try to recreate this issue, I haven't experienced it with high use though. Running dead by april profile from the shop and the script from the sgs4 repository. Script has a noticeable difference and I like it. And I could use Drastic no problem :)....love this kernel, but I want to push it to it's limits even more...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Small request, can we have faux sound support in next tw kernel update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
[MENTION=4551784]matrixzone[/MENTION]

Try this, I thought it was in there but may have been missing:

http://goo.gl/MLXIe9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I'm on MG2. Still getting the error. Running ART, if that could make a difference.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It is probably FART, that thing is the devil, cant even count how many posts have been generated about problems that end up clearing up after doing a fresh/clean flash and never using FART again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Can someone that uses Faux Sound test this so I know its good to go? Traveling on Monday morn and want to make sure this is a done deal :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
My Guinea Pig erm I mean the other TW S3 just went out. So gotta wait till it comes back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
You're good to go, no longer gets the kernel does not support screen. Su permissions granted :thumbup: now if we can get those scripts in the ktweaker shop today will be a good day. Lol great work kt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Ah beat me to it. My Guinea Pig hasn't come back yet. But don't think [MENTION=4325945]ktoonsez[/MENTION] needs me now. :p

[MENTION=4788295]Shels[/MENTION] Please discuss all about KTweker App in Luigi's Thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, well anybody that uses the Faux Sound app can feel free to download it :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Since when have there been major issues with ART? It has been working perfectly for me since before the official CM nightlies and nobody else complains.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Always. For me, the only issue I have had is es file explorer, snap camera, and gallery don't work. For many others it will work for days. Then they flash some thing and get stuck in a boot loop forever. Games stop working and won't open anymore. Many more that I can't remember.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I'm going to try to replicate the cache problem with Dalvik.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Other than Xposed framework which isn't compatible, I've had no issues with Art. Very happy with Slimkat and KT, been using Art for the past few weeks full-time.