Okay. So it appears that the version 1.4.3 firmware DOES fix the issue with connecting to the ConnectClip. I will keep testing it, but after an initial glitch with my More HAs not talking to each other, there have been no further issues. Has anyone else been able to get an update to firmware version 1.4.3 ?
I’ve used 1.4.3 firmware and in my case, it did not fix the problem. I sent my hearing aids to be downgraded back to 1.3.0 because 1.4.3 firmware did not work reliably.
The drop-outs are very inconsistent. Sometimes the hearing aids work for days or weeks. Other times, they don’t work at all.
Yeah. Mine stopped working correctly today. I am back to the problem of random disconnection from the ConnectClip, just like before. So firmware 1.4.3 is a no-go. My Oticon Mores are only about 8 months old, so I am going back to the vendor to request they be replaced with the equivalent Oticon Opn S-R model.
I think a better solution is to send back your More to have Oticon revert them back to firmware 1.3.0 than to switch to the OPN S-R. At least then it’s not a major downgrade back to the older generation of hearing aid, but just a temporary firmware version setback until Oticon figures out how to fix it for good with a newer firmware on the More.
1 Like
This is not a sure fix. When I originally got More hearing aids, they were at 1.3.0 and they worked fine with the ConnectClip. They weren’t at 1.3.0 for very long before they were upgraded. After being upgraded, I started to experience the audio drop-outs. After trying several newer firmware versions, they were sent back to be downgraded to 1.3.0. I found after using them for a few weeks at 1.3.0 that the same problems happened. So in my experience, which may not be the same as others, neither More nor Real work reliably with the ConnectClip. Opn S are very reliable, however. I have never experienced such problems with my Opn S hearing aids.
As of the most recent report from Oticon, they have identified the cause of the drop-outs in Real hearing aids and will have a fix, but they have not identified the cause of the drop-outs in More hearing aids. This is contradictory to what they originally told me regarding More hearing aids. I had previously understood they had identified the cause and were preparing a firmware upgrade for More hearing aids. For this reason, I returned my More hearing aids and exchanged them for Real hearing aids. I have an outer ear infection, so I haven’t been able to try them with the ConnectClip since I got them.
1 Like
Wow, what a headache! Thanks for clarifying.
2 Likes
I have read many of the experiences above. I want to share mine during the last five months.
I have destroyed three ConnectClip and two mobile phones.
After analysing the events, it was clear that the problems started after the implementation of the FW 1.4.2 for my More 1.
The ConnectClip has the problem as described above.
On the two phones the fault is that the left channel audio went dead when streaming audio from internet. Samsung Galaxy S22 respective S23.
These are facts.
As I got no support from Oticon I had to speculate myself.
The involved equipment are a pair of hearing aids, one ConnectClip and one mobile. What is in common?? BLE!!
BLE, Bluetooth Light Energy, uses its own time slot in the WiFi band. Has its own hardware and uses several different software protocols.
The Bluetooth classic is still working with my Oticon TV adapter.
As an old repair man I suspected that the HA is causing the problem. But how to prove it for people used to find errors in SW?
I have not succeeded yet!!!
I have consulted two persons on a technical forum. They think it is unlikely but not impossible, that a setting in the HA FW causes BLE-SW to “burn” BLE HW in the ConnectClip and the mobile phone.
Anyone on this forum has had the same experience or have a better theory???
Really, how did you manage that, as in you destroyed them in frustration?
So regardless of the bluetooth device used (say another set of bluetooth headphones) you still have this issue?
Bluetooth Low Energy is a well established profile, been around since 4.2 i think, it works in most cases without issue, its not wifi.
Possibly, but your not alone having this issue with the ConnectClip, its all over the forum.
This shouldn’t surprise you,its firmware issue going by all the other posts on this.
Well I’d take that with a pinch of salt thanks, i mean its hard to say what the exact issue is, but until oticon releases new firmware to iron it out its indeed pure speculation.
1 Like
The Oticon TV Adapter takes wired input from the source, either the Toslink/SPIF optical input, or the RCA level stereo input. It does not take or operate Bluetooth classic with the source.
The wireless connection between the Oticon TV Adapter and the Oticon hearing aids is a proprietary BT LE protocol that Oticon licensed from CEVA called RivieraWaves BLE IP. Most likely, the wireless connection between the Oticon ConnectClip and the Oticon hearing aids also uses this same proprietary protocol. Similarly for the EduMic.
The wireless connection between the Oticon ConnectClip and the streaming source (whether it be your Android phone or laptop or another BT source is the Bluetooth Classic.
With all due respect, I find it very difficult (impossible, to be honest) to believe that the 1.4.2 firmware caused hardware problems in either your ConnectClips or your phones. Bluetooth (Classic or LE) has such low power that there is no way it could physically damage hardware. When a device is released, it is thoroughly tested by the FCC to verify that it operates in the allowed frequency range and does not exceed allowable power levels. The same process is used in other countries.
Bluetooth and WiFi both operate in the 2.4 GHz frequency range and they do overlap, but BT is a frequency hopping protocol, so it avoids WiFi.
You are mistaken that the Oticon TV Adapter uses Bluetooth Classic. It uses the same protocol as BLE, but at a higher power. You can read the FCC report on the device if you search for it.
1 Like
No, I am not mistaken! The TV adapter is still working, It is possible it uses the same BLE protocol, but the HW is definitely BT Classic. The range for Oticon BT Classic is 10-5 meters while its BLE is 4-5 meters.
I am told that headphones uses BT Classic. My More HA uses BLE hardware.
I think I have to clarify that I have used the word BLE for the hardware, while I now have realized that most people mean different protocols of BLE software. I found this document Bluetooth Low Energy (BLE): A Complete Guide
with this text:
Advantages of BLE
Prevalence in smartphones
"This is probably the biggest advantage BLE has over its competitors, such as ZigBee, Z-Wave, and Thread. The vast majority of people in the world own a smartphone, and almost all of those smartphones have BLE hardware inside. This gives developers a much larger potential user base for their applications.”
Earlier this year I thought the problem was that Samsung and Oticon used the same micro circuits from the same faulty batch. How likely is that??
When my Samsung dealer told me, if I come back a third time with a faulty BLE, they will give me the money back. The advice was to look for a fault in the HA.
Then I made a summary of events:
ConnectClip 1 worked for eleven months with FW 1.1.1
After loading FW 1.4.1 ConnectClip stopped working after one month.
ConnectClip 2 was faulty on delivery, re-cycled.
Here between I got the updated FW 1.4.2.
ConnectClip 3 went faulty after 30 days.
Samsung Galaxy S22 faulty after tree weeks.
Samsung Galaxy S23 faulty after two months.
That’s why I am asking if a faulty setting in any BLE protocol can get the phone respectively the ClipConnect to “burn” its own BLE circuit. We do not believe there are enough power in the HA battery to “burn” the circuits.
Bluetooth classic 4.2 incorporates LE, all the latest versions of Bluetooth are backwards compatible as well, by the way the ConnectClip works with Bluetooth from version 2.1 onwards which is pretty old version now, phones that work for your More are MFi and ASHA which is Low Energy, but regardless i still see no way that whatever bluetooth versions/protocols being used have anything to do your issues.
1 Like
I recently bought a Noahlink Wireless and also acquired the 2023.1 version of Genie 2 software. When I connected the ConnectClip to my computer, Genie 2 detected the current version of firmware, but it did not provide an available version. It was blank. Did you have to do anything for that to work?
I received my new Real hearing aids a couple of weeks ago. Initially, I only paired them with the ConnectClip and the iPhone 13. I intentionally didn’t pair them with the Pixel 6. During the couple of weeks that I used them with, there was not a single instance of audio drop-out. Last night, I paired the hearing aids with my Pixel 6 phone. Right away, I started to experience audio drop-outs on my ConnectClip. Turning off Bluetooth on the iPhone and Pixel made no difference. I cleared the pairings in the ConnectClip and re-paired the hearing aids with the laptop. That also made no difference, even with Bluetooth on the iPhone and Pixel turned off. I used the Genie 2 software to clear all of the pairings and then re-paired the hearing aids only with the ConnectClip. There are no audio drop-outs. I’m not sure if it was the act of pairing with a 3rd device or with an ASHA device, but the audio drop-outs started right away after pairing with the Pixel, so it seems unlikely to be a coincidence. I will use them like this for a while, then I will try pairing only with the Pixel to see what happens.
When I ran the Accessories Updater on Genie 2 2023.1, below is the screen that shows up when I connect my ConnectClip to my laptop via USB. It shows that it’s at version 1.13.0 and that it’s up-to-date. So the Available Version is 1.13.0, the same as the current version on my ConnectClip.
1 Like
Mine shows a blank where the available version should be. When I get a chance, I’ll try it for both of my ConnectClips to see if they are the same. Do you have any special access to Oticon to get updates?
You mean in terms of downloading the latest versions of Genie 2. As you may know already, Genie 2 used to be readily available on the Oticon to be downloaded by anyone before, but about a year or two ago, Oticon started to require people to register (maybe to verify that they’re health care providers?) before allowing them access to Genie 2 downloads now. But for folks who already have a version of Genie 2 installed, they can just use to Updater that came with Genie 2 to get newer versions updated automatically. This is how I’ve been getting updates for Genie 2 lately. I don’t have a full download of the latest version anymore.
1 Like
I can’t believe that it’s been 6 months since this issue appeared with one of the updates and they still couldn’t fix it. What a disrespect to the customers.
1 Like