Age | Commit message (Collapse) | Author |
|
branded builds
|
|
|
|
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
|
|
further investigations
|
|
|
|
|
|
|
|
foreground service start
|
|
notification in onCreate already
|
|
|
|
|
|
ensure the private api and the preshipped certificate will be used to setup...
Closes #9029
See merge request leap/bitmask_android!130
|
|
|
|
the provider in custom builds
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Android O: evaluate last connection state in OnBootReceiver
|
|
Fix always on reboot
Closes #8994
See merge request leap/bitmask_android!119
|
|
closes #9001
|
|
|
|
|
|
reboot due to always-on system settings or if system killed app due to low memory
|
|
names differ between fat and fatweb builds
|
|
gets added correctly
|
|
negotiation issues
|
|
|
|
for RiseupVPN builds
|
|
|
|
|
|
|
|
|