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
-
Hi folks, updated Oneplus 9 Pro to android 14. Tidal connect for Node 2i and Node 130 no longer working. Tidal connect for Wiim mini works fine.
0 -
Tidal connect avec bluos et bluesound node 2i ne fonctionne pas sous android 14 avec Samsung one ui 6 et même avec une tablette Samsung android 12 tidal connect se coupe c’est catastrophique au niveau fonctionnement avant je n’avais pas de problème qu’en est il des correctifs???
-2 -
Node 130 working now. All I did was unplug it
Exclusive mode also works now.
Perhaps there was an auto update - not sure. Node 2i still doesn't work and has not been unplugged. Will do the same with it later.
0 -
For me it works every other day. Yesterday it worked again and today it doesn't. Really weird.
0 -
Interesting, yesterday Tidal Connect refused to work. Than I opened Spotify Connect, started one song, back to Tidal Connect and voila! Same thing today.
1 -
Actually that just worked for me as well. Thanks for the workaround until it hopefully will be resolved completely.
1 -
Reporting in that the Spotify Connect workaround did not work for me. Still no luck connecting to Tidal from Pixel 6a on Android 14. It will work every once in a while, but never for long. Tidal always sees Node 2i, but cannot connect.
0 -
Mon samsung A53 est sous android 14 version ONE UI6 mon lecteur bluesound node 2i et bluos sont à jour et je ne peux plus lire tidal je vois mon bluesound sur le haut parleur de tidal mais rien ne se passe.
J'ai une tablette Tab 7 sous Android 12 et ça fonctionne bien.
J'ai contacté le développeur tidal et ils n'ont trouvé aucun problème c'est bluesound le problème voilà la réponse de tidal.
Le bug est du à android 14 merci de faire des correctifs.
0 -
In a curious twist, Spotify Connect doesn't show anymore either, but can still find it on BluOS 😭
0 -
UPDATED OFFICIAL COMMENT
Thank you for your patience. Our Product Development Team is working very closely with TIDAL's Development Team in a joint effort to locate the root cause of this issue. What we have learnt is if you try to use TIDAL Connect using any device (iOS, a PAC an Android device running Android 13 or earlier), not Android 14 and then use an Android 14 device, TIDAL Connect works fine.
If your BluOS Player has recently power cycled and the first device you use to establish a TIDAL Connect link after a power cycle is an Android 14 device, TIDAL Connect will not work with any device and you must power cycle your player (Settings, Diagnostics, Reboot in the BluOS App) and set an initial connection with a non Android 14 device.
We are working to resolve this issue as quickly as possible - thank you for your patience and continue to monitor this thread for updates on this issue.
0 -
Grateful for Tony's updated information. Thanks so much. Can confirm that a reboot of my Node 2i, followed by Tidal Connect from my PC, did allow my Pixel 6a on Android 14 to connect. Hopefully it will continue to work until a solution is found. Fingers crossed.
1 -
Quick update. Fix lasted several hours for me before I lost Tidal Connect from my Pixel 6a again.
0 -
Mine also stopped working. I wonder Tony - perhaps the new Tidal API (which enables FLAC) is not affected by Android 14 switch.
0 -
Hi folks, let me give an update, this is specific to Android 14 and Tidal is aware of the issue and looking to fix. It seems that for some reason it is localized to BluOS, and they are actively working on it. I have the issue myself with a Pixel 6 and android 14. So it was easy for me to demonstrate to the folks in Oslo lol.
1 -
Thanks Andrew. Glad to hear that Tidal is aware and working on a fix. I was frustrated that they responded to my ticket by repeatedly referring to Bluesound.
0 -
Not entirely their fault, took us mutually a couple days to figure out where the issue was since it appears to localized on us.
0 -
Understood. Just glad that progress is being made.
0 -
Thank you Andrew for the update - this is really great news. :)
Now let's hope, that Tidal can get it fixed as soon as possible, so that we can fully enjoy our Bluesound products again. :D
0 -
Agreed. I remain grateful for the official updates on this thread.
0 -
Can you please share the technical reasons standing behind this issue? It could be very interesting for us, fellow developers to learn what went wrong here and how you managed to counter it. (I'm looking for a technical explanation and don't mind lowest-level details).
1 -
0
-
Node 2i working now, Node 130 still not working. BluOS version 4 was a significant change - I am surprised this Tidal Connect issue is the only one I have had to be honest. Perhaps this is the part where I touch wood.
0 -
Hi folks, here is an update. Tomorrow morning Toronto time we will begin to roll out 4.2.6 which includes the Tidal Connect update for High Res FLAC along with a dozen or so BluOS general updates. I want to be upfront about the recent Android 14 Tidal Connect issues as they will be still be there after you update your BluOS. The issue and I'm not going to get into it technically still resides with Tidal and they are deeply working on it. We hope to see Tidal update their systems with a hotfix at some point and we are speaking with their Oslo team daily as we work through it. In the meantime there is a workaround - [reboot the unit / use a different device (not Android 14) to make the first connection after reboot with Tidal Connect / use Tidal Connect with any device]. We will keep everyone updated as we move forward.
Workaround; https://support1.bluesound.com/hc/en-us/community/posts/18722793189783/comments/195870763570150 -
Appreciate the update and the forthrightness Andrew. Hopefully the fix is getting closer. At least for me, the workaround only holds for a few hours before I lose Tidal Connect again. Still, the new version of BluOS allows me to more easily navigate my Tidal content.
0 -
At least it is a known and repeatable issue now that can be resolved, and I'm proud of our team for digging in hard on helping to solve it. Good to know that it only lasts a while, thanks for sharing that.
0 -
Agree completely, and you're welcome. I do love Bluesound.
0 -
Hi Andrew - the FLAC update will be most welcome. Toronto time is so behind us here. About 7 hours. But this will be worth the wait.
0 -
Andrew -
If you're willing, please keep us updated on any news from Tidal. I have not had much luck getting information from them. And I'd love to try Tidal Connect with FLAC.
Thanks again.
0 -
Had the issue for quite some time with Google Pixel 7 and used the BluOS App instead. Just out of curiosity, I tried it today, after my phone had received another Android Update - and to my surprise it worked out of the box.
I am using TIDAL - Beta.1 -
Hey.. My pixel 6 is the same, working on all speakers now! I will have to follow up with Tidal to find out if they hot patched or if the android update fixed the issue.
0
Post is closed for comments.
Comments
149 comments