This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

R10 not picking up any shots.

R10 5 days ago everything was fine now everything is good green light flashing hit the shot light goes white. Hit power button it goes flashing green same results hit the shot goes white nothing recorded. Same place same setup can’t get it to work chat says must be above the level of the mat it’s been that work all along. Anybody else seen this?

Top Replies

All Replies

0 nbargolf over 3 years ago

Found the problem with help of Garmin support chat thanks Josh. I had to delete reinstall the app and go through the setup again. Don't know why this happened but it fixed the problem.

0 Nosauce over 1 year ago in reply to nbargolf

Thanks so much for this post. Reloading the garmin golf app has fixed my issue too. My R10 was connecting with my phone and working exactly as it should with leds BUT it would not pick up any shots at all. All good now after reloading the app. Thanks again

0 MoreDuh over 1 year ago in reply to Nosauce

Just deleted and reinstalled and all is good again!

0 Garmin-Cody over 1 year ago

If you are experiencing this issue, please try following the steps outlined below:

On the Garmin golf app: Select Menu> Garmin Devices> Press and hold the R10> Remove
On the bluetooth settings on your phone: Settings> Bluetooth> Select the Gear next to the R10> Unpair
Next please uninstall/delete the Garmin Golf app off of your phone.
Clear the Play Store Cache: Phone Settings> Apps> Google Play Store> Storage> Clear Cache
Turn off your phone, wait 10 seconds, Power it back on
Reinstall the Garmin golf app
Reset the R10 by pressing and holding the button for 30 seconds
Power off the R10 then put it into manual pairing mode by pressing and holding the button until you see a solid blue light
Re-pair your phone and R10 through the Garmin Golf app

0 Martin_Po over 1 year ago

One big THANK YOU for this. I was getting desperate because of this bug. Obviously there had to be some update problem recently. No other explanation for so many people having same issue at the same time.