Naim app Android 1.7

The new version seems to work much better. I have not had any crash yesterday, even when switching between ipad and Nexus5. Also it seems to reconnect to the uniti much faster now. Nice.

Yeah, it's a considerable improvement. I'm a bit surprised at the lack of fanfare. I'd edit the title of the thread to highlight that it's new, but the edit function seems to have disappeared!

Android version of the app is not getting much love here, I've noticed...

Dave***t posted:

Yeah, it's a considerable improvement. I'm a bit surprised at the lack of fanfare. I'd edit the title of the thread to highlight that it's new, but the edit function seems to have disappeared!

Dave,

you could try the "Report reply" option via the "Take Action" link to ask Richard to amend the thread title for you.

I didnt even notice it had auto updated until I read this thread, but yes, my impression of it is also that it is really good, especially in light of the not great beginnings with the Android App. No crashes at all.

I also have a couple of iOS devices and I wouldnt say there is much, if anything, between them now. The lack of Rovi database on Android App is the only real differentiation now.

it always gets left behind. which is not right.  with the muso family I would guess there are more android customers 

I also noticed incredible stability/crash enhancements! Great job!

Although, switching from my NAS playlist to DAB works fine, but switching back from DAB to my playlist still doesn't work. It mentions "Stopped", which is true of course, but in this state I can't see my playlist anymore, so I can't start it either. Only way to let the playlist start again, is pressing the "play" button on the real remote...

Yeah, the stability is streets ahead of what it was.  One or two hangs is all I've had so far, nothing like the crashfest prior to the update.

I have had a new problem crop up, though.  Having selected something to play via UPnP and then left the app alone for a while, when I go back to browse UPnP, I'm returned to the root, i.e. back to the server selection.  Doesn't seem to happen if I return to the app quickly, it stays on the album I'd selected for a while.  But only for a while.

I barely use playlists, so can't comment on those, but there seem to be a few unsquashed bugs left, perhaps.  No Rovi or anything either, of course, but one step at a time.

sjbabbey posted:

Dave***t posted:

Yeah, it's a considerable improvement. I'm a bit surprised at the lack of fanfare. I'd edit the title of the thread to highlight that it's new, but the edit function seems to have disappeared!

Dave,

you could try the "Report reply" option via the "Take Action" link to ask Richard to amend the thread title for you.

Cheers for the suggestion, but I'll leave him unmolested for the time being

One issue I have with the naim android app, while I am not sure, if it is a new one: Sometimes when opening the app for the 2nd time, e.g. from the app window history or simply by touching the app icon again, the app just shows a black screen and hangs. The whole phone hangs and does not react for some seconds. If I try to open the app window history again, it then takes approx. 10 seconds to react. The best way to get into the naim app again is to kill it (by swiping away the app window from the android history) and restart it again. It feels like the app consumes so much memor, that the phone is swapping.

My device: Nexus5. 

Is this a lack of free memory? A too big list of music data in the library? Or just a bug? 

That'll be a bug. I get it too, though seemingly less than I did prior to 1.7.

A Nexus 5 should be easily capable of displaying a very long list of information - it's a computer with 2GB of RAM, not a 3210. Same goes for my LG G3, which sometimes does the same thing.

The proof of the pudding is that once you kill the app and restart it, it works again - all other processes still running.

Stability is much improved with 1.7, but still some kinks to iron out.

I have been using  using Android 1.7 with my UnitiQute 2 for a couple of weeks.  It was my first introduction to Naim software, and a user manual would have been useful.  Perhaps I did not look for it in the right place?   It took some time to find my way around the menus so I could play and album or a group of tracks from an album.   Some things seemed counter intuitive at first , (like choosing 'play next' for three successive tracks puts them in the queue in reverse order!).  I now want to come up with a simple step by step guide for other family members to use which should be "no more complicated then putting on a CD!"  Perhaps such a thing already exists on this forum?  If so a link would be most appreciated.

I wonder if someone could give me advice on a couple of points.  First is how to best navigate back to the album list after the an album has finished playing?  Sometimes I have found that a few touches to the 'back' triangle on the Nexus 7, will take me there but other times a single touch goes to the input selection page.  I have not yet worked out when this occurs and how make sure to always use one or the other..

Secondly is that I have found that some options for adding to the queue clear the queue automatically, but others do not.   Checking the contents of the queue before starting play would help, but I could not find how to do this.  Could anyone advise me on the best process for adding an album, or a group of tracks from an album  to the queue?

magicia posted:

 Checking the contents of the queue before starting play would help, but I could not find how to do it.  Could anyone advise me on the best process for adding an album, or a group of tracks from an album  to the queue?

 

Hi Magicia, you can find the play queue by touching the Now Playing section at the bottom of the screen (when you are looking at what to play in UPnP or Tidal for example) and then touch the button on the right hand side of the <||> controls. This will give you the Play Queue, and you can toggle between the Track Playing and the complete Play Queue.

To add an album, touch the '...' at the top of the screen by the album title and select Queue Next/ Queue Last.

To add a track to the queue touch the '...' by the side of the track or tracks you want to add and make your selection.

Hopefully this will help?

It takes a little while to suss it all out, but once you have it it's a diddle.

Good luck!

magicia posted:

