• Off Topic

  • GrapheneOS not letting my Galaxy Watch work?

ForeverGOS Should be fine with that version.

I see you mentioned that you bought the watch off someone else. Are you sure it doesn't have anything wrong with it?

      ForeverGOS

      other8026 I see you mentioned that you bought the watch off someone else.

      Ahh, this is a smart observation.

      Is the watch still tied to the previous owner's Samsung account?

      It is conceivable the watch and app worked together despite being on someone else's account; but then wiping the esim has disrupted things ... because stop working after a thief tries to reset watch stuff?

      I don't mean the watch has been stolen, but that the original owner has not removed the watch from their account so the the Samsung 'theft' stuff trips in.

            YA657 @other8026
            Sure its all good, as I mention on my post, I have been able to connect it to my other phone and it worked perfectly.
            The other phone is a normal Android Samsung.

                ForeverGOS oh, that's right. Forgot that part.

                Based on what you've said so far, it sounds like you've done all the things that I've seen on here. I don't have a smart watch myself, so I can only go by what I've read here. I know Samsung watches work with GrapheneOS. There are multiple people here on the forum who've said as much, though I'm not sure what the difference is here.

                I know you've tried many things, but did you remove it like de0u suggested? Are you letting the app establish the connection instead of doing so via the settings?

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

                    Not sure if that´s what he means, if so I did it. However bear in mind, the phone never really shows that its connected to my phone, it kind of struggles establishing a bluetooth connection with my phone for some reason, but it does establish it with the other normal android phone.

                    PS: I thought of giving GPS all the permissions, including the notifications one that only launcher has to test, but Iam afraid doing that ruins the whole purpuse of using GOS? Help here if possible pls

                        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.

                                Vagabond8630
                                Thanks for your comment, I´d like to say that your comment was kind of the solution to the issue. I happened to reflect on your words and tried everything from scratch. However, this time I uninstalled GPS from ALL users. Also, I did not only uninstall Wearable but also the Wearable Plugin 6. Began everything from scratch, then it worked!

                                I however encounter two issues now

                                1. 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?

                                2. 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?

                                Thank you

                                    11 days later

                                    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.

                                          JAvila
                                          Thanks for your kid words. You can go ahead and turn off network permissions for Gservices and everything will keep working smoothly:)!

                                            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.

                                              5 months later

                                              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

                                                4 months later
                                                19 days later

                                                Vagabond8630 I got the same issue and your outlined solution worked. It seems that Google Play services crashed when missing some permissions (I enabled nearby devices and location for it to work). After this, the screen that tell me to login to Google account appeared, and everything went smoothly from there.