Android Auto stopped working on Galaxy Fold 3 - Android Q&A, Help & Troubleshooting

Android Auto has stopped working. I have a Galaxy Fold 3 that I have been using since November with the Uconnect in my 2018 Jeep Compass. It suddenly stopped working. It worked fine until today. I last used it about 2 weeks ago. The phone connects with the car via Bluetooth just fine. I am able to make calls and receive texts. When I connect the phone using my USB cable to use Android Auto, the phone shows that it is charging and I verified it is set to be able to transfer data. Instead of launching and connecting to Android Auto, the screen on the car tells me to follow directions on the phone screen to connect. The phone screen shows an Android Auto screen that shows it wants to start set up to connect (it used to connect without any issues) but when I hit the "next" button on the phone, Android Auto on the phone just shuts down. I cleared the cache & data for Android Auto, uninstalled & reinstalled Android Auto, verified my phone has all of its software updates, tried a different USB cable, reboot my phone, unpaired & then paired the phone to the car... nothing is working. My phone software updated on August 2nd. This is the first I've tried to use the Android Auto since the last phone software update. I've tried all of the suggestions on Android Auto's troubleshooting page. Can anyone help?

Related

[Q] Auto startup after shutdown!

All right, I have a lil problem that goes a little some like this...
1) Everytime a try to shut down the phone it reboots automatically!
I've also been having other problems with the phone too! and they are
2) I charge my mobile at night go to work and only, only just last when i get home after 8 - 10 hours, in that time i dont even use it! but when i disconnect it from charging fully, it takes a while to recognise that it has disconnected, displays battery still charging etc, and it makes noises that its connected and disconnected???
3) They unlock screen plays up, you'll try and drag your finger across the screen to make a pattern to unlock and it does complete the pattern or recognise where your finger is, if you wait for a little bit or lock then try again it works??? (GO LOCK installed, along with GO PRO theme!)
4) GO weather doesn't recognise your GPS positioning but the Navigation program does. (this maybe the program i dont know, its just all happening at once that all)
5)Try to connect to Samsung Kies Pc studio to update the firmware and mobile, and i keep getting a message saying 'Reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported be Kies. (and this is with the updated Kies program)
6) Now when i turn it off and restarts it's self, it hangs on at shut down flashing between two picture, the battery status picture and saying its overheated, when now it doesn't overheat like it was doing earlier or even get hot at all??? And to get it outta this mode i have to put a charger in it and turn it back on and take it out
What i have done so far:
a) I've uninstalled all the 'GO' apps
b) followed the Samsung Kies instructions and still same problem
c) tried going throught the mobile's options to turn on or off anything to do with USB sharing and bebugging, and keeps telling me that the usb cable is to be disconnected when it is not???
All i can relate this to is when, one time while i was working i put my mobile away in the glove box of the work vehicle, i returned to it at the end of the day and remember my mobile would be flat at this stage, so i was gonna check the time, and i sore the mobile had SOME how went into 'ODIN' mode, NO one ever touched it, nor did i do anything to it to do this, and sore it was trying to download something? I panicked, try to turn it off, and wouldn't turn back on till i got a charger into it.
So now i am thinking this maybe to problem 'ODIN' mode when i forced it to shut down!, but from here this is where i need help? What is first
Additional info:
PC O/S: windows 7 Home premium
Samsung Galaxy S2 I9100
Mobile: PDA: I9100TDVKF4
Phone: I9100TDVKF2
CSC: I9100TTELKF3
Build Info: TUE JUN 21 16:41:40 KST 2011
Provider: Telstra
Country: Australia
Any help would be very grateful, thankz in advanced for your time to share any info
Ok, wired thing just happened, i was stuffing around, my mobile was connected by usb to the computer charging, and it reached 100% so i disconnected it and was playing through the menus again, trying to disable debugging mode and... it finally disconnected!
So i was able to connected to Kies, checking everything and it was saying that i had the latest updates and firmware, is this true because i've been reading other wise and was wondering, if there is a better update then i've got, cause i've still got all the other same problems!
So what do i do, reinstall, update??? i have no idea!
The problems with the phone restarting and not disconnecting is probably your micro usb connection on the phone. Try cleaning it.
Sent from my GT-I9100 using Tapatalk

[Q] Cubot One Bluetooth Connection Issues

I have a Cubot One, using the G800_CUBOT_D1_V0.8_20140124_MJK firmware (4.2.1) - it was previously on the 0.6 firmware and had the same issue.
What I have experienced is that when connecting to a device with Bluetooth - in this case a Sony SW2, but have also tried Bluetooth headsets - it has problems pairing.
The phone sees the BT device as an available device, and when I select it, it starts the pairing process. Initially it seems to be ok and successfully pairs for 2-5 seconds, the the device is relisted as an available device, but not connected. I have had success twice. The first time was immediately after rooted my phone, and this was ok for several days, even rebooting my phone and the watch didn't seem to cause the issue again, but then it randomly stopped working. I was unable to connect until flashing with the 0.8 ROM. At this point is was again working for about 24 hours - even better than before - until I switched the watch off. Since then I have been unsuccessful in pairing again.
Interestingly, when I try to pair with my Galaxy Tab 2 I have the same problem, UNLESS I initiate the connection with the tablet, then it is fine.
I know that there were problems with the Bluetooth stack on 4.2.1 when it first came out, and it may be related to that, but can anyone offer suggestions as to what else I can try?

