Bug, Since the latest update, the R10 is randomly going into sleep mode even while actively being used.
Suggestion, do not send shot data onto simulator software if it is not complete..
Bug, Since the latest update, the R10 is randomly going into sleep mode even while actively being used.
Suggestion, do not send shot data onto simulator software if it is not complete..
Same thing with my unit. On the latest firmware, shots read great, I'm calibrated and out of nowhere, the R10 will start falling asleep multiple times in the course of a few minutes. Nothing in the…
Same here. Got this at least 10 times today and no Garmin Rob all your suggestions don't help. It's clearly a software bug with 4.20. Never had this issue prior to updating to 4.2.
Yes in the app it asks if I want to wake up the R10
Any updates to this? It's getting very annoying and disappointing.
I may be seeing this as well... 2 out of 4 times playing HTH the app crashed and closed. Both times when I tried to restart and sign-in it suggested that I could 'Resume' a round, but when I tapped Resume, it crashed again. Restarting the App required 2 Sign-Ins, and then Resumed round is not available.
Also, I got the weird 'Purple Blinking' light from the R10. I've never seen that before. Had to power off/on to get back into a normal Bluetooth connection mode and all I was doing was moving the unit from iPad to iPhone?
Any update to this issue?
If the developers reads this, I'm pretty sure it's related to bluetooth connection.
Yesterday it was impossible to get the R10 going. Constant white flashing after every shot.
Solved it by disabling bluetooth on the tablet, turned off the R10, started Garmin Golf, turned on bluetooth and then powered up the R10 unit.
At least I think it was in this order.
Unit worked fine after that for the whole session.
Same here. Brand new. 2 sessions outdoors on grass at the range. 20% of the balls hit were missed cause the f’n things asleep. Hyper annoying
Hello, please see thread: 4.20 Wakeup Issues - Approach R10 - Golf - Garmin Forums. A fix is on the horizon for this issue. The moment it is released I will update this thread.
I am locking this post to prevent multiple running threads on this issue.