Age | Commit message (Collapse) | Author |
|
|
|
Removed the sign up dialog, log in one is enough with the third button I
added some time ago to sign up.
Removed classes we don't need due to the libraries I have recently
introduced.
|
|
|
|
|
|
Initial status message is "not connected", rather than "unknown".
|
|
|
|
|
|
|
|
Fixed notifications too (forgot to do it in another branch, it's #5964).
|
|
When the user has already been connected to a VPN and she configured the
client to use persistent-tun, we should warn her that until the VPN
connection is again established, no traffic will flow.
|
|
|
|
It's enough to reflect the fact that the button leads to a dialog from
which the user can both log in or sign up.
|
|
I don't use the eip status receiver because it wasn't reliable on
timing: updated messages were arriving before the receiver was notifying
a new state.
Current and last ConnectionStatus is now managed at EIP.
More refactoring on the eip fragment, now there are separate methods for
setting up the UI depending on the message received.
|
|
|
|
|
|
|
|
|
|
If the connection is being established, the key with a clock icon is
shown.
If the connection has been established, the key without the clock icon
is shown.
I've also added all some icons to more resolutions.
|
|
|
|
|
|
|
|
|
|
I've also fixed another message: if a file to be downloaded is not
found, we say the entered provider isn't a LEAP provider. This is based
on the fact that if provider.json doesn't exist/contain valid
information, then the url isn't pointing to a LEAP provider.
|
|
|
|
|
|
The active gateway cannot be null.
|
|
|
|
In case there is an error, user will not be prompted with a strange log
window, but the app will provide it if s/he really wants to see it.
|
|
Merged updated ics-openvpn-upstream (e7803cc8efcd1794e18b4e30a43d814c2834552d).
|
|
|
|
|
|
Refactored AndroidManifest to include launchvpn and openvpnservice.
Imported changes from ics-openvpn-upstream
|
|
Forgot to add the menu for the log.
Now we'll strive to fix se.leap.bitmaskclient problems: first compilation, then functionality.
|
|
api folder and aidl files aren't needed for us. They are used for
external apps that want to use ics-openvpn as an already installed
package, while what we want is to avoid the installation of ics-openvpn
including it (refactored) in bitmask android.
|
|
|
|
Now we need to decide what's our relationship with LogWindow and
LaunchVPN, refactor its classes and fix ours so that we use the
currently supported methods.
|
|
I'm hardcoding their values based on the compilation errors (i.e., the
drawables referenced by de.blinkt.openvpn.core.OpenVpnService). If a new
drawable were introduced, build.gradle should be updated accordingly.
|
|
I privilege ics-openvpn translation to ours. If we need to change
something, we can introduce a new xml element without any future
compatibility problem with ics-openvpn.
|
|
|
|
Functionality copied to the Release build.
|
|
There is some problem in the maths, because the server says it's ok but
login doesn't work from Android app nor from webapp.
|
|
This return to "app" instead of "bitmask_android" is due to this reading: https://developer.android.com/sdk/installing/studio-build.html#projectStructure
I'll have to tweak the final apk name in build.gradle.
|
|
This way, gradle commands generate apks correctly named.
|
|
|