Fully back to normal for me too now. Must have been something on the Tidal end.
Mine has stopped working since today. I’m now on Android Tidal app v2.65.1. A look in the volumio logs for vtcs shows this error:
Aug 22 12:26:07 volumio vtcs[1397]: [2022-08-22 12:26:07] [error] handle_transport_init received error: TLS handshake failed
Aug 22 12:26:07 volumio vtcs[1397]: [2022-08-22 12:26:07] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
1 Like
We are currently investigating this issue, allthough it seems to be on Tidal side.
As a workaround, please uninstall / reinstall the Tidal app or clear the app cache and data. Let us know if it works for you.
1 Like
Clearing cache and uninstalling etc doesn’t work for me. This issue started already from v2.65.0 when I was experimenting with those leaked binaries on the web and now it’s stopped working with v2.65.1 with Volumio.
It works from my Windows machine so the problem for me at least is only with the latest Android version of Tidal. - edit - My Windows machine now connects and does its thing but it loses focus and disconnects leaving Volumio playing and switching to my PC speaker output at the same time. So not really functional.
I am also having the same issue. I uninstalled Tidal app on my android phone and my iPad but it didn’t help.
Tried restarting Volumio, shutting Volumio down and factory reset but nothing helped.
The only thing which ‘fixed’ it for me was to re-flash the SD card for my Rpi4, HOWEVER after playing a track for a few minutes the problem has come back - arggh!
Interestingly, while trying to find a workaround last night I observed a number of weird things going on:
- after giving up on Volumio for the evening I decided to play a track from Tidal using the Tidal app on my Google Chromecast Google TV. It played for a few minutes then stopped, saying that Tidal was already playing on Volumio. Upon starting playing using Google TV, the same thing happened again after a few minutes.
- I tried playing a Tidal track from the volumio.local gui but it would not play. I saw two errors pop up on two different occasions:
“Failed to open “alsa” (alsa): Failed to open ALSA device “volumio”: Device or resource busy”
“Failed to enable output “default detected output” (jack): Failed to connect to JACK server, status=17”
I hope that the devs find a solution to this soon as my trial period for Premium has just ended and I opted originally for the 12months purchase, so I can’t just decide to pay month by month
I have exactly the same issue as @charliesjc
Tidal connect was working fine about a week ago, now I get the TLS handshake error.
I didn’t change anything.
It would appear that Tidal, in an effort to hinder a handful of people who can actually make use of their leaked binaries, have succeeded in locking out their much larger legal user base.
Tidal latest Android v2.66.0 has NOT fixed this problem.
Same issue here. Tidal works fine from Windows or from Volumio itself but doesn’t work from Android.
Volumio version 3.324 (fresh installed)
Tidal 2.65.1
Solved cleaning cache, data and reinstalling Tidal from scracth. Now is working again from Android.
Same issue: TLS Handshake Fails - Latest version of Tidal on Android.
Device: Raspberry Pi 4
Volumio Version: 3.324
DAC: Schiit Bifrost 2/64
Logs: http://logs.volumio.org/volumio/a6S6u2k.html
Aug 27 17:15:56 asgard vtcs[1147]: [2022-08-27 17:15:56] [error] handle_transport_init received error: TLS handshake failed
Aug 27 17:15:56 asgard vtcs[1147]: [2022-08-27 17:15:56] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
Error Before clearing the Android Apps Data & Cache (clearing cache alone won’t fix it)
Error goes away and plays fine after.
BigManz are you saying that clearing cache AND data fixes the problem for you? I.e. basically start with a fresh instance of Tidal?
1 Like
It seems that, finally, clearing cache and data works to restore tidal connect functionality for me on v2.66.0.
It suddenly started working for me a couple of days ago and has been fine since. Before that I had cleared the android apps Cache but it didn’t help. I didn’t realize at that time I had to clear the Apps Data too.
Anyway, I just checked and my android app is at 2.65.1 so I’m wondering if I should update it or leave it alone (‘if it ain’t broke, don’t fix it’). I guess I’m going to have to bite the bullet and update it at some point so hopefully it doesn’t become broken again.
@mervinio
Like @charliesjc and @bbear1, on my Android phone after deleting the Tidal cache and data, uninstalling and reinstalling the Tidal app it’s now working.
I now have Tidal 2.65.1 on my phone (no idea what I had before)
I think it’s weird that there is a TLS error on Volumio, and uninstalling reinstalling the app on Android makes it work again. Does Volumio talk directly to the app on my phone? Or vice versa? Or is the TLS error unrelated?
Anyway I’m just happy that it’s working again, and I don’t have to debug a TLS issue in my spare time - it’s bad enough having to do this at work every second day. 
A few days ago, cleaning the memory and data in the Tidal application helped. Tidal connect started working properly. Today the problem reappeared, this time I reinstalled the Tidal app and it helped. I wonder for how long?
Seems as if this might not be Tidal related as I read on these forums of TLS handshake errors happening with Volumio and Spotify Connect. Hopefully Tidal Connect continues to work on my Volumio Rpi4 setup
Edit: Spoke to soon, Tidal Connect is broken again for me. I got a couple of days listening this time, so frustrating!
2 Likes
After struggling forever to keep Tidal Connect stable, the tip to clear the app cache & data seems to have worked. At least in the sense that for a couple of days the app refused any attempt to connect, despite rebooting Pi, etc., and being used to the randomness I switched to the internal Tidal (which is clunky and I miss the Daily Discovery). After reading the this thread and clearing the app cache & data, I could connect immediately and play flawlessly. If it happens again I’ll try just clearing the cache.
WiFi hygiene: Earlier I separated my 5GHz and 2.4GHz network SSIDs so the Pi only connects over 5Ghz; otherwise the Pi seems to prefer 2.4Ghz which is unstable for me. I would not assume wired is better unless proven in your particular case; it’s very particular to the individual environment and wired is just a simple answer to reduce a number of variables. WiFi is peachy keen set-it-and-forget-it for many, many other things.
While the app-data-clearing doesn’t prove the root cause, it does seem to indicate not a network (WiFi) problem (assuming an otherwise working setup), not a reboot-Pi problem, not a restart Android problem, not a re-install anything problem (tried all those many, many times). Time will tell.
1 Like
Just updated Tidal app on my Android phone to 2.66.0 (the latest version took a while to appear on the Canadian Play store!)
Cleared cache and memory, so wait to see if the problem returns
DefintelyNotThor, thanks for the tip on separating the 2.4g and 5g SSIDs. I have a slew of wireless networks in my home from two separate wireless routers, a selection of 2.4g, 5g and 5g AC. At the moment my Pi4 is connected to the 5g AC and has a strong and stable signal. I will keep an eye on it though
We have contacted Tidal and the issue is in the Tidal app. They have fixed the issue and the fix will be released September the 21st.
In the mean time, as a workaround, please reset the app’s cache when you encounter this issue.
1 Like
Sad that it will take so much time.
Also the work around does not work for me. I have reset the cache a few times but it still fails to connect.
It worked for a day or two when I previously reset the cache but then it stopped again.