Like why have the toggle in the first place if apps can detect it? Doesn’t letting apps know about it defeat the whole purpose?

  • eee@lemm.ee
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    It’s hard to make it undetectable. The lcoation API has to return something. If the location is “null” or “disabled”, then apps would know.

    Most apps play nice. Apps which force close/refuse to work without excessive permissions, i try not to use.

  • chris2112@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    In theory, devs need to know what setting you chose so that, if you legitimately need presicse location, you can tell the user to enable it. In practice I’m sure plenty of apps that claim they need precise location don’t really need it, but it’s not a restricted permission either so Google doesn’t do any validation during their review process

  • eatham 🇭🇲
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Some apps play nice, but most app that need location(like maps) would need exact location for their purpose.

  • kraken@u.fail
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Precision location leaks data about surrounding wifi networks to google. You can disable it, because a lot of people are uncomfortable with that.