4.11: Android app loses connection to player

Answered

Comments

44 comments

  • Official comment
    Tony W.
    Product Support Manager

    UPDATED OFFICIAL COMMENT

    This took a while but we have located the source of this issue. In the latest version of the Android App (4.4.1) we have moved to a more server-driven design. We are seeing an undue delay in receiving updates form all the Players in your system. If the last player you used is affected by this delay, you will see this prompted message. Our QA Team is currently beta testing a fix. Look for an update to the Android App about mid-next week to resolve this issue long term.

  • Ton Zandbergen

    I have the same problem. Rebooting my router, deleting the App, reinstalling did not have any result. 

    2
  • Bjørn Ulvik
    Hi-Res

    Same here.

    2
  • 20hz

    Same here. It's as if the app forgets which player it was last connected to and instead just list all the players it can find on the network. The one it was last connected to (Living Room, in my case) is literally right there in the list. This has never been an issue prior to 4.11.

    2
  • Bodi

    @Tony, what happens to this thread/issue now? Are you reading this, is the issue still open/reopened?

    2
  • KriHad
    Lossless

    Same here.

    1
  • KriHad
    Lossless

    Thanks Ton and Bjørn.

    1
  • Bodi

    I guess we're all having caching issues :)

    1
  • Bodi

    Seems to happen everytime I go out of the house and return.

    And indeed: after I disconnect from my WiFi network and reconnect, Bluesound app doesn't know about the last used player anymore. I guess the dreaded caching problems are on your end Bluesound :)

    1
  • Anders Stedtlund

    Ye, same here. Rebooting, clearing cache and such does not help. Started 4-5 days ago. It happens even without disconnects to the wifi. Though, if I disconnect and reconnect to the wifi it happens all the time.

    1
  • Jakob Gooijer

    Same here. Reboot doesn't solve the problem

    1
  • Max Dekker

    Same here!

    1
  • Bodi

    Thanks for the update Tony.

    1
  • 20hz

    Well, it seems to work fine for me after the 4.4.2 update, and I can no longer reproduce it by switching WiFi off/on either.

    EDIT: No, unfortunately the issue is still there, though more infrequent now.

    1
  • Bodi

    Good for you and I mean that. As you can see above, there are still people experiencing the same problem. Im afraid this will be one of those bugs bluesound will/cant fully fix

    1
  • Mal Godwin

    I had same issues about six months ago with all 3 of my Nodes. Tried all the reset nonsense. Didn't work. Swapped out the Vodafone modem for the old one. My 3 Nodes were then lighting fast like before. My issue was the new Vodafone modem. Strangely if I ran my nodes off the guest WiFi on the new modem, they were perfect. Also running the Node off a hotspot from a spare phone worked also. In the end I bought a new Modem and connected it to the Vodafone one. Had the new modem give out the IP addresses and manage all network. All nodes flawless since.

    1
  • Tony W.
    Product Support Manager

    Hi Bodi

    Likely some caching issues between your router, App and players. Please reboot your router, wait 5 minutes, reboot your player, wait 5 more minutes then kill and relaunch the app on your phone or tablet. If problems persist, please e-mail support@bluesound.com so we may take a closer look.

    0
  • KriHad
    Lossless

    LOL

    0
  • Kevin

    I also have this problem on my Node and Flex.

     

    Plus, on the Flex, since the last update, it sometimes stops playing music (tunein or my own nas) for a second (and sometimes even up to 5 seconds), and then just continues playing like nothing happened.

    Wifi range is exellent with 50dBm strength and on channel 1, with no interference from other networks, and it all works just fine on the Node. I've even put the Node in the Flex's spot and no issues. 

    0
  • 20hz

    @Tony

    Great news, thank you very much. Looking forward to the update.

    0
  • Bodi

    Android app versione 4.4.2 didn't fix this problem.

    0
  • Ton Zandbergen

    That is also my conclusion

    0
  • Jakob Gooijer

    It fixed other problems ( Grid/List) but not this one unfortunately

    0
  • Fraser Wilkinson

    Just updated to 4.4.2 and the 'Looking for players' issue seems to be resolved, however, the problems with play start time and accuracy persist (these began with the last player update a couple of weeks back). When I use Spotify Connect, as I always have, it now takes 10-20 seconds to begin playing, and it plays the next track - not the one I'm trying to play. Once it is playing, any subsequent commands (next track, pause, rewind, etc) take 10-20 seconds to execute. It's horrible to use, I'm afraid.

    0
  • Bodi

    The issue is still there but more infrequent yes. I also found out that the app doesn't remember the last selected player, so I have the switch to the last used player quite a lot.

    0
  • Bjørn Ulvik
    Hi-Res

    Same as Bodi, this is ridiculous!

    0
  • KriHad
    Lossless

    It's all back to normal since last app update, thanks.

    0
  • Bodi

    It clearly isnt. Are you on 4.4.2?

    0
  • KriHad
    Lossless

    Sure am. All is perfect.

    0
  • Sebastian

    Same for me... Had this occurring for weeks. Pretty annoying

    0

Please sign in to leave a comment.