For a lot of apps the life cycle events for activities are enough, no need bother with whether the user is in a call or not. And isn't the audio focus mechanism enough for most media/music apps unless you need to support API level < 8?
If you worry about IMEI, what about Wifi MAC? And what about the phone numbers of those you are in a call with? =) On Friday, August 17, 2012 2:17:30 AM UTC+2, CapnShiner wrote: > > I do not understand why permissions are still combined for phone state and > identity. I have no problem letting an app see that my phone is ringing or > that I'm on a call. I understand that many apps need this permission so > that they do not prevent normal operation of the device and its ability to > make and receive calls. On the other hand, very few apps need to know the > phone's MEID, which is personally identifiable information. I see no reason > why anyone should have to share such sensitive information just to install > the latest tower defense game. Permissions with varying degrees of > sensitivity or security should not be grouped together. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
