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
36 changes: 36 additions & 0 deletions device/husky/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,42 @@ 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-10-31: the touchscreen

Touch works on a test kernel, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153) (in review, stacked on #148). The test booted the U4 Omarchy image from `userdata` ([UFS-PLAN](UFS-PLAN.md)), with U4's kernel config.

- **The controller** [V, `R/` live DT]: an ST FTM5 (SALIXP, chip id `36 40`, firmware `0083`) on HSI0's USI2 SPI at `0x111d0000`.
- It runs at 10 MHz with manual chip select, as stock's `fts` node.
- Its attention line is `gpn0-0` (CUSTOM_ALIVE) and its reset is `gpp21-2` (PERIC1).
- The panel is 1344 × 2992.
- **Its rails** [V, `R/` live DT]: the main PMIC's (S2MPG14) LDO25M at 1.8 V and LDO4M at 3.3 V. The firmware leaves both off, already at those voltages.
- The PMIC sits behind ACPM, so #153 adds ACPM and its mailbox too.
- **Its clock** [V, `G/` CMUCAL tables]: the bootloader leaves USI2 at 399.36 MHz (PLL_SHARED2 / 2).
- zuma had no clock driver, so #153 adds one: it describes the path from CMU_TOP to USI2.
- It writes only USI2's divider and gates.
- **The scan echo** [V]: after the scan command, husky's firmware first reports a forced calibration (`43 05 01`), then echoes the command about 60 ms later.
- The `salixp` driver gave up after 50 ms. #153 waits up to stock's 2.5 s and stops at the echo.
- The touchscreen registers 3.8 s into the boot.
- **Orientation** [V, tag `husky-test-20261031-c5` on greenbrettmichael/linux-omarchy-mobile]: stock's node inverts both axes, but `salixp` already reports in the panel's orientation.
- With stock's inversion, taps came in rotated 180°: a tap at the top-left read (1191, 2824).
- Without it, a tap at the top-left reads (87, 144) of 1343 × 2991.
- **In Omarchy** [V]: Hyprland lists the touchscreen (`salixp-touchscreen`). The lock screen's PIN pad takes the keys that are touched, and the phone unlocks by touch. A touch wakes the screen.

## 2026-10-30: the buttons

Power and volume work through `gpio-keys` on a test kernel, the U4 kernel plus [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148) (in review). The test booted the U4 Omarchy image from `userdata` ([UFS-PLAN](UFS-PLAN.md)), with U4's kernel config.

- **The pins** [V, `R/` live DT]: power on `gpa4-0` (pull-up), volume down on `gpa4-1` and volume up on `gpa6-2`. All are active low, in the EINT function, and wake-up sources.
- **The ALIVE pin controller** [V, `R/` live DT]:
- It is at `0x154d0000`, controller 0 of the driver's zuma data, with ten banks (gpa0–gpa4, gpa6–gpa10).
- Each of its 50 pins has its own GIC interrupt, SPI 10–59 in pin order, level high, through a wake-up interrupt controller like Tensor G4's.
- zuma's upstream device tree had no ALIVE node, so #148 adds it.
- **Events** [V, tags `husky-test-20261030-b` and `-b2` on greenbrettmichael/linux-omarchy-mobile]: a reader on `/dev/input/event0` (`gpio-keys`) logged a down and an up event for each press of volume down (`KEY_VOLUMEDOWN`), volume up (`KEY_VOLUMEUP`) and power (`KEY_POWER`).
- **In Omarchy** [V]:
- A short press of power locks and darkens the screen, and the next one wakes it (omamobile-keys).
- Volume does nothing visible yet, since there is no sound card.
- **The driver's `irq number not available`** [V]: once ALIVE was described, the zuma pinctrl data ran the GPIO EINT setup on ALIVE, whose banks are all wake-up EINTs, and it logged this line at every boot. #148 drops that setup from ALIVE, as gs101 does, and test `-b2` logs no such line.

## 2026-10-21: stage 0, part 4: root capture, backup, and how ABL picks the DTB

Root for the capture: the stock `init_boot` from the CP3A.261005.005 OTA, extracted with `payload-dumper-go` 2.1.0 (hashes checked against the signed payload) and patched with Magisk v31.0, the first release with Android 17 support. It was flashed to **`init_boot_b` only**, with slot B booted. Slot A was not written. The capture and backup were read-only (`su -c cat`), into `~/android/reference/husky-root-*` (never the repository).
Expand Down
2 changes: 1 addition & 1 deletion docs/DEVICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have
| Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - |
| Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - |
| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | WIP ([#28](https://github.com/derekross/omarchy-mobile/issues/28): clocks, ACPM, panel and TCPC merged; the SoC and board device tree is in review, [kernel #80](https://github.com/derekross/linux-omarchy-mobile/pull/80)) | WIP (UFS root; reset across suspend merged, idle clock gating [kernel #99](https://github.com/derekross/linux-omarchy-mobile/pull/99)) | WIP (DSI panel 1080x2424 at 60 Hz, 120 Hz in review; panel driver merged, display DT [kernel #90](https://github.com/derekross/linux-omarchy-mobile/pull/90), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88)) | WIP (Panthor to 890 MHz; DT [kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85), [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87)) | WIP (DT [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), sleep fix [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82)) | WIP (gpio-keys; Power wakes s2idle) | WIP (gadget and replug; host mode: VBUS on, no enumeration yet; repeater driver [kernel #107](https://github.com/derekross/linux-omarchy-mobile/pull/107)) | WIP (brcmfmac joins WPA2; driver in review, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56)) | WIP (BCM4383 merged, [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); BlueZ, A2DP) | WIP (the gauge reads; unpublished kernel) | WIP (status and inhibit [kernel #92](https://github.com/derekross/linux-omarchy-mobile/pull/92); PD contract, tcpci_maxim merged, [kernel #97](https://github.com/derekross/linux-omarchy-mobile/pull/97)) | WIP (CS40L26, VPBR merged, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96)) | WIP (LM3644, 25 steps; DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96)) | no (firmware and CHPP run; the engine faulted with its three rails off at hand-off, now on, [kernel #101](https://github.com/derekross/linux-omarchy-mobile/pull/101)) | WIP (audio and sensors; unpublished kernel) | WIP (speakers capped, mics, A2DP; unpublished kernel) | WIP (accelerometer, light, proximity; unpublished kernel) | WIP (ONLINE with IPC, no SIM yet) | WIP (reads cards, [kernel #100](https://github.com/derekross/linux-omarchy-mobile/pull/100), clock [kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104)) | WIP (all three stream through libcamera, switching between them works; [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63), [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103)) | WIP (s2idle; Power and RTC alarm wake; drain still high) | WIP (sensor, trusted app and secure storage up, its stores on loop devices of images in `userdata`, [#101](https://github.com/derekross/omarchy-mobile/pull/101); factory calibration fetched, not loaded yet) |
| Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B, not marked successful; Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | WIP (simple-framebuffer: console and Omarchy's lock screen) | no | no | no | testing (USB and SSH) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no |
| Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B, not marked successful; Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | WIP (simple-framebuffer: console and Omarchy's lock screen) | no | testing (ST FTM5 over SPI on a test kernel, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); [NOTES](../device/husky/NOTES.md)) | testing (power and volume through `gpio-keys` on a test kernel, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); [NOTES](../device/husky/NOTES.md)) | testing (USB and SSH) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no |
| Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland lock screen) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are in review) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; a replug needs a reboot; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | no | no | no | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | no | no | no | no | no | no | no | no | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | no |
| *Template* | *codename* | *SoC* | | | | | | | | | | | | | | | | | | | | | | |

Expand Down