Age | Commit message (Collapse) | Author |
|
|
|
|
|
* fix setting http proxy port correctly
* snowflake+tor does currently only work when being connected to a wifi, not a cellular network.
For now, we check if the device is connected to a wifi, before attempting to start tor
|
|
|
|
been setup successfully
|
|
|
|
|
|
|
|
|
|
been initiated with TorService
|
|
API responses
|
|
|
|
|
|
|
|
|
|
for tor
|
|
|
|
|
|
|
|
tor notification text can be shown
|
|
reinitiated on next api call
|
|
|
|
|
|
|
|
|
|
|
|
|
|
compile time, turned off for Bitmask for now
|
|
and location fails
|
|
|
|
location is manually selected
|
|
|
|
support menshen
|
|
|
|
|
|
optionally parse sortedGateways json object from menshen backend reponse
|
|
|
|
connection with a misconfigured provider
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
adapt eip-service.json parsing to support ipv6
See merge request leap/bitmask_android!125
|
|
|
|
|
|
of the LogView
|
|
* always use a bound service connection to start a vpn service as foreground service to fix remote excptions. These appeared if the system wasn't able to set the service as forground shortly after it was started
* move vpn start logic from LaunchVPN activity to EIP service. LaunchVPN/VoidVPNLauncher is only used in case we need to ask the user for a permission. It reduces visual glitches when the transparent LaunchVPN activity appears and disappears
|