After reporting this to Garmin a year and a half ago, this feature is still broken and based on recent communication with Garmin Support I have no reason to believe it will ever be resolved.
At this point I feel like I'm entitled to a rant. I tried to go about resolving this issue the right way. I called Garmin Support twice. I've been in communication via email with multiple Garmin staff including the beta testing team and provided all information they've asked for. I've worked in software for nearly two decades including production support team lead roles so I'm confident that I'm providing them with good information.
Not only that, but there are numerous reports on this and other Garmin forums reporting that the AutoShot feature is not reliable on multiple devices including the flagship golf GPS S60. Yet, this critical feature that many golfers rely only seems to work if your club slams into the ground. Hit the ball off a tee with your driver? Flip a coin, sometimes it works, sometimes it doesn't. The most basic feature of a gps device, measuring the distance between two points, doesn't work because software architects at Garmin decided they would replace the fool proof manual shot measurement feature present on all commercial golf gps products with this fantastical feature that automatically records shot measurements by deducing golf shots from accelerometer data. Problem is, the idea is trash and should have been rejected at the Product Strategy level because it can't possibly be 100% reliable due to the nature of accelerometer data. How can you reliably differentiate a real golf shot from a practice shot or someone waving their arms around? It's an interesting question and apparently one that Garmin has yet to figure out.
A word of advice to Garmin software architects:
Do a better job of understanding your user's needs before gutting important features. I've been using Garmin for golf and automotive needs for a decade but the 5 Plus Titanium is probably the last Garmin product I buy as a result of your handling of this issue.
Thanks for listening. 
