I am using the latest beta (ARC, Roon & Rock), but have trouble with ARC starting in Android Auto. I see the album, playlists etc. and when I start a playlist or album it doen’t play (time bar keeps bouncing).
When I first start ARC (without cable attached for AA) it works when I attach the cable. As soon as I start another album or playlist it doesn’t work anymore.
I have tried re-installing the app, rebooted the core etc. but nothing works.
Before 159 it was okay! What am I doing wrong?
Hi, @mtimmans, sorry for the delay here. Could you, please, specify some things while your were in the broken state if you remember them:
Did the issue affect both local and streaming service media?
Were you able to play any downloaded media?
Am I getting it right that this part When I first start ARC (without cable attached for AA) it works when I attach the cable. As soon as I start another album or playlist it doesn’t work anymore. happens during every usage and as soon as you disconnect-reconnect you are able to play a track but the app ends up in a broken state again?
Could you, please, specify you setup details: phone model, OS, Roon Core setup.
@Carl_Dickson, could you, please, provide answers to the same questions and also specify your device model and other setup details?
Yes, you are correct it did happen everytime when i connected again
my phone is Google Pixel 7 pro, with android 13; The roon core setup is a Rock installed os
I hope this answers your questions. Unfortunately I am now on the production version, so I cannot help you with further questions/information. In the latest production version everything is working as supposed to be!
Understood, thank you, @mtimmans. Could you, please try to reproduce this issue one more time and let me know the timestamp in your local time? We are going to take a look at the diagnostics report from your device while it is in this state.
I have the same problem with B159. Also both with albums local on the core and from Qobuz. On AA albums are displayed but selecting it to play results in the displaying the first song but then the progress bar keeps ‘spinning’. When I disconnect the cable, start the song on my phone and reattach the cable then I can start playback on AA.
If you want I can test this on Wednesday and give you a timestamp.
Edit:
Phone: OnePlus Nord with android 13 (LineageOS)
Core: Ubuntu 22.04
Hi, I am using Roon Core version 1237 along with the most recent beta Arc.
At 8:40 AM NZT, I played music on my phone and then connected it to Android Auto. The music played well and I could skip tracks. However, when I selected a different album from the home screen, the “Now Playing” screen appeared but the music didn’t change - it continued playing the original album.
Next, I tried choosing a track from my library, but the same issue occurred. The “Now Playing” screen displayed the existing track, and the only option available was the stop button - I couldn’t change tracks at all, even using the steering wheel controls.
Finally, I reinstalled the app from the Play Store, but the problem persisted. This occurred at 8:50 AM NZT.
Quick question for @Joost_Hoogland, @Carl_Dickson, @mtimmans, when you are getting in your car and connect your phone to your car’s media system, is Roon ARC running at that moment or the issue occurs in both scenarios:
Connecting when Roon ARC was not running before you connected your device
Connecting when Roon ARC was running before you connected your device
Reconnecting doesn’t change anything.
When disconnected I opened Arc on my phone. It showed the selected track below in Now playing with the spinning wheel. Stopping and trying to restart didn’t play the track. Edit: I meant on Arc on my phone.
I had to close Arc completely and then I can restart the album and the first track starts playing on my phone.
Stopped the playback on my phone, reconnected the cable. Then I can also play the track on AA.
Hope this helps to identify the problem. Let me know if you have additional questions.
Cheers, Joost
Edit: I am on B161. Android 13. Core B1237 on Ubuntu 22.04.
I have the same issue since B159, using Wireless AA, so I doubt this has something to do with whether one uses wireless or wired AA. It’s a bug introduced in B159.
