Skip to content

DEVICES: the Pixel 9a's charging, AoC, speakers, sensors, NFC and cameras on by default, fingerprint opt-in, GNSS to testing - #248

Closed
W4HO-ham wants to merge 5 commits into
derekross:mainfrom
W4HO-ham:devices-tegu-0.2.3
Closed

W4HO-ham wants to merge 5 commits into
derekross:mainfrom
W4HO-ham:devices-tegu-0.2.3

Conversation

@W4HO-ham

@W4HO-ham W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Now that omamobile-device-tegu 0.2.3 is merged (#235), the charge limit, the AoC and NFC start at boot from the package, so their 9a cells move from "testing" (by hand) to "works" (on by default). Each was verified on a boot of its kernel pull request's head, built from the shared config fragment with #227's options. The record is the "every testing row on a published-style kernel" entry in #244, which now gives each boot's uname -r:

Cell Was Now Boot
Charging testing, driver loaded by hand works: the charger from the DT (kernel #161), the package's charge limit 7.3.0-rc6-omamobile-push1-g7dbac6f4e65c
AoC testing, started by hand works: at boot from the DT (kernel #162), 93 services 7.3.0-rc6-omamobile-push1-g922812d75006
Speakers/mics testing, by hand works: a tone from the speaker, the microphone at -32 dBFS, at boot with the AoC; the -10 dB ceiling stays same
Sensors testing, by hand works: five sensors through the proxy at boot same
NFC testing, started by hand works: at boot with neard and the link opener (kernel #104, #105) 7.3.0-rc6-omamobile-push1-gb45a0d400e49
Fingerprint testing works (opt-in), as on the 7 Pro: the service ships disabled because its first run writes Trusty's secure storage; the sensor binds from the DT (kernel #165) 7.3.0-rc6-omamobile-push1-gb533af3f1cbc

The kernel parts are in review, as for the display and GPU cells, and each cell names them. I've left the other cells alone:

This depends on #244 for the record's anchor, so please merge #244 first. tools/pr-check passes.

…y default with device-tegu 0.2.3, and fingerprint opt-in

With omamobile-device-tegu 0.2.3 merged, the charge limit, the AoC with its speakers, microphone and sensors, and NFC start at boot from the package, and each was verified on a boot of its kernel pull request's head. Fingerprint follows the 7 Pro's opt-in rule.
On the boot of kernel derekross#164's head the camera drivers loaded from the device tree with nothing by hand, libcamera listed all three cameras and each streamed.
@W4HO-ham

W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

Added the Cameras cell. On the boot of kernel #164's head (7.3.0-rc6-omamobile-push1-g4023f585ccae), the regulator, sensor, DC-PHY and CSIS drivers loaded from the device tree with nothing loaded by hand. tools/phone-smoke reported "3 listed by libcamera", and each camera streamed at 1280x960: main at 19 fps, ultrawide and front at 30. Picture quality is libcamera's software ISP's, and the cell says so.

@W4HO-ham W4HO-ham changed the title DEVICES: the Pixel 9a's charging, AoC, speakers, sensors and NFC on by default, fingerprint opt-in DEVICES: the Pixel 9a's charging, AoC, speakers, sensors, NFC and cameras on by default, fingerprint opt-in Nov 1, 2026
With the PERIC0 clock fix a 30-minute Location session with the modem up ran clean, so GNSS works by hand; it is not on by default while the modem is started by hand.
@W4HO-ham

W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

And GNSS moves from WIP to testing. With kernel #172 (the PERIC0 GPIO clock kept on), a 30-minute Location session with the modem up ran clean: 3759 link cycles, 1763 of 1765 GGA fixed. Every session before that fix reset the palmtop within minutes. It stays "testing" because the modem is still started by hand. The record is #202's G3-L1.

@derekross

Copy link
Copy Markdown
Owner

Thank you for this. Moving the 9a's cells to "works" once the package starts them, with each cell naming the kernel pull request it rests on and the release of its boot, is how the matrix should work. I checked each tested commit against its kernel pull request's current head: for #161, #162, #105, #164 and #165 the trees are identical, so the cells describe what will merge. The camera cell's note on the software ISP's picture quality is a good touch.

A few things before it merges:

  1. The Boot cell. It still says B "was marked successful by hand on 2026-10-28 with the devinfo write approved on 2026-10-22, now on hold". Since then B was unmarked by the 10-31 fastboot recovery and marked again during the hold, as AGENTS: on the Pixel 9a a plain fastboot flash of slot B clears its successful flag too #224 and device/tegu NOTES: every testing row on a published-style kernel, and the bring-up leftovers #244 record. Please add that to the cell, for example "marked again on 2026-10-31 during the hold (record)", linking device/tegu NOTES: every testing row on a published-style kernel, and the bring-up leftovers #244's entry, so the cell matches the notes.
  2. The GNSS cell. It says Omarchy's Location switch serves fixes and "a 30-minute session on 2026-11-01 ran clean". I've asked on device/tegu MODEM-PLAN, AGENTS: GNSS gets a fix on the 9a #202 whether that session went through the Location switch or through tegu-gnss-session. The Location script still defaults to holding the link, which the plan says crashes the CP after about 105 s. Please word the cell to match the answer: if the 30 minutes came from the session script, say so, and add the Location-switch run once it's done.
  3. The title. It covers charging, AoC, speakers, sensors, NFC, cameras and fingerprint, but not GNSS moving to testing. Please add it, since the title becomes the commit subject.

The order: this merges after #244, whose anchor every changed cell links, and after #227, since the charging cell says the charger is "built by #227" and a kernel from today's fragment doesn't build it yet. Cells whose kernel parts are still in review say so, as the display cells do, which is fine.

Main changed only other rows of the matrix (the Pixel 8 Pro, the Pixel 7 and the OnePlus 13), so those come from main and the 9a row from this branch.
…the GNSS cell names the Location path

The Boot cell now says the 10-31 fastboot recovery unmarked slot B and that it was marked again that day during the hold, linking the NOTES entry, so the cell matches the notes. The GNSS cell says the 30-minute session went through the Location switch with omamobile-gnss 0.2.5's start and the modem link cycling, which is what the runner did.
@W4HO-ham W4HO-ham changed the title DEVICES: the Pixel 9a's charging, AoC, speakers, sensors, NFC and cameras on by default, fingerprint opt-in DEVICES: the Pixel 9a's charging, AoC, speakers, sensors, NFC and cameras on by default, fingerprint opt-in, GNSS to testing Nov 1, 2026
@W4HO-ham

W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

All three are in. The Boot cell now says B was unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold, linking #244's entry. The 30-minute GNSS session did go through the Location switch (omamobile-gnss 0.2.5's start, with the modem started by hand first and the link left to cycle; details on #202), and the cell now says that. The title ends with "GNSS to testing". I also merged main in, since the branch conflicted in other rows of the matrix; the 9a row is unchanged apart from these two cells.

@derekross derekross closed this in 2d402cf Nov 1, 2026
@derekross

derekross commented Nov 1, 2026 •

Copy link
Copy Markdown
Owner

Landed on main as 2d402cf (squashed, authored by you). My review notes from before the merge, for the record:

Thank you, all three are in. The Boot cell now records the unmark and the re-mark with a link to the record, the GNSS cell says the 30 minutes went through the Location switch with the modem started by hand and the link cycling, and the title covers GNSS. Thanks for merging main in too; I checked that the only change against main is the 9a row.

I'll merge this. The GNSS cell links #114 and #202 for its evidence, so I'll merge those around the same time.

derekross added a commit that referenced this pull request Nov 13, 2026
…11-13 runs (#731)

The overnight standby (about 22 h), power off and the charger boot (on a
kernel with linux-omarchy-mobile#233 and #554) and double tap from
suspend-to-idle (kernel #248, #730) passed on the reference phone today.
The cell moves from WIP to testing, not works: auto-sleep still ships off,
the fixes aren't in a kernel release, and with the modem up the phone
doesn't sleep (kernel #232 lost mobile data after refused sleeps today).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…y default, fingerprint opt-in, GNSS to testing (derekross#248)

With omamobile-device-tegu 0.2.3 the charge limit, the AoC and NFC start
at boot from the package, so the Pixel 9a's Charging, AoC, Speakers/mics,
Sensors and NFC cells move to "works" (on by default), and Fingerprint to
"works (opt-in)", as on the 7 Pro. Each was verified on a boot of its
kernel pull request's head built from the shared config fragment; the
record is derekross#244's entry, which gives each boot's uname -r. The Boot cell
records the 10-31 unmark and re-mark, and GNSS moves to testing with the
modem started by hand (derekross#114, derekross#202, kernel derekross#172). The kernel parts are in
review, as each cell says.

Closes derekross#248

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 14, 2026
…m sleep, auto-sleep by default, the charging boot, power off at a critical battery (#730)

* omamobile-device-cheetah 0.1.56: double tap wakes the phone from sleep

With auto-sleep on, the phone really sleeps (suspend-to-idle) 30 s after
the screen goes off, and then only the power key woke it: the touch
driver turned its interrupt off for the whole sleep. linux-omarchy-mobile#248
makes the touchscreen wakeup capable, off by default; this udev rule turns
it on for the 7 Pro's Synaptics S3908. On a kernel without #248 there is no
power/wakeup attribute and the rule does nothing.

Tested on the reference phone on 2026-11-13 with the rule's effect set by
hand (echo enabled > power/wakeup) on a kernel with #248: asleep through
omamobile-sleepd, a double tap woke it on the touchscreen's interrupt and
lit the lock screen. 0.1.54 and 0.1.55 are claimed by open pull requests
(#556, #554).

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

* omamobile-device-cheetah: auto-sleep on by default on the Pixel 7 Pro

Ship /usr/share/omamobile/auto-sleep-default, which omamobile-shell 0.2.129's
user setup reads (#737): suspend on this phone is verified
(SUSPEND-PLAN, 2026-11-13), and with this package's touch-wake rule a
double tap wakes it from sleep, so auto-sleep no longer costs double tap.

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

* device-cheetah 0.1.55: off-mode charging instead of starting the phone on its cable

A 7 Pro powered off on its cable is started by the bootloader with
androidboot.mode = "charger", where stock runs only a charging screen.
We started the whole phone (2026-11-09: both boots after a power off on
the cable read "charger").

omamobile-charger-mode-generator makes omamobile-charger.target the
default of such a boot (early folder; /etc/omamobile/charger-mode-disable
turns it off). The target starts no session, modem, Wi-Fi or AoC, and
keeps SSH over USB as on a normal boot (usb-rescue, usb-mac, ufw).
omamobile-charger-mode turns the panel off, restarts into the phone on
Power held for a second, and powers off five seconds after the cable is
out. Needs linux-omarchy-mobile#233: without it, power off restarts.

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

* NOTES: power off restarted the 7 Pro (the PMIC's WTSR), and the charger boot

On a second 7 Pro, not the reference phone.

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

* omamobile-device-cheetah 0.1.55: power off at a critical battery

upower's default critical action is a suspend; suspended at 2 % the phone
runs flat asleep within about 20 minutes, a brown-out with the root file
system mounted. Power off now works (linux-omarchy-mobile#233, in
kernel-2026.11.13, on the development channel), and an off phone on a
charger starts the dark charging boot (#554's charger target, carried in
this pull request). So the drop-in of SUSPEND-PLAN 6.6: PowerOff at 3 %.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Hiroyuki Ikegami <ikegam@mixallow.net>
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