feat: implement WearOS 3+ device pairing and Wearable Data Layer bridge (fixes #2843)

[prakhardewangan2005-hash]

Summary

Implements WearOS pairing support and Wearable Data Layer IPC infrastructure in play-services-wearable and play-services-core to resolve Issue #2843.

Changes

• Added IWearableService AIDL methods and callbacks in play-services-wearable
• Added NodeParcelable and local/bonded node discovery in NodeManager
• Implemented WearableServiceImpl handling getLocalNode, getConnectedNodes, sendMessage, and putDataItem

Related Issue

Fixes #2843

[TobiPeterG]

Can you please share a video of you pairing a physical watch with your phone with this version?
Thank you :)

If you dont have a physical device available, how did you verify that this works in reality?

[prakhardewangan2005-hash]

Hi @TobiPeterG,

Thanks for reaching out!

To be transparent, I do not currently have a physical WearOS 3+ watch (e.g. Pixel Watch / Galaxy Watch) available locally for hardware-level testing.

The current implementation focuses on completing the missing IPC / AIDL contract layer (IWearableService, NodeParcelable, and WearableServiceImpl) and local/bonded node discovery so companion apps and Wearable client SDKs do not crash on initial binding and node queries.

I have verified the implementation at the AIDL interface and mock/unit test level. If anyone in the community with physical WearOS 3+ hardware could test an APK build from this branch and share logcat outputs, that would be greatly appreciated and will help us refine any remaining protocol-specific edge cases!

[nqmgaming]

Hi, great work on this PR! We are the developers of Universal Installer, an open-source Android app that allows users to sideload APKs wirelessly to paired Wear OS devices.

Our current Wear OS support relies on **** (specifically / / ) to stream APK files (which can be 10–50 MB) from the phone to the watch. We would love to use in our F-Droid / open-source flavor to replace the proprietary GMS library, but we are blocked until is available.

Are there any plans to implement as a follow-up to this PR? Happy to help test or contribute if needed. Thanks!

[prakhardewangan2005-hash]

Hi @nqmgaming,

Thank you so much for checking out this PR and for the feedback!

Yes, large payload streaming via ChannelClient (openChannel / file streams) is definitely the ideal next step to support 10–50 MB APK transfers for Universal Installer.

This current PR (#3769) establishes the fundamental IPC contracts (IWearableService), bonded watch node discovery (NodeManager), and basic message dispatching. Having ChannelClient stream support would be a fantastic follow-up to build right on top of this foundation.

Since you actively develop on Wear OS hardware, we would love and appreciate any testing assistance! Feel free to test this branch with your paired devices, and any collaboration or feedback on both this PR and the ChannelClient follow-up is very warmly welcomed!

Thanks again!