Skip to content

device-cheetah 0.1.55: handle the bootloader's off-mode charging boot - #554

Closed
ikegam wants to merge 2 commits into
derekross:mainfrom
ikegam:omamobile-charger-mode
Closed

ikegam wants to merge 2 commits into
derekross:mainfrom
ikegam:omamobile-charger-mode

Conversation

@ikegam

@ikegam ikegam commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

What and why

A Pixel 7 Pro that is off and gets a charger, or is powered off with the cable in, is started by its bootloader with androidboot.mode = "charger"; stock runs only its charging screen then. We ignored the mode and started the whole phone, so a 7 Pro powered off on its cable came straight back up.

device-cheetah 0.1.55 makes omamobile-charger.target the default target of such a boot (a generator, from its early folder so a default in /etc doesn't win; /etc/omamobile/charger-mode-disable turns it off). That boot starts no session, modem, Wi-Fi or AoC, masks Plymouth, Bluetooth and the camera timer, keeps SSH over USB as on a normal boot (usb-rescue, usb-mac, ufw), and runs (restarted on failure) omamobile-charger-mode: the panel off (bl_power 4, which systemd-backlight doesn't save), Power held for a second restarts into the phone, the cable out for five seconds powers it off. The script does nothing outside a charger boot, or in one where multi-user.target is up.

Also a NOTES entry for 2026-11-09: why power off restarted the phone (the PMIC's WTSR restart left armed by rtc-s5m; the kernel fix is linux-omarchy-mobile#233) and what the charger boot did.

Needs linux-omarchy-mobile#233: without it, power off restarts the phone, and "cable out: power off" does too.

Device and build

  • Phone: Pixel 7 Pro (cheetah)
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-g0e3da55c9e9f (the release kernel g2219cc6cda77 plus the RTC fix)
  • Packages changed, with versions: omamobile-device-cheetah 0.1.55 (tested on the phone as 0.1.45-0.1, the same files on an older main)

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes
  • tests/packages passes (or the packages I touched: omamobile-device-cheetah)
  • Each changed package has its version bumped, and the new version is in the commit subject
  • Commits have area prefixes and bodies that say why; any AI help is a Co-Authored-By: or Assisted-by: trailer, never a Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed: poweroff with the cable in → charger boot (androidboot.mode = "charger"), omamobile-charger.target active, multi-user/graphical/sddm/Wi-Fi/AoC inactive, Plymouth/Bluetooth/camera timer masked, nothing failed, panel off, SSH up; Power held → normal boot; cable out → charger unplugged: poweroff 5 s later, the phone stayed off.
  • What I did not test: a phone on the release kernel (it restarts at power off before it can reach the charger boot, see NOTES); a charger that isn't a laptop port; a flat battery's charger boot. Open: a wireless pad (the unplug rule follows the cable input only, so the phone likely stays in the charger boot when lifted off), and whether the bootloader spends one of slot B's tries on a charger boot while B is unmarked.
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)
tools/phone-smoke report

phone-smoke: cheetah

Kernel 7.3.0-rc6-omamobile-push1-g0e3da55c9e9f, tools at e19ea6c, 2026-11-09T08:54Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g0e3da55c9e9f, slot b, up 3143s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 95G 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, 1440x3120
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 true)
touch ok Synaptics TouchComm Touchscreen
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 51% Charging, 35 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras ok 4 listed by libcamera
thermal ok hottest zone 51 °C

Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.13-1, omamobile-boot-update 0.1.0-1, omamobile-device-cheetah 0.1.45-0.1, omamobile-fingerprint 0.1.15-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.2-1, omamobile-modem 0.1.16-1.2, omamobile-modem-sit 0.3.32-0.1, omamobile-omarchy 0.1.32-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.101-1.1, omaphone 0.2.3-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

🤖 Generated with Claude Code

@derekross

Copy link
Copy Markdown
Owner

