Watchface Activation for Samsung recent watch (waiting for tests to confirm it works before merge) - #5042
Open
Philoul wants to merge 2 commits into
Open
Watchface Activation for Samsung recent watch (waiting for tests to confirm it works before merge)#5042Philoul wants to merge 2 commits into
Philoul wants to merge 2 commits into
Conversation
Philoul
changed the title
|
27 tasks
Philoul
changed the title
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
1 participant
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.
On newer "Factory Built" Wear OS 5+ Samsung watches, the on-watch picker no longer offers code-based watch faces, so CustomWatchface may be impossible to activate at all. This adds a fallback: opening CWF's settings from the AAPS menu now sends a broadcast asking Samsung SysUI to activate and open the editor for CustomWatchface, Digital or Circle
This uses a standard, Samsung-authorized entry point (exported=true, auto-granted normal permission) — the mechanism itself is legitimate and documented as callable by third-party apps, only the specific intent extra key was found by inspection rather than official docs.
Fully safe on non-Samsung watches or older Samsung builds: the receiver is checked before sending, and the fallback is the exact existing behavior (nothing sent, screen shown normally).
I'm looking for tester... (an owner of recent Galaxy Watch no more compatible)
It works with my GW4, and I want to check if it also work with latest GW7, GW8 ...