[AshDizzle]

So I know I am not alone when I say I am frustrated at the amount of top android apps that when converted from .apk to .bar, do not work.

Apps like Netflix, Spotify, Instagram, etc. all can be converted to .bar no problem but always force close. What is the reason for this? Why are they force closing? Isn't there some work around we can do as a community to get this figured out?

Pic related: it's my frustation. SO CLOSE but force closes right after!

IMG-20121205-00008.jpg

[lunaticwithin]

I believe some of these apps use native code built into the app specific to that app which the android player can not support.

[Xopher]

It's the coding. The Android Player is built on Gingerbread 2.3. Depending on the API build, there may be function calls Worthing the app that aren't supported by the player.

Plus, it seems like most of the apps that transfer over are Java based (made using the Android SDK). Apps that include native C++ code (Android NDK) seem to be the ones that fail. The Android Player doesn't seem to fully support all of the Android operating system, just a subset.

[sjc1963]

The Android is so fractured that not even all native apps will function on all devices. Unlike the Playbook Androids come in many different configurations and CPUs....... Not all are compatible with each other either.

[ralfyguy]

Kinda sounds like a big ole mess to me.

[AshDizzle]

The Android is so fractured that not even all native apps will function on all devices. Unlike the Playbook Androids come in many different configurations and CPUs....... Not all are compatible with each other either.

In that case are each of the .apk files different from device to device? Is there an Android 2.3 device out there with extremely similar specs as the Playbook that we could steal .apk files from?