Revision history [back]
 | 1 | initial version | posted 2014-01-10 01:02:50 +0200  |
Android app compatibility .... "identify device as"-option
Some Android-apps state they are not avail. to jolla's Android environment (aka "Unknown Alien_jolla_bionic").
Would it make sense to circumvent this by implementing a dalvik-pulley where one could choose identifying the device ( dalvik runtime ) differently e.g. as a Samsung or other specific Android device ? I'd definitely support this ! 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 ...
| | 2 | No.2 Revision |
Android app compatibility mode .... definable app-by-app "identify device as"-optionas"-option/pulley
Some Android-apps state they are not avail. to jolla's Android environment (aka "Unknown Alien_jolla_bionic").
Would it make sense to circumvent this by implementing a dalvik-pulley where one could choose identifying the device ( dalvik runtime ) differently e.g. as a Samsung or other specific Android device ? I'd definitely support this ! 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 ...
| | 3 | No.3 Revision |
Android app compatibility mode .... definable ( app-by-app "identify device as"-option/pulleyas"-option )
Some Android-apps state they are not avail. to jolla's Android environment (aka the "Unknown Alien_jolla_bionic").
Would it It could make sense to circumvent this by implementing a dalvik-pulley Dalvik-pulley where one could choose identifying the device ( dalvik Dalvik runtime ) differently e.g. as a Samsung or other specific Android device ? I'd definitely support this !
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 ...
| | 4 | No.4 Revision |
Android app compatibility mode ( app-by-app "identify device as"-option as" option )
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 ...
| | 5 | No.5 Revision |
Android app device compatibility mode ( app-by-app "identify device as" option )
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 ...
| | 6 | No.6 Revision |
Android app device compatibility mode ( app-by-app "identify device as" option )
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 ...
Android app device compatibility mode ( app-by-app "identify device as" option )
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 ...