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

Firmware Downgrades - feature request petition

OK, here we go again. Nearly every active thread at the moment complaining that something that worked earlier now doesn't work.
I've got my own battery issues that I cant be sure are hardware or software.

If you gave us the ability to install older firmwares we'd be able to a) confirm whether our issues are hardware or software b) maintain a working device whilst you fix it.

Also, what happened to releasing software as betas where people could try, feedback, and if necessery backout. There are a lot of helpful people on here who could actively assist in your developemtn and testing.

I know your response will be you want everyone on the same version as it makes support easier, but you've shown time and time again you aren't capable of fixing anything without breaking something else and people should have the right to use the firmware that works best for them.

It would also have saved me and you the time, hassle and cost of me sending my watch back to you for a fault that may be just a software issue.

If anyone else agrees with this request can you please add your comments to this thread.

0 chunkywizard over 8 years ago

I can only recall one instance where a firmware upgrade caused crashes for a lot of people. This was on the FR225 (V2.50 I think), when Bluetooth caused the watch to reset. In this instance they did offer a downgrade to an early firmware. If you want to see what happens when something truly goes wrong go and look at the thread and you will see what a wide-spread issue looks like!

All the other firmware upgrades I've seen may have caused a change in behaviour (which people don't like), but nothing that 'brick' a device. I am sure Garmin put lots of bug fixes in each new firmware and so to make it easier from a support perspective they want everyone to be on the latest firmware. Offering a downgrade opinion doesn't make sense in this context.

If people upgrade to the latest firmware and have an issue with something not working I suggest they phone Garmin support to help them fix the issue. Usually people get a resolution after reinstalling software, reset the device etc. Compare the amount of people on the 235 latest firmware who have an issue (as opposed to a feature tweak they don't like) vs. the FR225 V2.50 and you will see its a very small percentage.

Just my 2p worth

CW

0 Former Member over 8 years ago

I can only recall one instance where a firmware upgrade caused crashes for a lot of people. This was on the FR225 (V2.50 I think), when Bluetooth caused the watch to reset. In this instance they did offer a downgrade to an early firmware. If you want to see what happens when something truly goes wrong go and look at the thread and you will see what a wide-spread issue looks like!

All the other firmware upgrades I've seen may have caused a change in behaviour (which people don't like), but nothing that 'brick' a device. I am sure Garmin put lots of bug fixes in each new firmware and so to make it easier from a support perspective they want everyone to be on the latest firmware. Offering a downgrade opinion doesn't make sense in this context.

If people upgrade to the latest firmware and have an issue with something not working I suggest they phone Garmin support to help them fix the issue. Usually people get a resolution after reinstalling software, reset the device etc. Compare the amount of people on the 235 latest firmware who have an issue (as opposed to a feature tweak they don't like) vs. the FR225 V2.50 and you will see its a very small percentage.

Just my 2p worth

CW

I couldn't disagree with you more. Why would a certain percentage dictate when someone could downgrade firmware if available? I was an initial release purchaser who had ZERO issues with the first firmware version. EVERY update since has caused more problems. I've gone down the path of calling support, reinstalling software and doing resets. Nothing has helped. My 235 went from great to an item listed on Craigslist. It's great that people are having no issues and are happy with their 235. Where's the harm in allowing those dissatisfied with their current FW to downgrade and be happy too? Making it easier for support is a weak argument when I could use a FW version that would prevent me from contacting support in the first place.

0 timgrose over 8 years ago

Unfortunate that the 235 is not working for you but it certainly would be unusual for a user to be perfectly happy with a release several versions ago and not with any one since.

Also it would be pretty stupid for Garmin to effectively say the current firmware version might be "bad" (unless it really was) by easily allowing you to go backwards.
I note you don't tend to get downgrade options with mobile phone apps which have similar updating mechanisms to Garmins.

As CW mentioned when a release has been shown to be "bad" then it gets pulled and a downgrade path is given. Same goes for beta software.

Anyway having now used 2 Garmin OHR devices, I have learnt that things work best for my purposes if I use a strap for actual activities and just use the OHR for some checking of HR at other times. I have not found that OHR worked better "in the past" however.

0 Former Member over 8 years ago

Unfortunate that the 235 is not working for you but it certainly would be unusual for a user to be perfectly happy with a release several versions ago and not with any one since.

Also it would be pretty stupid for Garmin to effectively say the current firmware version might be "bad" (unless it really was) by easily allowing you to go backwards.
I note you don't tend to get downgrade options with mobile phone apps which have similar updating mechanisms to Garmins.

As CW mentioned when a release has been shown to be "bad" then it gets pulled and a downgrade path is given. Same goes for beta software.

Anyway having now used 2 Garmin OHR devices, I have learnt that things work best for my purposes if I use a strap for actual activities and just use the OHR for some checking of HR at other times. I have not found that OHR worked better "in the past" however.

Your post kind of supports my argument. I'm not saying that that everyone is having the same problem after a FW release. This forum is filled with "the latest updated did this or that". Lets say for argument sake that I'm happy with 4.60 and we have the ability to downgrade. If I have an issue with the release of 4.70, I now have two options. 1. I can call support and see if the can solve my issue with 4.70. 2. I can downgrade to 4.60, the functioning FW update that was working for me. In either case, this doesn't place any burden on Garmin Support's ability to assist me. Currently, if support is unable to assist me with my 4.70 issue, I have to wait up to weeks for the release of 4.80 in the hopes it solves my problem. Others have suggested releasing updates similar to the beta updates of the past. I think that would solve many problems.