WIP: watch pairing implementation by deadYokai · Pull Request #3204 · microg/GmsCore

deadYokai · 2025-12-25T11:26:47Z

Stage: Paired

full pair process (still with bugs)
test watchfaces
test sensors
refactor/cleanup

recommended todo:

fix long pair time / check thread races
make RPC requests better
polish/clean/refactor code
make working account auth ( 🫪 blocked, need implement SMARTDEVICE_SOURCE_DIRECT_TRANSFER (part of com.google.android.gms.smartdevice))

working:

notifications sync
watchface change

Added some callbacks Added feature list to WearableService.java Added android:exported="true", required by android 12, for TOS only, cuz i don't know if in other needed true or false

deadYokai · 2025-12-28T23:29:01Z

now maybe fixes #2444 ,

at least my Mobvoi Health going to pair screen (after TOS)

but code in rough state for now

deadYokai · 2025-12-29T08:10:03Z

now, my device is trying to pair via Mobvoi Health

…dRequest`, `sendMessage` prepairing ConnectionConfiguration to bluetooth stuff, to proper pair devices filled some Parcable classes

and handshake some bluetooth stuff

deadYokai · 2025-12-31T04:05:15Z

now need to implement openChannel method (wip)

for now only rfcomm client supported

ble, network, server is not implemented

still failed to pair

ale5000-git · 2026-01-04T22:18:23Z

@deadYokai
Please look at the errors here: https://github.com/microg/GmsCore/actions/runs/20686657931?pr=3204

deadYokai · 2026-01-05T01:28:01Z

@ale5000-git as i mentioned before

After 465f5f0 requires merging PR microg/Wearable#3 and pushing to maven

deadYokai · 2026-01-05T01:34:51Z

or i can try to move https://github.com/microg/Wearable/ into GmsCore repo and get rid of dependence

https://mvnrepository.com/artifact/org.microg/wearable/0.1.1

ale5000-git · 2026-01-05T02:19:31Z

Sorry I missed that point, then we have to wait for @mar-v-in for the decision of this thing.
In the meanwhile go ahead with the other parts you are working, thanks.

mar-v-in · 2026-01-05T07:16:23Z

I'd suggest to entirely move the content of the microg/Wearable repo into play-services-wearable/core module in this repo and then we can archive the microg/Wearable repo entirely.

and some bluetooth changes

deadYokai · 2026-01-05T15:25:27Z

just sharing with good looking logs, in my opinion (logcat)

P.s. still not paired yet

some Bluetooth changes moved some functions from WearableImpl to MessageHandler

- and some DataItem changes

deadYokai · 2026-02-06T01:58:31Z

i cannot pinpoint why connection closing when channel tries to open

can anybody help me? like some logs maybe logs from watch (i cannot capture from my)?

teccheck · 2026-02-27T15:27:02Z

Just looked at your code quickly, and you're the first who even got the Bluetooth UUID right. Looks very promising, keep it up. 👍

I'll try to test your code, as soon as I can with my Pixel Watch.

EDIT: If you need more information about the protocol, hit me up. I'm happy to help :)

Replace the Wire 1.x wearable binary with Apache-2.0 source from microg/Wearable 137a09912aaa6d6fbbe6689ecf588059b89ae7a2 and generate its messages with GmsCore's Wire 6.4.6. Use generated adapters for socket framing. Reject negative frame lengths before allocation. Expose requiresResponse and senderRequestId using the experimental schema referenced in microg#3204. Document the source and limits; no setup response or FRP status is fabricated. Validated locally: wearable-core assembleDebug, testDebugUnitTest (12 tests, zero failures), lintDebug. Six new fixture tests cover legacy encoding/framing, RPC correlation fields, unknown fields and malformed frames. No hardware pairing validation; not a completed bounty submission.

deadYokai · 2026-09-30T09:50:40Z

i did it

woahwhattheheck · 2026-10-01T18:17:48Z

At current PR head eaf3b07, the consent UI and service state appear disconnected: TermsOfServiceActivity returns acceptance extras without persisting them, the normal getConsentStatus path returns hasTosConsent=true (its exception path returns status 13 and false flags), and addAccountToConsent returns success without recording consentGranted. That can make a declined or fresh setup indistinguishable from an accepted one when the companion asks for status. The consent files cited here are unchanged from the previously inspected 7dc49aac snapshot; the intervening PR commit changes only WearableImpl.java and Bluetooth connection files.

For a focused persistence patch, is there an existing reference or redacted Binder/parcel capture that establishes:

The meanings of AcceptTermsRequest fields 2–8 and RecordTermConsentRequest fields 1–6, which currently retain unk* names.
The parcelable item type expected in ConsentResponse.accountConsentRecords.
The intended account/node scope and the relationship between the activity result and getConsentStatusForRequest's string field.

The useful regression cases would be fresh state, explicit acceptance, decline/revocation, process restart, and isolation between distinct account/node contexts.

jun10r4lm31d4 · 2026-10-02T21:59:43Z

i did it

You cloud add google account to wear? Here not possible set lockscreen pin and add google account

The output stream API accepts length=0, but the no-progress guard returned before its existing empty-final-frame path. Keep waiting when input is unavailable, while allowing an exhausted zero length through the existing send and ACK lifecycle. One production guard and one regression in the existing ChannelBehaviorTest. The complete current ChannelStateMachine and candidate test compiled against the retained Wear runtime. Only zeroLengthSendEmitsFinalFrameAndClosesOnlyAfterAck ran under offline Robolectric (SDK 29): unchanged source failed because it emitted 0 frames; candidate passed. With offset=0 and length=0, it performs no transport read, emits one empty final frame, waits for the ACK without another pump send, then clears the timeout and closes the sender. The test uses a recording manager/transport; it does not assert physical-watch transport, APK acceptance or whole-channel closure. Nonzero offsets retain existing skipBytes behavior. Existing timeout/retry semantics remain in place; this change does not establish exactly-once delivery across timeouts. Additive integration-branch continuation on ea71500; preserves the initialization callback and asset storage fixes. Original Wear microg#2843 / PR microg#3204 and 998E integration ownership remain canonical. No upstream merge or bounty payment claim. Attribution: ASTRA-3C24-BH, GPT-6 Astra Pro, ChatGPT cloud harness. Coordination: https://tokenjunkielabs.slack.com/archives/C0BU51F1PL3/p1791105968382479

deadYokai · 2026-10-07T19:53:55Z

@jun10r4lm31d4

You cloud add google account to wear? Here not possible set lockscreen pin and add google account

i'm working on wifiSync where it crashes when connecting to google account, maybe it fix this

deadYokai · 2026-10-08T22:37:23Z

currently account connection not working, need to implement SMARTDEVICE_SOURCE_DIRECT_TRANSFER

deadYokai · 2026-10-08T22:46:16Z

@teccheck @ale5000-git could you give it a quick test?

Added bare layout for wearable TOS

e5668ac

Added some callbacks Added feature list to WearableService.java Added android:exported="true", required by android 12, for TOS only, cuz i don't know if in other needed true or false

deadYokai changed the title ~~Added bare layout for wearable TOS~~ WIP: wearable TOS Dec 26, 2025

deadYokai added 2 commits December 27, 2025 02:20

Added founded callbacks to IWearableCallbacks.aidl

5ae5054

Added missing classes (stubs) + aidls

30a2cad

deadYokai marked this pull request as draft December 27, 2025 05:30

Added some aidl files and consent stuff

75029a8

capability, connectionConfiguration rework

54f8fc7

deadYokai changed the title ~~WIP: wearable TOS~~ WIP: road to pair my TicWatch Dec 29, 2025

deadYokai added 2 commits December 30, 2025 08:41

added services getNodeId, sendRequest and option variants of `sen…

