alostpacket
Over Macho Grande?
I chuckle that they added "and the like" at the end. Google really needs to hire some project managers and proofreaders. I love that they are a company full of engineers and developers but it's like whoever was writing that description got distracted mid-sentence and stop caring so they finished with "and the like" heh.
And yeah the developer docs are #$%^ing TERRIBLE. /end rant
Anyways, back on topic: The thing about the IMEI is that it's not all that dangerous. WiFi only tablets don't even have an IMEI/IMSI and any app can give you it's own version of a unique ID number right when it's installed. I wouldn't grant it out willy nilly to everyone.... But for now, I wouldn't worry too much about it. I fully expect them to split that permission in two or three in Ice Cream.
The most obvious "danger" it poses is that someone like an ad network can aggregate data from multiple apps with different permissions and match them all together with an IMEI. However this is possible on your home computer with just a cookie in the browser. And would still be possible without an IMEI with just a file on your SD in Android.
So at the end of the day you, or I, or most people will probably let our IMEI out to some shady (but maybe not malicious) characters. And at the end of the day there isn't a lot they can do with it.
Going forward too, Android is going to require hardware makers to provide a unique ID for app devs to use. It's pretty fundamental for any kind of tracking & DRM/copy protection. It's just that the IMEI is what was used because there was no uniform ID accross different hardware, and now with so many WiFi tablets, it isn't recommended.
Android Developers Blog: Identifying App Installations
What I'd really like to see:
1) Read Phone State: gives app the following states/events: idle, incoming call, outgoing call, in call. (with no further information).
2) Read Phone Call details: gives app the numbers being called/calling in.
3) Read Phone Network ID (GSM/CDMA/LTE/HSPA)
Most apps would only need #1.
Dialer replacements could ask for #1 and #2.
And hardly any apps would need #3.
NOTE: before anyone comes saying they can use my IMEI and spoof me on the network, sure there are some very advanced hacks out there that can do stuff like that. However, they require a VERY high level of technical knowledge and having someome's IMEI wouldn't matter at that point. At that level of tech knowledge people could imporsonate a GSM tower or just make up an IMEI, they wouldn't care about your IMEI.
And yeah the developer docs are #$%^ing TERRIBLE. /end rant
Anyways, back on topic: The thing about the IMEI is that it's not all that dangerous. WiFi only tablets don't even have an IMEI/IMSI and any app can give you it's own version of a unique ID number right when it's installed. I wouldn't grant it out willy nilly to everyone.... But for now, I wouldn't worry too much about it. I fully expect them to split that permission in two or three in Ice Cream.
The most obvious "danger" it poses is that someone like an ad network can aggregate data from multiple apps with different permissions and match them all together with an IMEI. However this is possible on your home computer with just a cookie in the browser. And would still be possible without an IMEI with just a file on your SD in Android.
So at the end of the day you, or I, or most people will probably let our IMEI out to some shady (but maybe not malicious) characters. And at the end of the day there isn't a lot they can do with it.
Going forward too, Android is going to require hardware makers to provide a unique ID for app devs to use. It's pretty fundamental for any kind of tracking & DRM/copy protection. It's just that the IMEI is what was used because there was no uniform ID accross different hardware, and now with so many WiFi tablets, it isn't recommended.
Android Developers Blog: Identifying App Installations
What I'd really like to see:
1) Read Phone State: gives app the following states/events: idle, incoming call, outgoing call, in call. (with no further information).
2) Read Phone Call details: gives app the numbers being called/calling in.
3) Read Phone Network ID (GSM/CDMA/LTE/HSPA)
Most apps would only need #1.
Dialer replacements could ask for #1 and #2.
And hardly any apps would need #3.
NOTE: before anyone comes saying they can use my IMEI and spoof me on the network, sure there are some very advanced hacks out there that can do stuff like that. However, they require a VERY high level of technical knowledge and having someome's IMEI wouldn't matter at that point. At that level of tech knowledge people could imporsonate a GSM tower or just make up an IMEI, they wouldn't care about your IMEI.