Related
Has anyone else been unable to make phone calls after connecting to your vehicle's bluetooth? Most of the time, I can make phone calls without issue. Sometimes, I can't even hear the call ring when I'm connected to bluetooth. Occasionally, when I turn my vehicle off, the call goes silent instead of transferring to the earpiece on the phone. The only way I can fix the issue is rebooting the phone. This has become increasingly frustrating for me, since the issue is so inconsistent.
I'm running the stock ROM, rooted and un-encrypted.
Thanks!
Same here
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
I am having issues also. Just today, my phone shows I am connected to my Pioneer Navi head unit, and the Pioneer shows connected to my phone. I proceed to make a call. The audio on my radio mutes as it should, and nothing. No ringing, no busy signal nothing. so i hang up and try three more times. on that third retry, i heard the other party faintly, realizing that even though my radio muted and shows BT connected, the call went through the ear speaker on the phone. When I hung up the phone, my radio unmuted.
Last week, I was having issues where i couldnt hear any rings or busy signals. It would be silent for 20 seconds or so, then i hear the other party say "hello".
I honestly thought it was my head unit, since it is about 4 years old. But now I see others with similar issues on other brand bluetooth systems in their cars.
robbnice said:
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
Click to expand...
Click to collapse
I just got my N6 today and I'm having trouble with My Ford Touch as well. I can get it to pair and play music, but it won't "connect" to my phone. It's odd because my N5 works fine with it. I would assume the N6 wouldn't be different.
We probably have to wait for an update from Ford, which will probably take months...
EDIT: Well I decided to try it again. I deleted the Nexus 6 entry as well as the Nexus 5 entry. Went through the pairing process again and it worked as intended. Not sure what happened the first time.
I ran into the same problem as others where my N5 worked flawlessly with my Ford Sync in my fusion, but the N6 is terrible.
I love the phone, but this is really annoying. I get into the car and sometimes it connects immediately, other times I have to turn off and back on the bluetooth about 3 times for it to finally connect. Very weird. Ford offers an upgrade to my Sync system, but wants $50 to do the upgrade. Pass.
I might try what the other person did and delete all entries for phones and pair it again. Unfortunately, the weather is pretty bad outside, so it might need to wait a short bit.
Has anyone else had luck re-pairing with their car and had reliable connections?
I use Ford Sync.
robbnice said:
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
Click to expand...
Click to collapse
I use Ford Sync, and everything works as expected. I am Stock and unrooted. I guess it would come down to what version of Sync. Mine is from 2012. No touch screen. I also delete all other entries on the system and start from scratch making sure that the N6 is the main device.
If I can wake up the screen on my own, outgoing calls work fine
PaisanNYC said:
I am having issues also. Just today, my phone shows I am connected to my Pioneer Navi head unit, and the Pioneer shows connected to my phone. I proceed to make a call. The audio on my radio mutes as it should, and nothing. No ringing, no busy signal nothing. so i hang up and try three more times. on that third retry, i heard the other party faintly, realizing that even though my radio muted and shows BT connected, the call went through the ear speaker on the phone. When I hung up the phone, my radio unmuted.
Last week, I was having issues where i couldnt hear any rings or busy signals. It would be silent for 20 seconds or so, then i hear the other party say "hello".
I honestly thought it was my head unit, since it is about 4 years old. But now I see others with similar issues on other brand bluetooth systems in their cars.
Click to expand...
Click to collapse
I have a Nexus 6 running Benzo ROM (5.1.1) and I have a GPS Nuvi 3580 bluetooth-enabled which I want to use to make calls while driving. I have added this device to my trusted devices so my phone unlocks as soon as it connected to it.
If my phone screen is on, then I'm able to call anyone from the bluetooth device, no issues. But as soon as my screen goes off, I can't make calls and when I switch on the screen on my own, I see a message "Process system isn't responding. Wait or close?"
Irrespective of what I select on this message, the call goes through. But it totally defeats the purpose of handsfree bluetooth mode. Is there something that is not allowing the bluetooth device to wake my phone up.
Also when I receive an incoming call, I see the notification on my GPS but I can't receive the call in one go. It takes multiple calls for it go through. I have also noticed that my bluetooth device keeps disconnecting and connecting without any change on either the phone or the GPS side.
androidfan91 said:
I have a Nexus 6 running Benzo ROM (5.1.1) and I have a GPS Nuvi 3580 bluetooth-enabled which I want to use to make calls while driving. I have added this device to my trusted devices so my phone unlocks as soon as it connected to it.
If my phone screen is on, then I'm able to call anyone from the bluetooth device, no issues. But as soon as my screen goes off, I can't make calls and when I switch on the screen on my own, I see a message "Process system isn't responding. Wait or close?"
Irrespective of what I select on this message, the call goes through. But it totally defeats the purpose of handsfree bluetooth mode. Is there something that is not allowing the bluetooth device to wake my phone up.
Also when I receive an incoming call, I see the notification on my GPS but I can't receive the call in one go. It takes multiple calls for it go through. I have also noticed that my bluetooth device keeps disconnecting and connecting without any change on either the phone or the GPS side.
Click to expand...
Click to collapse
Since I last made that post you quoted, i purchased and installed a 2015 model of the Pioneer AVIC-8100NEX. It has Android Auto, but can be used with the regular Pioneer UI also. I have had no issues anymore with this new radio. Maybe the BT protocol in the radio is newer? Im not that tech savvy to know. But the 2015 radio had no issues with BT calls anymore, on Pioneer's UI or Android Auto's UI.
Hi All,
I've been extremely excited about the integration of my smartphone with my car for a while. Almost anyone who would be in the market for a motor vehicle with an advanced head unit would also already own a smartphone with data access.
However, like any new use of technology, there are growing pains and Android Auto is no different. I have struggled through a few issues already and continue to grapple with others. A huge difficulty I had was simply finding discussion threads. Do I look on sites that focus on cars? On Android Auto? On Android OS?
So here it is. I'm starting a thread to pull together the most common problems and their solutions. Also, please note - I am not an expert in any of these things, just a user. I will give credit where I have a source but I am just gathering the info into one place and adding it to my own observations.
I haven't decided how this thread is going to look or if it will be small or big, so I will save the first few message placeholders in case and I will add known problems, work-arounds, and identified solutions as they come.
Hopefully this helps out some other users!
Troubleshooting:
I strongly suggest you make sure you have a good quality USB cable and confirm that you are able to connect your phone to your computer and transfer a file (some cables will allow charging but not data transfer).
1. Problem: Bluetooth won't pair, won't connect, etc.
Possible Solution:
It appears that Android Auto will attempt to create a BT profile. So
a) Delete the pairing on your cell phone
b) Delete the pairing on your car head unit
c) Turn OFF bluetooth on your phone
d) Plug your phone into your car's head unit. Depending on your settings, you may need to tell your car to launch Android Auto and you may need to select the device. If so, make sure you are selecting it in Android Auto (NOT Bluetooth pairing). Respond appropriately to any requests for authorization on your phone and car.
This should leave you with a properly paired device and car.
2. Problem: Every time I launch Android Auto, I have to pair my phone again!
Work-around: Once you have a working AA connection between the car and your device, go into the settings in the Android Auto app on your device and turn off the option to "Add new cars to Android Auto."
3. Problem: Android Auto notifies me of a new message but won't read it out loud/but starts to read it and cuts off.
It looks like there is a conflict between Google Now, Android Auto, and the Bluetooth handoff with the car head unit. Kudos to XDA member BuildaWall for discovering that turning off the BT headset option in Google Now fixed it for some people. I did a little more testing and found that forcing Android Auto to make your phone the primary source of audio seems to be the other piece.
UPDATE:I applied the August CM-13 Snapshot and this workaround no longer fixes the problem. I have reheaded it as a possible work-around as it might fix the issue for people on slightly older ROMs
UPDATE Sept 27/2016: I have upgraded to stock Nougat (Android 7). This issue still exists. However, after reading this XDA article, I tested an accessibility option. AA began reading the messages once again.
Possible Work-arounds:
A) Several people reported that their Media volume on their phone was being changed to zero when they plugged into AA. Some also reported that turning USB Debugging OFF fixed this issue. If you don't know what USB debugging is, don't worry about it; you would have to have intentionally turned it on. For volume, tap your volume rocker but then tap the drop down on the pop up volume notification.. It will expand to multiple volume sliders. For simplicity, make sure none are zero.
B) On your phone, go into Google Now, Options, Settings, Voice and then turn off Bluetooth Headset. This was reported to help by some but not didn't help for me.
C) On your car's head unit, in Android Auto, select a music option (I have Spotify and Google Play Music, but I think any audio source app within AA will work). If you don't want to listen to anything, just play and then pause/stop it but you CANNOT go back to the car as a primary source (eg radio or sirusXM).
D) On Nougat (Android 7) go to settings, accessibility, and enable one of the options (I have tested Voice Access, but in theory, activating any accessibility option should reactivate the message reading in AA.
4. Reported with work-around by @ReppinTheSouth - Android auto either being laggy or flat-out disconnecting
ReppinTheSouth observed this on a Pioneer avh 4100 and a galaxy s4 and reported August 7, 2016
Suggested Work-Around: Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
5. Reported by @ReppinTheSouth - When driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive.
I'm not listing this as a work-around, as it doesn't resolve the problem, but is still good to know: @ReppinTheSouth advises: This only happens when voice commands are enabled & Unplugging and replugging the phone gets the head unit out of its frozen state.
More to come!
Tips and Tricks:
I will use this page to list tips to improve performance or usability that don't fit under troubleshooting.
1. Keeping the phone screen alive and accessible.
Please exercise safe driving habits.
TL; DR:
Turn on Developer options
Turn on Stay Awake
Optional: if you have a security lock you may want to add your car Bluetooth as a trusted device for smart lock so it doesn't lock you out.
Details:
Android Auto changes your screen timeout to 15 seconds every time it is activated. When combined with its flaws with hangouts chat notification (no groups, can't initiate a new chat without certain contact book entries, can't access chats that began before connecting to AA) it is VERY frustrating.
Access the Developer Options menu
Settings >>> About Phone
Scroll to the bottom and tap the Build Number option seven times in a row. You will get some sort of message saying you have access to developer options. You only need to do this once.
Settings >>> Developer Options
Make sure they are turned on. Next turn on the Stay Awake option.
Your phone will now allow dimming but won't turn off the display.
Optional:
If you use a security lock on your device, you may want to authorize your car Bluetooth connection as a trusted device under smart lock so it won't lock while connected.
==============================
Links to Other Resources:
https://forums.oneplus.net/threads/...to-connected-to-the-cara-infotainment.488786/
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work.... I changed my phone Bluetooth Headset setting to off and I was playing my spotify music through Android Auto. Am I forgetting something here? what versions of AA and Whatsapp do you use?
Good thread and it is much needed as far as I am concerned. I have a Pioneer avh 4100 and a galaxy s4. One of the issues I have had is with Android auto either being laggy or flat-out disconnecting for no reason. One of the things I have noticed is Android auto seems to be a resource hog. Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
The other issue I'm having which I can't solve is when driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive. I have to unplug my phone and then plug it back up to get it to work. This only happens when voice commands are enabled. I have not been able to resolve this issue.
Sent from my SPH-L720T using XDA-Developers mobile app
NLatuny said:
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work
Click to expand...
Click to collapse
Hi NLatuny & ReppinTheSouth!
@NLatuny - Thanks for the info. I just updated my Nexus 6p to the latest (august 2016) CM13 Snapshot, and the work-around no longer fixes the problem for me either. I've updated the original post. I think your request for version numbers is probably a good idea moving forward. I will update the original post to suggest that people include that in their posts.
@ReppinTheSouth - Thanks! I will look at adding those problems and your possible solutions for the lag to the top of the thread
Might be good to add a list of things you can and cannot do. For example, I found the other day through just trying you could ask various questions.
How old is (enter famous person here). = Correct answer.
I need to remember some of the other ones I've done. Good thread.
---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------
Perhaps also add how to get into Developer Mode, and what the settings in there do? The Force Day or Night mode thing is super useful.
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
duze76 said:
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
Click to expand...
Click to collapse
Check your permissions for Android Auto, you may have missed a few.
You can also uninstall and reinstall it.
I have tried all that, with no luck unfortunately
Having had a courtesy car for a few days that had an android auto system in I'm looking to purchase an android auto headunit for my car, probably after Christmas.
Until then I've been using my handsets connected to the aux input on my factory system. However since I got my Pixel handset last week I've encountered a couple of issues that weren't an issue on my m9 handset previously. I've reported then to the relevant support sites but as yet have received no response, so thought I would try you knowledgeable lot.
Firstly, when making or recurving phone calls with the aux cable connected the Pixel defaults to using the loudspeaker on the handset rather than putting through the aux to my car speakers.
Secondly, when receiving a message on WhatsApp i touch the screen too get it to read the message, it does so fine, then tells me I can press the mic soon symbol and say reply. When I do so I'm told "this chat app is not installed or needs an update". The app is installed and is up to date. I can send WhatsApp messages by saying "send a WhatsApp message to...." but can't reply.
Lastly, when I ask it to play specific tracks on Spotify it often comes back with no search results. Songs that I used to ask it to play regularly on my previous device come back as no search results found. Searching manually the tracks are there and can be played. And it isn't all tracks, some tracks are found without issue.
Thanks in advance.
Also hope this is in the right thread, I notice you seem to be taking mainly about the in car systems but as it can now be used on most android phones without a dedicated in car system I figured many would be doing so.
Hi folks, sorry for the absence. My N6P died on me in November and was sent away for warranty repair. Long story short, I'm very disappointed with Huawei and futuretel. Two months later, the process ended with me owning an unfixed Nexus 6P which is still under warranty until February 2017. It has a defective motherboard according the repair center but they will not repair it. So, after 2 months of making do with an iPhone 6 with a broken screen (wife's old phone), I have moved on to a One Plus 3T.
Irritatingly, Apple Carplay worked flawlessly for that time. Typical of Apple it was very locked down and had limited options. But in fairness, it executed those few features very well. Come on Google!
[/end rant]
I'm back and will try to get the thread up to date.
MM
Sent from my ONEPLUS A3000 using Tapatalk
Hello, thank you very much for this information, is very useful.
In my case, I have a Le Pro 3 X720 and is nightmare with AA, when I plug the phone on my Hyundai car the phone only charge so I had to change their ROM to lineage is 14.1 (Android 7.1.2) and with this AA starts quickly but after 5 minutes the screen is freeze then change the cable but it doesn't work, I change the cable again with the same result, so I back to use the original leeco cable and change their ROM again, with the same result, after 5 minutes the screen is freeze, the last one is AICP 12.1 (Android 7.1.2).
Do you know how to fix this?
Thank you in advance for your response.
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
mikefavro said:
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
Click to expand...
Click to collapse
Hi Mike,
You should say what phone and android version you are using. I have used both a One Plus 3T on Oreo beta and an LG V30 on 7.1.2.
The screen timeout sets to 15 sec when I plug in, but returns to normal when I unplug.
Sent from my LG-H933 using Tapatalk
I recently purchased a new VW car and have been using Android Auto on the built in display. The first time I used it it all worked perfectly, since then it hasn't. My Android Auto no longer gives me notifications when I receive texts. And if they do show up on the home screen and I click the play button to read them, it shows the four dots as if its thinking but nothing happens and I have to cancel out of it.
Additionally, I've noticed that my bluetooth smart lock doesn't seem to be working at all. Every time I connect it asks if I want to add my car to my trusted devices. Each time I say yes but it NEVER seems to save it. It will then later sometimes prompt for permission to read my messages. To this I again say yes but it doesn't seem to make the message issue go away even after I do this. I am not sure if these two issues are related (I'm hoping they are).
Can anyone tell me why the hell my smart lock can't seem to register and remember my car? And why wont android auto read my messages properly? (Pixel XL. Phone calls and navigation all are working properly)
Same issue here
You have to give Android Auto all permissions it asks for at the first start. And be sure to use a very good cable. There are many USB C cables on market which are not fully supporting USB C features and the system do expect them.
I'm in the same situation with my VW Atlas. Problem is with both my Pixel (running Android O) and my wife's Nexus 6p (running Nougat). I have given it all permissions, including some that it didn't ask for. I also have been using the little 4 inch cord that came with the 6p, so the cable or its length should not be an issue. In addition to the above, my car also forgets its bluetooth pairings if I try to connect the AA cable before the bluetooth has connected. I've been learning to do that but sometimes I forget. It's got to be an issue with the VW software.
I have come across these issues myself in a Golf Mk7 both with a Motorola Droid Turbo and now with a Google Pixel 3 XL.
In the case of getting Android Auto to read/send messages where you just get the four dots bouncing up and down and doing nothing else, that's a setting with the Google Assistant app. Go into that app on your phone (the round G icon) and drill into settings and under Voice >> Voice Match, make sure "OK Google" detection is turned on. Even though you might not be actually using it, it has to be turned on for this to work. Totally lame and non-intuitive, but that's what fixed that for me.
As for the car falling out of your Smart Lock and for repeatedly prompting you for permission to access your text messages, I have only had this issue with AA in my VW and not in other cars, so it's a VW-specific issue and something to do with the bluetooth hardware. I do not have a fix for it but the workaround is you must have BT turned on on your phone first and let it connect fully to your car OUTSIDE of AA. Make sure at that point you permit text message access (if prompted) and check your Smart Lock and add your car to it if needed. Then going forward whenever you connect to your car you MUST let BT connect fully first before you plug in and fire up AA. It's unfortunate that you can't just plug in and go w/o waiting for BT first but that's the only way I've gotten this to work without re-prompting me for SMS access permissions and Smart Lock.
Good luck!
Dear all
First post so here goes. Had my 7 plus exactly a week.
Specs as follows:
Model TA 1055
Android 8.1
1st June 2018 Security patch
unrooted but themed with Substratum (Swift Black)
So my phone won't detect either my amazon bluetooth adapter plugged into my bedside radio or my creative bluetooth speakers. My lenovo p2 can find these without issue. Strangely it can connect to my PC's bluetooth which gives a passcode. I've cleared bluetooth cache and still not fixed. Anybody else had bluetooth issues?
TA-1046 here with June patch and I have bluetooth issues as well.
I was not able to connect my Gear S3 smartwatch to my phone, untill I decided to turn off BT and turn it back on again.
Suddenly it worked.
Then I was not able to update my S3 apps from the Samsung App Store, untill I stopped BT and turned it back on again.
It seems to me that there is a BT issues in the June patch.
How it was before, I don't know as I received this phone 2 days ago and it updated automatically to June update.
Sorry for adding more negativity to this forum than assistance.
I am also having similar problem with connecting to my LG sound bar. It picks it up when i search, saves it but does not connect.
BT issues
Well unfortunately I have to say same. BT even can't see any device during scanning. Other devices each between other works. Other devices also see N7+ and can pair with it. Seems like scanning doesn't work for me on N7+.
I tried reset networks, clear BT cache couple of times - didn't changed anything. Still wanna avoid factory reset.
No mods, no root.
I'm bit surprised (in the sad way) by this device :-/
In the meantime BT has worked quite well for a couple of days, untill today.....
I could connect to my Gear S3, but not much later I notice new notifications on my phone but no popup on my watch.
It turned out that BT was not connected anymore.
Manually connected and the same process happens again.
Untill I rebooted my phone. From then on, my watch stayed paired with the phone and didn't loose connection.
speedme said:
In the meantime BT has worked quite well for a couple of days, untill today.....
I could connect to my Gear S3, but not much later I notice new notifications on my phone but no popup on my watch.
It turned out that BT was not connected anymore.
Manually connected and the same process happens again.
Untill I rebooted my phone. From then on, my watch stayed paired with the phone and didn't loose connection.
Click to expand...
Click to collapse
I lose the connection to my Gear S3 several times a day.
AlfredENeumann said:
I lose the connection to my Gear S3 several times a day.
Click to expand...
Click to collapse
Try resetting your Gear S3 to factory defaults and remove BT settings on phone.
(also clear BT cache).
I had to set up my watch a couple of times.
Still it disconnects sometimes, but then a normal reboot of the phone helps to get the connection back.
Submitted this to another thread, but I'll copy paste it here.
I recently got Bluetooth headphones and found that playback easily got choppy if a part of my body was in between my headset and phone, or if the phone got locked. I did find a solution to this however, and not sure if it would work for everyone that has Bluetooth issues as well.
It seems as if Bluetooth has its own app on Android 8.1, and due to this, it's getting managed by Doze or the automatic app power saving that's on by default. I switched off battery management using the following steps:
1. Go to Settings
2. Apps & Notifications
3. Tap on the option that says "See all x apps"
4. Tap on the top right hand 3 dots.
5. Tap on "Show system"
6. Scroll down until you find "Bluetooth" and tap on it
7. Tap on Battery
8. Tap on Battery Optimisation
9. Press the blue dropdown that should say "Not optimised", and select "All apps"
10. Find Bluetooth again, tap on it.
11. Optimise should be ticked, tick "Don't Optimise" instead, then press Done.
My Nokia 7 plus cannot find other Bluetooth devices.
I cleared cache, went to battery optimisation settings, ticked on the Bluetooth icon and selected *"Don't optimise"* turned on my Bluetooth to search for other devices and still this same problem persists. Can't find other Bluetooth devices including phones, tablets and headsets. I'm really confused on why there should be such a problem. I don't want to Reset to Factory settings. But I'm not being left with any other choice. I'm so upset that I have to spend so much and yet other cheap phones can search for other devices so easily.. please I need a solution immediately
Hey guys,
there is a feature cut in the Dual Audio functionality since Android 10. For most people, this might be not a big thing, but for people who are using dual audio while they workout, this feature cut might be very annoying.
The dual audio function of Android 8.x or 9.x was ablet to reconnect to both connected bluetooth speakers/headphones when the connection got lost, for example because the distance between the mobile phone and one of the headphones was to big or something like that. Also, when you switched on two paired bluetooth headsets, Android 8 and 9 was able to connect to both devices automatically.
Since Android 10, only one headset can connect automatically to the note 9. I always have to connect the second device manually. Once this is done and the connection to one of the two devices disconnects for some kind of reason, you have to reconnect the second device manually again.
One more annoying thing is, that when you are connected with bluetooth headset 1 to the mobile phone and activate bluetooth headset 2, the active connection will switch from headset 1 to headset 2, which means its possible to highjack the connection between note 9 and headset 1 with a paired device.
This is very annoying during a workout, because nobody wants to pause the workout to reconnect the second bluetooth device again, espacially if you are carrying the device during a run in a bag of your clothes, or a saddle bag, in you bag during a workout at the studio...
Are there any solutions to get the automatic functionality from Android 8 or 9 back? As far as i can see, this problem is also on all other samsung devices with android 10 and dual audio functionality. This issue came to alle devices since Android 10 with One UI 1.x.
This problem is adressed in the german samsung community forum, but till now, without a solution:
https://eu.community.samsung.com/t5...-10/td-p/1451023/jump-to/first-unread-message