Skip to content

omamobile-gnss 0.2.11: apps get positions after Location is turned on, and the runner records its own namespace PID - #864

Open
den-kloot wants to merge 2 commits into
derekross:mainfrom
den-kloot:gnss-location-setting
Open

den-kloot wants to merge 2 commits into
derekross:mainfrom
den-kloot:gnss-location-setting

Conversation

@den-kloot

@den-kloot den-kloot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Parts 2-4 of #862, found on the Pixel 9a the first time Location reached a fix on it:

  • The desktop's location setting. xdg-desktop-portal's Location portal (which libgeoclue's GClueSimple goes through) refuses every request while org.gnome.system.location enabled is false, the default on a new account (org.freedesktop.portal.Error.NotAllowed: Location services disabled). The GeoClue agent unit now sets it true before it starts and false after it stops, so it follows the switch.
  • GeoClue after Location off/on. GeoClue 2.8.2 refuses every client of a user whose agent registered again while the service kept running (AccessDenied: Geolocation disabled for UID 1000), and the switch restarts the agent. omamobile-gnss on|off now stops geoclue.service (D-Bus activated) before the caller's agent starts or stops, so the agent registers with a fresh service. The upgrade from before 0.2.11 does the same and restarts running agents once, so the setting is applied without a new login.
  • ns.pid. omamobile-vendor-chroot recorded awk's own PID (awk '/^NSpid:/ …' /proc/self/status runs in a child), so run and ns failed with nsenter: cannot open /proc/N/ns/mnt. That is the documented way to start the 9a's gnssd by hand. The PID is now read with a shell builtin. The same file is what the modem profile's NV overlay uses, so the fix also makes the overlay's capture at the modem's stop, and omamobile-modem nv-overlay diff and capture (and their timer), reach the running profile: with awk's dead PID they could never have worked, on any phone.

Device and build

  • Phone: Pixel 9a (tegu), slot B
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-gbd32edee1132
  • Packages changed, with versions: omamobile-gnss 0.2.11

Checks (no phone needed)

  • tools/pr-check passes (against c4623572, on the laptop)
  • tests/all: passes except tests/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 on main) on a heavily loaded laptop.
  • tests/packages for the package touched: packages/omamobile-gnss/test/all passes
  • 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; the AI help is a Co-Authored-By: trailer, no Signed-off-by:

On the phone

  • The new agent unit (as a user override) and the new CLI (run as root) on my phone, with omamobile-gnss 0.2.9 installed: Location off → setting false, portal refuses; on → setting true, a position at once (GeoIP, then GPS GGA/RMC); off → on again: answered. With the old CLI the second "on" was refused until geoclue restarted (reproduced three times).
  • The ns.pid fix: with the namespace PID corrected, omamobile-vendor-chroot modem run /vendor/bin/hw/gnssd entered the running modem namespace and gnssd ran.
  • Not tested: the upgrade hook on a real upgrade (only its shell syntax and the test's order checks), and the 7 Pro (same units, no 9a-specific code).
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace
tools/phone-smoke report

phone-smoke: unknown

Kernel 7.3.0-rc6-omamobile-push1-gbd32edee1132, tools at unknown, 2026-11-17T11:25Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-gbd32edee1132, slot b, up 4341s
storage guard (required) ok 62 partitions; only userdata and slot b's boot images writable
root (required) ok ext4 on userdata, 71G free
kernel health (required) ok no oops or BUG; 0 WARN, 0 error lines in dmesg (0 known, 0 new)
systemd units not ok failed: omamobile-bt-addr@hci0.service
USB gadget (required) ok bound to 11210000.usb
display ok card1-DSI-1 connected, 1080x2424
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok Synaptics TouchComm Touchscreen
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link down
Bluetooth ok hci0, powered false
battery ok 58% Charging, 39 °C
sound cards ok googleteguaocsn
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 55 °C

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@hci0 failed on the previous boot with the old kernel too: unrelated.)

🤖 Generated with Claude Code

…, and the runner records its own namespace PID

Found on the Pixel 9a on 2026-11-17, the first time Location reached a
fix on it (7.3.0-rc6-omamobile-push1-gbd32edee1132):

