Skip to content

device/husky: AOC-PLAN.md, the AoC and sound results so far, each with its date and uname -r - #450

Merged
derekross merged 2 commits into
derekross:mainfrom
Somnius:husky-aoc-plan
Nov 7, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
Somnius:husky-aoc-plan

Conversation

@Somnius

@Somnius Somnius commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Derek asked for this on #1: the AoC plan for the 8 Pro, with the results I posted there, each with its date and uname -r, before the next AoC boot. It replaces my local notes; the file has the plan (stages Z0 to Z7), what ran, and the open items.

It includes the System MMU read that reset the phone on 2026-11-04 (gd39ee40b43b6) and its cause: I had copied the 7 Pro's v8 register offsets and zuma's System MMU is v9, which doesn't have them (found on 2026-11-05 with g129efb688b6f, the v9 map reads fine). It also has the other things that cost me time: trusty-ipc before trusty-virtio, UltraLL (EP1) hanging the AoC against the deep-buffer route (EP6) that plays, and the pre-start data problem in the shared ALSA driver with PipeWire (not gated for zuma yet, so it must not reach the 7 Pro).

The code that ran is public: branch husky-e1-aoc-20261106 and tag husky-test-20261106-e1-aoc on my fork (https://github.com/Somnius/linux-omarchy-mobile/tree/husky-test-20261106-e1-aoc). They are TEST ONLY commits on Brett's c6 tag, nothing there is meant to go upstream as it is. Two commit messages were reworded for publishing, so some commit ids differ from the uname -r strings; the file maps them, and the trees are the same. No firmware or calibration is in the branch. tools/pr-check passes.

On the speaker levels: the file says plainly that on 2026-11-05 I drove the 8 Pro above the 7 Pro's media stage during level tests, and that it has been back at media since 2026-11-06 06:50.

…h its date and uname -r

The plan for the Pixel 8 Pro's AoC and sound, with what ran on my phone
in stages Z0 to Z7: the GSA and Trusty (trusty-ipc has to be loaded
before trusty-virtio), the System MMU read that reset the phone and its
cause (the 7 Pro's v8 offsets on zuma's v9 block), the load and start of
aoc.bin (94 services), both CS35L41 amplifiers, the speaker route (the
deep-buffer entry point, not UltraLL, which hangs the AoC), the shared
driver's pre-start data problem with PipeWire, and the speaker levels.

Every result has its date and the `uname -r` of the kernel it ran on.
The code is on a public branch and tag on my fork (TEST ONLY commits,
nothing in it is meant to go upstream as it is), linked in the file.
No firmware, calibration or other blob is in it.
@derekross

Copy link
Copy Markdown
Owner

@Somnius thank you for this. It's a real plan in the shape I hoped for: every stage has its date and kernel, the System MMU reset has its cause, and the dead ends (UltraLL, the PCU, the v8 offsets) are written down where the next person will find them. I checked the branch and tag on your fork. Both point at 7fa4d8b91, as the file says. The spi-s3c64xx scoping in §4 is right on our base: manual_native_cs is only set for zuma and zumapro. That includes the 9a, which your §8 already plans to show.

One change before I merge. §7 says the level tests were "short tone bursts at 817 / 17 … listening at 817 / 8". Your comment on #1 says more: bursts at analog 12 up to 17, then tens of minutes of music at 817 / 8 on the bottom amp, the top amp up to 817 / 8, with speaker_protection=1 on the card driver. Please put that sentence in the plan as you wrote it there. It's the record someone will read to judge whether these speakers were stressed, and it's also your evidence that nothing faulted.

Two optional things. §9 could say that on /dev/acd-debug only help and read commands are run without asking first, since watchdog_enable off, bclk ds and gpio ds all change something. And the status line and §8 can point at kernel #203 and #204 and at #453 now that they exist, in this PR or a later one.

@Somnius

Somnius commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

@derekross fixed. §7 now has the level sentences as I wrote them on #1, word for word: the short bursts on the bottom amp at digital 817 / analog 12 up to 17, then tens of minutes of YouTube and music through the bottom amp at 817 / 8, and the top amp up to 817 / 8 too, and that I had been loading the card driver with speaker_protection=1 at the time. It also keeps my note that there was no amp fault or over-temperature in dmesg. I added your /dev/acd-debug rule to §9 (only help and read commands without asking first, since watchdog_enable off, bclk ds and gpio ds all change something), and the status line and §8 now point at derekross/linux-omarchy-mobile#203, derekross/linux-omarchy-mobile#204 and #453.

@derekross

Copy link
Copy Markdown
Owner

@Somnius thank you. §7 now reads exactly as you wrote it on #1, and that's the record I wanted next to the results. The /dev/acd-debug rule and the pointers to the kernel PRs and #453 are in as well. Merging this now, ahead of #472, which links it.

@derekross
derekross merged commit 51463dc into derekross:main Nov 7, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Merged, thank you @Somnius. One correction for the record, and an apology: the squash commit on main ends with Signed-off-by: Lef <me@lefteros.com>, which I added and which your commits on this PR didn't carry. That was my mistake, and you didn't sign anything off here. omarchy-mobile doesn't require a sign-off, and main isn't rewritten, so this comment is the correction. Say if you'd like anything else done about it.

@Somnius

Somnius commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

@derekross thank you for telling me, and I'm fine with it, nothing more needs doing. One request: please make sure the Pixel 8 Pro updates make it onto the devices page on the website too, so people can see that the 8 Pro is actively worked on by several of us, all keen to see it working with OmaMobile.

robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…s#450)

The Pixel 8 Pro's AoC plan: every stage with its date and kernel, the System MMU reset with its cause, the dead ends (UltraLL, the PCU, the v8 offsets) written down, the speaker-level history as recorded on derekross#1, and the rule that only help and read commands run on /dev/acd-debug without asking first.

Signed-off-by: Lef <me@lefteros.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