Skip to main content

Wakey Wakey - Network Alarm Clock

I repurpose old Android mobile phones (from the KitKat/Lollipop era) to use as alarm clocks in my 3 young kids' rooms. After a while, it gets pretty tiresome syncing up the alarm clocks (eg. when the next day is a public holiday and you want to disable the alarm just for that day so that everyone can get a bit more sleep).

I thought it would be pretty cool if I could update all the alarm clocks remotely from a webapp. I couldn't find any alarm clock app that can be remotely controlled on the app store, so I decided to implement my own.

For the webapp, I repurposed another project of mine called Shopping Buddy. This turned out to be relatively easy, because it basically involved stripping away features like bookmarks and history, and trying not to break things along the way. It was done pretty quickly, and I called it Wakey Wakey

The production site can be found at:

The Github repository can be found at:


Now I needed an Android app that can talk to the backend, download the alarm schedule and basically function as an alarm clock.

For a humble alarm clock app, this turned out to be more difficult than I imagine. Unlike a normal app, an alarm clock needs to do a lot of platform-native stuff, including:
  • running periodically in the background to schedule alarms
  • activate the alarm, even if the application is not in the foreground, or the phone is asleep
  • setup everything again after a reboot etc.
I initially turned to Javascript-based app development frameworks such as Cordova, which will require platform-specific plugins to implement the above functions. But there was no single plugin that provides all the necessary functions, and the ones available seem to be old and buggy, which will require a lot of tweaking and debugging before they might even be fit-for-purpose. So given the options available, it seems most sensible to go fully native instead.

I downloaded Android Studio 4.0 and pulled in code from a few alarm clock apps from GitHub, including the one from ASOP KitKat. I wanted to target SDK level 19, because I wanted the app to work with Android versions as low as 4.0. It came together slowly. I had prior experience on Android development with Java, and it was every bit as laborious as I remembered, nothing like the brevity and levity one feels when developing with a higher level language like Javascript.

The UI is extremely plain and simple. The client will turn the volume up to maximum, so the alarms will ring even if the phone has been accidentally muted or airplane mode has been switched on (yeah, I can't remember how many times my kids have done that to me).

Once an alarm goes off, it will continue for 10 minutes, or until the alarm is remotely disabled on the webapp. The code is actually there to dismiss the alarm by touching the screen, but I have commented it out!

Replication happens in the background to a local database, so the alarm clock will function even if wifi is down (provided the changes have already been replicated to the local instance before the network went down).

The Android client APK can be downloaded at:

The Github repository can be found at:




Popular posts from this blog

Adding "Stereo Mixer" to Windows 7 with Conexant sound card

This procedure worked for my laptop (Thinkpad E530) with a Conexant 20671 sound card, but I suspect it will work for other sound cards in the Conexant family. I was playing with CamStudio to do a video capture of a Flash-based cartoon so that I can put it on the WDTV media player and play it on the big screen in the living room for my kids. The video capture worked brilliantly, but to do a sound capture, I needed to do some hacking. Apparently, there was this recording device called "Stereo Mixer" that was pretty standard in the Windows XP days. This allowed you to capture whatever was played to the speaker in all its digital glory. Then under pressure from various organizations on the dark side of the force, Microsoft and soundcard makers starting disabling this wonderful feature from Windows Vista onwards. So after much Googling around, I found out that for most sound cards, the hardware feature is still there, just not enabled on the software side. Unfortunately, to

Attiny85 timer programming using Timer1

This Arduino sketch uses Timer1 to drive the LED blinker: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 /* * Program ATTiny85 to blink LED connected to PB1 at 1s interval. * Assumes ATTiny85 is running at 1MHz internal clock speed. */ #include <avr/io.h> #include <avr/wdt.h> #include <avr/sleep.h> #include <avr/interrupt.h> bool timer1 = false , led = true ; // Interrupt service routine for timer1 ISR(TIMER1_COMPA_vect) { timer1 = true ; } void setup() { // Setup output pins pinMode( 1 , OUTPUT); digitalWrite( 1 , led); set_sleep_mode(SLEEP_MODE_IDLE); // Setup timer1 to interrupt every second TCCR1 = 0 ; // Stop timer TCNT1 = 0 ; // Zero timer GTCCR = _BV(PSR1); // Reset prescaler OCR1A = 243 ; // T = prescaler / 1MHz = 0.004096s; OCR1A = (1s/T) - 1 = 243 OCR1C = 243 ; // Set to same value to reset timer1 to

Hacking an analog clock to sync with NTP - Part 5

This is how it looks after I have put everything together. The Arduino sketch is available here . The 2 jumper wires soldered to the clock mechanism are connected to pins D0 and D1 on the ESP-12 (in any order). When the device first boots up, it presents an access point which can be connected to via the PC or smartphone. Once connected, the captive portal redirects the web browser to the configuration page:     A custom field has been added to the WiFi configuration page to enter the current clock time in HHMMSS format. Try to set the clock time to as close to the current time as possible using the radial dial at the back of the clock so the clock will have less work to do catching up. In the config page, the HTML5 Geolocation API is also used to obtain your current location (so if your web browser asks if you would like to share your location, answer "yes"). This is then passed to the Google Time Zone API to obtain the time and DST offset of your time z