This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/DutchOfBurdock on 2023-09-22 13:40:49.

So I had this update rudely thrust upon me. Never had auto updates on, but just checking if there was one, decided to ignore my “Install Later” requests and installed overnight, as I were sleeping, with watch on wrist, falling asleep with 32%. FU Samsung.

Anyway, rant over.

BT and WiFi Debugging

ADB will be like it is on newer Android. You need to first pair to a random port, then connect to a different one each WiFi. You can however start ADB tcpip like you can, as to keep an ADB service running always. This will allow AutoWear to continue to work. But, days are gone now where AutoWear could grant itself it’s permissions via BT debugging, which used to open port 7272, even on WiFi.

Port 7272 is now closed on BT debugging. I totally get why they did this, actually surprised it took them this long. So here it is.

Termux can ADB pair to watch, adb tcpip 7272 (or 5555 if you wish) and no WiFi needed. Just use said port in AutoWear.

edit: You don’t need to pair when you do this, just adb connect watch.ip.add.ress:port and grant always.

Complications

Just set them all back up on your face(s). Watchmaker, f.e. lost steps, distance and calories until setting them back. Same for AutoWear based ones.

Will update

As more fan is smothered, or not.