| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
confusing and people trying to connect to that server
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Fixed error, when stopVPN method in ManagementThread returned true regardless of actual stop signal have been sent.
As result - management stopped to send any state updates to listeners because of mShuttingDown flag.
* Fixed error, when endVpnService method didn't actually stop vpn thread because of missing thread interruption handling.
|
|
|
|
|
|
|
|
|
|
all who told me about that bug
|
|
|
|
|
|
|
|
|
|
exited), closes #553
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
configuration like in issue #546 *sigh*
|
|
|
|
This happens due to a race condition in background threads that use an
activity context to call long-running RPCs in keychain and keystore.
If the activity goes away while services are still bound, its context
will be disposed of and any attempts to unbind those services will raise
an IllegalStateException.
The right thing to do is make these calls using an application context
instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
overhaul time between connection logic massively.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
