Wear OS support: TOS, Bluetooth RFCOMM, notification/media/call bridges - #3756
Open
Gurjotharika wants to merge 1 commit into
Open
Wear OS support: TOS, Bluetooth RFCOMM, notification/media/call bridges#3756Gurjotharika wants to merge 1 commit into
Gurjotharika wants to merge 1 commit into
Conversation
…ion/media/call bridges. Companions currently hang on a missing TOS activity and only get a TCP debug socket, so modern watches cannot pair. This wires the WearableBt RFCOMM UUIDs, client Node/Data/Message APIs, and phone-side notification/media/call controls so Wear apps can talk to companions on microG. Co-authored-by: Cursor <cursoragent@cursor.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
2 participants
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.
Summary
TermsOfServiceActivityforcom.google.android.gms.wearable.TOS(Galaxy Watch / companion hang), Bluetooth RFCOMM using WearableBt/Flow/Flow15 UUIDs instead of generic SPP, and restore of enabled connection configs.NodeApi/DataApi/MessageApithroughGmsConnectorso Wear apps can talk to companion apps (local node, connected nodes, data items, messages, listeners).NotificationListenerService+ Data/Message paths), media session control, and call answer/end/silence, plus a Wear OS settings page and self-check Bluetooth/call permissions.Test plan
WearableBt(not SPP) andgetConnectedNodesreturns the watchMessageApi.sendMessage/DataApi.putDataItemreaches the companion app on the phoneWearableBtUuidsTest(UUID is not SPP, MAC detection, notification payload round-trip)