microG + Android Auto fully working

[Rikj000]

That just sounds great!
As @Xurde78 already reported (and I repeatet the test), the King installer doesn't seem to work (in terms of faking the installation source). I used one of the already released Magisk packages that works fine for Maps or VLC, but not for any other navigation app. Installing OSMAnd~ by KingInstaller showed me in Setting/Apps/OSMAnd~/Appstore: Installed by Kinginstaller ...and it is not listed in Launcher. I belive you that it works for you, but why that works for us? Do you have an idea? I am on LOS20 too.

King-Installer v1.2 didn't work for me either on my LineageOS phone,
because we have a different `com.android.packageinstaller` provided by our ROM.

That's why I created King-Installer v1.3, with the "Enable if you use rooted (LineageOS) phone" checkbox.

Question: Do you see in the /settings/apps/xxx/app-shop really: Google Play Store?

Yes I do, you can check the proof I uploaded here, as a comment on my PR

Reading the full manual I see few difference:
* You install stubs and AA BEFORE installing the Magisk-AA-Module.

This is to make it less detectable that you're using modded software, however at the moment it's not a requirement.
(Currently AA will also be happy if you do not have the dependencies installed "as Google Play Store")

* You installed the stubs with King-installer too, but if that doesn't work with OSMand, why it should work with the stubs? Or does it more than fake installation source?

Did you try my v1.3 fork with the "Enable if you use rooted (LineageOS) phone" checkbox?
Also please re-visit the ReadMe, I've added new installation / usage instructions earlier today.

* You used Aurora root installation mode, while I used default (session installation?).

The "Root installer" of Aurora Store is a requirement to "install as Google Play".
I've checked the source code, and for as far as I researched it,
it was the only installation method which spoofed "com.android.vending" during installation.

Before I was using "Aurora Services" as the Aurora Store installation method,
which didn't work either.

 

[starbright_]

That might help others, but unfortunately this solution doesn't bring non-google navi-apps as "OSMAnd" or "here" alive in a LOS+microG environment.

 

[Rikj000]

OsmAnd works correctly on my end.

To switch to my newer fork first:
1. Uninstall current AA updates
2. Uninstall current aa4mg v0.3-a13
3. Reboot

Then follow the instructions in the readme of my KingInstaller fork to install my v1.3 release.

After that follow the instructions in the readme of my aa4mg fork to reinstall AA with my aa4mg v0.4-a13 release.

Then you are ready to install OsmAnd as following:
- Download the latest OsmAnd .apk
- Open KingInstaller
=> Select File
=> OsmAnd .apk
=> Check "Enable if you use rooted (LineageOS phone)"
=> Install as King
=> Grant root permission
=> Wait for text-field with .apk path to clear

That's it, after thatOsmAnd should work.
Not tested in my car yet,
but shows up in launcher + works in head unit emulator.

I did not need additional AA-Tweaker tweaks,
nor did I need to modify the phenotype.db after installing as described above.

 

[Xurde78]

I am going to try
...excited...

 

[Xurde78]

It hasn't worked for me, but I'm getting more and more sure that it's my phone.
I have installed the module and the latest version of Kinginstaller, with the same result, installed apps show up in AA settings but not in AA launcher.
I have tried the repackaged Osmand and S2M applications with the same result.
Apps installed with King seem to be installed from the Fakestore, so it works fine.
With AA AIO TWEAKER I have tried to patch the applications, without result. Although I got the green tick that third-party applications were patched...
The phone was working fine, but I touched something but now it doesn't seem to turn on (but it was because of something I touched, both the module and the application worked without problem) it is an opportunity to do a clean installation of everything and re-approve .....
Question is there any Stub for GPlay .....?

 

[sn00x]

So cool, @Rikj000! I just merged the pull requests and released a new version: aa4mg-v0.4-a13.zip
Thanks!

Edit: Better use aa4mg-v0.4.2-a13.zip, which is basically 0.4 without stubs.

 

[starbright_]

Question is there any Stub for GPlay .....?

Isn't fakestore a kind of stub? At least it is registering with same name (com.android.vending). Whether the name (here Fakestore) is of any meaning for other apps - I don't know.
Summery from me so far. Installation of AA was never as smooth and easy - but the KingInstaller doesn't seem to help (me) for navi-apps as OSMand. I am not aware of any mistakes while the installation, but I can't exclude that. Also I don't have a deeper understanding of how Google controls the navi apps - I just know they treated special for some reason.
So I am curious of feedback from others.

@Rikj000: your Magisk module contains stubs for Google, Maps, Speech. So why to install them before? Can you explain that detail?

@sn00x: does the magisk modules differ in other things than documentation?

 

[Rikj000]

Isn't fakestore a kind of stub? At least it is registering with same name (com.android.vending). Whether the name (here Fakestore) is of any meaning for other apps - I don't know.

On MicroG,
FakeStore = Google Play Store = com.android.vending.

FakeStore is indeed a stub, provided by MicroG itself.

@Rikj000: your Magisk module contains stubs for Google, Maps, Speech. So why to install them before? Can you explain that detail?

You can also install them before/after AA,
the order doesn't matter, as long as they are installed once you are actually gonna use AA.

You can even freeze these dependencies through hail.

@sn00x: does the magisk modules differ in other things than documentation?

Nope, only docs are slightly different to assure the URLs on my fork repo work correctly.

 

[sn00x]

Fakestore is an empty package that mocks the existence of the Google Play Store to the Play Services client. Requires the FAKE_PACKAGE_SIGNATURE patch to be functional.

