Orbot seems unable to cope with roaming Wi-Fi
|Target version:||v14 - April Anons|
I've been staying away from home recently, so have been using BT Wi-Fi, which allows me to connect to the Internet via any nearby BT router (unless the customer has disabled this feature). This requires using the BT Wi-Fi app, as once connected my BT username/password have to be entered to verify I'm a BT customer and the app takes care of that, so simply using the Android Wi-Fi connection screen alone won't work (it will connect but I'll be unable to access the Internet).
It will automatically hop to the strongest available signal, so over the course of an hour it might switch between two or three nearby routers.
What I've found is that Orbot doesn't seem to be able to cope with this and the browser (Dolphin) ends up with no access or it reverts to plain un-Torred access. To fix this, I have to go to Orbot, disable it and re-enable it. This is obviously a pain so I'm wondering if Orbot could be made to automatically stop/restart itself when the Wi-Fi connection changes (it might also be necessary if the connection is lost and then it re-connects to the same router but I'm not sure about that).
#1 Updated by doveman over 4 years ago
I should mention that I'm using app-selection in Orbot, not Tor Everything. Also, when I lose the Tor connection, often it seems not only do I have to restart Orbot but also Exit and restart Dolphin before it starts using Tor again. This might be a limitation of Dolphin or the Android OS itself though.