android: the handoff — the pending rounds, the pipeline, and what is unverified
Everything written this session that has not been through the device: rounds 43 to 48 (each patch adversarially verified, 43's transient-notice expectation fixed), a partial round 49, the pipeline scripts, the Android Auto design and the icon comparison mock. Also the two harness changes that were never A/B'd — adaptive waits, which may only shorten a declared wait and never lengthen it, and a ship that runs the mock walk and the deploy at the same time. The A/B and its 255-step baseline are in handoff/tools; main stays at what the phone has actually walked.
This commit is contained in:
1 parent
867fd42972
commit
9f0601027c
400 files changed
+26401
-3
No files matched your search
@@ -0,0 +1,19 @@
|
||||
Then, after the step loop, twelve things the mock cannot do at all: a
|
||||
force-stop and the paused restore that follows it (waited out past
|
||||
twenty-five seconds, which is well past the ten-second FGS-kill window), the
|
||||
position restored, playback resumed, the system media session and its
|
||||
ownership, media keys, exactly one card in the shade and exactly one session
|
||||
in the system's list — the two checks that prove the media3 migration landed
|
||||
rather than doubled — the two intent filters Android Auto knocks on, the
|
||||
legacy browse one and media3's own, both resolving to `MediaService`
|
||||
(`auto-browse`, `auto-library`: the catcher for a plugin module that
|
||||
compiled and never reached the APK, which is how this project once got a
|
||||
start-up `ClassNotFoundException`), ten seconds in the background with the
|
||||
position still advancing, SoulStream's own mixer underruns, and the queue
|
||||
window that rides along with every card update and that the lock-screen card
|
||||
is now built out of. Two more lines print and never fail: whether the service
|
||||
is foreground, whether our audio focus is in the system's stack and whether
|
||||
the becoming-noisy receiver is registered; and the Auto declaration as
|
||||
`tools/auto-prober/` last read it, because `pm dump` prints no application
|
||||
meta-data and nothing else on the phone can be asked. What none of it touches
|
||||
is in "What the walk proves about the card, and what it does not", above.
|
||||
Reference in new issue
Block a user