OsmAnd+ (from Amazon App Store) does not connect to Android Auto

[anastasiia936]

Description

OsmAnd+ app (from the Amazon Appstore) does not work with Android Auto on my whole range of devices (from Android 6.0.1 to Android 12.
Tested on sony tablet (SGP621) with Android 6.0.1, Pixel 5 with Android 12, Nokia 3.1 with
Android 10.
It is always the same problem: The OsmAnd* app does not even show up in the list of Android Auto apps.

OsmAnd 4.1.10

[stephane607]

I have the same issue with OsmAnd+ app from Amazon Appstore, Tested on Oneplus 6 on Fairphone3.

[casta]

I have the same issue when installing OsnAnd+ using AuroraStore (so apk from playstore but not installed using playstore).
After digging a bit, it « seems » that the application only show in AA if it was installed by com.android.vending (so only playstore). That’s why things like KingInstaller exist (this is only just basic installer, but forcing the installer name:
https://gitlab.com/annexhack/king-installer/-/blob/master/app/src/main/java/com/example/kinginstaller/MainActivity.java#L129

Maybe a track to follow?

Thank’s!

[ghost]

I have the same issue with the APK installed by F-Droid.

[bauspanderu]

I'm having the same issue with the F-Droid version, even with "unknown apps" enabled in the debug options in AA

[panoskpv]

Same here for app downloaded from f-droid. Any idea to solve this issue?

[x86dev]

Asking myself the same. Could anybody shed some light one this, please?

[vshcherb]

FYI: #3391 (comment)

[stifi]

As proposed on reddit and discussed on gitlab, I got the F-Droid version of Osmand~ working with Android Auto using adb installation:

  adb push net.osmand.plus_421.apk /data/local/tmp
  adb shell pm install -i "com.android.vending" -r /data/local/tmp/net.osmand.plus_421.apk

[panoskpv]

Thank you for the provided information. However, i had no lack with MIUI 13 (android 12). Any ideas?

[polarbearing]

The workaround above by @stifi works for me in Android 7.1.1, and when I check the general settings -> Apps, it now says in small print at the end of the OsmAnd details "App installed from Google Play Store", which of course it isn't, the Play store was disabled all the time.

So apparently the workaround has been tested successfully in Android 7 – 10, while the user in reddit reports fail in Android 11, and a user in gitlab and a user here report that it does not work anymore in Android 12.

Now AA bothers me with large notifications that my Android is too old, however there is no newer version for this device. Why can't they just let me working with what I have...

[stifi]

After successfully applying the workaround discussed in #13514 (comment) I updated OsmAnd~ to 4.2.4 using F-Droid. After the update OsmAnd~, wasn't listed anymore in Android Auto (confirms that the issue is still unresolved). So I manually downloaded the apk and installed it again with:

adb push net.osmand.plus_424.apk /data/local/tmp
adb shell pm install -i "com.android.vending" -r /data/local/tmp/net.osmand.plus_424.apk

With this method OsmAnd~ 4.2.4. is again available in the launcher of Android Auto.

I have Android 10.

[licaon-kter]

An interesting note here: TeamNewPipe/NewPipe#1758 (comment)

[giabao06]

The workaround mentioned here failed on android 11 for me. OnePlus Nord N10 5G, F-droid package (version 4.2.6). AA settings show OsmAnd~ in packages but no option to show it in launcher.