[Bug] Android Auto can fail to surface last played media from cold/background state #45
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On September 10, 2026, while using BookWave through Android Auto, the last-played audiobook failed to load.
Android Auto appeared to request/load the last-played media, showed a brief loading/thinking state, and then gave up without surfacing or starting the remembered audiobook.
The problem has not yet been reproduced consistently.
Expected behavior
When BookWave has no active playback session, Android Auto should still be able to resolve the remembered/last-played audiobook and present or resume it.
Observed behavior
Android Auto briefly attempted to resolve the last-played item, then returned no usable media and playback did not start.
Relationship to #43
This was observed while investigating #43, but it should initially be treated as a separate failure.
#43 occurs after the correct audiobook has already been resolved: cold Play can install that book at 0:00 and needs resume-freshness validation before audio starts.
This Android Auto failure appears earlier in the flow: the remembered media either was not returned, could not be resolved, or failed while opening the playback session.
Do not combine the issues unless investigation demonstrates a common root cause.
Investigation scope
Inspect the Android Auto / MediaLibrary recent and remembered-media path, cold MediaLibraryService startup, profile-scoped remembered audiobook identity, authentication/profile availability during cold startup, media-item resolution, playback-session opening, cancellation/timeouts, and error handling.
Also check whether this overlaps current/planned remembered-audiobook persistence work rather than adding a second owner for that state.
Determine whether the failure occurs during:
remembered identity -> media item resolution -> playback-session open -> Media3 playback resumptionLogging should make those stages distinguishable without recording audiobook titles, server URLs, tokens, or other library data.
Reproduction context
Real Android Auto connection.
BookWave was not actively being used in the foreground.
Android Auto attempted to obtain the last-played media, displayed a loading state briefly, and then stopped.
Intermittent; not reproduced on demand yet.
Acceptance criteria
Cold/background Android Auto startup reliably exposes the remembered audiobook when one exists.
A failure to resolve/open it produces a diagnosable redaction-safe reason rather than silently returning nothing.
The implementation reuses the existing playback/session ownership boundaries and does not introduce Android-Auto-specific playback correctness policy.
Verify with DHU and, where practical, a real Android Auto connection.
Cross-check #43 to ensure cold Play still passes through the shared resume-freshness policy once an item has successfully been resolved.