Repository navigation
Conversation
… charger driver The merged max77779-charger driver has charge inhibit and no end threshold, so the charge limit wrote nothing. The script now switches charge_behaviour between inhibit-charge and auto by the battery's capacity, from the limit to 5 below, and udev runs it on every battery change.
With the kernel branch tegu-dt-aoc the device tree enables Trusty, the GSA and the AoC, so the AoC start gets its wants link and answers to omamobile-aoc.service, which the sensor proxy and the fingerprint service name. Trusty and the TAS2572 amplifier driver are blacklisted too, and the amplifiers load once the AoC is online.
This was referenced Oct 31, 2026
Contributor
Author
|
Speaker confirmed by ear on this package's boot-time AoC start with linux-omarchy-mobile#162's kernel: a 5 s tone through the |
Owner
|
Merged as part of #235's squash (0.2.1 through 0.2.3 together). Thanks! |
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…, the AoC and NFC at boot, and the 9a's own setup-system (derekross#235) Merges the stack derekross#230, derekross#234 and derekross#235: - 0.2.1 (derekross#230): the charge limit works with the published max77779 charger driver, which offers inhibit rather than an end threshold; the script handles both and always falls back to auto on a missing or bad file. While the phone sleeps nothing runs the script (the battery's change events come from a freezable 30 s poll), so a phone asleep on the charger below the limit charges past it until it wakes. - 0.2.2 (derekross#234): the AoC starts at boot from the device tree, hang-safe, gated on the AoC node, under the omamobile-aoc.service alias so the sensor proxy orders after it; the amplifiers load after the AoC is online. Speaker protection stays cheetah-only. - 0.2.3 (derekross#235): NFC at boot, gated on a node that names its clock; the existing sleep hook stops polling before s2idle. The 9a gets its own omamobile-setup-system. Closes derekross#230, closes derekross#234.
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.
Stacked on #230 (0.2.1, the charge limit); the second commit is this one.
With linux-omarchy-mobile#162 the 9a's device tree enables Trusty, the GSA and the AoC. So the AoC start now:
ConditionPathExists=/sys/bus/platform/devices/154b0000.aocskips it on a device tree without the node;omamobile-aoc.servicethrough an alias link. The sensor proxy (Requires=/After=), the fingerprint service and speaker protection all name that unit, so they now order after the 9a's AoC as they do on the 7 Pro;snd_soc_tas2781_i2ctoo, so only the script loads them, in order: the amplifiers load after the AoC is online, so the card finds its back end.The tests now check the wants link, the alias, the condition and the longer blacklist, and
test/aoc-startchecks the new last step. The README section "The AoC start at boot" replaces "ships disabled".Tested on the palmtop today with #162's kernel (
7.3.0-rc6-omamobile-push1-g922812d75006) and this package installed. At boot, with nothing run by hand:omamobile-tegu-aoc.service: active, success, Namesomamobile-tegu-aoc.service omamobile-aoc.service.google,tegu-aoc-snd-cardregistered.omamobile-sensor-proxy.service: active, with accel, light, proximity, compass and gyro.Two things on the palmtop itself, not in the package. The bring-up image had
/etc/systemd/system/omamobile-aoc.serviceandomamobile-sensor-proxy.servicemasked to/dev/null, and I removed those two masks. And while the palmtop still boots its integration kernel, where the bring-up script owns the AoC, a local drop-in withConditionKernelVersion=!…-dirtykeeps this unit off there. A fresh install has neither.Speaker playback isn't in this run; the next one plays a quiet tone through the UCM profile.
test/allandtools/pr-checkpass.