A little less friction

Shot Timer
Troubleshooting

Check the basics. Get back to practice.

Your browser check

Capability checks do not activate the microphone. Access is requested only when you press Enable microphone.

  • Enable JavaScript to inspect browser capabilities.
0

Microphone permission denied

In Safari, inspect this website’s settings for microphone access. In Chrome or Edge, open the site controls beside the address and review Microphone permission. The wording depends on the browser and operating system. If access is blocked at OS level, also check the browser’s microphone permission in system settings.

Reopen the site over HTTPS and tap Start or Enable microphone again. Installed iPhone Home Screen apps may ask for permission again after a cold launch; your saved results are independent of that grant. This app cannot change browser or OS permissions for you.

No microphone signal or another app is using it

Close other apps using the microphone, reconnect an external device if needed, and try the diagnostic button. A connected headset may select an unexpected input. A moving meter confirms signal, not correct event detection. If the check receives no frames, try a current browser and reload.

Missed shots

A threshold can be too high for quieter transients. Calibrate for the current environment and test a more sensitive setting. Avoid covering the microphone. Events within the initial 0.63-second cue guard or 0.12-second event separation can be missed or merged. Phone processing can also change the signal; no universal setting guarantees detection.

False triggers and nearby shooters

Echoes, wind, conversation and nearby shots can all create sharp sounds. Choose a less sensitive setting, recalibrate when conditions change, and use Ignore false event in the review table. If noise overlaps your samples, calibration may be unreliable. Use Par Timer when acoustic separation is not useful.

No start beep or delayed audio

Audio must be enabled from your tap. Test the beep after adjusting media volume and output route. Bluetooth and speaker buffering can delay what you hear relative to the internal audio clock. Browser scheduling and input latency remain uncertain; displayed hundredths are not certified accuracy.

Screen locks, background tabs and wake lock

Screen wake lock requires a secure origin and browser support. Power-saving settings can prevent or revoke it. Screen awake is shown only after the browser grants the lock. When the app is hidden, audio is suspended, the microphone ends or a granted wake lock is released, timing is stopped and marked interrupted. Resume practice with a new session and keep the app visible.

Offline or installation problems

Open the tools online over HTTPS and wait for Offline tools ready in Install App. A browser can clear cached pages and local data. If a route cannot reopen offline, reconnect and reload to finish setup. On iPhone, use Safari’s Share → Add to Home Screen; on Android, look for Install app in the browser menu.

Reset settings or erase local data

Advanced settings on the Shot Timer include Reset settings, which keeps history and calibration profiles. History can delete individual sessions or clear all results. Privacy controls can erase results, profiles, presets and theme together. Browser site-storage settings can also remove the offline cache.

On this device

No saved sessions yet.

Your timer. One tap away.

On iPhone or iPad: open in Safari, tap Share, then Add to Home Screen. On Android: use your browser’s Install app or Add to Home screen menu.

Open the tools online once before going offline. Microphone permissions may be requested again after launch. Keep the app visible while timing.

Offline setup requires a secure connection.