Repository navigation
Replies: 2 comments
|
SUCCESS: Fermata Auto 2.0.2 on Samsung Galaxy S26 / Android Auto 18.0 via KingInstaller Confirmed working, including successful YouTube video playback on the vehicle display. Configuration:
Original problem: I initially installed Fermata Auto 2.0.1 using AAAD. Fermata Auto worked on the phone but did not appear in Android Auto's Customize Launcher. Fermata Media appeared, but Fermata Auto was missing. Solution:
Result: FULLY WORKING. Fermata Auto appears in Android Auto, launches successfully, and plays YouTube video on the car display. Hope this helps others encountering the same problem with newer Samsung phones and Android Auto versions! |
|
A related finding for MEDIA apps on Android Auto 18.0.664264, which may be what's behind some of the "worked yesterday, gone today" reports: step 9 (the "Unknown sources" fallback) is racy. Environment. Android Auto 18.0.664264-release, Android 16 (moto g power 2026), two different cars, wired and wireless. A sideloaded media app (MediaBrowserService / Media3 MediaLibraryService), "Unknown sources" on, plain adb install. First seen around Android Auto 17.8 (mid-October). Symptom. In roughly 3 of 4 projection sessions the app is missing from the launcher and rail for the whole session. Reconnecting sometimes brings it back. Nothing on the app side differs between good and bad sessions (process alive or not, service bound or not). Logcat, bad session: Good session (same car process, 14 minutes later): the same Cause, from the 18.0.664264 dex (obfuscated names are for that build only; the validator is
So for MEDIA apps the result of step 9 depends on thread timing at projection start, not on anything the app or the user did. I counted 586 of those This is read from the dex and matches the log lines; I haven't reproduced the race on demand. I'm also reporting it to Google. |
Uh oh!
There was an error while loading. Please reload this page.
TL;DR: Android Auto only lists a sideloaded Fermata Auto or Mirror if it's recorded as installed by the Play Store, or if the head unit is a developer head unit (e.g. AAWireless's developer mode). "Unknown sources" doesn't cover them. Without a dongle or root, install Fermata with KingInstaller: step by step.
Android Auto shows a sideloaded projection app (Fermata Auto, Fermata Mirror, any video or mirroring app) only if one of these is true: its recorded installer is the Play Store (or Play vouches for it), the head unit identifies as a Google developer head unit, or AA is patched on a rooted phone. The "Unknown sources" developer setting does not cover projection apps at all. This is what Android Auto 17.7's own code does; the details, log lines and evidence are below so we can stop guessing.
In short
Package DENIED; failed all other checks.How Android Auto validates an app
Every app AA considers for the car goes through one validator method (logged under the tag
CAR.VALIDATOR), called with the package and the type being validated. The launcher's list of custom-UI apps is built by querying services with actionandroid.intent.action.MAINand categorycom.google.android.gms.car.category.CATEGORY_PROJECTION_OEM, and each one is validated as type PROJECTION. Fermata Auto'sCarServiceandMirrorServicedeclare that category. Fermata Media Service is a media browser service, validated as MEDIA.The checks run in this order; the first decisive one wins.
Package DENIED; package not foundorPackage DENIED; package is disabled.getInstallSourceInfo(pkg).getInitiatingPackageName(). Only if that iscom.google.android.packageinstallerdoes it usegetInstallingPackageName()instead. (Before Android 11:getInstallerPackageName().)Package DENIED; block listed.res/xml/automotive_app_desc.xmlmust declare<uses name="…"/>for the type being validated, otherwisePackage DENIED; Uses for <TYPE> not defined. This is per type: it hides only the components of that type, not the whole package.Google/Desktop Head Unit,Google/tangorpro [AAR]orPanasonic/Seahawk [AAR], and a Google server-side flag is on. (A debug build of AA connected toGoogle/Emulatoralso qualifies.)Package DENIED; Should not run on HU.PlayGearheadServiceforFinsky.IsValid, which Play sets only when an account on the phone owns the app in its Play library, with a matching signing certificate); or the installer iscom.android.vendingwith a Google-signed Play Store.allow_unknown_sourcesin AA'scarservicepreferences), but only for the types in the table below.Package DENIED; failed all other checks.On my phone (OnePlus 12, Android 16, AA 17.7, "Unknown sources" on), a shell-installed Fermata Auto produced exactly the end of this path:
What works, what doesn't
For Fermata Auto and Mirror (type PROJECTION), these are the only routes the validator leaves open:
What doesn't work, and why:
pm install -i com.android.vending). AA's own comparison uses the initiating installer, which for a shell install is the shell, not the name passed with-i.KingInstaller, explained. It doesn't install the APK itself. It opens the system package installer, naming the Play Store as installer (
EXTRA_INSTALLER_PACKAGE_NAME, plusEXTRA_NOT_UNKNOWN_SOURCE; source: classic, Shizuku). Android then records the package installer as initiator and the Play Store as installer. AA sees the package installer as initiator, so it uses the recorded installer (step 2), and the Play Store passes step 7 without Play being asked anything. Its README says the classic method works only on some devices; the Shizuku method makes the same request with the shell's privileges and works on a wider set. A plainpm install -i com.android.vendingfrom the shell fails, because there the shell itself is the initiator.Why it can work, then stop. Two things in this code can change the result without anything visibly changing. A positive result is cached per package and version, so it sticks until the app is updated or AA's data is cleared; the next validation can then come out differently. And an update installed any other way (for example a plain sideload) replaces the recorded installer, which then fails step 7. Both fit the "worked yesterday, gone today" reports in #773, but I haven't reproduced them.
Fermata-specific notes
Uses for TEMPLATE not definedcomes fromautomotive_app_desc.xmldropping<uses name="template"/>. It only hides the old FS Mirror (a Car App Library service), not the whole package. My earlier #829 read it as a package-wide denial; that was wrong.Step by step with KingInstaller
This is the route that works without a dongle or root. The code above explains why, and it's reported working on a OnePlus 12R with Android 16 in #811, with the Shizuku method. KingInstaller's README is the reference: follow it first and foremost, including its advice to try the classic method first. The Shizuku method works on a wider set of devices. These steps only add what matters for Fermata and Android Auto.
If Fermata Auto is already installed, export its settings (Settings → Export preferences) and uninstall it, so the new install gets a fresh install record.
Install KingInstaller from its GitHub releases.
Install the Fermata Auto APK with KingInstaller, the classic way first, with no switches enabled, as its README says.
Check the install record. KingInstaller's app checker should show Requested by: Package Installer and Installed by: Play Store. Those are exactly the two values Android Auto reads (step 2 of the validation above). Over adb, for the GitHub release build:
should print
installerPackageName=com.android.vendingandinitiatingPackageName=com.google.android.packageinstaller.If the record is wrong, use the Shizuku method, which works on a wider set of devices: install and start Shizuku (KingInstaller recommends Shizuku-Next, which can start without Wi-Fi; standard Shizuku works too), enable KingInstaller's Shizuku Trick switch, grant it Shizuku access, install again, and check again.
Open Android Auto's Customize launcher on the phone (no car needed) and enable Fermata Auto and Fermata Mirror. Android Auto's "Unknown sources" setting isn't needed for this.
Install every Fermata update the same way. An update installed any other way replaces the install record, and Fermata disappears from the car again.
If it still doesn't appear: force-stop Android Auto and open Customize launcher again. On Xiaomi, POCO and Redmi phones, KingInstaller's README says the Shizuku method usually fails and root is needed. With Fermata 2.0.2, the old FS Mirror doesn't appear by design (see the notes above).
Evidence and caveats
Everything above comes from decompiling Android Auto 17.7.666914 (
com.google.android.projection.gearhead) and the Play Store's Gearhead service (from the Play Store on my phone), from KingInstaller's source, and from logs and car tests on a OnePlus 12 (Android 16, OxygenOS) with an AAWireless dongle.jao, methodzPackage DENIED; failed all other checksandUses for %s not definedjao.N(CarInfo)Desktop Head Unit,tangorpro [AAR],Seahawk [AAR]jao.J()allow_unknown_sourcesin thecarservicepreferencesqvaFinsky.IsValidauxx, the binder behindPlayGearheadServicePlayGearheadService %s, app owners emptyandFinsky.IsValidInstallationUtils(classic),ShizukuUtils.installApk(Shizuku)What's verified, and how
Finsky.IsValidchecks: read from the Play Store's code. Only Android Auto and Google Play services may ask, and the answer is yes only when an account on the phone owns the app in its Play library with a matching signing certificate. The installer isn't looked at.What's inferred
Caveats
Related issues: #773, #717, #580, #605, #811, #829.
All reactions