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.
Related
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.
Like the title says. Google must have implemented something in the new Android auto update, the one with the new UI. I've been using AA Mirror to cast my phone's screen to my 2016 Sierra for a while now with no issues. But just got the latest update with the new UI. When you use the AA Unlock .apk to unlock the feature it disabled the ability to even use Android auto on your vehicles head unit. If you already have Android Auto open on your radio you will lose the ability to operate android auto from the screen. The default android auto home screen will still remain on your radio but none of the touch functions of the screen will work. If you don't have it open before you use the AA Unlock .apk to use that feature, then Everytime you click on on the Android auto icon on your radio it ignores android auto completely on the radio but opens the phone version on your phone.
This sucks. I like having FOX news in the mornings on the ride to work.
Uhm, I don't know if you're aware of AA Phenotype Patcher. AA Unlock stopped working a while ago. You should use Phenotype Patcher. It works just fine for unlocking 3rd party apps. I'm actually impressed on how much time you had apps unlocked with AA Unlock, actually, cause after a while apps would just disappear.
I would also re-install Android Auto and wipe cache of Google Play Services before proceeding.
Same issue. Just tried AA Mirror and AA Phenotype Patcher yesterday (latest versions). No way to have them work...
:/
I am using as mirror and pheontype patcher and the sept 3 android auto everything works just fine but did work better a bit before the head unit got updated not sure how to roll back a head unit. My truck is a 2019 Chevy zr2 Colorado.
Installed custom Android Q ROM and Android Auto stopped working. Looking around learned Android 10 muggles around Assistant Driving mode and some promised AA for Phone Screen etc but common ground is no solution for running AA on Q I found.
Digging more, found out working solution:
1. Grab latest apks of AA, Play Services and Google apps (apkmirror or so). Pay attention to look for latest version designated specifically for Android 10 if there are such!!! (otherwise get whatever is latest)
2. Install in following order: Play Services, Google and AA latest.
3. Move AA to system apps. Use Titanium or manually
http://www.friendfactor.org/install-user-apps-as-system-apps-on-android/
4. Reboot to recovery, clear cache & davlink.
5. Reboot to system
AA is installed but not visible in launcher. Check it is installed by going to settings - apps and look for it. On bottom of its details, there is option for more settings in application - there you can get int AA settings and activate Dev mode and other options.
So, AA is there but you cannot launch it as normal app.
YET...
After plugging phone to car, AA started automatically and now works flawlessly.
BTW in Dev options now is possible to activate option I'm main settings to use WiFi connection. Tried and working with my Audi
Tested also CarStream 2.0.4 and it works
I've tried it multiple times, with reinstall and reconfiguration both the smartphone and the car. It works for some time and is back to the same behaviour after that.
Was it rock stable for you?
m0d3rn said:
I've tried it multiple times, with reinstall and reconfiguration both the smartphone and the car. It works for some time and is back to the same behaviour after that.
Was it rock stable for you?
Click to expand...
Click to collapse
Yes it is stable for me. Today I also updated with latest Open gapps and it works Ok. I use it for a half an hour commute to work.
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
Hi there, i have installed the screen2auto through the AAAD app, i did the right settings (i think so) and gave the permissions on Xiaomi Note 8 Pro (no root) but when i run the screen2auto 3.6.3 via Android auto i cannot see anything. If for example choose the instagram app or gmail app i can see only a black screen. Is there something i can do to resolve that issue? Or a good tutorial to watch and setup the right settings step by step?
Best regards.
josecarlosss said:
Hi there, i have installed the screen2auto through the AAAD app, i did the right settings (i think so) and gave the permissions on Xiaomi Note 8 Pro (no root) but when i run the screen2auto 3.6.3 via Android auto i cannot see anything. If for example choose the instagram app or gmail app i can see only a black screen. Is there something i can do to resolve that issue? Or a good tutorial to watch and setup the right settings step by step?
Best regards.
Click to expand...
Click to collapse
Hi.
I have non rooted Samsung note 9 and using s2a 3.6.2 /wireless Android Auto connection in my car. I have been using it for the last 5 months and it works very well and the s2a app has not dropped off my AA apps. I started by uninstalling AA and installing older version of AA 6.6.xxx . Playstore forced update to newer version of AA. Under settings menu tap the 'Version' 10 times to enter developer settings. Under these setting select(tick) 'download from unknown sources', 'developer mode' and 'wireless projection'.
I know there is a newer version of S2A but I am using 3.6.2 version and will not upgrade because 3.6.3 may not work on my phone. Download S2A 3.6.2 and AA Ease page 94 of this thread https://forum.xda-developers.com/t/...rroring-only-for-root-devices.4062787/page-94.
Install S2A with AA Ease and this should install in Android Auto and S2A should show in app list or as one of apps under AA Version.
This has worked for me and not had to reinstall it on a non rooted samsung note 9. I can watch youtube, bbc iplayer but only get sound on netflix because of DRM protection. Also try AAAD because I paid for pro version and Carstream and Fermata Auto work on my phone/car head unit.