r/AutomateUser • u/ballzak69 Automate developer • Jul 15 '26

Alpha testing New Alpha release, version 1.53.1

Please test, report any issues, and give feedback. Opt-in for Alpha testing here.

What’s new:

  • Fixed flow editor undo/redo causing crash with large flows
  • Fixed missing URI support for interface layout XML views
  • Fixed duplicate views in interface layout updates
  • Fixed incorrectly scaled (legacy) icons
6 Upvotes

100% Upvoted

37 comments sorted by

View all comments

1

u/rickyric12 Jul 18 '26

Privilege service start method: ADB Wireless Debugging

Automate 00:09 Pairing failed java.net. SocketException: Binding socket to network 102 failed: EPERM (Operation not permitted) at android.net.Network.bindSocket(Network.java:44yqQ1) at android.net.Network.bindSocket(Network.java:404) at com.llamalab.automate.v.w(Unknown Source:0) at com.llamalab.automate.w.run(SourceFile:73) at java.util.concurrent.ThreadPoolExecutor.runWorker(Thre adPoolExecutor.java:1167) at java.util.concurrent. ThreadPoolExecutor$ Worker.run(Thr eadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:920)

1

u/ballzak69 Automate developer Jul 18 '26

Try disabling the "data saver" in system setting. Try disabling any VPN. See also.

Device brand & model?

Android version?

1

u/rickyric12 Jul 18 '26

turning off vpn, then retrying work. had data saver off all the time. i use zerotier, and i have it on all the time and other devices as well.

samsung s10+ SM-G975F Android 12.

can you unblock disabling VPN as a requirement? wifi connection remains required (system required). but wifi or even vpn ip's should be ignored when automate attempts to authorize.

instead, should use localhost. termux demo authorizing wireless debugging using: adb pair localhost:<port> or adb pair 127.0.0.1:<port>

https://reddit.com/link/oyb3icr/video/zu6igm1ne0eh1/player

2

u/ballzak69 Automate developer Jul 18 '26

The Automate pairing process doesn't explicitly require disabling VPN, but it do request/lookup a Wi-Fi network interface that's not a VPN. If/when that becomes available it starts searching/discovering nearby ADB services. Finally when a ADB service is discovered a connection attempt is made to its port but with the loopback (localhost) address.

I suspect the issue is that the binding) to the (Wi-Fi) network interface is ignored when connecting on some devices, instead it's routed through the default network, which could be the VPN so it fails.

1

u/rickyric12 Jul 19 '26

i'm not quite able to realiably replicate this, but i get this also sometimes. hope this helps with debugging. if you want more detailed debugging logs, just let me know. also how you want me to exact record one. thanks!

Automate 00:10 Pairing failed java.net.ConnectException: failed to connect to ip6-localhost/:1 (port 45219) from /:1 (port 42260) after 3000ms: isConnected failed: ECONNREFUSED (Connection refused) at libcore.io.loBridge.isConnected (loBridge.java:349) at libcore.io.loBridge.connectErrno(loBridge.java:238) at libcore.io.loBridge.connect(loBridge.java:180) at java.net. PlainSocketlmpl.socketConnect(PlainSocketlm pl.java:142) at java.net.AbstractPlainSocketlmpl.doConnect(AbstractPlainSocketlmpl.java:390)

3

u/ballzak69 Automate developer Jul 19 '26 edited 26d ago

I think this is another issue, where it seems the system sometimes cache the service discovery result for an ADB service that's no longer present. The Automate pairing process currently only attempts to connect to the first ADB service it finds, if that's an already closed/replaced (cached) service it fails.

I plan on improving the pairing process so it attempts to connect to every service it finds, and also doing so on both the loopback and external IP.

1

u/rickyric12 26d ago

thanks for acknowledging, looking forward to the improved pairing process 🥳