I have a similar issue in my atom since the update. I noticed as soon as it started updating the screen started turning off and on, lines running through it etc. After the update it continued doing all sorts of weird things, even went white at one stage. I’ve tried power cycling, left the cable unplugged for the night. It didn’t fix the problem. Now the screen just goes black after a little while.
Sent an email to customer support and hopefully hear back soon.
Update from my side - playlists are still not working when previously they were. Sent a support request at the beginning of the month and haven’t had a response. Anyone able to help me follow up? Ticket number is: 122505.
Jackjacka, and anyone else who may be awaiting a response from the Support team, they’re quite a small team and of course, since the recent Firmware and App updates they’ve got a lot of queries to get through, so please be patient.
If it’s really urgent then a good way to flag up your email, is to send another email, quoting the original email ticket number, in the subject bar, for example “Re- Ticket XXXXXX”. This shows then that the original ticket is of high importance, and they’ll hopefully prioritise a response to it.
Thanks Richard - especially on behalf of the very busy Support team.
And rest assured, all, that all feedback on issues is being fed back to the Naim software team, whom are working with our Beta group on testing potential fixes.
2 months after having an Atomo, with the problems that the update has brought me and that the technical answer of “we are working on it”.
I can’t listen to part of my music on HDD, the radios are constantly interrupted. They do not tell me how to downgrade to return to the previous state.
I am already thinking of returning the Atom to my supplier and moving to another line or brand
ANother issue happening now. The Atom wouldnt turn on this morning, just stuck on the Naim screen and wouldnt go any further. Unplugged it for a minute, still wouldnt work. Unplugged it for an hour and it finally turned on but immediately turned off again. Managed to get it back on and play some music but now the volume doesnt come up in screen.
This is the 2nd update Naim have released since ive had this thing and both times have had issues. I dont know what type of testing is being done but id suggest it isnt good enough. Its not acceptable for Naim support to basically say “wait until the next update in 2 months” These arent cheap throwaway items.
Also the naim app itself isnt working on either my phone or tablet now. It says the streamer is not responding. Funny how both HiFI cast and Bubble UPNP apps are both finding it fine though and streaming music to it.
So sorry that you are having issues. This definitely feels like something beyond firmware to me. Could you contact your local dealer and take your Uniti Atom in to see if the problem persists there, and/or possibly borrow a different unit to try at home?
Returning to firmware, we do have a Beta test group of external users - many of whom are also active on these forums - and a wide range of set-ups and scenarios are tested. But with so many potential different set-ups, there may occassionally be outlier issues. As soon as these are identified, Naim’s software team works on fixes: Firmware 3.7.1 is already in development and being tested for release, for example.
Once again, I am sincerely sorry you’re having issues, and would urge you to contact your local dealer for assistance.
The technicians contacted me and they say that in the next few days a patch will come out that would solve the problems.
I suggest that everyone have the possibility of being able to downgrade easily
It would be interesting at least to have a way to go back one firmware in an easy way. I only have one issue with covers in roon. I would gladly go back to 3.6 on my ndx2 until 3.8 comes out to recover the last behavior in roon.
Also this could give to the users that have “suffering” more serious issues a way to recover at least the last working state and not having to wait weeks or months to get a new fixed firmware.
Software development is complex, with every bug that is fixed it grows in stability, but with every new feature added we gain new bugs to correct.
As far as I’m aware, outside of beta testing, that’s not possible, mainly because Naim have to keep the fw current for streaming service partners who don’t want users to downgrade.
I have this issue on my Nova with the new firmware too. It’s needs a full power off and re-boot to get it to work and without the screen you can’t access on-screen controls.
It’s a bit disappointing really. I’ve had the Nova for about 3 years and there has always be some form of bug with the Firmware. A fix of one has always introduced a new one.
It’s easy to reproduce on my side using exlusively an iPad or iPhone as a remote in roon server. There is also other users in the roon fórum mentioning the same issue.
If I use the naim remote control it Works as expected.
The issue is only happening in roon after the latest firmware 3.7.
Possibly an iOS thing? I’m using the remotes on Android and Windows (and Roon ROCK) and am not noticing any changes with cover display. Maybe I’m not looking for the right thing, but seems to me that I always see the correct cover on the NDX2 display whatever I try
BTW there is a known issue that the radio station logo is not displayed on the streamer when using Internet radio in Roon, but this is a Roon issue
If only for this issue, I’d prob have to say 3.6 was ‘better’ though 3.7 has brought certain other improvements.
Before 3.6 I had the frequent Atom problem of artwork freezing ever week or so. Now it’s the whole darn thing. On the positive side the random reboots appear to have ceased completely.
I do not think is an iOS bug, tested with my MacBook and it’s the same. Not a big of an issue on NDX 2 but it is present. An hard reset did not do anything different.
As I use exclusively roon as the source for my devices and the behavior only occurred after the update I felt it as a bug. I could simply leave the display always on and forget it.
Ok not iOS then but it’s still macOS. It’s certainly possible that it’s a bug somewhere either in firmware, Roon Apple versions, or both together. Unfortunately I can’t contribute much as I’m not seeing it on Windows/Android. It’s just something that made me concerned as I’m in the Beta group so was wondering if this is something I could have caught