As we can find android unique id usin native code like -
import android.provider.Settings.Secure;
private String android_id = Secure.getString(getContext().getContentResolver(),
Secure.ANDROID_ID);
But please suggest me is their any way to do same thing using phonegap?
http://docs.phonegap.com/en/1.0.0/phonegap_device_device.md.html#device.uuid
Actually, that's the default behavior when you call device.uuid , at least on Phonegap 3.5.0. You can see that if you check the source code of org.apache.cordova.device.Device
public class Device extends CordovaPlugin {
...
/**
* Get the device's Universally Unique Identifier (UUID).
*
* #return
*/
public String getUuid() {
String uuid = Settings.Secure.getString(this.cordova.getActivity().getContentResolver(), android.provider.Settings.Secure.ANDROID_ID);
return uuid;
}
...
}
Related
I have tried to these methods such as IMEI,MEID,mac address,android_id, but all not OK.
How to get unique device numer in Android?
There are several Unique Identifiers available for Android devices
IMEI
TelephonyManager TelephonyMgr = (TelephonyManager)getSystemService(TELEPHONY_SERVICE);
String imei = TelephonyMgr.getDeviceId();
permission
android.permission.READ_PHONE_STATE
WLAN MAC Address
WifiManager wifi = (WifiManager)getSystemService(Context.WIFI_SERVICE);
String wanMAC = wifi .getConnectionInfo().getMacAddress();
permission
android.permission.ACCESS_WIFI_STATE
Bluetooth MAC Address
BluetoothAdapter bluetoothAdapter =BluetoothAdapter.getDefaultAdapter();
String bluetoothMAC = bluetoothAdapter .getAddress();
permission
android.permission.BLUETOOTH
Android ID
String androidID = Secure.getString(getContentResolver(), Secure.ANDROID_ID);
As the requirement for most of the applications is to identify a particular installation and not a physical device, a good solution to get the unique id for a user if to use UUID class. The following solution has been presented by Reto Meier from Google in a Google I/O presentation :
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;
}
UUID.randomUUID() method generates an unique identifier for a specific installation. You have just to store that value and your user will be identified at the next launch of your application. You can also try to associate this solution with Android Backup service to keep the information available to the user even if he installs your application on the other device.
You can explore more at https://medium.com/#ssaurel/how-to-retrieve-an-unique-id-to-identify-android-devices-6f99fd5369eb
In Android 10 you can't have access to non resettable device ids, like IMEI ,MEID etc.
So I think your best chance is creating a UUID. You can do that using the code below and saving this UUID into database or preference file.
String uniqueID = UUID.randomUUID().toString();
As a random number, everytime you call this method it'll return a different code, and I think is not you are looking for.
To get a "unique ID" from UUID, the best choise is the code below.It will work fine, but the documentation ask to avoid using Android_ID too.
String androidId = Settings.Secure.getString(context.getContentResolver(),
Settings.Secure.ANDROID_ID);
UUID androidId_UUID = UUID
.nameUUIDFromBytes(androidId.getBytes("utf8"));
This code will give you a almost unique code because if the user do a factory reset, this number would be changed.
I'm looking for another way to get a unique ID but, until now, I couldn't find.
Here ar some Android Developers documentation that should be usefull.
Good pratices to define a unique ID
https://developer.android.com/training/articles/user-data-ids
How to define a unique Id based in you use case:
https://developer.android.com/training/articles/user-data-ids#common-use-cases
I hope this could help someone.
Below code is I used in my project
To get Unique Android Id
static String androidID = Settings.Secure.getString(MyApplication.getContext().getContentResolver(), Settings.Secure.ANDROID_ID);
I used this as a global so i can use anywhere in my project
To retrieve the unique ID associated to your device, you can use the following code :
import android.telephony.TelephonyManager;
import android.content.Context;
// ...
TelephonyManager telephonyManager;
telephonyManager = (TelephonyManager) getSystemService(Context.
TELEPHONY_SERVICE);
/*
* getDeviceId() returns the unique device ID.
* For example,the IMEI for GSM and the MEID or ESN for CDMA phones.
*/
String deviceId = telephonyManager.getDeviceId();
/*
* getSubscriberId() returns the unique subscriber ID,
* For example, the IMSI for a GSM phone.
*/
String subscriberId = telephonyManager.getSubscriberId();
Secure Android ID
String androidId = Settings.Secure.getString(getContentResolver(),
Settings.Secure.ANDROID_ID);
I want to create a unique ID for my android app so that my server can identify from which device the request has come and send messages to the app accordingly. I read that ANDROID_ID is not safe to use as a unique identifier as it can be compromised on a rooted device. And also some manufacturer don't even provide it.
Is UUID safe to use for my porpose ? Is it really the globally unique id for the app ? If yes, I am planning to store it using the keystore so that I can keep it until the app uninstalls. Is it the right approach. Please suggest.
Its actually safe to use UUID, this is a helper function I created to get the UUID myself,keep it in Helper.java , so you will call it :
Helper.getDeviceId(context);
also don forget the change String sharedPrefDbName variable to your sharef db name, also you can store the UUID in DB or local file incase app is uninstalled like you said.
//uuid
static String deviceId;
static String sharedPrefDbName = "MyAPPDB";
/**
* getDeviceId
* #param context
* #return String
*/
public static String getDeviceId(Context context){
//lets get device Id if not available, we create and save it
//means device Id is created once
//if the deviceId is not null, return it
if(deviceId != null){
return deviceId;
}//end
//shared preferences
SharedPreferences sharedPref = context.getSharedPreferences(sharedPrefDbName,context.MODE_PRIVATE);
//lets get the device Id
deviceId = sharedPref.getString("device_id",null);
//if the saved device Id is null, lets create it and save it
if(deviceId == null) {
//generate new device id
deviceId = generateUniqueID();
//Shared Preference editor
SharedPreferences.Editor sharedPrefEditor = sharedPref.edit();
//save the device id
sharedPrefEditor.putString("device_id",deviceId);
//commit it
sharedPrefEditor.commit();
}//end if device id was null
//return
return deviceId;
}//end get device Id
/**
* generateUniqueID - Generate Device Id
* #return
*/
public static String generateUniqueID() {
String id = UUID.randomUUID().toString();
return id;
}//end method
I have the following endpoint method:
public class PlayerEndpoint {
private static final String PLAYER_NAME = "player_name";
private static final String PLAYER_UUID = "player_uuid";
#ApiMethod(name = "register", httpMethod = ApiMethod.HttpMethod.POST, path="register")
public Player register(#Named(PLAYER_UUID) String uuid,
#Named(PLAYER_NAME) String playerName) {
log.info(String.format("Registering user uuid: %s name: %s", uuid, playerName));
...
}
}
When I call this from my Android client:
String uuid = "test_uuid";
String name = "test_name";
playerEndpoint.register(uuid, name).execute();
The backend logs:
Registering user uuid: test_name name: test_uuid
What is going on here?
I figured it out. Apparently Endpoints sorts your methods alphabetically.
Method parameters in the generated client library are in alphabetical order, regardless of the original order in the backend method. As a result, you should be careful when editing your methods, especially if there are several parameters of the same type. The compiler will not be able to catch parameter-ordering errors for you.
https://cloud.google.com/developers/articles/google-cloud-endpoints-for-android/
From this thread, it can say that Settings.Secure#ANDROID_ID can be null sometimes. On the other hand, the telephony-based ID can be null too in tablet devices and can be changed if user change the SIM card or flight mode.
Thinking of getting mac address, from this thread, sometimes the mac address cannot be got too.
Is there any solution that I can get Android unique ID that won't change in any condition?
Rendy, the code I used for that is the above (from emmby answer (with minimal modifications) of question Is there a unique Android device ID?):
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;
}
}
To use that in an Activity, do the following:
UUID identifier = new DeviceUuidFactory(this).getDeviceUuid();
The options you mentioned cover pretty much all the different scenarios to get a unique ID, there's also a unique ID value provided by the OS which has been proved was incorrectly implemented by some vendors and it returns the same value for all the devices of that specific vendor, so No, there's no 1 and only best way to do it, usually you need to combine and validate if one or another exist, for example in our project:
First we go for TelephonyManager and if it exist we take it from there
If not( as is the case in most tablets), then we go for MAC address
If not, then we use the Android unique ID provided in Settings.
Hope it helps!
Regards!
I'm getting the weirdest error. Im attempting to store a String to Azure Mobile Service Table and I'm getting this exception. ( Being thrown for a GCM ID I'm generating"
java.lang.NumberFormatException: Invalid int: "C3960965-ECE0-4533-B99D-84DB3881A50F"
public class User
{
private int id;
private String gcmChannel;
public User()
{
}
/**
* Getters and setters
*
*/
public String getRegistrationId() {
return gcmChannel;
}
public final void setRegistrationId(String registrationId) {
gcmChannel = registrationId;
}
There was a change in the tables created in Azure Mobile Services - the tables by default now have ids of type string (instead of integer, as before). If you change your type definition to the following:
public class User
{
private String id;
private String gcmChannel;
// ... rest the same
}
It should work fine. Notice that you'll also need the latest Azure Mobile Services SDK for Android (version 1.1.0) which has support for types with string ids - you can find that SDK at http://www.windowsazure.com/en-us/downloads/?sdk=mobile.
You can find the announcement of this change in the MSDN Forums, or more information about it in this blog post.