- The desktop's location setting. libgeoclue's GClueSimple goes through
  xdg-desktop-portal's Location portal, which refuses every request while
  org.gnome.system.location enabled is false, the default on a new
  account ("org.freedesktop.portal.Error.NotAllowed: Location services
  disabled"). Nothing turned it on, so with Location on, a fix in the
  NMEA stream and the agent running, where-am-i and every libgeoclue app
  got nothing. The agent unit now sets it true before it starts and false
  after it stops, so it follows the switch (and the session: the next
  login's start turns it on again).

- GeoClue and a restarted agent. GeoClue 2.8.2 refuses every client of a
  user whose agent went away and registered again while the service kept
  running ("Starting GeoClue client failed: ... AccessDenied: Geolocation
  disabled for UID 1000"), and turning Location off and on restarts the
  agent. Reproduced three times on the phone; a stop of geoclue.service
  (it is D-Bus activated) made the next agent start work every time.
  "omamobile-gnss on" and "off" now stop geoclue as root before the
  caller's agent starts or stops, so the agent's registration goes to a
  fresh service.

- The upgrade from before 0.2.11 stops geoclue and restarts the running
  agents once (a restart, not start + try-restart, which would register
  twice under the new service), so the setting is applied without a new
  login.

- The namespace PID. omamobile-vendor-chroot wrote
  awk '/^NSpid:/ {print $2}' /proc/self/status, which is awk's own,
  short-lived PID, so "run" and "ns" failed with "nsenter: cannot open
  /proc/N/ns/mnt" (the documented way to start gnssd by hand). It is now
  read with a shell builtin, so /proc/self is the runner.

On the phone: Location off -> on -> off -> on with this CLI and agent
unit, each "on" answered at once (GeoIP first, then GPS GGA/RMC); without
it the second "on" was refused until geoclue restarted. The ns.pid fix
let "omamobile-vendor-chroot modem run /vendor/bin/hw/gnssd" enter the
running modem namespace.

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

Copy link
Copy Markdown
Owner

Thank you for this, and for #862: three separate causes, each with its log line, is exactly what makes a report like that usable. I reproduced the ns.pid bug here in a fresh PID namespace (awk reports its own PID, your builtin loop reports the runner's), checked the order in the switch (the root half finishes before the caller's agent starts, so "on" always meets a fresh GeoClue), and confirmed that the portal's "Location services disabled" comes from the lockdown key that follows org.gnome.system.location.

Two things have to happen on my Pixel 7 Pro before I merge, and both are mine to do:

  1. The ns.pid fix does more than run and ns. The modem profile's NV overlay reads the same file: the capture at the modem's stop (modem_nv_capture in modem.conf) returns silently when the PID isn't alive, and omamobile-modem nv-overlay diff and capture (and the 30-minute timer) answer "the modem profile isn't running". With awk's dead PID in the file, none of them can ever have worked, on any phone. Your fix switches them on. That is what we want, and nothing in it touches an NV partition (the capture reads RAM copies and writes only the overlay directory on userdata), but its first run has to be deliberate, so I'll check my phone's state and run the overlay's read-only step first. Could you add a sentence to the description saying the fix also makes the overlay's capture reachable? And one question: on your 9a, has a modem stop run yet with a correct ns.pid (the new runner installed, not the file corrected by hand)? If so, what did journalctl -b -1 say around "nv-overlay" at the stop?
  2. omamobile-gnss on|off now stops GeoClue on every phone. GeoClue is the same version everywhere, so I expect the 7 Pro has the bug you found; I'll run off, on, off, on from the tile there with the weather widget open, and the upgrade from 0.2.10 with Location on.

One suggestion for the tests: test/install-hook.sh's stand-in vercmp only ever prints 0 or 1, so the new "older than 0.2.11" branches (stop GeoClue, restart the agent) are never run; test/all only greps for the two strings. A stand-in that can answer -1, and an assertion that the stop comes before the restart in the recorded calls, would cover them.

I'll report the 7 Pro's results here.

@W4HO-ham

Copy link
Copy Markdown
Contributor

One thing for when 0.2.11 is built for the repository, since this takes the version I asked for in #748: the published 0.2.10-1 has no usr/lib/omamobile-vendor/omamobile-gnss-client, which is den-kloot's first note under 5 in #862 as well. The build host's packages/omamobile-gnss/bionic/prebuilt/ is from before the client existed, so it needs one more make -C packages/omamobile-gnss/bionic NDK=<Android NDK r27 or later> before the package is built, and tar -tf out/repo/aarch64/omamobile-gnss-0.2.11-1-aarch64.pkg.tar.zst | grep omamobile-gnss-client should then print the file. If the NDK on the build host is what's in the way, say so and I'll send a script that fetches a pinned NDK and runs the make.

I'll run this branch with #863 on my palmtop tomorrow and post the result here.

@W4HO-ham

Copy link
Copy Markdown
Contributor

Ran on my palmtop this morning with #863 (the kernel and versions are in my comment there): omamobile-gnss 0.2.11-1 from this branch, with the 9a's client from my local bionic/prebuilt/, upgraded from 0.2.10-1 with Location on and the modem off, then a reboot.

  • ns.pid names the runner now. /run/omamobile-vendor/modem/ns.pid held the PID of omamobile-vendor-chroot, and omamobile-vendor-chroot modem ns findmnt entered the namespace.
  • The setting follows the switch. Done as the tile does it (systemctl start omamobile-gnss-location@off|on.service, then the user's agent stopped or started), off, on, off, on: org.gnome.system.location enabled read false, true, false, true, and the agent was inactive, active, inactive, active. After the upgrade and the reboot the setting was true and the agent active.
  • GeoClue never refused the user: no "Geolocation disabled for UID" in the journal over five off/on rounds in the boot.
  • Positions for a libgeoclue client (where-am-i -t 40 as the session's user) after an "on": 69, 66 and 69 positions in three runs, and none within the 40 s in two others (the first after the boot, and one after an off/on). A 120 s run after 90 s with Location off had its first position after 1 s. The two empty runs came with no refusal and no error from the client, and I don't know yet what they were.

One thing I couldn't check is the overlay's capture at the modem's stop: the NV overlay isn't turned on on my palmtop (no /etc/omamobile/modem-nv-overlay-enable). The next clean reboot will be its first modem stop with a correct ns.pid; I'll say here what the journal has around "nv-overlay" then.

@W4HO-ham

Copy link
Copy Markdown
Contributor

The clean reboot was this morning, so here is the modem's first stop with a correct ns.pid on my palmtop: omamobile-modem 0.1.27-1 from #863 and omamobile-gnss 0.2.11-1 from this branch, both installed since yesterday's boot. The NV overlay is off here (no /etc/omamobile/modem-nv-overlay-enable).

Before the reboot, with the modem up:

  • /run/omamobile-vendor/modem/ns.pid named omamobile-vendor-chroot modem start.
  • omamobile-modem nv-overlay status said enabled: no (/etc/omamobile/modem-nv-overlay-enable absent) and state: none (the modem starts from the backup alone).
  • omamobile-modem nv-overlay diff got into the profile and answered no base recorded at this start: the overlay was off when the modem started. Before the fix it could only say the profile isn't running.

At the stop (systemctl reboot), from journalctl -b -1:

systemd: Stopping [systemd-run] /usr/bin/bash -c "exec /usr/lib/omamobile-vendor/omamobile-vendor-chroot modem start >> /var/log/omamobile/modem.log 2>&1"...
kernel: cpif: s5100_poweroff_pcie: Skip pci power off: already powered off
omamobile-vendor-chroot: omamobile-modem-nv-overlay: off (/etc/omamobile/modem-nv-overlay-enable absent): nothing kept
omamobile-tegu-modem-up: modem stopped (success, the CP OFFLINE before the daemons went): /var/lib/omamobile/modem-bringup-started removed
systemd: omamobile-tegu-modem.service: Deactivated successfully.

That one line is all the journal has on the overlay for that boot. So the capture at the stop is reached now, and with the overlay off it keeps nothing. The unit's stop took 0.6 s.

The boot after it came up as usual: the CP ONLINE with IMS voice and SMS and the data bearer, the stub bound read-only over libsitril-gps.so in the namespace again, gnssd CODELOAD->OPERATIONAL, no failed unit.

I haven't turned the overlay on here, so a capture that keeps something is still untried on the 9a.

….2.11" branches

The stand-in vercmp only ever printed 0 or 1, so the branches that stop
geoclue and restart the agent on an upgrade from before 0.2.11 never ran,
and test/all only grepped for the two strings. The stand-in now answers
-1, 0 and 1 like pacman's, and the hook runs as an upgrade to 0.2.11-1
from 0.2.8-1, 0.2.10-1 and 0.2.11-1: from before 0.2.11 geoclue stops
before the agent restarts (by line order in the recorded calls); from
0.2.11 on geoclue is left alone and the agent is only started.

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

Copy link
Copy Markdown
Contributor Author

Results from my Pixel 9a (tegu, slot B, kernel 7.3.0-rc6-omamobile-push1-gbd32edee1132, omamobile-modem 0.1.26-1), and the test you suggested.

The test. test/install-hook.sh's stand-in vercmp now answers -1, 0 and 1 (pkgrel ignored), and the hook runs as an upgrade to 0.2.11-1 from 0.2.8-1, 0.2.10-1 and 0.2.11-1. From before 0.2.11 it checks that geoclue is stopped and that this comes before the agent's restart in the recorded calls; from 0.2.11 on, that geoclue is left alone and the agent is only started. I checked that it catches the two regressions it is for: dropping the stop fails "geoclue stops before the agent restarts", and restarting the agent from 0.2.11 on fails too. test/all passes. Pushed as a second commit.

Description. Added under ns.pid: the fix also makes the NV overlay's capture at the modem's stop, and omamobile-modem nv-overlay diff|capture, reach the running profile for the first time.

The upgrade. 0.2.11-1 built from this branch (with the client from bionic/prebuilt/; tar -tf lists usr/lib/omamobile-vendor/omamobile-gnss-client), installed over the repository's 0.2.10-1 with Location on. The hook restarted the running agent, org.gnome.system.location enabled read true afterwards. pacman needed --overwrite for the client, which I had installed by hand before.

The switch, done as the tile does it (omamobile-gnss-location@off|on.service, then the agent): off, on, off, on gave the setting false, true, false, true and the agent inactive, active, inactive, active. No "Geolocation disabled for UID" and no portal refusal in the journal. After each "on" where-am-i got a position, but only GeoIP: indoors the receiver produced no fix within 3 minutes. Its NMEA stream had only $PSAMAID and $PSAMCLK, no GGA/RMC/GSV at all, while the HAL reported start and status 1. On 17.11 the same phone had a fix after ~55 s indoors with GGA/RMC, so I'll look at that separately; nothing in this PR touches the HAL or gnssd. After the boot below, where-am-i -t 40 also had no position in the first 40 s, like W4HO-ham's first run after a boot.

Your question: a modem stop with a correct ns.pid. Yes. The boot that started at 14:43 ran the new runner from the start (ns.pid named omamobile-vendor-chroot modem start, and omamobile-vendor-chroot modem ns findmnt / entered the namespace). It ended at 16:45 with a clean shutdown (low battery). From journalctl -b -1:

16:45:47 systemd-logind: System is powering down.
16:45:48 systemd: Stopping [systemd-run] /usr/bin/bash -c "exec /usr/lib/omamobile-vendor/omamobile-vendor-chroot modem start >> /var/log/omamobile/modem.log 2>&1"...
16:45:49 omamobile-vendor-chroot: omamobile-modem-nv-overlay: off (/etc/omamobile/modem-nv-overlay-enable absent): nothing kept
16:45:49 omamobile-tegu-modem-up: modem stopped (success): /var/lib/omamobile/modem-bringup-started removed

That is the only overlay line. The overlay is off here, as on W4HO-ham's palmtop, so a capture that keeps something is still untried on the 9a. The next boot came up normally: modem and mobile data up, gnssd running, ns.pid naming the runner again, and Location still on after the boot (setting true, agent active).

One thing I learned the hard way, for anyone testing this: on the 9a the modem can't be started a second time in the same boot (CPIF was loaded earlier this boot; reboot before starting the modem again), so a stop and start of omamobile-tegu-modem-boot.service leaves the phone without mobile data until a reboot. A reboot is the only way to test the stop.

@derekross

Copy link
Copy Markdown
Owner

Thank you both. @W4HO-ham, that run answers what I asked den-kloot about the 9a, and more: the upgrade from 0.2.10 with Location on, the switch four times with the setting following it and no refusal from GeoClue, ns.pid naming the runner, nv-overlay diff reaching the profile for the first time, and the modem's first stop with a correct ns.pid leaving exactly one line, "off (… absent): nothing kept", in 0.6 s. That is what I hoped the overlay-off case would look like.

Where this stands:

  • My Pixel 7 Pro runs are still to do, and they come before the merge: the overlay's state and a stop there, and the Location tile off and on with the weather widget open. I'll post them here.
  • The two empty runs. Two of your five where-am-i -t 40 runs got nothing (the first after the boot, and one after an off/on), with no error. A cold first fix took about 55 s on den-kloot's 9a in omamobile-modem 0.1.27: give gnssd the SIT RIL GPS stub on the Pixel 9a #863, so 40 s may simply be too short, but it can't tell "no fix yet" from "nothing delivered". Could you repeat those two cases with -t 120 and post gnssd's and GeoClue's journal lines for that time? If a position comes late, that's fine and I'd like the delay written down; if none comes, it's a fourth cause.
  • The client missing from the published 0.2.10-1: thank you, that's on my build machine. I'll rebuild the bionic prebuilt there before 0.2.11 is published and check the package lists the client. Please don't send the NDK script as part of this: a download with a pinned checksum is welcome, but as its own pull request, so it gets its own review.

@den-kloot, one request from last time is still open: a sentence in the description that the ns.pid fix also makes omamobile-modem nv-overlay diff|capture and the overlay's capture at the modem's stop reachable. The vercmp stand-in in test/install-hook.sh can be a follow-up.

@W4HO-ham

Copy link
Copy Markdown
Contributor

Both cases again with -t 120, on my palmtop this morning: kernel 7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty, omamobile-modem 0.1.27-1 (as merged in #863), omamobile-gnss 0.2.11-1 from this branch (a7e223c, with the client), Location on, indoors at the same spot as before. Times are the palmtop's clock; gnssd's own clock runs on UTC.

After an off/on: a fix, just past 40 s. Location off and on as the tile does it, then where-am-i -t 120. The receiver hadn't run yet that boot. The session started 6 s into the request, and gnssd logged its first fix 40.6 s after that:

gnssd: lal_router_tx_queue_internal: TARGET_GNSS_START
gnssd: SllOspHandlePsPosResp: Got First Fix from PTA(TTFF): 40.56 Sec
gnssd: GNSS_TTFF: 40557(ms) Accuracy:39(m) desired:HOT actual:COLD RefLoc:0 RefTime:0 RefFreq:1 Supl:0 0(ms) Sgee:0 Eph:1 Alm:1

So the first position from the receiver came about 46 s after the request, and my earlier 40 s run ended just before it. Until then the client got GeoClue's coarse positions (25 km). A second off/on two minutes later had the receiver's first position 9.7 s after the request, and 240 of them in the 120 s. So that case is "no fix yet", not a cause.

The start is cold every time because gnssd gets no reference time or position: its NTP lookup fails inside the modem profile, and the extended ephemeris request finds no network:

gnssd: SCSCNtpLookupHandler: getaddrinfo() error:7 - No address associated with hostname
gnssd: EEAidingProvider_Request: network unavailable

That isn't this PR's business, but it is why a first fix takes about 40 s here even with the sky in view.

The first request after a boot: a fourth cause. I rebooted and ran where-am-i -t 120 as soon as the session was up, at 20 s of uptime. The client got three coarse positions and nothing from the receiver. The NMEA socket was dead the whole time:

09:28:46 kernel: cpif: change_modem_state: s5300->state changed (BOOTING -> ONLINE)
09:28:50 systemd: Started Omarchy Mobile GNSS (...)
09:28:50 omamobile-gnss: gnssd isn't running (the modem profile with OMAMOBILE_MODEM_GNSS=1); nothing to do
   (start, "nothing to do", stop: five times in the same second, as GeoClue reconnected)
09:28:51 systemd: omamobile-gnss.service: Start request repeated too quickly.
09:28:51 systemd: omamobile-gnss.service: Failed with result 'start-limit-hit'.
09:28:51 systemd: Dependency failed for Omarchy Mobile GNSS NMEA bridge.
09:28:56 geoclue: Failed to connect to NMEA service: Could not connect: Connection refused
   (every 5 s to the end of the run; omamobile-gnss-nmea.socket stays failed)

gnssd started at 09:29:06, 20 s after ONLINE (OMAMOBILE_MODEM_GNSS_DELAY), 15 s after the socket had already failed. Nothing brings the socket back during the boot. Turning Location off and on does, because on runs enable --now on it, which is why my off/on case worked.

So a location request between the modem's start and gnssd's start leaves Location dead until the next boot or a toggle. The window is about the first minute after boot. The service exits at once there, GeoClue reconnects at once, and the start limit does the rest.

The fix I'd suggest is in omamobile-gnss-start, which this PR doesn't touch:

  • when gnssd isn't up but the modem unit runs with OMAMOBILE_MODEM_GNSS=1, wait for @GNSSND (bounded, say 90 s) instead of exiting;
  • when gnssd won't come, hold the connection for a few seconds before "nothing to do", so a client that reconnects can't trip the start limit.

I can send that as its own pull request on main once this one is in, as 0.2.12, unless you'd rather it went another way.

Nothing in either run asked for a coordinate; the numbers above are counts, times and accuracies.

@derekross derekross left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@den-kloot, first an apology: your push and your results of 15:51 crossed my comment of 16:06, which asked again for two things you had just done. Both are in: the description now says the ns.pid fix makes the overlay's capture and nv-overlay diff|capture reach the profile, and the hook's test runs the "older than 0.2.11" branches. I ran that test and broke the hook three ways (no geoclue stop, a restart from 0.2.11 on, the threshold at 0.2.10); each one fails the assertion written for it. Thank you also for the real upgrade from 0.2.10-1 and the second clean stop with a correct ns.pid. Nothing more is needed from you here.

One note on the modem: a stop and start of the 9a's modem unit in one boot is on our "never" list (a second start once reset the palmtop silently). The guard refused it for you, which is what it is for; a reboot is the way, as you found.

@W4HO-ham, thank you, that settles the 40 s question: gnssd's own line puts the cold first fix 40.6 s after the session start, so that run ended just short, and it is "no fix yet".

The first request after a boot is a real fault, and it is on main, not in this pull request: omamobile-gnss-start exits at once while gnssd isn't up yet, GeoClue reconnects, the start limit trips and the NMEA socket stays failed for the boot. Yes please to a pull request of its own as 0.2.12 once this is in. Two things to keep in it: the wait goes before the hang marker is written, as the client check does, and a wait that gives up leaves no marker behind. Could you open an issue with your journal lines now, so it isn't buried here? I've seen #900 and will review it on its own.

What is left is mine: the two Pixel 7 Pro runs (the overlay's state and a stop there, and the Location tile off and on with the weather widget open), and rebuilding the client on the build machine before 0.2.11 is published. I'll post the runs here and merge after them.

W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 19, 2026
…pt-in), with the runs on the published branch

Location now works whenever the modem is up, and the modem's start at boot is opt-in for the reason the Modem cell names, so the cell takes the same form as the Modem and Suspend cells. The record has the runs on the published omamobile at 26867fc4e with derekross#864 and derekross#921: a GNSS fix in 25 of 28 boots from a request made before gnssd was up, each reboot made during a session, none skipping GNSS; GeoClue's own start stalled in the other 3, cause open; and five switch-offs and -ons with a fix 7.5 to 9.4 s after each request.
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.

3 participants