We have moved to a new Sailfish OS Forum. Please start new discussions there.

Android app device compatibility mode ( app-by-app "identify device as" option )

asked 2014-01-10 01:02:50 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2014-07-24 12:57:39 +0300

eric gravatar image

Some Android-apps state they are not avail. to jolla's Android environment (aka the "Unknown Alien_jolla_bionic").

It could make sense to circumvent this by implementing a Dalvik-pulley where one could choose identifying the Dalvik runtime differently e.g. as a Samsung or other specific Android device. For example, a Sony-remote App happens to be "Unknown Alien_jolla_bionic"-compatible (even though jolla has no IR-transmitter built in) whereas a headphone's audio suite ("Parrot Audio Suite") is prevented from getting installed even though just being a Bluetooth communication app ...

edit retag flag offensive close delete


I made the experience myself that some android applications do work on Jolla even when they were marked as not compatible. As long as the market share of Jolla is low I think this option could make sense. Otherwise you need an additional android device to download the *.apk files

NFec ( 2014-01-10 01:07:59 +0300 )edit

yes, the *.apk-download ;-) ... anyway it could be a bit more efficient in long term having an option to open any Android-app with a certain, selectable device association: Maybe a bit like Win7's option Properties > Compatibility > "Run this program in compatibility mode for" (e.g. WinXP SP3) ...

launchpad ( 2014-01-10 10:06:57 +0300 )edit

I think this might be why LinkedIn login works half way (a session is established, but one cannot advance from the login page).

pulsar ( 2014-11-29 21:00:02 +0300 )edit

The LinkedIn that does not work is the one from the Opera Mobile Store, I think it is older than the one in the Jolla Aptoide Store. I saw people on real Android having similar login problems with this app at some point, so identification might not be the problem after all in this case.

pulsar ( 2014-11-29 21:24:29 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2014-01-10 19:05:54 +0300

Sailor gravatar image

updated 2014-01-10 19:09:02 +0300

It should help to edit build.prop to a Samsung galaxy s3 (located in /opt/alien/system):

edit flag offensive delete publish link more



Looks good to begin with ---> but'll be great if it could be implemented neatly as a pulley-menu or tile control. So it can be possible to open one app with Samsung-device-settings and another one simultaneously with "identify-as-Sony" settings. I'll try your idea anyway as soon as having some time.

launchpad ( 2014-01-10 20:17:01 +0300 )edit

Yes, that would be cool. But I think this is not the intention of sailfish because I (we?) want native apps :). Please vote if you liked the answer anyway :).

Sailor ( 2014-01-10 20:43:37 +0300 )edit

I prefer native apps. PAUSE & FULLSTOP ;-) But if I had to fall back on an Android version (like Parrot's Audio Suite) I'd welcome a versatile fallback to circumvent paternalistic limitations as "device compatibility" is handled rather superficial than objectively in the Playstore :-( ...

launchpad ( 2014-01-13 00:02:24 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2014-01-10 01:02:50 +0300

Seen: 2,440 times

Last updated: Jan 10 '14