Skip to content
HearingTracker
Log in

Widex Allure App Issues

This topic is closed.

16 replies1.4k viewsLast reply

Link to this topic

I’m currently trialling Widex Allure 220 having tried Moments for a while. So far finding the sound quality and voice-in-noise better than the Moments. However the app and interaction between app and is for me a total disaster. Samsung Galaxy S10 Android 12. First I find everytime I wake the phone up, even if not streaming, the HAs sound is interrupted and changes volume. When I close the phone the same happens. Very disturbing. In addition, I have constant “Error 3000” when trying to open the app - requiring restart of app and restart of bluetooth to repair. Then there is the volume - it seems almost random how loud the streaming will be and changing the phone volume only makes marginal changes to the volume streamed to the HAs. I’ve tried to be systematic about nailing down some of these issues (there are more) but it is such a mess that it is hard to do reliable repeatable experiments! Anyone else had issues? It is such a shame given how good the HAs are otherwise.

7 people in this conversation4 min readJump to latest

This what I was thinking, just seems an old phone for this latest model from Widex, have you got access to another later model to test.
But it does seem like some kind of “notification” trying to come through, have you tried the settings on your Sammy to turn everything off
(notifications) to check.

In reply to @philbob57

Not an unreasonable suggestion :slight_smile: However I was working off the fact that the audiologist had contacted Widex who said the phone and OS were fine, and also from Widex website that says the same.

Edited

In reply to @tenkan

I don’t think it is a notification - in fact if I have the Widex app open and then lock the phone, what I see happen when I unlock it is that it immediately switches to streaming, then checks and sees I’m not streaming anything and switches back to Universal. Hence the interruptions. This just seems like a bug (or “operating as designed… badly designed”). Sadly I don’t have access to a more modern Android. I have messaged Widex so will see what they say (and I’ll update the thread with any discoveries)

Seems very strongly like a notification to me. Often the duration of the sound is so short you never hear it because the bt hasn’t finished connecting for the content yet and the sound is done. Meanwhile, the program resets.

WH

I understand why you might think that - however from watching the behaviour of the Widex app I can see what happens - when I unlock the phone it immediately defaults to the Streaming program, then seems to check if streaming is actually needed, notices it isn’t and swaps back to the Universal program. Not sure why there is also a change of some kind when I lock the phone again, but overall it is irritating!

Hi. I use Widex Allure 440 and I get the same error. That error is probably happening because of signal interference in the environment. It is not the hearing aids itself it’s the bluetooth on the phone it’s losing connection due to some interference. Can be like a bluetooth connection on a tv, etc.

Bluetooth disconnections will happen, of course, and the developers will have anticipated that. How that is handled makes all the difference and distinguishes good software from bad - the fact that I can reconnect the app by restarting it and/or restarting bluetooth suggests that the software could have reconnected, but just showed an error instead. I think that is my overall impression - great hardware, terrible software. At least that should be fixable, I just hope they do!

Yep, still sounds like Bluetooth interference, even Phonak hearing aids do that, even Starkey. I am in IT and have tested a bit of them.

I am just testing Allure 440 with Samsung Galaxy A55 with Android 15. I have the same bad behavior of the app as fineman. Additionally I noticed that the Equalizer-changes I made for streaming stayed selected after the back-switch to Universal mode.
The app should be debugged very soon!!!

I tried - their support simply told me they won’t deal with individuals, only with audiologists. So my audiologist has to report the issues (which he is trying, unsuccessfully)

This is very disappointing. They don’t realize that the problems concern not an aidiologist but a software engineer.

But which bluetooth version were you using, Moment doesn’t have LEA, it’s so some difference there.

Related discussions