Harden car-arrival headset continuity after route flap (#36) #64
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/issue-36-car-arrival-route-flap-v2"
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?
Summary
Follow-up for #36 after the second physical Android Auto drive exposed a transient Bluetooth route-list flap during car binding.
The measured failure was:
AUDIO_FOCUS_LOSS;What changed
heardRouteafter Android Auto begins mutating the route list.selectedId == targetbeforeplay().AUDIO_BECOMING_NOISY, and later controller bindings excluded.Regression coverage
Added/updated tests for:
heardRoutedisappearing without destroying the captured target;Verification
Exact branch head:
e50748732dba86dc4e3ae3996548a95e8a4f82b8Forgejo Actions run #153: success
Relevant checks passed:
:playback:compileDebugKotlin:playback:detektDebug:playback:detektDebugUnitTest:playback:ktlintMainSourceSetCheck:playback:ktlintTestSourceSetCheck:playback:testDebugUnitTest:playback:verifyDebugBUILD SUCCESSFULAcceptance
This fixes the code path exposed by the 18:15 physical trace, but #36 should remain open until another real Android Auto drive confirms:
Playback resumed after the car took audio focusis logged;Do not merge automatically; physical re-acceptance is still required.