I am finally back to having a rooted phone after a decade! Feels nice to have control over my phone again.

The only thing left to get working again for me is the Samsung Wear connection to my Watch6.
I can get pretty far in the setup, but it eventually says it can’t connect.

I tried the Magisk module GoogleSpoofForWear and even edited my .prop file, no luck! Safetynet passes and playintegrity is intact.

Followed every guide I could find, so reaching out to you guys for help! anyone get their watch working on a rooted phone? (android 14)

Edit “Solution”: I was able to get it to work after fully resetting my watch. I kept the app magisk hidden but not sure if it was necessary… I didn’t want to have to do that but at least it works now!

  • kirk781@discuss.tchncs.deEnglish
    0·
    3 months ago

    Fully resetting the watch is a sorry thing that I too have to deal with. Despite Wear OS 4 (on GW 6) having backups and switching functionality, half of the time it doesn’t work. I don’t have a rooted phone, but switching phones or God forbid, you forcibly remove Galaxy Watch from Bluetooth settings and then you have to redo things from scratch sometimes.

    Too bad, that some Garmin models support Gadgetbridge, but I don’t think any Wear OS model does.

    • 4lan@lemmy.worldOPEnglish
      0·
      3 months ago

      So that’s why I assumed it was root causing the issue actually. I never had a hard time switching phones with my Galaxy watch 6. Went back and forth between phones for a while even, and it was always pretty painless.

      I probably could have got it to work, but just gave in and pressed reset 😂

  • luciddaemon@lemmy.dbzer0.comEnglish
    0·
    3 months ago

    I use lsposed + hidemyapplist. Sometimes apps look for magisk, or other signs of being rooted. That will hide them all.

    I also have magisk hide and sulist enabled. They also help hide root by preventing apps from requesting root unless explicitly allowed. It also hides magisk, which bank apps usually look for.

    Edit: A bit redundant now that I think about it, but I haven’t had any issues.

  • pacjo@lemmy.dbzer0.comEnglish
    0·
    3 months ago

    Next time you can save yourself a reset by using adb.

    1. connect to watch over adb (usb or wireless)
    2. run adb shell "pm clear com.google.android.gms && reboot"
    3. wait a few minutes (might not be necessary, but I found it increases success rate)
    4. run adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE"
    5. pair new device in companion app (I reset the app for good measure, don’t know if it’s needed)

    Also on my device (oppo watch), play integrity doesn’t seem to matter. Some of the time I’m only passing basic and watch works perfectly.

    • 4lan@lemmy.worldOPEnglish
      0·
      2 months ago

      thanks! I’ll remember this and hopefully it helps others in the same boat that search in the future