Age | Commit message (Collapse) | Author |
|
adapt eip-service.json parsing to support ipv6
See merge request leap/bitmask_android!125
|
|
|
|
* 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
|
|
|
|
|
|
foreground service start
|
|
notification in onCreate already
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
context instead
|
|
for it
|
|
those supporting the requested transport in order to get the nClosest gateway; adding more tests
|
|
profiles mUsePluggableTransports flag instead of shared preferences to get the requested transport
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
reduce UI flickering
|
|
throws an nullpointer exception while it tries to prepare
the VpnService
|
|
|
|
|
|
of the list of available gateways has been reached during setup
|
|
|
|
|
|
|
|
|
|
valid configurations
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not be started
|
|
|
|
|
|
between obfs4 and plain openvpn connections
|
|
|
|
|