Some Shadowrocket for Android users do not have a visible log screen in the app. In that case, troubleshooting should not depend on log entries. A better approach is to use observable network tests and change one variable at a time.
Quick answer
If Shadowrocket for Android has no visible logs, troubleshoot by layer: confirm the local network works without the proxy, check whether the public IP changes after connecting, run a DNS leak test, isolate routing rules, compare with a known-good node, and verify Android VPN permissions and battery restrictions.
Start with the local network
Turn off Shadowrocket for Android and open a normal website. If the site fails without the proxy, the issue is not the proxy client. Check Wi-Fi, mobile data, captive portals, local DNS, and carrier connectivity first.
Check visible IP change
After connecting, open an IP check page. If the visible IP does not change, the browser or app may not be routed through the proxy, the rule set may send the test site direct, or the Android VPN tunnel may not be active. Compare this with the VPN connected but IP address not changing guide.
Run a DNS leak test
If the IP changes but websites still behave incorrectly, check DNS. Local DNS results can cause regional redirects, blocked domains, or inconsistent access. Use a DNS leak test and compare the resolver location with the proxy exit.
Isolate routing rules
When only one app or site fails, routing rules are a likely cause. Temporarily route the target app or domain through one known-good outbound. If the result changes, the problem is probably rule matching, per-app proxy behavior, or policy group selection.
Compare nodes carefully
Switch to one known-good node without changing DNS and rules at the same time. If only one node fails, inspect that node's protocol, port, transport, SNI, and server status. If every node fails, focus on subscription format, Android VPN permissions, or network environment.
Check Android VPN permissions
Android may restrict VPN tunnels, background activity, battery usage, or network access after the screen is locked. If the problem appears after locking the phone or switching networks, also read the Shadowrocket for Android background stability guide.
What not to assume
- Do not assume every build exposes logs.
- Do not assume a failed page means the node is dead.
- Do not run multiple VPN-based proxy clients at the same time.
- Do not change DNS, node, rules, and app permissions all at once.
FAQ
Can I troubleshoot without logs?
Yes. IP tests, DNS leak tests, rule isolation, node comparison, and Android permission checks cover many common failures.
Why change only one setting at a time?
It keeps the test result meaningful. If several settings change together, the cause becomes unclear.
Should I reinstall the app?
Only after checking configuration, subscriptions, permissions, and network state. Reinstalling can remove local settings without fixing the root cause.