Closed 0x1a8510f2 closed 1 year ago
Did you grant the required permissions which at minimum includes Nearby devices?
Thanks for the quick reply!
I've granted the following to the WearOS app:
Nearby Devices
Network
Notifications
Sensors
I also got the ADB logcat for the WearOS app which is included below starting from the point where I selected the watch in the system Bluetooth dialog. The MAC address and date/time has been edited for privacy.
Some additional research indicates that this is likely caused by the fact that the WearOS/Google app (WearOS depends on the Google app) are installed as non-system/third party apps: https://developer.android.com/reference/android/Manifest.permission#BLUETOOTH_PRIVILEGED. I assume an extra permission could be added to GrapheneOS much like the network permission to solve this? Or is there any way to fix this without any changes needed to Graphene?
Start by trying giving Nearby Devices to Play services too.
Well, that was simple enough!
WearOS App:
com.google.android.wearable.app
Google App:
com.google.android.googlequicksearchbox
Google Play services App:
com.google.android.gms
(Eek)
These are likely not the minimum required, but they work. Thanks for the help!
I have attempted to pair the same watch with 3 phones total. 2 phones with their stock OS (one of which is signed into the same Google account as the GrapheneOS phone) pair successfully every time. Meanwhile, the GrapheneOS phone always fails with the following screen:
Exiting and re-opening the WearOS app shows a screen as though the watch was paired but without any data filled in in the UI. The watch remains on the "continue setup on your phone" screen and eventually times out.
I will try to get a logcat from the WearOS app but I'm not sure how do debug further.