Naim app update - iOS and Android
Posted by: TJ on 18 December 2014
Naim app updates will be available later this afternoon for both iOS and Android.
Ciao bicela, I asked the question because I had exactly the same problem yesterday when I cleaned out my iPad & that included to reinstall the app. It has been 100% perfect for all the last months of testing, but after the reinstall I could not find my NDX !!! a few seconds of panic, but relief once I had switched multiroom OFF & it was 100% OK again.
I think it is something more that the team at Naim need to look into
Migliori auguri di un buon 2015
Ciao bicela, I asked the question because I had exactly the same problem yesterday when I cleaned out my iPad & that included to reinstall the app. It has been 100% perfect for all the last months of testing, but after the reinstall I could not find my NDX !!! a few seconds of panic, but relief once I had switched multiroom OFF & it was 100% OK again.
I think it is something more that the team at Naim need to look into
Migliori auguri di un buon 2015
Me too, Mike! Problems starts exactly when I removed the beta App to install fresh the released. On 5th of January I will back at home and I will test it.
@Fernando Pereira
Hi
Have you tried uninstalling and reinstalling Bubble? The new version works faultlessly for me, which is more than I can say for the irritating Naim app. I use Android and find Bubble and UpNPlayer much easier to use than Naim as I listen to classical and want to select tracks, often from within a disc. That is harder to do in Naim which seems to me to be designed for pop music and just playing discs straight through.
I still find the App a bit quirky, but have not had time to really explore its functionality. It would be useful to be able to add an album to the end of the queue rather than play next (but perhaps you can?).
Yes, you can touch the three dots . . . next to the name of a selected album and chose "queue next."
Gert, the volume control shows up in the screen showing the specific track playing . . . if you're connected to a Uniti player. If you're using an ND- player you must enable system automation on your player.
Actually, Bart, you choose 'queue last', which is doubtless what you meant. The three dots at the top affect the whole album while those by each track deal with said track.
Quite right!
Do you have a multiroom system or just one NDS in one room ??
If yes, have you turned multiroom OFF ??
= tools > settings > input settings > multiroom
Mike there is no "multiroom" setting for the NDS; it's not supported. That said, I wonder if multiroom being ON on a second player on the network has an effect; just in case, I've turned it OFF for my Qute2 as it's quite irrelevant paired to my NDS.
Have you tried uninstalling and reinstalling Bubble?
I'll give that a try, but I'm very familiar with Android and I've never encountered an app that needs to be uninstalled and reinstalled to work right.
The new version works faultlessly for me, which is more than I can say for the irritating Naim app. I use Android and find Bubble and UpNPlayer much easier to use than Naim as I listen to classical and want to select tracks, often from within a disc. That is harder to do in Naim which seems to me to be designed for pop music and just playing discs straight through.
If I click on the "..." to the right of a track name, I can "queue next" or add it to a playlist. I agree it would be nice if you could select a range of tracks for playing in one go, rather than one by one.
Have you tried uninstalling and reinstalling Bubble?
I'll give that a try, but I'm very familiar with Android and I've never encountered an app that needs to be uninstalled and reinstalled to work right.
So, surprisingly, reinstalling Bubble seems to have made it able to play without repeats or hiccups. Thanks for the tip.
After this upgrade, the connection becomes faulty again. There were instances that the iPad app couldn't find the NDS, which have never happened to me throughout 4.0 to 4.2; and the app now takes forever to reconnect to the NDS after a short iPad nap. I need to rescan in the minimserver to make the Synology server "re-appears" again.
Before the update, did your NDS have a static or dynamic IP address? And after the update? When I installed the latest firmware, the factory settings were restored at the end of the update with the result that the fixed IP address assigned to my NDX was replaced with the default DHCP setting. As I am sure you know, dynamic IPs are problematic due to the caching of such information by participating network devices, so it is preferable to manually assign a fixed IP to the streamer. A dynamic IP could well be the cause of the issue you describe.
Cheers
Andrew
After this upgrade, the connection becomes faulty again. There were instances that the iPad app couldn't find the NDS, which have never happened to me throughout 4.0 to 4.2; and the app now takes forever to reconnect to the NDS after a short iPad nap. I need to rescan in the minimserver to make the Synology server "re-appears" again.
Before the update, did your NDS have a static or dynamic IP address? And after the update? When I installed the latest firmware, the factory settings were restored at the end of the update with the result that the fixed IP address assigned to my NDX was replaced with the default DHCP setting. As I am sure you know, dynamic IPs are problematic due to the caching of such information by participating network devices, so it is preferable to manually assign a fixed IP to the streamer. A dynamic IP could well be the cause of the issue you describe.
Cheers
Andrew
Thanks.
I found that out moments after I made the post by reading the DHCP status of my router, which is serving as the DHCP server of my local network. The firmware upgrade reset everything back to factory default and need to manually key back all the network parameters and restart both the NDS and the router to make things work smoother again.
There is a problem with Android version. Search is not working. When I press a search button and try to write a search string, a virtual keyboard appeared but cannot add text.
Nexus5, Android 5.0.1
There is a problem with Android version. Search is not working. When I press a search button and try to write a search string, a virtual keyboard appeared but cannot add text.
Nexus5, Android 5.0.1
Same problem on Nexus 7, Android 5.0.1.
Hi Tom Johnson,
I experience a bug in the latest Naim app 4.3 when using playlists. After a playlist is created, sometimes I do some retagging (in JRiver software), like adding the release year in the album title or so. In the playlist you get an error message: a red cross on the right side. So far so good, this was always the case.
The bug is: If I want to REMOVE that song from the playlist by pressing the red cross, a windows pops up and says 'Do you want to remove' with the option 'Only this track or 'all missing tracks' (or similar wording, I use the Dutch language version). Whichever of the two options I press, nothing happens.
In the previous versions I simply deleted those 'red-crossed'songs, but App 4.3 does not react when I tap on the window. I checked this on two iPads.
Can you check please and tell me how to remove 'red crossed' songs from the playlists?
Anybody else with this experience?
Bert
I have the same problem
David
Hi Tom Johnson,
I experience a bug in the latest Naim app 4.3 when using playlists. After a playlist is created, sometimes I do some retagging (in JRiver software), like adding the release year in the album title or so. In the playlist you get an error message: a red cross on the right side. So far so good, this was always the case.
The bug is: If I want to REMOVE that song from the playlist by pressing the red cross, a windows pops up and says 'Do you want to remove' with the option 'Only this track or 'all missing tracks' (or similar wording, I use the Dutch language version). Whichever of the two options I press, nothing happens.
In the previous versions I simply deleted those 'red-crossed'songs, but App 4.3 does not react when I tap on the window. I checked this on two iPads.
Can you check please and tell me how to remove 'red crossed' songs from the playlists?
Anybody else with this experience?
Bert
I have the same problem
David
I also have this problem!
Hi guys,
Good news: I contacted Tom Johnson by e-mail and he confirmed this bug will be repaired in the next update. He also gave a practical work-around:
Hi Bert,
One of our support team has confirmed it is a bug, It will be addressed in the next release.
A short term workaround would be to play the playlist in question - this will result in only the playable tracks being loaded into the play queue. Then re-save the play queue as a playlist. The end result of this will be a duplicate of your original playlist except with only the playable tracks included.
Obviously I am only suggesting this as a temporary solution, the bug will be fixed in the next release
Tom
So with a little patience this will be resolved.
There is a problem with Android version. Search is not working. When I press a search button and try to write a search string, a virtual keyboard appeared but cannot add text.
Nexus5, Android 5.0.1
Same problem on Nexus 7, Android 5.0.1.
It seems that on Nexus 7, Android 4.4 is working - somehow (slow). The problem is not directly in keyboard, but the apps search in background instantly when typing - there should be a problem.
...and there is definitely no volume control that I can find. OK, i could dig out the remote and use that, but why not control the whole shebang from the iPad?
Volume control with the N series units needs a cable connection between The streamer & pre-amp to allow the app-streamer link to control the pre-amp volume control, then activate the volume control in the app. Its all in the manual.
My app used to control the volume, but it seems to have got lost with the pre-Chrimbo upgrade?
If it was there, it's not gone nowhere with the upgrades. I have changed a bunch on the beta group & am now on the released streamer & app versions. Volume is really working OK
I don't use system automation myself so not speaking from experience. However as the new firmware update forces a factory reset perhaps system automation has to re-enabled in the streamer's settings for the volume control to be available on the app.
Since my change to NDX/SN2 I have been using System Automation and I did struggle to work out which Inputs to connect to each other on the NDX front screen menu to get the volume control to show in the App.
Several combinations enable me to use the remote to adjust volume, but eventually I did get to the correct combination to enable the volume controls (+/-) to show in the App (both in nStream and the Naim apps).
So it definitely still works.
As sjbabbey suggests, maybe you have to reactivite it?
maybe you have to reactivite it?
Thanks, I'll give it a go
"Fixed" "my" "problem".
Fixed - not really
my - mine because of poor software writing from Naim app guys, should be Naims problem
problem - no problem with old app
I "confiscated" iPod Touch (gen4 with IOS6.16) from my kids. It still uses latest Naim 3.xx app.
Everything works perfectly. You can also use iPod Touch gen3 or gen2. The same goes for iPhones if the were not upgraded beyond IOS 6.xx.
My phone (Xperia Z1 with 4.4.4 KitKat with Naim app 1.2) will not be used untill this bugs are fixed.
My conclusion is:
Get yourself old or used iPad 1 or iPad 2 with IOS6.xx as maximum upgrade. It is pretty old and unuseful now so no one will use it to surf the web. They are also really affordable now (100 EUR) and the app is in beautiful Naim green colour, which the new app does not have anymore. It is also easier to use and more stable. And you already know how to use it.
Igor

As sjbabbey suggests, maybe you have to reactivite it?
sjbabbey is entirely correct - you just have to reactivate it. Volume control is back where it should be.
Tommay
RE iOS problem where playlists tracks cannot be deleted - this has been confirmed as a bug and will be resolved in the next release
RE Android search not working. This seems to be a lollipop compatibility problem. i.e it works Ok on Android 4.x but doesn't on version 5. will be sorted in next release
Tom