On Oct 31, 2:39 pm, c beck <[email protected]> wrote: > > Actually, that is a pretty scary permission even if most uses of it are > benign. You can thank Google for not bothering to separate the ability to > read imei from making calls to 1-900 numbers. Or at least that was my > understanding of it when I looked into it earlier. >
I could wish they would separate "find unique identifier" from this permission. This is Market's description: READ PHONE STATE AND IDENTITY Allows the application to access the phone features of the device. An application with this permission can determine the phone number and serial number of this phone, whether a call is active, the number that call is connected to and the like. So I *could* find out your phone number and all the people you talk to and for how long. They just have to believe me that I have no interest in doing so. Some people will read "can" => "will", and for those people, no amount of explanation will help. The READ_LOG is even more scary for some people. READ SENSITIVE LOG DATA Allows an application to read from the system's various log files. This allows it to discover general information about what you are doing with the device, potentially including personal or private information. > At the very least, if you add a permission, any permission, make sure the > first line of "what's new" states it and says why. That is your best > chance at avoiding the mess, IMO. > It's good to do, but it's no guarantee. Nathan -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
