Add optional Ponte Android remote service commands - #10347
Open
LucasOl1337 wants to merge 1 commit into
Open
Conversation
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.
Ponte lets an Android phone control an Omarchy desktop over Tailscale, with a touchpad, keyboard, window controls and live views of physical monitors. This draft proposes explicit, optional install/remove commands; it does not add Ponte to the default installation.
omarchy install service ponteinstalls the package and showsponte setup/ponte installas the next steps. It does not start a service or change Tailscale configuration. Removal tears down Ponte's managed user services before dropping the package and preserves private configuration and recordings.The companion package proposal is omacom/omarchy-pkgs#316. It pins Ponte v0.1.0-alpha.1 and contains no APK, certificate or pairing key. English is the app default, with an optional saved Portuguese preference.
I read plans/remote.md and its Sunshine/Moonlight direction. Ponte's scope is phone controls and a limited monitor view; MJPEG tops out at 10 fps and carries no system audio. This draft is for feedback on whether that optional scope belongs here.
The project page, presentation and evidence report include screenshots and measured results. Live view, fullscreen and saved pairing worked on a Redmi development build. The public portable build passes source and signed-APK fixture tests; a clean physical-device install of that build, an Android recording retest, and cellular/WAN measurements remain open. First-time setup still needs an APK built for the user's PC, a pairing key and existing
/dev/uinputaccess.Validation: seven focused shell cases, CLI metadata/routing suite, safe help output, Bash syntax and diff checks passed. The package was built from the published archive using
makepkg --nodeps(Node is provided by mise); its file layout and extracted CLI were checked with temporary XDG state and service-command stubs. A clean chroot build is still pending. The running desktop was not changed. Broader clean-session acceptance remains a prerequisite for requesting merge.@dhh, I'd appreciate your take on the scope before developing the upstream integration further.