f9c59c3

…dRequest`, `sendMessage` prepairing ConnectionConfiguration to bluetooth stuff, to proper pair devices filled some Parcable classes

finaly successful connection

465f5f0

and handshake some bluetooth stuff

Some channel manager things

af855ec

still failed to pair

Wearable lib relocation

63a77a0

and some bluetooth changes

deadYokai added 6 commits January 9, 2026 18:25

updated NodeDatabaseHelper

4e22cf9

some Bluetooth changes moved some functions from WearableImpl to MessageHandler

fix lint

ab5c920

updated scary Bluetooth things

f9244e2

- and some DataItem changes

Node & Assets db update

a261776

reworked Bluetooth

8544d12

update code

1eacce1

implement few unimplemented methods

5012986

hitchman007 mentioned this pull request Sep 28, 2026

NEXORA QA: WearOS support #2843 — staged implementation hitchman007/GmsCore#1

Draft

working pairing

7dc49aa

deadYokai marked this pull request as ready for review September 30, 2026 09:51

fix some bluetooth leaks

eaf3b07

ToS and consents

7e63384

This was referenced Oct 4, 2026

Wear integration: preserve callback delivery across listener removal woahwhattheheck/GmsCore#5

Merged

Retain PR author and source identity in bounty audits woahwhattheheck/bounty-concierge#705

Merged

deadYokai added 15 commits October 7, 2026 23:00

remove setConnectionAlive

3a916d2

Merge branch 'master' into wearable_tos

8a75329

fix github resolve FEATURES duplicate

8ffe96f

update features

283d34b

added WearableWifiService class

d4b34a8

onDestroy needs BLUETOOTH_SCAN permission

3027747

syncRecordToAll public for WearableWifiService

3bb9bb1

wifiSync

76b021c

AppRecommendations & AppTheme

6451d72

RPC and Assets update

a0c84b7

update some parcels

548c59d

some EAP and FastPair (not tested)

cac506c

some logs

29d82b5

getFdForAsset update

fb23044

add warning log for DummyService

ef2c957

Conversation

deadYokai commented Dec 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

deadYokai commented Dec 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

deadYokai commented Dec 29, 2025

Uh oh!

deadYokai commented Dec 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ale5000-git commented Jan 4, 2026

Uh oh!

deadYokai commented Jan 5, 2026

Uh oh!

deadYokai commented Jan 5, 2026

Uh oh!

ale5000-git commented Jan 5, 2026

Uh oh!

mar-v-in commented Jan 5, 2026

Uh oh!

deadYokai commented Jan 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

deadYokai commented Feb 6, 2026

Uh oh!

teccheck commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

deadYokai commented Sep 30, 2026

Uh oh!

woahwhattheheck commented Oct 1, 2026

Uh oh!

jun10r4lm31d4 commented Oct 2, 2026

Uh oh!

deadYokai commented Oct 7, 2026

Uh oh!

deadYokai commented Oct 8, 2026

Uh oh!

deadYokai commented Oct 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

deadYokai commented Dec 25, 2025 •

edited

Loading

deadYokai commented Dec 28, 2025 •

edited

Loading

deadYokai commented Dec 31, 2025 •

edited

Loading

deadYokai commented Jan 5, 2026 •

edited

Loading

teccheck commented Feb 27, 2026 •

edited

Loading