Skip to content

omamobile-audio 0.5.15, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) - #401

Merged
derekross merged 6 commits into
derekross:mainfrom
robotosaith:omamobile-raven-speakers-v2
Nov 5, 2026
Merged

derekross merged 6 commits into
derekross:mainfrom
robotosaith:omamobile-raven-speakers-v2

Conversation

@robotosaith

@robotosaith robotosaith commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Stacked on #400 (its first two commits); this PR's own change is the last two. AUDIO-PLAN R6 measured raven's own speaker limits on 2026-10-27: at stage media (737/10) the protection firmware's coil estimate is sane on both speakers and verify passes; it holds to about +9.5 dB and breaks at +10 dB, as on cheetah. So raven runs cheetah's stage media under protection: omamobile-speaker-protection.service now also starts on gs101's AoC (175d0000), and device-raven enables it in place of the microphones-only unit (the two conflict), with no stage of its own. Louder levels stay gated as on cheetah; raven's boost peak current (stock's 1.70/1.90 A) is a separate kernel change.

Device and build

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes
  • tests/packages passes (or the packages I touched: omamobile-audio, omamobile-device-raven; omamobile-audio's "alsa-lib control access" fails on this laptop only, a Homebrew alsa-lib that can't open the laptop's own card)
  • 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; any AI help is a Co-Authored-By: or Assisted-by: trailer, never a Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed (plan, step, result): AUDIO-PLAN R6 (2026-10-27): C9a at stage media passed with verify, stepping up to 757/17 sane, 817/10 and 777/17 misread; 2026-11-03 on this build: factory calibration read from persist and read back from both DSPs, both amplifiers running the protection firmware, a -20 dBFS tone heard from both speakers, coils at 23.0 C, the watchdog within 737/10.
  • What I did not test: a reboot with these packages installed fresh (on the phone protection was started for the boot, with the unit's new AoC condition as a runtime drop-in), music at stage media for long, and anything above stage media.
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)
tools/phone-smoke report

phone-smoke: raven

Kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at 0d328a02, 2026-11-03T14:31Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, slot b, up 3419s
storage guard (required) ok 49 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 405 error lines in dmesg (0 known, 405 new)
new dmesg errors not ok cpif: mif_gpio_get_value: GET GPIO N is not valid x207; cpif: rx_demux: PCIE: ERR! N is not opened x66; cpif: pass_skb_to_demux: PCIE: N<N: ERR! N>recv_skb fail (N) x66
systemd units not ok failed: omamobile-bt-addr@hci0:11.service
USB gadget (required) ok bound to 11110000.usb
display ok card1-DSI-1 connected, 1440x3120
GPU ok render node on panfrost
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok s6sy761
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 89% Discharging, 22 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 47 °C

Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.1-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.14-1, omamobile-device-raven 0.1.31-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.2-1, omamobile-modem 0.1.14-1, omamobile-modem-sit 0.3.30-1, omamobile-omarchy 0.1.31-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.94-1, omamobile-voice 0.1.0-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

The smoke report's CPIF lines are the unpublished modem driver's (an optional GPIO raven's DT doesn't name, a channel nobody had open yet), and omamobile-bt-addr@hci0 failed once on that boot while Bluetooth came up (#77).

🤖 Generated with Claude Code

@robotosaith robotosaith changed the title omamobile-audio 0.5.12, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) omamobile-audio 0.5.15, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) Nov 3, 2026
robotosaith and others added 2 commits November 3, 2026 16:40
The AoC sound card waits for both CS35L41 amplifiers as codecs, so
while their driver stays blacklisted (no validated speaker limits, as on
raven, or protection not yet enabled) there are no microphones either.
omamobile-speaker-protection mics loads the driver and mutes both
amplifiers, as start does before anything else, and stops there: no DSP
firmware, no unmute, the same hang marker. omamobile-audio-mics.service
runs it; this package enables nothing, a device package does. The unit
conflicts with speaker protection and doesn't run once that is enabled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Enables omamobile-audio-mics.service (omamobile-audio 0.5.14), so raven's
microphones work while speaker protection stays off. Checked on raven
after a reboot: the card up, both amplifiers at Digital PCM Volume 0,
the microphone at -64.5 dBFS in a quiet room and -48 to -56 dBFS with
speech. AUDIO-PLAN has the run; the matrix row says microphones only.

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

