Repository navigation
Pixel 8a (akita) M4: battery and charging, the USB rescue, and the dead-man tool on the 8a - #718
Conversation
The Pixel 8a has the Pixel 8 Pro's MAX77759 on the same bus (10cb0000.i2c), the same fuel gauge power supply and the same SoC watchdog (10060000.watchdog), so the dead-man tool works on it as it is, except for two things: the phone half refused any board but google,zuma-husky, and its current guard (1.7 A) was sized for the 8 Pro's DT charge current of 1.485 A. The phone half now names the board from the device tree's first compatible: google,zuma-husky keeps 1.7 A, google,zuma-akita gets 1.5 A above its DT's 1.32 A, and any other board is still refused before anything is applied. Every other limit, the undo and the watchdog path are unchanged. The desktop half's text no longer says the 8 Pro only. Read-only check on a Pixel 8a: the board function reads "Pixel 8a" and 1500000, and "tools/husky-deadman dump" reads the battery and the charger's registers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…blacklist The Pixel 8a's battery chips are the Pixel 8 Pro's, on the same bus, so husky's omamobile-usb-rescue and its unit come over byte for byte, enabled by a wants link, and the test checks they stay husky's. On the 8a an unplug opened the MAX77759's USB2 data switch (0x25:0x93 read 0x00), and the rescue brought the link back on the replug with no reboot (device/akita/BRINGUP-M4.md, M4.4). Without hsi2c_11 in the board file (linux-omarchy-mobile#246) it finds no bus and exits 0. omamobile-max77759.conf has husky's settings: the charger, GPIO, NVMEM and Type-C drivers don't autoload, so the charger runs only under tools/husky-deadman; the gauge and the MFD core do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two bring-up overlays from M4, never default. pack-eeprom-test.dtso is husky's: it enables hsi2c_9 so the pack's ID (EEPROM byte 0x17) can be read; this phone's reads 1, the ATL pack. gauge-model-atl.dtso loads Google's atl-a1-1k model into the fuel gauge, generated by tools/gen-gauge-overlay.py from zuma-akita-battery-data.dtsi (android-16.0.0_r0.10), with the header written for akita. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The M4 runbook and its results (tests 36 to 47): the gauge with the ATL model, the bootloader's charger state, the USB rescue, charging under tools/husky-deadman on a laptop port and a wall charger (gate h), and the PMIC's interrupt for the RTC alarm. NOTES gets an M4 section, and BRINGUP-M2 notes that M2.7's lost USB link is now confirmed to be the charger's data switch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, this is a careful M4. The plan reads well next to husky's notes, every step ends with slot B's tries, the fresh NV backup came first, and the open points are written down as open instead of smoothed over. I checked a few things myself: the rescue and its unit are husky's blobs exactly; the ATL model's 48 table words and 28 parameters match Google's Two things before I merge:
On your question about the name: please keep On the order: I'll merge this before linux-omarchy-mobile#246. With #246's board file and the 0.1.3 package, nothing would keep Smaller points, none of them blocking:
Thanks again. This is the kind of record that lets a second 8a owner repeat the work. |
…ADME and M4.6 stop and rollback From derekross#718's review. The desktop half's recovery text now speaks for each phone: the Pixel 8 Pro's lines as they were (Power + Volume Up for 15 to 30 s; whether a reset restores the charger is not known for husky), and for the Pixel 8a what BRINGUP-M4 measured, with "not tested" where it wasn't. board() also sets the steps each phone may run (both: noop, wd-drill, b3-charger), and preflight refuses any other step before anything is applied, so a step for one phone's hardware can't run on the other. akita's package README says the default boot has no gauge model (22.0 C and a level about 4 points high), and BRINGUP-M4's M4.6 gets its stop conditions (the guard's trips, the exit codes) and its rollback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From derekross#718's review: omamobile-device-akita 0.1.4 built and installed on the phone, the hand-made modprobe file and test unit gone, one reboot. The MFD core and the gauge autoload, the charger and Type-C drivers don't, the rescue starts from the package's wants link and closed the data switch after an unplug, and phone-smoke is clean. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you for checking all of that. Both are done, in 1. One boot of the package itself. The kernel is the #246 test tree (
The dependency didn't really get tested: i2c-tools was already on the phone, as a dependency of the Omarchy image's
One unplug and replug: The switch opened on the unplug, and the rescue closed it two seconds after the replug, with no reboot.
|
| Check | Result | Detail |
|---|---|---|
| boot (required) | ok | kernel 7.3.0-rc6-omamobile-push1-g8136602c700c, slot b, up 14s |
| storage guard (required) | ok | 62 partitions; only userdata and slot B's boot images writable |
| root (required) | ok | ext4 on userdata, 97G free |
| kernel health (required) | ok | no oops or BUG; 0 WARN, 2 error lines in dmesg (2 known, 0 new) |
| systemd units | ok | none failed |
| USB gadget (required) | ok | bound to 11210000.usb |
| display | ok | card0-Unknown-1 connected, 1080x2400 |
| GPU | not ok | no render node |
| session (required) | ok | Hyprland and the Omarchy shell running |
| lock | ok | PAM file present, the shell can lock (passwordPam true, locked false) |
| touch | ok | Goodix Berlin Capacitive TouchScreen |
| buttons | ok | gpio-keys |
| Wi-Fi | skip | no wireless interface |
| Bluetooth | skip | no controller |
| battery | ok | 89% Charging, 36 °C |
| sound cards | skip | none |
| sensors | skip | no sensor proxy |
| cameras | skip | no libcamera tools |
| thermal | ok | hottest zone 36 °C |
Packages: hyprland 0.57.0-3.3, 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-device-akita 0.1.4-1, omamobile-firstboot 0.1.5-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.44-1, omamobile-owl-widgets 0.1.2-1, omamobile-settings 0.1.2-1, omamobile-shell 0.2.127-1, omamobile-voice 0.1.0-1, omaphone 0.2.3-1, omarchy 4.5.0-3, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1
That's test 48 in BRINGUP-M4's results.
2. The recovery text is now per phone:
- The 8 Pro's lines are as they were: Power + Volume Up for 15 to 30 s, "Power alone does nothing on the 8 Pro under our kernel", and "NOT known for husky". Some lines wrap differently.
- The 8a gets what was measured:
- the forced restart: not tested; Volume Down + Power held for over a minute came back into slot B once;
- the charger registers: a reboot through the bootloader restored them (test 46); a forced restart isn't tested;
- fastboot by hand: reached once in M2, once not; "how long to hold which key is not known".
The name and the steps: husky-deadman and its log paths stay. board() now also sets STEPS for each phone (both: noop wd-drill b3-charger), and preflight refuses any other step before the watchdog is armed or the charger touched. So #282's husky-only steps need only be added to husky's list.
The smaller points:
- The README now says the default boot has no gauge model: 22.0 C and a level about 4 points high.
- M4.6 now has its stop conditions (the guard's trips, exit codes 3 to 7) and its rollback (
undo b3-chargerat once after a clean soak, thendump). - The charge current: agreed, the level and the current come from the same gauge, so one doesn't confirm the other. I don't have an inline USB meter yet, so I'll measure it once I have one and report back here. No limit goes up until it's settled.
- The squash subject: fine by me.
🤖 Generated with Claude Code
|
Thank you, both points are done, and the record is better for how you did them. Test 48 is exactly the boot I asked for: the hand files gone, the package built from the branch, the MFD core and the gauge loading under the package's own blacklist with no charger or Type-C driver, the rescue started by its wants link and closing the switch two seconds after a replug, and the smoke report. Thank you for saying plainly that the I ran your package's test and husky's on today's main with this merged (both pass), and the head's CI is green. I'll merge it now, before linux-omarchy-mobile#246 as I said, so the blacklist is published before the board file that needs it. Two small notes for later: |
|
The charge current, measured with an inline USB meter. The Pixel 8a was at 44 %, screen off, with the charger as the bootloader leaves it: mode 0x05, CHGIN_ILIM
So the gauge's current is right. The roughly 2.8 W that doesn't reach the battery fits the phone's own idle load with the screen off, plus charger losses. What doesn't hold is the 500 mA input limit: the phone draws well above it on both a laptop port and a wall charger. Either 🤖 Generated with Claude Code |
akita's M4, battery and charging: the runbook and its results, the two overlays it used, the USB rescue and the MAX77759 blacklist in akita's package, and the dead-man tool running on the 8a. The kernel side is linux-omarchy-mobile#246.
What's in it:
device/akita/BRINGUP-M4.md: the plan (M4.0 to M4.7) and the results, tests 36 to 47. In short:atl-a1-1kmodel (real temperature, 4486 mAh);rtc0an alarm.device/akita/overlays/:pack-eeprom-test.dtso: husky's, enablinghsi2c_9to read the pack's ID;gauge-model-atl.dtso: generated bytools/gen-gauge-overlay.pyfrom Google'szuma-akita-battery-data.dtsi(android-16.0.0_r0.10). The tool's header text names husky, so this one's header was written by hand.Both are bring-up overlays and aren't in
device.conf, as on husky.omamobile-device-akita 0.1.4:
omamobile-usb-rescueand its unit, enabled by a wants link. They're husky's files byte for byte, and the test checks they stay that way.omamobile-max77759.conf, with husky's settings (the comment names the 8a; the test checks the settings).i2c-toolsas a dependency.Without docs/review: lessons L-362 to L-389 from the 2026-11-01 round #246 the rescue finds no
10cb0000.i2cand exits 0, so it's harmless on today's kernel.tools/husky-deadmanand-phone: they read the board from the device tree's first compatible. The Pixel 8 Pro keeps its 1.7 A current guard. The Pixel 8a gets 1.5 A, for its 1.32 A charge limit. Any other board is refused. The log names the board.NOTES: an M4 section, and a line in BRINGUP-M2 that M2.7's lost link was the charger's data switch, now confirmed on akita.
A question for you: the dead-man tool's name. It keeps the name
husky-deadmanand its log paths, so husky's runbooks still work. Would you rather it were renamed (zuma-deadman?) with husky's docs updated, or akita got its own copy? I'm happy to do either in this PR.Open, from the results:
max77759_charger'sconstant_charge_voltage_maxreads4200, which looks like millivolts where sysfs uses microvolts.Checks:
tests/all,tests/packagesandtools/pr-checkpass. akita's package test has 3 new checks, 19 in all:The install also stages 14 files now.
Slot B ended with 2 tries.
🤖 Generated with Claude Code