Has anyone else had issues with Android Auto and this phone?
It's a complete disaster.
Google Assistant doesn't stay as the default Assistant app. It stops being the default app after two minutes so you can't even use Google Assistant on Android Auto.
Not to mention, Android Auto completely freezes in your dashboard screen if you use it for more than three minutes.
It's an absolute disaster on my end.
How has it been for you guys?
On my nex with global rom and VW touareg all is working fine. Maybe problem is with chinese devices?
Maybe... I am using the Chinese device
Same on Global Rom... Android Auto "restart" after 5min of utiliazation...
Have been using Android Auto from the day I got the phone and I must report that the above issues haven't ever surfaced.
What does happen regularly is that the music starts playing via the phone speaker on hanging up a phone calls. That's really annoying and requires disconnecting the phone from usb and reconnecting.
Anyone else facing this issue?
Bug AndroidAuto
I have the same problem, I use the Phone in Brazil with Portuguese PT (not BR) and the App seens restar when I use Waze or Maps.
Eternia said:
Same on Global Rom... Android Auto "restart" after 5min of utiliazation...
Click to expand...
Click to collapse
Have you found a fix for this? Happens to me too, Android Auto restarts every 5 mins
Can't get Android Auto to see my car at all.
Android Auto/ settings/ connected cars/ doesn't even see my Kia Forte although after much work I was able to get the Bluetooth to connect to the car, so my contacts list and phone and music are accessible on the car system. I had no problems connecting with my prior Motorola MOTO G5 Plus.
My Global edition is working perfectly with Android Auto in my Hyundai. Make sure you're using a quality USB C cable.
I've had tons of problems with Android Auto on other phones though. A lot of times, clearing the app data helps it get going again.
background power consumption
For Chinese version, make sure you allow high background power consumption for google maps or any other navigation and music apps. Since when you are using Android Auto, those apps were actually running in the background and the phone will treat them as suspicious apps and close them. This can be done in battery settings.
Got this just last week. Phone is great but i had issues with it on Android Auto. I have a the Civic FC and other phones work flawlessly (samsung, LG, etc.)
This is what i found;
1. Mate 20 Pro with AA occasionally disconnects from the car using a usb-c generic cable. There are less disconnections when using the original charging cable so i guess it is a communication issue.
2. If there is a call log entry without an entry on the contact list (meaning just the mobile entry), AA wouldnt start. It will simply stall and crash. In this case, i need to clear the call log entry to fix the crash or simply set AA permission without the contact list.
3. AA would crash if you select the phone icon. I am guessing that this is also related to the contact list issue. I could not find any fix for this thus i simply removed the "telephony permission" from the Android Auto app.
Even if i replace the dialer with the Google version, Mate 20 Pro simply crashes if you click or select the telephone icon. This approach fixed the Huawei P10 dialer issue (my previous phone).
Any temporary fix available out there ? I simply could not wait for Google or Huawei to fix these things as it will surely take some time.
Welcome to the club for 900 this phone should work with AA flawlessly
I'm very upset that the call functionality doesn't work especially coming from an iPhone X
I've logged it with Huawei but they won't do Jack about it just give you some development spiel
Great phone but ruined by the this experience
I'm. Trying to swap for an Xs max
They already fixed it with an update yesterday. It has something to do with the Voicemail settings which was missing from the previous firmware version --
https://forum.xda-developers.com/mate-20-pro/help/mate-20-pro-android-auto-call-dialer-t3866032
Hello all, new user here.
I just got Amazfit Verge, I'm using it with iPhone XR and I have a problem, the watch has constant reconnect issues, when for example I'll go out of phone range, it won't reconnect (or reconnect only one device as there are two devices visible in bluetooth menu, one for calling and contacts and one for notifications it seems). I've removed and forgot the device that is for calling and now it reconnects like 70% of time which is still no good. I didn't find any info about that in google but maybe someone has faced similar issue and found a fix or has a clue if any custom rom fixes that?
I like the watch a lot but that problem is realy annoying.
i have same problem with my verge and iphone 7. i did factory reset both devices and nothing changed. after that i synced the watch with old an android phone s3 mini and the watch perfectly worked. i think there is a problem with iOS
I have an issue that I need some help. I've been searching in the forum and internet and didn't find anything that applies. I'm not sure if this is a problem with my phone, with S9+ or Android 10. If this post is placed incorrectly, I would like to ask any mod to change it to the correct location.
I have a new S9+ phone, upgraded to official Android 10 OneUI 2.5, and then rooted with Magisk. I have much of the crapware Samsung shoved in the equipment either removed or disabled, but nothing is related with Bluetooth, AFAIK.
This phone have a very odd and annoying behaviour. It looses the Bluetooth pared devices list every time I turn off BT, and I'm forced to pair it again with any device previously paired. This happens with any other BT device - another phone, an earphone, speakers, etc. If I turn the other device BT off, and keep the phone BT on, it shows the disconnected device in the list, and when I turn it on again, it's still in the list of paired devices. Therefore, it only happens if I switch off the phone BT.
I usually have the "nearby devices BLE" crap disabled, but if I turn it on, this behaviour doesn't show - it doesn't loose the devices list. I think that might be because that "nearby devices" keeps part of Bluetooth always on, even when I switch BT off.
Please note that I don't have any other issue to operate or pair a BT device. It pairs without issues and it keeps the connection normally. My old S7 Android 8 phone still works like a charm with same devices.
I already tried the only 2 possible solutions I found for somewhat related issues; I dumped the cache and data of the Bluetooth service, and I reset all connections (WiFi+BT+Mobile) in the Settings. Nothing have solved the issue. I would do a complete factory reset, but the phone is completely configured and all apps installed and it would be a major pain if I had to start over!
Anyone can help?
When you repare what does it do?
Just a pop up asking if you want to connect?
Or it doesn't recognize the previously registered bt device?
Are you using the Wearables app?
I don't repair. I just switch off BT and it immediately forgets the previously paired devices.
In my old phone(s), each time I turn BT on, it shows a list with the paired devices, and if I connect the BT on any of these, it automatically connects. If I turn off BT in the phone and on again, it will show the paired devices list and they are still there.
That doesn't happen with the new phone. I switch BT on, it shows an empty list of paired or available devices. It start to scan for new devices. If I switch on my BT earphone (for example), it finds it, I can pair them and use the earphone perfectly. If I switch off and on again the earphone, the device is still listed. If I switch BT off and on again IN THE PHONE, the list of paired and available devices is empty. I have to scan, find and pair the earphone (or any other device) to use them again. Every time.
I don't have any smart watch or similar. My earphone is a Jabra 25 but that happens with another phone or device. I have the Samsung wearables apps freezed. I will unfreeze them to see if it changes anything.
BTW... I found this post (https://forum.xda-developers.com/t/bluetooth-pairing-gone-adter-reboot-phone.4004833/) and I tried to install Magisk libsecure_storage, but it said "installation failed" and it still doesn't work.
Wearable Manager Installer was not (and is not) frozen.
I defrosted ANT+ and ANT Radio stuff and Device Services, but it didn't work. I also have SmartThings crap frozen, but I don't think it's related with this issue.
On the other hand, Magisk is 23.0 and I have BusyBox, MagiskHide Props Config and Systemless Hosts Modules installed, if that's relevant.
phoenix.pt said:
Wearable Manager Installer was not (and is not) frozen.
I defrosted ANT+ and ANT Radio stuff and Device Services, but it didn't work. I also have SmartThings crap frozen, but I don't think it's related with this issue.
On the other hand, Magisk is 23.0 and I have BusyBox, MagiskHide Props Config and Systemless Hosts Modules installed, if that's relevant.
Click to expand...
Click to collapse
Was Wearables updated recently?
The last update broke mine and it was behaving similar to yours. I had to reinstall a copy of a previous version and then firewall block it's updating IP. It's a handful.
Galaxy Buds, Buds+ Set up
Install the Galaxy Wearable and Galaxy Buds software. Update software and Buds firmware, this is important because the old versions sound sucks. Turn on/go to Developer Options in Settings and on the Bluetooth Codec setting toggle on Samsung's...
forum.xda-developers.com
I really don't know... I have been updating most apps and services in the last week or two, to prepare my new phone, so probably yes. What is exactly the wearables app you talk about? "Wearable Manager Installer"? That's the only "wear" app I have.
Both. Had to reinstall both of them or at least I did. The new Galaxy Wearables interface sucked.
Galaxy Wearables:
Known good versions:
Wearables Manager Installer, Version 1.1.15.13054
Galaxy Wearables, Version 2.2.33.20082161
I suppose I don't need Galaxy Wearables at all, because I don't have gear from Samsung, right? Only the installer?
Indeed my version of Installer is 2.1.01.19006
phoenix.pt said:
I suppose I don't need Galaxy Wearables at all, because I don't have gear from Samsung, right? Only the installer?
Indeed my version of Installer is 2.1.01.19006
Click to expand...
Click to collapse
Yeah, you need the Installer as it loads the drivers I think.
Wearables is intended for the Buds and such. It also provides firmware flash updates for them
I don't know the buggy installer or Wearables version numbers.
I had multiple problems including connectivity and bad audio quality except for phone calls
I keep installable backup copies via ApkExport so I was able uninstall then reinstall the old versions. Otherwise I been more boned... more than I was already. I was pissed.
Try this...
Uninstall the newer version first. You'll may need to block the IP address* I gave in my Buds+ thread to prevent an auto update.
Firewall's log: (UID 10339) [18.203.4.139]
Hello everyone
I am having Xiaomi MI 11 lite 5G and Galaxy Watch. I am having problem with losing bluetooth connection between them. I searched a lot of forums about this solution but without any luck.
I’ve already tried resetting and reinstalling everything. I’ve set the settings for all three samsung apps to autostart and disabled battery optimization for them, also made an exception in the security memory cleaner app.
But the watch is constantly losing connection. It is interesting that one day he works normally, other day he constantly loses. The loss of a connection becomes more frequent, as if it is getting worse.
When i open galaxy wearable app it says reconnect but nothing happen so i have to close app disable and enable bluetooth and then open app and connect.
I doubt there is a problem with some application because when I disable / enable the bluetooth, watch vibrates again to signal that the connection is lost, although it already has a lost connection icon on the watch.
Does anyone have similar difficulties or a solution to this problem?
Just updated to miui 13 and I also have a gear 3 watch, experienced the same issues but after update haven't found a single disconection, I'm using xiaomi.eu miui 13
Thank you for your reply.
Last week I updatetet to xiaomi.eu miui 13.
Now everything works as it should.