mullvadvpn/android/service, branch decrease-leaks-during-reconnectThe Mullvad VPN client app for desktop and mobilehttp://git.waynecole.info/mullvadvpn/atom?h=decrease-leaks-during-reconnect2025-10-28T14:56:09ZRename 'shared' to 'repository'2025-10-28T14:56:09ZKalle Lindströmkarl.lindstrom@mullvad.net2025-10-27T10:35:42Zurn:sha1:d10085b894e0061138c5e0ff4b351ed04a22c65eAdd option to show relay location in notification2025-10-28T14:55:52ZKalle Lindströmkarl.lindstrom@mullvad.net2025-10-23T14:15:02Zurn:sha1:376372c84c6b881e0097e5dab5348adab3e5f100
This PR adds the following:
- An option to show the relay location in the connection notification.
- A new submenu under Settings called Notifications.
- In the new Notifications screen a toggle to enable/disable showing the
location in the notification.
Fix failing test due to time zone change2025-10-23T12:12:16ZKalle Lindströmkarl.lindstrom@mullvad.net2025-10-23T11:38:49Zurn:sha1:98eab84c1cd238e6b380476f6e36870962386508Move ApiEndpointOverride to its own bean in app module2025-09-11T09:00:26ZJonatan Rhodinjonatan.rhodin@mullvad.net2025-09-10T09:06:22Zurn:sha1:99764348eb6522b1eab76b085969fcfae3afd6beAttempt to fix potential ANR2025-08-04T10:44:04ZKalle Lindströmkarl.lindstrom@mullvad.net2025-08-04T09:19:50Zurn:sha1:0a12ecffef67b5a3422dcd6ae53eeca114d407d4
In onReceive in NotificationAlarmReceiver onBlocking() was used which
could potentially take too much time and cause an ANR. This PR changes
the onBlocking() call to instead use the goAsync() API so that the
onReceive method can return immediately.
Fix gradle kotlinOptions warnings2025-07-03T08:18:59ZDavid Göranssondavid.goransson@mullvad.net2025-07-03T07:34:41Zurn:sha1:c65a73d6b996f8933d3e6a9e53ef5c43de96c164Use AlarmManager for notifications2025-06-19T07:36:26ZKalle Lindströmkarl.lindstrom@mullvad.net2025-06-09T15:16:45Zurn:sha1:cdc2c4d700cd41f37cf4b1607a0396019b1fbee5
Instead of scheduling system notifications from a flow we now
schedule them independently from the app lifecycle via AlarmManager.
This is done so that for example an expiry notification that the user
dismissed won't get redisplayed if the app process gets killed and
then restarted.
When the account exiry time is fetched we schedule an alarm that will
show a notification 3 days before the account time expires. This alarm
then also schedules a new alarm to show the following notification and
so on.
To make this work this PR also introduces two new broadcast receivers;
one on boot received listener and one on time time/timezone changed
listener.
Beause Android clears alarms when the devices is rebooted/the time is
changed we need these listeners to re-trigger the alarm.
To enable the broadcast receivers to re-trigger the alarm we also have
to persist the expiry time in the DataStore preferences.
Migrate remaining deps and versions to version catalogs2025-05-26T07:42:46ZDavid Göranssondavid.goransson@mullvad.net2025-05-24T07:23:14Zurn:sha1:1a421b646b09599c6f329226284b66b8416eef88Supply IP address when using API override2025-05-21T10:42:25ZDavid Göranssondavid.goransson@mullvad.net2025-05-21T09:17:25Zurn:sha1:7e7d6734b1c53dcc26774aebca60e5c09201152b
Previously we did a DNS lookup for Stagemole and Devmole however, this
causes problem when starting the app with no internet and is different
from how the app performs in production mode. This commit removes that
logic in order to align closer to what we expect in prod.
Unify usage of gradle properties2025-05-21T09:56:43ZDavid Göranssondavid.goransson@mullvad.net2025-05-20T08:11:16Zurn:sha1:bf7f22e42500ba570776a08d132b6ee1e3a93df9
This commit does multiple changes to how we work with properties.
- Instead of relying on `e2e.properties` and `local.properties` only use
the `gradle.properties` as per standard gradle.
- Naming of properties are changed to have a coherent structure.
- Allow for setting stagemole and prod account separately.
- Consolidate all the default values into `gradle.properties`