answered
2016-02-11 09:12:22 +0300
t-lo 
4384 ●51 ●61 ●63
I don't think this refers to aliendalvik, but to the low level hardware adaptation. Take a look at the SailfishOS stack (from https://sailfishos.org/about/):
We can clearly identify the optional propriatary Android runtime (Myriad's Aliendalvik). However, the hardware adaptationat the very bottom shows libhybris (a modified version of bionic, Android's C library/runtime) as well as Android hardware abstraction layer (hal) services. By the way, the kernel we're running on the Jolla Phone is an Android-specific vendor kernel provided by the SoC vendor (it's a far cry from any vanilla kernel.org version; and no upgrade to a newer version is possible). Without vendor support we would not have drivers for video, audio, telephony, opengl, etc... Jolla did not write those dirvers, nor are they even close to being resourced to actually do this themselves.
The (optional) Aliendalvik high-level libraries interface with those (mandatory) low-level Android layers. There's yet another Android hidden in your phone. On the upside it's mostly open source; at least all the Google low level stuff is. Vendor kernels however often include proprietary kernel modules for e.g. graphics and telephony (that's true everywhere, AOSP, CyanogenMod and all the others use those, too).
I strongly suspect the text on the sailfishos page refers to the low level layers; not to Aliendalvik.
Hope this helps,
Thilo
I agree, could be clearer that way.
juiceme ( 2016-02-10 20:37:23 +0300 )editFurthermore,it could be mentioned that sailfish os may run android applications. It does not run apps depending on android newer than kitkat, depending on google play services. Aliendalvik in sasilfish os is quite unstable, as far as I am concerned.
Moo-Crumpus ( 2016-02-11 09:01:33 +0300 )editAt least it should be mentioned, that Sailfish OS only runs Android apps on devices with an officially licenced Alien dalvik installed.
wanderer ( 2016-02-11 09:10:51 +0300 )edit