A client can sometimes use an Android hotspot for internet access yet fail to connect to a service running on the phone itself. That is usually an ingress problem, not proof that cellular routing failed.
Check the simple variables first
Confirm that the user enabled the hotspot in Android settings, the client joined that exact hotspot, and CellRoute reports its proxy as running. Use the current hotspot gateway address shown by the app—not an old Wi-Fi address—and verify the protocol, port, username and password.
Test with a client that explicitly supports TCP SOCKS5 or HTTP proxying. A generic “internet works” test does not exercise the local proxy listener.
Understand OEM isolation
Android device makers can implement hotspot routing and firewall rules differently. Some allow a connected client to reach the phone’s gateway address; others allow only forwarding beyond the phone. CellRoute cannot bypass an OEM firewall rule that blocks hotspot-to-phone traffic.
This is why hotspot isolation should remain Unknown until a real client attempts a connection. A phone-only self-test cannot reliably reproduce the client’s direction through the hotspot interface.
Separate ingress from cellular status
If the client cannot open a TCP connection to the local proxy port, troubleshoot the hotspot address, listener, local firewall and isolation first. If it can authenticate but destinations fail, then inspect cellular validation, DNS, destination ACLs and carrier conditions.
If the OEM blocks local hotspot access, the same-Wi-Fi mode may be a practical alternative when a trusted Wi-Fi network allows peer-to-peer client access.