uniqueidentifier - Is there a unique Android device ID?

ID : 202

viewed : 262

Tags : androiduniqueidentifierandroid

Top 5 Answer for uniqueidentifier - Is there a unique Android device ID?

vote vote


Settings.Secure#ANDROID_ID returns the Android ID as an unique for each user 64-bit hex string.

import android.provider.Settings.Secure;  private String android_id = Secure.getString(getContext().getContentResolver(),                                                         Secure.ANDROID_ID); 

Also read Best practices for unique identifiers: https://developer.android.com/training/articles/user-data-ids

vote vote


UPDATE: As of recent versions of Android, many of the issues with ANDROID_ID have been resolved, and I believe this approach is no longer necessary. Please take a look at Anthony's answer.

Full disclosure: my app used the below approach originally but no longer uses this approach, and we now use the approach outlined in the Android Developer Blog entry that emmby's answer links to (namely, generating and saving a UUID#randomUUID()).

There are many answers to this question, most of which will only work "some" of the time, and unfortunately, that's not good enough.

Based on my tests of devices (all phones, at least one of which is not activated):

  1. All devices tested returned a value for TelephonyManager.getDeviceId()
  2. All GSM devices (all tested with a SIM) returned a value for TelephonyManager.getSimSerialNumber()
  3. All CDMA devices returned null for getSimSerialNumber() (as expected)
  4. All devices with a Google account added returned a value for ANDROID_ID
  5. All CDMA devices returned the same value (or derivation of the same value) for both ANDROID_ID and TelephonyManager.getDeviceId() -- as long as a Google account has been added during setup.
  6. I did not yet have a chance to test GSM devices with no SIM, a GSM device with no Google account added, or any of the devices in airplane mode.

So if you want something unique to the device itself, TM.getDeviceId() should be sufficient. Obviously, some users are more paranoid than others, so it might be useful to hash 1 or more of these identifiers, so that the string is still virtually unique to the device, but does not explicitly identify the user's actual device. For example, using String.hashCode(), combined with a UUID:

final TelephonyManager tm = (TelephonyManager) getBaseContext().getSystemService(Context.TELEPHONY_SERVICE);  final String tmDevice, tmSerial, androidId; tmDevice = "" + tm.getDeviceId(); tmSerial = "" + tm.getSimSerialNumber(); androidId = "" + android.provider.Settings.Secure.getString(getContentResolver(), android.provider.Settings.Secure.ANDROID_ID);  UUID deviceUuid = new UUID(androidId.hashCode(), ((long)tmDevice.hashCode() << 32) | tmSerial.hashCode()); String deviceId = deviceUuid.toString(); 

might result in something like: 00000000-54b3-e7c7-0000-000046bffd97

It works well enough for me.

As Richard mentions below, don't forget that you need permission to read the TelephonyManager properties, so add this to your manifest:

<uses-permission android:name="android.permission.READ_PHONE_STATE" /> 

import libraries

import android.content.Context; import android.telephony.TelephonyManager; import android.view.View; 
vote vote


#Last Updated: 6/2/15

After reading every Stack Overflow post about creating a unique ID, the Google developer blog, and Android documentation, I feel as if the 'Pseudo ID' is the best possible option.

Main Issue: Hardware vs Software


  • Users can change their hardware, Android tablet, or phone, so unique IDs based on hardware are not good ideas for TRACKING USERS
  • For TRACKING HARDWARE, this is a great idea


  • Users can wipe/change their ROM if they are rooted
  • You can track users across platforms (iOS, Android, Windows, and Web)
  • The best want to TRACK AN INDIVIDUAL USER with their consent is to simply have them login (make this seamless using OAuth)

#Overall breakdown with Android

###- Guarantee uniqueness (include rooted devices) for API >= 9/10 (99.5% of Android devices) ###- No extra permissions

Psuedo code:

if API >= 9/10: (99.5% of devices)  return unique ID containing serial id (rooted devices may be different)  else  return the unique ID of build information (may overlap data - API < 9) 

Thanks to @stansult for posting all of our options (in this Stack Overflow question).

