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
14 changes: 13 additions & 1 deletion device/husky/AOC-PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,18 @@ From Google's GPL tree (`android-gs-shusky-6.1-android16`; `kernel/devices/googl
| Z7c | ALSA card, amplifiers linked into it, protection firmware | 2026-11-05, `g757721ba1a81` | the card `google,aoc-snd-card` with 30 PCM devices and the amplifiers' controls; protection firmware loads on both |
| Z7d | first sound | 2026-11-05, `g74d6ba329f68` | the speaker route is the deep-buffer entry point (`TDM_0_RX Mixer EP6`); EP1 (UltraLL) hangs the AoC (see 5) |
| Z7e | PipeWire / browser sound, boot unit | 2026-11-05, `g69c83385020e`, `gd0d87517121a` | works (see 6) |
| Z8 | the packaged start: `omamobile-husky-aoc.service` and its script from derekross/omarchy-mobile#453 (local builds of omamobile-device-husky 0.1.9 and omamobile-audio 0.5.18 from `aafe089` and `80e5905`; the versions that merged are Derek's), no hand steps | 2026-11-09, `ga291900124c4` | see "The packaged start" below |

### The packaged start (2026-11-09, one phone, kernel `ga291900124c4`)

With the packages from #453 installed and my hand-installed start, UCM and WirePlumber files moved away: a first boot (which I recovered by hand), then a clean cold boot; the A/B check below used two more cold boots.

- **First boot: "no firmware node in /sys/bus/platform/devices/154b0000.aoc"** [V]. The unit stopped before touching the firmware file, as it should. My test kernel carries `gs201_aoc_boot`, which matches `google,zuma-aoc`, so it autoloaded and bound the AoC node before `aoc_core`; my old local blacklist had hidden that. `80e5905` adds `blacklist gs201_aoc_boot` to the package. Derek's note on #453: the published kernel's `gs201_aoc_boot` only matches `google,gs201-aoc`, so the line does nothing there (the 7 Pro's and Pixel 6 Pro's packages have it too); it matters only on a test kernel like mine.
- **Trusty is under `soc@0` on the 8 Pro** [V]: `/proc/device-tree/soc@0/trusty/status` reads `okay`, and the start script looked for `/proc/device-tree/trusty/status` only. `aafe089` checks both, with tests for the root layout, the `soc@0` layout and no node (it still fails closed with no node).
- **Second boot, cold, no hand steps** [V]: the card came up within a second or two of the unit starting, `Services : 94`, `EP6 playback` and `EP1 capture`, no failed units, no CS35L41 mailbox errors, uptime 203 s. `tools/phone-smoke` on that boot (at 898 s of uptime): every required check ok, 0 WARN and 0 errors in dmesg, hottest zone 54 C.
- **A/B tone check** [V]: the packaged start and my old hand-run start, each on a cold boot, amplifiers at digital 737 and analog 8 (top) and 10 (bottom), `pw-play` at 1.0, speaker 0.75, a file with 440 Hz left then 880 Hz right peaking at -22 and -12 dBFS. Both tones were heard clean on both paths, and the mic (EP1 mono, 48 kHz) read the 880 Hz tone at -51.6 and -43.1 dBFS (hand-run) against -52.9 and -43.1 (packaged), within about a dB. The first test file (`lr-test.wav`) peaked at -32 dBFS and was near the hearing threshold, so the quiet speaker I reported on #453 was that file, not a fault. Nothing above -12 dBFS was played, and the ceilings (737 / 8 and 10) were not exceeded.
- **Unexplained** [U]: seven `cs35l41 spi1.1: Failed to set mailbox cmd 1` lines (with `Bottom DSP1 event failed: -42`) at about 271 s of uptime on the first boot, which I had recovered by hand (`modprobe -r gs201_aoc_boot`, binding the node to `aoc_core`, starting the unit). None of the four earlier boots and none of the cold boots had them. Cause unknown. Derek's advice on #453: after a failed start a reboot is the safer way back than unloading and rebinding by hand.
- **Not covered** [U]: the packaged `HiFi.conf` drives both amplifiers in stereo for the Speaker device, where my old one used the bottom one only. Which `HiFi.conf` the hand-run side of the A/B check used was not recorded, and the difference was not measured further.

