Android devices use a daily request to make sure their time is set correctly. Without this, devices may experience their clocks slowly drifting, becoming less and less incorrect overtime. If this drift gets bad enough, it can even cause your device to start to fail to connect to the internet.

Android's default network time sync uses SNTP with a single time query approximately once a day to try to ensure it always has a recent time signal. Network latency effects are the biggest contributor to time inaccuracy with Android's SNTP implementation. Learn more about how Android systems handle network time detection.

ManageXR doesn't set the date and time on headsets - we only read the internal clock of a device (Android's default network time). Devices need to be connected to a network to communicate with the servers that automatically set the date and time. If devices cannot properly communicate with servers, they cannot update their time, and leave the devices' clocks to slowly drift. This problem is incredibly common and happens slowly over weeks and months. If you notice clock drift on your devices, it's important to correct it before it causes problems!

These are the most common causes of time drift, accompanied by troubleshooting steps:

While ManageXR can't alter a device's date and time, we do allow users to choose whether or not to manually set a time zone for Pico devices. As mentioned before, it's important to correct time drift as soon as you notice it. The time zone settings in ManageXR provide a potential method of correcting time drift for Pico devices.