Nathan,
The docs say that getDeviceId is the IMEI for GSM or its equivalent for
CDMA devices.
Glad it works for you, but I have two issues with this:
1 - It requires a special permission, for no good reason from users'
point of view (unless the app already needs this).
2 - There might be devices that don't return the IMEI correctly, just
like the DROID 2 doesn't generate the ANDROID_ID correctly.
Note that using the right IMEI value in the low-level cellular radio
code (so phone calls work) and returning it all the way to application
layer are two different things, at least it would seem that way.
-- Kostya
18.08.2010 19:39, Nathan пишет:
Great. I can just wait to see if angry customers ask why their trial
is already over.
Nonetheless, I couldn't find 9774d56d682e549c among my trial users.
Maybe no Droid 2s have tried it yet.
I'm using this as the id but I believe it does the same as ANDROID_ID.
TelephonyManager manager =
(TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE);
String imei = manager.getDeviceId();
Nathan
On Aug 18, 7:41 am, "Maps.Huge.Info (Maps API Guru)"
<[email protected]> wrote:
Do you think this should be logged at code.google.com as an issue. I
did as search for ANDROID_ID there and nothing came up.
I think the right people are looking into this problem. Hopefully, it
will turn out to be easy to correct.
-John Coryat
--
Kostya Vasilev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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-developers?hl=en
