KeelrLeek
9f0601027c
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.
22 lines
1.4 KiB
Plaintext
22 lines
1.4 KiB
Plaintext
queue window arriving across the bridge, field for field (`queue-window`);
|
|
and both of the intent filters Android Auto knocks on — the legacy
|
|
`android.media.browse.MediaBrowserService` and media3's own
|
|
`androidx.media3.session.MediaLibraryService` — resolving to `MediaService`
|
|
(`auto-browse`, `auto-library`), which is also the guard for a media-session
|
|
plugin that compiled and never reached the APK: the service, its filters and
|
|
the Auto meta-data live in one library manifest and are lost together, which
|
|
this project has already been through once as a start-up
|
|
`ClassNotFoundException`. Printed but never failed, because their `dumpsys`
|
|
formats have never been read back from this phone: whether the service is
|
|
foreground, whether our audio focus is in the system's stack, and whether the
|
|
becoming-noisy receiver is registered (`media-plumbing`). Printed and never
|
|
failed for a different reason — `pm dump` prints no application meta-data at
|
|
all, so nothing on the phone can be asked about it — the
|
|
`com.google.android.gms.car.application` declaration as `tools/auto-prober/`
|
|
last resolved it (`auto-desc`).
|
|
|
|
**The browse tree is not proven here and cannot be.** With the app
|
|
force-stopped there is no WebView, so no DevTools socket, so `smoke.mjs` has
|
|
nothing to attach to; `tools/auto-prober/` is the instrument for that, and
|
|
"### The Auto prober" under Verifying is where it lives.
|