I want to propose a project that anyone can contribute to that will help bring near official quality Google apps to the windows phone. Any developer can contribute as they will be open sourced...
I would like all the apps to be built using the new universal code methods provided by the latest visual studio update so that the apps may be ported for windows rt.
Would anyone else be interested in this?
I currently have a Google Music app out (and also undergoing a full redesign of it at the moment), but I'm not open-sourcing that unfortunately.
Is there a hack or work around for rooted users to use unauthorized android auto apps that are not live in the Play store? For example I am working on one that will read my emails. I have some of it working in the emulator but I want to also try it out in my vehicle. I found this on another forum:
"Because of the UX/Safety concerns, you HAVE to be live on the Play Store - aka go through review (which is a new thing for Android) before testing in-car. However, this doesn't mean that you have to be public - you can publish to the Alpha or Beta channel, so only you and an optional controlled list of people can access it."
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
Hello. I was wondering if phone applications such as Line2, textPlus, TextNow, etc will be able to make modifications to their programs to have an alternative Phone dialer in Android Auto or will Google first have to update Android Auto to allow this? Changing the map was added later and not sure if we will have to wait for the Phone Dialer to be updated in Android Auto to allow alternatives. Thank you!
Anyone?
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