Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions device/raven/AUDIO-PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -423,3 +423,20 @@ clash Derek pointed out. Ways forward, not decided: give the card a
speaker-less link set when the amplifiers are absent, or load the
amplifier driver muted with no protection firmware, so the card and the
microphones come up while the speakers stay off.

**Microphones without protection (2026-10-27, `gb3d6253b0d61`,
omamobile-audio 0.5.3, device-raven 0.1.25; branch
`omamobile-raven-mics`):** the second way. `omamobile-speaker-protection
mics` (run by `omamobile-audio-mics.service`, which device-raven enables)
loads `snd_soc_cs35l41_spi` and mutes both amplifiers, as `start` does
before anything else, and stops there: no DSP firmware, no unmute. The
unit doesn't run once speaker protection is enabled, and uses the same
hang marker. On raven, after a reboot: the unit finished at 12:01:45, the
card came up, both amplifiers read `Digital PCM Volume` 0, speaker
protection inactive, and PipeWire's default source was "Built-in Audio
Microphone". A 4 s recording in a quiet room read -64.5 dBFS RMS (not
digital silence); with the human counting out loud, -48 to -56 dBFS per
half second, falling to about -71 dBFS between words. So the microphones
work with the speakers muted. Not tested: a call (the modem doesn't start
at boot with this package set), and the speaker sink, which PipeWire still
lists but which plays into muted amplifiers.
10 changes: 6 additions & 4 deletions device/raven/device.conf
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,12 @@ SOC=gs101
COMPATIBLE="google,gs101-raven"
PACKAGE=omamobile-device-raven
# This phone's other packages in the root image, on top of the shared
# rootfs/packages.omamobile: the sensors through the AoC, and GNSS (off
# until `omamobile-gnss on`). Audio waits on the amplifiers' limits, the
# modem on its kernel.
ROOTFS_PACKAGES="omamobile-sensors omamobile-gnss"
# rootfs/packages.omamobile: the sensors through the AoC, GNSS (off until
# `omamobile-gnss on`), and the audio package for the microphones (its
# blacklist keeps the amplifiers' driver from loading on its own; device-
# raven's omamobile-audio-mics loads it muted). Speaker protection stays
# off until raven's limits are in a package; the modem waits on its kernel.
ROOTFS_PACKAGES="omamobile-sensors omamobile-gnss omamobile-audio"

# --- Kernel and device tree ---
DTB=exynos/google/gs101-raven.dtb
Expand Down
2 changes: 1 addition & 1 deletion docs/DEVICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Pixel 7 Pro | cheetah | gs201 (Tensor G2) | works | works | works (120 Hz) | works (DVFS) | works | works | works | works | works (audio) | works | works | works | works | works | works | works | works | works (calls, texts and mobile data on a Verizon-network SIM, 2026-11-03; see below) | works | works (telephoto fixed-focus) | WIP | works |
| Pixel Fold | felix | gs201 (Tensor G2) | WIP ([#3](https://github.com/derekross/omarchy-mobile/issues/3)) | WIP (UFS behind the read-only guard, checked on the phone) | WIP (cover: simplefb console; inner: simpledrm output listed by Hyprland, its splash reserved by [kernel #72](https://github.com/derekross/linux-omarchy-mobile/pull/72); both panels' display triggers set by the descriptor, [#82](https://github.com/derekross/omarchy-mobile/pull/82)) | testing (Panthor; glmark2 on the cover, not up on every image yet; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | WIP (cover: chip id read, no touches yet; the driver's touch reports are merged, [kernel #48](https://github.com/derekross/linux-omarchy-mobile/pull/48), untested on the Fold; [notes](../device/felix/NOTES.md#2026-10-23-cover-touch-id)) | works (volume and power; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | works | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no |
| Pixel 6 Pro ([notes](../device/raven/NOTES.md)) | raven | gs101 (Tensor) | works ([#2](https://github.com/derekross/omarchy-mobile/issues/2)) | works | works (120 Hz through gs-decon and the S6E3HC3 driver; unpublished kernel, `omamobile-gs101-display`, in review as [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116), [plan](../device/raven/DISPLAY-PLAN.md)); the published kernel has the boot console only | partial (Panfrost; DVFS on an unpublished kernel, [plan](../device/raven/GPU-PLAN.md)) | works ([kernel #8](https://github.com/derekross/linux-omarchy-mobile/pull/8)) | works | works (a NOT FOR MERGE DT change; [plan](../device/raven/USB-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-wifi`; [plan](../device/raven/WIFI-PLAN.md)) | partial ([kernel #6](https://github.com/derekross/linux-omarchy-mobile/pull/6); own address; pairing untested; start-up after a warm reboot is [#77](https://github.com/derekross/omarchy-mobile/issues/77)) | works (the gauge; unpublished kernel) | works (the MAX77759 charger at stock's limits with its temperature guard, loaded at boot by device-raven 0.1.26; a full charge to 100 %; the battery node is in the published kernel, [kernel #112](https://github.com/derekross/linux-omarchy-mobile/pull/112), tested on an unpublished kernel; [plan](../device/raven/USB-PLAN.md#4-charging-the-max77759-charger-ravens-b3-after-cheetahs)) | works (CS40L25A through feedbackd, device-raven 0.1.27, with the phone's own firmware from `tools/extract-vendor-firmware -d raven`; the driver and node are merged, [kernel #114](https://github.com/derekross/linux-omarchy-mobile/pull/114); [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (tested on `omamobile-gs101-torch`; the LED's node is now in the published kernel, [kernel #113](https://github.com/derekross/linux-omarchy-mobile/pull/113), not yet run from it; [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-gnss`; [plan](../device/raven/GNSS-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md)) | no (the amplifiers stay off until raven's own limits are validated, and without them the card doesn't probe, so no mics either; [plan](../device/raven/AUDIO-PLAN.md#without-the-amplifiers-2026-10-27-gb3d6253b0d61-device-raven-0123)) | works (accelerometer, light, proximity, compass through the AoC; unpublished kernel) | WIP (calls, texts and data on an unpublished kernel, `omamobile-gs101-cpif`; the package doesn't enable it; [plan](../device/raven/MODEM-PLAN.md)) | no | no | no | no |
| Pixel 6 Pro ([notes](../device/raven/NOTES.md)) | raven | gs101 (Tensor) | works ([#2](https://github.com/derekross/omarchy-mobile/issues/2)) | works | works (120 Hz through gs-decon and the S6E3HC3 driver; unpublished kernel, `omamobile-gs101-display`, in review as [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116), [plan](../device/raven/DISPLAY-PLAN.md)); the published kernel has the boot console only | partial (Panfrost; DVFS on an unpublished kernel, [plan](../device/raven/GPU-PLAN.md)) | works ([kernel #8](https://github.com/derekross/linux-omarchy-mobile/pull/8)) | works | works (a NOT FOR MERGE DT change; [plan](../device/raven/USB-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-wifi`; [plan](../device/raven/WIFI-PLAN.md)) | partial ([kernel #6](https://github.com/derekross/linux-omarchy-mobile/pull/6); own address; pairing untested; start-up after a warm reboot is [#77](https://github.com/derekross/omarchy-mobile/issues/77)) | works (the gauge; unpublished kernel) | works (the MAX77759 charger at stock's limits with its temperature guard, loaded at boot by device-raven 0.1.26; a full charge to 100 %; the battery node is in the published kernel, [kernel #112](https://github.com/derekross/linux-omarchy-mobile/pull/112), tested on an unpublished kernel; [plan](../device/raven/USB-PLAN.md#4-charging-the-max77759-charger-ravens-b3-after-cheetahs)) | works (CS40L25A through feedbackd, device-raven 0.1.27, with the phone's own firmware from `tools/extract-vendor-firmware -d raven`; the driver and node are merged, [kernel #114](https://github.com/derekross/linux-omarchy-mobile/pull/114); [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (tested on `omamobile-gs101-torch`; the LED's node is now in the published kernel, [kernel #113](https://github.com/derekross/linux-omarchy-mobile/pull/113), not yet run from it; [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-gnss`; [plan](../device/raven/GNSS-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md)) | partial (microphones only, speakers muted until raven's own limits are validated; unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md#without-the-amplifiers-2026-10-27-gb3d6253b0d61-device-raven-0123)) | works (accelerometer, light, proximity, compass through the AoC; unpublished kernel) | WIP (calls, texts and data on an unpublished kernel, `omamobile-gs101-cpif`; the package doesn't enable it; [plan](../device/raven/MODEM-PLAN.md)) | no | no | no | no |
| Pixel 7a ([notes](../device/lynx/NOTES.md)) | lynx | gs201 (Tensor G2) | WIP ([#36](https://github.com/derekross/omarchy-mobile/issues/36): Arch root on `userdata` from slot B, SSH; the device package marks the slot successful) | WIP (UFS behind the read-only guard, in the published kernel, [kernel #91](https://github.com/derekross/linux-omarchy-mobile/pull/91); [notes](../device/lynx/NOTES.md#2026-10-24-on-screen-console-and-ufs)) | WIP (simpledrm console only, [notes](../device/lynx/NOTES.md)) | no | WIP (GT9895 touches in the session, in the published kernel, [kernel #93](https://github.com/derekross/linux-omarchy-mobile/pull/93); [notes](../device/lynx/NOTES.md#2026-10-24-touchscreen-rtc-and-slot-retries)) | no | works | no (parked at the chip's boot ROM; [plan](../device/lynx/WIFI-PLAN.md)) | WIP (same chip as Wi-Fi; scans through its own UART; the device tree is in review, [kernel #98](https://github.com/derekross/linux-omarchy-mobile/pull/98), and the package side, [#98](https://github.com/derekross/omarchy-mobile/pull/98); [plan](../device/lynx/WIFI-PLAN.md)) | no | no | no | no | no | no | no | no | no | no | no | no | no |
| Pixel 6 | oriole | gs101 (Tensor G1) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); native test image on one phone; slot B marked successful and `vbmeta_b` verification turned off, both without project approval; see notes) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); guarded `userdata` root on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); connected output on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); Panfrost render node present) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); touchscreen detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); gpio-keys detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); USB network and SSH on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); link up; traffic not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); controller powered; pairing not checked) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charge and temperature reported) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no |
| Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - |
Expand Down
1 change: 1 addition & 0 deletions packages/omamobile-audio/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ protection firmware and the phone's factory calibration, as stock Android does.
| File | What |
|---|---|
| `omamobile-speaker-protection` + `.service` (system, **not enabled by the package**) | loads the amplifier driver (or, when it is already bound, rebinds both amplifiers: a chip reset, so `systemctl restart` recovers a stuck DSP), mutes both at once, holds them out of runtime suspend (hibernation breaks the stock firmware), checks the kernel's volume limits, the stage's ceilings, the firmware and the factory calibration (`persist:/audio/speaker.cal` via debugfs, read-only), loads the protection firmware, writes `CAL_*` into both DSPs and reads it back, routes the DAC through the DSP, checks health (held awake, DSP controls present, no amplifier error in the kernel log), and only then unmutes. Any failure leaves both muted; a hang marker keeps the driver alone on the next boot. `status`, `health`, `monitor` and `verify` read the DSPs' state (coil temperature, CSPL state and errors, heartbeat), never the calibration values; `impedance` (during playback) reads the coil impedance the firmware measures, as a ratio to the factory value; `feedback start|stop|status` runs the amplifiers' VMON/IMON stream to the AoC as stock does (AOC-PLAN C9d-7); `mute` mutes |
| `omamobile-audio-mics.service` (system, **not enabled by the package**) | the microphones without speaker protection: `omamobile-speaker-protection mics` loads the amplifier driver (the card waits for both amplifiers as codecs, so without it there are no microphones either) and mutes both, with no DSP firmware and no unmute, so the speakers stay silent. For a phone whose speaker limits aren't validated; a device package enables it (omamobile-device-raven). It doesn't run once `omamobile-speaker-protection` is enabled, which then owns the amplifiers; same hang marker |
| `omamobile-speaker-watch.service` | started with it and bound to it: mutes both amplifiers on an amplifier error in the kernel log (CSPL error, failed wake, failed resume), an amplifier no longer held awake, a level above the ceilings, or, during playback, a DSP not running the protection firmware with the calibration applied, a coil estimate above 80 C, or (stage c9 only, the stage whose analog ceiling is above 10; since 0.5.3) one that rises more than 5 C within a stream; mutes too when it stops. Writes stock's media delta at stream start; with `OMAMOBILE_SPK_FEEDBACK=1` runs the V/I feedback stream with every speaker stream |
| `udev.rules` | holds the amplifiers awake from the moment the driver binds |
| `verified-firmware` (`/usr/share/omamobile-audio/`, 0.5.10) | the speaker protection firmware verified on the reference phone: one `SYSTEM DIGEST NOTE` line per firmware, the digest over Google's protection firmware and both tunings that a C9a stamp records (`omamobile-speaker-protection digest` prints the installed one as such a line). Stage auto runs c9 on a phone with `speaker_protection=1` when **this phone's own stamp** matches the firmware, or when the firmware's digest is **in this list**, so a fresh install (the stamp lives on `userdata` and is lost on every install) gets the louder levels too; media otherwise. The start logs which ("stage c9 chosen by the verified firmware list" or "by this phone's stamp"), and so does `status`. A listed digest means the same files byte for byte, not the same phone: on c9 from the list the watchdog checks this phone at its first speaker stream after each start, about 3 s in (CSPL_ENABLE 1 on both, the model on the resistance written from this phone's persist, the heartbeat moving, both coil estimates within 10-65 C); c9 from the list is capped at the levels verified with music (817, analog top 11, bottom 14: a configured level above is lowered, with a log line, and the watchdog holds the same ceilings; 17 needs this phone's own stamp). A failure mutes, records the firmware in `/var/lib/omamobile/speaker-protection-c9-refused` (a coil estimate out of the band alone, or a `/var/lib` that can't be written: in `/run/omamobile/` for this boot only; if neither can be written it stays muted, without a restart) and restarts the service, which then picks media. The list's path and the check's band are fixed outside the tests. The phone's own stamp (an attended `verify`) wins over a refusal. It lists the reference phone's firmware from factory image cp2a.260705.006 (C9a verify 2026-11-02; AOC-PLAN, "C9 for every phone with verified firmware") |
Expand Down
Loading