Repository navigation
omamobile-modem 0.1.27: give gnssd the SIT RIL GPS stub on the Pixel 9a - #863
Conversation
gnssd's libcustomgnss (gps.cfg GlueLayer_IsUseCustomGnssLib=1) dlopen()s
/vendor/lib64/libsitril-gps.so and takes GpsOpen, GpsClose,
RegisterCallback and RequestAGPS from it. The real library reaches the
RIL's GPS channel through libsitril-client over binder, and the modem
profile has no binder. With a modem chroot extracted from
CP3A.261005.005, libbinder ends gnssd at its first call, 20 s after
ONLINE:
F libbinder.ProcessState: Binder driver '/dev/binder' could not be
opened. Error: 2 (No such file or directory) ... Terminating.
libc: Fatal signal 6 (SIGABRT) ... (gnssd)
so @GNSSND never appears and Location has no receiver. The profile now
bind-mounts omamobile-gnss's stub (libomamobile-sitril-gps.so, the same
four calls succeeding as no-ops, which the 7 Pro's gpsd already preloads)
read-only over that file, inside the profile's namespace only: the image
stays as extracted. Without the image's library or without the stub it
does nothing (with a note for the missing stub). bind() is not used for
it, because it truncates a file target before mounting.
On the Pixel 9a (7.3.0-rc6-omamobile-push1-gbd32edee1132, modem up with
--gnss, no SIM needed): with the stub in place gnssd goes
CODELOAD -> OPERATIONAL, listens on @GNSSND, and a Location session gave
its first fix after about 55 s (cold, indoors), 18 satellites seen, up to
5 used, no Kepler fault.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, this is a clean fix, and the write-up in #862 made it easy to follow. I checked the mechanism here in a scratch namespace: the stub mounts read-only over a file inside the read-only image bind, the chroot reads the stub, and the image's own file is untouched. I also deleted the read-only remount to see your test fail, and it does. The Pixel 7 Pro can't reach the new function, since only the 9a's modem image carries gnssd. Two things before I merge it:
Two smaller points:
|
|
I'll run this on my palmtop (the BP3A chroot, where |
|
Ran on my palmtop this morning (2026-11-18), with the BP3A chroot.
So on the BP3A chroot the stub changes nothing I can see: |
… the same way twice SLOT=b in boot-update.conf moved the modem to modem_b, but omamobile-boot-update treats SLOT=b as its default, the same as no line, so adding the documented default to a slot-B phone would have paired the firmware with an older radio image and set the NV overlay aside. SLOT=b now reads nothing else and gives modem_a, like no line. SLOT=a (a format-2 install on slot A) still gives modem_a only on a boot from slot A. Nothing selects modem_b until a slot-B install has a signal of its own (ACTIVE-SLOT-PLAN §4, which now describes what was built). The rule is in the profile (shell) and the NV overlay (Python), and the two differed on a CRLF line, a CR in bootconfig and non-UTF-8 bytes, where the Python side also raised an uncaught error. Both now read bytes and split on \n only, a boot-update.conf that is there but can't be read is unknown in both, and test/all feeds one table of 31 inputs to both readers. The version moves to 0.1.28: #863 keeps 0.1.27. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Merged as omamobile-modem 0.1.27, thank you @den-kloot, and thank you @W4HO-ham for the start from the package on the BP3A chroot: that was the run I was waiting for. Two things I'd still like, as a follow-up PR whenever it suits:
|
…h new profile functions kept, version 0.1.28 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
What and why
Part 1 of #862. On the Pixel 9a, gnssd aborts 20 s after the modem reaches ONLINE:
libcustomgnssdlopen()s/vendor/lib64/libsitril-gps.so, whoselibsitril-clientneeds binder, and the modem profile has none (F libbinder.ProcessState: Binder driver '/dev/binder' could not be opened ... Terminating., SIGABRT). So@GNSSNDnever appears and Location has no receiver.libcustomgnsstakes onlyGpsOpen,GpsClose,RegisterCallbackandRequestAGPSfrom that library (bydlsym), the same four that omamobile-gnss'slibomamobile-sitril-gps.soalready stubs for the 7 Pro's gpsd. The modem profile now bind-mounts that stub read-only over the library inside its own namespace when the GNSS devices go in. The extracted image is unchanged. Without the library or without the stub, it does nothing (with a note in the second case). It doesn't usebind(), which truncates a file target before mounting.Device and build
uname -r): 7.3.0-rc6-omamobile-push1-gbd32edee1132 (local: the previous kernel plus linux-omarchy-mobile device-oriole: add minimal first-light policy package #222, device-panther 0.1.3: USB comes back after a replug, and the battery plan #247, omamobile-shell 0.2.56: fluid home and drawer gestures #237 andCONFIG_EXYNOS_GNSS_IF_SPI=m)Checks (no phone needed)
tools/pr-checkpasses (againstc4623572, on the laptop)tests/all: passes excepttests/install-phone's "an interrupt on the other slot's screen", a signal-timing case in a file this PR doesn't touch. It failed on some runs and passed on others (including onmain) on a heavily loaded laptop.tests/packagesfor the package touched:packages/omamobile-modem/test/allpassesversionbumped, and the new version is in the commit subjectCo-Authored-By:trailer, noSigned-off-by:On the phone
libsitril-gps.so, gnssd wentCODELOAD -> OPERATIONAL, listened on@GNSSND, and a Location session had its first fix after about 55 s (cold, indoors), 18 satellites seen, up to 5 used, no Kepler fault, no reset.modem_gnss_sitrilitself ran inside the live modem namespace: the stub was mountedroover the library, and the host's image file was untouched and not mounted.userdata, weakens the storage guard, or reads registers from userspacetools/phone-smokereportphone-smoke: unknown
Kernel
7.3.0-rc6-omamobile-push1-gbd32edee1132, tools atunknown, 2026-11-17T11:25Z.Packages: hyprland 0.57.0-3.4, libcamera 0.7.2-4.25, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.3-1, omamobile-audio 0.5.18-1, omamobile-device-tegu 0.2.18-1, omamobile-firstboot 0.1.5-1, omamobile-gnss 0.2.9-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.4-1, omamobile-modem 0.1.21-1, omamobile-modem-sit 0.3.35-1, omamobile-omarchy 0.1.44-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-settings 0.1.2-1, omamobile-shell 0.2.127-1, omamobile-voice 0.1.0-1, omaphone 0.2.3-1, omarchy 4.5.0-3, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1
(
omamobile-bt-addr@hci0failed on the previous boot with the old kernel too: unrelated.)🤖 Generated with Claude Code