Repository navigation
Conversation
|
Thank you for this, and welcome! Finding out why power off restarted the A few things before it can go in:
Some questions, not blockers yet:
Your note about Before merging I'll run it on my 7 Pro with the kernel fix: a normal |
|
Thanks for the review! I'll fix all of these. |
|
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:
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. |
41b5b16 to
b369f12
Compare
|
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, One change before I run it on my phone:
Smaller things, in the same push if you like:
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. |
b369f12 to
ba3867c
Compare
ba3867c to
73b9abc
Compare
|
@ikegam, I ran this on my Pixel 7 Pro today (2026-11-13) on a kernel built from
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. |
…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>
…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>
73b9abc to
34d1526
Compare
|
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. |
|
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 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 |
|
@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. |
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>
…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>
|
@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 |
…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>
…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>
- 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>
…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>
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.targetthe default target of such a boot (a generator, from its early folder so a default in /etc doesn't win;/etc/omamobile/charger-mode-disableturns 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_power4, 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 wheremulti-user.targetis 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
uname -r): 7.3.0-rc6-omamobile-push1-g0e3da55c9e9f (the release kernel g2219cc6cda77 plus the RTC fix)Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpassestests/packagespasses (or the packages I touched: omamobile-device-cheetah)versionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
androidboot.mode = "charger"),omamobile-charger.targetactive,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: poweroff5 s later, the phone stayed off.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)tools/phone-smokereportphone-smoke: cheetah
Kernel
7.3.0-rc6-omamobile-push1-g0e3da55c9e9f, tools ate19ea6c, 2026-11-09T08:54Z.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