Android 14

[dmitrykok]

Discussed in https://github.com/AndreyPavlenko/Fermata/discussions/315

^{Originally posted by **sensorial7** November 8, 2023} Hello, There is a problem with the Android 14 platform, after installing Fermata Auto and Control version 1.9.5 via Kinginstaller 1.4, there are no fermata icons in the AndroidAuto service. Everything worked on the previous version of Android 13. When can we expect the new version of Fermata dedicated to Android 14

On my Samsung Galaxy S23 Ultra, FermataAuto stopped working. Just I don't see it in AndroidAuto from now. FermataControl do exist in AndroidAuto. Tried to reinstall and reinstall with clean data, clean data of AndroidAuto and reinstall clean AndroidAuto, nothing help. AndroidAuto: 10.8.634424-release Android: 14

I resolved it by compiling it by myself and added some keys to manifests files. I did it according to: https://developer.android.com/training/cars/media/auto

to: control/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" />

to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

to: fermata/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" />

Actually maybe only this is needed, because min and target SDK are set via Gradle: to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

[AndreyPavlenko]

Adding <uses name="media" />, you make it a standard AA media app. I.e. no custom interface, no video etc.

[dmitrykok]

Yes you're right, now I see it in AndroidAuto, but it runs like FermataControl :( So how this can be fixed ? FermataAuto without <uses name="media" /> just not seen in AndroidAuto.

[AndreyPavlenko]

Unfortunately, I don't know. The only solution now is to root your device. I've not tested this option, but people say it works.

[dmitrykok]

Tried to downgrade to older versions from May 2023 of AndroidAuto, still no FermataAuto in it.

[dmitrykok]

Additional info, all works fine when run in "Desktop Head Unit". When disconnect from "Desktop Head Unit" FermataAuto disappear from AndroidAuto.

[AndreyPavlenko]

Additional info, all works fine when run in "Desktop Head Unit".

That's strange. Previously it was the case when 'Unknown sources" was disabled in AA settings.

[akulp]

Unfortunately, I don't know. The only solution now is to root your device. I've not tested this option, but people say it works.

@AndreyPavlenko is it confirmed that works on rooted devices?

I have Pixel 7 Pro, A14, unrooted.

But if it works with root, I'll go for it.

[AndreyPavlenko]

I can't confirm that.

[dmitrykok]

Additional info, all works fine when run in "Desktop Head Unit".

That's strange. Previously it was the case when 'Unknown sources" was disabled in AA settings.

Yes, 'Unknown sources' was always enabled in my AA. Interesting thing in "Desktop Head Unit". When "Desktop Head Unit" not running, open "Customize launcher" in AA, you don't see "FermataAuto", start "Desktop Head Unit" - exist from "Customize launcher" and open it once more, you will see "FermataAuto" in AA. After closing "Desktop Head Unit" - exist from "Customize launcher" and open it once more "FermataAuto" disappeared from AA. Looks like "Desktop Head Unit" put AA in some "dev" not restricted mode. Maybe I will try to capture communication between AA and DHU and will see some "set dev mode" message. Maybe we can put AA in this "dev and not restricted mode" without DHU.

[fcaronte]

As I know the wired to wireless devices "AAWireless" have a setting to enabled and then all app will showed as if connected to pc emulator and Is confirmed working on A14 too, should be interesting to see how is work and if was replicable software side without that hardware, unfortunately I have "Carsifi" and seem a abandoned from dev 🥲

[scheuerer]

Hello @fcaronte where to find this option in the "AAWireless" app, and how it is called, and how to active this, for Fermata, that it is shown in the launchpad again on a A14 U23ultra device?

[alpayyildirim]

Hello, fermata was running on Android 13. After the Android 14 update, it first gave a warning that it was not compatible with this version, but it continued to work despite this. When I uninstalled and reinstalled it, it didn't work. Maybe it can help you with your work.

[fcaronte]

Hello @fcaronte where to find this option in the "AAWireless" app, and how it is called, and how to active this, for Fermata, that it is shown in the launchpad again on a A14 U23ultra device?

I don't know exactly what's could be, I haven't tested myself, if you have it give a check to all options maybe is the one to continue using app during movement

[fcaronte]

