Repository navigation
device/panther: SUSPEND-PLAN and BLUETOOTH-PLAN, the Pixel 7's sleep and Bluetooth records - #852
Conversation
…and Bluetooth records The two plans that until now lived only in a local tree, so that the pull requests that follow (the Wi-Fi check, the brcmfmac patches, the memory bus floor, the Bluetooth package) can cite results that are on main. SUSPEND-PLAN: s2idle on the Pixel 7 Pro's path, stages Z1 to Z6 and P7 with their results from 2026-11-05 to 2026-11-13: the RTC alarm, the Wi-Fi firmware trap at a resume on the freeze path and the check that reloads it, the sleep hook, the keys as the wake, standby numbers with the memory bus at 2028 and 1014 MHz and with Wi-Fi kept, why deep doesn't wake, and power off on a kernel with linux-omarchy-mobile#233. BLUETOOTH-PLAN: the BCM4389 on the APM UART, gates BT1 to BT3 with their results from 2026-11-01, and the headset profile against WirePlumber's switch. Both status lines say what has merged since and what is still to come. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Thank you, Alejandro. I read both plans from top to bottom, and this is the kind of record I'd like every device to have: one change per boot, every result with its date and kernel, the two sleep paths counted apart, and the readings that turned out wrong (Z2e's PME theory, Z6g's empty pstore) corrected in place where a reader can follow them. I found no identifiers in either file, and the pull requests and merges the status lines name are as you say. The Wi-Fi trap work in Z2 and the same-evening MIF runs in Z6j are especially good. Five small things in SUSPEND-PLAN before I merge it:
One thing I'm taking from this for the Pixel 7 Pro: your Z1 explains the early alarm wakes I never tracked down there, and Z6k's 52 mA for keeping Wi-Fi loaded is a number I should measure on mine. |
- The Pixel 9a, not the Pixel 9 Pro, for device/tegu/SLEEP-PLAN.md. - The status line: the kernel releases since kernel-2026.11.13 carry linux-omarchy-mobile#233, so the upower drop-in waits only for off-mode charging (derekross#788). P7's last takeaway names derekross#730, which carried derekross#554's commits. - The standby numbers in the status line each with their condition: Wi-Fi kept at 2028 and at 1014 MHz, Wi-Fi unloaded at 1014 MHz. - Z2k's boot: only stock recovery came up, not Android. - DISPLAY-PLAN D5 and the NOTES entries, which come with the 90 Hz pull request, say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you for reading both plans so closely. All five are in one commit on top, 45b31a0:
I'm glad Z1 helps on the Pixel 7 Pro too. 🤖 Generated with Claude Code |
|
Thank you, Alejandro. All five are in, and I checked the new standby numbers against Z6c, Z6j and Z6k: they agree, and the status line now says what each one was measured with. Z2k's sentence settles the backup question, since Android itself never started. Merging. |
The Pixel 7's two plans that until now lived only in my tree:
device/panther/SUSPEND-PLAN.mdanddevice/panther/BLUETOOTH-PLAN.md. Documentation only, no package or kernel change. I'm opening them first so the pull requests that follow can cite results on main, as you preferred on #827.SUSPEND-PLAN, s2idle on the Pixel 7 Pro's path, stages Z1 to Z6 and P7, with their results from 2026-11-05 to 2026-11-13:
rtcwake -m freeze, 4 of about 73); onsystemctl suspendit hasn't trapped in 256 resumes. The record decoded, the driver's report, and the check that reloads the stack (Z2l, Z2m: it ran after 70 of 70 resumes and found the firmware answering). This is the evidence behind device-panther 0.1.10: Wi-Fi at boot with the Pixel 7 Pro's guarded start, unloaded around suspend (from #419) #475's default, Wi-Fi unloaded around sleep, and behind the check and the two brcmfmac patches to come.deepdoesn't wake; the power domains kernel that resets the phone, and the flat one that sleeps. The memory bus floor is a kernel pull request to come.kernel-2026.11.13); with the cable in, the bootloader's charger boot, which is what omamobile-device-panther: off-mode charging instead of starting the phone on its cable #788 handles.BLUETOOTH-PLAN, the BCM4389 on the APM UART, gates BT1 to BT3 with their results from 2026-11-01 (the kernel side merged as linux-omarchy-mobile#196, the options as #304), and the headset profile against WirePlumber's switch, which is why
BT_RFCOMMstayed out of #304. The package side is a pull request to come.Both status lines say what has merged since and what is still to come. SUSPEND-PLAN cites DISPLAY-PLAN D5 (the screen after s2idle), which comes with DISPLAY-PLAN's update in the 90 Hz pull request after linux-omarchy-mobile#181. Kernel names, local build numbers and the dates are as they were on the phone; I've checked the files for identifiers.
Checks:
tools/pr-checkpasses.🤖 Generated with Claude Code