Weird Tidal software glitches

californiaboy935

Active Member
Verified Owner
Supporting Member
Joined
Apr 30, 2023
Messages
405
Reaction score
321
Cars
Lucid Grand Touring
Referral Code
WDATGN78
Been experiencing some weird bugs with Tidal being uncontrollable for 2-6 mins when you first jump in the car. The screen and the steering wheel controls for volume/play pause won’t work. I caught a bit of it this morning in the garage.

It seems to have happened more frequently since the update but I might just be noticing it more as I am currently trying to decide whether to keep the Tidal subscription (which I have only for Atmos) or get rid of it… anyways that’s another topic for another time.

See the attached video which is a view of the bug. My least favorite thing to hear when I was a lead “…I can’t replicate that…”
 
Been experiencing some weird bugs with Tidal being uncontrollable for 2-6 mins when you first jump in the car. The screen and the steering wheel controls for volume/play pause won’t work. I caught a bit of it this morning in the garage.

It seems to have happened more frequently since the update but I might just be noticing it more as I am currently trying to decide whether to keep the Tidal subscription (which I have only for Atmos) or get rid of it… anyways that’s another topic for another time.

See the attached video which is a view of the bug. My least favorite thing to hear when I was a lead “…I can’t replicate that…”

 
So Tidal app is really showing it's age.. i can consistently make it crash.. I need to reboot the car just to get it to play.. once playing, if I advance 1 track at a time more than 4 tracks, there is nothing you can do to have it start playing anything... it's just STOPPED dead. If I then go to FM or any other service, everything works as intended... but going back to Tidal after that.. . still dead. Sometimes it will start to play a song, but then immediately stop, and start playing the song from the start again before completely crashing again.

was telling this to one of our software engineers where I work, and she has a very logical take on this issue that I agree with.. That the app is not caching memory efficiently against the core needs of the operating system, and is stalling when the buffer is full so as not to impact the other functions of the OS.. so when it tries to play a track, it's only playing what was buffered in memory. the song will only play a few sec and stop, or just stop altogether as the app is in core dump. The only way to fix that, is to kill the app (that we can't do) or restart the OS.. that we can do, as I have to do every day I want to use Tidal. Essentially clearing the memory buffer(s) so it works again. Since the tidal bit rate is so high, that POSSIBLY the operating system for Lucid is not managing its file handling very well and not accounting for the larger packets to process correctly when its pulled down over the cell connection. This is (maybe) why I can consistently make Tidal crash by asking it to advance many tracks (that it thinks it needs to download), and when I do settle on a song to listen to... it can't pull things down to buffer since it's busy spinning on the tracks you didn't play. ...core dump. Dead app until restart. Every. Freakin. Time.

A software suggestion... allow the owners to restart applications instead of restarting the entire operating system. Like being able to open up a shell and kill the app and it's dependencies.
 
A software suggestion... allow the owners to restart applications instead of restarting the entire operating system. Like being able to open up a shell and kill the app and it's dependencies.

I don't think you're ever going to see that in a car infotainment system.
 
So Tidal app is really showing it's age.. i can consistently make it crash.. I need to reboot the car just to get it to play.. once playing, if I advance 1 track at a time more than 4 tracks, there is nothing you can do to have it start playing anything... it's just STOPPED dead. If I then go to FM or any other service, everything works as intended... but going back to Tidal after that.. . still dead. Sometimes it will start to play a song, but then immediately stop, and start playing the song from the start again before completely crashing again.

was telling this to one of our software engineers where I work, and she has a very logical take on this issue that I agree with.. That the app is not caching memory efficiently against the core needs of the operating system, and is stalling when the buffer is full so as not to impact the other functions of the OS.. so when it tries to play a track, it's only playing what was buffered in memory. the song will only play a few sec and stop, or just stop altogether as the app is in core dump. The only way to fix that, is to kill the app (that we can't do) or restart the OS.. that we can do, as I have to do every day I want to use Tidal. Essentially clearing the memory buffer(s) so it works again. Since the tidal bit rate is so high, that POSSIBLY the operating system for Lucid is not managing its file handling very well and not accounting for the larger packets to process correctly when its pulled down over the cell connection. This is (maybe) why I can consistently make Tidal crash by asking it to advance many tracks (that it thinks it needs to download), and when I do settle on a song to listen to... it can't pull things down to buffer since it's busy spinning on the tracks you didn't play. ...core dump. Dead app until restart. Every. Freakin. Time.

A software suggestion... allow the owners to restart applications instead of restarting the entire operating system. Like being able to open up a shell and kill the app and it's dependencies.
Im having a very similar experience. Is there a place where we can go to put in bug reports on it?
 
Back
Top