If you are trying to get Fermata Auto working on Android 16, you may find that installing the app alone is not enough.
Android 16 has additional restrictions that can affect how sideloaded apps work with Android Auto. Depending on your phone and Android Auto version, you may need to enable Android Auto developer settings, allow installation from unknown sources, install Fermata Auto with the Fermata Auto App Installer, enable a restricted permission, and use an ADB command.
The good news is that a working setup does not necessarily require root.
This guide explains the main steps and what to check if Fermata Auto isn't appearing or working correctly with Android Auto.
What Do You Need for Fermata Auto on Android 16?
- Before starting, you will need:
- An Android phone running Android 16
- Android Auto installed on your phone
- Android Auto developer settings enabled
- The option to install unknown apps enabled where required
- Fermata Auto
- Fermata Auto App Installer
- A computer with ADB installed
- USB debugging enabled on your phone
- The required Fermata Auto restricted permission
- The Fermata Auto ADB command for the `PROJECT_MEDIA` permission
You may not need root for this method.
However, Android 16 is not identical on every phone. The exact menus and behavior can depend on your phone manufacturer, Android build, Android Auto version, and Fermata Auto version.
Does Fermata Auto Work on Android 16?
Yes, there are Android 16 setups where Fermata Auto works.
The Fermata project has documented methods involving ADB and the `PROJECT_MEDIA` app operation, and users have also reported using Fermata Auto successfully on Android 16 devices.
For example, Android 16 users have reported using Fermata Auto on devices such as the Pixel series and Samsung phones. However, the experience is not the same on every device. Some Android 16 users have reported problems with Fermata Auto appearing in the Android Auto launcher or with mirroring features.
If Fermata Auto doesn't work immediately after installation, there are several settings worth checking.
Step 1: Enable Android Auto Developer Settings
Start by opening the Android Auto settings on your phone
- You need to enable Developer Settings in Android Auto before continuing.
- The developer settings provide additional options that can be useful when testing apps such as Fermata Auto.
- The location of these settings can change between Android Auto versions, so the menu may look slightly different on your phone.
- After developer settings are enabled, look for the option that allows apps from unknown sources.
Enable Unknown Sources
Android Auto can restrict which apps are allowed to appear in its interface.
If your Android Auto version provides an Unknown sources option in developer settings, enable it before continuing.
This is important when you are installing Fermata Auto outside the normal Google Play installation process.
Step 2: Allow Installation From Unknown Sources
- Android also has its own security setting for installing apps from outside Google Play.
- If you are using the Fermata Auto App Installer, Android may ask you to allow the installer to install applications.
- Go to your Android settings and find the Install unknown apps option.
- Allow the required permission for the installer you are using.
- The exact location can vary between phones. On some Android devices, you can find it under:
- Settings → Apps → Special app access → Install unknown apps
- Only enable this permission for the installer you intend to use.
Step 3: Install Fermata Auto With Fermata Auto App Installer
Once the required Android Auto and installation settings are ready, install Fermata Auto using the Fermata Auto App Installer.
This is an important part of the setup because simply downloading the Fermata Auto APK does not always give you the complete configuration needed for Android Auto.
Follow the installation process provided by the installer and make sure Fermata Auto is installed correctly.
You do not necessarily need root for this setup.
After installation, open Fermata Auto once and check that the app starts correctly on your phone.
Do not worry if Android Auto is not working yet. There are still permission settings that need to be checked.
Step 4: Enable Fermata Auto Restricted Permissions
- This is one of the steps that can easily be missed on Android 16.
- After installing Fermata Auto, open your phone's Android settings and go to:
- Settings → Apps → Fermata Auto
- Then tap the three-dot menu in the top-right corner.
- Look for an option related to restricted permissions.
Android can restrict certain permissions for apps installed through alternative methods. Because of this, Fermata Auto may install successfully but still not have access to everything it needs.
Enable the required permission when Android provides the option.
The exact permission list can vary depending on the Android version and Fermata Auto build, so do not assume that every Android 16 phone will show exactly the same options.
Step 5: Enable USB Debugging
The next part uses ADB, which stands for Android Debug Bridge.
ADB allows you to send commands from a computer to your Android phone.
First, enable Android's developer options if you have not already done so.
Then enable:
- USB debugging
- Connect your phone to your computer with a USB cable.
When Android asks whether you want to allow USB debugging from the computer, approve the connection.
You can then check that ADB can communicate with your phone.
Step 6: Run the Fermata Auto ADB Command
The Fermata project has documented an ADB command that allows Fermata Auto to use the `PROJECT_MEDIA` app operation.
This permission is related to allowing the app to capture the device's screen and audio. The Fermata project's documentation specifically describes this command as a way to allow screen/audio capture.
The command is:
```bash
adb shell appops set me.aap.fermata.auto.dear.google.why PROJECT_MEDIA allow
```
Run the command from a terminal or Command Prompt while your phone is connected through ADB.
If the command completes successfully, the `PROJECT_MEDIA` permission should be allowed for the Fermata Auto package.
Important: The command should be treated as part of the Fermata Auto setup rather than a general Android command.
If it produces a permission or security error, check that:
- USB debugging is enabled
- The computer is authorized on the phone
- ADB can see the device
- The required Android Auto developer settings are enabled
- Fermata Auto is installed correctly
- The required restricted permissions have already been enabled
The Fermata project has also documented that permission monitoring can affect whether this type of ADB command succeeds on some Android versions.
Step 7: Connect Android Auto and Test Fermata Auto
After completing the installation and permission steps, connect your phone to Android Auto.
Check the Android Auto launcher and see whether **Fermata Auto** is available.
If it appears, open it and test the features you need.
If it does not appear, do not immediately reinstall everything.
Android 16 has introduced additional restrictions around how apps installed outside Google Play are recognized by Android Auto. The Fermata project has specifically discussed the requirement for apps to be installed from Google Play for normal Android Auto availability, along with alternative approaches for some setups.
This means that installation and launcher visibility can be separate problems.
Why Is Fermata Auto More Difficult on Android 16?
The main reason is that several Android and Android Auto restrictions can affect sideloaded applications.
Fermata Auto is not simply a normal media player when it is being used with Android Auto. Some of its functionality involves Android Auto integration, screen projection, media access, and additional permissions.
Android 16 can therefore make older Fermata Auto installation methods behave differently.
This is why you may see situations where:
- Fermata Auto is installed on the phone but does not appear in Android Auto
- Fermata Auto opens on the phone but does not work correctly through Android Auto
- A required permission is shown as restricted
- The app requires an additional ADB configuration
- The same Fermata Auto version works on one Android phone but not another
These differences have also appeared in user reports and Fermata project discussions.
Does Fermata Auto on Android 16 Need Root?
Not necessarily.
The Fermata project has documented an ADB-based method that does not require root for the `PROJECT_MEDIA` permission.
However, not every Android 16 problem can be solved with the same method.
For example, if Android Auto is refusing to recognize a sideloaded application, that can be a separate issue from the screen-capture permission.
Some alternative Android 16 solutions do require root, while other approaches use additional hardware. The correct method depends on what exactly is preventing Fermata Auto from working on your phone.
So it is better to identify the specific problem before assuming that root is required.
Fermata Auto Android 16 Setup Checklist
Before troubleshooting, go through this checklist:
- Android 16 is installed
- Android Auto is installed and working
- Android Auto developer settings are enabled
- Unknown sources are enabled where required
- Installation from unknown apps is allowed for the required installer
- Fermata Auto App Installer has been used
- Fermata Auto opens correctly on the phone
- Fermata Auto restricted permissions have been enabled
- Developer options are enabled
- USB debugging is enabled
- ADB recognizes the phone
- The `PROJECT_MEDIA` ADB command has been executed
- Android Auto has been restarted
- The phone has been reconnected to the car
If you have completed these steps and Fermata Auto still does not appear, the problem may be related to Android Auto's app installation or launcher restrictions rather than Fermata's media permission.
Fermata Auto Not Showing in Android Auto on Android 16
One of the most common problems reported by Android 16 users is that Fermata Auto is installed on the phone but does not appear in the Android Auto launcher.
This can happen because Android Auto checks how applications are installed and whether they meet its requirements.
The Fermata project has stated that Android Auto normally does not allow apps installed outside Google Play to appear on real head units.
That is why simply installing the Fermata APK may not always be enough.
If this happens, first check:
- Android Auto developer settings
- Unknown sources
- Fermata Auto installation method
- Fermata Auto restricted permissions
- Your Android Auto version
- Your Fermata Auto version
- Whether the app appears under Android Auto's launcher customization
Android 16 behavior can change as Google updates Android Auto, so an older guide may not work the same way today.
Fermata Auto Android 16: What Actually Matters?
The Android 16 setup can look complicated, but the basic idea is simple.
You need to prepare Android Auto, install Fermata Auto correctly, give the app the required permissions, and then configure the media permission through ADB.
The process can be summarized like this:
Enable Android Auto Developer Settings
↓
Allow Unknown Sources
↓
Install Fermata Auto with Fermata Auto App Installer
↓
Enable Fermata Auto Restricted Permissions
↓
Enable USB Debugging
↓
Run the PROJECT_MEDIA ADB Command
↓
Restart Android Auto
↓
Connect and Test Fermata Auto
This is the main process to check before looking for more complicated solutions.
Getting Fermata Auto working on Android 16 can require more steps than it did on older Android versions.
The important thing is not to treat the APK installation as the entire setup. Android Auto developer settings, installation permissions, Fermata Auto's restricted permissions, and the `PROJECT_MEDIA` ADB permission can all matter.
The Fermata project itself documents the ADB method:
adb shell appops set me.aap.fermata.auto.dear.google.why PROJECT_MEDIA allow
At the same time, Android 16 behavior can vary between phones and Android Auto versions. Some users may still encounter launcher or installation-source restrictions even after completing the permission setup.
If your Fermata Auto installation works on the phone but does not appear in Android Auto, focus on the Android Auto installation-source and launcher restrictions rather than repeatedly running the same ADB command.
For the most reliable results, always check the current Fermata project instructions for your Android and Fermata Auto versions before applying an older workaround.


0 Comments