I have an NDX2 and SN2 connected by ethernet (and switch).
I only use the unit for streaming Qobus via the Naim App ie no local streaming/Tidal etc.
The unit is about 16 months old.
I have been experiencing random restarts - about 3 in as many weeks - since the latest update.
Like many others I am very happy with the sound of it but it does not feel reliable as a unit.
The NDX2 has also stuttered during streaming a couple of times (sounds like a damaged cd when stuck).
Prior to the update I was experiencing very brief intermittent drop outs when streaming HiRes on Qobus.
Richard - I will be contacting Naim Technical Support first thing tomorrow to report this.
I confirm that I have switched everything off and waited half an hour before powering back up again in the sequence recommended but this has not resolved the problem.
Well, it seems my NDX2 now also has showed some problems. It had performed flawlessly since the update.
Then yesterday while listening to Tidal, it started to stutter and rebooted by itself. It came back online and was okay. But, the automatic reboot bothers me.
Please ensure you report this to the support team at support@naimaudio.com. We need to ensure that the engineers are aware of the magnitude of the problem, or at least how widespread it is.
Yes reporting all events is important but I imagine Naim and specifically the software team are aware of the magnitude and are diligently working on update although I imagine this will take a fair amount of time .
But at post #745 Richard implied, albeit eight days ago, that there hadnāt been that many reports of the stuttering or random reboots to Naim Tech Support, so I feel it is important to keep the pressure on. I am reporting each such event and will continue to do so until this is resolved.
Yes, as Clive suggests above, itās really important to contact Naim support should you experience any stuttering and then re-boots, particularly if you have already done the recommended re-boot procedure following the update.
Naim R&D will be using the support logs in their investigation, so the more info they have the better.
@Thomas , did you get a reply with a ticket number? I tried to log one a while back, got no response, tried again a week later, still no response, then I sent it again from a different email address, and received a ticket number within minutes. So your email may have gone in a spam inbox. try another email address if you have one
I didnāt receive a reply to my report of the second instance of random reboot, although I did refer to the initial ticket number, so I assume that the two instances have been linked. It would be nice to have an update with some indication as to when this will be resolved. Iād be happy to live with version 3.4 if that could be made available, even if it did mean accepting fortnightly screen freezes.
Maybe this is how v3.5 overcomes the fortnightly screen freeze. The way to overcome the frozen screen is to power off and reboot the streamer. Now it happens automatically!