You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I purchased dsub from the app store specially because it has an "offline mode" and supports Android Auto.
My expectation is that I should be able to be without wifi and for the dsub app to work via the android auto UI. No connection to the navidrome/subsonic server should be needed for me to listen to my music. However, I've found that if my navidrome server is not available then the dsub application hangs and is non-functional within Android Auto under most (all?) circumstances. In my mind, this isn't REALLY offline fully and/or taking advantage of all the pre-caching I did when I was within range of my wifi.
Note, that offline mode playback does still work if I control the dsub app from my phone UI. So this bug is unique to android auto specifically... I don't think that is unique to my particular vehicle.
The text was updated successfully, but these errors were encountered:
Are you able to control DSub from car screen under any circumstances? I haven't been able to yet, but perhaps it's because I'm trying offline and my server is VPN only?
I purchased dsub from the app store specially because it has an "offline mode" and supports Android Auto.
My expectation is that I should be able to be without wifi and for the dsub app to work via the android auto UI. No connection to the navidrome/subsonic server should be needed for me to listen to my music. However, I've found that if my navidrome server is not available then the dsub application hangs and is non-functional within Android Auto under most (all?) circumstances. In my mind, this isn't REALLY offline fully and/or taking advantage of all the pre-caching I did when I was within range of my wifi.
Note, that offline mode playback does still work if I control the dsub app from my phone UI. So this bug is unique to android auto specifically... I don't think that is unique to my particular vehicle.
The text was updated successfully, but these errors were encountered: