Skip to content

Pixel 9a: Location end to end — gnssd abort (libsitril-gps needs binder), portal 'Location services disabled', GeoClue after agent restart, stale ns.pid #862

Open

Description

@den-kloot

Summary

On 2026-11-17 a second Pixel 9a got Location working end to end, from the GNSS kernel pieces that are merged now (linux-omarchy-mobile #185, #222, #237, #247, built with CONFIG_EXYNOS_GNSS_IF_SPI=m) up to apps getting positions from GeoClue. The kernel side worked at the first boot. Five things in userspace or setup were in the way. Three of them are fixed in pull requests linked below; two are notes for whoever sets up the next 9a.

Result: first fix about 55 s after the session started (cold start, indoors by a window), 18 satellites seen, up to 5 used, GGA and RMC through GeoClue, no Kepler fault and no reset in the session. The modem came up with omamobile-tegu-modem-up --phone --gnss; the chroots came from the factory image CP3A.261005.005.

What went wrong, and the fixes

1. gnssd aborts 20 s after ONLINE: libsitril-gps needs binder (fix: PR, omamobile-modem 0.1.27)

[gnssd] I -[284]: libcustomgnss: dlopen /vendor/lib64/libsitril-gps.so
[gnssd] I libsitril-client[284]: RilClientHelperDLImpl::Init
[gnssd] E libbinder.ProcessState[284]: Binder driver /dev/vndbinder is unavailable. Using /dev/binder instead.
[gnssd] F libbinder.ProcessState[284]: Binder driver '/dev/binder' could not be opened. Error: 2 (No such file or directory) Opening '/dev/binder' failed. Terminating.
[gnssd] libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 284 (gnssd), pid 284 (gnssd)

libcustomgnss (gps.cfg GlueLayer_IsUseCustomGnssLib=1) takes exactly four symbols from libsitril-gps.so by dlsym: GpsOpen, GpsClose, RegisterCallback, RequestAGPS. Those are the four that omamobile-gnss's libomamobile-sitril-gps.so stub already provides for the 7 Pro's gpsd. With the stub bound over the image's library, gnssd goes CODELOAD -> OPERATIONAL and listens on @GNSSND. The PR binds it read-only inside the modem profile's namespace; the image stays as extracted. (MODEM-PLAN G3 noted GpsOpen() failing without radioExternal; with this chroot it is an abort, not a failure.)

2. Apps get "Location services disabled" (fix: PR, omamobile-gnss 0.2.11)

where-am-i and every libgeoclue client go through xdg-desktop-portal's Location portal, which refuses while org.gnome.system.location enabled is false, the default for a new account:

Failed to connect to GeoClue2 service: GDBus.Error:org.freedesktop.portal.Error.NotAllowed: Location services disabled

The GeoClue agent unit now turns the setting on at start and off at stop, so it follows the Location switch.

3. After Location off/on, GeoClue refuses the user until it restarts (fix: same PR)

xdg-desktop-portal: Starting GeoClue client failed: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000

GeoClue 2.8.2 refuses a user whose agent went away and registered again while the service kept running, and the switch restarts the agent. Reproduced three times; each time it worked again after systemctl stop geoclue (it is D-Bus activated). omamobile-gnss on|off now stops geoclue before the agent starts or stops. Tested on the phone: off, on, off, on all answered.

4. omamobile-vendor-chroot … run / ns can't enter the namespace (fix: same PR, and omamobile-fingerprint 0.1.18)

awk '/^NSpid:/ {print $2}' /proc/self/status > "$NSPID" records awk's own PID, not the runner's, so ns.pid names a process that has already exited:

nsenter: cannot open /proc/1685/ns/mnt: No such file or directory

That blocks the documented way to start gnssd by hand (omamobile-vendor-chroot modem run /vendor/bin/hw/gnssd). omamobile-fp-chroot has the same line. Both now read the PID with a shell builtin.

5. Notes for setting up a 9a by hand (no change proposed)

  • The gnss-slsi image and omamobile-gnss-client aren't in any package; the client needs the NDK (make -C packages/omamobile-gnss/bionic NDK=…, r27.2 worked). Without them, omamobile-gnss status reports "vendor files: missing", and turning Location on does nothing.
  • omamobile-tegu-modem-boot.service starts the modem without --gnss by default; gnssd only runs with it.
  • A kernel push replaces /usr/lib/modules/<release>. Modules installed by hand for the old release (here, a patched max77779_battery.ko) don't carry over, so the battery disappeared until they were rebuilt for the new release. This is expected behaviour (AGENTS.md), noted only because it hit at the same time.

Device

Activity

  1. den-kloot commented on Nov 17, 2026

    @den-kloot
    ContributorAuthor

    Fixes for this issue:

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions