I find that the multi-connection is more of a hindrance than anything else. It's not super well done and I've posted my issues with it before, most notably that streaming audio from one device and a secondary device receiving notifications results in garbled audio, skipping, etc. TBH, I don't see a large use case for two simultaneous connections, esp when it's not well done. Most of the time, I end up going into my phone and manually disabling the secondary connection.
As such, I suggest an option in settings that would allow you to disable multiple connections and enable singular connections.
Solved! Solution.
Hello mulhearn22,
Thanks for bringing your suggestion to the Bose Community.
Whilst this is not currently available as an option, I'll be happy to pass along your suggestion to our development team for consideration.
Let me know if you have any further questions.
Hello mulhearn22,
Thanks for bringing your suggestion to the Bose Community.
Whilst this is not currently available as an option, I'll be happy to pass along your suggestion to our development team for consideration.
Let me know if you have any further questions.
Great, thank you. Wasn't sure how to submit a feature request.
Incredibly sad that you cant disable this feature! There's constant choppiness when connected to both a mac computer and iphone.
And no resetting does not solve this.
LOL right! I never had a bluetooth headphone that I was like "man, I wish this connected to my laptop and my phone!"
I don’t see why this answer is marked as "solution". Is it now possible to disable the second connection? Or not?
This "feature" of 2 connections is really the worst part about my On-Ear Wireless 25. It always connects to the wrong devices. When I am in a call or listening to music, it randomly tries to connect to other devices. It it does connect to a second device, the sound quality of the first device decreases.
Turning off bluetooth on the devices is not really an option, because my computer uses bluetooth mouse and keyword.
This issue is open for many years now, I hope you can soon publish an update, so this issue can actually be solved.