Pairing third-party Bluetooth transmitters with N7

With regards to a third party audio transmitter, the issue is whether the phone (with an app) is able to receive the BT stream and then whether the Cochlear app is able to pick it up and transmit it to the N7.

If it cannot, another option is to attach a BT receiver to the phone via the audio port so that the BT communication (sound streaming) happens between two external BT devices (one transmitter and one receiver) and the phone will receive an audio signal. This is a bit more cumbersome, but it is more likely to work. What I am not entirely sure about is whether the phone will handle the audio signal through its audio port.

The app does not transmit the signal. I’m not trying to argue with you but to reduce confusion. The communication with the app (sorry I’m not an engineer and may not be using proper technical language) is by small data packets using Low Energy Bluetooth. Unless somebody has used “magic sauce” like Apple’s Made for iPhone or Android’s ASHA, the phones can’t stream directly to Cochlear device. As others have mentioned, introducing other devices into the mix contributes to latency which could be an issue with synchronizing sound and lip movements while watching TV.

@MDB said:

Unless somebody has used “magic sauce” like Apple’s Made for iPhone or Android’s ASHA, the phones can’t stream directly to Cochlear device.

This is exactly correct. Cochlear streams with iOS or Android 10 or higher, plain simple.
Using this protocol will give great results.

@MDB said:

The app does not transmit the signal. I’m not trying to argue with you but to reduce confusion. The communication with the app (sorry I’m not an engineer and may not be using proper technical language) is by small data packets using Low Energy Bluetooth. Unless somebody has used “magic sauce” like Apple’s Made for iPhone or Android’s ASHA, the phones can’t stream directly to Cochlear device. As others have mentioned, introducing other devices into the mix contributes to latency which could be an issue with synchronizing sound and lip movements while watching TV.

@MDB, it’s ok to argue with me. It is my preferred way to learn. I am not an engineer either, but I have (or I hope I still have ) a full understanding of the difference between hardware and software. Of course, it is not the app that is transmitting the packets, it “only” controls the transmission on the user level. So the questions are really about what the hardware can possibly do (even if not designed to do so), and finding an app that realizes that possibility.

It is for that reason I did a 180 to turn away from using (or even trying to understand) the Cochlear BT, and use other technology to extend its capabilities. It is a bit like subcontracting certain tasks. I assume a working connection between the N7 and the phone via BT, and use the phone’s and other external devices (computer, third party BT devices etc) to bypass the need of a Cochlear TV adapter… and save $500 for Xmas presents.

Of course, the introduction of more devices will increases latency and that may cause some problem with lip reading. However, I am sure all with severe hearing loss would agree that it is infinitely better to listen to a movie (with latency) rather than reading subtitle. Further, it is the very reason for having direct streaming into a CI, to reduce the need for lip reading. Latency becomes an issue only when there are more than one source of sound (for example, connecting and listening to my acoustic guitar via BT)
Cheers

Another question raised by this discussion. I live in the “Phonak Universe” and know how their stuff works but do not live in the “Resound/Cochlear” Universe. In the Phonak Universe, the app is not needed to stream. I stream from my computers to my aids with my phone and app off. Is the app needed in the Resound/Cochlear Universe to be able to stream?

@Shenman said:

Finally I identified 4 different ways to achieve what I intended to. One is a definite answer, another is a “highly likely” candidate, and two others are in the “too hard basket”.

… and you couldn’t take a few minutes out of your busy day to tell us what those solutions are. You got what you came for and exit stage left? You clearly don’t know how forums like this are supposed to work. I know you’re still watching for a reaction to your last post by the way, 'cause that’s the kind of guy you are. I’d love to save it’s been fun, but it hasn’t. xxx

For the time being, there are only two protocols allowing to stream audio to the cochlear latest processors and GN Resound hearing aids.

• The first one is a proprietary protocol only compatible with Apple products (iPad. iPhones) or GN Resound or cochlear wireless accessories (phone clip, mini mic, tv streamer), probably based on the lower level Bluetooth Low Energy protocol or at least using the same RF frequencies and a similar modulation scheme. The specification of this proprietary protocol is not public, it is only available after paying a license.
• The second one is a protocol defined by Google. It is Open source and based on Bluetooth Low Energy, but as far I know, only Google, Samsung, GN Resound and Cochlear implemented this protocols in their devices. And the only audio sources that supports this protocol are rather high end Android smartphones manufactured by Google and Samsung. There are no cheap transmitters despite the protocol is open source.

The reason is that a third protocol not compatible with these two protocols has been integrated to next versions of the Bluetooth standard (Bluetooth version 5.2). This audio streaming protocol based on Bluetooth Low Energy will be recognised as a non proprietary standard and will be supported by the major Bluetooth chips and IP manufacturers. It will use a better audio codec requiring less bandwidth than the two existing protocols. But it is unlikely that il will be supported by the current hearing aids and cochlear implant processors : only new generation devices will implement it. Nevertheless, this prevent most audio devices manufacturers to invest in the development of the software required to support the Google protocol for their devices despite it is open source : it is not so simple (and therefore expensive) and they know that it will become obsolete rather quickly …

When using your pixel 3, how far can you go from the phone before it the streaming stops working ? For the time being I am using an iPad to listen to the radio, but I would like to replace my old android phone by a newer android phone instead of an iPhone. But I want to make sure that I can move at the same distance from this phone as from the iPad, else I will buy an iPhone …

The Google Pixel 3 will stream to my Nucleus 7 straight line of sight, a little over 50 feet.

@mleroy003 said:

When using your pixel 3, how far can you go from the phone before it the streaming stops working ?

Thank you very much. Quite similar to my iPad, but it is significantly lower when there is a wall in the signal path. With 1 or 2 walls in the path, I can stream only up to 20/25 feet, sometimes less depending on the wall. But the protocol is really robust: after a loss of streaming, if I move a bit closer, it reconnects automatically.