4 ms·
One of the reasons behind this is location, where there are a class of apps which could conceivably rely on you not being able to lie about it. (The existing mo
by fidotron 12y ago
One of the reasons behind this is location, where there are a class of apps which could conceivably rely on you not being able to lie about it. (The existing mock location facilities explicitly notify apps they are mock for this reason).
However, the use of this feature for it in practice is . . . non-existent.
Google also famously went crazy when Motorola almost used Skyhook as network location provider for the Droid, on the basis that such information feeding back into their systems might be inaccurate and thus pollute their data collection activities. (They use Android devices as modern proxies for the WiFi slurping the streetmap cars used to do). As such Google have absolutely no incentive to resolve this problem as they are reliant on you not lying to them about where you are.
What's fun is J2ME got this right. Apps couldn't just assume they had permission for certain tasks, and users would be asked when the app wanted to do something. If the user refused you'd get an exception, but you were expected to handle it gracefully. It really wasn't that big of a problem, except for the user experience of the prompts some manufacturers chose to implement being fairly horrible.
- macspoofing 12y ago>where there are a class of apps which could conceivably rely on you not being able to lie about it. I don't think having 'mock' data is the right approach, but as you mentioned below, it's enough that the relevant API simply throw a security exception and let the app handle it gracefully. >If the user refused you'd get an exception, but you were expected to handle it gracefully. And that's absolutely the right approach. >It really wasn't that big of a problem, except for the user experience of the prompts some manufacturers chose to implement being fairly horrible. That should be handled by the OS, which would completely negate this issue.
- PeterisP 12y agoExceptions are not a solution - instead of the OS request "grant permission X to install the app" you get an app request "grant permission X to run the app". This is the exact scenario that needs to be avoided - if the app developer wants something that I don't want to give, then you can't rely on cooperation from the app. The whole point is that if a flaslight app wants to read my SMS, then I shouldn't have to choose between using that app and keeping my privacy; the OS is perfectly capable of keeping that app in an ignorant bliss thinking that it read my SMS and can turn on the light.
- babuskov 12y ago> flaslight app wants to read my SMS I got so frustrated with flashlight apps asking for Internet access to show ads and getting stuck when there is no Internet (typically the same time when I need a flashlight) that I wrote one and made it completely permission free: https://play.google.com/store/apps/details?id=com.bigosaur.lampa https://play.google.com/store/apps/details?id=com.bigosaur.l...
- phpnode 12y agohey, this looks great, but it's not actually working on either on either of my nexus 5s, is that a known issue? There's no crash or anything, the flashlight just doesn't actually turn on.
- babuskov 12y agoApparently there are two APIs available for this. Unfortunatelly, none of the devices I have at hand use the other API so I cannot test. :( If you want, I can send you the source code to try to modify it. Just e-mail me.
- TeMPOraL 12y agoBeautiful in its simplicity. It Just Works. Tested on S4. Sharing with friends ;).
- wprzyb 12y agobecause using system flashlight app is too edgy, huh? Why you need extra app for thing you have just build in Android ? Check your widgets for "Assistive light". Problem solved.
- TeMPOraL 12y agoBecase that thing is built-in in Android since 4.2, which is fairly recent. People needed flashlight apps even two years ago.
- Zigurd 12y agoAndroid could shift to revocable "a la carte" permissions just easily, and could ease the transition by granting sets of permissions for old apps, but substituting, for example, an empty Contacts database for the real one if the user opts out of that permission. Google couldn't even argue that getting fake data is harmful, as long as the data is forthrightly null or unavailable. Location apps have to deal with the lack of location data. Apps that access SMS have to deal with devices that don't get SMS messages. I hope alternative Android distributions mature to the point that some OEMs will choose to provide more-private "remixes" of Android based on these distributions and on ecosystem partners like DDG.