I’m confused. I’ve read this thread but it’s not clear to me which screen (or screens) is frozen?
I reported an issue with my Uniti Core iOS App several weeks ago. The main screen freezes on the second access. I have to exit the app and then force it closed on my iPad. When I return to the app it will work normally for one command. Then the screen will freeze up again.
I was told to try a factory reset but it doesn’t do a thing to fix the problem.
It’s the HD color display on the NDX 2, ND 555, etc. that gets stuck. You must reset the unit to make it work again. Naim is aware of this and works on a solution. Hopefully with next firmware update.
In the meantime it’s still worthwhile contacting Naim support if this occurs regularly. Give them as much supporting info as possible as that’s the best help for trying to nail the solution.
That’s very odd and I haven’t heard of anyone else having this issue with the app.
Although I don’t often recommend this, you could try deleting the app from your ipad, restarting the iPad and then reinstalling the app. Deleting the app also deletes all the data that the iPad is holding so you get a chance to start afresh as it were.
I hope you are keeping well and away from the virus?
Good idea. I’m willing to try anything at this point as it’s quite annoying to have to go through what I call “the ritual” all the time. But I have a question: what is the data that the iPad is holding?
We are doing okay! Getting a little bored at the enforced “shelter at home” requirement but it’s for a good reason. I just wish more effort would be put into acquiring an ample supply of test kits so we could concentrate on isolating the sick instead of everybody.
The data I was thinking of is the app keeps a note of where the rooms were last time it saw them (so the IP address for your Core). I’m not sure what other configuration info it might keep, but anyway you get to start again if you delete the app.
I’m sure they’re doing their best, and are trying, but I think the real issue here is that their release schedule only allows them to try one thing every quarter or so.
Why not release smaller bugfix releases (without any new features), and do so frequently? With only the ‘feature’ releases every quarter.
If you have been reading this thread for a while you will know about my onngoing issues with this.
I am on my third Star, the previous two being replaced by Naim.
With my current Star when it freezes or more accurately doesn’t respond to the remote control, it does respond to the iPad version of the app and after a period of time (15 to 30 mins or so) the screen unfreezes and the unit responds to the remote control again. Intersestingly, it never freezes when it is on the internet radio input before turning off, now having written this I expect this could be a case of famous last words. It has frozen on all other inputs that I use, whether it is turned off manually or allowed to turn off automatically after a set amount of time. Sometimes it freezes with with a blank screen, sometimes with the icon screen. I must admit I am getting a bit fed up with this state of affairs.
It generally makes more sense for releases to encompass a number of fixes or improvements. Of course, I can appreciate that this can be frustrating for anybody with a particular issue right now, such as the screen freezing. What I can suggest is that the Beta group get to trial fixes before release, so if you’re keen to get stuck in and take part (especially if your issues are persistent and repeatable - your feedback could be really important) then please do contact R&D on beta@naimaudio.com and they will be in touch.
Yes and no. I would agree with the literal statement, but disagree assuming you mean what Naim currently do. Develop for 3-4 months and then do a giant release with many changes, and no bugfixes between releases. Of course I don’t mean that there should only be a single bugfix per release.
Naim’s versioning scheme even seems to cater for it. 3.3.0 -> 3.4.0. There could have been a 3.3.1, 3.3.2 etc.?
I might indeed join the beta group, anyone with experiences they can share here?
I get this once per listening session. Hitting ‘Try again’ fails. The only way out is to kill the app and restart. This is on an iPad, everything up to date.
That message can mean that the wifi signal picked up by your phone/tablet is quite weak for whatever reason and the phone has switched to “WiFi Assist”. You could turn WiFi Assist off and see whether that helps (WiFi Assist uses mobile data when WiFi is weak and if the phone is using mobile data instead of WiFi, it will lose the streamer). There was a time when this was an issue a couple of years or so back and I recall some beta group activity on it, but it’s not been a problem since then so far as I am aware.