{"id":7226,"date":"2026-11-03T19:23:19","date_gmt":"2026-11-03T18:23:19","guid":{"rendered":"https:\/\/www.pschatzmann.ch\/home\/?p=7226"},"modified":"2026-11-03T19:23:19","modified_gmt":"2026-11-03T18:23:19","slug":"your-phone-as-a-time-server-for-arduino","status":"publish","type":"post","link":"https:\/\/www.pschatzmann.ch\/home\/2026\/11\/03\/your-phone-as-a-time-server-for-arduino\/","title":{"rendered":"Your Phone as a Time Server for Arduino"},"content":{"rendered":"

Every microcontroller project that logs data, schedules actions or shows a clock eventually needs to know the time. Getting it right is surprisingly hard: internal clocks drift, RTC modules need to be set, and NTP needs internet access, which you often don’t have in the field, in a workshop or on a battery-powered sensor.<\/p>\n

Yet the answer is probably in your pocket. A smartphone knows the time very precisely, from the network and from its satellite receiver. The idea behind this project is simple: let the phone share its time with your boards.<\/strong><\/p>\n

Three projects that work together<\/h2>\n

Android Time Services<\/strong> is an app that turns an Android phone into a small time server. It collects time from internet time servers, from the phone’s satellite receiver and from nearby Bluetooth devices, combines these sources into one reliable clock, and keeps going even when some sources disappear. It then shares that time in two ways: over Wi-Fi, using the standard Network Time Protocol (NTP), and over Bluetooth Low Energy, using the standard Current Time Service (CTS).<\/p>\n

TinyNTP<\/strong> is a small Arduino library for NTP. It lets a board get the time over Wi-Fi or Ethernet, from the phone or any other time server, and it can also act as a time server itself.<\/p>\n

TinyCTS<\/strong> is the Bluetooth counterpart. It lets a board get the time from a phone, a watch or another board over Bluetooth, with no network at all, and it can also serve the time to others.<\/p>\n

Together they give you a small, self-contained time network: the phone is the reference, and the boards pick up the time by whichever route suits them.<\/p>\n

Wi-Fi or Bluetooth?<\/h2>\n

NTP over Wi-Fi<\/strong> is the natural choice when your board is on Wi-Fi anyway or needs the best precision. The phone can even provide its own hotspot, so this works without any internet connection as long as the phone can see the sky.<\/p>\n

Bluetooth<\/strong> is the choice for battery-powered devices, places without a network, or simply “set the clock from my phone”. It uses little power, needs no setup, and the phone sends its time zone along, so the board shows the correct local time automatically.<\/p>\n

It works in both directions<\/h2>\n

The app is not only a server. Boards running TinyNTP or TinyCTS as a server, for example with a GPS module or a precise real-time clock attached, can feed their time back into the app as additional sources. Boards can also pass time along: one board can fetch the time over Wi-Fi and then share it over Bluetooth with others that have no network.<\/p>\n

Where things stand<\/h2>\n

The app is a working prototype, so far tested on one phone. The libraries run on popular boards such as the ESP32, the Raspberry Pi Pico W and Arduino’s Bluetooth-capable boards, as well as on Linux desktops. Feedback from other phones and boards is very welcome.<\/p>\n

Learn more<\/h2>\n