Skip to content
  • There are no suggestions because the search field is empty.

How to Configure a Custom NTP Server on a RealWear Device

This article describes how to manually configure a custom NTP server on a RealWear device using ADB (Android Debug Bridge).

By default, RealWear devices use standard public NTP (Network Time Protocol) servers to synchronise the device time. In enterprise environments where devices operate on isolated networks, behind strict firewalls, or in air-gapped deployments without internet access, RealWear devices can be configured to point to an internal NTP server hosted within the customer's network.

Note: Cloud-managed NTP configuration via the Ari Business Cloud (RealWear Cloud) is in development and is targeted for a future release. Until then, manual ADB-based configuration is the supported method.

Prerequisites

Before configuring a custom NTP server, ensure the following:

  • A Windows or Mac computer with ADB installed
  • A USB cable to connect the RealWear device to the computer
  • The IP address or hostname of the internal NTP server (e.g. time.company.local or 10.0.0.1)
  • The RealWear device's ADB debugging mode enabled
  • Network connectivity from the RealWear device to the target NTP server (the device must be able to reach the NTP server over the network)

Configuration Steps

Step 1: Connect the Device to Your Computer

  1. Connect the RealWear device to your computer using the supplied USB cable.
  2. Open a terminal or command prompt on your computer.
  3. Confirm the device is detected by running:
adb devices

The device should appear in the list as device. If it shows unauthorized, accept the USB debugging prompt on the headset display.

Step 2: Set the Custom NTP Server

Run the following ADB command to set the NTP server address:

adb shell settings put global ntp_server <NTP_SERVER_ADDRESS>

Replace <NTP_SERVER_ADDRESS> with your internal NTP server's IP address or hostname.

Example:

adb shell settings put global ntp_server time.company.local

or

adb shell settings put global ntp_server 10.0.0.1

Step 3: Verify the Configuration

To confirm the NTP server has been set correctly, run:

adb shell settings get global ntp_server

The output should display the NTP server address you configured.

Step 4: Reboot the Device

Reboot the RealWear device for the changes to take full effect:

adb reboot

Once the device has restarted and is connected to the network, it will use the configured NTP server for time synchronisation.

Reverting to the Default NTP Server

If you need to revert the device back to the default NTP configuration, run:

adb shell settings delete global ntp_server

Then reboot the device.

Troubleshooting

Device time is not syncing after configuration

  • Verify that the device can reach the NTP server. Test connectivity by pinging the NTP server from another device on the same network.
  • Ensure UDP port 123 (the standard NTP port) is not blocked by firewall rules between the RealWear device and the NTP server.
  • Confirm the NTP server is operational and serving time requests.

Time drifts over time even after configuration

  • This can occur if the device intermittently loses connectivity to the NTP server. Ensure the NTP server is highly available and reachable from the device's network at all times.

ADB does not detect the device

  • Ensure USB debugging is enabled on the device.
  • Try a different USB cable or USB port.
  • Refer to the RealWear Explorer setup guide.

Related Articles

Need Further Help?

For further assistance, contact RealWear Support at support@realwear.com.