Repository navigation
omamobile-device-cheetah 0.1.59: hold suspend with the modem up again - #794
Merged
Merged
Conversation
The final M6 check on kernel-2026.11.15 with omamobile-modem 0.1.26 and device-cheetah 0.1.58 (twenty auto-sleeps with the modem up, an RTC alarm every minute) entered and woke all twenty sleeps without a failure or a storage error, but mobile data stopped answering from the first timer wake on and stayed down with the phone awake (CPIF logging 'Reserve doorbell interrupt: PCI not powered on' while the link came up again and again), while the modem still reported its bearer up. The development channel now turns that on by default, so take the device's declaration back out: without it omamobile-modem's inhibitor keeps the phone awake while the modem is up, as before #791. Sleep with the modem off is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross
added a commit
that referenced
this pull request
Nov 15, 2026
…797) * AGENTS, DEVICES: sleep with the modem up is held on the 7 Pro again #791 described sleep with the modem up as on by default on the 7 Pro. #794 took the device's declaration back out after the twenty auto-sleeps on kernel-2026.11.15 lost mobile data, so the AGENTS entry goes back to its earlier wording, with one sentence on what passed and what didn't, and DEVICES' suspend cell and note say the gap is open again. The rule itself is the one from before #791: with the modem up nothing passes the inhibitor except the maintainer's attended test on the charger. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * DEVICES: the Modem row says the modem-up sleep is held again too Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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 20-sleep check with the modem up on kernel-2026.11.15 lost mobile data from the first timer wake on (all 20 sleeps entered and woke; data stayed down with the phone awake, the modem reporting its bearer up). Since #791 the development channel turns modem-up sleep on by default for the 7 Pro, so this removes the device's
suspend-verifieddeclaration: the modem's inhibitor keeps the phone awake with the modem up again, as before. Sleep with the modem off is unchanged. The cause is open (lead: this install unloads Wi-Fi around every sleep, which re-probes the second PCIe controller).Not to merge or publish without the maintainer's go.
🤖 Generated with Claude Code