HUMODDA well, both the menu method and the button combo method are described by Garmin as resetting to factory defaults. (As well as the “hold back while powering on” method described in the link you posted.) (Although the menu method doesn’t delete screenshots, so it’s def not a full reset — not sure about the button combo method, although I wouldn’t shocked if it also didn’t delete screenshots.)
I only suggested the menu method because it’s a lot easier to do. But if the button combo method resets more things, then go for it.
I always assumed that the button combo method was a last resort for when you couldn’t even turn on the watch. E.g. I’ve had to use it when a 235 was rebooting endlessly and the normal UI was inaccessible. I also thought that earlier Garmin watches didn’t have a menu option for this, which is why the old button combo method is still mentioned so often today — because there was a time when it was the only way to “fully” reset your watch.
I’d be curious to hear about what additional things the button combo is known to reset over the menu option tho....
Next try on this beta: what happened to this fix? Never appeared in official or beta versions again... [h=4]Changes made from version 11.57 to 12.01:[/h]
Fixed an issue that could cause the number of floors climbed to be inaccurate.
Have tried the GPS 2.50 just to have a quick peek if Galileo performance would improve. Well, it's more the opposite, even with up to date EPO file the GPS fix took half a minute or longer, reproducibly. I changed back to 2.30 and the fix again is established within seconds. Seems to require some further finetuning though.
GPS 2.50 is now available through "normal" update channels, it's in my synch queue but I have auto updates turend off. Waiting for more reviews until installing it...
GPS 2.50 is now available through "normal" update channels, it's in my synch queue but I have auto updates turend off. Waiting for more reviews until installing it...
As it became now "official" I gave it another try, this time with a full reset of the watch afterwards and fresh install.
And what a difference!! Galileo is now simply AMAZING!! Where I had erratic and wobbling tracks, they now are straight as a gunshot and pretty accurate. This new 2.50 version really improved Galileo a great lot. The GLONASS performance looks unchanged to me, could not spot any major differences with 2.30
but it doesn't change anything, I still have the problem with the sensor like here
My recommendation to you would be to get in touch with Garmin support and claim a hardware fault. Seriously, your error does not look like a software bug to me, this seems more like a hardware issue. Especially if you tried the secondary master reset. This actually would have reset all the software on your watch to the initial state, and if that does not help, your issue is probably more serious and would require a replacement.
My recommendation to you would be to get in touch with Garmin support and claim a hardware fault. Seriously, your error does not look like a software bug to me, this seems more like a hardware issue. Especially if you tried the secondary master reset. This actually would have reset all the software on your watch to the initial state, and if that does not help, your issue is probably more serious and would require a replacement.
Thanks for your feedback
It's very strange, because the problem appeared just after the update to version 12.10. And I'm not the only one impacted (see this topic)
I have already sent back my first 935 for a problem with a difference in altitude. All right, a hardware fault may be present.. But i don't want to send this watch back, again, which was working until this firmware update. Especially since I waited almost two months before receiving the new watch.
