Post #3552239

2026-07-03 07:38 UTC

@GrapheneOS@grapheneos.social @beistanbul@mastodon.social @eteryu@infosec.exchange > Apps not yet targeting Android 17 can now have it taken away after installation. Is it possible to take away from all apps by default? Also now enabling local network requires granting nearby devices which would allow bluetooth beacons too right?

Replies (1)

@eteryu@infosec.exchange 2026-07-03 08:02

@BucciaBuccia@mastodon.social @GrapheneOS@grapheneos.social @beistanbul@mastodon.social Unfortunately, it is not possible to strip it automatically by default for older apps because the compatibility mode is hardcoded into the OS baseline to prevent legacy apps from crashing instantly upon installation. We have to revoke it manually app by app until they update their target API to Android 17, just as GrapheneOS mentioned. Regarding Bluetooth beacons, there is a very important detail in how Android 17 handles this. The initial "Allow to keep app working" compatibility state is highly specific because it grants the app local network access only, without opening the door to Bluetooth scanning. However, if you toggle it off and then decide to grant it back by choosing the full "Allow" option, the app will indeed gain access to the whole group, including Bluetooth. As long as you leave older apps on the default compatibility status or completely revoke the permission, they cannot use Bluetooth beacons to track you.

Open ##3552238