Skip to content
HearingTracker
Log in

Phonak Target infinio sphere connection problem with one HA

33 replies660 viewsLast reply

Jump
Link to this topic
Reply
Edited

I have Phonak Infinio Spheres for about 1 year. It was setup by my audiologist, but i do some tweaking using a NoahLink Wireless.

Today ( afyer several months) I tried Target again. although Target does detect my fine, after selecting both and pressing continue I get a Detection Problem on my left HA every time.

I had just upgraded to Target 11, so I moved back to 10, but no luck. If I select just my right HA I can connect it just fine.

I tried holding the HA button for 15-20 seconds, but no change. All my devices have Bluetooth switched off. I rebooted after Target install. No luck.

Any idea what I can do to restore the connection?

Is there some reset procedure that might help?

4 people in this conversation8 min readJump to latest

It sounds like a weak Bluetooth or Bluetooth interference. That is exactly what happens to me when I forget to turn off my Phone. But since you have already ruled that out, have you tried placing your hearing aids right next to the Noahlink?

In reply to @PeterOo

You could try restarting the left as soon as you get that connection error and then click retry, must be something simple as you’ve been connecting without issues on version 10, must be a coincidence updating to 11 and now not connecting , shouldn’t make a difference there, also you can try shutting down PC (not a reboot but a complete shut down) disconnect Noahlink and start PC and then open target, now plug NLW back in and try connecting again.

Thnaks for the suggestions everybody.

I let windows finish an update. shutdown and powered off computer. no luck after restart.

Tried to power off, then on with NLW disconnected until Target was started, no luck.

I tried the NLW and the in a metal bowl with a metal lid. Same result, detected both but would not connect to Left HA.

I tried several reset procedures found on the internet: hold down button for 15-20 or for 30 seconds. Tried with devices on initially (and switching off after 5s) and with devices already off. Then putting in charger: same result.

i did see the light turning yellow, green blinking or green solid while I was holding the button. No idea what that means.

The only effect there was that at one time Target did not recognize left and right at detection. But still no connection for left HA.

Did anybody find a detailed description of the reset procedures?

@PeterOo said:

Did anybody find a detailed description of the reset procedures?

What reset are you meaning?

So there seems to be a problem alright, but you didn’t mention the “You could try restarting the left as soon as you get that connection error and then click retry” also try “make a new client and fitting from scratch” to see if you can then connect, is the left side working as it should when streaming, can you pair and unpair it from your phone and the App works with left?and just remember that you only have a couple of minutes to make the connection to Noahlink otherwise you get timed out, all really strange hopefully you’ll find a solution!

Edited

Sorry, I did not mention but I also tried the restart just after error, it will detect again and then will not connect in the next step.

Restarting after detect just after pressing continue also did not work.

Starting as a New client also gives no connection.

Changing cable or usb port did not help.

Streaming is as expected. Mostly ok, now and then drop-outs. Right is my streaming , so Left drops out earlier than right.

I know there is limited time after restart. I restart just before or just after starting conne tion attemp. Mostly by taking the HAs out if the charger.

My guess it is either a hardware problem or something in the memory that might be reset in some way.

I could try unpairing in the app first and see if that makes a difference. Never has been a problem, since Bluetooth on my phone is off.

Else I should go back to the audiologist.

Yes last resort is your Audiologist, as this problem only surfaced after updating to win11 it’s possible their PC and fitting could reactivate it.

I guess a possibility, but still the right side is connecting which says it’s working with the driver now.

It’d be interesting to see if the problem persists by using another PC with win10 .

In reply to @tenkan

I installed Target 11 on a Virtual machine running Windows 11 and got exactly the same result.

Unpairing from all devices including the Phonak app also did not help.

I even tried in a different location, since in another thread somebody had a similar problem due to interference at that location.

Always the same result, so I think I have to see my audiologist and see what she can do.

The reset procedures like described here3 also did not help.

@PeterOo said:

I installed Target 11 on a Virtual machine running Windows 11 and got exactly the same result.

Yeah but that’s not a guaranteed way to try, you should use a windows based PC running win10, this way it takes you back to when you where able to connect and program in times past.

I have exactly the same issue with my left Sphere on a system I have used successfully for fitting in the past. My audiologist (independent, not where I bought my ) has the same issue with my left HA on his system, which makes me wonder if there is an issue with my HA.

I’m running Target 11.0 on Win10, native Intel i5 PC. Noah Wireless also just updated to FW 3.17 to see if this makes a difference, but issue remains.

In reply to @tenkan

I tried it on my Windows 10 system also. The problem remains after removing Target and reinstalling Target 10.
I could not start a remote session because this was not activated for my (says Target). But I need a working NoahLink connection for that I understand.

Same happened on 10.x before updating to 11. I am currently checking out how to best send them in, I bought them online (within the EU, but far way).

In reply to @PeterOo

@PeterOo said:

I could not start a remote session because this was not activated for my HAs

Well yeah that’s right, so what are you trying to do remote session for tho? Obviously something wrong with the , send it back to Phonak and get them to sort it out.

@Sneak said:

I have exactly the same issue with my left Sphere on a system I have used successfully for fitting in the past.

Really, exactly the same issue as @PeterOo ? Like that’s just really strange, have you tried all the other suggestions posted above to see if you can get it connected.

Yes, all of them, and as said, my audiologist also could not connect my left Sphere to his system - and I am sure he does a lot of Target fittings every day.

Well this points to a serious “bug” with Bluetooth then, no one else as yet, should see plenty of complaining if it is tho.

I wonder what firmware you guys are running, any updates available through the App?

Related discussions