Age | Commit message (Collapse) | Author |
|
|
|
|
|
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)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OpenVPNService.
|
|
|
|
|
|
|
|
|
|
|
|
In an ideal world, application developers would read the documentation and realize that the *calling* app needs to ensure that the target app can read the URI (e.g. by GRANT_PERMISSION) but ES file explorer (and from user report the internal file manager of cyanogenmod?!) call OpenVPN for Android with a file:// URI which OpenVPN for Android cannot read without SD card permission.
Always to try request SD card permission on file:// urls...
|
|
|
|
|
|
|
|
|
|
|