Hush

Waze Bridge Repair Survives Process Death — the repair target lived only in memory, and a repair spans a system uninstall that puts Hush in the background — where it can be killed. Reproduced on a real device: repair started, bridge removed, process recreated, and the repair was simply forgotten, leaving the bridge gone and nothing installing the bundled one. The target is now persisted (with a 15-minute staleness rule), so the second half runs whichever process performs it. (Hush) - Bridge Installs Are Patient Enough for the Prompts They Cause — a Bridge install on a real device is not one dialog: it is the installer, then Play Protect's "Scan app", then the vendor's own "Continue installation". Three prompts took longer than the ~33s the attempt allowed, so a working install was reported as a failure and only the retry rescued it. The wait is now ~46s per pass, counted from measurement rather than guesswork. (Hush) - A Verification Completed in Settings Now Wakes Playback — the Audio Sources screen hosted its own challenge and, unlike the overlay and the browser route, never reported success. A track parked waiting for that source was never resumed, the "SpotiFLAC needs verification" card stayed up over a source that was already fine, and the freshly earned session was never mirrored into the vault. All three surfaces now report through one entry point. (Hush) - A Release Gate for the Waze Bridge Lifecycle — a shell-driven smoke test that exercises detect → remove → install → verify → update in place → uninstall → repair → restore against a real device, with machine-readable verdicts and its own exit codes, so the lifecycle that breaks users on release day is checked before a release rather than after. (Hush)

Write a review