QC 35 II unable to autoconnect to Android when configured as "Use for Calls" only
Bose product name
QuietComfort 35 II
latest as of 19-Jan-2021: 4.8.1
Uninstalled the app, since I see no benefit from it. The behavior described here happens irrespectively if the app is installed, or not.
What devices were you using that were affected and what version are they on
Samsung Galaxy S20+, SM-G985F/DS, Android 11, Kernel 4.19.87-20699066 (7-Jan-2021), but previous versions had the same problem.
Detailed description of the issue and steps to reproduce
The bluetooth headset's primary usecase is for confcalls.
I need it to work 100% reliably in that usecase.
If I leave the default configuration, after pairing with the phone, then they connect for both Calls and Audio. That results in me losing the audio from on ongoing confcall whenever some app on my phone decides to make a notification sound, since the headset automaticaly switches audio to that app, and never returns to the ongoing confcall. The way this works in Android, is, that even if the Headset is no longer connected to the confcall (calls app), the calls app does not output via the speakers on the phone either. The end result is, that because of a 1 second ping from some other app, I randomly lose connection to my ongoing important confcall - often without even realizing, that it happened, since I simply do not hear anything, and don't know, if nobody is just saying anything, or I got disconnected, or my headset decided to switch to a different app as audio source.
!! The absurdity of that happening on a 200+ Eur premium headset is mind boggling !!
As a workaround, I have unpaired the headset from my laptop, left it paired only with my phone, and I have therefore switched off the "Use for Audio" toggle for the QC 35 II on my phone, leaving it only as "Use for Calls". This works fine to get undisturbed confcalls, *but* at the cost of the Headset no longer connecting to the phone automatically, after I turn on the Headset.
More specifically: After turning on the QC 35 II headset, it says "Battery 100%. Connected to Samsung Galaxy S20." and 0.5 second later: "Samsung Galaxy S20 disconnected". And I have to manually navigate to the bluetooth menu, find the QC 35 II, and click it, so that it actually connects, and I can use it for the upcoming confcall.
I refuse to accept this clumsy solution with a premium headset, and strongly hope, that it is just a user error, that can be fixed .. and therefore I am open for suggestions.
What environment do you experience the issue in?
Irrelevant to the problem.
When did you start to experience the issue? Did it work correctly previously?
No, this is how it seems to be designed to "work".
Any troubleshooting steps you took
Yes, already described above, in the Problem description.
I did as well update the firmware to the latest version, un-paired and re-paired the headset with the phone, and as well uninstalled the Bose app - just in case it was causing some interference with the Android bluetooth driver .. Nothing helped.