Repository navigation
omamobile-audio 0.5.15, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) - #401
Conversation
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>
e906d63 to
469fc8b
Compare
|
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:
Smaller things:
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. |
…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>
469fc8b to
f6730ea
Compare
|
Thanks for reading R6 so closely. All in the rebased head (f6730ea, on #400's fixes):
units and statusphone-smokephone-smoke: ravenKernel
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. Smaller things:
On merging: this head now carries #400's review fixes too, so merging this alone works. |
…th this PR's speakers cell)
|
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 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 One small thing, also in #400: the new README row has three cells in a two-column table. Moving |
…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>
…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>
… 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.
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
verifypasses; 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.servicenow 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
uname -r): 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf (raven's integration kernel; the AoC isn't published yet)Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpassestests/packagespasses (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)versionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
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.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)tools/phone-smokereportphone-smoke: raven
Kernel
7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at0d328a02, 2026-11-03T14:31Z.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@hci0failed once on that boot while Bluetooth came up (#77).🤖 Generated with Claude Code