Fermata in the paid version. #718
Replies: 8 comments 4 replies
-
|
I don't think it's legal selling playstore links. When Google knows about it, it will probably block all these accounts, and it could even block the app in AA, in this case, it will stop working for all, even for those who use it through AAWireless. |
Beta Was this translation helpful? Give feedback.
-
|
OMG! I just bought this one, this is not fron the dev?? |
Beta Was this translation helpful? Give feedback.
-
|
@huyle0406 No they are not |
Beta Was this translation helpful? Give feedback.
-
|
Android 16 & 2025 Nissan Qashqai - Beta Testing Request for Fermata Auto Hi Andrey, I'm a user from Turkey with a 2025 Nissan Qashqai and a phone running Android 16. My phone is a corporate device, so I cannot root it or use unofficial methods that require system modifications. I want to solve the icon visibility issue using only official software channels. I would like to help you as a Beta Tester for this specific Android 16 / 2025 Nissan setup. Could you please add my email to the Google Play Beta Testing track? My goal is to install Fermata as a "trusted app" directly from the Play Store to see if it bypasses the Android 16 "sideload" restriction on my vehicle's screen. My Email for Play Store: orkun.atis@gmail.com I can provide logs and feedback regarding the performance on this new vehicle system and OS. Thank you for your amazing work. |
Beta Was this translation helpful? Give feedback.
-
|
I do not distribute the app in this way. Sideloading does not require neither root nor any system modifications. But I understand, that it could be restricted on corp devices. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Andrey, thanks for the clarification. I understand that you don't
distribute via Play Store. Since this is a corporate device with Android
16, I will try to install it via *ADB* using the -i com.android.vending
flag to trick the installer source. Do you think this 'installer spoofing'
still works on Android 16 to bypass the AA launcher restriction, or has
Google patched this bypass as well?"
Andrey Pavlenko ***@***.***>, 11 Mar 2026 Çar, 21:57
tarihinde şunu yazdı:
… I do not distribute the app in this way. Sideloading does not require
neither root nor any system modifications. But I understand, that it could
be restricted on corp devices.
—
Reply to this email directly, view it on GitHub
<#718 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B7XZWVSS3IYBNO2HOJKEVLL4QGZH3AVCNFSM6AAAAACV6LZIHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBYG42TQMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
You don't need adb and com.android.vending will not help, just download. Just download the apk to the phone and install. All you need is AAWireless. |
Beta Was this translation helpful? Give feedback.
-
|
"Hi Andrey,
Thank you for your quick response.
I understand your point about AAWireless, but I have a very specific
observation that I’d like to share:
I tested my wife’s phone, which is running Android 13, in the exact same
2025 Nissan Qashqai using the same version of Fermata Auto. It worked
perfectly, including YouTube and the Web Browser, even while the car was in
motion. This confirms that the car’s head unit does not have a
hardware-level 'Video-in-Motion' block.
The issue only occurs on my Samsung A24 with Android 16, where I get the
'Parked' restriction. Since the car itself is capable of showing the video,
it seems the restriction is purely coming from the new security layers of
Android 16.
Is there any way to bypass this Android 16 restriction (like a specific
installer or a 'tester' build) without purchasing additional hardware like
AAWireless? Since it works on Android 13 without any extra device, I am
looking for a software-based solution for the newer OS.
Thank you for your guidance.
Best regards,
Orkun"
12 Mar 2026 Per 12:08 tarihinde Andrey Pavlenko ***@***.***>
şunu yazdı:
… You don't need adb and com.android.vending will not help, just download.
Just download the apk to the phone and install. All you need is AAWireless.
—
Reply to this email directly, view it on GitHub
<#718 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B7XZWVV6W4JNKP2SLKKGF6D4QJ5ANAVCNFSM6AAAAACV6LZIHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBZGUYTANY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
"Hi Andrey,
I have a very clear comparison that explains the issue. I’ve attached two
screenshots from the 'Customize Launcher' settings of Android Auto.
On my wife's phone (Android 13): The 'Fermata Auto' app icon appears
correctly in the launcher list, and it works perfectly while driving in my
2025 Nissan Qashqai.
On my phone (Android 16): The 'Fermata Auto' icon is missing from the list
entirely. I can only see 'Fermata Control' and 'Media Service'.
This proves that Android 16 is actively blocking the main 'Fermata Auto'
app from the launcher due to its new sideloading restrictions, even though
I used KingInstaller.
Since I know the car supports it (as seen on Android 13), I want to avoid
buying AAWireless if there is a software bypass. Is there a specific way to
make the 'Fermata Auto' icon appear in the Android 16 launcher? Perhaps a
version signed for the Play Store or a method using Wireless
Debugging/Shizuku?
Thank you for your expertise.
Best regards,
Orkun
18 Mar 2026 Çar 08:32 tarihinde Orkun Atış ***@***.***> şunu
yazdı:
… "Hi Andrey,
Thank you for your quick response.
I understand your point about AAWireless, but I have a very specific
observation that I’d like to share:
I tested my wife’s phone, which is running Android 13, in the exact same
2025 Nissan Qashqai using the same version of Fermata Auto. It worked
perfectly, including YouTube and the Web Browser, even while the car was in
motion. This confirms that the car’s head unit does not have a
hardware-level 'Video-in-Motion' block.
The issue only occurs on my Samsung A24 with Android 16, where I get the
'Parked' restriction. Since the car itself is capable of showing the video,
it seems the restriction is purely coming from the new security layers of
Android 16.
Is there any way to bypass this Android 16 restriction (like a specific
installer or a 'tester' build) without purchasing additional hardware like
AAWireless? Since it works on Android 13 without any extra device, I am
looking for a software-based solution for the newer OS.
Thank you for your guidance.
Best regards,
Orkun"
12 Mar 2026 Per 12:08 tarihinde Andrey Pavlenko ***@***.***>
şunu yazdı:
> You don't need adb and com.android.vending will not help, just download.
> Just download the apk to the phone and install. All you need is AAWireless.
>
> —
> Reply to this email directly, view it on GitHub
> <#718 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/B7XZWVV6W4JNKP2SLKKGF6D4QJ5ANAVCNFSM6AAAAACV6LZIHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBZGUYTANY>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
To be available in AA the app must be installed from google play. In software you can workaround it if you have root. There is also one more opensource solution, but it requires a hardware - https://github.com/aa-proxy/aa-proxy-rs . |
Beta Was this translation helpful? Give feedback.
-
|
Hi Andrey,
Thank you very much for your honest and technical clarification.
It is now clear to me that the restriction is strictly tied to Google
Play's installation requirements on Android 16, as my tests on Android 13
were successful without any issues.
I appreciate the work you’ve put into this project and for pointing me
towards the hardware-based solutions like AA-Proxy. For now, I will look
into the hardware options to bypass these new OS limitations.
Thank you again for your time and guidance.
Best regards,
Orkun
18 Mar 2026 Çar 13:26 tarihinde Andrey Pavlenko ***@***.***>
şunu yazdı:
… To be available in AA the app must be installed from google play. In
software you can workaround it if you have root. There is also one more
opensource solution, but it requires a hardware -
https://github.com/aa-proxy/aa-proxy-rs .
—
Reply to this email directly, view it on GitHub
<#718 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B7XZWVWMSSH5KC7MX2QRVNT4RJ2T5AVCNFSM6AAAAACV6LZIHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJZGA3TKOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Look here and its free |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Andrey!
The guy at https://buymeacoffee.com/fermata is selling your app for $10, and he’s already sold over a thousand copies. Don't you think you should make a similar move? After all, it’s your hard work.
A lot of people would rather pay those $10 than buy an AAWireless dongle, which is even more expensive, or deal with rooting their phone just for Fermata. That money could really support your project. Plus, you could provide official updates and a guarantee that the source code is safe, since it would be coming directly from you.
Beta Was this translation helpful? Give feedback.
All reactions