Enhance WearOS features and fix service stubs and bugs

[samuel-asleep]

This pull request introduces a new Wearable settings section and notification bridging support for Wear OS devices, along with related permission, UI, and infrastructure changes. The main themes are: adding a user-facing Wearable settings panel (including an auto-accept Terms of Service option), implementing a notification listener service to bridge notifications to wearables, and updating permissions and manifest declarations to support these features.

Wearable Settings Integration:

• Added a new WearableFragment (WearableFragment.kt) and navigation entry to allow users to configure Wearable-related settings, including a toggle for automatically accepting the Wearable Terms of Service. The settings are wired through WearablePreferences for persistence and retrieval. [1] [2] [3] [4] [5]
• Updated the main settings fragment (SettingsFragment.kt) to include a Wearable entry and handle navigation to the new Wearable settings screen. [1] [2]

Terms of Service Flow:

• Modified the Wearable Terms of Service activity (TermsOfServiceActivity.kt) to auto-accept if the user has enabled the setting, or otherwise show an explicit dialog for user consent.

Notification Bridging:

• Introduced WearableNotificationService, a NotificationListenerService that bridges Android notifications (excluding ongoing/self/unclearable ones) to connected Wear OS peers via the microG Wearable message transport. This includes encoding/decoding helpers and UID management.
• Declared the notification service and updated existing wearable service declarations in the manifest, ensuring correct permissions and android:exported attributes.

Permissions and Manifest Updates:

• Added required Bluetooth, notification, and phone call permissions to the manifest to support Wear OS and notification features.
• Marked wearable-related services as android:exported="true" for proper service exposure. [1] [2]

Settings Infrastructure:

• Extended the SettingsContract and SettingsProvider to support Wearable settings, including querying and updating the auto-accept TOS preference. [1] [2] [3] [4] [5]

These changes collectively provide a user-configurable Wearable settings panel, allow for seamless notification forwarding to Wear OS devices, and ensure proper permissions and data persistence for these new features.

fixes #2843

[Tamriel]

Why did you close this?

[samuel-asleep]

Why did you close this?

I taught the repo was inactive , I'll reopen it !!

[samuel-asleep]

Last update on the repo was 2weeks ago so I just assumed !

[mar-v-in]

Have you verified this on a real device to pair a wearable? Which device/wearable/Android version?

[samuel-asleep]

Have you verified this on a real device to pair a wearable? Which device/wearable/Android version?

I've tried verifying with a wearOS emulator but my pc is too weak to run it , am currently looking for other alternatives like a cloud emulator or smt similar , I'll update you once I verify and it's working

[mar-v-in]

So you're asking for inclusion of code into microG and make bold claims that it solves an issue without even testing it?

You shouldn't test this with an emulator, because emulators are not real devices and microG is meant to run on real devices. Even if it fixes the issue for emulators, that might be insufficient to fix it on real devices.

Also, there is no disclosure on the use of LLM in this pull request. Please declare which LLMs you used to generate code. It has always been good practice to credit the authors when using other people's code.

[samuel-asleep]

So you're asking for inclusion of code into microG and make bold claims that it solves an issue without even testing it?

You shouldn't test this with an emulator, because emulators are not real devices and microG is meant to run on real devices. Even if it fixes the issue for emulators, that might be insufficient to fix it on real devices.

Also, there is no disclosure on the use of LLM in this pull request. Please declare which LLMs you used to generate code. It has always been good practice to credit the authors when using other people's code.

You're right — I shouldn't have implied that it fully solves the issue without validating on a real device. That was my mistake.

I currently don't have access to a WearOS device, and my system isn't capable of running the emulator reliably. I'll avoid making definitive claims until I can properly test it on real hardware.

If required, I'm happy to mark this as draft or rework it once proper device testing is done.

Regarding LLM usage: I did not copy code from external sources. The changes were written by me, though I used tooling assistance for refactoring and reviewing. Let me know if you’d like me to explicitly document that in the PR.

Thanks for the feedback.

[Tamriel]

@samuel-asleep I would like to test it if you provide an apk file.
( I could not build myself, because the build crashed on my machine. )

[samuel-asleep]

@Tamriel Here's a pre-built artifact from CI: https://github.com/samuel-asleep/GmsCore/actions/runs/22588226029/artifacts/5726384849

The download is a zip containing:

• play-services-core APK (the main GmsCore app — install this)
• vending-app APK (Play Store stub — optional)

Note: You'll need to be signed into GitHub to download CI artifacts. This build has not been tested on real hardware yet, so any feedback on pairing behavior with your watch would be very valuable.

[Tamriel]

Here's a pre-built artifact from CI: https://github.com/samuel-asleep/GmsCore/actions/runs/22588226029/artifacts/5726384849

Thanks a lot. Sadly, the install fails due to missing certificates in the apk.

[samuel-asleep]

Here's a pre-built artifact from CI: https://github.com/samuel-asleep/GmsCore/actions/runs/22588226029/artifacts/5726384849

Thanks a lot. Sadly, the install fails due to missing certificates in the apk.

Thanks for the feedback am still working on it !!

[samuel-asleep]

Here's a pre-built artifact from CI: https://github.com/samuel-asleep/GmsCore/actions/runs/22588226029/artifacts/5726384849

Thanks a lot. Sadly, the install fails due to missing certificates in the apk.

I've just ordered a smartwatch so I can test this properly on real hardware. If everything goes smoothly, I should be finished by next week—possibly sooner

[samuel-asleep]

@Tamriel can you please help me test again

https://github.com/samuel-asleep/GmsCore/actions/runs/22958844187/artifacts/5872623356