Repository navigation
device/husky: AOC-PLAN.md, the AoC and sound results so far, each with its date and uname -r - #450
Conversation
…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.
|
@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 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 Two optional things. §9 could say that on |
|
@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 |
|
Merged, thank you @Somnius. One correction for the record, and an apology: the squash commit on main ends with |
|
@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. |
…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>
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 withg129efb688b6f, the v9 map reads fine). It also has the other things that cost me time:trusty-ipcbeforetrusty-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-20261106and taghusky-test-20261106-e1-aocon 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 theuname -rstrings; the file maps them, and the trees are the same. No firmware or calibration is in the branch.tools/pr-checkpasses.On the speaker levels: the file says plainly that on 2026-11-05 I drove the 8 Pro above the 7 Pro's
mediastage during level tests, and that it has been back atmediasince 2026-11-06 06:50.