How to Adjust Beat Error on Miyota 8215 Movement w/ Tweezers & an Android App

I had already adjusted the rate of the watch but I had heard moving the mobile stud carrier as a novice was a stupid idea so I decided to go for it. I was able to bring down a beat error of .8-1.2ms to .3-.6ms. With that it required readjusting the rate to get the watch to run within +/-4 sec/day which I was happy with. The app I used is called Watch Accuracy Meter which is a free Android app which uses you phones mic as a Timegrapher. Even if you don't want to play around with different studs on the watch movement it's very fun to to see how accurate you watch is. Hope you enjoy!

[@lohikarhu734]

I've very successfully used this app with my seiko V, and was able to regulate it in several positions, then used the app to set the rate at different states of winding, and get maybe better than 1 minute per week, which is rather close to chronometer performance, and can get it to better than 5 seconds per day if i keep the winding up...i did the rate adjustment at low winding, a bit minus, and a few seconds fast at full winding, so that, in daily 'real world' use, it's pretty darned fine.
The app worked really well, and needed only a relatively quiet room.

[@nathanfrank9838]

That app that you used really helped!

[@Hodapp]

Glad to hear it. I actually bought a little grey box thing that you can hook to a phone or computer to make it even more accurate plus doesn’t require holding the watch to the phone in the right position and allows for testing in multiple positions but as a quick run and gun check it is awesome. I have a Weishi Timegrapher at work and I’ve checked it against both the phones mic and the $10 Chinese amplifier box thing and both are pretty much dead on or within a reasonable margin of error that the number is something you can trust. Plus free app without having ads which is a rarity nowadays.

[@nathanfrank9838]

That's definitely good information to have. I just got into watches and my second watch was an oris xxl. Knew it was running really slow but had no idea. Saw your video and took it from -240 s/day to 0 s/day. Beat error of 2.7ms to 0.6ms.