Repository navigation
device-raven 0.1.30, device/raven: a raven root image builds from main again - #392
Merged
Merged
Conversation
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>
Owner
|
Thanks, that's the right fix: raven's package and omamobile-shell both installed |
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 noROOTFS_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 untilomamobile-gnss on).Device and build
uname -r): 7.3.0-rc6-omamobile-push1-ge1e6adb69bbfChecks (no phone needed)
tools/pr-check origin/mainpassestests/allpassestests/packagespasses (or the packages I touched: omamobile-device-raven)versionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
omamobile-boot-checkreported all parts up.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).userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)tools/phone-smokereportphone-smoke: raven
Kernel
7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at0d328a0, 2026-11-03T11:17Z.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