The device ID is used by Traveler to uniquely identify the physical device in the traveler database. For Android, there are 3 different possibilities as to how the device ID is determined. The Traveler client will attempt to determine a unique id using these methods in order. Only if for some reason a unique id cannot be found will it proceed to the next method.
This is an api provided by the operating system that is described here:
This is an api provided by the operating system associated with phone and is described here:
3. Generate an ID using a random number in the form of Android__gen
This ID is saved in application local storage.
If the device id is ever lost or reset, then this device will appear to traveler to be a different device. This means:
- All settings will be set to default.
- The initial sync will take longer than normal as the server sets up the new device.
- Any block or deny access requests will no longer apply, because the server will consider this a different device.
The following table describes if the device id is retained or lost under the different combinations of ID attainment method and wipe/reset operations:
|Device ID method||Application Wipe/Application Uninstall||Device Wipe/Reset to Factory|
|Option 2:TelephonyManager.getDeviceId() ||retained||retained|
|Option 3:Random number ||lost||lost|