GrapheneOS not letting my Galaxy Watch work?

ForeverGOS I thought of giving GPS all the permissions, including the notifications one that only launcher has to test

The device & app notifications permission will be necessary when you use the watch to receive notifications, but I doubt that the app not having that permission would cause it to not connect.

ForeverGOS Iam afraid doing that ruins the whole purpuse of using GOS?

Some people might think so, but I personally don't. The "point" of GrapheneOS isn't to be a de-Googled OS. Though even if you do grant all of those permissions, Google still gets way less information about you since none of their apps are privileged.

ForeverGOS To be honest I am unsure what does @de0u exactly mean. I went to bluetooth, clicked on the watch > forget.

To be honest, I'm not sure what I meant either! I looked around a bit and so far have not found the post I remember reading, and, again, I don't have one of these devices. So I guess I am suggesting telling the phone to forget the pairing with the watch, telling the watch to forget the pairing with the phone, and, if there is a way to tell any cloud account to remove the watch from the account, doing that as well. But please understand that this is very-low-quality advice.

That's very strange. Galaxy watches should work with GOS under the following conditions:

1. Galaxy Wearable and the required Watch Manager are installed in the owner profile
2. Sandboxed Google Play Services is installed in the same owner profile
3. Nearby devices permission for Google Play services is granted (Apps > Google Play Services > Settings > Nearby devices > Allow)
4. Allow any required permissions within the Galaxy Wearable and required Watch Manager apps

With the above, my Galaxy Watch 6 classic BT works great with my Pixel 8 running GOS build 2024042200. It could be due to the fact that you have an LTE model, and perhaps some additional setting tweaks are required for establishing LTE connectivity.

Just thought I'd stop by to thank everyone who participated in this thread and the previous one. I've had my Pixel 8 Pro with GOS from day one since January, and I've had a Watch 4 Classic for years now. It's literally been dead-weight and just apparel (I've been using it turned off for months) until right now. I hate the solution, since I wanted to keep the owner profile de-googled entirely, but at least it's an f'ing solution.

Now I'd really like to know how much can be undone without breaking the watch connection....but I'm kinda not willing to try and experiment at the moment.

ForeverGOS

GOS does not allow wearable to send me notifications to my watch, the "Device and app notifications" menu will not allow me to "allow notification access to Galaxy Watch 6 Manager" "Restricted setting for your security, this setting is currently unavailavble" How can I Fix that?

I've never seen that before, so I have no idea, sorry. That must be frustrating that notifications doesn't work, as that's the main use case for a smart watch. Did you allow notification permissions for all of the following apps?

1. Galaxy Watch6 Manager
2. Galaxy Wearable
3. Google Play services

Sideloaded Molly to the watch, but I neither receive notifications nor can actually use the app properly since its too big for the screen. Is there a way to resize the app instead of the whole watch like I already did?

I use pure Signal and just use the available actions that come up on Signal notifications, but I assume sideloaded apks will not adjust to the watch screen size unless the app is specifically written for WearOS. If your first issue gets sorted out, you should theoretically not have to sideload any apps, although I do sincerely wish for a WearOS app for Signal/Molly.

JAvila I hate the solution, since I wanted to keep the owner profile de-googled entirely, but at least it's an f'ing solution

Yeah, I'm with you there. I wish I didn't have to install GPS on my owner profile, but I'm living with it, as it allows me to use my watch.

I also didn't have the best experiences with battery drain from Signal's websockets back when I was using another degoogled ROM without any GPS-equivalent when I didn't have a Pixel, so I'm taking solace in the fact that having sandboxed GPS on my profile means I don't have to worry about excessive battery drain.

I'm not sure where the GPS requirements comes in. I've been using my Galaxy Watch 3 with GrapheneOS and no GPS installed in the Owner Profile.
Maybe I'm just not using those features?
I only connect it to pull the Health/Fitness/Sleep data off the watch.

Seems like the recent Galaxy Wear or Graphene update changed things. The app is no longer crashing while pairing to the watch. Instead the app is persistent on requesting permissions it has already been granted

shimun
I concur