naim app fails constant

Hello everyone,

Positive news from my side. Since today the app works fine. 

At the end this issue had nothing to do with the naim app.

After consulting Tom he advised me to check if my network detects UPnP devises.

This was not the case. Turns out my KPN modem / router did not support this. After receipt and installation of a new router / modem the app works fine as before.

The only question I keep is why oh why did the old " green"  app did not have any problem with this. This worked okay since the beginning. 

So for those who still have a problem........ who knows it might work for you too, check UPnP (there a several tools available on the internet)

Thanks for all the replies and suggestions, In the end it was Sondek71 who brought me in contact with Tom. Thanks Sondek71!

The (new) naim app works without any problem on my iPhone 5S with iOS7. As soon as I want to use it with on any Apple device with iOS8, it's only working with UnPn-Compatibility mode switched on. Which is a pity, because playlists and scrubbing do no work anymore... :-(

Jan

It doesn't add to much to the discussion, but I just want to let you know I face similar problems. Running iOS 8.2 regularly causes crashes with the Naim app. I use the latest firmware. Also face connection issues (connection is made but takes way longer than before) with Asset.

The moment the app runs, it works flawlessly and I like the current UI and features.

Iver

Hi Iver...

8.2? Isn't the latest public release 8.1.1?

Have to say that this latest iOS update seems to have caused so many app authors issues - I seem to be updating apps at least every other day and I don't really have a huge amount of stuff installed on my phone.

Phil

I have repeatedly connection losses between the mu-so app and the streamer. When it runs, it works smoothly but every now and then the connection between mu-so and my NDS is blocked. This is happening without active change of any of the settings neither in the network nor in the iOS nor on the streamer. I run the newest firmwares on all devices and have an Apple only installation (iPad, Airport). The problem can sometimes (but not always) be recovered by a complete boot of the network (unpower Airports).

I have now analyzed the communication between the app and the NDS using the Naim Tool NetAPIIA: It looks like every now and then the communication between the app and the NDS is interrupted. The streamer does not answer the requests from the app anymore. 

At the moment I am investigating the problem with TJ and a Naim firmware developer. My guess is at the moment that there is a bug in the 3.22 firmware which became obvious only when using iOS 8.0 or higher and the newest Airport firmware. Currently we are looking at the tunneled communication between the app and the streamer (Event TunnelfromHost)......

What I want to say: I am surely not the only one with this problem and I will keep sticked to it until we have found and fixed the problem. I have as a consumer already spent too much of my time on this specific matter now....

Anyone else running in this kind of problems: Get in touch with TJ. The forum is not the right place to get stuff fixed (it doesn't help to be only talking about it).

Sondek I have similar issues (dating back well prior to the new app and iOS 8), and the same setup (Apple home networking products) that leads to some disconnect between the NDS and the rest of the network.  Rebooting the NDS solves it for me.  I've emailed Tom, thanks.

I will try leaving the NDS on something other than UPnP during downtime to see if that helps.  My Qute2 does not suffer this infirmity it seems.  Just the NDS that needs rebooting every 10 days or so.

Hi Bart,

Are the NDS and Qute on the same firmware versions? Are they both connected to your router via the same 'path' (i.e. both wired, both wireless)? Does one run through a switch or network extender that the other doesn't?

Cheers

Phil

Hi Phil,

We'll get to the bottom of this.  I don't know if it's related to the issue you've addressed with me, or not.

Everything is on the same wired network, all through the same 16-port unmanaged switch.  uServe, NDS, Qute, and my wifi router (latest-gen Time Capsule, which is just an Airport Extreme plus extra hardware) are all plugged into the same switch.

The NDS is on 3.22 and Qute is on 3.21.  The Qute is on the same rack as all of my networking gear, while the NDS is connected by a long run of ethernet cable.  When the NDS wants to be rebooted, it's unresponsive from both the wifi app and its front panel controls.  But rebooting it sets it back to normal operation.

I can confirm that I had the problem also before iOS8 but could always recover it by rebooting the NDS. It happened like you stated when the NDS was running over a couple of days. Since iOS8 the rebooting is not enough anymore. It keeps being blocked.....

I hope to get a feedback soon from the firmware developers of Naim. Would probably be worth a try  to reapply firmware version 3.21 to see whether the problem came in with 3.22. Or whatever it takes to track down the error is welcome...will keep you posted on the progress....  

I had the problem before firmware version 3.22. Upgrading to firmware 3.22 afterwards didn't change anything in the behaviour of the app. The problems began with updating to iOS 8 on my iPad. Running under iOS 7 everything was fine - even with the new naim app. 

Mike, forgive me if this is irrelevant to you, but is your network set up as shown in the best network solution thread? You should not have these connection issues if it is.

I have set up my network as discussed in the thread so nothing new to me.

The problem is, that the NDS is not returning the event TunnelFromHost(...) to the the streaming app. That's why the app is waiting a while until it disconnects and shows a message like "cannot connect to device" or "another instance of the app is already connected" appears. This problem is now with the app and firmware development departments of Naim. I am waiting for instructions how to proceed the debugging....

The following network analysis is done using Naims NetAPIIA:

succesful case:

2014-11-25 19:51:34.401 C>S: Cmd: TunnelToHost( id="3", data=<*NVM PRODUCT
2014-11-25 19:51:34.401 > )
2014-11-25 19:51:34.417 S>C: Reply: TunnelToHost( id="3" )
2014-11-25 19:51:34.620 S>C: Event: TunnelFromHost( data=<#NVM PRODUCT NDS
2014-11-25 19:51:34.620 > )
2014-11-25 19:51:34.620 C>S: Cmd: TunnelToHost( id="4", data=<*NVM VERSION
2014-11-25 19:51:34.620 > )
2014-11-25 19:51:34.635 S>C: Reply: TunnelToHost( id="4" )
2014-11-25 19:51:34.838 S>C: Event: TunnelFromHost( data=<#NVM VERSION 3.22.000 7232WE PRODUCTION RELEASE

bad case: 

2014-11-25 19:21:09.008 C>S: Cmd: TunnelToHost( id="25", data=<*NVM PRODUCT
2014-11-25 19:21:09.008 > )
2014-11-25 19:21:09.024 S>C: Reply: TunnelToHost( id="25" )
2014-11-25 19:21:14.016 C>S: Cmd: Ping( id="26" )
2014-11-25 19:21:14.016 S>C: Reply: Ping( id="26" )
2014-11-25 19:21:19.008 C>S: Cmd: Ping( id="27" )
2014-11-25 19:21:19.024 S>C: Reply: Ping( id="27" )
2014-11-25 19:21:24.016 C>S: Cmd: Ping( id="28" )
2014-11-25 19:21:24.016 S>C: Reply: Ping( id="28" )
2014-11-25 19:21:29.008 C>S: Cmd: Ping( id="29" )
2014-11-25 19:21:29.023 S>C: Reply: Ping( id="29" )
2014-11-25 19:21:29.023 C>S: Cmd: Disconnect( id="0" )

Ha , I have bought a Mu-so and also have a qute 2 and uniti 2. Problem started with the mu-so that everyone has been complaining about ie app loosing connection . Ok after reading all these I decided to plug an Ethernet cable into the Mu-so ( as I had with the others) and the problem stopped straight away - kind of defeats the purpose of a wireless speaker but at least I can now use it and it's avoided being thrown out the window. Hopefully Naim or Apple can sort it out one day...... Good luck the rest of you.

I am having the same issue as well. And have had to resort to the hardwire. Not ideal, but for now at least I can listen to it.