Android Auto isn't detecting apps on my radio. I have Podcast Addict and Google Play on the list of available apps. However, Audible, Spotify, and Pandora don't appear in the list of available apps. Is there something I am supposed to do to get the apps to appear?
I am using SyncGen3 w/ Android Auto and a Galaxy S7 Active phone.
Applications mentioned above must have following to be visible at AA Google play
1) valid AA certification
2) valid country code
I assume you have issue with 2. Please identify your current country and we can check. Workaround is to use fakeGPS/fakeGmail based on US, install required apps and then unlink and connect your original gmail country. This works for me also.
I experienced the same behaviour. I installed an app compatible with AA and didn't find it on the display in my car. Even rebooting the phone didn't help. After some days after I installing a further AA app the first one got visible as well.
Related
EDIT: Updating the AA app manually did the trick.
AA was working for me yesterday.
Now it shows an error due to enforcing of the country whitelist that I guess does not include my Canada.
Not sure where yet or how to bypass. AA app is the same, and Google Play Services is a few weeks old.
Previously log said "Country is not whitelisted: " + ph.c() + " but gearhead.apk is installed, so we continue"
Maybe it activated by date ? Maybe it's an online switch ? AA won't start on devices that I've now turned GPS and WiFi off.
There are other whitelists and blacklists in the AA app that may be activated in future: mobile device, head unit/car.
Headunit (or my headunit app) does not currently seem to validate headunit certificate(s) but there is code for that & I wonder if that may be enabled also.
EDIT: Updating the AA app manually did the trick.
There is an AA startup phase where you are prompted to install or update the needed apps: Music, Maps, whatever...
I've gone through this several times; not sure why it doesn't always stick.
At this point I get a popup dialog saying "This item isn't available in your country."
Which is exactly what we get trying to download apps not enabled for our country.
I created a new account claiming to be in the US, but that didn't help; probably Google's IP detection knows I wasn't in the US.
Hmm, maybe if I manually update the needed apps as well as the AA app ?; I'm still using the original AA app.
So manually updating the AA app worked and you can now continue using AA?
(Sorry if I did not post this right. Its my first time on xda.)
fraessp said:
So manually updating the AA app worked and you can now continue using AA?
(Sorry if I did not post this right. Its my first time on xda.)
Click to expand...
Click to collapse
That is correct.
This will be an ongoing problem for those of us outside approved countries, and it could get worse.
Once it detects that there is an update, it refuses to run before the update is done, and outside the US the AA app can't normally be auto-updated by Play.
And most of us want the features we need to be logged into Google for, so disabling update detection is not entirely feasible.
Hi everybody
I have seen a lot of posts from people using Android Auto in a non-supported country who get the message "This Item Isn't Available in Your Country".
Since I haven't seen a real solution for this problem and I encountered this today, I thought it might be useful to post a small guide on how to avoid this problem. (At least it worked for me today)
Basically, you get this message because Android Auto needs to download (or update) some Google applications for Android Auto to work on your phone. While doing this, the application performs a country check and thus refuses to run. By installing these applications through the play store and make sure they are up to date, you won't run into this message.
1. Install or update the following applications: Google Calendar, Google Play Music, Google Maps, Google Voice, Google, GMail, Google text-to-speech (Basically all apps Google uses in Android Auto )
2. Reboot your phone
3. Use a wifi-network to connect to the internet. So do not connect using mobile data.
4. In the security settings, enable "Unknown sources"
4. Download the latest Android Auto APK from a trustworthy website like apkmirror.
5. Install Android Auto by opening the downloaded APK-file
6. Run Android Auto and follow the steps in the setup process
7. Enjoy Android Auto
Not working
Unfortunately it doesn't work for me
Some people report that Android Auto does not start after connecting their car. I want to share some tips for eveyone, hoping to help guys with this problem.
Troubleshooting:
1. Make sure the car is compatible with Android Auto (To query if the car compatible Android Auto, please check from the website, https://www.android.com/auto/#hit-the-road)
2. Your phone's system version is Android 5.0 or later
3. The Google service framework is pre-installed or installed on your phone. Otherwise, you cannot use Android Auto properly.
4. Make sure the network which you connect to has access to the Google server. You need to log in to your Google ID in Google Play Store to download the app to be used with Android Auto (such as Google Maps, Google browser, Google Play Music, and Google Text-to-speech). Enable all relevant app permissions and make sure that the app, such as Google Maps and Google Assistant, has access to the Google server. Currently, common networks in China do not have direct access to the Google server.
5. Try using a new USB cable.
Here are some tips for finding the best USB cable to use with Android Auto:
1) Use cables less than 6 feet in length and do not use extended cable.
2) Make sure your cable has the USB icon.
If Android Auto has stopped working in your compatible car:
1) Try replacing the USB cable – most problem are solved by this!
Good post
I have been reading the various threads and GitHub issues for popular custom AA apps and it seems nobody has really explained the real reason the apps are not working any more: any apps developed using an unofficial AA app SDK (aauto-sdk) OR using the internal AA APIs will no longer run (crash on start - the screen just blinks and goes back to AA launcher) because of this Exception:
java.lang.SecurityException: Wrong signature - go/gearhead-retail-device
There are temporary workarounds such as downgrading the Android Auto APK and preventing server-side config from downloading to device but currently, for normal non-rooted users which have auto-update on these apps won't work. Renaming their package names won't help either as they will still trigger the Exception when trying to show their UI on AA screen.
For AA developers: Google wants to limit the functionality of AA apps for various reasons, including safety while driving. The only official way to develop AA apps is to use the Android for Cars App Library. This library does of course not allow for low-level API access which custom AA apps relied on - no longer can you just manipulate your own Activity and draw normal Android UI. It also limits the amount of text/interaction permitted. This means any custom apps will have to workaround using the very limited APIs available in this library - a full redesign will be needed.
Perhaps load older version and either use a adb edit or a package disabler to kill updates on stock devices.
OTA updates is the first thing I lock down on a stock Android... once bitten, twice shy.
Any directions what someone which is rooted should do so, never need to update android auto? I have a dedicated phone for android auto in car. I use it only for this. But every now and then, android auto doesn't work and force you to update to last version. (in which last version custom apps doesn't work).
Some suggest use firewall for Google play services and android auto, to cut internet from those. I tried it but I'm not sure it's working..
sosimple said:
Any directions what someone which is rooted should do so, never need to update android auto? I have a dedicated phone for android auto in car. I use it only for this. But every now and then, android auto doesn't work and force you to update to last version. (in which last version custom apps doesn't work).
Some suggest use firewall for Google play services and android auto, to cut internet from those. I tried it but I'm not sure it's working..
Click to expand...
Click to collapse
You have to ID what are the offending update app/UID(s).
Google play Services can be temporarily disabled but it has dependencies like Gmail and certain 3rd party apps. The update app(s) may also be dependencies of this service.
Not a practical solution.
Each case is unique. Sometimes it's a force update to an app like in my Samsung's case, Wearables. The update screwed my Buds+ sound proper. Wearables checks for updates everytime it's used.
Solution: uninstalled new version, install older previous backup copy and use Karma Firewall* to ID the app's and/or UID when it connected to the internet.
Repeat above process as when it connected it again updated Except the second time around I firewall blocked Wearables (there are actually 2 that needed to be blocked) internet access.
Took close to an hour to troubleshoot, quit irritating.
Updates, destroyer of worlds
Yes, well... play with it
*Karma's valuable logging feature is blocked on Android 10 and higher. You can still ferret out the offending app/UIDs but it's harder
Actually app are working correctly on android 9\10\11 installed using aaad, kingInstaller or aaease. Unfortunately this error is showed on android 12 devices and can't find a workaround for now
fcaronte said:
Actually app are working correctly on android 9\10\11 installed using aaad, kingInstaller or aaease. Unfortunately this error is showed on android 12 devices and can't find a workaround for now
Click to expand...
Click to collapse
is Android Auto not working on Android 12 ?
Ze2ro said:
is Android Auto not working on Android 12 ?
Click to expand...
Click to collapse
As now on android 12 will work only with version 6.9xxxx44 but Google is start showing a notification to update, you can avoid it for now but I don't know how lot will work this trick. The other solutions is working with new version but is really annoying and practically you need to clear data of android apps every time you want to connect to the car and use custom app
Guys, I've a rooted Moto Z2 force, I'm plannig to use it as an android auto device only. AA is not available in the play store, but I can sidelode any version (I've downloaded the 7.2.62).
I'm tried a couple of tools, AA Tweaker, AA installer, etc, but so far only the cartube application is showing in the car screen (but e.g. fermata auto is not)
I'm planning to use the some official AA applications
- spotify, gmaps, waze, abetterrouteplanner
and would like to have
-youtube, netflix and maybe carscanner on the car screen (in motion as well for the passengers)
Please share you working setup, which tools and which versions (including android auto) are you using with android 9 - or point me to a thread where it is already discussed
Hi.
I have a non root samsung note 9(android 9) with wireless AA set up to aftermarket smart module connected to OEM headunit in my peugeot. Uninstalled AA. Installed screen2auto with AA Ease. Downloaded and installed AA 6.6xxxx version. Activated developer options and selected download from unknown sources. Playstore forced update on my phone to latest version 7.1xxxx but kept original settings and third party apps. Enabled wireless projections on settings and this works quite well provided bluetooth pairing. So can use voice control to for maps, music apps and receive and send messages.
Jinkue said:
Hi.
I have a non root samsung note 9(android 9) with wireless AA set up to aftermarket smart module connected to OEM headunit in my peugeot. Uninstalled AA. Installed screen2auto with AA Ease. Downloaded and installed AA 6.6xxxx version. Activated developer options and selected download from unknown sources. Playstore forced update on my phone to latest version 7.1xxxx but kept original settings and third party apps. Enabled wireless projections on settings and this works quite well provided bluetooth pairing. So can use voice control to for maps, music apps and receive and send messages.
Click to expand...
Click to collapse
Thank you very much, the android version was the problem I've installed AA version 6.9.613744 (instead of the latest 7.*) and everything started working instantly.
Sorry to bring this topic up again, the solution works for me for a few days, than AA is not showing the extra apps anymore. If I uninstall and install android auto again, it works again for a few days. I have no idea why, is there a blacklist AA downloads?
uzi74 said:
Sorry to bring this topic up again, the solution works for me for a few days, than AA is not showing the extra apps anymore. If I uninstall and install android auto again, it works again for a few days. I have no idea why, is there a blacklist AA downloads?
Click to expand...
Click to collapse
My samsung note 9 is non root. I installed as described above and still have apps on galaxy note 8(android 9) and note 9 ( recently updated to android 10). You can try clearing cache of AA. But you should read through screen2auto rooted thread as you will probably find solution and/or somebody will offer good solution.
uzi74 said:
Sorry to bring this topic up again, the solution works for me for a few days, than AA is not showing the extra apps anymore. If I uninstall and install android auto again, it works again for a few days. I have no idea why, is there a blacklist AA downloads? I have attached screenshot of my note 9 with AA 7.1xxxxxx
Click to expand...
Click to collapse
Yes, Google blocked again all 3rd party apps with Android Auto 7.1.
With 7.1 I have the 3rd party apps for about 2 minutes. If I don't start Android Auto in this time, I have to clear data and cache of Google Play Services and Android Auto and do all the setup again. That means I have to do this before every car ride.