| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
This refactor aims to be a step in decoupling the service connection
from the main activity and fragment inheritance. The goal is to avoid
or minimize the fragment inheritance and instead let each domain observe
service connection changes and adjust accordingly.
|
|
|
|
|
|
Loads the UI specific DI module only in the process/activity where it's
used. Before, the UI module and its dependencies would be loaded in the
service and tile processes as well.
|
|
Rename the UI specific DI module to avoid potential confusion with the
Application class.
|
|
The wireguard key view is removed in favor of the new way of managing
devices. Translations and some error handling remain.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is an intermediate way of handling revoked devices until the proper
screen has been merged.
|
|
|
|
|
|
|
|
|
|
|
|
The webview is added to the debug build type of the main app, but it's
current purpose is only to enable verification as part of e2e tests. One
example is to open the webview on the device while connected and verify
the results of the Mullvad Connection Check.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds device state communication between the app and service with a
repository backed by a data source to add abstraction layers on the app
side.
Limitations:
* Expiration is not updated correctly.
* The login/creation flow has not been fully adapted to devices.
|
|
|
|
|
|
|
|
Android Studio and ktlint seem to agree on most styling except for
imports. Some settings can be changed in Android Studio, however it
seems to be hard to get lexicographical order (which ktlin wants).
Therefore ktlint should be ran after any formatting has been applied by
Android Studio (otherwise the CI workflow will complain).
|
|
The URL is a left-over after implementing in-app account creation via
the daemon.
|
|
Adapts the Android app to use the device login/logout functionality.
Limitations:
* State will not always be correctly propagated to all components of the
app (i.e. Settings). This will be fixed in later device commits.
* Some temporary error messages will be used in the Login view. These
will change in later commits and/or be replaced with new views (i.e.
when a user has too many devices registered).
|
|
Initial limited adaption of the daemon device changes. Makes it possible
to launch, login and connect. However, there are some limitiations:
* State is not properly handled thoughout the app.
* The app itself doesn't expose any device functionality to the user.
* The wireguard key actions are disabled (regenerate and verify).
* Accounts are not remembered across app restart.
|
|
|
|
|
|
|
|
|
|
F-Droid requires the metadata to be present in a specific location which
isn't compatible with our mono-repo structure, therefore this change
moves the Gradle Play Publisher (GPP) directories to a location
compatible with F-Droid and adds a symlink at the location GPP expects,
which leads to the F-Droid location.
The reason for doing it this way rather than symlinking the other way
around is that we don't use GPP itself atm. Even if we start using it,
it's still easier to make sure everything is working (in regards to the
symlink) in the GPP build environment compared to the F-Droid build
environment.
|
|
Fixes tile service crash that occurred when the tile service tries to
unbind even though there are no binding or pending binding.
|
|
As releases usually are built from release branches, the current
strategy will be to keep this file empty on master.
|
|
The main activity and tv activity are both designed to be running as
singleTask and the app would crash if both were started. This would not
be common, but possible, on a phone or tablet, however this can
potentially occur frequently on Android TV (perhaps depending on OEM),
as both categories LAUNCHER and LEANBACK_LAUNCHER are used. E.g.the tv
launcher would use LEANBACK_LAUNCHER whereas the settings app would use
LAUNCHER.
As the tv activity isn't used for any customization atm, this was fixed
by simply removing the tv activity and adding the LEANBACK_LAUNCHER
category to the main activity.
|
|
Default vibration behavior:
* Vibration enabled for account expiration notification.
* Vibration disabled for tunnel state notification.
These defaults can be overridden in system settings.
|
|
The tunnel state notification is hidden from the lock screen by using
the Android notification visibility mechanism.
|
|
|
