詳解Android獲取設(shè)備唯一ID的幾種方式
先來看看幾種比較單一的方式:
IMEI
方式:TelephonyManager.getDeviceId():
問題
- 范圍:只能支持擁有通話功能的設(shè)備,對(duì)于平板不可以。
- 持久性:返廠,數(shù)據(jù)擦除的時(shí)候不徹底,保留了原來的標(biāo)識(shí)。
- 權(quán)限:需要權(quán)限:Android.permission.READ_PHONE_STATE
- bug: 有些廠家的實(shí)現(xiàn)有bug,返回一些不可用的數(shù)據(jù)
Mac地址
ACCESS_WIFI_STATE權(quán)限
有些設(shè)備沒有WiFi,或者藍(lán)牙,就不可以,如果WiFi沒有打開,硬件也不會(huì)返回Mac地址,不建議使用
ANDROID_ID
2.2(Froyo,8)版本系統(tǒng)會(huì)不可信,來自主要生產(chǎn)廠商的主流手機(jī),至少有一個(gè)普遍發(fā)現(xiàn)的bug,這些有問題的手機(jī)相同的ANDROID_ID: 9774d56d682e549c
但是如果返廠的手機(jī),或者被root的手機(jī),可能會(huì)變
Serial Number
從Android 2.3 (“Gingerbread”)開始可用,可以通過android.os.Build.SERIAL獲取,對(duì)于沒有通話功能的設(shè)備,它會(huì)返回一個(gè)唯一的device ID,
以下幾個(gè)是stackoverflow上評(píng)論較多的幾個(gè),沒貼完,還有其他,綜合的,用到以上的部分方式:
地址:http://stackoverflow.com/questions/2785485/is-there-a-unique-android-device-id
有興趣的朋友可以再仔細(xì)看看
支持率比較高的(支持票數(shù)157):androidID --> 剔除2.2版本(API 8)中有問題的手機(jī),使用UUID替代
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 volatile 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; } }
根據(jù)版本進(jìn)行判斷的方式:Serial序列號(hào)-->UUID (支持?jǐn)?shù)31)
通過Serial 即可,在覆蓋率上,你已經(jīng)成功的獲得了98.4%的用戶,剩下的1.6%的用戶系統(tǒng)是在9 以下的。
通過AndroidID獲取,前面已經(jīng)說過,在8上,有些商家的手機(jī)會(huì)有一些bug,返回相同的AndroidID,如果Serial和AndroidID都不行
/** * 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 phone 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! // http://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 phone, 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 e) { // String needs to be initialized serial = "serial"; // some value } // Thanks @Joe! // http://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(); }
不用READ_PHONE_STATE權(quán)限直接獲取ROM信息的方式:(支持率較低 16)
String m_szDevIDShort = "35" + //we make this look like a valid IMEI Build.BOARD.length()%10+ Build.BRAND.length()%10 + Build.CPU_ABI.length()%10 + Build.DEVICE.length()%10 + Build.DISPLAY.length()%10 + Build.HOST.length()%10 + Build.ID.length()%10 + Build.MANUFACTURER.length()%10 + Build.MODEL.length()%10 + Build.PRODUCT.length()%10 + Build.TAGS.length()%10 + Build.TYPE.length()%10 + Build.USER.length()%10 ; //13 digits
最后貼上自己在項(xiàng)目中用的:
public static String getDeviceId(Context context) { String deviceId = ""; if (deviceId != null && !"".equals(deviceId)) { return deviceId; } if (deviceId == null || "".equals(deviceId)) { try { deviceId = getLocalMac(context).replace(":", ""); } catch (Exception e) { e.printStackTrace(); } } if (deviceId == null || "".equals(deviceId)) { try { deviceId = getAndroidId(context); } catch (Exception e) { e.printStackTrace(); } } if (deviceId == null || "".equals(deviceId)) { if (deviceId == null || "".equals(deviceId)) { UUID uuid = UUID.randomUUID(); deviceId = uuid.toString().replace("-", ""); writeDeviceID(deviceId); } } return deviceId; }
// IMEI碼 private static String getIMIEStatus(Context context) { TelephonyManager tm = (TelephonyManager) context .getSystemService(Context.TELEPHONY_SERVICE); String deviceId = tm.getDeviceId(); return deviceId; } // Mac地址 private static String getLocalMac(Context context) { WifiManager wifi = (WifiManager) context .getSystemService(Context.WIFI_SERVICE); WifiInfo info = wifi.getConnectionInfo(); return info.getMacAddress(); } // Android Id private static String getAndroidId(Context context) { String androidId = Settings.Secure.getString( context.getContentResolver(), Settings.Secure.ANDROID_ID); return androidId; } public static void saveDeviceID(String str) { try { FileOutputStream fos = new FileOutputStream(file); Writer out = new OutputStreamWriter(fos, "UTF-8"); out.write(str); out.close(); } catch (IOException e) { e.printStackTrace(); } } public static String readDeviceID() { StringBuffer buffer = new StringBuffer(); try { FileInputStream fis = new FileInputStream(file); InputStreamReader isr = new InputStreamReader(fis, "UTF-8"); Reader in = new BufferedReader(isr); int i; while ((i = in.read()) > -1) { buffer.append((char) i); } in.close(); return buffer.toString(); } catch (IOException e) { e.printStackTrace(); return null; } }
對(duì)于獲取設(shè)備唯一ID并沒有絕對(duì)的方案,這一點(diǎn)在android的官方博客中也提到了,不過以上幾種方案,應(yīng)該可以滿足平時(shí)的需求,大家可以選擇其中自己認(rèn)為比較好的,用于自己的項(xiàng)目中。
以上就是本文的全部?jī)?nèi)容,希望對(duì)大家的學(xué)習(xí)有所幫助,也希望大家多多支持腳本之家。
相關(guān)文章
Android實(shí)戰(zhàn)教程第七篇之如何在內(nèi)存中存儲(chǔ)用戶名和密碼
這篇文章主要為大家詳細(xì)介紹了Android如何實(shí)現(xiàn)在內(nèi)存中存儲(chǔ)用戶名和密碼的相關(guān)代碼,具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2016-11-11Android編程學(xué)習(xí)之異步加載圖片的方法
這篇文章主要介紹了Android編程學(xué)習(xí)之異步加載圖片的方法,以實(shí)例形式較為詳細(xì)的分析了Android異步加載圖片所涉及的頁面布局及功能實(shí)現(xiàn)技巧,具有一定參考借鑒價(jià)值,需要的朋友可以參考下2015-10-10獲取Android系統(tǒng)唯一識(shí)別碼的方法
這篇文章主要介紹了獲取Android系統(tǒng)唯一識(shí)別碼的方法,涉及通過編程獲取Android系統(tǒng)硬件設(shè)備標(biāo)識(shí)的相關(guān)技巧,具有一定參考借鑒價(jià)值,需要的朋友可以參考下2015-10-10Android使用Theme自定義Activity進(jìn)入退出動(dòng)畫的方法
這篇文章主要介紹了Android使用Theme自定義Activity進(jìn)入退出動(dòng)畫的方法,涉及Android的Activity屬性設(shè)置與資源操作技巧,需要的朋友可以參考下2016-07-07Android獲取手機(jī)本機(jī)號(hào)碼的實(shí)現(xiàn)方法
這篇文章主要介紹了Android獲取手機(jī)本機(jī)號(hào)碼的實(shí)現(xiàn)方法的相關(guān)資料,希望通過本文大家能夠?qū)崿F(xiàn)這樣的方法,需要的朋友可以參考下2017-10-10詳解Android中Fragment的兩種創(chuàng)建方式
本篇文章主要介紹了Android中Fragment的兩種創(chuàng)建方式,具有一定的參考價(jià)值,有興趣的可以了解一下。2016-12-12Android 實(shí)現(xiàn)仿網(wǎng)絡(luò)直播彈幕功能詳解及實(shí)例
這篇文章主要介紹了Android 實(shí)現(xiàn)仿網(wǎng)絡(luò)直播彈幕功能詳解的相關(guān)資料,并附實(shí)例代碼及實(shí)現(xiàn)效果圖,需要的朋友可以參考下2016-11-11Android自定義TextView仿微信朋友圈文字展開全文功能
這篇文章主要為大家詳細(xì)介紹了Android自定義TextView仿微信朋友圈文字展開全文功能,具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2018-06-06Android實(shí)現(xiàn)水波紋效果實(shí)例代碼
大家好,本篇文章主要講的是Android實(shí)現(xiàn)水波紋效果實(shí)例代碼,感興趣的同學(xué)趕快來看一看吧,對(duì)你有幫助的話記得收藏一下2022-02-02