I use Qobuz on my NDX2 and inside the menu there is a item titled ‘Quality’ which lists:
MP3 - 320 kbps
CD - 16Bit / 44.1 kHz
Hi Res - 24-Bit / 96 kHz
Hi Res - 24 Bit / 192 kHz
Have you looked Servics & Accounts menu, then the Tidal option?
I use android for all my streamers and don’t experience any of these issues.
If I ever do have any connectivity issues I just toggle the WiFi off and on on my phone. This sometimes happens if I come in from the garden where I have a different network.
So if you use mesh WiFi or multiple networks in your home, try that. It takes seconds
1 Like
Tidal Max (above 44.1/16) was introduced with the latest firmware version.
Works fine on my Sony 10 v6 and both my Toshiba and Neocore tablets via a TP-Link Deco mesh.
1 Like
That shouldn’t need to be done if you need use a Mesh system as that manages all the individual nodes co-operating and co-ordinated via a singe SSID, so the device user doesn’t need to do the switch as the Mesh does that.
Multiple networks definitely creates a nightmare. Same with a mixed ethernet and wifi home IF you’re not having EVERYTHING ultimately on the same router. (This is a potential issue if you use a home wifi router in addition to your internet provider’s router, which is common because the isp provided router often has inferior wifi compared to what a mesh network can do.). You can end up with your Naim player on one network and your phone/tablet on another and, of course, they can’t communicate.
Mesh on the other hand does not; it’s one network. Your device may jump from endpoint to endpoint . . . but that’s by definition seamless on the network connectivity front.
Its not your network. The app is screwed up again. The app is freezing, responding 30 seconds after i switch tracks, pause, play. Its just about impossible to call up by artist then album. Search function does not work. The only reason im on this forum today is to see if anyone else is having the same difficulties that i am. Its been about a month since i used mu Uniti Core Server and now its not working and i know its app related.
Agreed. What I’m saying is that it’s my phone that ‘sticks’ to the wrong network sometimes. Not a naim fault in this case.
I mentioned mesh in case it is an issue. It isn’t for me, it works seamlessly within my house.
I do have a different network in the garden though (based in an external gym room). If the phone connects to that and then I come into the house, it can’t find the naim streamers straight away. So I bounce the connection.
I don’t think Android 15 is the real issue. As said, I have been on Android 15 since it was officially released for the Google Pixel devices (last year), I always update the monthly security patch (company policy) and everything in the Focal/Naim App has always worked fine. Only with the update to the 7.4 version things went wrong. 7.3 worked fine on Android 15 and the February security patch. Hence I really think the issue is in the Android version of the app.
1 Like
I’m on 15 with no problem.
1 Like
Hi @Xanthe, I am not really sure… yes the Naim app uses approximate timing update information, but it is not critical in an any way and has no impact on the audio… the timing update is not crucial. WLAN has always, ever since it was conceived, has been designed to provide suitable connectivity for such flows.
The power required by any WLC even built into a modes wifi enabled router is minimal. Current wifi security capabilities are far more demanding.
Now the implementation of UPnP does require certain considerations
- the server and control points are in the same network.
- the WLAN and LAN needs to support multicast.
The latter is common now and is also used by other ubiquitous functions like mDNS. UPnP uses SSDP. (For discovery). However some home poor network devices (and these can be equally off the shelf products as well as ISP broadband wifi routers) can time out on group addresses used in multicast (nothing to do with DHCP IP addresses) and so devices ‘disappear’. An ISP that offers IPTV services (eg BT) is very likely to provide capable and suitable WiFi routers here.
Also the Android OS is a rather open OS, with manufacturer variability… and as such we have seen issues with the WLAN stack in certain Android devices which have caused issues with certain network libraries on these devices. So an application can call upon Android libraries and get unindented operation.
Also problems here:
Samsung A52s Android 14 and Naim app 7.2 and Qobuz is working fine. Also "now playing is there…
Samsung A55 Android 14 and Naim app 7.4 problems! Qobuz not working, no “now playing” etc.
So the problems started with Naim app software 7.4
2 Likes
Agree with the 7.4 version of the app being the likely cause. My ndx2/Samsung S23 were solid before last app update. Now, i cant rely on it, having to use my ipad.
I dont have a mesh system, just a simple ISP issued modem/router/WAP that works with everything else in my house ( wired and wifi).
1 Like
And yes, the 7.4 version of the app struggles with my NAS at times too. The synology/asset setup works on my wiim ultra fine, but not alway the naim app. At best sluggish, at worst not at all.
What I have found is that issues with responses to the app taking too long to to get a response (I can’t recall which ones it was, I don’t have the Wireshark traces any more, and it doesn’t happen now - see below) can cause the app to tell the streamer to load a track while it’s already playing, but the messages are out of sequence from the view of the streamer, causing it to jump to the start of that track but then not play it. This can happen during audio playback.
Moving to a separate, but no more capable WAP (a TP-Link Archer, with all other functions turned off) improved matters, moving to a much more capable WAP (TP-Link Deco) sorted this issue completely even when using the same hardware for the control point. It also used to happen with all three of the devices on which I run the Naim app.
Hi, that won’t be wlan related, unless you have network congestion or interference and frames are being discarded; more likely application control point / streamer / server latency. The wlan latency will be in the order of 20 to 30 mS or less, probably quite hard to detect.
Strange that it precisely correlates to the WAP used though.
Indeed not WiFi related, more like WAP hardware / firmware related.
Yes, might be discarded data… check the signal quality and interference level on the access point. It might not have selected optimum channels, or be faulty. (Best to let your APs auto select… typically every 24 hours)
If there is high interference, data could be lost and one is then relying on TCP in the network stack to resend the data… but the wifi performance would need to be pretty bad for that to be noticeable other than by a machine.
It was not the WiFi signal itself.
In all cases it was by far the strongest signal at the location of the control point (by at least 20dB, usually more), I made sure to check that as it was an obvious possibility that needed to be eliminated first. Other interference on 2.4GHz AND 5GHz (same thing happened with both) is a possibility I couldn’t control.
Did you check the RX/TX/Discard ratios? Many modern wifi solutions give a ‘quality’ score for particular clients. The interference might be closer to the client than AP. Signal strength and quality don’t always correlate.
If discard is low then yes the wifi is working fine… and points to the server/control point/ streamer latency/lag