Hello, fermata was running on Android 13. After the Android 14 update, it first gave a warning that it was not compatible with this version, but it continued to work despite this. When I uninstalled and reinstalled it, it didn't work. Maybe it can help you with your work.

So you loose your jolly, app was working when updating from A13 to A14 but after you touch that app, reinstall update etc will stop to work and actually no solution without root

[akulp]

Hello, fermata was running on Android 13. After the Android 14 update, it first gave a warning that it was not compatible with this version, but it continued to work despite this. When I uninstalled and reinstalled it, it didn't work. Maybe it can help you with your work.

So you loose your jolly, app was working when updating from A13 to A14 but after you touch that app, reinstall update etc will stop to work and actually no solution without root

If you check few posts above, there's no "official" confirmation to work on rooted devices as well... :(

[alpayyildirim]

There is no problem with Android 14s that have been updated from Android 13. If you want to install it later, it gives an error. I think if you make changes to the root directories, this problem will be solved.

[akulp]

Can you please describe what changes?

[fcaronte]

Hello, fermata was running on Android 13. After the Android 14 update, it first gave a warning that it was not compatible with this version, but it continued to work despite this. When I uninstalled and reinstalled it, it didn't work. Maybe it can help you with your work.

So you loose your jolly, app was working when updating from A13 to A14 but after you touch that app, reinstall update etc will stop to work and actually no solution without root

If you check few posts above, there's no "official" confirmation to work on rooted devices as well... :(

Will never exist an official status, all things are based on test from someone and actually root seem the only solution but is not suggested to root

[scheuerer]

@alpayyildirim Please make some suggestion what means exactly "I think if you make changes to the root directories, this problem will be solved." what and where do do, whitout rooting the phone...

[alpayyildirim]

I have no knowledge about this, sorry. I just stated that there is no problem in switching from A13 to A14. This may be an idea for software developer friends.

[akulp]

Hello, fermata was running on Android 13. After the Android 14 update, it first gave a warning that it was not compatible with this version, but it continued to work despite this. When I uninstalled and reinstalled it, it didn't work. Maybe it can help you with your work.

So you loose your jolly, app was working when updating from A13 to A14 but after you touch that app, reinstall update etc will stop to work and actually no solution without root

If you check few posts above, there's no "official" confirmation to work on rooted devices as well... :(

Will never exist an official status, all things are based on test from someone and actually root seem the only solution but is not suggested to root

With "official" I meant that Fermata will be (some day I hope) supported on A14 by author.

[scheuerer]

I found by myself an solution for me (not tested in the car so far), but the Fermata Icon is visable again in the AA launcher pad from the app.

1. Made an backup file from the configuration from Fermata on the local phone e.g. in the folder "download".
2. Deinstalled Fermata from the A14 Phone.
3. Installed it from the Google Store (the offical version, release 1.8.11)
4. Open it and restored the configuration from the backup file
5. Downloaded from (in the app via the link) the latest version (1.96)
6. Made upgrade of the app
7. Open the app and all the feature and settings are still there.
8. Check in the AA Launcher, and it was added as a new app I can move it on which place in the launcher I want.

So let's cross the fingers, that it will be also visable in the car when when testing it tonight.

[fcaronte]

I found by myself an solution for me (not tested in the car so far), but the Fermata Icon is visable again in the AA launcher pad from the app.

1. Made an backup file from the configuration from Fermata on the local phone e.g. in the folder "download".
2. Deinstalled Fermata from the A14 Phone.
3. Installed it from the Google Store (the offical version, release 1.8.11)
4. Open it and restored the configuration from the backup file
5. Downloaded from (in the app via the link) the latest version (1.96)
6. Made upgrade of the app
7. Open the app and all the feature and settings are still there.
8. Check in the AA Launcher, and it was added as a new app I can move it on which place in the launcher I want.

So let's cross the fingers, that it will be also visable in the car when when testing it tonight.

Umh go to try because see icon won't mean is working, and as I remember PlayStore version have different packages name so probably you have two Fermata installed

[scheuerer]

