The Following 3 Users Say Thank You to biketool For This Useful Post: | ||
|
2013-02-25
, 20:11
|
|
Posts: 1,079 |
Thanked: 1,019 times |
Joined on Mar 2010
|
#2
|
The Following User Says Thank You to stickymick For This Useful Post: | ||
|
2013-02-26
, 00:18
|
Posts: 569 |
Thanked: 462 times |
Joined on Jul 2010
@ USA
|
#3
|
The Following User Says Thank You to rotoflex For This Useful Post: | ||
|
2013-02-26
, 00:55
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#4
|
|
2013-02-26
, 07:10
|
Posts: 1,424 |
Thanked: 2,622 times |
Joined on Jan 2011
@ Touring
|
#5
|
The Following User Says Thank You to biketool For This Useful Post: | ||
Tags |
android, mechaincal, regulation, watch |
|
and I have seen a similar app which runs on Apple phones.
It uses the microphone to listen for the ticking of a watch or mechanical clock and compares it to its own more accurate internal clock. By accurately timing the ticks it can tell if there is variation between positions and if the watch is running fast or slow even with a sample as short as a few seconds.
I imagine it would only take a few dozen lines of code to create such an app with graphing but I dont have the space on my netbook to install scratchbox. One issue is getting accurate time without background processes bogging the measurement of time or sound inputs.
It would be a cool app for watch regulating/repair geeks or before buying a used mechanical watch.