Repository navigation
omamobile-audio 0.5.14, device-raven 0.1.31: raven's microphones without speaker protection - #400
robotosaith wants to merge 3 commits into
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>
d59b9f9 to
cc44003
Compare
|
Thank you for this. Getting raven's microphones back without touching the speakers is the right first step, and it also fixes something I didn't know about: on today's raven image the amplifier driver autoloads with nothing muting it. I read the new One thing before I merge, and one question:
Small things, fine in the same push:
On versions: device-raven 0.1.31 is also used by #403 and a few of the 9a modem PRs. Whichever merges second will get the next free number at merge, so no need to change anything now. |
…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>
|
Thanks for the close read, and for catching the unmuted autoload on today's image. All in 507f17a:
The small ones are in too: a second Thanks for taking care of the version numbers at merge. |
|
Thank you, every point is in, and I checked each against the diff. The dependency and raven's own blacklist mean an updated phone gets both the unit and the guard. The settle-then-recheck closes the restore window, and since Since #401 carries this head and moves raven on to protection, my plan is to merge #401 on its own and close this one with a note, so the history lands once. One nit that #401 shares: the new row in device-raven's README has three cells in a two-column table, so GitHub renders it oddly. Putting |
… protection at stage media (#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 #400.
|
Merged as part of #401 (squash commit on main), which carried this head unchanged together with raven's speakers through protection. Thank you! |
… 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
On main a fresh raven has no microphones:
omamobile-audioisn't in its image, and without speaker protection nothing loads the CS35L41 driver, while the AoC card waits for both amplifiers as codecs.omamobile-speaker-protection micsloads the driver and mutes both amplifiers, nothing more;omamobile-audio-mics.serviceruns it on gs201 or gs101, and stands down once protection is enabled. device-raven enables it and putsomamobile-audioin raven's image, whose blacklist also stops the driver loading on its own (on today's fresh install it did, unprotected). Speakers stay muted here; the next PR turns them on.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
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