@fcaronte: You are correct :-) I have now two apps on the phone. The one is "Fermata", with less features, and the other "Fermata Auto" with more features. In the AA Launcher the "Fermata" is visable and not "Fermata Auto". So I assume, that only the light version will be working in the car under AA. As I use for IPTV the IPcarTV App, it is current not this important for me personal. Main focus is watching local stored music-videos. So not perfect, but fine for me for the the first time. Let's cross the fingers, that we are able to help Andrey to find a workaround for us.

[fcaronte]

@fcaronte: You are correct :-) I have now two apps on the phone. The one is "Fermata", with less features, and the other "Fermata Auto" with more features. In the AA Launcher the "Fermata" is visable and not "Fermata Auto". So I assume, that only the light version will be working in the car under AA. As I use for IPTV the IPcarTV App, it is current not this important for me personal. Main focus is watching local stored music-videos. So not perfect, but fine for me for the the first time. Let's cross the fingers, that we are able to help Andrey to find a workaround for us.

With the PlayStore version you can use the music part only without video, like with the Fermata control

[scheuerer]

Here comes the picture from the Fermata now working again, with all features, after my 8 steps I have written . So this is for me a temporary solution, having two times Fermata installed on my A14 phone.

[fcaronte]

Here comes the picture from the Fermata now working again, with all features, after my 8 steps I have written . So this is for me a temporary solution, having two times Fermata installed on my A14 phone.

Good so need to try this step

[fcaronte]

Here comes the picture from the Fermata now working again, with all features, after my 8 steps I have written . So this is for me a temporary solution, having two times Fermata installed on my A14 phone.

I read your step but for me now you actually have two installed versions of Fermata because play store and GitHub Version have two different packages name then maybe have two app installed is the trick, give a check if confirm the two app together

[akulp]

Here comes the picture from the Fermata now working again, with all features, after my 8 steps I have written . So this is for me a temporary solution, having two times Fermata installed on my A14 phone.

I read your step but for me now you actually have two installed versions of Fermata because play store and GitHub Version have two different packages name then maybe have two app installed is the trick, give a check if confirm the two app together

I'm not sure, so asking again. You had Fermata installed on A13 before? Then you made upgrade to A14?

Btw, off-topic. How did you move AA "navigation bar" on the left side? I tried with ON/OFF "Show quick controls for apps" option from settings, but it does not work for me. Maybe it depends from screen size ...

[scheuerer]

I started with A13 and Fermata auto 1.9.5. No issue. I upgrade to A14. No issue with 1.9.5 Now I updated to 1.9.6 under A14 and have had the issue.

After the 8 steps, I have 2 x Fermata on the phone. In the launcher AA app it is called Fermata and not more Fermata Auto, but in my car Fermata is working with all features as before…

Under AA there is a flag called change layout (closer to the driver)

[akulp]

I started with A13 an Fermata auto 1.9.5. No issue. I upgrade to A14. No issue with 1.9.5 Now I updated to 1.9.6 under A14 and have had the issue.

After the 8 steps, I have 2 x Fermata on the phone. In the launcher AA app it is called Fermata and not more Fermata Auto, but in my car Fermata is working with all features As before…

under AA there is a flag called change layout (closer to the driver)

Ok, yes. You started with A13. I installed Fermata for the 1st time when I was already on A14. I'm waiting new phone, which will probably have A13 and I'll try to install Fermata first and then I'll go with A14.

Thank you!

About "under AA there is a flag called change layout (closer to the driver)": This just turn around my apps, nav bar is still at the bottom.

[AndreyPavlenko]

I started with A13 an Fermata auto 1.9.5. No issue. I upgrade to A14. No issue with 1.9.5 Now I updated to 1.9.6 under A14 and have had the issue.

After the 8 steps, I have 2 x Fermata on the phone. In the launcher AA app it is called Fermata and not more Fermata Auto, but in my car Fermata is working with all features As before…

under AA there is a flag called change layout (closer to the driver)

Do you use any wireless adapter or connect directly via usb?

[Salafi83]

I started with A13 an Fermata auto 1.9.5. No issue. I upgrade to A14. No issue with 1.9.5 Now I updated to 1.9.6 under A14 and have had the issue.

After the 8 steps, I have 2 x Fermata on the phone. In the launcher AA app it is called Fermata and not more Fermata Auto, but in my car Fermata is working with all features As before…

