Repository navigation
omamobile-audio 0.5.13: the earpiece works at the louder stage, with the boost converter on - #402
Conversation
…the boost converter on `omamobile-speaker-protection earpiece on` refused whenever the last start had left the amplifiers' boost converter on, unless OMAMOBILE_SPK_BOOST=1 asked for it, because C9j found the converter distorting in its light-load regime at analog 10 and below. The converter is a module-wide parameter set when the amplifiers probe, and stage c9 (the louder default on verified firmware since 0.5.8: digital 817, analog 11/14) leaves it on, so every call on such a phone was refused earpiece audio, and the owner had to run the speakers at stage media for calls (the DEVICES matrix said "the louder stage and the earpiece exclude each other for now"). C9j's finding was under music on the speakers and doesn't apply to the voice path. On 2026-11-03 the owner ran the earpiece at 657/6 with the boost on at stage c9 (OMAMOBILE_SPK_BOOST=1, earpiece on through omamobile-earpiece@on.service: Top 657/6 through ASP, the bottom muted) on a VoLTE call and found it clean: no static, no hum. Stock's own handset path also runs the top amplifier with the boost on (mixer_paths.xml handset: analog 7). So `earpiece on` now takes the converter as the last start left it, in every stage, and records its state in the status line, as before. No other refusal changes, and OMAMOBILE_SPK_BOOST keeps its meaning for the start (the speakers): earpiece mode no longer reads it at all, so OMAMOBILE_SPK_BOOST=1 with the converter off is no longer refused either. The tests expect the acceptance now, at stage media with the converter forced on and at stage c9 against a live watchdog, with `off` restoring the stage's levels. speaker.conf, the README, AOC-PLAN C9j/C9k (a dated note) and the DEVICES matrix say the earpiece works at every stage. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
|
Thanks, this is the right fix: the refusal was a quality guard from the speaker measurements, not a safety one, and it was silencing every call on a phone at the louder stage. I read the earpiece path and the watchdog: nothing about the levels, the ceilings, the limits and health checks or the watchdog's earpiece rules changes, and |
…the boost converter on (derekross#402) `omamobile-speaker-protection earpiece on` refused whenever the last start had left the amplifiers' boost converter on, unless OMAMOBILE_SPK_BOOST=1 asked for it, because C9j found the converter distorting in its light-load regime at analog 10 and below. The converter is a module-wide parameter set when the amplifiers probe, and stage c9 (the louder default on verified firmware since 0.5.8: digital 817, analog 11/14) leaves it on, so every call on such a phone was refused earpiece audio, and the owner had to run the speakers at stage media for calls (the DEVICES matrix said "the louder stage and the earpiece exclude each other for now"). C9j's finding was under music on the speakers and doesn't apply to the voice path. On 2026-11-03 the owner ran the earpiece at 657/6 with the boost on at stage c9 (OMAMOBILE_SPK_BOOST=1, earpiece on through omamobile-earpiece@on.service: Top 657/6 through ASP, the bottom muted) on a VoLTE call and found it clean: no static, no hum. Stock's own handset path also runs the top amplifier with the boost on (mixer_paths.xml handset: analog 7). So `earpiece on` now takes the converter as the last start left it, in every stage, and records its state in the status line, as before. No other refusal changes, and OMAMOBILE_SPK_BOOST keeps its meaning for the start (the speakers): earpiece mode no longer reads it at all, so OMAMOBILE_SPK_BOOST=1 with the converter off is no longer refused either. The tests expect the acceptance now, at stage media with the converter forced on and at stage c9 against a live watchdog, with `off` restoring the stage's levels. speaker.conf, the README, AOC-PLAN C9j/C9k (a dated note) and the DEVICES matrix say the earpiece works at every stage. Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
What
omamobile-speaker-protection earpiece onrefused whenever the last start had left the amplifiers' boost converter on ("the earpiece (analog 6) needs the boost converter off (AOC-PLAN C9j)"), unlessOMAMOBILE_SPK_BOOST=1asked for it. The converter is a module-wide parameter set when the amplifiers probe, and stage c9 (the louder default on verified firmware since 0.5.8: digital 817, analog 11/14) leaves it on, so every call on such a phone was refused earpiece audio, and the maintainer had to run the speakers at stage media for calls.0.5.13 takes the converter as the last start left it, in every stage, and records its state in the status line as before. Nothing else is refused or accepted differently: the level ceilings, the limits check, the health check, the hang marker and the watchdog handshake stay.
OMAMOBILE_SPK_BOOSTkeeps its meaning for the start (the speakers); earpiece mode no longer reads it, soOMAMOBILE_SPK_BOOST=1with the converter off is no longer refused either (it never did anything for the earpiece).Why it is safe
OMAMOBILE_SPK_BOOST=1, earpiece on throughomamobile-earpiece@on.service: Top 657/6 through ASP, the bottom muted) on a VoLTE call: no static, no hum.mixer_paths.xmlhandset: analog 7).omamobile-modem-sit'scheck_levelsalready accepts earpiece mode at any stage (its earpiece ceilings don't read the bottom's analog gain), so call audio at stage c9 needs nothing there.Files
packages/omamobile-audio/bin/omamobile-speaker-protection: the refusal gone, the comments say why.packages/omamobile-audio/speaker.conf,README.md: the earpiece works in every stage;OMAMOBILE_SPK_BOOSTis the start's.packages/omamobile-audio/test/all: the two boost refusals become acceptance (status line says "boost converter on"), plus a stage c9 case against a live watchdog withoffrestoring 817/17.packages/omamobile-audio/version: 0.5.13 (0.5.11 and 0.5.12 are omamobile-audio 0.5.14, device-raven 0.1.31: raven's microphones without speaker protection #400 and omamobile-audio 0.5.15, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) #401).device/cheetah/AOC-PLAN.md: status paragraph, C9j and C9k "Refusals" with the dated 2026-11-03 note.docs/DEVICES.md: the cheetah Modem row no longer says call audio needs stage media.Overlap with #398
docs/release-notes/2026-11-DRAFT.mdon main doesn't mention stage media (git grep -n "stage media"finds nothing there), so this PR leaves it alone. omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: the Pixel 7 Pro's modem stack on by default #398 adds to it: "Call audio through the earpiece needs the speakers at stagemedia(omamobile-speaker-protection): the louder stage and the earpiece exclude each other for now." Once both are in, that sentence is wrong and should go (a one-line follow-up, or omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: the Pixel 7 Pro's modem stack on by default #398 can drop it before it merges).docs/DEVICES.md: omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: the Pixel 7 Pro's modem stack on by default #398 rewrites the same cheetah Modem row (the boot-by-default part) and keeps the "call audio needs the speakers at stagemedia…" sentence in it; this PR replaces only that sentence. Whichever lands second needs a trivial rebase of that row: keep omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: the Pixel 7 Pro's modem stack on by default #398's boot text and this PR's earpiece text.Checks
packages/omamobile-audio/test/alltests/alltools/pr-check origin/mainNo phone was touched; the 2026-11-03 result is the maintainer's own.
🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d