http://www.whispersys.com/whispermonitor.html
it requires changes to the framework though, so it's only available in their own "whispercore" rom:
@ck2 is performing as thorough of a verification as possible without source code access. If I were a malicious app developer, however, I might program my app to wait a week before transmitting any user data.
But what I really want is the marketplaces to allow direct apk downloads because I always want to examine the file first on an emulator.
1) Adult-rated apps need an explicit approval after the password before they will even install. Also applies to updates.
2) On first launch, apps that want to use badges or notifications or notification sounds have to ask for approval, although it is a generic approval of all three and doesn't discuss what they would be fore.
3) Before an app can use location services (current device location), it has to explicitly ask.
1) This is pointless. If you want to block adult-apps, go ahead and do it in Parental Permissions. Especially since a lot of apps are adult because they do web stuff generically.
2) This is pointless, in my opinion, since you can't tell what they plan on doing with the alerts.
3) This works OK, although it is generally triggered after you request something location related so it feels redundant. Like, why is it asking me again, didn't I just click the location button? Does the average user understand that the prompt is coming from the OS rather than the app?
There's no easy way to add this to AOSP core in one swoop without making exceptions for legacy applications, to the point that no one would use it anyway.
I'd love to see this system evolve somehow to make permissions more granular, but it's going to be a breaking change and it's certainly not going to be implemented this way where fake data was returned. Not sure why people are shocked it works this way. I've tried to explain the breaking and problems that would occur from trying to implement this. Of course, a couple months ago when I tried to explain this, everyone here told me it was "simple" and that I just didn't understand. Oh well.
How would that not make an application crash? Additionally, returning fake data has it's own problems including at the very least integrity.
Some apps have some crazy requests that need explaining!
Does the iphone have any such granularity control for permissions? (official or unofficial)