Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion device/husky/ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ A proposal, not a verdict; Brett and Derek know the hardware better.
- Which microphone id is which hole, and what do the earpiece and headset paths need (#450, #453)?
- Why does the phone draw about 0.5 A idle with the screen off, and why did the CPU idle-state and power-domain overlays reboot-loop it? Not known; no measurement plan yet.
- In which file shape should the zuma System MMU v9 code and the AoC core port go (asked on #1)?
- Marking slot B successful (a `devinfo` write): decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252) (2026-11-07). It is a manual, attended step, once per install of a smoke-tested image, never from a unit, with per-phone layout evidence first. The boot LUNs get the whole-disk node removed and each partition's own flag set first (its own PR, booted on the maintainer's Pixel 7 Pro), then the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)). Until both are in nothing marks slot B on the 8 Pro: flash a known-good set before the boot that would use B's last try, and count every deliberate reset as a boot. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252.
- Marking slot B successful (a `devinfo` write): decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252) (2026-11-07). It is a manual, attended step, once per install of a smoke-tested image, never from a unit, with per-phone layout evidence first. The boot LUNs get the whole-disk node removed and each partition's own flag set first (its own PR, booted on the maintainer's Pixel 7 Pro), then the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)). Until both are in nothing marks slot B on the 8 Pro: flash a known-good set before the boot that would use B's last try, and count every deliberate reset as a boot. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252. On Lef's phone slot B stayed marked (`devinfo` byte 0x35 read `06`) from the unit's last write until the first flash after the unit was masked on 2026-11-07, when it read `04`. Since then, about a dozen flashes on 2026-11-07 (each followed by `fastboot set_active b`; a `flash`, which also sets B active, clears the bit) have read `slot-retry-count:b` as 3 after `set_active` and 2 after one boot, so a boot spends one of B's tries and the flash-before-the-last-try routine above applies. `slot-successful:b` was not read after those flashes, so "cleared" rests on the retry count and byte 0x35, not on the bootloader's own answer. The bit is not cleared by hand: that would be a `devinfo` write too.
- Does touch survive a long idle with the screen off? One 12 h idle on 2026-11-04 left only Power working; not reproduced, not cause-checked.

## Credits and sources
Expand Down
Loading