under AA there is a flag called change layout (closer to the driver)

I have a similar issue. I started with A13 with FA 1.9.5 then upgraded to A14 with no problems. I accidentally reinstalled FA 1.9.5 using AAAD and FA stopped showing on AA. Also tried reinstalling FA 1.9.5 with KI but it didn't work.

I just reinstalled FA 1.9.6 via Playstore along with FA 1.9.6 that's already installed on my phone with AAAD and it shows up on AA as only Fermata without the 'Auto'...

I'm connected using USB.

[Denn1992]

Can we describe the steps in more depth? Like which configuration are you making a backup from?

[scheuerer]

1. @AndreyPavlenko: Yes, I'm using the GEN2 wireless Adapter from aawireless.io It works current with an beta version of

AA over CP in my Mercedes C-Class (MOPF) with 1920x720 pix screen include coolwalk with AA 10.9.634624.

@Denn1992:

I'll try to expain a litte bit more:

In principle I use a Samsung Galaxy S23 ultra (German, unbranded, with an Vodafone SIM), with A14 and ONE-UI, latest upgrades etc, The phone is NOT rooted.

1. Fermata has an own Backup and Restore feature. Under "settings", "miscellaneous", you can export the settings, playlist etc, in a file on the phone, e.g. in the download folder. This file can be used for an restore after you e.g. have complete deinstalled and installed new Fermata from the phone.
2. I deinstalled Fermata from the A14 Phone, by removing the app.
3. Then I installed from the Google Play Store (the offical version from Fermata, release 1.8.11)
4. Open it and restored in the fermata app itself, the exported configuration from the backup file which was ealierer stored.
5. Downloaded from github.com (via the link in the app with "about") the latest version of "Fermata Auto" (version1.9.6), fermata-1.9.6-auto-universal.arm.apk
6. After download I made an upgrade of the fermata app, by open the fermata-1.9.6-auto-universal.arm.apk file.
7. Open the Fermata app (without "auto") and all the feature and settings are still there.
8. Check in the AA Launcher, and it was added as a new app I can move it on which place in the launcher I want.

I have now two time fermata apps installed on the phone. "one fermata-auto", and one "fermata" Booth versions have my configuration inside the app. From the screenshot in the car you can see, that all features work, and the version is named as 1.9.6 Was playing around and all what is new compared to the Offical-Google-Playstore downloaded Fermata App, e.g. the cursor for D-Pad Emulation is there and work.

So for me (beside that I current have 2 x Fermata on the phone), everything works. If I had one wish it would be, that Andrey will not release an e.g. 1.9.7, before the A14 issue is not solved, to have the trouble again.

[fcaronte]

1. @AndreyPavlenko: Yes, I'm using the GEN2 wireless Adapter from aawireless.io It works current with an beta version of

AA over CP in my Mercedes C-Class (MOPF) with 1920x720 pix screen include coolwalk with AA 10.9.634624.

@Denn1992:

I'll try to expain a litte bit more:

In principle I use a Samsung Galaxy S23 ultra (German, unbranded, with an Vodafone SIM), with A14 and ONE-UI, latest upgrades etc, The phone is NOT rooted.

1. Fermata has an own Backup and Restore feature. Under "settings", "miscellaneous", you can export the settings, playlist etc, in a file on the phone, e.g. in the download folder. This file can be used for an restore after you e.g. have complete deinstalled and installed new Fermata from the phone.
2. I deinstalled Fermata from the A14 Phone, by removing the app.
3. Then I installed from the Google Play Store (the offical version from Fermata, release 1.8.11)
4. Open it and restored in the fermata app itself, the exported configuration from the backup file which was ealierer stored.
5. Downloaded from github.com (via the link in the app with "about") the latest version of "Fermata Auto" (version1.9.6), fermata-1.9.6-auto-universal.arm.apk
6. After download I made an upgrade of the fermata app, by open the fermata-1.9.6-auto-universal.arm.apk file.
7. Open the Fermata app (without "auto") and all the feature and settings are still there.
8. Check in the AA Launcher, and it was added as a new app I can move it on which place in the launcher I want.

