I find that when I want to switch from and iPhone to iPad (and vice-versa), I need to shut down Bluetooth on the device from which I’m switching. After that, I can get the new target device to recognize the Real 1s, but I often have to “forget” the Real 1s and repair and sometimes even need to reboot the new target device completely before the Reals are recognized again.
I do have the Oticon On app on both iPhone and iPad, but I would think switching BT connections should be independent of the On app which (as best I can tell) really just sits on top of the phone / iPad integration with the HAs. The On app works fine on the new target device once the new BT connection is established.
I feel like I’m missing something obvious here as switching between iPhone and iPads should be pretty seamless.
That is a common problem, I have been wearing Oticon aids since 2010 and been using the iPhone and iPad since I believe 2015. Part of it is just the nature of Bluetooth I believe, and part of it is due to the very weak signal that has to be used by the hearing aids. I have learned to just disable the Bluetooth on one device to switch to the other then once the switch has happened I reenable the Bluetooth on the device normally my phone. I can override some of it by setting the hearing aid routing to always hearing devices, this will sometimes force the switch over but with some delay.
Thanks for the responses. I did have this problem with the MFi Resounds but was hoping Oticon had solved it.
I’m still trying to find the exact amount of timing, actions required as my iPad just required about 20 seconds and a reboot to connect with the already paired Reals (iPhone BT was shut off) which is an eternity when the Reals are a foot away. I’m wondering if other BT devices in the house or my Apple Watch, TV Connector, etc are causing an issue in the session establishment. The Resound MFi issues weren’t as bad.
I suspect it will just be trial and error to figure out what works best.
Thanks, that’s very interesting and would seem to indicate an active audio stream helps the new target device (iphone or ipad) recognize it needs to launch the MFi support. I’ll have to try that as a workaround.
In 2025 with the Oticon Intents, the issue remains. I either turn the BT off on the device not wanted, allow the connection to establish on the new device, then turn BT back on, on the 1st device or briefly play a Spotify song. The reason that works is the setting to grab audio from a nearby device is turned on.
The key is ‘nearby’. Often, I use my iPad and listen to news clips, then leave the house for an errand or meeting and forget to toggle BT off, on the iPad. Then it prevents the iPhone connection from being established since the iPad is no longer ‘near’ the iPhone.
Does anyone know how to create a shortcut or an available app which would toggle BT off after a set amount of time or proximity to home? It would be great if the iPad was separated from the iPhone by a distance and the BT on the iPad would automatically turn off.
I am going to tell you my findings and opinion. The problem isn’t withe the hearing aids, the problem is in the Bluetooth design. Yes Apple trys to say it works and I should but it doesn’t. I used iPhone and iPad for 9 years and gave up snd went back to Android and Samsung phones. I have the Samsung S23 and absolutely love my setup. I have no issues with connectivity and the app stays connected to my aids. I have le audio connectivity and full hands free calls. There are a few things igave up but the hassle free connectivity still makes it worth giving up a few minor things.