Repository navigation
omamobile-device-tegu 0.2.20: double tap wakes the palmtop from sleep - #779
Merged
Merged
Conversation
The 7 Pro's touch-wake rule (device-cheetah 0.1.55, derekross#730) for the 9a, whose touchscreen is the same Synaptics S3908 on the same synaptics-tcm driver: linux-omarchy-mobile#248, in kernel-2026.11.13, makes the touchscreen wakeup capable and leaves it off, and this rule turns it on. On a kernel without derekross#248 there is no power/wakeup and the rule does nothing. 0.2.19 is claimed by open pull requests (derekross#766, and derekross#483's rebase).
Owner
|
Thank you, this is a nice small one. The rule line matches the 7 Pro's byte for byte, the test compares the two only when cheetah's package is next to it, and #248 is in kernel-2026.11.13 as you say. On a default 9a, with auto-sleep off, nothing changes until the owner turns auto-sleep on, and then a double tap wakes it as on the 7 Pro. Two things for the record, neither holding this up:
If you have one, a I'll merge this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 7 Pro's double tap from sleep (#730), for the 9a. The 9a's touchscreen is the same Synaptics S3908 on the same
synaptics-tcmdriver, so linux-omarchy-mobile#248 (inkernel-2026.11.13) gives it the samepower/wakeup, off by default, and the same rule line turns it on.What
vendor/udev/rules.d/70-omamobile-touch-wake.rules: the 7 Pro's rule line, with a comment that names the 9a. On a kernel without DEVICES: the Pixel 9a's charging, AoC, speakers, sensors, NFC and cameras on by default, fingerprint opt-in, GNSS to testing #248 there is nopower/wakeupand it does nothing.test/all: the rule is staged, holds that one line, and matches the 7 Pro's line when the 7 Pro's package is beside it (a build of this package alone, astools/phone-install-packagedoes, skips the comparison).Tested
On my palmtop (Pixel 9a), 2026-11-14, the package installed from this branch with
tools/phone-install-package, on a test kernel: the publishedomamobileat82f31d3a7plus kernel #247, kernel #232 atfef165e74and the sleep guard on for zumapro (7.3.0-rc6-omamobile-push1-g716f6d8ef355). omamobile-shell 0.2.127 (double tap and sleepd running).power/wakeuponspi0.0readenabled, set by the rule; nothing set by hand.systemctl suspend -i, a 10-minute RTC alarm as a backstop; wakes by the modem went straight back to sleep). The owner double-tapped the dark screen: the sleep ended on the touchscreen's interrupt (pm_wakeup_irq55,spi0.0) after 90 s, and the panel was lit 3 s later (bl_power0). He saw the screen light "maybe a half second" after the tap.test/all,tests/allandtools/pr-checkpass.The owner was at the palmtop for the tap; the rest ran without him, as he has asked.
Not tested
omamobile-sleepd) putting the palmtop back to sleep after a wake that lit nothing: with the modem up the 9a's own inhibitor holds, so sleepd never slept it here.This doesn't turn auto-sleep on for the 9a (no
auto-sleep-default): that waits for the 9a's suspend to be verified as the 7 Pro's was, with #765 among the open points.