##List of options - reasons why/ why not to use them:

  • User Email - Software

  • User could change email - HIGHLY unlikely

  • API 5+ <uses-permission android:name="android.permission.GET_ACCOUNTS" /> or

  • API 14+ <uses-permission android:name="android.permission.READ_PROFILE" /> <uses-permission android:name="android.permission.READ_CONTACTS" /> (How to get the Android device's primary e-mail address)

  • User Phone Number - Software

  • Users could change phone numbers - HIGHLY unlikely

  • <uses-permission android:name="android.permission.READ_PHONE_STATE" />

  • IMEI - Hardware (only phones, needs android.permission.READ_PHONE_STATE)

  • Most users hate the fact that it says "Phone Calls" in the permission. Some users give bad ratings because they believe you are simply stealing their personal information when all you really want to do is track device installs. It is obvious that you are collecting data.

  • <uses-permission android:name="android.permission.READ_PHONE_STATE" />

  • Android ID - Hardware (can be null, can change upon factory reset, can be altered on a rooted device)

  • Since it can be 'null', we can check for 'null' and change its value, but this means it will no longer be unique.

  • If you have a user with a factory reset device, the value may have changed or altered on the rooted device so there may be duplicates entries if you are tracking user installs.

  • WLAN MAC Address - Hardware (needs android.permission.ACCESS_WIFI_STATE)

  • This could be the second-best option, but you are still collecting and storing a unique identifier that comes directly from a user. This is obvious that you are collecting data.

  • <uses-permission android:name="android.permission.ACCESS_WIFI_STATE "/>

  • Bluetooth MAC Address - Hardware (devices with Bluetooth, needs android.permission.BLUETOOTH)

  • Most applications on the market do not use Bluetooth, and so if your application doesn't use Bluetooth and you are including this, the user could become suspicious.

  • <uses-permission android:name="android.permission.BLUETOOTH "/>

  • Pseudo-Unique ID - Software (for all Android devices)

  • Very possible, may contain collisions - See my method posted below!

  • This allows you to have an 'almost unique' ID from the user without taking anything that is private. You can create your own anonymous ID from device information.

I know there isn't any 'perfect' way of getting a unique ID without using permissions; however, sometimes we only really need to track the device installation. When it comes to creating a unique ID, we can create a 'pseudo unique id' based solely on information that the Android API gives us without using extra permissions. This way, we can show the user respect and try to offer a good user experience as well.

With a pseudo-unique id, you really only run into the fact that there may be duplicates based on the fact that there are similar devices. You can tweak the combined method to make it more unique; however, some developers need to track device installs and this will do the trick or performance based on similar devices.

##API >= 9:

If their Android device is API 9 or over, this is guaranteed to be unique because of the 'Build.SERIAL' field.

REMEMBER, you are technically only missing out on around 0.5% of users who have API < 9. So you can focus on the rest: This is 99.5% of the users!

##API < 9:

If the user's Android device is lower than API 9; hopefully, they have not done a factory reset and their 'Secure.ANDROID_ID' will be preserved or not 'null'. (see http://developer.android.com/about/dashboards/index.html)

##If all else fails:

If all else fails, if the user does have lower than API 9 (lower than Gingerbread), has reset their device, or 'Secure.ANDROID_ID' returns 'null', then simply the ID returned will be solely based on their Android device information. This is where the collisions can happen.


  • Removed 'Android.SECURE_ID' because factory resets could cause the value to change
  • Edited the code to change on API
  • Changed the Pseudo

Please take a look at the method below:

/**  * Return pseudo unique ID  * @return ID  */ public static String getUniquePsuedoID() {     // If all else fails, if the user does have lower than API 9 (lower     // than Gingerbread), has reset their device or 'Secure.ANDROID_ID'     // returns 'null', then simply the ID returned will be solely based     // off their Android device information. This is where the collisions     // can happen.     // Thanks http://www.pocketmagic.net/?p=1662!     // Try not to use DISPLAY, HOST or ID - these items could change.     // If there are collisions, there will be overlapping data     String m_szDevIDShort = "35" + (Build.BOARD.length() % 10) + (Build.BRAND.length() % 10) + (Build.CPU_ABI.length() % 10) + (Build.DEVICE.length() % 10) + (Build.MANUFACTURER.length() % 10) + (Build.MODEL.length() % 10) + (Build.PRODUCT.length() % 10);      // Thanks to @Roman SL!     // https://stackoverflow.com/a/4789483/950427     // Only devices with API >= 9 have android.os.Build.SERIAL     // http://developer.android.com/reference/android/os/Build.html#SERIAL     // If a user upgrades software or roots their device, there will be a duplicate entry     String serial = null;     try {         serial = android.os.Build.class.getField("SERIAL").get(null).toString();          // Go ahead and return the serial for api => 9         return new UUID(m_szDevIDShort.hashCode(), serial.hashCode()).toString();     } catch (Exception exception) {         // String needs to be initialized         serial = "serial"; // some value     }      // Thanks @Joe!     // https://stackoverflow.com/a/2853253/950427     // Finally, combine the values we have found by using the UUID class to create a unique identifier     return new UUID(m_szDevIDShort.hashCode(), serial.hashCode()).toString(); } 

#New (for apps with ads AND Google Play Services):

From the Google Play Developer's console:

Beginning August 1st, 2014, the Google Play Developer Program Policy requires all-new app uploads and updates to use the advertising ID in lieu of any other persistent identifiers for any advertising purposes. Learn more



<uses-permission android:name="android.permission.INTERNET" /> 


import com.google.android.gms.ads.identifier.AdvertisingIdClient; import com.google.android.gms.ads.identifier.AdvertisingIdClient.Info; import com.google.android.gms.common.GooglePlayServicesAvailabilityException; import com.google.android.gms.common.GooglePlayServicesNotAvailableException; import java.io.IOException; ...  // Do not call this function from the main thread. Otherwise,  // an IllegalStateException will be thrown. public void getIdThread() {    Info adInfo = null;   try {     adInfo = AdvertisingIdClient.getAdvertisingIdInfo(mContext);    } catch (IOException exception) {     // Unrecoverable error connecting to Google Play services (e.g.,     // the old version of the service doesn't support getting AdvertisingId).     } catch (GooglePlayServicesAvailabilityException exception) {     // Encountered a recoverable error connecting to Google Play services.     } catch (GooglePlayServicesNotAvailableException exception) {     // Google Play services is not available entirely.   }   final String id = adInfo.getId();   final boolean isLAT = adInfo.isLimitAdTrackingEnabled(); } 


http://developer.android.com/google/play-services/id.html http://developer.android.com/reference/com/google/android/gms/ads/identifier/AdvertisingIdClient.html


It is intended that the advertising ID completely replace existing usage of other identifiers for ads purposes (such as the use of ANDROID_ID in Settings.Secure) when Google Play Services is available. Cases where Google Play Services is unavailable are indicated by a GooglePlayServicesNotAvailableException being thrown by getAdvertisingIdInfo().

##Warning, users can reset:


I have tried to reference every link that I took information from. If you are missing and need to be included, please comment!

Google Player Services InstanceID


vote vote


As Dave Webb mentions, the Android Developer Blog has an article that covers this. Their preferred solution is to track app installs rather than devices, and that will work well for most use cases. The blog post will show you the necessary code to make that work, and I recommend you check it out.

However, the blog post goes on to discuss solutions if you need a device identifier rather than an app installation identifier. I spoke with someone at Google to get some additional clarification on a few items in the event that you need to do so. Here's what I discovered about device identifiers that's NOT mentioned in the aforementioned blog post:

  • ANDROID_ID is the preferred device identifier. ANDROID_ID is perfectly reliable on versions of Android <=2.1 or >=2.3. Only 2.2 has the problems mentioned in the post.
  • Several devices by several manufacturers are affected by the ANDROID_ID bug in 2.2.
  • As far as I've been able to determine, all affected devices have the same ANDROID_ID, which is 9774d56d682e549c. Which is also the same device id reported by the emulator, btw.
  • Google believes that OEMs have patched the issue for many or most of their devices, but I was able to verify that as of the beginning of April 2011, at least, it's still quite easy to find devices that have the broken ANDROID_ID.

Based on Google's recommendations, I implemented a class that will generate a unique UUID for each device, using ANDROID_ID as the seed where appropriate, falling back on TelephonyManager.getDeviceId() as necessary, and if that fails, resorting to a randomly generated unique UUID that is persisted across app restarts (but not app re-installations).

Note that for devices that have to fallback on the device ID, the unique ID WILL persist across factory resets. This is something to be aware of. If you need to ensure that a factory reset will reset your unique ID, you may want to consider falling back directly to the random UUID instead of the device ID.

Again, this code is for a device ID, not an app installation ID. For most situations, an app installation ID is probably what you're looking for. But if you do need a device ID, then the following code will probably work for you.

import android.content.Context; import android.content.SharedPreferences; import android.provider.Settings.Secure; import android.telephony.TelephonyManager;  import java.io.UnsupportedEncodingException; import java.util.UUID;  public class DeviceUuidFactory {      protected static final String PREFS_FILE = "device_id.xml";     protected static final String PREFS_DEVICE_ID = "device_id";     protected volatile static UUID uuid;      public DeviceUuidFactory(Context context) {         if (uuid == null) {             synchronized (DeviceUuidFactory.class) {                 if (uuid == null) {                     final SharedPreferences prefs = context                             .getSharedPreferences(PREFS_FILE, 0);                     final String id = prefs.getString(PREFS_DEVICE_ID, null);                     if (id != null) {                         // Use the ids previously computed and stored in the                         // prefs file                         uuid = UUID.fromString(id);                     } else {                         final String androidId = Secure.getString(                             context.getContentResolver(), Secure.ANDROID_ID);                         // Use the Android ID unless it's broken, in which case                         // fallback on deviceId,                         // unless it's not available, then fallback on a random                         // number which we store to a prefs file                         try {                             if (!"9774d56d682e549c".equals(androidId)) {                                 uuid = UUID.nameUUIDFromBytes(androidId                                         .getBytes("utf8"));                             } else {                                 final String deviceId = (                                     (TelephonyManager) context                                     .getSystemService(Context.TELEPHONY_SERVICE))                                     .getDeviceId();                                 uuid = deviceId != null ? UUID                                     .nameUUIDFromBytes(deviceId                                             .getBytes("utf8")) : UUID                                     .randomUUID();                             }                         } catch (UnsupportedEncodingException e) {                             throw new RuntimeException(e);                         }                         // Write the value out to the prefs file                         prefs.edit()                                 .putString(PREFS_DEVICE_ID, uuid.toString())                                 .commit();                     }                 }             }         }     }      /**      * Returns a unique UUID for the current android device. As with all UUIDs,      * this unique ID is "very highly likely" to be unique across all Android      * devices. Much more so than ANDROID_ID is.      *       * The UUID is generated by using ANDROID_ID as the base key if appropriate,      * falling back on TelephonyManager.getDeviceID() if ANDROID_ID is known to      * be incorrect, and finally falling back on a random UUID that's persisted      * to SharedPreferences if getDeviceID() does not return a usable value.      *       * In some rare circumstances, this ID may change. In particular, if the      * device is factory reset a new device ID may be generated. In addition, if      * a user upgrades their phone from certain buggy implementations of Android      * 2.2 to a newer, non-buggy version of Android, the device ID may change.      * Or, if a user uninstalls your app on a device that has neither a proper      * Android ID nor a Device ID, this ID may change on reinstallation.      *       * Note that if the code falls back on using TelephonyManager.getDeviceId(),      * the resulting ID will NOT change after a factory reset. Something to be      * aware of.      *       * Works around a bug in Android 2.2 for many devices when using ANDROID_ID      * directly.      *       * @see http://code.google.com/p/android/issues/detail?id=10603      *       * @return a UUID that may be used to uniquely identify your device for most      *         purposes.      */     public UUID getDeviceUuid() {         return uuid;     } } 
vote vote


Here is the code that Reto Meier used in the Google I/O presentation this year to get a unique id for the user:

private static String uniqueID = null; private static final String PREF_UNIQUE_ID = "PREF_UNIQUE_ID";  public synchronized static String id(Context context) {     if (uniqueID == null) {         SharedPreferences sharedPrefs = context.getSharedPreferences(                 PREF_UNIQUE_ID, Context.MODE_PRIVATE);         uniqueID = sharedPrefs.getString(PREF_UNIQUE_ID, null);         if (uniqueID == null) {             uniqueID = UUID.randomUUID().toString();             Editor editor = sharedPrefs.edit();             editor.putString(PREF_UNIQUE_ID, uniqueID);             editor.commit();         }     }     return uniqueID; } 

If you couple this with a backup strategy to send preferences to the cloud (also described in Reto's talk, you should have an id that ties to a user and sticks around after the device has been wiped, or even replaced. I plan to use this in analytics going forward (in other words, I have not done that bit yet :).

Top 3 video Explaining uniqueidentifier - Is there a unique Android device ID?