Keep phone skip controls when no car is bound #56
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/issue-38-phone-skip-layout"
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?
Closes #38
Ownership
Android System & Auto Agent — media-session/system-control surface only.
What changed
CarConnections.isConnected()state;OutputButtonsitself is unchanged;Safety
SLOT_BACKremains occupied in every tested car-bound/action-visibility combination, preventing raw Previous from becoming exposed to the single-window player.Automated proof
MediaButtonLayoutTest: both car states and output visibility matrix through Media3's real legacy slot conversion;MediaButtonSlotConversionTest: both binding states, skip relocation and SLOT_BACK invariant;MediaButtonPublishingTest: first bind/final unbind publication and no repeated-state republish storm.Acceptance still requiring hardware/DHU
No #6 behavior changes are included; that issue will be re-tested only after this PR is reviewed and merged.
Final implementation-owner status
06e221e299090f518fa8c960f3b3d26d1f5df789verifyDebug: BUILD SUCCESSFULAutomated coverage verifies car bound/unbound layout priority, output-action visibility combinations, Media3 slot conversion, the permanent
SLOT_BACKinvariant, and meaningful-state publication without repeated-state republish storms.Outstanding device/DHU acceptance:
Per lane sequencing, issue #6 has not been changed or re-tested as merged behavior yet. Stop here until #38 is reviewed and merged.
06e221e299tocec2f3c8b4