I wonder if someone could give me advice on a couple of points.  First is how to best navigate back to the album list after the an album has finished playing?  Sometimes I have found that a few touches to the 'back' triangle on the Nexus 7, will take me there but other times a single touch goes to the input selection page.  I have not yet worked out when this occurs and how make sure to always use one or the other..

Inconsistent back button behaviour (be it with other instances of such behaviour within the app, or with how the back button is generally understood to work in other contexts) is one of the criticisms I have of the Android app, and that I've seen others mention too.

Generally I just press back until either I get where I expected to be, or I get to the home screen for the Naim device in question.  If the latter, tapping UPnP usually takes me where I was aiming to be.

That's complicated a bit by the new intermittent issue of the UPnP browser going all the way back to server selection as opposed to where it was when you last browsed your library.  But in general it's how to go about it IME.

ChrisH posted:

 

Magicia, you can find the play queue by touching the Now Playing section at the bottom of the screen (when you are looking at what to play in UPnP or Tidal for example) and then touch the button on the right hand side of the <||> controls. This will give you the Play Queue, and you can toggle between the Track Playing and the complete Play Queue.

 

Thank you for your clarification.  

One more question.  Do most people use the  "Tap for options" setting?  I selected it at first because I found my fingers often missed the three dots on the right of track, which triggered Play now instead of Queue last, but is does add an extra step is the selection process and I later deselected it.  I wonder if it offers any other advantages?

Dave***t posted:

 

Inconsistent back button behaviour (be it with other instances of such behaviour within the app, or with how the back button is generally understood to work in other contexts) is one of the criticisms I have of the Android app, and that I've seen others mention too.

Thank you.  I am relieved that the inconsistent behavior of the back button is not due to any inability to use it appropriately on my part.  Incidentally, does the X on the top left corner duplicate the back button?  

I hope there are not too many examples of similar behaviours in the Android app.  I want to avoid having to use an iPad if at all possible.

magicia posted:  One more question.  Do most people use the  "Tap for options" setting?  I selected it at first because I found my fingers often missed the three dots on the right of track, which triggered Play now instead of Queue last, but is does add an extra step is the selection process and I later deselected it.  I wonder if it offers any other advantages?

I still have it enabled because of the same reason why you had enabled it first. It is very annoying to delete the whole playlist just because of an mistouch. If there was the choice to enqueu it on touch, I maybe would select this. But the extra touch for the opening 3dot-menu is not a problem for me.

magicia posted:

Dave***t posted:

 

Inconsistent back button behaviour (be it with other instances of such behaviour within the app, or with how the back button is generally understood to work in other contexts) is one of the criticisms I have of the Android app, and that I've seen others mention too.

Thank you.  I am relieved that the inconsistent behavior of the back button is not due to any inability to use it appropriately on my part.  Incidentally, does the X on the top left corner duplicate the back button?  

I hope there are not too many examples of similar behaviours in the Android app.  I want to avoid having to use an iPad if at all possible.

If by use an iPad you mean use one that you already have then frankly I think I'd use it - the iOS incarnation of the app seems to receive more development attention, and gives you access to Rovi, which was nice when I tried it on a borrowed iPad. The recent update to the Android app seems to have closed the stability gap between the platforms somewhat, but the iOS version remains the one to have IMO.

But if it means buying an iPad, I sympathise entirely. I simply refuse to buy something like that to use as a remote control when I already have multiple android devices which are easily capable of doing the job. The Android software should just work. And yes, I'm aware of the irony of that choice of words

My iPad only runs iOS 5.1, so I cannot use it for the Niam iOS app.  

I will try and do as you did, and borrow one.

Has anyone else noticed that the audio settings category in the settings menu has disappeared?

I tried to pull it up to mess about with balance, and can't find the audio settings heading or any other way to change balance control. It was definitely there previously.

You are right. The android app is missing the audio menu item!? In the iOS app it is still present.

Just an update to say I've mentioned it to Naim support, and sent them a screenshot of the settings menu in the app (i.e. with no audio settings entry in the list).

Fingers crossed there'll be a fix.

This is good news to me - I do not wish to buy an iPhone

I quickly need to buy a tablet - can anyone recommend the cheapest reasonable android tablet to use the Naim app for my imminent NDX

Thanks

Al

I use a Medion Lifetab tablet - about £70 from Aldi - it's functionally as good (and actually better re storage and connectivity) than an iPad I used for a few weeks.

gert posted:

One issue I have with the naim android app, while I am not sure, if it is a new one: Sometimes when opening the app for the 2nd time, e.g. from the app window history or simply by touching the app icon again, the app just shows a black screen and hangs. The whole phone hangs and does not react for some seconds. If I try to open the app window history again, it then takes approx. 10 seconds to react. The best way to get into the naim app again is to kill it (by swiping away the app window from the android history) and restart it again. It feels like the app consumes so much memor, that the phone is swapping.

My device: Nexus5. 

Is this a lack of free memory? A too big list of music data in the library? Or just a bug? 

One time the android app was not able to find my uniti anymore. (I do not know what was wrong!?) So I added it manually to the android app by entering a name and its IP-address. (I have configured my router to always set the same IP address for a device.) Since them I had not have any hang and time out problems anymore. So entering the streamer manually to the app might be a workaround for this? (Probably the problem occurs again the next time I will use it after mentioning it here? )