Bug #5779
all v15.0.1 can't "start" orbot in "APP" (VPN) mode on Lollipop 5.0.1
| Status: | New | Start date: | 09/13/2015 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Component: |
Description
orbot v15.0.1x can't start and, therefore, can't restart/resume in APP/VPN mode. error typically is can't parse torrc, or tor start parses torrc, but never acquires carrier's (Sprint) network.
v15.0.0x could start/restart/resume in APP mode on Android Lollipop 5.0.1 (Samsung).
set v15.0.1x to start in non-APP mode, with exact same torrc, and orbot starts every time and can then be switched into APP mode. but, whenever device loses air network connectivity, orbot, in APP/VPN mode fails to resume/restart. THIS IS A HUGE PITA, when using voice call dialers, like S Voice or Skyvi, that otherwise work with tor, but require air network access.
can't believe this bug can't be fixed by automating orbot APP/VPN mode restart/resume to auto-magically, temporarily drop out of APP mode, resume/restart in non-APP mode, then switch back to APP mode.
in the absence of said automation, that's what i'm forced to do MANUALLY. wtf...