Thank you for this, and welcome! Finding out why power off restarted the
phone, and then giving the charger boot something sensible to do, is
exactly the kind of work the 7 Pro needed. The generator approach (early
directory, an opt-out file, masks only in that boot) is clean, and the
tests drive the real script through a fake sysfs and a FIFO for the power
key, which I appreciate. I ran the package's test in our build container
and it passes; CI is waiting on my approval, which I'll give.

A few things before it can go in:

  1. Whose phone the NOTES entry describes. device/cheetah/NOTES.md has
    been my phone's record so far, and my phone has never run a power off
    from Linux (SUSPEND-PLAN P7). Could you head the entry with "on a second
    Pixel 7 Pro (yours: a release install with AUTO_WRITE=yes)", so nobody
    reads it as the reference phone's result?
  2. Volume Down + Power. Our recovery instructions say that holding
    Volume Down + Power for about 20 s reaches fastboot, so "ended in a
    normal boot" matters a lot. Could you add: was the phone running Linux
    or off when you started holding, for how long, which slot booted, and
    does it reach fastboot now with the RTC fix? I don't think the kernel
    fix can change this path (it only runs on a power off, not on the
    PMIC's manual reset), so if the keys don't work on your phone, I'd like
    to understand why before anyone relies on them.
  3. Order with the kernel fix. Without linux-omarchy-mobile#233, a
    charger boot only happens from a phone that was really off, and there
    "cable out: power off" restarts it into the full phone. Could the
    description say the behaviour needs omamobile-shell 0.2.53: an Updates entry in the app drawer, and update sheet fixes from its first run #233? I'll merge this after the
    kernel fix is in a release.

Some questions, not blockers yet:

  • omamobile-boot-success runs after multi-user.target, so a charger
    boot doesn't mark slot B. On a phone where B is marked that's fine. If
    you ever have B unmarked (after a flash or a fresh install), could you
    read omamobile-bootctl dump (only the slot b lines) before and after
    one charger boot? If ABL spends a try on each charger boot, a few plugs
    in a row could fall back to slot A, and I'd rather know before release.
  • ufw.service is wanted by multi-user.target, so the charger boot runs
    sshd without the firewall. Only usb0 exists then, so it's the same in
    practice, but adding ufw.service to the target's Wants= would keep it
    the same by construction.
  • omamobile-charger.service has no Restart=; if the script ever dies
    after the panel goes off, only a 30 s Power hold gets out.
    Restart=on-failure would cover that.
  • If you can, one run on a wall charger (no USB host), read back afterwards
    from journalctl -b -1 -u omamobile-charger. That's what most people
    will do.

Your note about AUTO_WRITE=yes replacing a pushed kernel is a good catch;
I'll add it to the release notes for people who develop on a release
install.

Before merging I'll run it on my 7 Pro with the kernel fix: a normal
reboot, a power off on the cable into the charger boot (checking that the
modem, AoC and Wi-Fi stay down, the battery charges and slot B's flags
don't change), Power held to boot, and unplugging to power off. The
version number will move at merge, since 0.1.48 is also claimed by two
other open pull requests; no need to change it.

@ikegam

ikegam commented Nov 11, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the review! I'll fix all of these.

@derekross

Copy link
Copy Markdown
Owner

Thanks for the reply. Nothing has been pushed yet, so the points from my last comment stand, and main has moved since, which is why GitHub now shows conflicts. Here is exactly what the rebase needs, so it's one pass:

  1. version. Main is at device-cheetah 0.1.50, so 0.1.48 is taken. Use the next free number when you push (0.1.51 today) in the file, the commit subject and the title. Another open pull request claims the same number, so I may move it by one at merge; that's mine to sort out.
  2. test/all. Keep both sides: main's new block (the USB address and location-agent tests) and your charger block. Neither replaces the other.
  3. NOTES.md. Keep both sides, newest entry first. Please head yours "on a second Pixel 7 Pro (a release install with AUTO_WRITE=yes)". And the Volume Down + Power sentence can now be settled: I tried the keys on my 7 Pro with your kernel fix on 2026-11-10. Holding them forces a reset, and the phone reaches fastboot only when Volume Down is still held while the bootloader starts; otherwise it boots normally. That's the bootloader's ordinary behaviour, so please reword the entry to say that, rather than that the keys failed.
  4. One new thing from main. omamobile-device-cheetah 0.1.45: the USB gadget keeps the same MAC addresses across boots (#448) #510 added omamobile-usb-mac.service, which gives the USB gadget the same addresses on every boot, and it's wanted only by multi-user.target, which your charger boot doesn't reach. A charger boot would then show the laptop a different network device than a normal boot. Could you add it to omamobile-charger.target's Wants=, next to omamobile-usb-rescue.service? It has no default dependencies and never holds the boot.
  5. From before: the description should say the behaviour needs linux-omarchy-mobile#233, and the smaller ones are still welcome in the same push (ufw.service in the target's Wants=, Restart=on-failure on the charger service, slot B's flags across one charger boot if you ever have B unmarked, a wall-charger run).

The kernel fix isn't merged yet (it waits on one sentence in its commit message), and this goes in after it is in a kernel release. Then I'll run it on my 7 Pro as described last time.

@ikegam
ikegam force-pushed the omamobile-charger-mode branch from 41b5b16 to b369f12 Compare November 12, 2026 12:26
@ikegam ikegam changed the title device-cheetah 0.1.48: handle the bootloader's off-mode charging boot device-cheetah 0.1.53: handle the bootloader's off-mode charging boot Nov 12, 2026
@derekross

Copy link
Copy Markdown
Owner

Thank you, this push covers everything from my two comments: the NOTES entry is headed as a second Pixel 7 Pro, the Volume Down + Power sentence now says what the bootloader really does, omamobile-usb-mac and ufw are in the target, the service restarts on failure, and the description says it needs the kernel fix. I also like the new check that the script does nothing when multi-user.target is up. CI is waiting for my approval and the branch conflicts on version only (main took 0.1.52 last night); I ran the gate and the package's tests on a merge with main and they pass. 0.1.53 is right for today; I'll settle the final number at merge, since #556 touches the same file.

One change before I run it on my phone:

  • The panel is switched off once, at start, and only if the backlight device is already there. omamobile-charger-mode calls panel(True) once before its loop. The panel driver is a module that udev loads, and the service is ordered only after basic.target, so nothing guarantees /sys/class/backlight/1c2c0000.dsi.0 exists at that moment. I tried it with a fake sysfs where the backlight folder appears half a second after the script starts: bl_power stays 0 and nothing is logged, so the panel would stay lit for the whole charge. Your run ended dark, so the timing worked out there, but I'd rather not depend on it. Could the loop write bl_power for any backlight that doesn't read 4 (it already wakes every second), with a test where the folder appears late?

Smaller things, in the same push if you like:

  • finish() returns 0 even when systemctl reboot or poweroff fails, so Restart=on-failure never applies there and the phone is left dark with Power doing nothing. Returning systemctl's status would cover it.
  • The test harness uses PATH=/usr/bin:/bin, so the script's plymouth quit runs the real plymouth on whatever machine runs the test. A fake on the path would keep it self-contained.
  • Two lines for "not tested": a wireless pad (the unplug rule follows the cable input only, so I'd expect the phone to stay in the charger boot after it's lifted off), and whether the bootloader spends one of slot B's tries on a charger boot when B isn't marked. Neither needs a run from you now; I just want them written down as open.

Then it's my turn: with the kernel fix on my 7 Pro I'll check a normal boot, power off on the cable into the charger boot (the modem, AoC and Wi-Fi down, the panel dark at one and at fifteen minutes, the charge guard on, the same USB address, slot B's flags unchanged), Power held, unplugging on the laptop and on a wall charger, and one charge left to Full. This still goes in after linux-omarchy-mobile#233 is in a kernel release.

@ikegam
ikegam force-pushed the omamobile-charger-mode branch from b369f12 to ba3867c Compare November 12, 2026 15:14
@ikegam ikegam changed the title device-cheetah 0.1.53: handle the bootloader's off-mode charging boot device-cheetah 0.1.55: handle the bootloader's off-mode charging boot Nov 12, 2026
@ikegam
ikegam force-pushed the omamobile-charger-mode branch from ba3867c to 73b9abc Compare November 12, 2026 15:20
@derekross

Copy link
Copy Markdown
Owner

@ikegam, I ran this on my Pixel 7 Pro today (2026-11-13) on a kernel built from github/omamobile at 2db2bc35beec (with linux-omarchy-mobile#233; 7.3.0-rc6-omamobile-push1-g2db2bc35beec), the package built from this branch merged with main (NOTES resolved by keeping both entries) as 0.1.55-0.1, installed before the push so the boot-update hook couldn't touch slot B.

  • A normal boot on the kernel: tools/phone-smoke passed, registered, the charger target and service inactive, no generator link.
  • Power off, cable out: it stayed off. omamobile-shell 0.2.53: an Updates entry in the app drawer, and update sheet fixes from its first run #233 does its job on this unit.
  • Plugging an off phone in: the bootloader started the charger boot. Holding Power: "Power held: reboot", then a normal boot.
  • Power off on the laptop's cable: androidboot.mode = "charger", the charger target active, multi-user, graphical, sddm, the modem, Wi-Fi and AoC inactive, nothing failed, bl_power 4, no cpif, brcmfmac or aoc_core loaded, ufw active, the USB address the same as before, charging at about 320 mA.
  • Unplugging in the charger boot: it powered off; plugging back in started the charger boot again.

Two small things for later, not blocking: the first status line of each charger boot reads "battery 99% Discharging" (read before the charger reports online; it says Charging a second later), and what the owner sees is the bootloader's warning, its charging icon, our boot logo, then black, so a charging indicator would help someone who doesn't know the screen is meant to be dark. Not run yet: the fifteen minutes dark, a wall charger, charging to Full.

This merges after the kernel release that carries #233, which waits for #232; until then a release phone's power off restarts it and never reaches this boot. I'll set the device-cheetah version at merge.

derekross added a commit that referenced this pull request Nov 13, 2026
…11-13 runs (#731)

The overnight standby (about 22 h), power off and the charger boot (on a
kernel with linux-omarchy-mobile#233 and #554) and double tap from
suspend-to-idle (kernel #248, #730) passed on the reference phone today.
The cell moves from WIP to testing, not works: auto-sleep still ships off,
the fixes aren't in a kernel release, and with the modem up the phone
doesn't sleep (kernel #232 lost mobile data after refused sleeps today).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
ikegam and others added 2 commits November 14, 2026 06:55
…e on its cable

A 7 Pro powered off on its cable is started by the bootloader with
androidboot.mode = "charger", where stock runs only a charging screen.
We started the whole phone (2026-11-09: both boots after a power off on
the cable read "charger").

omamobile-charger-mode-generator makes omamobile-charger.target the
default of such a boot (early folder; /etc/omamobile/charger-mode-disable
turns it off). The target starts no session, modem, Wi-Fi or AoC, and
keeps SSH over USB as on a normal boot (usb-rescue, usb-mac, ufw).
omamobile-charger-mode turns the panel off, restarts into the phone on
Power held for a second, and powers off five seconds after the cable is
out. Needs linux-omarchy-mobile#233: without it, power off restarts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er boot

On a second 7 Pro, not the reference phone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ikegam
ikegam force-pushed the omamobile-charger-mode branch from 73b9abc to 34d1526 Compare November 13, 2026 21:55
@ikegam

ikegam commented Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the thorough run on your 7 Pro! Rebased on today's main: the version stays 0.1.55 and NOTES keeps both entries, no code changed. Noted the first "Discharging" line and the charging indicator for later.

@nesmeck

nesmeck commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

One data point for the open question about slot B's tries, from a Pixel 7 (panther), not a 7 Pro. On a kernel built from omamobile at 82f31d3a7, which has #233, with slot B unmarked as usual for panther, a power off on the cable went to the bootloader's charger boot. The charging icon showed for under a second, then our kernel came up on slot B with androidboot.mode = "charger". Slot B had 2 tries left before the power off and still 2 after the charger boot. A power-on by holding Power after a power off with the cable out spent one try, as a normal boot does.

That is one charger boot, so it isn't proof, but it suggests the bootloader doesn't count a charger boot as a try. panther doesn't have this handling yet, so that boot started the whole phone. I plan to bring the same files to device-panther once this is merged.

🤖 Generated with Claude Code

@ikegam

ikegam commented Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

@nesmeck thanks for checking it on the 7 and counting the tries! Good to know a charger boot doesn't spend one. Happy to see it go to panther too.

derekross added a commit that referenced this pull request Nov 14, 2026
upower's default critical action is a suspend; suspended at 2 % the phone
runs flat asleep within about 20 minutes, a brown-out with the root file
system mounted. Power off now works (linux-omarchy-mobile#233, in
kernel-2026.11.13, on the development channel), and an off phone on a
charger starts the dark charging boot (#554's charger target, carried in
this pull request). So the drop-in of SUSPEND-PLAN 6.6: PowerOff at 3 %.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 14, 2026
…m sleep, auto-sleep by default, the charging boot, power off at a critical battery (#730)

* omamobile-device-cheetah 0.1.56: double tap wakes the phone from sleep

With auto-sleep on, the phone really sleeps (suspend-to-idle) 30 s after
the screen goes off, and then only the power key woke it: the touch
driver turned its interrupt off for the whole sleep. linux-omarchy-mobile#248
makes the touchscreen wakeup capable, off by default; this udev rule turns
it on for the 7 Pro's Synaptics S3908. On a kernel without #248 there is no
power/wakeup attribute and the rule does nothing.

Tested on the reference phone on 2026-11-13 with the rule's effect set by
hand (echo enabled > power/wakeup) on a kernel with #248: asleep through
omamobile-sleepd, a double tap woke it on the touchscreen's interrupt and
lit the lock screen. 0.1.54 and 0.1.55 are claimed by open pull requests
(#556, #554).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* omamobile-device-cheetah: auto-sleep on by default on the Pixel 7 Pro

Ship /usr/share/omamobile/auto-sleep-default, which omamobile-shell 0.2.129's
user setup reads (#737): suspend on this phone is verified
(SUSPEND-PLAN, 2026-11-13), and with this package's touch-wake rule a
double tap wakes it from sleep, so auto-sleep no longer costs double tap.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* device-cheetah 0.1.55: off-mode charging instead of starting the phone on its cable

A 7 Pro powered off on its cable is started by the bootloader with
androidboot.mode = "charger", where stock runs only a charging screen.
We started the whole phone (2026-11-09: both boots after a power off on
the cable read "charger").

omamobile-charger-mode-generator makes omamobile-charger.target the
default of such a boot (early folder; /etc/omamobile/charger-mode-disable
turns it off). The target starts no session, modem, Wi-Fi or AoC, and
keeps SSH over USB as on a normal boot (usb-rescue, usb-mac, ufw).
omamobile-charger-mode turns the panel off, restarts into the phone on
Power held for a second, and powers off five seconds after the cable is
out. Needs linux-omarchy-mobile#233: without it, power off restarts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* NOTES: power off restarted the 7 Pro (the PMIC's WTSR), and the charger boot

On a second 7 Pro, not the reference phone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* omamobile-device-cheetah 0.1.55: power off at a critical battery

upower's default critical action is a suspend; suspended at 2 % the phone
runs flat asleep within about 20 minutes, a brown-out with the root file
system mounted. Power off now works (linux-omarchy-mobile#233, in
kernel-2026.11.13, on the development channel), and an off phone on a
charger starts the dark charging boot (#554's charger target, carried in
this pull request). So the drop-in of SUSPEND-PLAN 6.6: PowerOff at 3 %.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Hiroyuki Ikegami <ikegam@mixallow.net>
@derekross

Copy link
Copy Markdown
Owner

@ikegam, your two commits landed on main unchanged, with your authorship, as part of #730 (omamobile-device-cheetah 0.1.55), together with the touch-wake rule, auto-sleep by default and the critical-battery power-off. I carried them there because the device package needed one version for all four and the NOTES conflict was mine to resolve. The kernel side (#233) is in kernel-2026.11.13, on the development channel. Thanks for this one: it closed P7. Closing this as landed.

@derekross derekross closed this Nov 14, 2026
nesmeck added a commit to nesmeck/omarchy-mobile that referenced this pull request Nov 15, 2026
…g the phone on its cable

A Pixel 7 powered off on its cable is started by its bootloader with
androidboot.mode = "charger", where stock runs only a charging screen.
We started the whole phone.

The Pixel 7 Pro's off-mode charging (derekross#554, landed in derekross#730), copied byte
for byte: omamobile-charger-mode-generator makes omamobile-charger.target
the default of such a boot, and omamobile-charger-mode turns the panel
off, restarts into the phone on Power held for a second, and powers off
five seconds after the cable is out. The test checks the copies against
the cheetah package, runs the generator on a charger boot, a normal boot
and with charger-mode-disable, and checks that the target keeps SSH over
USB and starts nothing of the phone. python joins depends.

The power off on an unplug reads the charger's online, which needs the
MAX77759 charger in the device tree; omamobile doesn't describe it for
panther yet, so there the phone stays in the dark charging boot until
Power is held.

Tested on a Pixel 7 from slot B, on a kernel that describes the charger:
a power off on the cable went to the charger boot, the panel went dark
and SSH over USB came up; Power held restarted into the phone; a second
charger boot powered off once the cable was out. Neither charger boot
spent a slot B try.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nesmeck added a commit to nesmeck/omarchy-mobile that referenced this pull request Nov 15, 2026
…hone on its cable

A Pixel 7 powered off on its cable is started by its bootloader with
androidboot.mode = "charger", where stock runs only a charging screen.
We started the whole phone.

The Pixel 7 Pro's off-mode charging (derekross#554, landed in derekross#730), copied byte
for byte: omamobile-charger-mode-generator makes omamobile-charger.target
the default of such a boot, and omamobile-charger-mode turns the panel
off, restarts into the phone on Power held for a second, and powers off
five seconds after the cable is out. The test checks the copies against
the cheetah package, runs the generator on a charger boot, a normal boot
and with charger-mode-disable, and checks that the target keeps SSH over
USB and starts nothing of the phone. python joins depends.

The power off on an unplug reads the charger's online, which needs the
MAX77759 charger in the device tree (linux-omarchy-mobile#259).
Without it the phone stays in the dark charging boot until Power is
held.

Tested on a Pixel 7 from slot B, on a kernel that describes the charger:
a power off on the cable went to the charger boot, the panel went dark
and SSH over USB came up; Power held restarted into the phone; a second
charger boot powered off once the cable was out. Neither charger boot
spent a slot B try.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nesmeck added a commit to nesmeck/omarchy-mobile that referenced this pull request Nov 18, 2026
- 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>
nesmeck added a commit to nesmeck/omarchy-mobile that referenced this pull request Nov 18, 2026
…hone on its cable

A Pixel 7 powered off on its cable is started by its bootloader with
androidboot.mode = "charger", where stock runs only a charging screen.
We started the whole phone.

The Pixel 7 Pro's off-mode charging (derekross#554, landed in derekross#730), copied byte
for byte: omamobile-charger-mode-generator makes omamobile-charger.target
the default of such a boot, and omamobile-charger-mode turns the panel
off, restarts into the phone on Power held for a second, and powers off
five seconds after the cable is out. The test checks the copies against
the cheetah package, runs the generator on a charger boot, a normal boot
and with charger-mode-disable, and checks that the target keeps SSH over
USB and starts nothing of the phone. python joins depends.

The power off on an unplug reads the charger's online, which needs the
MAX77759 charger in the device tree (linux-omarchy-mobile#259).
Without it the phone stays in the dark charging boot until Power is
held.

Tested on a Pixel 7 from slot B, on a kernel that describes the charger:
a power off on the cable went to the charger boot, the panel went dark
and SSH over USB came up; Power held restarted into the phone; a second
charger boot powered off once the cable was out. Neither charger boot
spent a slot B try.

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.

3 participants