Tidal Connect on BluOS-devices not working with Android 14 anymore?

Answered

Comments

149 comments

  • Official comment
    Tony W.
    Product Support Manager

    UPDATED OFFICIAL COMMENT

    This morning, we have released BluOS 4.2.10. This release provides better error handling when IPv6 requests have been rejected from streaming Apps such as TIDAL. We do hope this will make a better experience in the interim. Long term, we are continuing to work with TIDAL behind the scenes. Thanks for your patience and understanding.

  • Tony W.
    Product Support Manager

    Hi Tino

    We are having a hard time replicating this on our end using an Android 14 device. Let's reboot your router, Wait 5 minutes ten reboot the Players. Wait 5 more minutes and then relaunch the TIDAL App.

    If the problem still exists or returns in the next few days, please send us a log file of one of your players by selecting Settings, Send Support Request in the BluOS App so we may review the Player log files.

    0
  • Tino Goratsch

    Hi Tony,

    I've just updated/extended my original post with some additional information.

    But for what it's worth: Playing back music from Tidal with the BluOS Controller app works just fine. "Only" playing back music via Tidal Connect via the Tidal-Android-App doesn't work.

    Rebooting all the devices also didn't do the trick.

    0
  • Tony W.
    Product Support Manager

    Hi Tino

    Go ahead and send us the logs then so our Support Crew can take a closer look.

    0
  • Mark Sanchez

    Same for me. I'm on a Pixel 5 and Android 14. It just shows the generic "Let's add music" screen. It works fine from BluOS on my iMac and my girlfriend's iPhone.

    0
  • Penn Perry

    Same for me as well.  I started a support ticket and sent my logs a couple of weeks ago.  I was put through the same steps.  I also have a Pixel 6a, and this did not start until I updated to Android 14.  I also have no trouble playing through the BluOS Controller App, only Tidal Connect to my Node 2i.  FWIW, Tidal Connect still works fine from my Windows PC app.  Just no luck with the Tidal Connect on my 6a.

    1
  • Tino Goratsch

    Hi Tony,

    sorry for the late reply. I've send the logs (and therefore created the ticket) 2 days ago: #380967.

    Would be glad to hear/see some progress there.

    I've also directed Tidal's support to this thread + my Bluesound ticket number, in the hope, that your developers + Tidal's developer can find the error + solution in a joint effort a little faster. :)

    0
  • Penn Perry

    Hilariously, Tidal has thrown up their hands and asked that I contact Bluesound.  I sent them logs and went through all the usual rebooting and reinstalling steps.  Still no Tidal Connect to my Node 2i from my Pixel 6a on Android 14.  Tidal Connect to Chromecast devices works fine, and the Bluesound app works fine.

    I really like the new Bluesound App, fwiw.

    0
  • Mark Sanchez

    So, I did reboot my Node 2 (2021 version) and Pixel 5 with Android 14 and now have Tidal access. I wonder if it's the 2i's code base that's causing issues?

    0
  • Penn Perry

    No idea, but I did try rebooting both my 6a and my Node 2i, to no avail.  Tidal Connect from Windows 10 PC app to Node 2i, works fine.  Tidal Connect from Android app to Chromecast devices, works fine.  It's just Tidal Connect to the Node 2i from Android app that doesn't work for me.  Since updating to Android 14.

    0
  • Tino Goratsch

    Because of reasons (at least for now), Tidal Connect seems to work with my Node 2i and Pulse M again, but my Pulse 2i still doesn't want to corporate...

    Update: It stopped working on the Node 2i and Pulse M, but now it suddenly works with the Pulse 2i...

    0
  • Penn Perry

    My Tidal Connect has worked for a few minutes a couple of times with the Node 2i, then stopped working.  No rhyme or reason, as far as I can tell.

    0
  • Penn Perry

    I'm wondering if anyone besides me is still having this problem. I still cannot get Tidal Connect to work with my Node 2i using my Pixel 6a on Android 14.

    0
  • Tino Goratsch

    Yes - I'm still having these problems, too. But - sometimes it works, sometimes not - really strange... :/

    1
  • Penn Perry

    Same here. No rhyme or reason. Spotify Connect works fine, fwiw. But Tidal Connect is still mostly a no. Frustrating.

    1
  • Alexander Meyerzon

    I'm having the same issue as well. I've tried rebooting, restarting, etc.. 

    0
  • Darko Meic

    Same problem with Tidal Connect on Powernode Edge. Tidal sometimes works fine and than it won't connect no matter what I do. Spotify works every time.

    0
  • Alexander Sitz

    Got the same problems on my Samsung Galaxy s23+ with android 14.

    Tidal Connect doesnt work with the app. I see both my Node 2i and my NAD 778 available for selection. But nothing happens when I try to connect.

    Playing via the Bluos app works as well as with the Tidal app under Windows 11 (i can select both, Node and NAD from the Windows app without problems). Seems to be some problem regarding the mobile android app.

     

    Tried reinstalling the tidal app, Rebooting my internet router, rebooting my phone.

     

     

    Edit 23.11.23:

    It's working again on both of my players. Not sure why though. Maybe some random bug. First it worked only on my t778 again and then a while after also on my node 2i. Hope it stays that way.

    Edit 2.12.23:

    Well. It didn't stay that was. Actually worked only again that one time. Didn't try that often last week but when I did, no luck. Guess we have to wait for a fix

    0
  • Tino Goratsch

    Did anyone of you also raised an issue at Bluesound and Tidal like me?

    Unfortunately, Tidal and Bluesound are pointing their fingers to each other, which is quite a bummer. Hopefully - the more people submitting the problem to both of them (and maybe even pointing to this thread), will eventually put some pressure on them to actually find and fix the problem...

    0
  • Penn Perry

    Oh man exactly the same for me. Tickets in both places, very similar troubleshooting steps in each, eventually leading to a request that I contact the other service. I have been referencing this thread on both of my tickets as a way to make clear that others besides me are having this issue.

    0
  • Stefan Wimmer

    I am in the same boat as everyone else. Tidal Connect worked mostly fine for two years, but now is showing an erratic behaviour with the 2i. until today I was at least able to see the Node in Tidal and "only" had connection issues - it tried to connect for a couple of seconds, then stopped. Sometimes clearing the cache helped, sometimes signing out and in.
    Today the Node has vanished completely.
    Also using Android 14 on a Sony Xperia 1 v. I guess I am going to switch to a Wiim...

    0
  • Penn Perry

    Just an FYI.  I have a separate ticket open with Bluesound about this issue, and the customer service rep just reported that Bluesound has been able to replicate the issue with Android 14 and my Node 2i.  So, some progress.  Tidal has been completely unhelpful and only asking me to contact Bluesound.

    2
  • Tino Goratsch

    That's really good news @Penn Perry - fingers crossed, that the issues get's resolved quickly! :)

    On a more or less unrelated note: I just got an update of the Tidal's Android to version 2.95.x and all my BluOS-devices seem to work again - for now...

    0
  • Penn Perry

    Fingers crossed here too.  And that's great about the new version of Tidal's Android app.  Hoping to see it here soon.

    Also, I find it ironic that the new version of the Tidal app seems to resolve the problem, given that they never even admitted to a problem on their end and just constantly referred me to Bluesound.

    Thanks for the info.

    0
  • Tino Goratsch

    Cheered to soon - after a simple restart of the Bluesound Pulse 2i, Tidal Connect isn't working anymore.

    So - I'm glad that at least Bluesound/Lenbrook finally can reproduce the issue.

    0
  • Penn Perry

    Totally unsurprising. That's the way it's been for me for over a month. It works for a few minutes, maybe after a restart, maybe after an uninstall/reinstall, then down it goes again.

    And agreed about Bluesound being able to replicate the issue. Fingers remain crossed.

    0
  • Arnold Greidanus

    Same here, with my Pixel Pro 7 and Node 2i. Have also cleared cache, disconnected and reconnected to my router, which occasionally did the trick, but now Tidal Connect is not responding whatsoever. Very frustrating.
    Also, I'd like to add that before upgrading to Android 14 Tidal Connect was also unstable at times, dis/reconnecting the phone to my LAN usually being the solution to get it working again.
    I hope this soon will be solved!

    1
  • Paul D

    Just adding my "me too" post.
    OnePlus 11 using Android 14 with Powernode Edge.

    Struggles, but finally does, connect to BluOS though sometimes loses it, but only managed to use Tidal Connect once in 10 days
    Spotify Connect works fine (someone on Reddit pointed out that SC works regardless of being on the same network, suggesting it's network related, rather than directly Tidal/BluOS?)

    0
  • Kristof Jozsa

    Add me to the list, I can confirm everything above. Having a Pixel 6a also running the latest Android 14,it's a hit and miss, it works about 20% of the cases and doesn't work some hours later again.

    To add to the picture, I'm running a Unifi mesh at home with an ad blocking Pihole dns server, but I could not pinpoint the issue to either of these.

    I'm highly technical and willing to help with anything if needed, just leave me alone with that reboot your router thing..

    1
  • Penn Perry

    Glad more and more of us are on this thread.  I am also tired of the reboot suggestions.  And I do not believe that it is network related.  Tidal Connect to my Node 2i works fine from my desktop, just not from my Pixel 6a on Android 14.  Spotify Connect works fine from both.  Other network devices in my house working as they should.  I'm pinning my hopes on Bluesound having replicated the problem.  Tidal has been pretty much unhelpful.

    0

Post is closed for comments.