Bug #3413
Orweb asks for starting of Orbot when Orbot has already started, causes jam
| Status: | New | Start date: | 05/25/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Backlog | |||
| Component: | squishy bits |
Description
"Orbot doesn't appear to be running. Would you like to start it up and connect to Tor?"
It was running, actually, and had been for some time. The thing was, WiFi had been spotty and the WiFi wasn't connected.
Touching "yes" at Orweb's prompt brings you "back" to Orbot but really what you get is a black screen for a few minutes while something in there is all confused.
Is it starting another Orbot over a previously running instance? Is that even how Android works? Idk. It's messed up and stuff.