The main difference of the new release: It now ships with phenotype db, which AA uses to store information about launchable apps. You could try use AA Phenotype patcher (see github and thread) to enable your 3rd party apps.

I didn't test it myself though, cause I'm not even on A13, yet. Hopefully I will find some time soon (new phone is already here, just didn't have time to set it up, yet)

 

[starbright_]

You can also install them before/after AA,
the order doesn't matter, as long as they are installed once you are actually gonna use AA.

My question points to another direction. If the stubs are in magisk-aa module - why there is a need of manually install them? Why not install them in that step automatically (if not already existing). So you will have a choise:
Install the real apps either before magisk-aa or they will be installed as stubs in the magisk-aa module.

 

[Rikj000]

there is a need of manually install them? Why not install them in that step automatically (if not already existing).

aa4mg does not install any stubs.

You have to either:
- Manually install the stubs
- Update the aa4mg module code so it will install the stubs for you automatically.

 

[starbright_]

aa4mg does not install any stubs.

You have to either:
- Manually install the stubs
- Update the aa4mg module code so it will install the stubs for you automatically.

That I understood, that is clear in your very good documentation! But why they are part of the module if they are not used in it? Don't get me wrong - its great to have them all available here, but they should they be outside of it or used. Otherwise some (like me) will ask : why that?
But finally it's no problem, I am just wondering why.

 

[Rikj000]

That I understood, that is clear in your very good documentation! But why they are part of the module if they are not used in it? Don't get me wrong - its great to have them all available here, but they should they be outside of it or used. Otherwise some (like me) will ask : why that?
But finally it's no problem, I am just wondering why.

I did not include them in my pre-release module .zip as they are not required in there.

I think @sn00x added the .apk's in the module either:
- By accident
- For completion (mirror whole repo in .zip)

 

[starbright_]

Got it. But maybe the idea if installing the stubs - only if the real apps are not installed - is not so bad. That will speed up bring up AA even more.

 

[byReqz]

Just released my forks + opened PRs!
They should help with bringing better Anrdoid Auto support on (LineageOS based) MicroG devices.
Enjoy!

Nice. I was trying to rig up an "empty" phenotype DB for myself but it seems like I've been beaten. Is yours just copied from a device running real gms? As a sidenote, having a real phenotype DB also allows you to use https://github.com/shmykelsa/AA-Tweaker/ .

 

[Rikj000]

Nice. I was trying to rig up an "empty" phenotype DB for myself but it seems like I've been beaten. Is yours just copied from a device running real gms? As a sidenote, having a real phenotype DB also allows you to use https://github.com/shmykelsa/AA-Tweaker/ .

Pulled the files from a rooted AVD without Google Account,
the phenotype.db is pre-patched with AA-Tweaker, but can be further modified if desired.

If you're interested,
wrote some more details about the files and my findings about em in this MicroG Github issue:

[ Feature Request ] : Android Auto Support · Issue #897 · microg/GmsCore

Installed : Google App / Google Maps / Android Auto Launched Android Auto Stuck at Android Auto launcher. Below are the logs : 07-21 00:12:25.191 16269 16305 I MicroDetectionWorker: #startMicroDete...

github.com

 

[Rikj000]

OsmAnd works correctly on my end.

To switch to my newer fork first:
1. Uninstall current AA updates
2. Uninstall current aa4mg v0.3-a13
3. Reboot

Then follow the instructions in the readme of my KingInstaller fork to install my v1.3 release.

After that follow the instructions in the readme of my aa4mg fork to reinstall AA with my aa4mg v0.4-a13 release.

Then you are ready to install OsmAnd as following:
- Download the latest OsmAnd .apk
- Open KingInstaller
=> Select File
=> OsmAnd .apk
=> Check "Enable if you use rooted (LineageOS phone)"
=> Install as King
=> Grant root permission
=> Wait for text-field with .apk path to clear

That's it, after that OsmAnd should work.
Not tested in my car yet,
but shows up in launcher + works in head unit emulator.

I did not need additional AA-Tweaker tweaks,
nor did I need to modify the phenotype.db after installing as described above.

Figured out that I've missed a few steps there!

For OsmAnd and some other apps to show up / work correctly, you will also need to:
1. Install LSPosed
2. Install Fermata,
3. Enable the Fermata LSPosed module for AA
4. Reboot

I'll send in a PR with properly updated docs tonight after my work

 

[Xurde78]

Figured out that I've missed a few steps there!

For OsmAnd and some other apps to show up / work correctly, you will also need to:
1. Install LSPosed
2. Install Fermata,
3. Enable the Fermata LSPosed module for AA
4. Reboot

I'll send in a PR with properly updated docs tonight after my work

You've done it
Pocophone F1
A12, CrDroid 8.12
MicroG Core 0.2.27.223616
AA 9.1.631044
Kinginstaller V1.3
Thank you very very much. Rikj000

byReqz starbright_​

Thank you for your contribution and instructions.
It only remains to connect it to the car, but that is a small detail.

 

[starbright_]

Just be aware: If you wipe data/cache of your AA app (to do some kind of restart/refresh) ... some files of the magisk-aa module will be deleted!
That's an unexpected side effect.

 

[Rikj000]

I'll send in a PR with properly updated docs tonight after my work

Published a new minimal Xposed module, which only uses the hooks from Fermata,
to unlock additional third party apps.

You can find the XDA thread for it here:
[Release] Android Auto - Xposed Unlocked (AAXU)

PRs to add it to the docs of aa4mg and KingInstaller have been sent.

Enjoy your fully unlocked AA guys!