Unbelievable worst cycling purchase I have ever made

NeilJonesOnline and steve_s_t we do read the forums and post where we can to offer help. There are a number of threads related to issues posted here that I have posted in and the shutdown issues has its own forum sticky topic where we have asked forum users to post data. If you have specific issues that you feel are not being addressed please reach out to me directly via PM.

Hi Sean (@shawn-garmin), thanks for chipping in on this. I know that you have responded on a good few threads, it just seems to me (rightly or wrong) that there are still a lot that drift on without any sign of comment or solution. I wasn't having a pop at you though, your input and help is much appreciated. Also I accept that I may have missed key, "official" comments on some of the longer threads, but sometimes it just feels like an official update on bigger issues would appease a lot of the grumpiness in some threads. For the record, whilst I do get frustrated with some of the glitches (my Edge 820 Explore corrupted and then deleted the .fit file for a 130 mile bike ride at the end of May - that burned a bit), overall I'm happy with my experiences on all of the Garmins I've used, and try to remain positive in the forums.

Thanks again,

Steve

Appreciate the feedback @steve_s_t

NeilJonesOnline and steve_s_t we do read the forums and post where we can to offer help. There are a number of threads related to issues posted here that I have posted in and the shutdown issues has its own forum sticky topic where we have asked forum users to post data. If you have specific issues that you feel are not being addressed please reach out to me directly via PM.

Hi Shawn, the criticism was a general one, so please don't take it personally. There *are* good examples of Garmin engaging with their customers on here, but it's so inconsistent which is what makes it all the more frustrating. For example, there used to be very good engagement in the Fenix 5 forum. However, in the f5+ forum there's a thread nearly 200 posts long discussing serious apparent battery drain problems that many people are experiencing but not even an acknowledgement from Garmin that they're investigating - and we're now two betas on from when the thread started. People are now spending (wasting) a lot of their own time going through different settings on their watches and meticulously logging battery usage every hour of the day trying to get a common consensus on the cause, completely blind as to whether Garmin have already identified it and are working on a fix, or aren't even addressing it as an issue. There's also the amount of times an admin posts early in a discussion that "This is something we are investigating/working on" and that they will keep everyone updated, then either nothing else ever gets posted or we just get a vague "we're still working on it" (which I'll admit is better than nothing).

I know sometimes customers have unrealistic expectations, but I still think a bit more acknowledgement from Garmin would go a long way in improving the perception of customer support that comes across in many of these forums.

Neil

I don't know what you could possibly be doing wrong but there is hope since I have had no problems with my 1030. I've only had it for three months and about 24 rides and it has been flawless connecting to my Iphone, Varia, and speed,cadence sensors. Live tracking works too. My thinking is that many of the issues are from the phone side. The remote has been a problem for many and I have just bought one and hope my luck continues.

I have used my Edge 1030 for six months now and I have ridden approximately 6000 km with it. I have had one shutdown while riding. Sometimes the normal shutdown fails and corrupts a fit file. But mostly the device functions very well. I have al large screen, lots of battery time, I can program my own datafields and navigation works fine.
Stava segments work fine as well as the bluetooth connection with my Samsung S7. I use a Garmin Varia radar and a set of lights and of course cadence, speed and HR-sensors,
My only concern now is dat I see the beginning of a blue halo just as on my previous Edge 820.

I have been using the 1030 for a year now and my experience is not nearly as bad as the poster suggest. Overall it works just fine. And I used it a lot, for navigation, training. etc/ I had the halo issue and Garmin replaced the hardware. My Edge Remote is not reliable but kind of work (annoying but not a big deal). Overall it works. And the latest firmware updates brough lots of features and improvements. It is not all bad for sure.

Had mine 3 weeks and no issues at all, far better than the 510. With any firmware on anything, they fix something and causes problems somewhere else.

Anyone moaning they are having issues and is horrible, then stop moaning and dont use beta firmware, this is your issue.

Beta firmware for anything, when its offered using it is always at your own risk and will have issues.

The problem is that virtually all the firmware/software that Garmin put out is of beta quality, regardless of whether they actually call it a beta or not. I spent almost 30 years writing software, and we would never have dreamed of releasing the sort of bug-riddled stuff that Garmin regularly come out with.