Naim app update

Not just restarted, also restarted the phone, removed the app entirely, reinstalled, tried a different password (you never know..), still the same result. 
Tried iradio within the app too, same issue. 

Installed the Tidal app, and no issue. Also in other apps no issues. Just the Naim app. 

And again, not just my phone, my wife's Samsung Android 6 device too. 

So, next step is to restart the NDX. Maybe something went wrong there, I've setup my whole system again due to new furniture yesterday.  Maybe a coincidence, maybe not.

Edit, restarted the NDX, same result. 

My Android device is doing exactly the same since the update

I am experiencing exactly the same search problems in Tidal with the new Android app version. I think it is because the app now filters in real time instead of waiting for the search criteria to be completed which from a usability point of view is incredibly slow and frustrating. Another problem is that none of my recent searches are listed. I am very surprised that this wasn't found in testing or if it was found it was deemed to be acceptable. It really does need to be sorted.

For info it is the same on 3 different tablets and a phone so it has nothing to do with hardware or Android versions. 

Johnell posted:

I am experiencing exactly the same search problems in Tidal with the new Android app version. I think it is because the app now filters in real time instead of waiting for the search criteria to be completed which from a usability point of view is incredibly slow and frustrating. Another problem is that none of my recent searches are listed. I am very surprised that this wasn't found in testing or if it was found it was deemed to be acceptable. It really does need to be sorted.

For info it is the same on 3 different tablets and a phone so it has nothing to do with hardware or Android versions. 

 

Hi,

This issue has been reported and logged and I believe a fix will be in the next Android release.

Best

Phil

Phil Harris posted:

Johnell posted:

I am experiencing exactly the same search problems in Tidal with the new Android app version. I think it is because the app now filters in real time instead of waiting for the search criteria to be completed which from a usability point of view is incredibly slow and frustrating. Another problem is that none of my recent searches are listed. I am very surprised that this wasn't found in testing or if it was found it was deemed to be acceptable. It really does need to be sorted.

For info it is the same on 3 different tablets and a phone so it has nothing to do with hardware or Android versions. 

 

Hi,

This issue has been reported and logged and I believe a fix will be in the next Android release.

Best

Phil

Having previously posted that I wasn't seeing this problem, I can see it now. Much the same issue when searching UPnP as well.

[@mention:1566878603985147]

Thanks for the update.  Something as basic as this should never have been missed in testing, or even worse, it was found but released anyway.

Johnell posted:

[@mention:1566878603985147]

Thanks for the update.  Something as basic as this should never have been missed in testing, or even worse, it was found but released anyway.

Hi John,

It doesn't affect all users though and didn't crop up with either our own internal test team or the external Beta testers ... It's been reported by (I think) less than a dozen people and we have many thousands of users out there who aren't reporting it as being an issue.

Best

Phil

My apologies for implying that it wasn't tested or ignored Phil but as I said it happens on 4 different devices for me so please forgive the assumption.

Phil, it depends. Not everyone is using the latest version, not everyone is using Tidal (although the issue is throughout the app), not everyone is reporting or even know how to report an issue. And only a few will post a comment in the Play Store.

The fact that in my case two devices in the same household experience the exact same issue, and other people have reported the same issue makes me believe that this is a universal issue. 

Anyway, glad that this will be fixed soon. 

Btw, in the past I ran into an issue with a T+A  streamer in combination with J.River. The J.River people asked me to run an analyzer app and to send the dump which was very handy. Issue was resolved in no time. During typing I'm trying to remember the name of that tool. Maybe you are using something similar? If not, again, could be useful.

Johnell posted:

I am experiencing exactly the same search problems in Tidal with the new Android app version. I think it is because the app now filters in real time instead of waiting for the search criteria to be completed which from a usability point of view is incredibly slow and frustrating. Another problem is that none of my recent searches are listed. I am very surprised that this wasn't found in testing or if it was found it was deemed to be acceptable. It really does need to be sorted.

For info it is the same on 3 different tablets and a phone so it has nothing to do with hardware or Android versions. 

 

I an experiencing exactly the same with the search function:

- unable to type a full name, letters keep disapearing as well as keyboard

- no previous search available

This occurs both in  the Tidal and sometimes the UPnP search.

This occurs on my tablet (acer) and my phone (fairphone), with 2 différent android versions and started with the app update.

I posted a report about the updated app (Android) defaulting to root level of my NAS, and then reported that the app seemed to be working fine.

Sad to report that this behaviour (which is unlike the immediate previous version) occurs intermittently. I have not been able to detect any pattern. Originally I thought it might be as a result of changes to the content on the NAS (i.e. addition/deletion/update of data), but that is not the case. Ho-hummm.

I want to search for an individual track/song/title using the app from the NDS room. Half the time the search icon is missing, if it is present then it mainly allows only search of TIDAL but sometimes allows a full music search. The behavior seems totally random.

I am having problems with the search function with Tidal on my Android tablet as well.

Red Kite posted:

I want to search for an individual track/song/title using the app from the NDS room. Half the time the search icon is missing, if it is present then it mainly allows only search of TIDAL but sometimes allows a full music search. The behavior seems totally random.

The search is not random, but might seem like it is until you've figured it out. In the UPnP input or elsewhere, the search still only delivers Tidal results, unless you are searching the list that is currently on screen. It then searches the screen you can see, so it's only a local search, rather than a 'global' search, so is arguably useless unless you have forgotten the alphabet. 

