I have a Galaxy S9+ using a sony head unit. Since the android 10 update most things dont work anymore. Samsung doesnt respond to questions and either does google. I would roll back to 9 but my bootloader is locked. Is there anyway around this ?
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
mrdlejzr said:
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
Click to expand...
Click to collapse
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
uhi711 said:
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I uninstalled the old aa app on my phone because i thought it was part of the os, restarted the phone and plugged it in my truck and it would not connect. The only way aa almost works is if you install the app on your phone.
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
uhi711 said:
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
dinosaurus1 said:
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
Click to expand...
Click to collapse
Sorry to hear about all the trouble. Just keep searching the internet about your specific problem and configuration. If you still have your previous phone and if it still has a working AA, you could use it just in your car connected to your wifi hotspot from your Note 10. Also try a different cable, a shorter one (I use a 1 foot only cable), all my connection problems went away with this shorter cable bought on Aliexpress. Wish you luck!
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:59 PM ---------- Previous post was at 07:50 PM ----------
I forgot to ask, did you try using AA with a wireless connection? If you have a new car, chances are that you could use wireless connection between your phone and the car. There is a setting in AA to enable this. Just set this switch on before trying to connect to the car's infotainment system.
Sent from my SM-N975F using Tapatalk
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
deepudips said:
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
Click to expand...
Click to collapse
Unfortunately, I do not have a satisfactory answer for you. I just didn't upgrade my phone to Android 10, because of the many bug reports I read about. A long time ago, when I was using the Note 8 and Android 8, I had the same connection problems for a few months. Then, the only thing that helped me was using short (20-25 cm) quality cables, bought on Aliexpress. It might also be a coincidence, I'm not sure, because in the same time I changed cable after cable, Google also updated AA. As of now, I'm using the Note 10+ with Android 9 and the same short cable that I think it fixed my connection problem then, and I still don't have any problem. You'll just have to wait patiently for Google to fix the bugs.
Sent from my SM-N975F using Tapatalk
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
woody4165 said:
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
Click to expand...
Click to collapse
I'm sorry, I'm afraid I can't help you. I don't know what is Lineage OS and how it works. What I do know is that there is no such a thing as different AA versions. There is only one kind of AA app downloadable from the Play store if you have Android 9 or less on your phone. If you have Android 10 installed on your phone, then you do not need the AA app and you won't be able to download it from the Play store, because it is already built-in in the OS (Android 10).
Sent from my SM-N975F using Tapatalk
I had the same problem with my Note 9 with Android 10, it kept connecting and disconnecting. Restarting the phone worked for me.
The couple AA and Android 10 is known for a lot of bugs and connection problems.
Sent from my SM-N975F using Tapatalk
Related
Hi, I just recently got a new Golf with the app connect system that has Android Auto functionality built in. However, I just can't get it to work with my G4. I've downloaded the Android Auto app, I've tried using different cables but every time I plug it in the AA app seems to just crash. It also won't connect manually when I try to connect it in the car. I live in Australia. Is there anything else I can do/download to make this work? Thanks.
Don't know if this will help, but try to set the Android Auto on a headunit. Mine was set to Mirrorlink by default.
Maybe in the settings you should define it to choose Android Auto instead ?
Make sure the phone is unlocked when its plugged in. Also, try plugging in the phone before you turn on the car. My Nexus 5 is able to connect 90% of time on my 2016 GTI.
I just picked up my GTI last night. The salesman couldn't get Android Auto to connect to my AT&T G4. Android Auto was set as the preferred connection. I've tried connecting with my phone locked, unlocked, plugged in before/after the car is on, plugged in after/before the phone is unlocked, USB debugging on and off, MTP, charging only, PTP.
monkadelicd said:
I just picked up my GTI last night. The salesman couldn't get Android Auto to connect to my AT&T G4. Android Auto was set as the preferred connection. I've tried connecting with my phone locked, unlocked, plugged in before/after the car is on, plugged in after/before the phone is unlocked, USB debugging on and off, MTP, charging only, PTP.
Click to expand...
Click to collapse
Did you ever get connected?
Robbie Doo said:
Did you ever get connected?
Click to expand...
Click to collapse
tt
I work at a vw/Skoda dealership. I am tech savvy. I have tried I phones and various Androids with Mirrorlink/Android Auto and to be honest the results are pretty Mixed. I phones mostly pair OK but with so many iterations of Android topped with manufactures bloatware its impossible. I have failed to pair phones that are compatible and tried every app every cable and every configuration even the Manufacturers are clueless. Some models I managed to pair took me 40 or 50 attemps. Android Auto is in its infancy and stability will take time. I managed an S5 with ease and S6 with great difficulty a HTC one A9 which is very unstable. A HTC one M8, but didn't manage the Huawei P8 yet but I'm working on it. I failed with a galaxy S4 and succeeded with another one. I have an LG G4 on the way so that will be interesting. I have had 100% success pairing I iPhones but customers tell us the connection drops out. However I do think Android Auto offers more in terms of functionality if you can live with the fact that you may not ever get it working.
Anything new with G4
Did you manage to make the LG G4 working?
Hello
I had the same problem with my VW Passat GTE 2016 + LG G4. Solved it by going into the settings in the car (under App Connect) and chose Android Auto as default instead of MirrorLink which was the default before.
(although it doesn't work very well anyway, sometimes it does, sometimes it doesn't)
I have Android Auto 1.6.2400
Konstigt said:
Hello
I had the same problem with my VW Passat GTE 2016 + LG G4. Solved it by going into the settings in the car (under App Connect) and chose Android Auto as default instead of MirrorLink which was the default before.
(although it doesn't work very well anyway, sometimes it does, sometimes it doesn't)
I have Android Auto 1.6.2400
Click to expand...
Click to collapse
Just to confuse the issue even more, my vw connects to android auto pretty much perfectly every time & yet I only discovered by accident that the default setting on the head unit was set to mirror link so maybe that's not the cause for you after all. It's pretty basic software so far it seems.
Sent from my Nexus 6P using XDA-Developers mobile app
I picked up my new Golf today, but it doesn't have the App Connect. My phone is an Oneplus One with MM Cos 13, do you think Android Auto can work with it?
Just my experience : I own a 2016 Jetta with App Connect and a Nexus 4. I had similar issues with AA connections first. The phone was running Android L 5.1..1. 2 weeks ago I went ahead and installed CM13 and now AA works way better : I never had a connection failure since... Really a plug and forget experience now. So I think Android M is better for Android Auto. Moreover I read that latest AA update includes fixes for connection stability.
I've tried three Roms (2 Oreo and 1 nougat) and I can't get Android Auto to work with any of them. Has anyone gotten Android Auto to work with any of the Roms available here?
Sent from my Nexus 6 using Tapatalk
It has worked well for me on the latest 7.1.2 Pure Nexus ROM. I am currently running AICP Oreo and it works great. It also worked on S.I.X. ROM Oreo and Republic of Madness Oreo ROMs for me.
What issues are you having?
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
imaGine00 said:
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
Click to expand...
Click to collapse
Have you tried a different cable? I had to try 3 of them before it worked right to start with in my F150
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
imaGine00 said:
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
Click to expand...
Click to collapse
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
AAuto works great on my N6 with LineageOS on my Kia Sportage. It's a brand new 2018 Kia purchased two days ago. One of the main reasons for that purchase was AAuto in the electronics package.
bfmetcalf said:
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
Click to expand...
Click to collapse
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
imaGine00 said:
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
Click to expand...
Click to collapse
Try clearing data for AA and see if that helps.
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Negotiator50 said:
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
This did the trick!! Thank you so much!
Sent from my Nexus 6 using Tapatalk
bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
woooooh that did the trick ! Thank you !!
I use it with crDroid 4.0 Beta 6 and everything work ...
Hi,
My car is not able to connect to Note 9 via MirrorLink. I used Galaxy A5 in the past with the same car. So I assume it's not a car issue.
Once MirrorLink is selected on car Media system, it tries to connect to my phone and even launches SkodaApp (but on the phone screen.. not car multimedia system) and immedately quits with an error that phone doesn't support MirrorLink.
MAybe something's missing in the phone. Any ideas?
AndroidAuto runs perfectly with Note9+Skoda. But not MirrorLink
Thanks
bat0nas said:
Hi,
My car is not able to connect to Note 9 via MirrorLink. I used Galaxy A5 in the past with the same car. So I assume it's not a car issue.
Once MirrorLink is selected on car Media system, it tries to connect to my phone and even launches SkodaApp (but on the phone screen.. not car multimedia system) and immedately quits with an error that phone doesn't support MirrorLink.
MAybe something's missing in the phone. Any ideas?
AndroidAuto runs perfectly with Note9+Skoda. But not MirrorLink
Thanks
Click to expand...
Click to collapse
Is it a Yeti?
Sent from my SM-N960U1 using Tapatalk
Limeybastard said:
Is it a Yeti?
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
No. Superb.
Sent from my SM-N960F using Tapatalk
bat0nas said:
Hi,
My car is not able to connect to Note 9 via MirrorLink. I used Galaxy A5 in the past with the same car. So I assume it's not a car issue.
Once MirrorLink is selected on car Media system, it tries to connect to my phone and even launches SkodaApp (but on the phone screen.. not car multimedia system) and immedately quits with an error that phone doesn't support MirrorLink.
MAybe something's missing in the phone. Any ideas?
AndroidAuto runs perfectly with Note9+Skoda. But not MirrorLink
Thanks
Click to expand...
Click to collapse
My Subaru has MirrorLink, but it doesn't work correctly either. Message board says MirrorLink is not backwards compatible with older versions... So, the Note 9 version (1.4) is "too new" for older vehicles. People have downgraded the app (not sure how, really), and it connects. Maybe this is why...
RGardner said:
My Subaru has MirrorLink, but it doesn't work correctly either. Message board says MirrorLink is not backwards compatible with older versions... So, the Note 9 version (1.4) is "too new" for older vehicles. People have downgraded the app (not sure how, really), and it connects. Maybe this is why...
Click to expand...
Click to collapse
Maybe disable note 9 version, side load correct version from APK mirror, with app clone
Sent from my SM-N960U using Tapatalk
hayabusa1300cc said:
Maybe disable note 9 version, side load correct version from APK mirror, with app clone
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Yeah, I have Samsung's MirrorLink app disabled, otherwise when I charge my phone from the USB port, it locks up.
And, I just tried to sideload an older version, but it won't (yes, sideloading is enabled). Of course, no reason why is given.
But, it's just an experiment for me. MirrorLink isn't well supported, not a lot of apps. I'd rather have Android Auto (which the 2018 Forester DOESN'T support either... :silly.
RGardner said:
Yeah, I have Samsung's MirrorLink app disabled, otherwise when I charge my phone from the USB port, it locks up.
And, I just tried to sideload an older version, but it won't (yes, sideloading is enabled). Of course, no reason why is given.
But, it's just an experiment for me. MirrorLink isn't well supported, not a lot of apps. I'd rather have Android Auto (which the 2018 Forester DOESN'T support either... :silly.
Click to expand...
Click to collapse
Regarding side loading, you may need to use App Cloner. It will sign the APK differently so you're essentially running another instance of the cloned app, instead of replacing the original app. In my experience, very few Samsung app you can side load with the newer phones.
Sent from my SM-N960U using Tapatalk
After few experiments it started working for me.
Looks like Samsung Car Mode must be installed for other MirrorLink apps to work. I've read somewhere that at least one MirrorLink certified app must be installed. Not sure what Certified means because apps like Skoda One App are also certified.
Anyway - problem solved. Both Android Auto and MirrorLink is working. Both are useless* for me but at least both are working if I'll need a show off for my friends
*Useless because I can't use assistant apps (EN is not my native), Waze looks poor and blured on car screen etc.
I wish to figure out if it's possible to change AA DPI when phone is connected to head unit.
With AA wireless, when you change DPI, it's possible to get a splitted screen, but i wish to know if it's possible to do it with a wired connection?
Regards
huck3301 said:
I wish to figure out if it's possible to change AA DPI when phone is connected to head unit.
With AA wireless, when you change DPI, it's possible to get a splitted screen, but i wish to know if it's possible to do it with a wired connection?
Regards
Click to expand...
Click to collapse
There already is one for wired connections. Use it all the time. Works great.
[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto
Update 30.11.2022 End of life and open source. Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source. Code is accessible...
forum.xda-developers.com
heffer86 said:
There already is one for wired connections. Use it all the time. Works great.
[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto
Update 30.11.2022 End of life and open source. Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source. Code is accessible...
forum.xda-developers.com
Click to expand...
Click to collapse
Would you be willing to share what setup/versions you're using that is working? It seems like OBD2AA isn't working on newer AA versions, at least for me anyways. I've spent way too much time on it as a project haha.
I've got a 2022 VW Golf R (MIB3) and have tried with a Pixel 6 Pro on A12L and a OnePlus 6T on A9. Every time I select OBD2AA when connecting to my car the head unit will bring up a black screen as though it's about to show AA, but just goes back to a prior menu on the car and OBD2AA just crashes (on both phones). I tried patching the app via AA AIO Tweaker as well.
Tried older versions of AA on the 6T and even if I can get around the app requirements being out of date, AA just throws error 14 and wants me to update Play Services. So I've been a bit stuck with it unfortunately.
MINISPOON939 said:
Would you be willing to share what setup/versions you're using that is working? It seems like OBD2AA isn't working on newer AA versions, at least for me anyways. I've spent way too much time on it as a project haha.
I've got a 2022 VW Golf R (MIB3) and have tried with a Pixel 6 Pro on A12L and a OnePlus 6T on A9. Every time I select OBD2AA when connecting to my car the head unit will bring up a black screen as though it's about to show AA, but just goes back to a prior menu on the car and OBD2AA just crashes (on both phones). I tried patching the app via AA AIO Tweaker as well.
Tried older versions of AA on the 6T and even if I can get around the app requirements being out of date, AA just throws error 14 and wants me to update Play Services. So I've been a bit stuck with it unfortunately.
Click to expand...
Click to collapse
I am running a Pixel 5 on Android 12 with Ford Sync 3 and 4. I have the latest version of AA also. Do you have the torque pro app? Did you pay for the app on the website in the post? You can't just use the one found in the app store. You don't need a rooted phone for it to work.
My suggestion would be to clear out the app data for Android Auto and clear out the app defaults. I would then reboot your phone. While the phone is un-locked plug your phone into your headunit. Hopefully you will get the prompt to select Android Auto or OBD2AA.
heffer86 said:
I am running a Pixel 5 on Android 12 with Ford Sync 3 and 4. I have the latest version of AA also. Do you have the torque pro app? Did you pay for the app on the website in the post? You can't just use the one found in the app store. You don't need a rooted phone for it to work.
My suggestion would be to clear out the app data for Android Auto and clear out the app defaults. I would then reboot your phone. While the phone is un-locked plug your phone into your headunit. Hopefully you will get the prompt to select Android Auto or OBD2AA.
Click to expand...
Click to collapse
Thanks for all that info, I appreciate the reply. I've got both apps and ensured Torque Pro is communicating properly as well. I'll try clearing everything for AA, I had been doing that with the other apps instead thinking that was the issue but never thought to try it with AA itself.
Hi everyone,
I'm having an issue with my Xiaomi 12T Pro and Android Auto. I've been using Android Auto wirelessly via Bluetooth on my KIA CEED 2023 MY(wireless support) for the past three weeks without any issues. I even updated my phone to Android 13 and MIUI 14 about 2 weeks ago, and everything still worked fine.
However, couple days ago when I was driving my car, Android Auto suddenly stopped working during my drive. Since then, I've tried factory reset of my KIA infotainment system, network setting reset, unpairing and repairing Bluetooth, and even installing the latest version of the AA mirror apk. I've also uninstalled and reinstalled the current version of AA from Google Play, but I still can't connect to Android Auto wirelessly and the only error message is during the attempt of connecting: "The phone is not responding. Try it again".
The connection with a cable works fine. I tried 3 other phones on my car - all work. I tried to connect my Xiaomi 12T Pro to a different car and I have the same problem as on my Kia.
Even Android Auto support seems to be helpless. I shared with them a bug report, tried some suggested setups, but nothing works..
Does anybody have any ideas or have same experience?
Hello, the same thing happens to me with the carplay of my mercedes benz. And driving seems to disconnect my Xiaomi 12T PRO. I still don't have a solution from the manufacturer Xiami or the manufacturer of the carplay module. Is there anyone who can help us?
First of all, make sure you have the latest available firmware for your headunit. I don't know where you live but in some regions the Kia and Hyundai headunits can be upgraded by using the Kia Navigation Update application and a spare USB thumbdrive.
This said, I've had similar issues in a Kia Rio when using Android Auto wirelessly:
* Make sure the hour and date are set correctly in your headunit. Sometimes the headunit craps itself while trying to get the GPS hour and it sets incorrectly, wich causes conectivity issues with Android Auto
* Make sure your phone is not connected to any other bluetooth device before connecting to the headunit. I have a couple Xiaomi phones and neither of them is able to use Wireless Android Auto if they're connected to a wireless headphones, a laptop or a smartwatch. I don't understand why this happens but only happens with Xiaomi phones.
* MIUI has a battery optimization feature wich kills some apps and background services to save energy. Even if you disable it for some of your apps, sometimes a MIUI update will override this and cause problems. Make sure Android Auto, Google Maps, your music app and your messaging apps are excluded from the battery saver features, and make sure Google Maps has the location permission set to "all the time".
* Unpair your phone from the headunit and sync it again.
* Go to Android Auto settings (in your phone) and make sure that Wireless Android Auto toggle is enabled. Disable the Android Auto's developer mode if it's enabled.
* Factory reset the headunit and try to sync your phone again. The first time you sync the phone, do it with the USB cable.
YgorTN said:
Hi everyone,
I'm having an issue with my Xiaomi 12T Pro and Android Auto. I've been using Android Auto wirelessly via Bluetooth on my KIA CEED 2023 MY(wireless support) for the past three weeks without any issues. I even updated my phone to Android 13 and MIUI 14 about 2 weeks ago, and everything still worked fine.
However, couple days ago when I was driving my car, Android Auto suddenly stopped working during my drive. Since then, I've tried factory reset of my KIA infotainment system, network setting reset, unpairing and repairing Bluetooth, and even installing the latest version of the AA mirror apk. I've also uninstalled and reinstalled the current version of AA from Google Play, but I still can't connect to Android Auto wirelessly and the only error message is during the attempt of connecting: "The phone is not responding. Try it again".
The connection with a cable works fine. I tried 3 other phones on my car - all work. I tried to connect my Xiaomi 12T Pro to a different car and I have the same problem as on my Kia.
Even Android Auto support seems to be helpless. I shared with them a bug report, tried some suggested setups, but nothing works..
Does anybody have any ideas or have same experience?
Click to expand...
Click to collapse
Turn off power saving settings clear cache when locked & disable mobile data when locked
then Check battery saving settings for android auto app and system service. Also turn off miui memory optimization, just because. It always fcks up background processes at little gain to the user.
Edit: apparently most of these settings are gone in MIUI14.0.5 global rom/Android 13
Thanks for your advice guys. Meantime, I did a factory reset, and since then everything works fine.
ALas its a miui bug known since ages. If the device for whatever reason losses connection to the mobile network the devs somehow made sure the device disconnnects any Wifi connection. Hence AA stopping working.
Want to test tthis?
Simply deactivate mobile data on your phone and activate it again.
yuukiw said:
ALas its a miui bug known since ages. If the device for whatever reason losses connection to the mobile network the devs somehow made sure the device disconnnects any Wifi connection. Hence AA stopping working.
Want to test tthis?
Simply deactivate mobile data on your phone and activate it again.
Click to expand...
Click to collapse
It has been fixed in n miui 14.