Hide Android Auto Queue from the player #35

Open
opened 2026-09-18 08:47:32 +02:00 by alexander · 5 comments
Owner

Current decision — 2026-09-20

The owner no longer wants History on the Android Auto player and no longer requires History as a car browse destination.

This issue now has one requirement:

Do not show Android Auto's standard Queue affordance for BookWave.

PR #61 implements that by withholding Player.COMMAND_GET_TIMELINE from Media3's media-notification/platform-session proxy. Media3 then omits the framework queue that projected Android Auto reads.

Acceptance criteria

  • The standard Queue button is absent on the owner's projected Android Auto head unit.
  • BookWave's real one-book ExoPlayer timeline is unchanged.
  • The in-app Media3 controller retains its timeline access.
  • No synthetic History queue/timeline is introduced.
  • No player-side History description/subtitle link is published.
  • Existing playback, progress, route ownership and media-button behavior remain unchanged.

Scope boundary

The Android Auto browse redesign is separate issue #65. Its intended root is Continue → Series → Authors → Profiles, with artwork and profile switching. Do not implement that browse redesign in #35 / PR #61.

The earlier investigation established why the standard Queue could not safely be redirected to History: Media3 derives the legacy queue from the Player timeline, and a queue-row activation is a playback/seek operation. The 2026-09-19 physical test also showed that the attempted description/subtitle History metadata links were not rendered by this projected host.

Those findings remain useful historical/platform evidence, but History replacement is no longer an acceptance criterion.

## Current decision — 2026-09-20 The owner no longer wants History on the Android Auto player and no longer requires History as a car browse destination. This issue now has one requirement: > **Do not show Android Auto's standard Queue affordance for BookWave.** PR #61 implements that by withholding `Player.COMMAND_GET_TIMELINE` from Media3's media-notification/platform-session proxy. Media3 then omits the framework queue that projected Android Auto reads. ## Acceptance criteria - [ ] The standard Queue button is absent on the owner's projected Android Auto head unit. - [ ] BookWave's real one-book ExoPlayer timeline is unchanged. - [ ] The in-app Media3 controller retains its timeline access. - [ ] No synthetic History queue/timeline is introduced. - [ ] No player-side History description/subtitle link is published. - [ ] Existing playback, progress, route ownership and media-button behavior remain unchanged. ## Scope boundary The Android Auto browse redesign is separate issue #65. Its intended root is **Continue → Series → Authors → Profiles**, with artwork and profile switching. Do not implement that browse redesign in #35 / PR #61. The earlier investigation established why the standard Queue could not safely be redirected to History: Media3 derives the legacy queue from the Player timeline, and a queue-row activation is a playback/seek operation. The 2026-09-19 physical test also showed that the attempted description/subtitle History metadata links were not rendered by this projected host. Those findings remain useful historical/platform evidence, but History replacement is no longer an acceptance criterion.
Author
Owner

Implemented in PR #61 without changing Media3's queue/timeline. The playing item now publishes both KEY_DESCRIPTION_LINK_MEDIA_ID and KEY_SUBTITLE_LINK_MEDIA_ID to tab/history, with History as the visible optional subtitle/description while author + series remain in the artist/byline. Physical Android Auto acceptance is still required before closing.

Implemented in PR #61 without changing Media3's queue/timeline. The playing item now publishes both `KEY_DESCRIPTION_LINK_MEDIA_ID` and `KEY_SUBTITLE_LINK_MEDIA_ID` to `tab/history`, with `History` as the visible optional subtitle/description while author + series remain in the artist/byline. Physical Android Auto acceptance is still required before closing.
Author
Owner

Physical re-test on PR #61 (2026-09-19) confirmed this projected Android Auto host renders neither History metadata link and still shows the standard queue button. The exact substitution 'queue button opens History' is not supported by the standard Media3/Android Auto player surface. The branch now withholds Player.COMMAND_GET_TIMELINE from Media3's media-notification/platform-session proxy, which Media3 explicitly uses to omit the framework queue and therefore the Android Auto queue button. History links remain for hosts that support them; same-head-unit re-test required.