Copy link
Copy Markdown
Owner

Thank you for R6. Measuring raven's own limits instead of borrowing cheetah's is exactly what I hoped for, and the step-up table makes the +10 dB break easy to see. Running stage media under protection on raven follows from it, and cheetah's stage values are untouched here.

Two things before I merge:

  1. Stage c9 can still be chosen on raven. resolve_stage picks c9 when aoc_alsa_dev speaker_protection is on and c9_source passes. c9_source accepts this phone's own verify stamp without looking at which phone it is, and c9 then runs at 817 with analog 14/11, which R6 shows the firmware misreads on raven. device-raven doesn't set the parameter, so a fresh raven stays at media. But your phone has both the stamp (R6's verify) and the bring-up speaker_protection=1 file, so with this package it would boot into c9 at those levels unless your local speaker.conf overrides them. Could you make c9 refuse on any system without c9 levels of its own (today, anything but cheetah)? Or give raven c9 ceilings at or below R6's last sane step? Either way, a test with SYSTEM=raven, the parameter on and a matching stamp would pin it.
  2. A boot of this build. Since this turns the speakers on at every boot, I'd like one reboot on 0.5.15 and 0.1.32 as installed, without the runtime drop-in. Please send the two units' status, omamobile-speaker-protection status (the stage and the boost line), and a smoke report from that boot; the report in the description is omamobile-audio 0.5.14, device-raven 0.1.31: raven's microphones without speaker protection #400's.

Smaller things:

  • device-raven's new test greps SPEAKER_STAGE in a vendor/omamobile/speaker.conf that doesn't exist (the variable is OMAMOBILE_SPK_STAGE), so it can't fail. A check that raven's modprobe.d never sets speaker_protection would guard what actually matters.
  • The protection unit still says "cheetah only: raven's amplifiers aren't validated" just above the line that now enables raven, and device-raven's README still lists the microphones unit as enabled.
  • Please make device-raven depend on omamobile-audio>=0.5.15. With an older audio package the protection unit skips raven, and with the mics unit gone the phone would have no sound.
  • Does raven's kernel have the boost_en parameter? At media the boost converter should be off, and with stock running raven's speakers at a lower boost peak current than mainline, I'd like to know which way it is.
  • With omamobile-modem 0.1.22, omamobile-modem-sit 0.3.35, device-raven 0.1.36: the modem runtime on the Pixel 6 Pro #389 in, a call on raven will put the top amplifier into earpiece mode at cheetah's 657/6. Is raven's top amplifier the earpiece too? I'd run the earpiece check from cheetah's AOC-PLAN C9k on raven before the first call, or keep earpiece mode off there for now.

On merging: once #400 is squashed this one conflicts on the version files, so I'll either merge this alone (it carries #400) or ask you for a rebase; I'll say which when we get there.

robotosaith and others added 3 commits November 4, 2026 07:23
…rophones

Review on derekross#400:
- device-raven depends on omamobile-audio>=0.5.14 and blacklists
  snd_soc_cs35l41_spi itself, so a raven that updates gets the unit its
  wants link names, and the amplifier driver never autoloads unmuted
  whatever the audio package ships; mics and start still modprobe it.
- mics waits for udev to settle (alsa-utils' restore runs when the card
  appears) before it mutes, then reads both amplifiers again a second
  later and fails, muting again, if either isn't at 0.
- The unit also stands down when protection is enabled by a /usr/lib
  wants link (a device package, as derekross#401 does), and is ordered before
  protection, so its mute on stop ends before protection starts.
- mics() moved above the "Read-only report" comment that belongs to
  status(); device-raven's README names omamobile-audio 0.5.14.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stock's gains match cheetah's; its speaker-path boost peak doesn't (1.7 /
1.9 A against our 3.5 A, fixed in omamobile-gs101-audio). C9a passed at
stage media. Stepping up, the protection firmware read sanely up to
about +9.5 dB and misread from +10 dB; 737/17 (+7 dB) held through a
music run and is the human's local daily level.

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

R6 (AUDIO-PLAN) measured raven's own limits: at stage media (737/10)
the protection firmware's coil estimate is sane on both speakers,
verify passes, and it holds to about +9.5 dB before breaking at +10 dB,
as on cheetah. So raven can run cheetah's stage media under protection.

omamobile-speaker-protection.service only started on gs201's AoC
(181d0000); it now also starts on gs101's (175d0000), as the
microphones unit already does. device-raven enables it in place of the
microphones-only unit (the two conflict), and sets no stage of its own:
the package default, stage media. Checked on raven 2026-11-03: the
factory calibration read from persist and read back from both DSPs,
both amplifiers running the protection firmware, a -20 dBFS tone heard
from both speakers, coils at 23.0 C.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith
robotosaith force-pushed the omamobile-raven-speakers-v2 branch from 469fc8b to f6730ea Compare November 4, 2026 07:39
@robotosaith

Copy link
Copy Markdown
Contributor Author

Thanks for reading R6 so closely. All in the rebased head (f6730ea, on #400's fixes):

  1. c9 on raven: c9_source now refuses on any system outside C9_SYSTEMS (today cheetah) before it looks at a stamp or the list, so neither auto nor an explicit OMAMOBILE_SPK_STAGE=c9 can reach 817/14/11 on raven. The tests use SYSTEM=raven with the parameter on and a stamp for raven's own firmware: auto stays at media 737/10, and c9 is refused with "no levels measured for raven". (This phone has no speaker_protection file since the reinstall, but the guard doesn't depend on that.)
  2. A boot of this build: omamobile-audio 0.5.15 and device-raven 0.1.32 built from this head and installed, the old 10-raven-aoc.conf drop-in removed, one reboot on 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf:
units and status
● omamobile-speaker-protection.service: active (exited)
  omamobile-speaker: boost converter on (kernel without boost_en)
  omamobile-speaker: factory calibration read from persist (read-only): both records valid
  omamobile-speaker: calibration written to both DSPs and read back
  omamobile-speaker: speaker protection on (stage media): both amplifiers through the DSP, digital/analog Top 737/10, Bottom 737/10
● omamobile-speaker-watch.service: active (running)
  watchdog: ceilings digital 737 analog {'Top': 10, 'Bottom': 10}, heartbeat enforced, coil temperature backstop 80 C
○ omamobile-audio-mics.service: inactive (disabled)
aoc_alsa_dev speaker_protection: N

$ omamobile-speaker-protection status
ok: stage media, protection firmware with factory calibration, PCM Source DSP, held awake, digital/analog Top 737/10, Bottom 737/10, boost converter on (kernel without boost_en)
firmware raven <digest>: not in the verified firmware list
mode: speaker (the watchdog enforces: speaker)
Top (spi12.0): PCM Source DSP, Digital 737 (max 817), Analog 10 (max 10), DRE on, DSP1 Firmware Protection; calibration in the DSP vs persist: match
Bottom (spi12.1): PCM Source DSP, Digital 737 (max 817), Analog 10 (max 10), DRE on, DSP1 Firmware Protection; calibration in the DSP vs persist: match
phone-smoke

phone-smoke: raven

Kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at f6730eaa, 2026-11-04T07:36Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, slot b, up 90s
storage guard (required) ok 49 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 329 error lines in dmesg (50 known, of them ASoC no backend DAIs (PipeWire probe) x1, 279 new)
new dmesg errors not ok wc-mbox N: Try increasing MBOX_TX_QUEUE_LEN x243; Bluetooth: N: command N tx timeout x8; Bluetooth: N: Failed to set baudrate x4
systemd units not ok failed: omamobile-modem.service
USB gadget (required) ok bound to 11110000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panfrost
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked true)
touch ok s6sy761
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered unknown
battery ok 87% Discharging, 22 °C
sound cards ok googleaocsndcar
sensors ok AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 44 °C

Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.1-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.15-1, omamobile-device-raven 0.1.32-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.2-1, omamobile-modem 0.1.14-1, omamobile-modem-sit 0.3.30-1, omamobile-omarchy 0.1.31-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.94-1, omamobile-voice 0.1.0-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

The smoke report's three flags aren't from this PR. MBOX_TX_QUEUE_LEN x243 is one burst within a second, 10 s after protection starts, while PipeWire probes the new card's PCMs; it doesn't grow, and R6's boot had the same burst (122). The Bluetooth lines are the silent chip on the daily kernel (#395, B4). omamobile-modem refused because of the latch from the previous boot's reboot.

Smaller things:

  • device-raven's test now checks that its modprobe.d never sets speaker_protection, along with the wants link, the blacklist and the dependency; the SPEAKER_STAGE grep is gone.
  • The unit's "cheetah only" comment and device-raven's README are updated.
  • device-raven depends on omamobile-audio>=0.5.15.
  • boost_en: raven's kernel doesn't have it (modinfo lists no parameters for snd_soc_cs35l41, and the script logs "boost converter on (kernel without boost_en)"), so at media raven runs with the boost converter on at the mainline peak current. Since raven's own limits were measured that way, I kept it, but it isn't stock's lower peak.
  • Earpiece: until C9k has run on raven, earpiece on is refused there (EAR_SYSTEMS, tested with SYSTEM=raven), and off still works. modem-sit's [audio] card defaults to none, so a call on raven routes no audio unless someone sets it.

On merging: this head now carries #400's review fixes too, so merging this alone works.

@derekross

Copy link
Copy Markdown
Owner

Thank you, both points are in, and I checked them in the code and the tests. c9 now stops on the system before it looks at a stamp or the list, and your SYSTEM=raven tests pin both auto and an explicit c9. The earpiece gate refuses on and writes nothing, which with #416's defaults means a call on raven stays silent rather than guessing. The boot report is what I hoped for: stage media at 737/10 on both, the calibration read back, the watchdog's ceilings at 737/10 and the microphones unit out of the way. Thanks also for the boost_en answer. Since R6 says 3.50 A is stock raven's own default outside the speaker path, I'm fine with it as it is.

Merging plan: this carries #400, so I'll merge this one on its own and close #400. #395 goes in first, and I'll resolve the raven DEVICES row by hand (the two PRs touch different cells). If #389 lands before this, device-raven's test/all and version will conflict; keep both test blocks and take the next number, or leave it to me.

One small thing, also in #400: the new README row has three cells in a two-column table. Moving omamobile-raven.conf into the second cell fixes the rendering. And an optional one: SYSTEM falls back to cheetah when it finds no amplifier node. That's harmless on raven today, but a fallback that isn't a real phone would keep the new gates from depending on it.

@derekross
derekross merged commit f8b2a20 into derekross:main Nov 5, 2026
2 checks passed
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 10, 2026
…s after today's main

main has moved past this branch's numbers (omamobile-modem 0.1.17,
modem-sit 0.3.33 and device-raven 0.1.33 have shipped), so the three
packages take the next ones. Raven's MODEM-PLAN section 11 names the
modem's crash notice by the release this lands in, as it already does
for modem-sit's, rather than by a number that moves.

