3 ms·
According to Google [1], it was never meant to ship at that point as it was not ready for general public. There was some compatibility problems with many applic
by Maakuth 13y ago
According to Google [1], it was never meant to ship at that point as it was not ready for general public. There was some compatibility problems with many applications, so that is somewhat believable.
[1] http://www.dailytech.com/Google+Removes+App+Ops+Privacy+Control+Feature+from+Android+442/article33936.htm http://www.dailytech.com/Google+Removes+App+Ops+Privacy+Cont...
- blueskin_ 13y agoOf course, they have to spin it some way, because they're years past the point they could be honest and believed. I think it's more likely one google engineer wanted to resist the constant invasion of privacy and likely ended up paying with his job.
- skj 13y ago"more likely one google engineer wanted to resist the constant invasion of privacy" One engineer can't launch a product alone. Just isn't possible unless its under a personal name. "and likely ended up paying with his job." 0% chance.
- king_jester 13y agoApp Ops throws SecurityExceptions when you try to access a permission, it doesn't return empty data. You can imagine that most apps didn't build exception handling into the feature access that is required in the manifest at install time. That is the primary reason why it is not a fully public feature for users.