Skip to content

device-panther: the speakers on the default calibration without speaker.cal - #496

Merged
derekross merged 3 commits into
derekross:mainfrom
angelrenefm:panther-speaker-default-cal
Nov 8, 2026
Merged

derekross merged 3 commits into
derekross:mainfrom
angelrenefm:panther-speaker-default-cal

Conversation

@angelrenefm

Copy link
Copy Markdown
Contributor

This turns on #427's OMAMOBILE_SPK_DEFAULT_CAL=1 for the Pixel 7, as you asked in its review. The evidence is your comment there of 2026-11-07 16:13 UTC: a start and a playback on omamobile-audio 0.5.16, installed with pacman -U, on a Pixel 7 without speaker.cal.

How. A drop-in for omamobile-speaker-protection.service in device-panther sets Environment=OMAMOBILE_SPK_DEFAULT_CAL=1.

  • A phone that has speaker.cal still uses it.
  • c9 and verify stay refused on the default calibration.
  • /etc/omamobile/speaker.conf is read after it (EnvironmentFile overrides Environment), so a line there still turns it off.
  • test/all checks the drop-in, and the README has its row.

And the LC_ALL=C you suggested: the one debugfs call whose message is matched ("File not found by ext2_lookup") now runs under it, so a phone in another language can't trip it.

On the phone. Same Pixel 7, with the line taken out of speaker.conf and this drop-in and script in place:

  • systemctl show gives the service the setting;
  • start logs "using the protection firmware's default calibration", stage media at 737/10;
  • /run/omamobile/speaker-protection-calibration reads "default calibration";
  • a playback, and the watchdog stays active.

The packages' tests pass (device-panther 19, omamobile-audio 45), and so does tools/pr-check. I left the versions to you.

Not checked: a Pixel 7 that has speaker.cal with the drop-in on (only covered by #427's test of the setting with a factory start), and a phone running in another language.

I used AI help (Claude) to work on this.

…er.cal

Turns on omamobile-audio 0.5.16's OMAMOBILE_SPK_DEFAULT_CAL=1 for the
Pixel 7, with a drop-in for omamobile-speaker-protection.service: some
units have no speaker.cal in persist, and stock's HAL then runs the
protection firmware on its tuning's default calibration. A phone that has
speaker.cal still uses it, c9 and verify stay refused on the default, and
/etc/omamobile/speaker.conf is read after the drop-in, so a line there
still turns it off.

Evidence: derekross#427, comment of 2026-11-07 16:13 UTC
(a start and a playback on 0.5.16, installed with pacman -U, on a Pixel 7
without speaker.cal). On the same phone with this drop-in and the line
taken out of speaker.conf: the service gets the setting, start logs
"using the protection firmware's default calibration", stage media at
737/10, /run/omamobile/speaker-protection-calibration reads "default
calibration", a playback, and the watchdog stays active.

omamobile-audio: the one debugfs call whose message is matched ("File not
found by ext2_lookup") runs under LC_ALL=C, so a phone in another
language can't trip it (derekross#427's review).

I used AI help (Claude) to work on this.
@derekross

Copy link
Copy Markdown
Owner

Thank you, @angelrenefm. This is exactly the change I asked for on #427, and it's built carefully. The drop-in only flips the opt-in, a phone with speaker.cal keeps using it, a line in speaker.conf still wins (EnvironmentFile overrides Environment=), and c9 and verify stay refused on the default calibration. I also checked that the protection service's own restarts go through the unit, so they get the setting too, and that the watchdog and earpiece units don't need it. Thanks as well for folding in the LC_ALL=C.

I'll take care of the rest at merge: omamobile-audio 0.5.17 and device-panther 0.1.13 (both free today), with a subject that names omamobile-audio too, since this changes it.

Two small things, whenever you next touch the package:

If you get a chance after this lands, a tools/phone-smoke report with both packages installed from main through pacman -U would close it. Thanks again!

@derekross
derekross merged commit 2fa55ca into derekross:main Nov 8, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… on the firmware's default calibration without speaker.cal (derekross#496)

Turns on omamobile-audio's OMAMOBILE_SPK_DEFAULT_CAL=1 for the Pixel 7,
with a drop-in for omamobile-speaker-protection.service: some units have
no speaker.cal in persist, and stock's HAL then runs the protection
firmware on its tuning's default calibration. A phone that has
speaker.cal still uses it, c9 and verify stay refused on the default,
the volume ceilings are unchanged (stage media, 737/10), and
/etc/omamobile/speaker.conf is read after the drop-in, so a line there
still turns it off.

Evidence: derekross#427, the contributor's comment of 2026-11-07 15:33 UTC (a
start and a playback on 0.5.16, installed with pacman -U, on a Pixel 7
without speaker.cal), and with this drop-in: the service gets the
setting, start logs "using the protection firmware's default
calibration", stage media at 737/10, a playback, and the watchdog stays
active.

