The “app” runs on Java, which runs on the native OS, in the context of the “app player” application. By the time you run a “native” Android app on a hardware emulator running on Windows, the efficiency is at or less than 10%.Īn “app player” skips the hardware emulation:īecause we skip the hardware layer, the emulation is 300% or more efficient than a hardware emulator. On top of this, an emulator running on top of Windows only becomes increasingly more inefficient. Unfortunately, Windows is horribly inefficient. Eventually, the OS loads the User Interface (UI), and allows the Windows –> Android user to load an Android application. When the device “boots”, it loads a ROM image, and the CPU (virtual CPU) begins to process instructions. It starts by building a virtual hardware layer, and then it emulates a virtual CPU. When you install the android developer kit (ADK), it comes with a hardware emulator that runs on Windows.Ī hardware emulator emulates literally every function. The final app “efficiency” on native hardware is about 0.5:1, or about 50%. If we look at the bare Android hardware and its operating system stack:Īndroid runs a proprietary operating system, and all android “apps” runs on top of Java, leveraging android libraries for device and hardware access, as well as look and feel.Īn Android app runs on the native CPU at a ratio of 1:1, but Java is inefficient, and all Android apps run in Java.
The appeal of an “app player” is that it’s about 3 times more efficient than an emulator.
0 kommentar(er)