Physical re-test on PR #61 (2026-09-19) confirmed this projected Android Auto host renders neither History metadata link and still shows the standard queue button. The exact substitution 'queue button opens History' is not supported by the standard Media3/Android Auto player surface. The branch now withholds `Player.COMMAND_GET_TIMELINE` from Media3's media-notification/platform-session proxy, which Media3 explicitly uses to omit the framework queue and therefore the Android Auto queue button. History links remain for hosts that support them; same-head-unit re-test required.
Author
Owner

Product decision update (2026-09-19): the owner no longer wants History in the Android Auto player or browse library. docs/product-decisions.md PD-001 (PR #66) makes History a non-goal for the car browse surface and explicitly rejects a synthetic History queue/timeline. #35 therefore only needs to leave the unwanted standard Queue absent; the new browse redesign is tracked separately in #65.

Product decision update (2026-09-19): the owner no longer wants History in the Android Auto player or browse library. `docs/product-decisions.md` PD-001 (PR #66) makes History a non-goal for the car browse surface and explicitly rejects a synthetic History queue/timeline. #35 therefore only needs to leave the unwanted standard Queue absent; the new browse redesign is tracked separately in #65.
alexander changed title from Player screen still shows the queue rather than History to Hide Android Auto Queue from the player 2026-09-20 09:55:39 +02:00
Author
Owner

Implementation moved from stale PR #61 to replacement PR #67, recreated from current main. #35 remains queue-suppression only: no player-side History metadata and no synthetic timeline; the media-notification/platform-session proxy withholds COMMAND_GET_TIMELINE. Physical acceptance is now only that the standard Queue affordance is absent.

Implementation moved from stale PR #61 to replacement PR #67, recreated from current `main`. #35 remains queue-suppression only: no player-side History metadata and no synthetic timeline; the media-notification/platform-session proxy withholds `COMMAND_GET_TIMELINE`. Physical acceptance is now only that the standard Queue affordance is absent.
Author
Owner

Canonical acceptance staging — 2026-09-24

Reviewed main / acceptance APK source: 88ae231ddc01897d83e24968bed5443ea861aedd
Merged implementation: PR #67, accepted head 20dae444aa5f8b4a41bd673d90f76b043027dc97, merge commit fea83c6abc1354e8d831a012881cc20f0afa81c0.
Exact-head CI: Forgejo run #164 — success.
Current-main regression evidence: later shared-service PR #89 exact head passed run #270 with verifyDebug, 2606 tests / 0 failures, ktlint, detekt, Android Lint and Room schema checks; current-main push run #271 passed at 88ae231d....

Current implementation / automated evidence

  • PROVEN — automated: the media-notification/platform-session proxy alone has Player.COMMAND_GET_TIMELINE withheld. MediaButtonPublishingTest directly asserts “the platform session withholds timeline so Android Auto has no queue button”.
  • PROVEN — automated: ordinary/in-app Media3 controllers do not have that command removed; onConnect applies the queue suppression only when isMediaNotificationController is true.
  • PROVEN — repository/product decision: BookWave's actual one-book ExoPlayer timeline is not replaced or synthesized. The implementation changes controller capability, not the player timeline.
  • PROVEN — repository/product decision: no synthetic History timeline/queue exists. Current playback source contains no custom Timeline construction for this feature.
  • PROVEN — repository/product decision: the abandoned player-side History description/subtitle workaround is gone. Current MediaItems has no History metadata; its subtitle use is the normal series presentation.
  • PROVEN — automated: publication still goes through the normal session + notification-controller path and the later full-suite regression gate is green.
  • NO LONGER APPLICABLE: replacing Queue with History. The current product decision is deliberately narrower: the standard Queue affordance must be absent; no History replacement is required.

Physical evidence already on record

The 2026-09-19 device result was against the earlier History-metadata attempt: the host still showed Queue and did not render the History link. That evidence motivated PR #67, but it is not a physical pass for PR #67's queue-suppression mechanism.

No later issue comment proves the post-PR-#67 projected-host Queue is absent.

Acceptance APK

Forgejo Build APK run #272 produced the signed debug artifact:

  • artifact: bookwave-debug-0.10.6.1-2272
  • APK: bookwave-debug-0.10.6.1-2272.apk
  • package: org.homebord.bookwave.debug
  • exact source: 88ae231ddc01897d83e24968bed5443ea861aedd
  • signer: verified against the configured BookWave keystore
  • this artifact workflow intentionally did not rerun verifyDebug; the exact code already has the green evidence above.

Minimum remaining projected-host test

  1. Install bookwave-debug-0.10.6.1-2272.apk.
  2. Start ordinary audiobook playback.
  3. Connect projected Android Auto.
  4. Open the standard Now Playing/player surface.
  5. Verify the standard Queue button/affordance is absent.
  6. Verify ordinary transport/player controls still work.

Acceptance matrix for those host-dependent claims:

  • STILL REQUIRES PHYSICAL TEST: Android Auto actually omits the standard Queue affordance.
  • STILL REQUIRES PHYSICAL TEST: ordinary controls remain usable on the projected host after queue suppression.

If #36 interrupts playback during this check, record it as an external #36 observation; do not misclassify Queue suppression itself.

Result

READY FOR PHYSICAL ACCEPTANCE

## Canonical acceptance staging — 2026-09-24 **Reviewed main / acceptance APK source:** `88ae231ddc01897d83e24968bed5443ea861aedd` **Merged implementation:** PR #67, accepted head `20dae444aa5f8b4a41bd673d90f76b043027dc97`, merge commit `fea83c6abc1354e8d831a012881cc20f0afa81c0`. **Exact-head CI:** Forgejo run #164 — success. **Current-main regression evidence:** later shared-service PR #89 exact head passed run #270 with `verifyDebug`, **2606 tests / 0 failures**, ktlint, detekt, Android Lint and Room schema checks; current-main push run #271 passed at `88ae231d...`. ### Current implementation / automated evidence - **PROVEN — automated:** the media-notification/platform-session proxy alone has `Player.COMMAND_GET_TIMELINE` withheld. `MediaButtonPublishingTest` directly asserts “the platform session withholds timeline so Android Auto has no queue button”. - **PROVEN — automated:** ordinary/in-app Media3 controllers do **not** have that command removed; `onConnect` applies the queue suppression only when `isMediaNotificationController` is true. - **PROVEN — repository/product decision:** BookWave's actual one-book ExoPlayer timeline is not replaced or synthesized. The implementation changes controller capability, not the player timeline. - **PROVEN — repository/product decision:** no synthetic History timeline/queue exists. Current playback source contains no custom `Timeline` construction for this feature. - **PROVEN — repository/product decision:** the abandoned player-side History description/subtitle workaround is gone. Current `MediaItems` has no History metadata; its subtitle use is the normal series presentation. - **PROVEN — automated:** publication still goes through the normal session + notification-controller path and the later full-suite regression gate is green. - **NO LONGER APPLICABLE:** replacing Queue with History. The current product decision is deliberately narrower: the standard Queue affordance must be absent; no History replacement is required. ### Physical evidence already on record The 2026-09-19 device result was against the earlier History-metadata attempt: the host still showed Queue and did not render the History link. That evidence motivated PR #67, but it is **not** a physical pass for PR #67's queue-suppression mechanism. No later issue comment proves the post-PR-#67 projected-host Queue is absent. ### Acceptance APK Forgejo **Build APK run #272** produced the signed debug artifact: - artifact: `bookwave-debug-0.10.6.1-2272` - APK: `bookwave-debug-0.10.6.1-2272.apk` - package: `org.homebord.bookwave.debug` - exact source: `88ae231ddc01897d83e24968bed5443ea861aedd` - signer: verified against the configured BookWave keystore - this artifact workflow intentionally did **not** rerun `verifyDebug`; the exact code already has the green evidence above. ### Minimum remaining projected-host test 1. Install `bookwave-debug-0.10.6.1-2272.apk`. 2. Start ordinary audiobook playback. 3. Connect projected Android Auto. 4. Open the standard Now Playing/player surface. 5. Verify the standard **Queue** button/affordance is absent. 6. Verify ordinary transport/player controls still work. Acceptance matrix for those host-dependent claims: - **STILL REQUIRES PHYSICAL TEST:** Android Auto actually omits the standard Queue affordance. - **STILL REQUIRES PHYSICAL TEST:** ordinary controls remain usable on the projected host after queue suppression. If #36 interrupts playback during this check, record it as an external #36 observation; do not misclassify Queue suppression itself. ## Result **READY FOR PHYSICAL ACCEPTANCE**
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alexander/Audiobookshelf-Manager-Claude#35
No description provided.