Public commit ids of the kernels whose ids differ on the branch: `gbb5ba9ba53d2` is `3239ac2628e4`, `g757721ba1a81` is `d59a29c08111`, `g3f5ba5e70070` is `9bd5c74b96da`, `g74d6ba329f68` is `cc4f0ec38718`, `gd0d87517121a` is `08c3095dc5aa`, `g1f109674c767` is `7fa4d8b91e8b`. Kernels up to `g4b0fc77182d8` have the same id on the branch.

Expand Down Expand Up @@ -59,7 +71,7 @@ The 7 Pro's stages (`omamobile-audio`): `media` is digital at most 737 and analo
## 8. Next

1. This document and the public branch (done with this change).
Now in review: kernel pull requests derekross/linux-omarchy-mobile#203 and #204, and package pull request derekross/omarchy-mobile#453 (the AoC start with a hang marker and the UCM2 profile).
Now in review: kernel pull requests derekross/linux-omarchy-mobile#203 and #204. Merged 2026-11-09: package pull request derekross/omarchy-mobile#453 (the AoC start with a hang marker and the UCM2 profile; results in "The packaged start" above).
2. The spi-s3c64xx change as a pull request against `omamobile`, with cheetah's object file before and after, the 9a's SPI nodes, and the check that a write to one amplifier does not reach the other.
3. The zuma System MMU v9 file beside `gs201-aoc-sysmmu.c`, with its own compatible and table.
4. The driver changes of section 6 behind zuma's match data, with the 7 Pro's objects shown unchanged.
Expand Down
2 changes: 1 addition & 1 deletion device/husky/BATTERY-NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -212,7 +212,7 @@ Test, verified from its journal: unplug at 11:37:08 (`usbsw=0x00 vbus=0`), replu

## 9. Slot B retries, and the cure that cheetah already has

Omarchy never marks slot B's boot successful, so every boot of slot B uses one of its three bootloader retries. At zero the bootloader falls back to slot A (GrapheneOS), and its first boot reformatted `userdata`: the Omarchy install was gone. It happened after a set of drills and reboots in one session. Observed with `fastboot getvar` after the fallback: current slot a; slot A successful, retry 1; slot B not successful, retry 0, not unbootable. `fastboot set_active b` sets the counter back to 3. Reading the count in the bootloader changes nothing; whether `reboot-to bootloader` itself uses a retry is not established (two of my readings disagree).
Omarchy never marks slot B's boot successful, so every boot of slot B uses one of its three bootloader retries. At zero the bootloader falls back to slot A (GrapheneOS), and its first boot reformatted `userdata`: the Omarchy install was gone. It happened after a set of drills and reboots in one session. Observed with `fastboot getvar` after the fallback: current slot a; slot A successful, retry 1; slot B not successful, retry 0, not unbootable. `fastboot set_active b` sets the counter back to 3: on 2026-11-09 it did so 9 times on my phone (the Kioxia UFS 4.0 one) without any flash. greenbrettmichael's refills end with `bin/omamobile flash`'s `--set-active=b` and read 3 as well ([#252](https://github.com/derekross/omarchy-mobile/issues/252)). Reading the count in the bootloader changes nothing, and on those 9 runs entering fastboot with `reboot-to bootloader` did not cost a try either (the count read what my own boot count predicted each time; the two readings that disagreed earlier are not explained). Wipe on fallback: seen with GrapheneOS on slot A (my phone), not yet known with stock Android on slot A. greenbrettmichael's slot A is stock Android 17, and his slot B has not fallen back since Omarchy went onto `userdata`.

