Tidal Connect on BluOS-devices not working with Android 14 anymore?
Beantwortet
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
-
I am happy to report that Tidal Connect is now working for me as well. I will report back if it stops working, but for the moment, hooray!
0 -
Yesterday it was working fine, but today it isn't anymore.
at least my "Pulse M" doesn't want to play with Tidal Connect - haven't tested the other players yet.Really looking forward to see this fixed - maybe Tidal even get's that fully fixed before Christmas... as a gift to its users. 😅
0 -
Ugh same here. Worked fine yesterday with my Node 2i, today it's a no go. As usual, Tidal on my Pixel 6a using Android 14 can see the Node 2i, but it cannot connect.
I'm with Tino. A Tidal fix would be a great Christmas gift.
0 -
Hi everyone, I got some days ago a new Nad amp, with Mdc module. Me too experienced the topic's problem.
Every single day, when trying to reconnect Tidal, I have to do some app termination and restart, Tidal and/or Bluos, I cannot found a given sequence, it depends from the day and seems not enough trying to make the first connection with a non A14 device.
With android 9 or iOS, all is everytime fine but I would like use mi personal cell that rely on android 14, so please persist with Tidal or anyone else involved...
Let me consent to write, I also have a WiiM mini streamer, toslink connected to same amp. Beside it never gave me a single problem, I would suggest taking this device as an example, for the functionality, connectivity and versatility it offers.
0 -
Every workaround doesn't work all the time. Something that works for me, for now at least. Long-press Tidal app. Click on info - should be left most icon on Android 14 - force stop the app. Next time I open the app - tidal connect works. Will this always work? nobody knows.
You might have to connect using alternate device first (like Windows) - after force stopping Tidal on your phone then use Android 14 device.
0 -
The workaround only works occasionally. I haven't discovered a pattern when it does/doesn't.
Forcing the app to stop doesn't provide a continuous solution either: it works again immediately afterwards, but when the app has been idle for some time it falters again (i.e. when one doesn't play music for a while, but the app is still 'loaded'/active).
(I have the latest versions of both BluOS and Tidal installed on my Pixel Pro 7.)
So, I hope Tidal/Bluesound come up with a real solution, this year would be nice ;-)0 -
So I'm waiting for Tidal to get back to me, but I did have an update for my pixel 6 phone on Friday and now Tidal connect has worked well all weekend. I'm on 4.2.6 the latest BluOS version as well (as you'd kind of expect) and wondering if you are still having an issue which version you are on?
0 -
Hi Andrew,
I'm using all the latest available versions for BluOS, Tidal and Android (I even joined the Pixel Beta Program in the hope, that it would fix the problem).0 -
I'm on 4.2.6 for BluOS and 2.96.0.1144.146 for Tidal Connect on my Pixel Pro 7 running Android 14 (November 1st, latest security update December 5th)
0 -
Same here. Latest BluOS, Tidal 2.96.0.1144.146, Pixel 6a on Android 15 with the December Security Update.
0 -
Yeah, I spoke with Tidal this am and they are still going through it and my phone stopped lol. From our side we see the issue and it is a frustrating timing based one. And the Oslo folks are working hard to fix it as several of them are also on Pixel phones.
0 -
Again, thanks for the update Andrew.
0 -
Tidal 2.96.0.1144.146, Bluos 4.2.6.
This early morning, I updated my galaxy S22 to its last Android 14 release but this didn't solve itself. As usual when I came back to home (when I left, it was connected), it failed to connect again and this time nothing seemed to work, in order to regain connection, until I found in the apps preference permissions, a voice "near devices" that was not enabled and I don't remind if was present before. It's missing at all on another Android 9 device.
As soon I enabled it, I was able to get the connection, even after gone outside and comeback to home (never happened before).
I'm hoping it's not just a single lucky shot...
I'll let you know and just to say, Tidal connection with WiiM, never ever failed...
0 -
As I feared, it was just a stroke of luck... This morning, Tidal Connect was able to connect to Bluos, even after several changes between different devices. Then I logged out of Tidal and closed the app for a couple of hours. When I tried again, it could no longer connect to Bluos while it was fine with WiiM. I managed to reconnect Tidal only after the usual, rather random sequence of various terminations and restarts of the apps (Tidal and Bluos). This time too, success came after opening and closing the setting in Android relating to Tidal and the detection of nearby devices... However, it is a very annoying thing which I hope will be resolved soon.
0 -
I'd like to share a different view on this problem.
As a customer who paid over 500 euros for a device which supports Tidal officially, I find this ridiculous and completely unacceptable. If a refund were available, I'd easily opt for it and wish I'd never meet this company, or that product.
That's my current view of this affair. Should you wish to improve on that towards your customers, open and upfront communication is the very first step to do so.
0 -
Should I worry about it? I contacted Tidal support also but they just responded it's not their problem...
This is the answer I got:
"Thank you for providing us with all the information we requested and for your continued patience as our developers attempted to diagnose this issue. After a thorough investigation, our development team is unable to reproduce this issue and we currently do not have a fix.
It appears that this issue may be related to your device and we suggest you contact Bluesound support for further assistance.
We apologize for the inconvenience and will be sure to contact you if there are any new developments regarding this issue from us"...0 -
@Luciano, I'll take up this comment with their support team. Clearly they didn't do any work to answer this and just closed the ticket.
0 -
Thank you Andrew, I'll keep resist with a couple of dismissed cell (when the new one refuse to work)...
0 -
Andrew, that is also the only response I have ever received from Tidal. Just FYI.
0 -
I must say - I did not expect this problem to last as long as it has lasted.
0 -
I have to agree.
0 -
Hoping this could help...
Even if I can't say to have surely found a definitive "sequence" of operation to regain connection to Bluos from tidal, it seems that if I go first in Android 14 apps preferences for just displaying Tidal own authorisations and force its termination and then force termination of Bluos app also (if in background), generally, after restarting Tidal I can get back connection between it and Bluos device (Nad 3050LE).
I must underline the annoyingness of this situation, if I add also that Dirac has a known and still unsolved problem with NAD amplifiers (from quite one year) and forces the use of a very old version, I can't tell I'm satisfied...
0 -
It's funny that this thread is marked as "answered" :D
Anyway, I've definitely had enough and it doesn't matter if it's Bluesound's or Tidal's fault - in the end it's just bloody annoying. After the holidays I'll get a cheap but working Wiim mini.
Cheers and happy holidays, dear fellow audioholics.0 -
I'm holding out for a fix, but I agree that it is frustrating how long it is taking for that fix. Happy Holidays.
0 -
Even after update it seems so Tidal Connect on Android 14 is not working.
0 -
I'm starting to lose hope and exploring other streaming platforms at this point.
0 -
You should not. Annoying as it maybe, the streamer is not unusable. Also, my experience is has been positive, it has worked flawlessly since I got it. Not fair to dump it with first hiccup.
0 -
If you have a Google Pixel phone which runs the latest Android and you are a Tidal user, then yes, it's downright unusable at the moment.
0 -
I meant Tidal Connect is a problem, but the BluOS app works as designed. I use the BluOS app at this point - it is not my preferred choice and doesn't have Tidal FLAC - but it works.
0 -
I agree. It's not a perfect solution, but I love my Node enough to keep using it for the time being. Really frustrating though.
0
Post ist für Kommentare geschlossen.
Kommentare
149 Kommentare