I have now two time fermata apps installed on the phone. "one fermata-auto", and one "fermata" Booth versions have my configuration inside the app. From the screenshot in the car you can see, that all features work, and the version is named as 1.9.6 Was playing around and all what is new compared to the Offical-Google-Playstore downloaded Fermata App, e.g. the cursor for D-Pad Emulation is there and work.

So for me (beside that I current have 2 x Fermata on the phone), everything works. If I had one wish it would be, that Andrey will not release an e.g. 1.9.7, before the A14 issue is not solved, to have the trouble again.

Oh so you have AAWireless, as I say in some post here, they have featured to unblock all app without do nothing special, I don't know how is work but I remember was working for oppo and now work on A14 too, so probably your trick disappear if you try through usb cables, please check to confirm thanks

[rraghava10]

Tried the above steps and as said it is showing 2 apps in phone and in 2apps YouTube is accessible in phone. And connected phone using cable to car and in car display it is showing only playstore version and nothing is accessible from car. Not working

[fcaronte]

Tried the above steps and as said it is showing 2 apps in phone and in 2apps YouTube is accessible in phone. And connected phone using cable to car and in car display it is showing only playstore version and nothing is accessible from car. Not working

So unfortunately as I think wasn't work, AAWireless do the magic

[scheuerer]

Now we have some more information that it could be, that the wireless Dongle works in a different way, as an USB-Cable. As my car is in the wintergarage (Cabrio) I have always to drive to the car and test it. I will do the USB Test next time when an new aawireless beta version will be released to fix the BT HF Call crash problem, which exists at the moment with AA over CP. Let's see how this information helps Andrey in his development.

[fcaronte]

Discussed in https://github.com/AndreyPavlenko/Fermata/discussions/315

^{Originally posted by **sensorial7** November 8, 2023} Hello, There is a problem with the Android 14 platform, after installing Fermata Auto and Control version 1.9.5 via Kinginstaller 1.4, there are no fermata icons in the AndroidAuto service. Everything worked on the previous version of Android 13. When can we expect the new version of Fermata dedicated to Android 14

On my Samsung Galaxy S23 Ultra, FermataAuto stopped working. Just I don't see it in AndroidAuto from now. FermataControl do exist in AndroidAuto. Tried to reinstall and reinstall with clean data, clean data of AndroidAuto and reinstall clean AndroidAuto, nothing help. AndroidAuto: 10.8.634424-release Android: 14

I resolved it by compiling it by myself and added some keys to manifests files. I did it according to: https://developer.android.com/training/cars/media/auto

to: control/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" />

to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

to: fermata/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" />

Actually maybe only this is needed, because min and target SDK are set via Gradle: to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

I mod Screen2Auto apk with that Change and give to some A14 user to try and when I'll get feedback I'll update to and if is really only this thing will be very easy to fix all app

[scheuerer]

I can confirm, that Fermata under A14 works not via USB cable, but works via AAW adapter in the same configuration

[akulp]

Discussed in #315

Originally posted by sensorial7 November 8, 2023 Hello, There is a problem with the Android 14 platform, after installing Fermata Auto and Control version 1.9.5 via Kinginstaller 1.4, there are no fermata icons in the AndroidAuto service. Everything worked on the previous version of Android 13. When can we expect the new version of Fermata dedicated to Android 14 On my Samsung Galaxy S23 Ultra, FermataAuto stopped working. Just I don't see it in AndroidAuto from now. FermataControl do exist in AndroidAuto. Tried to reinstall and reinstall with clean data, clean data of AndroidAuto and reinstall clean AndroidAuto, nothing help. AndroidAuto: 10.8.634424-release Android: 14 I resolved it by compiling it by myself and added some keys to manifests files. I did it according to: https://developer.android.com/training/cars/media/auto to: control/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" /> to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" /> to: fermata/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" /> Actually maybe only this is needed, because min and target SDK are set via Gradle: to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

I mod Screen2Auto apk with that Change and give to some A14 user to try and when I'll get feedback I'll update to and if is really only this thing will be very easy to fix all app

Well done! Thanks for the effort.

[The-legend-72]

I have tested Fermata Auto with an AAWireless dongle. It does not work. I have messed around with AAwireless settings to no avail.

Do we know what setting should be changed?

[fcaronte]

