惟一標識碼這東西在網絡應用中很是有用,例如檢測是否重複註冊之類的。
import android.provider.Settings.Secure;
private String android_id = Secure.getString(getContext().getContentResolver(), Secure.ANDROID_ID);
咱們在項目過程當中或多或少會使用到設備的惟一識別碼,咱們但願可以獲得一個穩定、可靠的設備惟一識別碼。今天咱們將介紹幾種方式。
1. DEVICE_ID
假設咱們確實須要用到真實設備的標識,可能就須要用到DEVICE_ID。在之前,咱們的Android設備是手機,這個DEVICE_ID能夠同經過TelephonyManager.getDeviceId()獲取,它根據不一樣的手機設備返回IMEI,MEID或者ESN碼,但它在使用的過程當中會遇到不少問題:
- 非手機設備: 若是隻帶有Wifi的設備或者音樂播放器沒有通話的硬件功能的話就沒有這個DEVICE_ID
- 權限: 獲取DEVICE_ID須要READ_PHONE_STATE權限,但若是咱們只爲了獲取它,沒有用到其餘的通話功能,那這個權限有點大才小用
- bug:在少數的一些手機設備上,該實現有漏洞,會返回垃圾,如:zeros或者asterisks的產品
2. MAC ADDRESS
咱們也能夠經過手機的Wifi或者藍牙設備獲取MAC ADDRESS做爲DEVICE ID,可是並不建議這麼作,由於並非全部的設備都有Wifi,而且,若是Wifi沒有打開,那硬件設備沒法返回MAC ADDRESS.
3. Serial Number
在Android 2.3能夠經過android.os.Build.SERIAL獲取,非手機設備能夠經過該接口獲取。
4. ANDROID_IDANDROID_ID是設備第一次啓動時產生和存儲的64bit的一個數,當設備被wipe後該數重置
ANDROID_ID彷佛是獲取Device ID的一個好選擇,但它也有缺陷:
- 它在Android <=2.1 or Android >=2.3的版本是可靠、穩定的,但在2.2的版本並非100%可靠的
- 在主流廠商生產的設備上,有一個很常常的bug,就是每一個設備都會產生相同的ANDROID_ID:9774d56d682e549c
5. Installtion ID : UUID
以上四種方式都有或多或少存在的必定的侷限性或者bug,在這裏,有另一種方式解決,就是使用UUID,該方法無需訪問設備的資源,也跟設備類型無關。
這種方式是經過在程序安裝後第一次運行後生成一個ID實現的,但該方式跟設備惟一標識不同,它會由於不一樣的應用程序而產生不一樣的ID,而不是設備惟一ID。所以常常用來標識在某個應用中的惟一ID(即Installtion ID),或者跟蹤應用的安裝數量。很幸運的,Google Developer Blog提供了這樣的一個框架:
public class Installation {
private static String sID = null;
private static final String INSTALLATION = "INSTALLATION";
public synchronized static String id(Context context) {
if (sID == null) {
File installation = new File(context.getFilesDir(), INSTALLATION);
try {
if (!installation.exists())
writeInstallationFile(installation);
sID = readInstallationFile(installation);
} catch (Exception e) {
throw new RuntimeException(e);
}
}
return sID;
}
private static String readInstallationFile(File installation) throws IOException {
RandomAccessFile f = new RandomAccessFile(installation, "r");
byte[] bytes = new byte[(int) f.length()];
f.readFully(bytes);
f.close();
return new String(bytes);
}
private static void writeInstallationFile(File installation) throws IOException {
FileOutputStream out = new FileOutputStream(installation);
String id = UUID.randomUUID().toString();
out.write(id.getBytes());
out.close();
}
}
總結
綜合以上所述,爲了實如今設備上更通用的獲取設備惟一標識,咱們能夠實現這樣的一個類,爲每一個設備產生惟一的UUID,以ANDROID_ID爲基礎,在獲取失敗時以TelephonyManager.getDeviceId()爲備選方法,若是再失敗,使用UUID的生成策略。
重申下,如下方法是生成Device ID,在大多數狀況下Installtion ID可以知足咱們的需求,可是若是確實須要用到Device ID,那能夠經過如下方式實現:
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 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;
}
}
代碼: 這裏是你在Android裏讀出 惟一的 IMSI-ID / IMEI-ID 的方法。 Java: String myIMSI = android.os.SystemProperties.get(android.telephony.TelephonyProperties.PROPERTY_IMSI); // within my emulator it returns: 310995000000000 String myIMEI = android.os.SystemProperties.get(android.telephony.TelephonyProperties.PROPERTY_IMEI); // within my emulator it returns: 000000000000000
注:android.os.SystemProperties的標籤被打上@hide了,因此sdk中並不會存在。若是須要使用,須要有android的source code支持。