A: @ rovo89 has explained himself. http://forum.xda-developers.com/show...55&postcount=3 A: Of course not. This is the main reason why deodex'ed ROM is a prerequisite.Samsung has implemented all sorts of funny stuffs on their version of ART. See the link above.To workaround this, converting a ROM to deodex'ed format somewhat brings back the oat formats to *AOSP-like* dex format(Huge thanks to @ _riddle ).After deodexing is done, we can use source-built ART binaries with minimal modifications.But due to my coding skills, I had to modify core-libart.jar to make it work again.The core-libart.jar differs from every single device out there and it'll be a real headache to match with 1 ART binary version. That's why I've included the core-libart.jar on the installation zip file.The included core-libart.jar has 2 different versions to correspond on the type of ROM user is using.1 : Firmwares with appStartup2 : Firmwares without appStartupAfter deodexing, installing new ART stuffs, we can start the boot-up sequence.Unfortunately again, /system/bin/installd passes some arguments that AOSP version of dex2oat do not understand. To bypass this, I've patched oat tools to ignore unimplemented arguments.Now we can see the good old "Android is upgrading" pop-up and go have a cup of coffee while it dexopts all those hundreds of bloatwares.A: To avoid that, that's why I've put 2 different versions of core-libart.jar. But unfortunately on those cases, my installer has failed to recognize which version your ROM uses.During the installation, the installer will output a message on which core-libart.jar is installed on your system.After you see that logcat stuffs, please change to the opposite version of core-libart.jar the installer told you.So for example, if the installer says core-libart1.jar is installed, extract the zip and replace /system/framework/core-libart.jar with core-libart2.jar within the zip.A: @ joeldroid and @ svadev have an awesome tool for you to deodex your ROM.Go check http://forum.xda-developers.com/andr...batch-t2980857 and http://forum.xda-developers.com/gala...oid-l-t2972025 Both worked flawlessly for me.A: https://github.com/arter97/android_a...msung-lollipop A: Most likely because they don't support Touchwiz Lollipop *yet*.A: Unfortunately, I had tested those only on 3 devices which, ironically, has the same processor. Maybe Exynos family is not support, I don't know.I told you to back-up beforehand. Post log and we can probably work together and add your device/ROM supported.