Search for a command to run...
I am a passionate and self-taught Android Developer who has good experience in AOSP, Native Android Apps (Java/Kotlin), Android for Embedded, Android in IoT, and Linux Kernel. I am more inclined to open-source, leading me to contribute to a few open-source projects. Sometimes I work in automation, scripting, and bots for myself.
No comments yet. Be the first to comment.
Let me introduce the fancy new LMODroid update we made for y'all. LMODroid is a free and open-source AOSP fork, providing optionally de-googled Android experience and top-notch stability along with a bunch of useful features so that you can enjoy usi...
Introduction You may come across a requirement in your app to store some configuration (not that big to use Room). For example, the previous UI mode - (Dark/Light) You might come across Shared Preferences for this requirement. Shared Preferences are ...
Introduction Imagine you are building a super cool android app! You want to share it with your friends so you have to generate a signed version APK and share it with your friends yourself. In the beginning, You will share an initial build with your f...
Prerequisites Make sure you know about the following topics. Basic Programming Open Source Git and GitHub Introduction What is open source? Open source projects are a type of project that is open and free for everyone so anyone can view, use and...
All of us use the android navigation component in our project to navigate from one screen to another easily. In some cases, you may need to navigate to another screen on a button-click event. To do that, you may do like the below code. binding.naviga...
Android APK is a file format(typically zip) containing the app's source code and resources.
Generally, Java/Kotlin code will be compiled into java bytecode. So we need a Virtual Machine to run the bytecode.
Android has an optimized runtime environment (like a virtual machine) to execute the compiled app instead of a Java VM. So android doesn't accept java byte code. It needs a different format based on the runtime.
Dalvik VM
Android Runtime (ART)
Let's see about them.
Dalvik VM is an optimized virtual machine for android to run android applications. It executes the .dex files.
Android APK contains the compiled app code in DEX format. You can check that by unpacking your apk and seeing the list of .dex files in it.
Your app code conversion happens in the following way.
.java / .kt (source) ---> .class (bytecode) ---> .dex ---> Dalvik VM ---> machine code
Dalvik uses JIT (Just In Time) compilation for translating the dex code into machine code to execute.
Whenever your app runs, Dalvik will JIT compile the part of the code which will run instead of the complete code.
Since Dalvik VM interprets the DEX every time the app runs, it gives a lower performance than native code execution. (like why python is slower than C++).
It's deprecated in Android 5.0
ART is introduced to solve the performance issue of Dalvik VM. It enables android applications to run natively.
There is no change in the APK. ART is also using the DEX format under the hood.
ART uses Ahead-of-time compilation (AOT) to compile apps into an ART-specific file format called oat at the time of app installation.
ART uses the dex2oat tool to compile the oat files for an app.
oat file is an executable file format which contains the AOT compiled code of the app. Technically, it's an ELF file.
After that, the app code will be executed from the compiled oat file directly.
Your app code conversion happens in the following way
.java/kt (source) ---> .class (bytecode) ---> .dex ---> .oat ---> ART (execution)
It has a better performance than Dalvik since it runs the code natively.
It is the default runtime in Android 5.0+.
image source: Wikipedia
A lot to learn in Android Runtime. A deep dive guide for another day.
Thanks for Reading ❤️