Anonymous
You don't own your watch, you (...) 09/30/26(Wed)10:04:23 No.109946795

File: you vill own nussing.jpg (528 KB, 2738x1825)

528 KB JPG

You don't own your watch, you rent it from Google Anonymous 09/30/26(Wed)10:04:23 No.109946795

>have a OnePlus watch running Wear OS 6
>want the Pixel Watch faces
>follow the guide, sideload the official Google APK over adb
>"Success"
>faces don't show up in the picker
>try forcing one with Google's own debug broadcast
>"set-watchface failed. Watch face package is not installed."
>it's literally installed, pm list packages shows it
>check logcat
>WearServices: [WFInfoResolver]Blocked watch face WatchFaceId[com.google.android.wearable.watchface.rwf, ...ChronographWatchFaceService]
>Blocked.
>not incompatible, not crashing, BLOCKED
>meanwhile OPPO's preinstalled faces use the exact same old AndroidX watch face API and run fine
>so it's not a technical limitation, it's a gatekeeper
>Google Play Services on YOUR watch decides which code-based faces you're allowed to run
>Pixel Watch owners run these same faces no problem
>on non-Pixel watches, faces from outside get silently filtered
>no error on the watch, no notice, nothing
>only way to find out is adb logcat
>and since January 14 2026 legacy faces can't even be installed from the Play Store anymore

Google calls it "moving to the Watch Face Format for battery life and security." Maybe. But a system component that silently blacklists apps you sideloaded yourself, while OEM apps using the same API are allowed, isn't about battery. You don't own your watch, you rent it from Google.