Easytether stability issue

crunch · 2021-06-01T19:38:01.031Z

(note: GL guys, no need to reply this post, I know Easytether isn’t officially supported by you. Just need to ask the other users if anyone has experienced this issue and if any possible workarounds are known, thanks.)

Using Easytether 1.1.19 on GL-AR150 running 3.201.

Easytether connection is running. But while downloading some Youtube videos to test the connection, the connection dies until I unplug/replug the Android phone (Samsung S20) usb cable from the router. At which point the connection is good again.

It’s good for maybe 10-15 minutes before it dies. Only one device connected. Download speeds 1-3MB/s.

I read about other users’ Easytether connections dying when they were idle. But this connection is very active. Maybe I need to upgrade to more powerful router?

Any tricks to make the Easytether connection more stable?

Any feedback appreciated, thank you.

alzhao · 2021-06-02T08:46:11.213Z

No zero reply. But sorry I don’t know.

Loco · 2021-07-10T21:53:17.798Z

Any fix on this? I’m having the exact same issue with no luck. Even tried scripts

crunch · 2021-07-10T22:28:36.133Z

I saw somewhere else someone wondering if it was just a ‘small cpu being overloaded’ problem, which made me wonder the same thing.

I switched to an AR750S (Slate) and the problem hasn’t reappeared. Another benefit of the AR750S is much more disk space to install packages etc.

makino16 · 2021-07-11T19:45:52.890Z

In my opinion, the OS seems to be blocking the operation of EasyTether (or USB Eathernet) services.
Battery “optimization” features by Google and other companies are becoming more powerful in newer operating systems. Especially noticeable on Android 10 and above.

And, the USB terminal has a feature to control the host and protocol in both hardware and software.
Depending on the combination of device and cable, even if the router side determines that it has been disconnected, the Android side may determine that the connection is still ongoing.

In my case, some devices didn’t recognize the disconnect under certain circumstances and didn’t respond when the router requested a reconnect (Android9 / Huawei).
Other devices required ADB commands to make the service resident (some optimization services do not offer a fully resident option).

Other things I came up with

It may be improved by using an OTG cable with power connector
- https://www.amazon.com/s?k=usb+otg+type+c+with+power+cable
  - Depending on the cable, you may need to connect a router to type C
  - https://www.amazon.com/s?k=type+c+to+type+a
  - Choose your product carefully, as misidentification of the host can break your device