ANDROID_ID - when is it set?

by Paul » Wed, 11 Aug 2010 02:01:40 GMT


Sponsored Links
 I've got an app that requires a unique ID for each device.

Either I use the ANDROID_ID or I use an ID I create myself (which is
fine).

I've found that ANDROID_ID isn't set immediately on every device...
(note: I *do* know that ANDROID_ID is not set on the emulator)

When is it set? Is it when the Google account is created on the
device?

Can't find docs on the subject...

--



ANDROID_ID - when is it set?

by Maps.Huge.Info (Maps API Guru) » Wed, 11 Aug 2010 02:31:04 GMT


 I don't know for certain but I believe the Android ID is set when the
OS is loaded. It's independent of the Google account.

There is no Android ID on the emulator.

-John Coryat

--


Sponsored Links


ANDROID_ID - when is it set?

by Wayne Wenthin » Wed, 11 Aug 2010 04:53:38 GMT


 There is an android id on the emulator now.  It was added in the 2.1 update
I think.  I know it broke my code because I relied on NULL.

On Tue, Aug 10, 2010 at 11:30 AM, Maps.Huge.Info (Maps API Guru) <



>



ANDROID_ID - when is it set?

by Paul Johnston » Thu, 12 Aug 2010 06:24:41 GMT


 On a 1.6 device before you setup the google account there is no ANDROID_ID
but there is a device id.




There is an android id on the emulator now.  It was added in the 2.1 update
I think.  I know it broke my code because I relied on NULL.



On Tue, Aug 10, 2010 at 11:30 AM, Maps.Huge.Info (Maps API Guru) <


-- 
Follow us on Twitter  @fuliginsoftware
Join the forums.
 http://www.fuligin.com/forums 



--



Other Threads

1. Orientation Sensor problems.

Hi All,

Hoping someone can help me make sense of my problem,  Using eclipse to
create a v1.5 compass application for my tmobile G1.  What i'm
experiencing is wacky heading results from the orientation sensor.

the important bits of my code are :

the setup of the sensor is >>

sensorManager = (SensorManager)getSystemService
(Context.SENSOR_SERVICE);
if (sensorManager != null) {
        Sensor orsensor = sensorManager.getSensorList
(Sensor.TYPE_ORIENTATION).get(0);
        sensorManager.registerListener(sensorListener, orsensor,
SensorManager.SENSOR_DELAY_NORMAL);
}

And my listener is defined as :
private final SensorEventListener sensorListener = new
SensorEventListener() {

                public void onAccuracyChanged(Sensor sensor, int accuracy) {}

                public void onSensorChanged(SensorEvent event) {
                        updateOrientation(event.values[0],
                                        event.values[1],
                                        event.values[2]);
                        Log.d("sensor","Sensor event: 
"+event.sensor.toString()+"//
"+event.values[0]+" "+event.values[1]+" "+event.values[2]);

                }
        };



When I run the app',  my heading values are always being reported as
being between 250 - 270 and don't alter from that irrelevant of which
way I'm pointing the device.

Theres nothing physically wrong with the hardware as all other apps
which use the sensors work fine so i'm confused, i'm sure its
something silly i've missed off.

If anyone can see a problem, please let me know it's greatly
appreciated..

Thanks

--~--~---------~--~----~------------~-------~--~----~

2. adb: command not found

This is more of a unix question.  In my terminal, I cd to my tools
directory, adb is right there, and I type adb, and get "adb: command
not found".   If I "cat ~/.bash_profile", I get the path that I expect
(It looks right, is there a way to verify?).

What can I try next?  I am Unix challenged, so pls explain with
detail, if you have suggestions, thanks.

I am on Mac OS X 10.5.6, and Android SDK 1.5.


--~--~---------~--~----~------------~-------~--~----~

3. How to send email using my application?

4. webservices-android-ksoap2 ? can i find the answer in this group

5. Join an app test group?

6. How to incorporate external library for android JNI project for a device

7. Camera Force Closed 9/10 of the times