device-raven's test/all keeps both the speaker-protection block from
derekross#401 and this branch's sitd/sit-data drop-in block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 11, 2026
…s after today's main

main has moved past this branch's numbers (omamobile-modem 0.1.20,
modem-sit 0.3.34 and device-raven 0.1.34 have shipped), so the three
packages take the next ones. Raven's MODEM-PLAN section 11 names the
modem's crash notice by the release this lands in, as it already does
for modem-sit's, rather than by a number that moves.

device-raven's test/all keeps both the speaker-protection block from
derekross#401 and this branch's sitd/sit-data drop-in block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith
robotosaith deleted the omamobile-raven-speakers-v2 branch November 12, 2026 17:18
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… protection at stage media (derekross#401)

Raven's speakers and microphones, through speaker protection at the
package's stage media (737/10). AUDIO-PLAN R6 measured raven's own
limits: at stage media the protection firmware's coil estimate is sane
on both speakers and verify passes, holding to about +9.5 dB before it
misreads from +10 dB, as on cheetah.

- omamobile-audio 0.5.15: `omamobile-speaker-protection mics` loads the
  CS35L41 driver and mutes both amplifiers (after udev settles, read
  back a second later), for a phone whose speakers aren't validated;
  protection also starts on gs101's AoC; stage c9 is refused on any
  system but cheetah, before any stamp or list is read, and earpiece
  mode is refused on raven (tests with SYSTEM=raven).
- device-raven 0.1.32: enables speaker protection in place of the
  microphones-only unit, depends on omamobile-audio>=0.5.15 and
  blacklists snd_soc_cs35l41_spi itself, so an updated raven never
  autoloads the amplifier driver unmuted.

Checked on raven: the factory calibration read back from both DSPs,
both amplifiers on the protection firmware at 737/10, a -20 dBFS tone
from both speakers, the watchdog at the media ceilings. Includes derekross#400.
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