Android App 2.5 continuing connectivity issues

I've asked Richard to change the tread title to

"Android App 2.5 continuing connectivity issues"

to try to keep the thread more focussed.

There you go Huge.  

Have you been in touch yet with anyone for Naim on this?

Thanks Richard,

I wanted to see if some people had found it fixed; as if it's just a one off in my system, then something else odd is happening here in my network!

You are not alone Huge my Samsung Galaxy S8 running Android v7.0 hung last night running Naim App v2.5. Had to force the app to close then reopen.

I have similar issues but of an intermittent nature and have informed Naim who gave me a reference number. As a work around I set the Naim app to always connected whenever I get "cut off". Only problem with this is that the phone can run warm and you may need to keep an eye on the batteries.

I'm running the 2.5 Version of the Naim app on a OnePlus5T with Android 8. It seems to be working okay at the moment, as in, it does stay connected and finds my SuperUniti when I open the app.

Unfortunately there are still issues with the Tidal integration. For one, the app keeps on going back to the Tidal main screen, even after I choose my playlist, it just jumps back. which is very annoying. Secondly the search function doesn't always work. And third, if I have been using Tidal,  when I try to go into uPnp, to listen to my own music, the app opens Tidal again. It's as if Tidal takes over the app, and the only way to solve this is to quit the app and re-launch it.

Not sure if this is just me or do others have this same issue.

OK, from the responses, this appears to be something odd and specific to my system at present.  I'll investigate my system further to find what the cause is now.

I have an idea looking from at another issue I have and tracing it back in time to a point when both the Naim app and the OS on my NAS were updated (the two Android devices updated the Naim app at different times either side of the NAS update, which confused things).  At the moment my working hypothesis is that this is an interaction of the two changes and the way that the Naim app behaves differently on the two devices.

Just spotted the thread - I have actually not listened to any music for a few days, because I am tired of - every time I put the screen in sleep mode, I lose Minimserver and have to switch my android pad off and re-start it to continue.

If this is caused by an interaction of various updates, then it is beyond me to fix !

I have been busy or I would have contacted support (which I must do) - but enjoyment is obvioulsy greatly reduced by this inconvenience

Still happens to me Huge, the old losing connection (spinning circle) after device reawakens issue.

This has been well reported, also via the Beta test team, and HQ are aware. I'm sure its being worked on (amongst other issues with the Android app) and we will see a new release at some stage.

It has been like this for some time though, so I'm looking forward to the resolution when it eventually arrives.

So far it seems that there's a timing problem...

The Naim app seems to allow about 1/2 a second for the Media Server to respond - you briefly see the rotating circle - before it draws the screen (whether the data are ready to be displayed or not).  If the data haven't been supplied by then, you either get a blank screen or "No Results Found", depending on which screen it is.  If the data arrive later than the screen redraw then you can't select anything from the screen!   If this happens on the tablet, rotating the device at exactly the right time can sometimes get it to redraw the screen without restarting the data fetch, but as rotation is disabled for the phone (for no good reason!), this option isn't available on that device.  

If it doesn't redraw properly...     Game over!

I have a single core NAS and it is often doing something else (e.g. OS tasks) so can take a second or so to respond, by which time the Naim app has redrawn the screen giving nothing to select. Preventing a portable device from entering sleep is NOT an acceptable solution, as it compromises the battery and causes cumulative hardware damage.

I believe the latest NAS OS update has slowed the NAS quite a bit (Linux and other Unix like kernels are inherently vulnerable to Meltdown and Spectre and the prevention has has particular impact on single core devices like mine - this could be the reason for the slowdown).  This may be the reason why the problem has been exacerbated.

With this situation I can use the app about 1 time in 3.