Skip to content

device-raven 0.1.30, device/raven: a raven root image builds from main again - #392

Merged
derekross merged 2 commits into
derekross:mainfrom
robotosaith:omamobile-raven-builds
Nov 3, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
robotosaith:omamobile-raven-builds

Conversation

@robotosaith

Copy link
Copy Markdown
Contributor

What and why

A raven root image no longer builds from main: pacstrap stops with "conflicting files" because device-raven still ships its own omamobile-sleepd (the binary, its user unit and the wants link) while omamobile-shell now ships the shared one. device-raven 0.1.30 drops its copy and keeps raven's sleep hook and s2idle policy. raven's descriptor also had no ROOTFS_PACKAGES, so a fresh install had the AoC up but no sensor proxy: it now installs omamobile-sensors, and omamobile-gnss as cheetah does (off until omamobile-gnss on).

Device and build

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes
  • tests/packages passes (or the packages I touched: omamobile-device-raven)
  • Each changed package has its version bumped, and the new version is in the commit subject
  • Commits have area prefixes and bodies that say why; any AI help is a Co-Authored-By: or Assisted-by: trailer, never a Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed (plan, step, result): a fresh install today from a root image built with device-raven 0.1.30; omamobile-sensors added by hand after the first boot (the descriptor change came after the image), then all four sensors and the gyro came up with the phone's factory calibration and omamobile-boot-check reported all parts up.
  • What I did not test: a second image built with the new ROOTFS_PACKAGES, and turning auto-sleep on with the shell's watcher (raven's old copy also held sleep off while an SSH session over usb0 was up; auto-sleep ships off).
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)
tools/phone-smoke report

phone-smoke: raven

Kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at 0d328a0, 2026-11-03T11:17Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, slot b, up 202s
storage guard (required) ok 49 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 198 error lines in dmesg (52 known, of them ASoC no backend DAIs (PipeWire probe) x1, 146 new)
new dmesg errors not ok cpif: mif_gpio_get_value: GET GPIO N is not valid x57; cpif: rx_demux: PCIE: ERR! N is not opened x17; cpif: pass_skb_to_demux: PCIE: N<N: ERR! N>recv_skb fail (N) x17
systemd units ok none failed
USB gadget (required) ok bound to 11110000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panfrost
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok s6sy761
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 95% Discharging, 31 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 46 °C

Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.1-1, omamobile-apps 0.2.2-1, omamobile-device-raven 0.1.30-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.1-1, omamobile-modem 0.1.14-1, omamobile-modem-sit 0.3.28-1, omamobile-omarchy 0.1.31-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.94-1, omamobile-voice 0.1.0-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

🤖 Generated with Claude Code

robotosaith and others added 2 commits November 3, 2026 12:22
omamobile-shell ships the shared sleep watcher (omamobile-sleepd, its user
service and the graphical-session wants link), and device-raven still
carried its own copy of all three. The two packages couldn't be installed
together: pacstrap of a raven root image stopped with "conflicting files"
on /usr/bin/omamobile-sleepd. Raven now uses the shell's watcher; its
sleep hook (omamobile-sleep) and s2idle policy stay here.

Raven's copy also treated bl_power as panel-off and held off sleep while
an SSH session over usb0 was up; auto-sleep ships off, so that difference
only matters once someone turns the toggle on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
raven's descriptor had no ROOTFS_PACKAGES, so a raven image got the device
package but not omamobile-sensors: on a fresh install the AoC came up and
nothing read its sensors (accelerometer, light, proximity and compass
missing in the boot check). With omamobile-sensors installed the proxy
starts at boot and all four come up with the phone's factory calibration.
omamobile-gnss comes along as on cheetah; it stays off until
`omamobile-gnss on`. Audio and the modem stay out until their own work
lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thanks, that's the right fix: raven's package and omamobile-shell both installed /usr/bin/omamobile-sleepd, and the shell's watcher already refuses sleep while SSH is open. Merging. One note for the record, nothing for you to do: the open 9a telephony stack also bumps device-raven to 0.1.30, so whichever lands second takes 0.1.31.

@derekross
derekross merged commit aa9616e into derekross:main Nov 3, 2026
2 checks passed
@robotosaith
robotosaith deleted the omamobile-raven-builds branch November 4, 2026 14:01
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
derekross#392)

* device-raven 0.1.30: leave omamobile-sleepd to omamobile-shell

omamobile-shell ships the shared sleep watcher (omamobile-sleepd, its user
service and the graphical-session wants link), and device-raven still
carried its own copy of all three. The two packages couldn't be installed
together: pacstrap of a raven root image stopped with "conflicting files"
on /usr/bin/omamobile-sleepd. Raven now uses the shell's watcher; its
sleep hook (omamobile-sleep) and s2idle policy stay here.

Raven's copy also treated bl_power as panel-off and held off sleep while
an SSH session over usb0 was up; auto-sleep ships off, so that difference
only matters once someone turns the toggle on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* device/raven: put the sensors and GNSS packages in the root image

raven's descriptor had no ROOTFS_PACKAGES, so a raven image got the device
package but not omamobile-sensors: on a fresh install the AoC came up and
nothing read its sensors (accelerometer, light, proximity and compass
missing in the boot check). With omamobile-sensors installed the proxy
starts at boot and all four come up with the phone's factory calibration.
omamobile-gnss comes along as on cheetah; it stays off until
`omamobile-gnss on`. Audio and the modem stay out until their own work
lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants