Defect Fix: Android Automotive Syncing
-
Sorry if this is a repeat. We just purchased a 2024 Blazer EV that has no Android Auto support, but uses Android Automotive as the OS for it’s infotainment system. I use Pocketcasts and pay for a subscription solely to support syncing across devices, PC desktop app, my android phone and now the Blazer.
On startup, the Android Automotive app resumes playing from whatever previous point was being played in the vehicle. After a brief period (a few seconds? Depends on network connection) I can tell a sync to the server has happened because I can see in progress episodes update, and if I manually choose one of those (and it’s a different episode than I was previously in the middle of in the vehicle) it will pick up playing at the appropriate, synced position. HOWEVER, without the manually steps by me, the vehicle will continue to play the incorrect episode from the incorrect location. Even worse, it will then queue this back as an in progress episode.
Acceptance Criteria/Expected behavior: Position sync to server should happen PRIOR to beginning playback on the Android Automotive app. Once sync has completed, resume playback in the correct episode (this includes “jumping” to the appropriate synced timestamp in the event the current in progress episode is the same as the episode from the previous drive, but the user has listened to a portion of the episode on another device)
If you’re concerned about user acceptance of this, you could make this an option in the settings, “delay playback on boot until server sync” or “maximum playback delay for server sync” with a numeric input in seconds.
-
Hi, @morrisonbenj! Since you have Plus, I’ll be reaching out to you through email. So, please keep an eye out for my message
- The topic ‘Defect Fix: Android Automotive Syncing’ is closed to new replies.
Pocket Casts Forum 