Firmware update v. 3.7.0

1 Like

If you search for Volume and Display there are quite many such posts, but I thought this was supposed to be fixed by one of the updates since, though haven’t read in detail and am not sure

1 Like

…from the Tidal Connect thread

ah well

That’s not good Jim especially after Naims latest firmware release bricked your ND5XS2!!!

Happening right now. Played Counting Crows this morning, started playing Coltrane now. It looks like this:



Widget:

The timer does nothing, it indicates 1:32 and just stays there. After the first song ends, it freezes. After which I start the album from song two by pressing it on the playlist and everything works fine after that.

Thanks @RexManning

1 Like

I’ve caught the similar issue. After the first song the ui does not react to my touches.
Both naim and Tidal are unable to handle anything(volume, source, play, pause, etc). The only feature that works in the Naim app is Standby.
However, Spotify always work fine. Before 3.7.1 it helped to kill app several times. After 3.7.1 I decided to use Spotify if possible and abandoned my Tidal subscription.

Must be problem with new firewal. After last update Tidal is freezing often (on Atom). I reboot few time in lasta days, something wrong with new update, for shure.

Are you running the latest version of the Naim App? (Android 2.22.3; Apple iOS 5.22.2

Yes, 2.22.3.
Last year Atom worked like swiss watch, but after last update I reboot him 4 time at list. I must to try to unplag from electrity for one hour, maybe thet helps?

I would suggest the following:

Unplug your Atom for 30 minutes
While it is unplugged from mains, reboot your router and power down/back up your phone/tablet running the Naim App.
Once your network and decides are fully back up and running, and the Atom has been unplugged for at least 30 minutes, reconnect it.

Let us know how you get on.

1 Like

when is the next firmware update coming out? I was told by naim support it will fix the issue with random play not working on playlists. If it doesnt fix it this time im going to have to sell this and go to a product that actually works the way it should.

1 Like

Your issue is the Asset Jukebox tracks selection still? If it’s the only issue, I don’t understand that it can have such importance that you are ready to buy another streamer from other brand.
Maybe then a proper jukebox would be the best to have in your case.

Nothing , now I cant sent Atom in standby mode, or I get mesages- Strimer not responding!

Wow.

My ND5XS2 is back.

The whole system has come alive again, better than ever.

Thank you to everyone at Naim. :smiley:

5 Likes

Great news! Enjoy :slight_smile:

1 Like

I use a tablet (android) to control my nd5xs2. Recently I had problems with the nd5xs2 control. It turned out that the microsd card stopped working. After replacing the card, everything returned to normal. So some reported problems could be due to tablet / phone malfunction including insufficient free memory. Too many applications …

1 Like

Hello everyone,

I come with my problem. Since updating my Uniti Atom, the streaming is slowing down.

I use spotify a lot via my smartphone. When I change the music or pause it, it takes about 2 seconds. It’s not instantaneous. Same with the remote.

My WIFI connection works very well.

I would like to point out that I have a Samsung S21 ultra and it works perfectly instantly on other streamers

Has anyone had this similar problem? I find the User experience unpleasant.

It sometimes happens for all of us. Try to restart your router, wait, restart your streamer, and install again your app. In most cases it works.

1 Like

Same here.

Before 3.7: < 1 second lag when hitting pause in a Spotify app (phone, tablet, watch)
3.7.1: about a 4 second lag.

Basically it’s gone from “quick enough to not really notice” to “slow enough to make you think it’s not working”.

The other “feature” introduced since 3.7 is that selecting the atom as a device no longer turns it on, if it was on standby. It now turns on when play is started. This means that avoid the first 4 seconds of the track is clipped. Not a great issue.

However, it does mean that the “feature” where there was about 2 seconds of the last track played (if you stopped and switched off during play) is dumped to the speakers no longer happens.

I say “feature” rather than “bug” as it’s six of one and half a dozen of the other, and it’s possibly alluded to in the release notes.

I’ve had about 2 “system crashes/reboots” since putting 3.7.1 which does make this release one of the least reliable (the version it shipped with was slightly worse, I think. Again, it’s more about expectations than a series problem as a cold boot sorts it out. However, where in previous releases, you could tell when a crash was coming as it usually followed some outage on the network, so it seems like it was just responding to an unknown condition. On 3.7.1, the reboots have been unpredictable.

1 Like