this post was submitted on 21 Aug 2024
21 points (100.0% liked)

Android

27484 readers
194 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

!android@lemmy.ml


founded 1 year ago
MODERATORS
 

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!

top 14 comments
sorted by: hot top controversial new old
[–] pacjo@lemmy.dbzer0.com 7 points 3 weeks ago (1 children)

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.world 1 points 3 weeks ago

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

[–] catloaf@lemm.ee 3 points 3 weeks ago (1 children)

Does it work on stock unrooted?

[–] 4lan@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago)

yep, OnePlus open, was using my watch like normal since I got it.

worked the same as on my Samsung phone before rooting.

[–] kirk781@discuss.tchncs.de 2 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

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.world 2 points 3 weeks 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.com 2 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

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.

[–] 4lan@lemmy.world 1 points 3 weeks ago

thanks! I'll try installing the Galaxy Wear stuff, hiding it, then try the process.

[–] 4lan@lemmy.world 1 points 3 weeks ago (1 children)
[–] luciddaemon@lemmy.dbzer0.com 1 points 3 weeks ago (1 children)

Is magisk also hidden?

Heres an example app: 1000038879

[–] 4lan@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

are you asking if Samsung Wear is hidden in Magisk, or if Magisk is hidden in HideMyApp?

Sorry I'm dense you have to be specific.

[–] luciddaemon@lemmy.dbzer0.com 2 points 3 weeks ago (1 children)

Within Magisk there is a hide open, select that, name it something like music-mag, then clear the samsung wear app data and try it again.

[–] 4lan@lemmy.world 1 points 3 weeks ago

I've already wiped my watch and connected it, not sure if you saw my update to the original post

So I can't even test that out now. Was trying to avoid resetting it but whatever