microG + Android Auto fully working

Search This thread

BIG_J_06

Member
Jan 5, 2011
6
2
Sad mine don't... (TWRP for Fairphone 4). Do you think it's better to disable encryption and wipe or wait for a new TWRP recovery ?
 

Rikj000

Senior Member
May 4, 2016
86
132
github.com
OnePlus One
OnePlus 2
Sad mine don't... (TWRP for Fairphone 4). Do you think it's better to disable encryption and wipe or wait for a new TWRP recovery ?
That's a decision you'll need to make for your own.

No encryption is a big security risk,
if someone would be able to get their hands on your phone, they would be able to read out the data.

But are you a high profile target, at risk of someone messing w your phone?

Chances are unlikely.
 

Third Position

New member
Apr 30, 2022
3
0
For some reason I can't get the Chuppito mod of Waze to work no matter what I do. AA4MC 0.6.1, AA AIO Tweaker, installed Waze with King Installer (although I get app installed from King Installer in settings>apps>app details in store).

In AA I've enabled application mode developer and unknown sources. Waze is present in the launcher (along with Screen2Auto which seems to work) but when I try to open Waze it fails to launch and instead I get an error saying I need to update to a newer version of Android Auto, despite being on the latest update.

Has anyone come across this? I had it working at some point and now can't get it going, super annoying so any assistance would be much appreciated.
 

Pangwalla

New member
There was an AA update about a week or so ago, and now some of the apps that had been present because of this mod are now gone (OsmAnd for example)
For some reason I can't get the Chuppito mod of Waze to work no matter what I do. AA4MC 0.6.1, AA AIO Tweaker, installed Waze with King Installer (although I get app installed from King Installer in settings>apps>app details in store).

In AA I've enabled application mode developer and unknown sources. Waze is present in the launcher (along with Screen2Auto which seems to work) but when I try to open Waze it fails to launch and instead I get an error saying I need to update to a newer version of Android Auto, despite being on the latest update.

Has anyone come across this? I had it working at some point and now can't get it going, super annoying so any assistance would be much appreciated.
 

renega

Member
Feb 24, 2007
10
0
"activate failed because no wireless projection" briefly appears in my Eyeride HUD. BT then wifi connection via AA is made, AA says to use the device, the specific app to control the HUD connects and works but no AA launch interface in the HUD, only the HUD boot logo.
xiaomi pad 5 tablet with arrowOS 13.1 routed, microg and aa4mg AA last versions; all install options enabled; all permissions enables on AA, migrog
 

cakewalking

New member
Jun 8, 2023
2
0
If there is anyone who can remotely install CalyxOS and the MicroG Android Auto from this thread on a virgin pixel 7,

please DM me your price. Thanks
 

RGAGA

New member
Feb 18, 2018
4
0
So it works, required all network permissions including mobile data, and a device reset before working. Thanks
Discovered your module this week and work like a charm !
As the others, I have only been able to use wireless AA by reactiving all network permissions. Maybe it should be precise on the github tutorial that the deactivation is optional/only for privacy issue (?) and needed for wireless AA ?

Anyway, thanks a lot your work !
 

android666

Senior Member
Jun 19, 2010
101
19
Any idea, why I do not see navigation softwares on the car-screen, also I do not see any navigation software (sygic,mapy.ca,Mapfactor,...) in AA "Customize launcher" ? I installed AAv9
Remaining useless icons are there visible (also on car screen), like VLC, Poweramp...

edit: after several restart it works now. no clue what it was. This is the best I've got In my de-googled phone... thanks got, experts and gurus still do exists
 
Last edited:

blumentopf75

Member
Apr 28, 2010
49
15
Hello everybody, xda-developers.com
I followed the instructions in #1 .
Wiped my Phone completely,
installed LOS 18 for my phone (TWRP)
installed installed the nikgapps AA addon for Android 11 with the script modification (which ist LOS 18)(TWRP))
Booted into system and installed the microG CoreGMS apk (via FDroid).
I can configure MicroG, but no hint, that there is AA installed.
Also installed the nikgapps AA addon for Android 11 again with TWRP after mircoG CoreGMS apk.
Still no luck.
When I USB-plug into my car, I get the message "Android Open Automotive Protocol - no compatible App installed"

How can I verify, that AA is really installed?
Do I have to configure something in MicroG settings (adding a Google account or something else, I did nothing with it, only installed it)?

Thank you
 

blumentopf75

