Releases: zaneschepke/wgtunnel
Releases · zaneschepke/wgtunnel
Release 2.2.0
Features:
- Added support for Android TV
- Added support for Android Always-on VPN
Fixes:
- Fixes bug where handshake notification was not dismissed after subsequent successful handshake
- Fixes bug that allowed user to use Auto tunneling without Location Services enabled
Release 2.1.4
Bugfixes:
- Fixes crashes on Android 14 because of new requirement for foregroundServiceType definition
Release 2.1.3
Bugfixes:
- Add scrollability to all screens to prevent inaccessible UI elements in landscape mode an on tablets
- Make FAB disappear on downward scroll to prevent it being in the way of tunnel control
Other:
- Bump targetSdk to 34
Release 2.1.2
New Features:
- Details screen which shows config details, handshake, rx, tx
- Tunnel status LED added to main screen
- Tunnel connection notification if tunnel connection failing
Bugfixes:
- Fixed bug that could cause crash if wrong file was selected during config selection
- Fixed bug where selecting QR code config import could result in nothing happening if QR code module was still being downloaded
- Fixed bug where edited changed to a config would not get propagated to settings if that config was the default config
Release 2.0.3
Bug fixes:
- Fix bug causing disconnects and reconnects after updating trusted SSID list
- Fix bug causing VPN to not disconnect on data when setting is disabled
Release 2.0.2
Bug Fixes:
- Fixed a bug preventing tunnels from starting via auto tunneling after the app auto launched in background because of a system reboot
- Fixed a bug causing crashes if a malformed tunnel config was uploaded via file
Release 2.0.1
Fix
- Update expired Discord link
Release 2.0.0
New Feature
- Split application tunneling added with tunnel configuration screen
Fixes
- QR code tunnel validation added
- Minor UI quality-of-life changes
Release 1.2.0
QR Code Scanning
- Added support for importing tunnel configs via QR Code
Release 1.1.5
fix: watcher service mobile data monitoring Fix for a bug where watcher service does not start monitoring mobile data when feature is turned on