To be honest, I am disappointed with Oticon… this really should not take a couple months to fix… I rely on dependable iPhone call streaming, and since going to 1.4.0 I had no other option but to go back to my old OPN’s while Oticon delays pushing out the fix…
John
I disagree, if Oticon rushed the fix then the aids could be in worse shape than before the fix. As someone that has been around electronics and software my adult life. I haven’t updated to 1.4.0 and thankfully due to the VA contracts wouldn’t be updating until the VA is happy with the fix. So no you don’t want a rushed repair or software fix, that could mean even worse damage to the aids.
What upsets me is that there isn’t more open communication between Apple and Google with the hearing aid companies. So that we don’t have these failures every time we have major updates to the phones and aids.
That is why I feel that hearing aid companies should stick with improving the basic functionality of their aids and not forgetting the basics for connectivity.
All of this gives me the sense of “smoke-filled back rooms” determining what you will get and when. And little sense of “Gee, we stumbled, and we are sorry…”
WH
When it comes to connectivity there are way too many hands in the mix. All it takes is one little bit of code that is unseen, and not detected until the perfect storm happens, then it is all hell to be paid. That is what I did a lot of, reading developers code to find the problems and errors that they couldn’t see because of their ownership of the code. All it takes is a period or comma in the wrong place or missing. And in this connectivity there are multiple sources of code that has to communicate with each other flawlessly. The odds are poor that it happens flawlessly.
If I were working there, I would be poking to be sure they were using automated scanning of the code and automated testing both simulated and and instrumented real HW in the lab. The issues you guys face would absolutely be beat to death before the next release. Our teams release code on an avg of once an hour. It has to have met an extensive array of tests, and then get a smoke test in a staging platform by folks who know how it ought to be used in production. And we still get out both regular releases of planned work and bugfix patches. But code that helps guys and gals come home is pretty important to our teams. We’re focused. I hope they are using best practices wherever it is they are cutting that code.
WH
I know it must be better know but what I saw of the computer scanners was a joke at best.
Rumor is that 1.4.1 is out… anyone confirm?
John
From what I have read on Facebook it is out and available in Gene2
I just updated. It’s not a rumor.
It’s a 2 step process. It serves up 1.4.0 first then 1.4.1 is shown.
Ooh, can anyone confirm whether 1.4.1 solves the BT disconnect problem with iOS?
I had 1.3.0 on my Oticon Mores and iOS 15.7 and was very happy. Then my audiologist upgraded me to 1.4.0 and it’s been a nightmare ever since. The audi said it’s an iOS problem and nothing to do with the Oticon upgrade, I updated to iOS 16.1 but no better. Hoping this new Oticon update will fix the problem!
I have firmware 1.4.1 now for about 6 hours no bt drops yet . 
It seems to work exactly as 1.3.0 did. No issues at all for me so far.
Oticon are touting this release as the solution to the dropout issue for the Polaris chipset.
We’ve been advised to upgrade all current product now.
Just updated to 1.4.1. Only one day of use but so far so good.
It’s working like a charm again. Thanks Oticon.
Firmware 1.4.1 - the Audi update it for you or it is automatic (over the air via wifi?). Mine is still Firmware 1.3.0
You will have to have your audiologist do the updates. It is a two step process first to 1.4.0 then 1.4.1. Not sure why they went completely that way, but suspect it was the best way with so many already updated to1.4.0
Thank you very much for your prompt reply.
The 1.4.1 update is also available for the Philips 9030 via Hearsuite and solves the BT disconnect problem here as well.