Reverting to earlier Android App version

Maybe write an email to the naim support if they can offer you the former version?

I've got exactly the same problem with Android 7 and the current app. Very frustrating. Just about to email Naim support.

Same issue here Huge. I gave up using my Android and went back to my very slow iPad2.

Forgot to mention Android v7.0

Killing the app and reloading restores connectivity.

Huge, I suggest you contact Phil Harris at Naim via the usual email address.

I also have the same issue which Naim HQ are finding difficult to reproduce. In my case on reawakening the phone I get the 'Another App Connected' message. I am able to click OK and then click on my product in the Rooms screen to reconnect. Do you not get that? Just doesn't connect?

I do not have this issue yet. But I am using the insecure Android 6.0.1 and an uniti1 as client (with streaming hardware upgrade of the uniti2).

Those seeing this issue are using Android 7 and which streaming hardware?

gert posted:

.....which streaming hardware?

Synology NAS running Minimserver. It happens with both the MusoQb and NDS.

gert posted:

I do not have this issue yet. But I am using the insecure Android 6.0.1 and an uniti1 as client (with streaming hardware upgrade of the uniti2).

Those seeing this issue are using Android 7 and which streaming hardware?

Samsung Galaxy S8

Also got an the same issue with the following configuration:

Synology NAS -> Asset on Rpi -> ethernet -> NDS  controlled via nexus7 on android 6.0.1

Only option is to kill the app (sometimes multiple times) and then re-start.

This has only been happening for me since the last app update.

i gave up on android  for issue after issue ,reluctantly when over to ipad

OK, we have a further twist to this...

Using a Lenovo P2 running Android 6.01, the Naim app V2.4 works perfectly in exactly the same circumstances.
Given that for a time V2.4 used to work OK on the Pegatron 2 running Android 5.1, I wonder how long this will last?

Conclusion:

It's an Android stability problem   (and not a problem with the Naim App!)

This situation is compounded by the fact that both Android and iOS are designed and managed purely as toys for today's throwaway culture.  It seems that for neither OS is any particular version expected to survive more than about 18 months before you throw it away and buy the latest and greatest device, so they're simply not designed for long term stability; and unfortunately the OS support for apps appears to reflect this lackadaisical attitude.

gert posted:

I do not have this issue yet. But I am using the insecure Android 6.0.1 and an uniti1 as client (with streaming hardware upgrade of the uniti2).

Those seeing this issue are using Android 7 and which streaming hardware?

The insecurity of Android 6 has been overstated, and in fact the fundamental error is in the WiFi implementation allowing Wifi encryption tokens to be cleared using a command transmitted wirelessly rather than limiting security changes to wired comms only.

Any network device holding data should require independent password verification anyway.
(However even here there's a further problem in that UNIX / Linux don't implement standard secure password transmission systems such as Kerberos so you end up sending passwords in the clear, but then you shouldn't be connecting these devices via WiFi).

Oh well Android 6 lasted less than four days and then failed permanently almost as soon as I posted that it's working.

Now after an hour of inactivity (during which it massively drains my phone's battery for no good reason) it makes no attempt to recreate a new connection to the DLNA Server after the existing one has timed out, so the app totally and irrevocably fails from that point on (i.e. the UPnP connection has suffered a hard lock-up).
The DLNA server and 272 themselves are fine and functioning OK as I can use the IR remote to navigate and play files.

At this point, the app will now never be able to connect to the server as it'll never try to open a new connection.  The only way to get the app to attempt to connect again is to kill the app.  Killing an app (either a soft or hard kill) is something that should NOT be done as a general matter on Android, or on iOS for that matter, as it can decrease the stability of the OS (and they're marginal enough at the best of times).

I've just had a reply from Phil Harris. They were aware of this problem with UPnP on Android (losing connection to the media server after Android goes into sleep mode) and have fixed it. It will be sorted in the next update of the App.

An update to the app was released last night - I presume that's the next update referred to, rather than having to wait for *another* one?

It appears to have been updated

from play store:

”What's New
New Feature: Metadata Editing
Fixed: Tidal Browse is blank on first Connection
Fixed: UPnP Servers - fail to discover after resuming app
Fixed: Show Remote Version in About screen
Additional information
Updated
14 December 2017”

Works on my tablet with one caveat...

The screen doesn't refresh when it re-discovers the Media Server(s).  The answer is either to flip from landscape to portrait, or to change inputs and then change back to UPnP!

I get a similar issue, though in my case it's that when resuming the app after a period of inactivity, if the last thing I did with the app was pick something to play via the upnp input, the screen shows the album I last selected to play something from.

From that screen, the back button takes me back to the app home screen. Pressing on the upnp input takes me back to the album, pressing back again takes me to the home screen, and so on - I can't get back to the artist list/album list/whichever way I picked what to play.

Killing and restarting the app fixes it, I'll try changing inputs back and forth next time it happens.

Irritatingly, I've reported this to Naim support for the last two iterations of the app, and it's still happening with the new one.

Ah yes, Dave***T, now that you mention this I remember that I saw this behaviour, too, on my Nexus5. But I do not know which app version this was. A restart of the app did help in my case as well.