4 ms·

Anyone know how the Android app compatibility works? Is it a fork of Google code? Can Jolla be shipped by Android OEMs or will they be banned by Google for viol

by ezico 13y ago

Anyone know how the Android app compatibility works? Is it a fork of Google code? Can Jolla be shipped by Android OEMs or will they be banned by Google for violating the secret terms of the OHA like Acer was?

gmuslera 13y ago
Is not an android fork, is derived from maemo/meego, and includes a compatibility layer very much like the BB10 one to sideload android apps.
- ezico 13y ago
  Yes, I know that, but does the compatibility layer include Google code? Also my question about Android OEMs still stands. Blackberry is not a Android OEM so they are free to ship such phones and Google cannot stop them. See for more details http://www.engadget.com/2012/09/15/google-wants-better-compatibility-for-android/ http://www.engadget.com/2012/09/15/google-wants-better-compa...
azakai 13y ago
I don't know anything about the legal and contractual aspects here (that stuff is mostly secret anyhow), but I would be shocked if they did not use Google's code to do this. To not do so would mean reimplementing Dalvik and all the Android infrastructure libraries. That's a huge, huge amount of code, and it would need to be bug-for-bug compatible with actual Android code. Instead, forking it is far more practical (if still hard).
- anonymfus 13y ago
  They licensed solution from company which already did this: Myriad Group.
  - azakai 13y ago
    Thanks, but did what, though - do you know if they reimplemented Dalvik+Android libs from scratch, or are reusing Google code?
anonymfus 13y ago
http://www.myriadgroup.com/Press/News-2013/Myriad%20Powers%20Android%20Apps%20on%20First%20Jolla%20Smartphone.aspx http://www.myriadgroup.com/Press/News-2013/Myriad%20Powers%2... It's independent from Google code.
- candl 13y ago
  Does it mean it's limited to running only pure Java android applications that don't rely on any native extensions? Seems like BlackBerry 10's Android Runtime had this exact limitation but is now being improved to address this: http://www.theregister.co.uk/2013/11/25/revealed_how_blackberry_made_its_better_android_than_android/ http://www.theregister.co.uk/2013/11/25/revealed_how_blackbe... I wonder how they both compare.
  - RyanZAG 13y ago
    What native extensions? Android native code is just regular ARMv7 (usually) that links into a stripped out libc called bionic. Since both Android and Jolla are Linux there should be no problem with portability. The big issue for compatibility is in the Google Play libs - Amazon devices have similar problems with maps and that.
crb 13y ago
http://en.wikipedia.org/wiki/Dalvik_Turbo_virtual_machine http://en.wikipedia.org/wiki/Dalvik_Turbo_virtual_machine
mongol 13y ago
The best source of information at this time seems to be Youtube videos showing how people download apps from various app stores. One said that it was quite disappointing, that apps were crashing. The one he displayed shut down due to missing Google Play Services. I think this will be the main problem, as Google puts more and more effort in these APIs and less in the general Android ones.

by ezico 13y ago

gmuslera 13y ago

Is not an android fork, is derived from maemo/meego, and includes a compatibility layer very much like the BB10 one to sideload android apps.

ezico 13y ago
Yes, I know that, but does the compatibility layer include Google code? Also my question about Android OEMs still stands. Blackberry is not a Android OEM so they are free to ship such phones and Google cannot stop them. See for more details http://www.engadget.com/2012/09/15/google-wants-better-compatibility-for-android/ http://www.engadget.com/2012/09/15/google-wants-better-compa...

azakai 13y ago

I don't know anything about the legal and contractual aspects here (that stuff is mostly secret anyhow), but I would be shocked if they did not use Google's code to do this. To not do so would mean reimplementing Dalvik and all the Android infrastructure libraries. That's a huge, huge amount of code, and it would need to be bug-for-bug compatible with actual Android code. Instead, forking it is far more practical (if still hard).

anonymfus 13y ago
They licensed solution from company which already did this: Myriad Group.
- azakai 13y ago
  Thanks, but did what, though - do you know if they reimplemented Dalvik+Android libs from scratch, or are reusing Google code?

anonymfus 13y ago

http://www.myriadgroup.com/Press/News-2013/Myriad%20Powers%20Android%20Apps%20on%20First%20Jolla%20Smartphone.aspx http://www.myriadgroup.com/Press/News-2013/Myriad%20Powers%2... It's independent from Google code.

candl 13y ago
Does it mean it's limited to running only pure Java android applications that don't rely on any native extensions? Seems like BlackBerry 10's Android Runtime had this exact limitation but is now being improved to address this: http://www.theregister.co.uk/2013/11/25/revealed_how_blackberry_made_its_better_android_than_android/ http://www.theregister.co.uk/2013/11/25/revealed_how_blackbe... I wonder how they both compare.
- RyanZAG 13y ago
  What native extensions? Android native code is just regular ARMv7 (usually) that links into a stripped out libc called bionic. Since both Android and Jolla are Linux there should be no problem with portability. The big issue for compatibility is in the Google Play libs - Amazon devices have similar problems with maps and that.

crb 13y ago

http://en.wikipedia.org/wiki/Dalvik_Turbo_virtual_machine http://en.wikipedia.org/wiki/Dalvik_Turbo_virtual_machine

mongol 13y ago

The best source of information at this time seems to be Youtube videos showing how people download apps from various app stores. One said that it was quite disappointing, that apps were crashing. The one he displayed shut down due to missing Google Play Services. I think this will be the main problem, as Google puts more and more effort in these APIs and less in the general Android ones.