Android app device compatibility mode ( app-by-app "identify device as" option )
asked 2014-01-10 01:02:50 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
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 ...
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 +0200 )edityes, 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 +0200 )editI 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 +0200 )editThe 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 +0200 )edit