Skip to content

feat(wearable): WearOS foundation — TOS, client APIs, Bluetooth RFCOMM - #3702

Open
rwchaneyjr wants to merge 1 commit into
microg:masterfrom
rwchaneyjr:cursor/wearos-support-foundation-9c5c
Open

feat(wearable): WearOS foundation — TOS, client APIs, Bluetooth RFCOMM#3702
rwchaneyjr wants to merge 1 commit into
microg:masterfrom
rwchaneyjr:cursor/wearos-support-foundation-9c5c

Conversation

@rwchaneyjr

Copy link
Copy Markdown

Unblock companion pairing and wire the Data Layer for Wear OS work on #2843/#2444:

  • TermsOfServiceActivity shows accept/decline instead of immediate cancel
  • NodeApi/DataApi/MessageApi delegate to WearableServiceImpl (no more stubs)
  • BluetoothConnectionThread uses researched WearableBt/Flow/Flow15 UUIDs
  • enableConnection starts WearableBt client when config.address is a BT MAC
  • Unit tests guard against known-wrong RFCOMM UUIDs from prior PRs

This is foundation work; stock notification/media bridging still needs device-verified companion protocol work.

Unblock companion pairing and wire the Data Layer for Wear OS work on microg#2843/microg#2444:

- TermsOfServiceActivity shows accept/decline instead of immediate cancel
- NodeApi/DataApi/MessageApi delegate to WearableServiceImpl (no more stubs)
- BluetoothConnectionThread uses researched WearableBt/Flow/Flow15 UUIDs
- enableConnection starts WearableBt client when config.address is a BT MAC
- Unit tests guard against known-wrong RFCOMM UUIDs from prior PRs

This is foundation work; stock notification/media bridging still needs
device-verified companion protocol work.

Co-authored-by: Robert Chaney <rwchaneyjr@users.noreply.github.com>
@rwchaneyjr

Copy link
Copy Markdown
Author

Summary
Foundation work for Wear OS support in microG (#2843 / #2444).

Changes
TOS screen — shows accept/decline instead of instantly canceling (unblocks Galaxy Wearable setup)
Client APIs — NodeApi, DataApi, MessageApi now work instead of throwing errors
Bluetooth RFCOMM — connects over WearableBt / Flow / Flow15 with correct UUIDs
Not included yet
Notification mirroring, media controls, and full pairing on a real watch still need more work.

Tested
Unit tests for Bluetooth RFCOMM UUIDs pass.

Related: #2843, #2444

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants