adb

Sequence: a previous crash leaves a crash database in /tmp, the next start shows a consent dialog nobody answers, adb never sees a device; deleting the database restores a normal boot

The Android emulator would not boot: a crash-consent dialog from the previous run was waiting for a click

jerome / 30 août 2026

adb devices stayed empty. The log said ‘Showing crashdialog to get consent’. Deleting /tmp/android-$USER/emu-crash-*.db fixed it.

Same moment of the same pour animation, captured twice: with the animator scale at 0 the receiving container is empty, with the scale at 1 the falling ribbon of sand is visible inside it.

Android

Jetpack Compose animations finish in one frame when the emulator’s animator scale is 0

jerome / 27 août 2026

Compose tweens respect the system animator scale. At 0 they complete instantly, so anything drawn mid-animation never renders.

Sequence of the working procedure: force-stop the app, pull the prefs XML with run-as cat, edit it locally, push it back through stdin with run-as sh -c, relaunch.

Android

Seeding SharedPreferences on an Android emulator with adb run-as (and the three ways it fails)

jerome / 23 août 2026

To screenshot a game-over screen that needs three finished rounds and a two-day streak, write the prefs XML through adb run-as — via stdin, after force-stop.