Quite simply, one could combine the ANDROID_ID and IMEI as a single
string, comma-delimited and use that as a unique identifier.
You might get "0123456789ABCDEF,null" for a prototype tablet though.
This assumes that all WiFi-only devices have unique ANDROID_IDs and
all phones have unique IMEIs.
Is the ANDROID_ID the id that is used to identify phones/emulators in
ddms?
My phone has the rather unlikely id 0123456789ABCDEF.
I guess my roms maker took the xkcd approach to random numbers.
http://xkcd.com/221/
On Oct 20, 4:48 am, John Coryat wrote:
> It's not only the DROID2 that has this i
It's not only the DROID2 that has this issue. There are several handsets
that have this "poisonous" ANDROID_ID. In our files, there are over 140,000
users with the id 9774d56d682e549c.
It's really not something that can be counted on being unique.
-John Coryat
--
You received this message bec
On Wed, Oct 19, 2011 at 7:48 PM, Nick wrote:
> Bringing this back from the dead (sorry)... Has this been fixed? What's the
> current status on this?
http://android-developers.blogspot.com/2011/03/identifying-app-installations.html
"First, it is not 100% reliable on releases of Android prior to
Bringing this back from the dead (sorry)... Has this been fixed? What's the
current status on this?
--
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 fr
We are seeing various devices still with this problem, we launched our
application 2 weeks ago, models we are seeing using the magic
ANDROID_ID:
Comeet
Dell
GT-I9000
GT-I9000B
GT-I9000M
GT-I9000T
GT-P1000
HTC
LG-P500
LS670
SAMSUNG-SGH-I897
SGH-T959
U8800
Vortex
ZTE-BLADE
On Dec 1 2010, 9:33 pm, F
Yes, I can verify that this is also true for the Samsung Galaxy Tab,
at least the one I've used.
--
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 th
I just saw a report about this unique ID issue affecting Galaxy Tabs
too.
Does anyone have one to verify?
Issue 10639:ANDROID_ID not random if ro.serialno isn't set
http://code.google.com/p/android/issues/detail?id=10639
Comment 2 by ddlatham, Today (16 minutes ago)
This
I don't understand why they don't use the MAC address of the Wifi
radio instead. It would be unique among all devices and eliminates the
worry of whether it is a phone or some sort of tablet device as all
android devices seem to have a wifi radio in them.
On Oct 15, 12:01 am, Scott Bonagofsky wro
Whatever the reason, please front-burner this issue for an OTA fix.
(Hopefully one that does not require a factory reset!) It is
preventing me from using the only dictation app in the Android Market
that seems to be worth a damn.
On Oct 14, 6:42 pm, Scott Bonagofsky wrote:
> Still no fix? I jus
Still no fix? I just bought a Droid 2 more than a month after
Motorola knew about this problem. Why didn't you fix the problem on
unsold phones before you sold them?
On Sep 30, 4:03 pm, JonFHancock wrote:
> The last update from Google/Verzion was half a month ago. Is there
> any progress to re
The last update from Google/Verzion was half a month ago. Is there
any progress to report?
On Sep 13, 11:48 am, "suzanne.alexandra"
wrote:
> Motorola is working on a fix for the ANDROID_ID issue on DROID 2. Any
> fix that becomes available will be upgraded to devices over the air. I
> don't have
On Sep 13, 3:42 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Suzanne,
>
> Thanks for keeping us in the loop.
>
> -John Coryat
>
> On Sep 13, 1:48 pm, "suzanne.alexandra"
>
>
>
> wrote:
> > Motorola is working on a fix for the ANDROID_ID issue on DROID 2. Any
> > fix that becomes available will
Wow this is really annoying. I hope it geta fixed soon, altough ill
probably have rewritten my app long before then
Thanks motorolla
On Sep 13, 2:48 pm, "suzanne.alexandra"
wrote:
> Motorola is working on a fix for the ANDROID_ID issue on DROID 2. Any
> fix that becomes available will be
Suzanne,
Thanks for keeping us in the loop.
-John Coryat
On Sep 13, 1:48 pm, "suzanne.alexandra"
wrote:
> Motorola is working on a fix for the ANDROID_ID issue on DROID 2. Any
> fix that becomes available will be upgraded to devices over the air. I
> don't have a timeline though.
>
> - Suzanne
Motorola is working on a fix for the ANDROID_ID issue on DROID 2. Any
fix that becomes available will be upgraded to devices over the air. I
don't have a timeline though.
- Suzanne
On Sep 8, 9:03 pm, gcstang wrote:
> Permission isn't as big an issue but the non phone part is definitely
> a conc
Permission isn't as big an issue but the non phone part is definitely
a concern.
Thank you for you answers
On Sep 8, 10:56 pm, William Ferguson
wrote:
> It also assumes the device is a phone.
> It may be a wifi only tablet, or whatever.
>
> On Sep 9, 2:09 am, "Maps.Huge.Info (Maps API Guru)"
>
It also assumes the device is a phone.
It may be a wifi only tablet, or whatever.
On Sep 9, 2:09 am, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Using IMEI requires an additional permission. Using ANDROID_ID
> doesn't.
>
> -John Coryat
--
You received this message because you are subscribed to th
Using IMEI requires an additional permission. Using ANDROID_ID
doesn't.
-John Coryat
--
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, s
What is the issue with using IMEI?
On Sep 7, 5:36 am, Opted Out wrote:
> I'm just coming into the market and can see some use for my
> application if each and everyone has a unique ID.
>
> Is there still issues or does it appear to be fixed?
>
> On Aug 18, 1:48 pm, "Maps.Huge.Info (Maps API Guru)
I'm just coming into the market and can see some use for my
application if each and everyone has a unique ID.
Is there still issues or does it appear to be fixed?
On Aug 18, 1:48 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> I'm relieved to see that I'm not the only one who's seeing the
> "mag
The new update 2.2.20.A955 does not fix the issue, even with a hard
reset the ANDROID_ID on my droid 2 is still 9774d56d682e549c.
On Aug 23, 10:20 am, Ben Pellow wrote:
> Assuming new devices are fixed moving forward, I'm curious about
> devices remaining in market with this problem. Will
>From what I understand, this is not something that will be addressed.
The devices that suffer the issue will retain the "magic" ID and won't
be fixed. It's not a huge problem unless you as a developer don't take
it into consideration.
-John Coryat
--
You received this message because you are su
Assuming new devices are fixed moving forward, I'm curious about
devices remaining in market with this problem. Will an OTA update to
Gingerbread fix the ANDROID_ID for clients with the default one? I'm
guessing ANDROID_ID persists across os updates and that only hard
reset will spawn a new one,
Perhaps this has already been answered in the originating thread, but
I couldn't find it. The LVL docs suggest using additional features
besides ANDROID_ID, and the question was which? Dianne Hackborne had
issues with using the IMEI. Is using the MAC address a better option?
On Aug 20, 12:04 pm, T
May I suggest doing an SHA-1 hash of the IMEI (if present) and the
ANDROID_ID?
Or if you don't need a fixed length, you can use the concatenation, or
you can fill in an IMEI of 0.
Finally, if you really want to get paranoid, you can check for the bad
ANDROID_ID, and if you have that, and no IMEI,
Great to hear this. Thanks.
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
21.08.2010 2:03 пользователь "suzanne.alexandra" <
suzanne.alexan...@motorola.com> написал:
An update from my side as well. We've been working with Trevor and
Google, and our kernel engineering team is aware of what
An update from my side as well. We've been working with Trevor and
Google, and our kernel engineering team is aware of what needs to
change.
- Suzanne
On Aug 20, 12:57 pm, FrankG wrote:
> Hi Trevor,
>
> This was my impression too on the 16th August
>
> "Try to set "ro.serialno" with setprop ..
Suzanne from Motorola - did you see the info from Trevor, below?
Trevor - perhaps testing for properly set ro.* should be added to CDD / CTS?
-- Kostya
20.08.2010 23:57, FrankG пишет:
Hi Trevor,
This was my impression too on the 16th August
"Try to set "ro.serialno" with setprop .."
But I
Hi Trevor,
This was my impression too on the 16th August
"Try to set "ro.serialno" with setprop .. "
But I assume that other vendors have also no clue about this property.
Good luck !
Frank
On 20 Aug., 21:04, Trevor Johns wrote:
> Hi everyone,
> Just to follow up a bit here, the reaso
Having to retrofit this into my code will be a nightmare for me. I don't
force upgrades and I rely on this in several places in my backend database.
I will be sending out a message and marking my app as not compatible
with the droid 2. Sigh.
On Fri, Aug 20, 2010 at 12:35 PM, Trevor Johns
Right now, we use the ANDROID_ID to prevent copying the license cache
between devices when using ServerManagedPolicy. In this case, you'll be able
to copy this cache between any two devices that have the same ANDROID_ID.
However, you still won't be able to modify the license cache, and you won't
b
How is the market licensing system affected by this?
-John Coryat
--
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
androi
Hi everyone,
Just to follow up a bit here, the reason we believe this is happening is
because ro.serialno isn't set on these devices. (Note that the ro.*
properties currently aren't required by the CDD/CTS.) Unfortunately, it
seems that we're using ro.serialno as the seed for the PRNG when generati
Andrew,
I don't know that this is reported in any public bug system. I've
reported it within a Motorola bug system.
- Suzanne
On Aug 20, 12:33 am, "Maps.Huge.Info (Maps API Guru)"
wrote:
> > John, have you had any complaints yet about conflicts from duplicate
> > unique ids?
>
> I handled it in
>
> John, have you had any complaints yet about conflicts from duplicate
> unique ids?
>
I handled it in code.
-John Coryat
--
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@googlegr
> Currently, I'm showing 1,168 DROID2's with that ANDROID_ID using my
> app.
John, have you had any complaints yet about conflicts from duplicate
unique ids?
-seni
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, sen
Suzanne,
Is this reported in any public bug tracking system?
On Aug 19, 6:35 pm, "suzanne.alexandra"
wrote:
> John, thanks for the number. I just filed a high-priority bug on this
> and will keep you updated.
>
> - Suzanne
>
> On Aug 19, 3:40 pm, "Maps.Huge.Info (Maps API Guru)"
>
> wrote:
> > S
John, thanks for the number. I just filed a high-priority bug on this
and will keep you updated.
- Suzanne
On Aug 19, 3:40 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Suzanne,
>
> All I can say is "Great" and "Bummer".
>
> Currently, I'm showing 1,168 DROID2's with that ANDROID_ID using my
>
Suzanne,
All I can say is "Great" and "Bummer".
Currently, I'm showing 1,168 DROID2's with that ANDROID_ID using my
app.
-John Coryat
--
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
Got it, thanks, my mistake. My DROID 2 here is returning the same
ANDROID_ID. Checking into it.
- Suzanne
On Aug 19, 2:44 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Perhaps Suzanne was thinking about another country... it certainly is
> out in the USA.
>
> -John Coryat
--
You received thi
Perhaps Suzanne was thinking about another country... it certainly is
out in the USA.
-John Coryat
--
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
On Aug 19, 9:54 pm, "suzanne.alexandra"
wrote:
> To confirm, the DROID 2 is not yet released.
Excuse me? By all accounts, the Droid 2 was released last week.
"the Droid 2 is now up for sale on Verizon" (Aug 11)
http://www.engadget.com/2010/08/11/verizon-droid-2-sales-begin/
"the Droid 2, which
So there is hope that this issue can be fixed before the release, correct?
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
20.08.2010 0:54 пользователь "suzanne.alexandra" <
suzanne.alexan...@motorola.com> написал:
I'm looking into this from Motorola - thanks to Mark for calling it to
my att
I'm looking into this from Motorola - thanks to Mark for calling it to
my attention. (You can also post questions on Motorola devices at
developer.motorola.com.)
To confirm, the DROID 2 is not yet released.
- Suzanne
On Aug 18, 10:18 am, Kostya Vasilyev wrote:
> How do they connect to the
On Aug 19, 2:54 am, Indicator Veritatis wrote:
> same on each unit? What do they think is going to happen when a
> customer loses a phone and asks the carrier to disable it? They do
> this by IMEI, not phone number.
Its simple, they don't provide the service to disable phones :)
Regards
Sarwar
It's my understanding this company doesn't make Android based phones, and if
they did, they won't be submitting them to Google for Android certification.
So no Market and no LVL for these.
It *is* pretty amazing, though.
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
19.08.2010 0:58 пользов
I am amazed the local telecom regulators let them get away with such a
blatant violation of the spec, one that pollutes the market and
network! So amazed, I have to doubt: is it really the IMEI that is the
same on each unit? What do they think is going to happen when a
customer loses a phone and as
On Aug 18, 10:48 am, "Maps.Huge.Info (Maps API Guru)"
wrote:
> I'm relieved to see that I'm not the only one who's seeing the "magic"
> ANDROID_ID problem.
Yeah, I'm surprised there haven't been more reports from apps that
depend on ANDROID_ID.
It looks like it's a known issue with custom ROMs f
On Aug 18, 11:18 pm, Kostya Vasilyev wrote:
> How do they connect to the cellular network if they all have the same
> IMEI?
>
> Or do they?
>
They do connect to the network, no restriction from the operators. The
problems we are facing that --- criminals are using those sets and as
their IMEI
I'm relieved to see that I'm not the only one who's seeing the "magic"
ANDROID_ID problem.
-John Coryat
--
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
But at least the IMEI is more likely to be unique, since telephone
connections depend on it, and checking its uniqueness (and
correspondence to the printed label) is probably written into some
stringent phone qualification tests.
On Aug 18, 10:49 am, Kostya Vasilyev wrote:
> Nathan,
>
> The doc
If this helps, here's what I'm seeing with my apps with the magic
ANDROID_ID=9774d56d682e549c
App #1 tracking urlConnection.getRequestProperty("User-Agent")
7-14 [***.mycingular.net] Dalvik/1.2.0 (Linux; U; Android 2.2; MSM
Build/MASTER)
8-14 (***.myvzw.com] Dalvik/1.2.0 (Linux; U; Android 2.2; D
On Aug 18, 9:25 am, Kostya Vasilyev wrote:
> No, this is different.
>
> IMEI is assigned to every phone before it leaves the factory, and
> doesn't change during its lifetime. It's often printed on the box.
>
> ANDROID_ID is generated by Android, and can change (e.g. when settings
> are reset)
How do they connect to the cellular network if they all have the same
IMEI?
Or do they?
-- Kostya
18.08.2010 21:02, Sarwar Erfan пишет:
On Aug 18, 10:25 pm, Kostya Vasilyev wrote:
IMEI is assigned to every phone before it leaves the factory, and
doesn't change during its lifetime. It's of
On Aug 18, 10:25 pm, Kostya Vasilyev wrote:
> IMEI is assigned to every phone before it leaves the factory, and
> doesn't change during its lifetime. It's often printed on the box.
Offtopic: We have thousands of "non-brand" phones with EXACT SAME IMEI
in our market --- all are imported from a s
No, this is different.
IMEI is assigned to every phone before it leaves the factory, and
doesn't change during its lifetime. It's often printed on the box.
ANDROID_ID is generated by Android, and can change (e.g. when settings
are reset).
If it works for you, it's great, but I would like t
I haven't seen that number yet. I'm still waiting for angry users
wondering why their trial expired already.
This is the code I use, but I think it returns the same as ANDROID_ID
TelephonyManager manager =
(TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE);
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
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
>
> 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
--
You received this message because you a
John,
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.
On Aug 17, 6:55 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> As far as I can tell, every DROID2 has the same ANDROID_ID. It's not
> just a couple, it's ALL. I don't
Hi Trevor,
It's good to hear from you on this issue.
I have to say, though, that if there's one company that I would have
expected to have an example of every device for testing, it's
Google...
String
On Aug 18, 2:00 am, Trevor Johns wrote:
> Hi everyone,
> I've been trying to investigate this
As far as I can tell, every DROID2 has the same ANDROID_ID. It's not
just a couple, it's ALL. I don't think it's cloning.
-John Coryat
--
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@
Could this behavior be explained by someone cloning phones?
On Aug 16, 2:06 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Update:
>
> Here are the numbers I've seen for July (ANDROID_ID =
> 9774d56d682e549c):
>
> 24 DROID2
> 4 DROIDX
> 3 European Vogue
> 11 HTC Desire
> 1
Hi everyone,
I've been trying to investigate this on my end, but unfortunately I
seem to having some trouble finding a Droid 2 in the office to
actually reproduce this with.
If anybody has access to a device that's exhibiting this behavior,
would you please send me a copy of the build fingerprint?
On Aug 16, 8:06 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Seems to be a problem that's mostly with the DROID2.
Yeah, I strongly suspect those others are indeed custom builds,
looking at the devices. What's an MSM?
On Aug 15, 8:34 pm, Kostya Vasilyev wrote:
> So what should be used for th
Update:
Here are the numbers I've seen for July (ANDROID_ID =
9774d56d682e549c):
24 DROID2
4 DROIDX
3 European Vogue
11 HTC Desire
1 HTC HD2
4 HTC Vogue FroYo
40 MSM
10 Nexus One
Builds:
29 FRF91
44 MASTER
24 VZW
Seems to be a problem
On 16 Aug., 06:43, "Maps.Huge.Info (Maps API Guru)"
wrote:
> > So prior to this month, there were no duplicate ANDROID_IDs? With pre-
> > Froyo devices?
>
> I can't say there were or weren't any duplicates pre-Froyo. I can say
> that every Droid2 that has downloaded my app "Radar Now!" has the s
>
> So prior to this month, there were no duplicate ANDROID_IDs? With pre-
> Froyo devices?
>
I can't say there were or weren't any duplicates pre-Froyo. I can say
that every Droid2 that has downloaded my app "Radar Now!" has the same
ANDROID_ID.
-John Coryat
--
You received this message becaus
So prior to this month, there were no duplicate ANDROID_IDs? With pre-
Froyo devices?
On Aug 15, 1:47 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> More on this bizarre error:
>
> Here are other devices I see (for the month of August only) that have
> this probem:
>
> 753 DROID2
> 4 DRO
My apps are distributed strictly through the Android market. All the
devices I listed have the same exact ANDROID_ID.
-John Coryat
--
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@goog
On Sun, Aug 15, 2010 at 4:47 PM, Maps.Huge.Info (Maps API Guru)
wrote:
> Here are other devices I see (for the month of August only) that have
> this probem:
>
> 753 DROID2
> 4 DROIDX
> 1 European Vogue
> 2 Full Android on Vogue
> 90 HTC Desire
> 15 HTC HD2
> 1
More on this bizarre error:
Here are other devices I see (for the month of August only) that have
this probem:
753 DROID2
4 DROIDX
1 European Vogue
2 Full Android on Vogue
90 HTC Desire
15 HTC HD2
1 HTC Vogue FroYo
1 LG-MS690
2 MSM
4 Nexus O
On Sun, Aug 15, 2010 at 2:10 PM, Maps.Huge.Info (Maps API Guru)
wrote:
> It appears the Droid2 has got a mistake in the OS. All Droid2 devices
> have the same ANDROID_ID: 9774d56d682e549c
>
> How in the heck could Motorola and Verizon make such a fatal error?
I don't think Verizon has much to do
So what should be used for the new licensing service on this device? Any
ideas?
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
15.08.2010 23:20 пользователь "Seni Sangrujee"
написал:
> have the same ANDROID_ID: 9774d56d682e549c
That's not good. This is not going to be fun to work around.
> have the same ANDROID_ID: 9774d56d682e549c
That's not good. This is not going to be fun to work around.
That looks like the same ANDROID_ID as here:
http://groups.google.com/group/android-developers/browse_thread/thread/f1b229e951114509/bcabfa6b83e153d1#bcabfa6b83e153d1
-seni
--
You receive
Update:
It appears the Droid2 has got a mistake in the OS. All Droid2 devices
have the same ANDROID_ID: 9774d56d682e549c
How in the heck could Motorola and Verizon make such a fatal error?
-John Coryat
--
You received this message because you are subscribed to the Google
Groups "Android Develo
78 matches
Mail list logo