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 @@ -49,7 +49,7 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists
| Modem | no | Lef, once a SIM is found ([Brett asked](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6544100933)) | cheetah [MODEM-PLAN](../cheetah/MODEM-PLAN.md); 9a [MODEM-PLAN](../tegu/MODEM-PLAN.md) ("ONLINE with IPC, no SIM yet") | A SIM (a prepaid one is the plan; the phone's own SIM is a data-only eSIM); the baseband is `g5300i` [V: fastboot], the S5300 family like cheetah's [I]; the CP's PCIe link and the `cpif` driver; modem firmware from the owner's own factory image; the NV protections. **Lef has a private read-only backup of the modem and calibration partitions (checksummed, plus an encrypted second copy) [V: not in this repository]; [#449](https://github.com/derekross/omarchy-mobile/pull/449) (open) gives husky's descriptor the `NV_PARTS` so `tools/nv-backup` takes and checks it.** | Read cheetah's and the 9a's MODEM-PLAN M0 to M2 end to end. Stage 0 is read-only: partitions, and what a booted phone answers without starting the modem |
| NFC | testing (a test kernel with the node switched on by an overlay: the chip answers and reads tags through `nxp-nci`; kernel [#208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209), both drafts) | Lef | 9a [#105](https://github.com/derekross/linux-omarchy-mobile/pull/105), [#104](https://github.com/derekross/linux-omarchy-mobile/pull/104) | What we found: an ST ST54L combo, its NCI controller at 0x08 on `hsi2c_0` (the haptics bus of #200) with its IRQ on gpa7, the chip's enable line on gph1-6 and a reference clock from the PMU's NFC pad (register 0x3e84); its secure element is on `spi_12` and is never to be touched. The driver is `nxp-nci` (as the 9a), not `st-nci`. On a test kernel the chip answered the NCI power-on, detected an ISO-DEP card, and read a Type 2 tag with one NDEF record; without the clock pad (#209) the same chip still powered on but found no tag in one run. Not tested: suspend, the secure element, the power cost of the pad clock, a second phone. The 9a's NFC must not poll through s2idle (AGENTS.md) | Merge #208 and #209, then s2idle with the driver bound and the clock's power cost |
| Cameras, video decode | no (read from the stock device tree, not tested) | unassigned | 9a [#103](https://github.com/derekross/linux-omarchy-mobile/pull/103); cheetah [CAMERA-PLAN](../cheetah/CAMERA-PLAN.md) | The sensors, the MIPI receiver and the rest of the pipeline; large. What we found for video: the SoC's codecs are Samsung's MFC (HEVC, VP9; firmware loaded behind the S2MPU through the GSA image loader) and Google's BigWave for AV1; neither has a driver in any tree we use, so there is no `/dev/video*` and Chromium decodes YouTube on the CPU, which heats the phone [V: Lef's phone] | After the rest; for video, a read of Google's MFC and BigWave trees first |
| Suspend | no (never run on husky) | unassigned | 9a [SLEEP-PLAN](../tegu/SLEEP-PLAN.md) (s2idle works, drain high); cheetah [SUSPEND-PLAN](../cheetah/SUSPEND-PLAN.md) | UFS hibern8 and system suspend ([UFS-PLAN](UFS-PLAN.md) U5 and U6); the "UFS at `spm_lvl` 5", "only s2idle" and "regulators late" gotchas. `/sys/power/mem_sleep` selects `deep` on the current kernels [V: Lef's phone], so a test must set `s2idle` first. Idle with the screen off draws about 0.5 A on Lef's phone, cause unknown; a CPU idle-state overlay and a power-domain overlay both reboot-looped the phone (recovered over fastboot), so neither is a safe next step [V: Lef's phone, test tree] | `pm_test=freezer` first, with the USB cable in; UFS-PLAN U5 on the guarded initramfs boot |
| Suspend | no (never run on husky) | unassigned | 9a [SLEEP-PLAN](../tegu/SLEEP-PLAN.md) (s2idle works, drain high); cheetah [SUSPEND-PLAN](../cheetah/SUSPEND-PLAN.md) | UFS hibern8 and system suspend ([UFS-PLAN](UFS-PLAN.md) U5 and U6); the "UFS at `spm_lvl` 5", "only s2idle" and "regulators late" gotchas. `/sys/power/mem_sleep` selects `deep` on the current kernels [V: Lef's phone, and Colin's on `husky-test-20261109-t1`]; omamobile-device-husky 0.1.10 makes systemd's Suspend use `s2idle`, but a test that writes `/sys/power/state` itself must still set `s2idle` first. Idle with the screen off draws about 0.5 A on Lef's phone, cause unknown; a CPU idle-state overlay and a power-domain overlay both reboot-looped the phone (recovered over fastboot), so neither is a safe next step [V: Lef's phone, test tree] | `pm_test=freezer` first, with the USB cable in; UFS-PLAN U5 on the guarded initramfs boot |
| Thermal, CPU DVFS | testing on [kernel #158](https://github.com/derekross/linux-omarchy-mobile/pull/158) (open, stacked on #157) | Brett | 9a [#87](https://github.com/derekross/linux-omarchy-mobile/pull/87) | #158 adds the CPU levels from the ECT and the CPU thermal zones; until then every core runs at the bootloader's rate. On Lef's test tree cpufreq-dt runs three policies and the four ACPM TMU zones report; software video decode took the SoC to 86 C, so his phone runs lowered passive trips and CPU caps as a stopgap (local, not in a package) | Review #158; then a skin temperature source (the S2MPG15 ADC) and cpuidle, which needs the MCT timer first |
| USB host, Type-C | testing (role switch to host without VBUS, once) | Lef (with Charging) | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a [#124](https://github.com/derekross/linux-omarchy-mobile/pull/124) | The Type-C controller is the MAX77759 TCPC above. dwc3 switches to xHCI host and back with no VBUS ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)); VBUS out is the gated part (draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)) | As Charging |
| Time, persistent storage | partly | unassigned | none yet | No RTC: `systemd-timesyncd` sets the clock a few minutes after Wi-Fi is up, and the first-boot release-key problem is fixed (omarchy-mobile #188, closed). Root is on `userdata` behind the read-only guard; marking slot B successful is a manual, attended step decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252); from 2026-11-01 to 2026-11-07 a local unit marked slot B on this phone; stopped pending #252, and nothing marks it on the 8 Pro until the boot-LUN guard change and the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)) are in | Write a short plan |
Expand Down
1 change: 1 addition & 0 deletions packages/omamobile-device-husky/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ Omarchy Mobile's first userspace package for the Google Pixel 8 Pro (codename hu
| `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover. A replug needs the USB rescue below: without it the link stays dead until a reboot |
| `vendor/systemd/logind.conf.d/10-omamobile-power-key.conf` | `/usr/lib/systemd/logind.conf.d` | A short power press does not power the phone off. Same drop-in as the Pixel 7 Pro. On husky the forced reset is Power + Volume Up held 15-30 s ([BRINGUP-M1](../../device/husky/BRINGUP-M1.md) test 23) |
| `vendor/NetworkManager/conf.d/10-omamobile-usb.conf` | `/usr/lib/NetworkManager/conf.d` | Keeps NetworkManager off that link |
| `vendor/systemd/sleep.conf.d/10-omamobile.conf` | `/usr/lib/systemd/sleep.conf.d` | Suspend means suspend-to-idle. The kernel's default on the 8 Pro is `deep` (`/sys/power/mem_sleep` reads `s2idle [deep]`), which Linux can't wake from on zuma yet. No hibernation: there is no swap. The settings are the Pixel 7 Pro's; the test checks. Suspend itself is still untested on the 8 Pro ([ROADMAP](../../device/husky/ROADMAP.md), [UFS-PLAN](../../device/husky/UFS-PLAN.md) U5 and U6), so this only keeps a tap on Suspend from choosing `deep` |
| `bin/omamobile-husky-display-start` + `vendor/systemd/system/omamobile-husky-display.service` + `display-manager.service.d/10-omamobile-husky.conf` | `/usr/bin`, `/usr/lib/systemd/system` | Loads gs-decon (kernel display PR) before the display manager, hang-safe: a synced marker that a start which never returns leaves behind keeps it off on the next boot, until `--retry`. First it allows the panel's DSI commands (`gs_dsim_cmd.allow_tx=1`, for brightness and 120 Hz), but only when the bootloader names the `google-hk3` panel on the command line, as the Pixel 9a's graphics start does for its panel. Then it sends the brightness systemd restored at boot again, which the panel could only take once `allow_tx` is on. On a kernel without the display PR (derekross/linux-omarchy-mobile#160) the DTB has no DECON0, so the unit is skipped by its condition and the screen stays on simple-framebuffer. With another panel name, `allow_tx` stays off and gs-decon runs read-only at 60 Hz |
| `vendor/modprobe.d/omamobile-husky-display.conf` | `/usr/lib/modprobe.d` | Blacklists gs_decon's autoload, so the display start loads it after `allow_tx`: gs-decon decides on 120 Hz at probe. Sets `screen_off=2`, as cheetah and tegu do: on DPMS off DECON stops its frames and the panel goes to sleep, and DPMS on wakes it |
| `vendor/modprobe.d/omamobile-husky-clk-acpm.conf` | `/usr/lib/modprobe.d` | Lets the GPU's ACPM clock move up to 890 MHz, stock's top (`zuma_gpu_max_khz`, kernel #157). The GPU thermal zone throttles it from 85 C. Without it the GPU stays at the bootloader's 150 MHz |
Expand Down
2 changes: 2 additions & 0 deletions packages/omamobile-device-husky/install
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ install -Dm644 vendor/systemd/logind.conf.d/10-omamobile-power-key.conf \
"$destination/usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf"
install -Dm644 vendor/NetworkManager/conf.d/10-omamobile-usb.conf \
"$destination/usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf"
install -Dm644 vendor/systemd/sleep.conf.d/10-omamobile.conf \
"$destination/usr/lib/systemd/sleep.conf.d/10-omamobile.conf"
install -Dm644 vendor/modprobe.d/omamobile-husky-clk-acpm.conf \
"$destination/usr/lib/modprobe.d/omamobile-husky-clk-acpm.conf"
install -Dm644 vendor/modprobe.d/omamobile-husky-display.conf \
Expand Down
10 changes: 10 additions & 0 deletions packages/omamobile-device-husky/test/all
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,11 @@ if [[ -f ../omamobile-device-cheetah/src/reboot-to.c ]]; then
../omamobile-device-cheetah/omamobile-device-cheetah.install \
|| fail "the pacman install script drifted from the cheetah package"
pass "the pacman install script matches the cheetah package"
# Its comment names zuma, cheetah's gs201: the settings are what must match
sleep=vendor/systemd/sleep.conf.d/10-omamobile.conf
[[ $(grep -v '^#' "$sleep") == "$(grep -v '^#' "../omamobile-device-cheetah/$sleep")" ]] \
|| fail "the sleep drop-in's settings drifted from the cheetah package"
pass "the sleep drop-in's settings match the cheetah package"
fi
grep -q 'omamobile-keyring' PKGBUILD || fail "pacman needs omamobile-keyring"
grep -q '^install=omamobile-device-husky.install$' PKGBUILD \
Expand All @@ -63,6 +68,7 @@ for f in usr/bin/reboot-to \
usr/lib/systemd/network/20-usb-gadget.network \
usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf \
usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf \
usr/lib/systemd/sleep.conf.d/10-omamobile.conf \
usr/lib/modprobe.d/omamobile-husky-clk-acpm.conf \
usr/lib/modprobe.d/omamobile-husky-display.conf \
usr/lib/systemd/system/omamobile-husky-display.service \
Expand All @@ -77,6 +83,10 @@ for f in usr/bin/reboot-to \
etc/pacman.d/omamobile-mirrorlist; do
[[ -f $tmp/root/$f ]] || fail "install stages $f"
done
grep -qx 'MemorySleepMode=s2idle' "$tmp/root/usr/lib/systemd/sleep.conf.d/10-omamobile.conf" \
|| fail "suspend must use s2idle: the kernel's default is deep, which zuma can't wake from yet"
grep -qx 'AllowHibernation=no' "$tmp/root/usr/lib/systemd/sleep.conf.d/10-omamobile.conf" \
|| fail "there is no swap to hibernate to"
grep -q 'KERNEL=="sda", MODE="0000"' "$tmp/root/usr/lib/udev/rules.d/10-omamobile-storage.rules" \
|| fail "the whole-disk node is made inaccessible"
grep -q 'ID_PART_ENTRY_NAME}!="userdata"' "$tmp/root/usr/lib/udev/rules.d/10-omamobile-storage.rules" \
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# SPDX-License-Identifier: MIT
# The firmware advertises PSCI SYSTEM_SUSPEND, so the kernel offers "deep"
# sleep, and on the 8 Pro it is the default (/sys/power/mem_sleep reads
# "s2idle [deep]", device/husky/ROADMAP.md, the Suspend row). Linux has no
# zuma SoC sleep sequence yet, so entering it would not wake, as on the
# Pixel 7 Pro (device/cheetah/SUSPEND-PLAN.md, sections 1 and 5). Suspend
# means suspend-to-idle until one exists. There is no swap to hibernate to.
[Sleep]
MemorySleepMode=s2idle
AllowHibernation=no
AllowHybridSleep=no
AllowSuspendThenHibernate=no
2 changes: 1 addition & 1 deletion packages/omamobile-device-husky/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.1.9
0.1.10