Samsung Galaxy S9+ Oreo 8.1 update? (need to solve Android Auto issues)

Hi,
I got my shiny S9+ two days ago and very happy with it although I have an issue with Android Auto.
My previous phone, Galaxy S7, never had a problem connecting to my car using Android Auto. It worked from the beginning and no issues whatsoever.
Now my S9+ refuses to connect with my car. Even manually launching Android Auto, the application still cannot register or recognize the car. The car also shows an error upon connecting the phone through USB (with or without Android Auto launched on the phone).
Just in case I tried three different USB C cables, uninstall/install Android Auto, clean cache & memory, reboot the phone, change the phone USB settings (MTA, File Transfer, etc), nothing seems to work. Somebody suggested me to use USB developer mode but I doubt it'll fix this issue.
I googled a little bit and found that Oreo 8.0 has issues with Android Auto that was fixed on 8.1. My phone currently has 8.0 so I wonder if somebody knows when Samsung will update their phones to Oreo 8.1
Thanks in advance,
Been using AA since day one without problems here.. And if someone suggested you try developer mode, why don't you just try it while you wait for 8.1?
Ok, thanks!
I have a PIoneer AVH4100-NEX and when I had my Nexus it was very flaky at best. I would have connection issues off and on frequent, but with my 9+ it has been flawless. Glad they worked it out.
jgirado said:
Hi,
I got my shiny S9+ two days ago and very happy with it although I have an issue with Android Auto.
My previous phone, Galaxy S7, never had a problem connecting to my car using Android Auto. It worked from the beginning and no issues whatsoever.
Now my S9+ refuses to connect with my car. Even manually launching Android Auto, the application still cannot register or recognize the car. The car also shows an error upon connecting the phone through USB (with or without Android Auto launched on the phone).
Just in case I tried three different USB C cables, uninstall/install Android Auto, clean cache & memory, reboot the phone, change the phone USB settings (MTA, File Transfer, etc), nothing seems to work. Somebody suggested me to use USB developer mode but I doubt it'll fix this issue.
I googled a little bit and found that Oreo 8.0 has issues with Android Auto that was fixed on 8.1. My phone currently has 8.0 so I wonder if somebody knows when Samsung will update their phones to Oreo 8.1
Thanks in advance,
Click to expand...
Click to collapse
If all fails, do the factory reset.
After S9+ got the update upon booting for the first time, the battery life was horrible. After the factory reset, however, happily ever after... (even though it was the pain in the a$$ to setup the phone again.
Thanks for all the tips. Although I delete my S7 profile in my car the solution was to perform a factory reset of my car's multimedia system/navigation. Now is working like a charm.
Javier

Parrot MKi9200 with Galaxy S2

I've recently upgraded my ROM on my S2 i9100 phone from the standard 4.1.2 official to various unofficial ROMs. None of these allow me to use the hands-free features of the MKi9200 device. All of them will pair with the Parrot but the phone-book does not sync. Pressing the green button on the Parrot (which should allow you to voice dial) simply gives the message "phonebook is busy please wait".
I have reached out to Parrot without any joy to date even after 8 emails each way. My symptoms to them were along the following lines.
"1. The phone pairs with the MKi9200 still but still does not automatically connect when I get into the car.
2. After pairing the phone, the menu item “Bluetooth/paired phones” is still greyed out. It used to have my phone listed there before I upgraded. I guess that this is why the MKi does not automatically connect.
3. As noted above, I have to manually connect my phone now, whereas before I upgraded the smartphone Android version, it connected automatically. When it does connect, it says it is synchronising for a second or two.
4. I can dial a number using the “Phonebook” on the MKi device using the central knob and the menu system. I cannot use the green button as it always says the “phonebook is busy please wait”, even after 15 minutes.
5. When I finish a call, the iPod music does not restart automatically and I cannot start it manually using the “Play” button. The green play icon appears for a few seconds then goes away. I can play a track/playlist by selecting it from the menu system and the central knob.
6. I can play music from my iPod through the MKi9200 but when I press Pause, the red “pause” icon appears and the MKi “freezes”. I have to reboot the MKi to get it to work again.
7. I have tried various options for pairing the phone such as “force AT sync” but none have worked yet."
Any clues from anyone would be very welcome. I've had the Parrot for nearly 10 years and love it. I know it still o=works as I can pair an old phone (with my SIM card in it) and it works flawlessly. There is clearly something about unofficial ROMs that it doesn't like.
For info, I have always installed Micro GAPS or lower and have tried disabling bluetooth scanning and the software "Bluetooth File Transfer (Android)" by Medieval (versions 5.2 and the latest).
Parrot say the MKi9200 is not compatible with Android 8 but I have tried various other ROMs below that with no success.
Apologies if this post is in the wrong place but it seems to be an unofficial ROM thing to me. I feel there is something in these ROMs which is not compatible with my Parrot and was hoping someone would know what that was.

Android Auto

Anyone having problems with constant disconnects with android auto?
I have latest UK firmware installed along with the latest android auto and waze on my phone.
I can connect fine , sometimes I can drive 30 minutes without a disconnect, other times it is 5 minutes.
The only way I can get it working again is if I unplug the phone from the car and reconnect.
Then this happens again.
I have not made a journey yet where the phone has not disconnected at least once.
My old phone (nokia 8) never had this problem.
Im using a good quality USB cable.
Any ideas of which settings I need to change to help this issue?
Try using the phone manager app's battery settings to set Android Auto and Waze to manage manually as to me it seems that the battery management's the issue.
Sent from my Mate 20 Pro using Tapatalk
Works fine for me, using Waze/Spotify most of the time. Using default battery optimization for Android auto.
I'm using a Huawei cable.
You could try to the one coming with the phone to test.
Hi ,
Thanks for the replies.
Im using the cable that came with the phone in my car and it still has the same problem.
I changed the settings to manage manually, but again I plugged the phone in to my car and it stopped working after 5 minutes. I had to unplug and start again before the car would see the phone again.
There are 3 sets of settings in the manage manually option. did you change any of these?
Should say that im plugging into a vauxhall Astra 2017 car with the latest software installed on my car.
Thanks again for any help.
I've only had my UK Mate 20 Pro for about 3 weeks now, but I too am having issues with Android Auto. Initially I was getting disconnects, I think this was due to the handset trying to ask me how I wanted the USB connection to be treated - charge only, transfer files, MIDI device etc. It didn't seem to matter what I chose, it always flicked back to charge only. Or, it could have been down to the third party always-on-display app(s) that I was trialling and have since deleted.
The disconnects now seem to have stopped and it's more stable for me - I don't know why, it could due to the above deletions or a recent EMUI update (I'm on 9.0.0.210), or maybe Android Auto updated?
I now have different issues with AA, in that when I connect the handset and the Android Auto home screen comes up, there's no play button showing for my Audiobook app (Listen Audiobook Player), when I click into the app and click the play button it stays on 'getting your selection' forever and nothing plays. Incidentally I can start playing a book on my handset, but AA doesn't notice that anything's changed and stays on the 'getting your selection' screen.
The only way I have found to return functionality to normal is to restart the phone and enter my pass code - this takes me back to the phone desktop and a different error message which says 'android auto can't find any supported devices to use' (or something similar), when I unplug and re-plug all works as it should again - this is all a bit of a pain to do whilst driving, or requires me to park up.
Additionally I have noticed similar issues when switching audio apps i.e. to Spotify and then to an audiobook etc., It doesn't seem to go smoothly like it used to on my S8+
I'm using a 2017 Vauxhall Astra also ?
Ive sent a message to customer services to see if they can offer any help.
Dont know if we will have to wait for a firmware update to sort this out?
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
andywright1982 said:
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
Click to expand...
Click to collapse
Do an factory reset and try it again. See if it works.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Hi, Can you all please share the model of your car ? Maybe the issue is also connected to the car, not only the M20Pro. Thank you.
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
pau1777 said:
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
Click to expand...
Click to collapse
Same car. Used a samsung a9 yesterday and worked flawlessly.
Done a factory reset on the mate and still ****s up. If it wasnt such a good camera I would be getting a different phone
I tried it on a Mercedes CLS, just for a short run. It worked fine. With non-official Huawei Cable. Just basic USB-C. Maybe I need to try for a long run to be sure about it.
Anyone tried it on a Volvo XC40-60-90 ?
Disconnects
Did you find a solution to this? my device also suffers from constant disconnects and sets the USB method to charge only and as soon as you change it just goes straight back. battery management is set to manual and all apps and phone are up to date. using it on a Vauxhall insignia 66 plate with OEM cable.
Hey guys,
The problem seems to be with a nearly full battery.
When the battery is >=92% the connection of AA drops very often.
Is anyone here with EMUI 10 to test if it's more stable?
EDIT: I've missed that today is the launch of the beta so forget my question.
Edit2: some links for the same topic.
https://support.google.com/androidauto/thread/15209528?hl=en
https://www.android-hilfe.de/forum/android-auto.3315/android-auto-verbindungsprobleme-bei-akku-ladung-ueber-90.920529.html

Categories

Resources