In order to see this local search bar, you need to be at the top of the list, then swipe down and it will appear. Unless the list is very short, in which case it will not appear as it is then deemed unnecessary.

Thanks, i see the logic in that and can now understand it and get it to work.

However if i close the app and reopen it the search icon is missing. If i am listening to the iradio i have to go to the upnp input but it still wont appear until i actually select a track and start it playing  ( a random one that i dont actually want to listen to  ) then i can search my music.

What i would like is to see the search icon whenever the app starts, and have it as a global search,  or even user selectable to Tidal or Music.

Any updates on the next release? Tidal and UPNP are still unusable. Also, I had an old Asus tablet lying around. Android 4.1.1, updated the Naim app to the latest version and........

The exact same issue. 

So I just cannot believe this is an issue that is limited to a small number of users. 

The workaround I'm using for searching on Tidal is to have the Tidal app open alongside the Naim app, then I run my searches in the Tidal app and anything I save is available in the Naim app when I go back to it.

Not ideal but way better than struggling with the Naim app.........

Now this is puzzling...

Since the Android upgrade to v 2.0, I find that when I select an entire album to play from my NAS via the naim app, some tracks appear in the track listing multiple times. These are, of course, added to any queues, and have to be manually deleted from the queue, which is a PITA, or the tracks play multiple times. The number of multiples seems to be random, sometimes two, sometimes three, but never more.

I have interrogated the server via its proprietary software and from my PC. As far as I can see none of the albums contain multiple 'copies'of these tracks, other than in the naim app. There doesn't seem to be any pattern to this, other than the same album always has the same 'ghosts'.

I tried resetting the naim app (several times), but that doesn't resolve the problem. I have rebooted the NAS (several times) with no success.

Suggestions warmly welcomed, please.

Johnell posted:

My apologies for implying that it wasn't tested or ignored Phil but as I said it happens on 4 different devices for me so please forgive the assumption.

Don't apologize, he is saying "we have many thousands of users out there who aren't reporting it as being an issue", which means that they are not complaining but it doen't mean they are not suffering the problem. In the other hand, the reality is that you are not happy with the product that is not working properly,  who cares if one million people are OK.

Fortunately it controls part of your hi-fi not an artificial pacemaker.

Erich, I offered my apology because I had implied that Naim had released the software without adequate testing, or worse, they had released it knowing there was a problem which was disrespectful of me.

The thing is, I had forgotten how infuriating it was when I had been accused of the very same thing during the 18 years I spent as a software test and systems integration manager prior to retirement.  

I have every confidence that the next release will address the issues............. 

Erich posted:

Johnell posted:

My apologies for implying that it wasn't tested or ignored Phil but as I said it happens on 4 different devices for me so please forgive the assumption.

Don't apologize, he is saying "we have many thousands of users out there who aren't reporting it as being an issue", which means that they are not complaining but it doen't mean they are not suffering the problem. In the other hand, the reality is that you are not happy with the product that is not working properly,  who cares if one million people are OK.

Fortunately it controls part of your hi-fi not an artificial pacemaker.

Hi Erich,

All I'm saying is that as a user if you experience an issue then it is very easy to presume that that issue is being seen by everyone. We have a moderately sized internal test team and none of them experienced the issue with the search text entry while we were testing internally and it wasn't reported from the Beta test team as far as I can see either. We're not all running the latest and greatest Android or Android hardware - myself I have a Samsung Galaxy Tab 7, an Acer Iconian One 10 and an NVIDIA Shield Tablet so a fair spread of devices but I didn't see it on my kit either.

When we get issues reported we do take them seriously.

...and by the way, pacemakers aren't perfect either, mine decides to fight with my natural rhythm about 4 or 5 times a year.

Phil

Phil, three devices here, ranging from new OnePlus 3T with now Android 7.1, old-ish Samsung Galaxy A3 and old Asus tablet with Android 4.1. Exactly the same issues. Complete opposite experience to yours. 

But your are telling now that you haven't seen the issue in your lab, nor in the beta group. This worries me, because if you don't see the issue, how can you resolve it? Or test it? 

Streamz posted:

Phil, three devices here, ranging from new OnePlus 3T with now Android 7.1, old-ish Samsung Galaxy A3 and old Asus tablet with Android 4.1. Exactly the same issues. Complete opposite experience to yours. 

But your are telling now that you haven't seen the issue in your lab, nor in the beta group. This worries me, because if you don't see the issue, how can you resolve it? Or test it? 

If an issue is reported then it may be possible for a software engineer to work backwards from the fault report to identify why a reported issue is occurring even if it has not occurred in testing...

Phil

My difficulty with this new version of Nstream is the way playlist are managed....i 'd a lot of playlist. After the update, none of the file within the playlists were available. i rebuilt all of them...and listen. but the day after, the same thing occured. None of the file could be red.

FDiop posted:

My difficulty with this new version of Nstream is the way playlist are managed....i 'd a lot of playlist. After the update, none of the file within the playlists were available. i rebuilt all of them...and listen. but the day after, the same thing occured. None of the file could be red.

In my experience, the app has always been prone to corrupted playlists. I create them on the server instead, then the app can find them in a folder in the UPnP input. Mine are on a Unitiserve, and can easily be restored from backup, which I don't think can be done with Naim app playlists any more.