Skip to content

omamobile-device-cheetah 0.1.55: suspend on the 7 Pro: double tap from sleep, auto-sleep by default, the charging boot, power off at a critical battery - #730

Merged
derekross merged 6 commits into
mainfrom
device-cheetah-touch-wake
Nov 14, 2026
Merged

derekross merged 6 commits into
mainfrom
device-cheetah-touch-wake

Conversation

@derekross

@derekross derekross commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

Everything the 7 Pro's suspend needs from its device package, for kernel-2026.11.13 (power off fixed by linux-omarchy-mobile#233, touch wake by #248), which is on the development channel:

Version 0.1.55 (main has 0.1.54). Tested: packages/omamobile-device-cheetah/test/all, tools/pr-check. On the phone: the touch-wake rule and the charging boot were run by hand on 2026-11-13; the upower drop-in's first real run is a phone reaching 3 %.

🤖 Generated with Claude Code

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>
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>
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>
@derekross derekross changed the title omamobile-device-cheetah 0.1.56: double tap wakes the phone from sleep omamobile-device-cheetah 0.1.56: double tap wakes the phone from sleep, and auto-sleep on by default Nov 13, 2026
derekross and others added 4 commits November 14, 2026 11:30
…wake

# Conflicts:
#	packages/omamobile-device-cheetah/version
…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>
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 derekross changed the title omamobile-device-cheetah 0.1.56: double tap wakes the phone from sleep, and auto-sleep on by default omamobile-device-cheetah 0.1.55: suspend on the 7 Pro: double tap from sleep, auto-sleep by default, the charging boot, power off at a critical battery Nov 14, 2026
@derekross
derekross merged commit 4fcdc03 into main Nov 14, 2026
2 checks passed
@derekross
derekross deleted the device-cheetah-touch-wake branch November 14, 2026 16:42
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.

2 participants