omamobile-audio: the one debugfs call whose message is matched ("File
not found by ext2_lookup") runs under LC_ALL=C, so a phone in another
language can't trip it.
@angelrenefm

Copy link
Copy Markdown
Contributor Author

The smoke report you asked for, with both packages installed from the repository (built from main: omamobile-audio
0.5.18 and device-panther 0.1.15, upgraded with pacman on 14 Nov). On this boot the protection service runs with
OMAMOBILE_SPK_DEFAULT_CAL=1 from the drop-in, there is no speaker.cal, and it logs "speaker protection on (stage
media): both amplifiers through the DSP".

tools/phone-smoke (main at ad58709), 15 Nov

phone-smoke: unknown

Kernel 7.3.0-rc6-omamobile-push1-g44048a9aa795, tools at unknown, 2026-11-15T13:02Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g44048a9aa795, slot b, up 68032s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 87G free
kernel health (required) ok no oops or BUG; 0 WARN, 0 error lines in dmesg (0 known, 0 new)
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1080x2400
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok FocalTech FT3658
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 90% Discharging, 35 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 53 °C

Packages: hyprland 0.57.0-3.4, libcamera 0.7.2-4.23, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.3-1, omamobile-audio 0.5.18-1, omamobile-device-panther 0.1.15-1, omamobile-firstboot 0.1.5-1, omamobile-gnss 0.2.9-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.41-1, omamobile-owl-widgets 0.1.2-1, omamobile-pixel 0.1.27-1, omamobile-sensors 0.2.1-1, omamobile-settings 0.1.2-1, omamobile-shell 0.2.126-1, omaphone 0.2.3-1, omarchy 4.5.0-3, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

The two smaller points are in #812: the drop-in now cites the 15:33 comment on #427, and an optdepends
line plus a sentence in the README and the drop-in say that with an omamobile-audio older than 0.5.16 the setting does
nothing.

angelrenefm added a commit to angelrenefm/omarchy-mobile that referenced this pull request Nov 17, 2026
…audio

Two follow-ups from derekross#496's review. The drop-in cited the 16:13 comment
on derekross#427; the start and the playback are in the 15:33 one. And
device-panther doesn't depend on omamobile-audio, so with one older
than 0.5.16 the setting does nothing and the speakers stay muted: an
optdepends line and a sentence in the README and the drop-in say so.

The package's test/all passes (19 ok). Version left for the merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
angelrenefm added a commit to angelrenefm/omarchy-mobile that referenced this pull request Nov 18, 2026
…audio

Two follow-ups from derekross#496's review. The drop-in cited the 16:13 comment
on derekross#427; the start and the playback are in the 15:33 one. And
device-panther doesn't depend on omamobile-audio, so with one older
than 0.5.16 the setting does nothing and the speakers stay muted: an
optdepends line and a sentence in the README and the drop-in say so.

The package's test/all passes (19 ok). Version left for the merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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