Hello,
This bug was present for a long time. I checked with adb, the cloak process is alive, but when shadowsocks connects to it, it gets a timeout and reports timeout connecting to the localhost port. I will compile a version of cloak with more logging (since it seems in shadowsocks we can't set logging level for cloak) and try to debug this issue.
It seems to happen in 2 cases, when cloak left for a long time idle (even when cloak and shadowsocks put in battery optimization whitelist), also rebooting the server triggers the issue more quickly.
Note: This issue never happens to shadowsocks alone and it is also using a native process.
Hello, This bug was present for a long time. I checked with adb, the cloak process is alive, but when shadowsocks connects to it, it gets a timeout and reports timeout connecting to the localhost port. I will compile a version of cloak with more logging (since it seems in shadowsocks we can't set logging level for cloak) and try to debug this issue.
It seems to happen in 2 cases, when cloak left for a long time idle (even when cloak and shadowsocks put in battery optimization whitelist), also rebooting the server triggers the issue more quickly.
Note: This issue never happens to shadowsocks alone and it is also using a native process.