ART to replace Dalvik runtime on next version of Android


ART - Dalvik Compiler

Google has been experimenting with the ART runtime compiler for quite some time now. Introduced initially alongside Android 4.4 KitKat, it was far from ready to be deployed as the default. However, over the months stability has improved multi fold and so has application compatibility.

What exactly is the difference between the two compilers? The current compiler ie Dalvik is a JIT compiler. JIT means Just In Time. What this means is that it will compile code only when the app needs it. In comparison, ART relies on Ahead Of Time compiling which will run the code before it is needed. Since it compiles the code at the time of installation, it will offer improved performance, better battery life with slightly larger installed app sizes being a tradeoff. Another possible tradeoff is that applications that haven’t been rewritten for ART may not work properly. That said, most popular applications have long since been updated.

Dalvik is dead, long live Dalvik! DO NOT MERGE croot cd libcore repo start dalvik-is-dead-long-live-dalvik . repo sync -c . git rm -r libdvm git add JavaLibrary.mk (after removing libdvm references, adding explict core-libart references) git add Docs.mk (after replacing references to libdvm with libart) git add benchmarks/Android.mk (after adding explict core-libart references) git add Android.mk (after removing dalvik-host target) git commit -a -m ‘Dalvik is dead, long live Dalvik! DO NOT MERGE’

Switch from core to core-libart

The above message was spotted in the changelog. With the removal of ART from the AOSP master branch and it being switched as the default compiler, we’re inclined to believe that the next major Android revision will replace Dalvik and switch to ART instead.

[Via – XDA Developers]


Author: Dhruv Bhutani

Your friendly neighborhood techie. Currently using a Pixel 2 XL. Catch him on Twitter (@DhruvBhutani) / Facebook .