I have tested Fermata Auto with an AAWireless dongle. It does not work. I have messed around with AAwireless settings to no avail.

Do we know what setting should be changed?

Unfortunately I don't know and the guy I ask say he don't know how and why is work have no special settings, maybe need a firmware update?

[The-legend-72]

I have tested Fermata Auto with an AAWireless dongle. It does not work. I have messed around with AAwireless settings to no avail. Do we know what setting should be changed?

Unfortunately I don't know and the guy I ask say he don't know how and why is work have no special settings, maybe need a firmware update?

I have it on the latest firmware. I think it has something to do with him upgrading from A13 to A14. I have A P8P and it came with A14 out of the box.

[fcaronte]

Discussed in https://github.com/AndreyPavlenko/Fermata/discussions/315

^{Originally posted by **sensorial7** November 8, 2023} Hello, There is a problem with the Android 14 platform, after installing Fermata Auto and Control version 1.9.5 via Kinginstaller 1.4, there are no fermata icons in the AndroidAuto service. Everything worked on the previous version of Android 13. When can we expect the new version of Fermata dedicated to Android 14

On my Samsung Galaxy S23 Ultra, FermataAuto stopped working. Just I don't see it in AndroidAuto from now. FermataControl do exist in AndroidAuto. Tried to reinstall and reinstall with clean data, clean data of AndroidAuto and reinstall clean AndroidAuto, nothing help. AndroidAuto: 10.8.634424-release Android: 14

I resolved it by compiling it by myself and added some keys to manifests files. I did it according to: https://developer.android.com/training/cars/media/auto

to: control/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" />

to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

to: fermata/src/main/AndroidManifest.xml added: <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="34" />

Actually maybe only this is needed, because min and target SDK are set via Gradle: to: fermata/src/auto/res/xml/automotive_app_desc.xml added: <uses name="media" />

Unfortunately we try on 3 devices and won't work on any of them, do you use AAWireless?

[idyum]

Hi, I am also having issues after upgrading to A14. Fermata auto was working fine after the upgrade to A14, but when I updated Fermata Auto it disappeared from Android Auto as others has reported.

I discovered a workaround if you're using the AAWireless adaptor: go to settings in the AAWireless companion app and enable developer mode.

Once i did this Fermata Auto reappeared, hope this helps 👍🏻

[fcaronte]

Hi, I am also having issues after upgrading to A14. Fermata auto was working fine after the upgrade to A14, but when I updated Fermata Auto it disappeared from Android Auto as others has reported.

I discovered a workaround if you're using the AAWireless adaptor: go to settings in the AAWireless companion app and enable developer mode.

Once i did this Fermata Auto reappeared, hope this helps 👍🏻

Oh good so now we have the confirm to what's need to enabled to make AAWireless do the trick, thanks

[The-legend-72]

Hi, I am also having issues after upgrading to A14. Fermata auto was working fine after the upgrade to A14, but when I updated Fermata Auto it disappeared from Android Auto as others has reported. I discovered a workaround if you're using the AAWireless adaptor: go to settings in the AAWireless companion app and enable developer mode. Once i did this Fermata Auto reappeared, hope this helps 👍🏻

Oh good so now we have the confirm to what's need to enabled to make AAWireless do the trick, thanks

Can confirm. Enabling developer mode in AAwireless does the trick.

[alpayyildirim]

Merhaba, A14'e yükselttikten sonra da sorunlar yaşıyorum. Fermata auto, A14'e yükseltme sonrasında iyi çalışıyordu, ancak Fermata Auto'yu güncellediğimde diğerlerinin bildirdiği gibi Android Auto'dan kayboldu. AAWireless adaptörünü kullanıyorsanız bir geçici çözüm buldum: AAWireless yardımcı uygulamasındaki ayarlara gidin ve geliştirici modunu etkinleştirin. Bunu yaptığımda Fermata Auto yeniden ortaya çıktı, umarım bu yardımcı olur 👍🏻

Ah güzel, artık AAWireless'ın işe yaraması için neyin etkinleştirilmesi gerektiğini onayladık, teşekkürler

Onaylayabilirim. AAwireless'ta geliştirici modunu etkinleştirmek işe yarar.

How to enable aawireless developer mode