[solved] eOS 3.1.4-a14 (FP5) Incompatible Apps - sideload via "adb install-multiple" possible

Using /e/OS User Queries
1

Hi,

I just switched over from Android Stock FP5 OS to eOS (3.1.4-a14) and mostly runs out of the box :slight_smile:

But I could not install some apps directly via “App Lounge” or “Aurora Store”. App Lounge stucks in “try installation again” and Aurora tells me, that the App in incompatible with my phone. Trying to install the APK directly inside eOS also tells me the App is incompatible.

I started debugging a little bit and identified by adb sideload the error INSTALL_FAILED_MISSING_SPLIT. Okay - that may be easy to fix because I’m aware using adb for app side-loading and apkeeper.

I used apkeeper for downloading the needed apps with the option split_apk=true and could then successfully install them with adb -s <id> install-multiple <app-package-name>/*. And the installed apps are running fine.

But what I couldn’t Identify is why the eOS tells me, that those apps aren’t compatible with the phone - even if the are running by adb side-loading.

Here an example/incomplete list of the apps I couldn’t install directly by the App Stores but got them working by adb side-loading:

  • Easypark
  • Parkster
  • DHL&Post
  • ChatGPT
  • Google
  • Google Maps
  • Android Auto
  • FreeNow
  • Uber
  • N26 Banking App
  • Google Text to Speech

Currently I’m not sure what the “incompatibility” forces. And I currently had not much time to start debugging the store or native installation process directly on the phone to figure out why the apps therefore can installed by adb side-loading.

Chris

1 Like
2

While i did not give much away about this problem which I believe is being taken seriously behind the scenes I linked this earlier Certain apps will not install through App Lounge - #4 by aibd

More evidence added to the Gitlab issue would be useful. Perhaps cross reference App Lounge - Amonymous Account Unavailable - #16 by aibd

3

Hi,

thx @aibd for the info and link. I didn’t found the linked topics together with my used keywords searching in the forum.

Changing the the phone type (aka spoofing) inside the “Aurora Store” app to another with the same API than the FP solved the installation issue.

I will also link this info to the gitlab topic.

But I also assume that this is not only a Aurora Store or App Lounge issue because installing the apks of the apps via the file manger e.g. also run into the issue “not compatible with your phone”. App Lounge is still not possible to install the mentioned and some other apps I’ve tested.

Thanks, Chris

2 Likes
4

Thank you for reporting precise information.

It would be great if you could get a logcat of this “on device” behaviour which might make more clear the trip up point. What “marker” on a Fairphone is being used to deny?

1 Like
5

This topic was automatically closed after 30 days. New replies are no longer allowed.