Picon
Gravatar

Settings.Secure.ANDROID_ID not unique on DROID2?

I'm seeing hundreds (877 at last count) of Froyo equipped devices
using our app with the same ANDROID_ID this month. Normally, this ID
is a unique thing but now it isn't.

I'm guessing this is due to a custom ROM with some invalid settings as
the device is a DROID2 and as far as I know, the DROID2 hasn't been
released yet.

Here's the user agent string:

Dalvik/1.2.0 (Linux; U; Android 2.2; DROID2 Build/VZW)

Has anyone else run into this problem yet?

-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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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 Developers" group.
To post to this group, send email to android-developers <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Seni Sangrujee | 15 Aug 21:20
Picon

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

> 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 received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Kostya Vasilyev | 15 Aug 21:34
Picon

Re: Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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" <sangrujee <at> gmail.com> написал:

> 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 received this message because you are subscribed to the Google
Groups "Android Developers" ...

--
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
Mark Murphy | 15 Aug 21:59
Favicon
Gravatar

Re: Re: Settings.Secure.ANDROID_ID not unique on DROID2?

On Sun, Aug 15, 2010 at 2:10 PM, Maps.Huge.Info (Maps API Guru)
<coryat <at> gmail.com> 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 with it. Also, bear in mind that
CTS-type tests are unlikely to uncover this sort of problem, since
they only test one device at a time, AFAIK.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 3.1 Available!

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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 One
1	boydTouch HD2
2	thunderc

Here are the builds:

117	FRF91
2	MASTER
757	VZW

Looks like this problem is wider than just Motorola, although it could
be the other devices are custom ROM's.

-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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Mark Murphy | 15 Aug 22:53
Favicon
Gravatar

Re: Re: Settings.Secure.ANDROID_ID not unique on DROID2?

On Sun, Aug 15, 2010 at 4:47 PM, Maps.Huge.Info (Maps API Guru)
<coryat <at> gmail.com> 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       HTC Vogue FroYo
> 1       LG-MS690
> 2       MSM
> 4       Nexus One
> 1       boydTouch HD2
> 2       thunderc
>
> Here are the builds:
>
> 117     FRF91
> 2       MASTER
> 757     VZW

Just to clarify, by "this problem" you mean having the same ANDROID_ID
as others of its model, or having this one magic ANDROID_ID?

If the latter...do you distribute your app outside of the Android Market?

> Looks like this problem is wider than just Motorola, although it could
> be the other devices are custom ROM's.

Custom ROMs would be one possibility -- the ROM mixer might have
grabbed the ANDROID_ID value out of the emulator.

The reason I asked about distribution is that I seem to recall that
ANDROID_ID is somehow tied into Google accounts and the Android
Market. I'm wondering if this magic ANDROID_ID is the new default
value. If so, devices that are not set up with the Android Market
(e.g., emulator) might return this value. That wouldn't explain the
DROID2 -- if 100% of DROID2's aren't getting the Market, that'd be
*huge* -- but it might explain some of your other ones.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 3.1 Available!

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

OldSkoolMark | 16 Aug 06:27

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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)"
<cor...@gmail.com> 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       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 One
> 1       boydTouch HD2
> 2       thunderc
>
> Here are the builds:
>
> 117     FRF91
> 2       MASTER
> 757     VZW
>
> Looks like this problem is wider than just Motorola, although it could
> be the other devices are custom ROM's.
>
> -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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

>
> 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 because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

FrankG | 16 Aug 10:36

Re: Settings.Secure.ANDROID_ID not unique on DROID2?


On 16 Aug., 06:43, "Maps.Huge.Info (Maps API Guru)" <cor...@gmail.com>
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 same
> ANDROID_ID.
>
> -John Coryat

If you look into the SettingsProvider class, then you can see that
this is done using

SecureRandom random = SecureRandom.getInstance("SHA1PRNG");

When the persistent system property ro.serialno is set, then this
value
will be used to  reseeds this random object.

Later comes a random.nextLong transformed to a Hex-String.

Interessting might be this part of the javadoc:

"the system will determine if there is an implementation of the
algorithm requested available in the environment"

Maybe their is a problem with this SHA1PRNG algorithm ?

Try to set "ro.serialno"  with setprop ..

Good luck !

  Frank

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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 that's mostly with the DROID2.

-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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

String | 16 Aug 21:45

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

On Aug 16, 8:06 pm, "Maps.Huge.Info (Maps API Guru)"
<cor...@gmail.com> 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 <kmans...@gmail.com> wrote:

> So what should be used for the new licensing service on this device?

That's the thing I'm most concerned about as well, at this point. I'd
REALLY like to hear from Mountain View on that topic. Trevor, you
still out there?

String

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Trevor Johns | 18 Aug 03:00
Picon
Favicon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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?
(Settings > About phone > Build number)

Thanks!

--
Trevor Johns

On Aug 16, 12:45 pm, String <sterling.ud...@googlemail.com> wrote:
> On Aug 16, 8:06 pm, "Maps.Huge.Info (Maps API Guru)"
>
> <cor...@gmail.com> 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 <kmans...@gmail.com> wrote:
>
> > So what should be used for the new licensing service on this device?
>
> That's the thing I'm most concerned about as well, at this point. I'd
> REALLY like to hear from Mountain View on that topic. Trevor, you
> still out there?
>
> String

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

String | 18 Aug 07:45

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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 <trevorjo...@google.com> wrote:
> 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?
> (Settings > About phone > Build number)
>
> Thanks!
>
> --
> Trevor Johns
>
> On Aug 16, 12:45 pm, String <sterling.ud...@googlemail.com> wrote:
>
>
>
>
>
>
>
> > On Aug 16, 8:06 pm, "Maps.Huge.Info (Maps API Guru)"
>
> > <cor...@gmail.com> 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 <kmans...@gmail.com> wrote:
>
> > > So what should be used for the new licensing service on this device?
>
> > That's the thing I'm most concerned about as well, at this point. I'd
> > REALLY like to hear from Mountain View on that topic. Trevor, you
> > still out there?
>
> > String

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

DanH | 18 Aug 03:20
Picon

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

Could this behavior be explained by someone cloning phones?

On Aug 16, 2:06 pm, "Maps.Huge.Info (Maps API Guru)"
<cor...@gmail.com> 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       HTC HD2
> 4       HTC Vogue FroYo
> 40      MSM
> 10      Nexus One
>
> Builds:
>
> 29      FRF91
> 44      MASTER
> 24      VZW
>
> Seems to be a problem that's mostly with the DROID2.
>
> -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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

OldSkoolMark | 18 Aug 07:48

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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)"
<cor...@gmail.com> 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 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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Picon
Gravatar

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

>
> 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 are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Nathan | 18 Aug 17:39

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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)"
<cor...@gmail.com> 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

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Nathan | 18 Aug 17:49

Re: Settings.Secure.ANDROID_ID not unique on DROID2?

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);

		String imei = manager.getDeviceId();

Nathan

On Aug 18, 7:41 am, "Maps.Huge.Info (Maps API Guru)"
<cor...@gmail.com> 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

--

-- 
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 <at> googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe <at> googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Gmane