Member
Apr 28, 2010
49
15
Hello everybody, xda-developers.com
I followed the instructions in #1 .
Wiped my Phone completely,
installed LOS 18 for my phone (TWRP)
installed installed the nikgapps AA addon for Android 11 with the script modification (which ist LOS 18)(TWRP))
Booted into system and installed the microG CoreGMS apk (via FDroid).
I can configure MicroG, but no hint, that there is AA installed.
Also installed the nikgapps AA addon for Android 11 again with TWRP after mircoG CoreGMS apk.
Still no luck.
When I USB-plug into my car, I get the message "Android Open Automotive Protocol - no compatible App installed"

How can I verify, that AA is really installed?
Do I have to configure something in MicroG settings (adding a Google account or something else, I did nothing with it, only installed it)?

Thank you
Maybe, I now know, whats the problem with the AndroidAuto addon from nikgapps. I decided to create my own nikGapps package. You can do this by forking the GitHub repo and modify the config-file. The name of the file was ...arm64...
Since I've got an older phone I ever had to install ARMv7 packages. At the moment I'm a bit confused, since the processor is an Exynos 7580, which should be a 64bit. But arm64 packages never worked.
Maybe I would find a AA zip for ARMv7...
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    This is how you can use Android Auto with microG and connect your phone with your car.

    Prerequisites:
    Android 10+
    Newest microG core (https://github.com/microg/GmsCore/releases)
    A custom recovery to flash a zip file

    Let's begin:

    For Android Auto we'll use nikgapps Android Auto add-on and modify one file in the flashable zip.
    Download nikgapps Android Auto add-on here: https://sourceforge.net/projects/nikgapps/files/Releases/
    Dpending on your Android version, choose the correct Addons-(Q/R) folder, then, you want to download "NikGapps-Addon-10/11-AndroidAuto-date-signed.zip"

    Now open the downloaded package and open the folder "common". In there you'll find "nikgapps_functions.sh". This file needs to be modified as follows:

    Open this file and search for "is_on_top_of_nikgapps"

    Remove the following (this code checks if you have installed nikgapps core already, but since we don't want to install that, it must be removed):
    Code:
    is_on_top_of_nikgapps() {
      nikgapps_present=false
      # shellcheck disable=SC2143
      if [ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/etc/sysconfig/*.xml)" ] ||
            [ "$(grep 'allow-in-power-save package=\"com.mgoogle.android.gms\"' "$system"/product/etc/sysconfig/*.xml)" ]; then
        nikgapps_present=true
      fi
      addToLog "- Is on top of NikGapps: $nikgapps_present"
      if [ "$nikgapps_present" != "true" ]; then
        abort "This Addon can only be flashed on top of NikGapps"
      fi
    }

    It should look something like this now:

    Code:
    .....
        else
          addToLog "- Failed to write $install_location"
          abort "Installation Failed! Looks like Storage space is full!"
        fi
      fi
    }
    
    # Check if the partition is mounted
    .....

    That's it! Now you can flash this zip with your recovery and you'll have fully working Android Auto!
    6
    I just created a Magisk Module that provides Android Auto for devices running microG on Android 11. I've made this mainly for myself, but wanted to share:

    Basically just install aa4mg-v0.1.zip as Magisk Module, reboot, optionally upgrade in Aurora Store, profit.

    But please see readme on github: https://github.com/sn-00-x/aa4mg
    5
    I've merged @byReqz's pull request (thanks for the great contribution!) and released a new version: https://github.com/sn-00-x/aa4mg/releases/tag/v0.3-a13
    5
    Til now I didn't hear of anyone get it working on A13.
    I did it. You need a A13 LineageOS-20.0 rom with signature spoofing patch. Here is my patch https://github.com/braga2/sigspoof
    Apply that patch and build as described in official instruction https://wiki.lineageos.org/devices/barbet/build instead of barbet use your device codename. I built for my bluejay.
    Burn the ROM.

    Install Google APP Stub. I built it from sources from here https://git.sr.ht/~dylanger/Google-App-Stub
    Install Mozilla UnifiedNLP Backend from F-droid.

    Then you have to install latest MicroG GmsCore and FakeStore from official github https://github.com/microg as a regular apps with forceQueryable flag enabled. I used such commands:
    adb install --force-queryable FakeStore-v0.1.0.apk
    adb install --force-queryable com.google.android.gms-223616052.apk
    Enable signature spoofing for both these apps and other required permissions.
    Enable Mozilla UnifiedNLP (Mozilla Location Service) in MicroG.
    Of course you can disable internet access for this app and for MicroG as well.

    Then reboot to LIneage Recovery and install 'android auto stub'. I used latest NikGapps-Addon-13-AndroidAuto from official sourceforge https://sourceforge.net/projects/ni...n-13-AndroidAuto-20220908-signed.zip/download
    I installed it manually without using scripts. Mounted system in recovery, then mounted /product in adb and put these 3 files using 'adb push': AndroidAutoOverlay.apk into /product/overlay, AndroidAutoStubPrebuilt.apk into /product/priv-app/AndroidAutoStubPrebuilt and com.google.android.projection.gearhead.xml into /product/etc/permissions
    Maintain correct permissions for files root:rw-r-r and for AndroidAutoStubPrebuilt dir root:rwx-rx-rx

    Also important! grep gearhed /product/etc/permissions/* and remove or comment all xml permission tags except our installed file(com.google.android.projection.gearhead.xml). I found it in privapp-permissions-google-p-lineage.xml and commented whole corresponding xml tag so it looks like this:
    Code:
        <!--privapp-permissions package="com.google.android.projection.gearhead">
            <permission name="android.permission.ACTIVITY_EMBEDDING"/>
            <permission name="android.permission.BLUETOOTH_PRIVILEGED"/>
            <permission name="android.permission.CALL_PRIVILEGED"/>
            <permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
            <permission name="android.permission.COMPANION_APPROVE_WIFI_CONNECTIONS"/>
            <permission name="android.permission.CONTROL_INCALL_EXPERIENCE"/>
            <permission name="android.permission.DUMP"/>
            <permission name="android.permission.ENTER_CAR_MODE_PRIORITIZED"/>
            <permission name="android.permission.LOCAL_MAC_ADDRESS"/>
            <permission name="android.permission.LOCATION_HARDWARE"/>
            <permission name="android.permission.MANAGE_USB"/>
            <permission name="android.permission.MODIFY_AUDIO_ROUTING"/>
            <permission name="android.permission.MODIFY_DAY_NIGHT_MODE"/>
            <permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
            <permission name="android.permission.REQUEST_COMPANION_SELF_MANAGED"/>
            <permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND"/>
            <permission name="android.permission.UPDATE_APP_OPS_STATS"/>
        </privapp-permissions-->

    Well. Reboot system now and install latest Android Auto, Google Maps, Google TTS from Aurora Store (or any other source).
    Enable location permission for GMaps and all permissions for Android Auto. Internet access for Android Auto can be disabled.
    Disable USB-debug in Android developer menu.
    Reboot the phone.
    Cross your fingers and try to connect to head-unit.
    When AA asks for maps location permission just hit Cancel.
    If it does not connect - disconnect USB cable and clear storage for GMaps and AA and try again. It should work!

    ps. Google Translate online does not work. It throws https 403 forbidden error but without MicroG it works fine.
    Also GMaps works only english US language. I could not switch it to any other language even if phone language was ok. I guess the reason is the same 403 error, google bans the requests to their services by some headers. I plan to reverse-engineer and fix this ;)
    4
    I have got in running finally on LOS19+microG, including OSMAnd and other Navi-apps and Screen2Auto. It was a long way to go. I try to summerize it:

    You can start here:

    I want to do a shortcut and put a recent AA into this package. (84624324). It is not as easy just to change the app, you also have to extract the libs from app and change that, but also change the permission.xml. You get the required data out of Manifest, decode the app with apktool
    Installation as it is described in the link.

    What drives me nuts was the thing about permission. Starting it in the car I get short after start a green screen with request to set location permission to Maps (although it was given - and it even shows my position). Not sure but maybe it was some location setting in microG that has to be called first.

    The next thing is to get other Navis than Maps running. It sees it needs to be installed from Playstore, but I don't have it on my device. But this can be faked.
    You have to install a few things: LsPosed, XPrivacyLua and its Pro-App.
    Installing is a bit of a pain, you have to enable XprivacyLua in LsPosed, check AA there (you have to unhide system apps) AND in XPrivacyLua
    It provides Hooks for 2 different AA versions. These have to be imported by the Pro Companion app and again activated in XprivacyLua.
    To figure out the values that has to be changed in the hook check the AA.apk with
    java -jar Bytecode-Viewer-2.11.2.jar and look for the string "isPackageAllowed3p". All credits go to "UnlockAA" who not only figured that out but alos helped me a lot with that.

    Screen2Auto works without root. But I need to enable the Alternative Touch method to get feedback from cars screen.
    With this you can mirror your phones screen, so no need for an app that is ready for AA.


    Although the orginal work has done by others (linked) I spend some hours to figure things out and get it working. Hope that will help others too.