| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the problems.
|
|
|
|
|
|
device on the VPN for Android N(ew York Cheesecake?)
|
|
|
|
|
|
Android NYC+ might start the VPN service on its own without any
useful intent extras saying which profile to load.
Handle it the same as the restart case -- use the most recent profile
instead of crashing.
|
|
understanding what goes wrong (closes #455)
|
|
|
|
|
|
|
|
|
|
|
