3 ms·

This is the reason I've been so frustrated with working with bluetooth devices on Android. Android places all bluetooth usage under Location permissions, and if

This is the reason I've been so frustrated with working with bluetooth devices on Android. Android places all bluetooth usage under Location permissions, and if you need talk to bluetooth devices in the background, users have to manually consent to background location tracking, even though that's not what we want to actually do.

mirntyfirty 4y ago
Is this because it automatically becomes possible to obtain location when accessing Bluetooth?
- alephxyz 4y ago
  It's because it's easy to estimate someone's location from nearby Bluetooth beacons or wifi access points.
- lern_too_spel 4y ago
  This is in fact what most iOS apps that ask for Bluetooth permission use it for. https://www.theverge.com/2019/9/19/20867286/ios-13-bluetooth-permission-privacy-feature-apps https://www.theverge.com/2019/9/19/20867286/ios-13-bluetooth...
mormegil 4y ago
IIANM, this is only when _scanning_: as soon as you pair/bond with a device, the app can communicate with it even with the location permission switched off.
gnabgib 4y ago
Unless I'm misunderstanding you, none of this is true for the Android devices I've owned. Vendor specific perhaps? Devious way to do it. Doesn't Apple suffer with the same problem (location+bluetooth tied?)
- lern_too_spel 4y ago
  It depends on the targetSdkVersion. https://www.androidpolice.com/2021/05/19/android-12-apps-wont-ask-for-location-permissions-when-all-they-want-is-bluetooth-scanning-which-yes-was-a-thing/ https://www.androidpolice.com/2021/05/19/android-12-apps-won...
  - gnabgib 4y ago
    That article says that from Android 6-12 if an app wanted to scan for bluetooth it ALSO had to require the location permission. Not that BT had hidden location information. As of Android 12 apps could bluetooth scan without requesting/enabling location.
    - lern_too_spel 4y ago
      That's what the person you're replying to said as well. In order to use Bluetooth, their app had to request a location permission from the user. If they wrote an app targeting a version of Android before that range, the permission would be requested for them even if their code didn't explicitly request it. If they targeted a version in that range, they would have to request the permission at build time.

mirntyfirty 4y ago

Is this because it automatically becomes possible to obtain location when accessing Bluetooth?

alephxyz 4y ago
It's because it's easy to estimate someone's location from nearby Bluetooth beacons or wifi access points.
lern_too_spel 4y ago
This is in fact what most iOS apps that ask for Bluetooth permission use it for. https://www.theverge.com/2019/9/19/20867286/ios-13-bluetooth-permission-privacy-feature-apps https://www.theverge.com/2019/9/19/20867286/ios-13-bluetooth...

mormegil 4y ago

IIANM, this is only when _scanning_: as soon as you pair/bond with a device, the app can communicate with it even with the location permission switched off.

gnabgib 4y ago

Unless I'm misunderstanding you, none of this is true for the Android devices I've owned. Vendor specific perhaps? Devious way to do it. Doesn't Apple suffer with the same problem (location+bluetooth tied?)

lern_too_spel 4y ago
It depends on the targetSdkVersion. https://www.androidpolice.com/2021/05/19/android-12-apps-wont-ask-for-location-permissions-when-all-they-want-is-bluetooth-scanning-which-yes-was-a-thing/ https://www.androidpolice.com/2021/05/19/android-12-apps-won...
- gnabgib 4y ago
  That article says that from Android 6-12 if an app wanted to scan for bluetooth it ALSO had to require the location permission. Not that BT had hidden location information. As of Android 12 apps could bluetooth scan without requesting/enabling location.
  - lern_too_spel 4y ago
    That's what the person you're replying to said as well. In order to use Bluetooth, their app had to request a location permission from the user. If they wrote an app targeting a version of Android before that range, the permission would be requested for them even if their code didn't explicitly request it. If they targeted a version in that range, they would have to request the permission at build time.