Google released Android 17 in June with four new network protections designed to tighten security for users. These changes matter because they shift how apps handle private data, specifically by encrypting browsing destinations and restricting background Wi-Fi scans. Developers building for the new version will see immediate effects, while those sticking to older standards may face reduced privacy features.
New encryption and permission rules target apps built for API level 37
The operating system targets apps that explicitly support Android 17, which corresponds to API level 37. This versioning creates a clear divide in how network traffic is handled. Applications built for Android 16 or earlier do not receive the new encryption protections on Android 17 devices. Users running older apps will see their network requests sent without the latest security wrappers.
Encrypted Client Hello (ECH) is now enabled for apps targeting Android 17. This feature encrypts the destination hostname during TLS handshakes, preventing third parties from seeing which websites users visit. The protection does not extend to apps targeting Android 16, which receive no ECH encryption on these devices. Developers using the OkHttp 5.5.0 library can enable this support, though it remains an optional feature that requires explicit configuration.
Android 17 introduces a new permission requirement for apps that scan for Wi-Fi devices. This restriction applies only to apps targeting Android 17, limiting background discovery capabilities for older software. Carriers can also use a switch available since Android 12 to turn off 2G networks for their customers. This move helps prevent SMS blaster attacks, although Google has not named specific carriers that have enabled this feature. We looked at the last Android 17 update, several of the same balance and stability themes came up.
Google published these details in a blog post alongside documentation from Android Developers and the OkHttp Changelog. The company acknowledges that it does not disclose the current adoption rate of Encrypted DNS among websites. It states that it is working with the industry to speed up adoption without providing specific metrics. The update confirms these four specific security mechanisms are active in the June release.
Source: NotebookCheck
Discussion
0 comments