I used pulsar detection techniques to turn a phone into a watch timegrapher

If you know the structure of the “tick”, you can apply the technique of a correlation receiver. It can dig up signals below the noise floor and is used in GPS reception.

Did you consider trying the iPhone accelerometer? Perhaps lay the phone face down on the table and then lay the watch on the back? Wondering if this would have higher or lower SNR.

10 seconds per day is a little over 115 ppm. What is the frequency error of the reference clock that ultimately drives the ADC connected to the microphone?

Awesome writeup! I wonder whether with a real contact mic (Korg offers one for about 20 bucks) you could get much better results. Due to no 3,5mm on phones anymore it might be easier to use a sound-enabled SBC though.

How does it compare to other apps ("watch accuracy meter" for example) on android?

It uses the built-in one. But as discussed in the article they ran into the problem where even when you try to force using the internal mic, iOS will silently switch to the mic on a pair of AirPods if there's a pair connected.

This is designed to be used by the internal device microphone. And this is in my write up, but if you have Airpods in all the time (like me), it will try to use that microphone and it will not work, and it will cause you to lose a day in frustration if you are working on something similar

This is the way. I got one as well to validate my results. Cost is the difference. If you're okay with close-enough and saving $145, I think the apps fit in a nice place.

I will say, this flow is not the primary concept for the app. My intended design, and what it's been for 2+ years, is a tool that provides structured flows for inputting the time on your device and comparing it to atomic time (provided in my app). If you stagger these measurements over 6 or so hours for a day or two, you get a very precise reading and I still recommend this approach as being better.

Piezo mics are pretty cheap, and if wired up to the microphone input of a computer or phone you could probably get better accuracy as well if you used the same signal processing techniques.

Seems some people have done this already with a PC app: https://timeandtidewatches.com/how-to-make-your-own-timegrap...

I used flutter so maybe some day!

It's in open beta testing on the Play Store for Android. You can also find low cost external mics for your devices that work well.

Watches are precise machinery that require maintenance and well known watch brands take great pride in the longevity of their pieces, meaning they provide support for the lifetime of the watch (you will pay for this though). Typically, every 5-10 years you send them in for a service. Overtime, the little pieces and minuscule drops of lubricant wear and age and need replaced. Visibility into these metrics can help you keep an eye out for problems.

Higher end watches also get external certifications that reflect different precision standards. Some examples: METAS, COSC, or Rolex Superlative Chronometer if you are Rolex and need to be special. They have different specs, Superlative Chronometer is +/-2 sec per day. If it's out of spec and you're under warranty, you may be entitled to a free adjustment by a service center. Otherwise, overtime, as the performance degrades, it's a signal you may need a service.

There's also the risk of magnetization. If the delicate machinery becomes magnetized, you'll see BIG swings, like +/- minutes per day. Demagnitization is something any watchmaker can do quickly. (There is inherently some risk posed by the phone itself having a lot of magnets, but modern watches are typically built to resist magnetization to varying degrees -- look at the Rolex Milgauss as an example of best-effort magnet resistance)

Watches will also perform variably depending on position. If you know your watch is -4sec/day on your wrist, but +6sec/day face down, you can effectively manage it's accuracy by placing it face down over night and never have to unscrew the crown but keep a true time. This is a very common use case.

Hope that covers the general cases. This app avoids a lot of even deeper complexity, like beat error and amplitude which are deeper metrics describing the movements performance and guide watchmakers to know which screws to adjust which way.

Old mechanical watches and clocks had an adjustment with which you could change slightly the oscillation frequency of the balance wheel (usually by changing the tension of the balance spring).

You used a device like that described in the parent article to measure the deviation from the correct frequency and you adjusted the frequency with a fine screwdriver or a similar tool, until measuring the desired nominal frequency.

It tells you for how long the time displayed by the watch is valid. If a watch loses ten seconds per day, in a month it will be about five minutes off.

The objective is to minimize this number as much as possible. The open source sensor watch has a temperature sensor and software which turns it into a temperature compensated quartz watch. Mine loses time every year instead of every day or every month.

It is actually pretty useful if you own a few mechanical watches. Daily rate tells you how annoying the drift will be, beat error can hint that regulation or service is due, and measuring in different positions gives you a decent sanity check on movement health. Even if you never open the watch yourself, it is a much better baseline before taking it to a watchmaker.