Hide Android Auto Queue from the player #35
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?
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:
PR #61 implements that by withholding
Player.COMMAND_GET_TIMELINEfrom Media3's media-notification/platform-session proxy. Media3 then omits the framework queue that projected Android Auto reads.Acceptance criteria
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.
Implemented in PR #61 without changing Media3's queue/timeline. The playing item now publishes both
KEY_DESCRIPTION_LINK_MEDIA_IDandKEY_SUBTITLE_LINK_MEDIA_IDtotab/history, withHistoryas the visible optional subtitle/description while author + series remain in the artist/byline. Physical Android Auto acceptance is still required before closing.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_TIMELINEfrom 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.Product decision update (2026-09-19): the owner no longer wants History in the Android Auto player or browse library.
docs/product-decisions.mdPD-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.Player screen still shows the queue rather than Historyto Hide Android Auto Queue from the playerImplementation 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 withholdsCOMMAND_GET_TIMELINE. Physical acceptance is now only that the standard Queue affordance is absent.Canonical acceptance staging — 2026-09-24
Reviewed main / acceptance APK source:
88ae231ddc01897d83e24968bed5443ea861aeddMerged implementation: PR #67, accepted head
20dae444aa5f8b4a41bd673d90f76b043027dc97, merge commitfea83c6abc1354e8d831a012881cc20f0afa81c0.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 at88ae231d....Current implementation / automated evidence
Player.COMMAND_GET_TIMELINEwithheld.MediaButtonPublishingTestdirectly asserts “the platform session withholds timeline so Android Auto has no queue button”.onConnectapplies the queue suppression only whenisMediaNotificationControlleris true.Timelineconstruction for this feature.MediaItemshas no History metadata; its subtitle use is the normal series presentation.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:
bookwave-debug-0.10.6.1-2272bookwave-debug-0.10.6.1-2272.apkorg.homebord.bookwave.debug88ae231ddc01897d83e24968bed5443ea861aeddverifyDebug; the exact code already has the green evidence above.Minimum remaining projected-host test
bookwave-debug-0.10.6.1-2272.apk.Acceptance matrix for those host-dependent claims:
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