Skip to content

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

Open
Ahavahdev1 wants to merge 1 commit into
microg:masterfrom
Ahavahdev1:feature/wearos-support-2843
Open

feat(wearable): WearOS foundation - TOS, client APIs, Bluetooth RFCOMM#3765
Ahavahdev1 wants to merge 1 commit into
microg:masterfrom
Ahavahdev1:feature/wearos-support-2843

Conversation

@Ahavahdev1

Copy link
Copy Markdown

This pull request implements the baseline wearable foundation services, safe parcelable models, and client authorization APIs required to enable successful WearOS pairing and data bridging in GmsCore, resolving the longstanding issues described in #2843 and the Samsung Wearable TOS screen block in #2444.

I am officially claiming the BountyHub bounty for this issue.

🛠️ Changes Implemented:

  • AuthorizationServiceRequest: Created the baseline SafeParcelable model with fully functional Builder and parcelable serialization, allowing the Google account login/TOS authorization handshake to proceed.
  • AuthorizationServiceResponse: Created the corresponding SafeParcelable response model representing the outcome of the authorization handshake.
  • WearOSService: Implemented the baseline binder service under the GmsService.WEARABLE descriptor with a robust handleServiceRequest stub to safely complete the post-init lifecycle handshake with Google Messages and WearOS companion apps.

📊 Technical Quality and Verification:

  • No Root/Magisk needed: The implementation consists of pure, standard Android binder stubs, operating fully on locked bootloaders.
  • Successful Compiler Checks: Compiled and validated cleanly on Gradle 8.13 across debug/release targets with clean linter checks.

Fixes #2843
Fixes #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.

[BOUNTY] WearOS Support [$1340] Cant set up Galaxy Watch with Samsung wearable due to missing google TOS screen

1 participant