Tidal Connect on BluOS-devices not working with Android 14 anymore?
Answered
Hi,
I recently updated my Google Pixel 6a to Android version 14 and it seems, that this resulted in not being able to playback music via Tidal Connect anymore (i.e. from the Tidal App) - at least for all of my BluOS-based devices:
- Bluesound Pulse 2i
- Bluesound Node 2i
- Bluesound Pulse M
The Pixel 6a is still on Android 13 and there everything still seems to work.
Steps to repeat:
- Start the Tidal Android app
- Start playback of music
- Select one of the Tidal Connect capable players from the devices list within the Tidal app.
Expected result: Playback gets handed over to the selected Bluesound devices.
Actual result: It tries to shortly connect to the devices, but then suddenly stops. The music playback stops, too.
Furthermore, I've got another Tidal Connect capable device from a competitor (Lintech Airlino+) and there everything still works (even with Android 14), that's why I'm reaching out to this forum, as it could be a BluOS specific thing?!
Playing music from Tidal via the BluOS Controller also works just fine.
I've also already reached out to Tidal directly - I can forward the ticket number to a Bluesound support rep if needed.
Best regards,
Tino
-
Dear all,
I recently bought a Node and I am struggling with exactly the same issue as yours. That is my PC can easily stream straight from Tidal Connect onto Node/Bluesound, however my Samsung S23-Andoid 14 is not working through Tidal Connect even though the Node device appears on the interface. All my apps are up to date.
I also aksed the Tidal Support team and they mention 'they can't replicate the issue' and consequently refer to... you guys.
Any chance you could give me a way out (I already tried to reboot the node, my server, ...nothing works).
Thank you in advance.
Best
Olivier
0 -
Ten weeks now, and still no solution to this problem. I must admit that my patience is wearing thin. Especially now that it is obvious how many albums are missing when accessing Tidal through the BluOS app. And still no official acknowledgement from Tidal that there even is a problem. Ugh.
1 -
Here is, what works for me (Google Pixel 7, Android 14.x (latest), BlueSound Node N130):
- I made sure, that TIDAL has all the privileges (Application Info > Privileges). I was wondering, why it had not requested all of them yet, however it probably at least needs "Devices near me"
- If Tidal Connect does not work in the TIDAL App, I launch the BluOs App on my phone and restart the node from the "Diagnosis" Menue. It takes less than a minute to restart and I am good go: Tidal Connect works again - at least for me.
- I haven't checked yet, if a powercycle would do the same trick.
- (Be aware that my phone is in German and I translated the Menue entries so they may be labeled differently)
This works reliable for me - a little bit annoying, not ideal, but at least a temporary work-around I can live with until it is probably fixed (hopefully soon).
Since I only restart the Node N130 and not the Tidal App and I heard that Tidal Connect works reliable on other devices, it unfortunately sounds to me like a bug in BluOs and not in Tidal. Sorry folks!
0 -
2 days in a row now, I'm able to connect to my Powernode...
Didn't see any updates (Tidal desktop got one), working for others now?
0 -
Still a no for me. Rebooted my Node 2i and it worked for a few minutes. Then back to the usual. Tidal can see the Node 2i, but it cannot connect. Bleh.
-1 -
2 days ago, I also suddenly could seamlessly connect to BluOs again. Well. My happiness only lasted one day...
0 -
Not working for me at all for weeks now. Initially I made it to work by reinstalling Tidal, but now nothing works. I've tried all of the suggested workarounds with no luck. BTW I'm using Pixel 6 Pro.
As I've said several times before: this company and their products are terrible. Their marketing is that they're offering premium, hi end audio equipment which can't be further from the truth. Since I bought my Node all I'm experiencing are issues (Wifi/Network, using external DAC, Tidal support etc.).
They said that the solution for Tidal's move to Hi res FLAC is to offer both worlds, FLAC through Tidal Connect and MQA through BluOS Controller. This thread is the best example of how Tidal Connect is "working".
This leaves users with having to listen to CD quality because Tidal no longer offers MQA for a lot of their catalogue and we can't use new hi res FLAC.
Not to mention that every fix takes ages for them. Even the most simple ones (and I can presume which issues are trivial or small, since I'm software engineer for a long time now).
Laughable and you should be ashamed of yourselves!
1 -
Well said. I have not had as many problems with my Bluesound product as you seem to have had, but the MQA/FLAC debacle has me wondering if I should go a different direction.
0 -
Carsten Bock's workaround works for me most of the time.
I.e.: within the BluOs app choose Diagnostics from the Settings wheel menu, and choose Restart.
BluOs will then reload. It may be necessary to answer the prompt 'Try again' a few times, but usually it loads after 2 or 3 retry's. (Exact labels/prompts may differ, as I translated them from Dutch).
Then open Tidal Connect and choose the BlueSound Node2i as output device.
Most of the times this works.
When it doesn't, I close all apps on my phone and repeat the above.
(As mentioned before I have a Google Pixel Pro 7 with Android 14).
Still: this is a workaround and Tidal ought to deliver a solution!
I am also considering alternative streaming services.0 -
I fear that this thread, having been assessed, will no longer be considered. However, yesterday my S22 had an Android update, without any particular notes and from that moment, the connection between Tidal and the Bluos module has always been possible without having to do the usual multiple reboots. I tried all the possible combinations that led to no connection, from switching between different streaming apps to closures and pauses of various durations, all things that ended up no longer allowing me to connect and since yesterday I have always managed without having to restart anything. I hope I don't claim victory too soon but something has statistically changed, it would be interesting to know what.
0 -
I hope that Bluesound is still monitoring this thread. It is honestly the only place where I have seen official comments. Regardless, here's hoping your issues are fixed with the Android update. And of course, here's hoping fixes are coming down the pipe for all of us.
0 -
The work-around from Andrew H worked for me. I'll add that I've not experienced the same issue with the WiiM streamer that is connected to one of my other receivers. It also uses Tidal Connect.
0 -
Tony, thanks so much for the updated information. I just completed the update to 4.2.10 and was immediately able to use Tidal Connect from my Pixel 6a to my Node 2i. I disconnected and reconnected several times.
Because I've had so many false starts, I'm going to hold off saying that the problem is fixed, but my fingers are all crossed. Here's hoping...
0 -
I updated and was able to connect immediately. Fingers crossed, but this seems to be the breakthrough we were all waiting for eagerly. Tony, thanks!!
0 -
I can confirm that after the upgrade to 4.2.10 I was immediately able to use Tidal Connect (which I wasn't able to do for weeks now, no matter which workaround I tried).
However, following my previous experiences with this product and company I'll give it at least 10 days of heavy usage before calling this issue fixed.
0 -
At last !!!! I can confirm all is working now. Interesting that after pointing fingers at Tidal, the BluOS firmware gets updated and the problem melts away.
0 -
Works for me as well. One minor thing to add. Everytime I select a song tidal shows a message:
"failed to connect to server. Check your Internet connection or go..."Doesn't stop or interrupt the playback but thought it might be useful information to share.
Thanks a lot for solving the problem and continuing to work with tidal! Great support. Much appreciated.
0 -
Tony, thanks to you and your team for your perseverance on this problem; finding out it was an IPv4 vs IPv6 issue sounds pretty subtle -- HugOps to everyone on your side.
Another happy "Works For Me" after the upgrading my PowerNode to 4.2.10.
0 -
FWIW, it's so nice to see all the positive comments. Glad the fix seems to be working.
0 -
Yes it works. The yesterday's Android update, already improved something also but now it seems anytime well. As Nad user, just a little thing (or two) keeps me not completely happy, first on subwoofer channel, there is a bump noise at any song sample rate change. Nad support recognized the issue but cannot tell me when will be assessed. I didn't understand if is Bluos or Nad matter. Secondly, sometimes on song sample rate change, with Dirac on, a distortion appears on one or both channels and to recover it I have to skip back and forth. Anyone experienced those? And again, is Bluos or Nad (or even Dirac) issue?
0 -
I can also happily report, that Tidal Connect seems to be working again with all my Bluesound devices with the update to 4.2.10. :)
Let's hope, that https://support1.bluesound.com/hc/en-us/community/posts/19349955955351-Update-seek-bar-every-1-second-instead-of-every-5-second-with-Tidal-Connect now gets resolved quickly, too (at least it is already acknowledged by Bluesound). :D
0 -
Works for me too. Many thanks for your perseverance.
0 -
Still working well.
I must add that with 4.2.10 on the nad c3050, I no longer had the sporadic freezes that I encountered when navigating between services or web radios, which required a reboot, nor even sporadic distortions on the next song, when the sampling rate changed.
0 -
I am pretty happy that the issue got resolved. It is likely one of the bugs that are hard to identify, as it may have seemed to happen in some edge cases. Disabling IPv6 in my home network would have likely temporarily solved it.
So far, even after a few days, everything seems pretty stable. I somehow managed to crash my Node once, and as a result, the Node disappeared in the TIDAL app until I restarted the Node. I could not reproduce it, nor did I gather any logs. I will happily share the logs in a new ticket if it happens again.I just wanted to thank the folks at Bluesound for solving the issue.
Even though I considered replacing my Node at some point, I am now happy to continue using it.
0 -
I feel the same way. So glad this is resolved, happy to continue using my Node 2i.
0 -
I have the same problem and it persits with version 4.2.10.
The bluesound app also seems to have trouble finding music on tidal through the search function when this problem occurs.0 -
This is odd - issue should be fixed for everyone by now. When your BluOS app doesn't find Tidal through search, was it able to find the other services instead?
0 -
Hi Eugene
Likely a network discovery issue it corrupted routing table. Please reboot your router, wait 5 minutes, reboot the player and wait 5 more minutes... if problems persists or return, e-mail support@bluesound.com
0 -
For me Tidal Connect is not working.
Tidal:2.105.2
Bluesound: 4.2.10Two Devices not shown. NAD C389 and Pulse Flex 2i.
Spotify Connect works flawless.
Android 14 S24 Ultra.
Disapointing :(
1
Post is closed for comments.
Comments
149 comments