Recovery was a fresh read-only backup in the initramfs, then `tools/install-phone` (it asks for answers, so it has to run in a real terminal), then the keyring repair for the known clock issue (#188), then the battery images and modules.

Expand Down
22 changes: 21 additions & 1 deletion device/husky/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,26 @@ Sources:
- `P/`: postmarketOS pmaports `device/testing` (2026-10-21).
- `G/`: Google's GPL kernel for this phone, `android-gs-shusky-6.1-android16` ([source.android.com: Build Pixel kernels](https://source.android.com/docs/setup/build/building-pixel-kernels)).

## 2026-11-09: NFC on the 8 Pro: the pad clock and the controller, two boots on the head of kernel #209

My phone (the Kioxia unit), slot B. Kernel PR [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209) (the `exynos-clkout` match for zuma, plus the `nfc@8` node from #208) was tested at its head, `e9c3fa348` (a8087e225 plus the two optional edits Derek suggested, a DTS comment and a commit message line); the kernel is `7.3.0-rc6-omamobile-push1-ge9c3fa348c8a`, built with my test kernel's config. That head has no HK3 display driver and no PCIe PHY symbol, so these boots had a simple framebuffer, no Wi-Fi and no sound; the phone was driven over USB ssh. Each boot spent one slot B try; the count was refilled to 3 with `fastboot set_active b` before each flash.

The overlay of boot 1 was one local file, `nfc-test.dtso`, not in the repository, added to the usual battery, panel and gauge overlays of my image set (the plain set of boot 2 is the same without it):

```
/dts-v1/;
/plugin/;

&nfc {
status = "okay";
};
```

- **Boot 1, with the overlay** [V] (uptime 213 s): `nxp_nci_i2c` bound on `2-0008`, `nfc0` present, `pmu-clkout0` enable count 1 and prepare count 1 in `clk_summary`, and a Type 2 (MIFARE) tag read through neard with one URI record (only the shape of the record was looked at, not its content). The one failed unit was my local thermal script, which wants a cpufreq policy this kernel doesn't have.
- **Boot 2, the same kernel with the plain image set (no overlay)** [V] (uptime 205 s): no `2-0008` device and no `nfc0` (the node is in the device tree, disabled), the `exynos-clkout` device bound with its clock registered, `pmu-clkout0` enable count 0 and prepare count 0: nothing is enabled.
- **After the two boots** [V]: the phone went back to the usual image set and was fine (AoC card up, 94 services, Wi-Fi, Hyprland).
- **Not done** [U]: **s2idle with the clkout driver bound** is still open and has to be tested before NFC is turned on in the device package (Derek's note on #209). It is a hang-class test, so it needs someone with the buttons in reach. Card emulation was not tested, and the eSE side (spi_12) is not described and was not touched.

## 2026-11-08: a third phone: Samsung 128 GB, UFS 3.1, still locked

A third retail Pixel 8 Pro, offered in [#1](https://github.com/derekross/omarchy-mobile/issues/1). `R3/` below means read-only queries of this phone (`adb shell getprop` while booted, `fastboot getvar all` on the locked bootloader), facts only, no serial, IMEI or MACs. Nothing has been unlocked, flashed or booted on it yet.
Expand All @@ -35,7 +55,7 @@ Lef's phone (Kioxia unit), slot B, while looking for the cause of a ~520 mA idle

## 2026-10-31: Wi-Fi

Wi-Fi works on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (a draft, stacked on #153, #143 and #56), at `f47c5bd34` on greenbrettmichael/linux-omarchy-mobile `omamobile-zuma-husky-wifi`, with the repository's husky config (`CONFIG_PHY_ZUMA_PCIE=m` is in #214), `modules-push` and the firmware from [#214](https://github.com/derekross/omarchy-mobile/pull/214). The phone joins its network at boot through NetworkManager. #156 has since been rebased to `717fba4f`; the only change is #143's join-parameter struct (`chanspec_list[1]` to `chanspec_list[]`). The phone joined at boot on that head too, as part of the display test kernel (tag `husky-test-20261031-d3`, which contains `717fba4f`), on 2026-10-31.
Wi-Fi works on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (it was a draft, stacked on #153, #143 and #56; closed on 2026-11-09 because its commits landed through [#187](https://github.com/derekross/linux-omarchy-mobile/pull/187), and the open gaps below stay in these notes), at `f47c5bd34` on greenbrettmichael/linux-omarchy-mobile `omamobile-zuma-husky-wifi`, with the repository's husky config (`CONFIG_PHY_ZUMA_PCIE=m` is in #214), `modules-push` and the firmware from [#214](https://github.com/derekross/omarchy-mobile/pull/214). The phone joins its network at boot through NetworkManager. #156 has since been rebased to `717fba4f`; the only change is #143's join-parameter struct (`chanspec_list[1]` to `chanspec_list[]`). The phone joined at boot on that head too, as part of the display test kernel (tag `husky-test-20261031-d3`, which contains `717fba4f`), on 2026-10-31.

- **The chip** [V]: a BCM4398 D0 (chip `0x4398` rev 3, PCI `14e4:4444`) on pcie_1, one Gen3 lane, as on stock.
- Its backplane is Broadcom's newer NCI interconnect (socitype 6), not AI. #156 ports enough of Google's `nciutils.c` to brcmfmac to find the cores and run the ARM.
Expand Down