Releases: AdguardTeam/AdguardForAndroid
2.1.267
Patch Release Notes
- [Added] New low-level setting "pref.net.exclusions". Allows to change the list of apps for which network filtering is disabled: #147
- [Fixed] Problem with filtering stuck at detecting filtered app: #154
- [Fixed] Cannot download file larger than 2Gb: #148
- [Fixed] [Critical] Wakelock when there are semi-closed connections: #137
- [Fixed] Compatibility issue with My JDownloader: #135
- [Fixed] App crash while checking if app is in foreground: #149
- [Fixed] Disabled update check for Amazon build: #102
- Minor changes: #152 #153
2.1.255
2.1.248
2.1.240
Multiple TCP stack improvements
Problems with large files download (#92, #98)
Previously there were problems with downloading large files, especially from Google Play. It is not the case anymore, you don't have to disable Adguard just to update your favorite app or download a new game.
Overall performance improvement
With recent changes Adguard has become faster, more stable and less resourse consuming. It was possible due to optimization of several 'bottleneck' situations.
Other changes:
- Moved firewall icons-cache to Cache folder to be able to clear it from app settings #89
- Fixed unnecessary restart of protection in Proxy mode #90
- Proxy mode: DNS cache is now flushed on network reconnect #91
- Multiple GUI improvement in Low-Level Settings #94, #96, #97, #103
- A new preference "pref.vpn.capture" added (#97) to low-level settings. If this setting is enabled, Adguard will create the special file named «tun.pcap». It contains all network packets transferred through the VPN. This file is located in the app cache directory, and can be analyzed with the Wireshark program.
- Optimized Pcap functionality in Low-Level Settings #97, #105
- Update channel options are hidden for Amazon builds #102
- Fixed handling of HTTP CONNECT requests without Host header #113
- Small UI fix on Send Feedback screen #118
- Added new localizations: Czech, French, Turkish, Serbian, Spanish #125
2.1.231 Beta
This is a release candidate for "2.1 patch" milestone.
- Multiple improvements in our TCP stack implementation #45, #92, #98, #101, #106, #109, #110, #112
- Moved firewall icons-cache to Cache folder to be able to clear it from app settings #89
- Fixed unnecessary restart of protection in Proxy mode #90
- Proxy mode: DNS cache is now flushed on network reconnect #91
- Multiple GUI improvement in Low-Level Settings #94, #96, #97, #103
- Optimized Pcap functionality in Low-Level Settings #97, #105
- Update channel options are hidden for Amazon builds #102
- Fixed handling of HTTP CONNECT requests without Host header #113
- Small fix in UI of Send Feedback activity #118
2.1.212 beta
Urgent update.
Previous beta version had incorrect TCP retransmission implementation. It could break large files downloads: #109
2.1.195 beta
- Fixed issues with downloading large files (including Google Play updates): #98 #92 #45
- Improved handling of TCP connections: #101
- Added summary field to "Low level settings": #96
- Added "pref.vpn.capture" preference to Low Level Settings section: #97
- Fixed an issue with applying "Low level preferences": #94
- Fixed an issue with DNS cache in manual proxy mode: #91
- Icons cache moved to app cache: #89
2.1.177
Firewall changes
Firewall settings section (#61)
Now it's up to you whether you need the Firewall feature or not. So, yeah, this feature can now be enabled and disabled. Very useful if you were setting different preferences for different apps and now would like to temporarily disable Firewall and won't lose all the settings herewith.
Firewall: Added an ability to temporarily pause blocking for foreground application (#27)
This feature allows to return the Internet access with one tap. Let's say you have prohibited some app (like Maps or any other using geolocation) to go online without you knowing. But when you need the app to connect to the Internet immediately - you no longer have to open Adguard, go in Firewall and change the settings. Now you can regain access to the network right in the app.
Low-level settings #42
What is low-level settings?
Most of users don't really need them. Such settings were made to make the troubleshooting faster, to solve some very rare problems or for a really specific configuration of the program. Now we won't spend time on the assembling of a special version for your device and you - on its download and installation. We will be able to tell right away what to change to solve the problem. So the support is now easier, and these settings are needed to parse some tricky bugs.
Let's go down the list:
pref.vpn.ipv4.force.default - disables the routes we use to exclude LAN from filtering.
pref.vpn.ipv4.force.complex - settings reverse to the previous one. Regardless of the network configuration use of routes excluding LAN. Usually, we do not exclude the LAN networks with a complex configuration. This setting will bypass the restriction.
pref.vpn.ipv6.bypass - forcibly exclude filtering of IPv6 networks. In this case, IPv6 will work, but will not be filtered.
pref.vpn.ipv6.disable- forcibly disable filtering for IPv6 networks. In case,IPv6 will not work at all.
pref.vpn.tun.mtu- the maximum size of the data package, which is used in VPN. In general, the rule is - the larger the package, the less CPU time spent on creating packages from the program, and the faster everything works. On the other hand, when the size is too large, VPN may cease to work at all, or fail to start. The recommended interval for the experiments is from 1500 to 9000.
pref.vpn.disable.pause - (#84) disable Adguard automatic restart functional when disconnecting/connecting to the network. Why needed? When the VPN is enabled, routes are built in accordance with the current network configuration on the device. Sometimes it happens that when you connect to another network, these routes no longer correspond to the new configuration, and VPN ceases to operate. Automatic restart is needed to avoid this situation.
Reworked DNS filtering
Now it should work even where external DNS are blocked
To 'catch' the requests to DNS servers (which resolve domains in IP) we had to set the preferences for our VPN, which provide access to some server outside the current network. We used one Google' and one Yandex' servers. But it turned out that there are providers and tariffs which block access to the external servers. Now, we look at what DNS server the user has. Then set some fake DNS in VPN settings. And when the query is executed to this fake server, we change the address with the one that the user has.
Other changes:
- Reworked the application life cycle: now the protection can be turned off/on without any issues #2, #36, #47, #65, #79
- Fixed application restart after deep sleep #2
- Fixed critical error that led to Adguard restart #24
- Fixed a mechanism for identifying modem and access point mode and showing a warning #81
- Fixed authorization problem in the Moscow Subway #41
- Fixed problem sending SMS/MMS in the AT&T network #33, #43
- Fixed an issue with collecting traffic statistics #56
- Fixed rare problem with automatic filter updates #59
- Fixed an issue with firewall interface on small screens #53
- Added support for new browsers: Dolphin Zero #22, Ghostery #19, CM Private Browsing #18, Jbak Browser #46 and more
- Exceptions added: Handcent Next SMS #75, Chomp SMS #49, FarmVille 2 #45
- Updated German and Polish localizations #73
- Fixed several issues in the interface #4, #5, #7
2.1.168 RC
This is the long-awaited Release Candidate!
Change notes:
- An option has been added to low-level configuration, which prohibits VPN pause when changing the network or disconnecting from it #84
- Fixed a mechanism for identifying modem and access point mode and showing a warning #81
- Now the notification about firewall blocking current app will hide when user allows it in firewall settings #78
- Updated German and Polish localizations #73