I’ll pile in too. Here’s how I see what happened.
“I’ve bricked Oticon aids during a firmware update,”
Yup. Could happen. Could happen with many systems where a firmware update is possible. Like your internet router. Your computer BIOS. etc. And every time, they have stern warnings about not interrupting the process.
“and also bricked a FittingLink 3 dongle.”
This I don’t know.
“IMO, they are total incompetents when it comes to software.”
Here’s where the problem started. The context of your post is about Oticon and Fittinglink. Your use of the word they then means you’re still in the context of Oticon and Fittinglink. You then are saying that they (Oticon and Fittinglink) and total incompetents etc.
If you had said in general that with ANY kind of device that has firmware update capability and that they have this risk of bricking when interrupted then sure. No problem. Fair gripe. I think pvc is taking exception to you saying that specifically and only about Oticon and Fittinglink. And then declaring that they’re incompetents. And then your next post spreads it more generally but still being mad at Oticon for YOU interrupting the process because they couldn’t be bothered to protect the process against user interruption. Sure. But they’re not alone in this design aspect. Maybe it’s a ROM capacity issue where space is at a premium with these tiny devices.
At the end of the day…what the heck are you doing interrupting the process when you know bricking is a very real possibility. And the update process tells you as much. Other DIY people would heed that warning. Do you test manufacturers firmware update methods for laughs? To see if they’re one of those fool manufacturers that don’t put in protections?
Bottom line…if you had said that darn those Oticon folks for not putting in protections against unknowing people interrupting firmware updates…probably nobody would have taken exception. I suspect there are reasons why many manufacturers don’t though.