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

Rolling back from FW 4.2 to 4.1

Former Member over 9 years ago

after update from 4.1 to 4.2 HR during running outdoor workout goes huts
i.e. it is not working during first 4 minutes of run and says after that i can't beat 140BPM anyhow :)
it has started right after update to 4.2 and garmin support approach by now is even worse than xiaomi (case is just opened for 2 days with no contacts)

so, my guess to rollback to working 4.1 but here comes garmin update approach: only the new :)

could anyone help me with that?

0 meccup over 9 years ago

I've got no idea why you are getting this, but my watch has become awesome after 4.2 update... Try to hard reset maybe?

0 Former Member over 9 years ago

I've got no idea why you are getting this, but my watch has become awesome after 4.2 update... Try to hard reset maybe?

did that couple of days ago
it was a messy day since all my watches in auto time sync mode went crazy
:)

it is still not even a question of glitchy 4.20 but i can't guess why there is no procedure of making previous release available for simple installation...
now enjoying staff like in attach

0 FlipStone over 9 years ago

did that couple of days ago
it was a messy day since all my watches in auto time sync mode went crazy
:)

it is still not even a question of glitchy 4.20 but i can't guess why there is no procedure of making previous release available for simple installation...
now enjoying staff like in attach

Same issue here, but afaik you can only roll back beta firmwares and not final versions. So stuck until garmin fixes this...

But when I run, and do a walking warmup with the run-activity ready and hr already on, it doesn't happen too often. So I guess it's some 'trying to determine and not registering yet'-thing. Although, 3-4 minutes for that (as it shown on normal walks/hikes is a bit much). Hope they fix this soon.

Cadence lock seems better for me, still present but less often and not 50+ % of the runs anymore...

0 Former Member over 9 years ago

Same issue here, but afaik you can only roll back beta firmwares and not final versions. So stuck until garmin fixes this...

But when I run, and do a walking warmup with the run-activity ready and hr already on, it doesn't happen too often. So I guess it's some 'trying to determine and not registering yet'-thing. Although, 3-4 minutes for that (as it shown on normal walks/hikes is a bit much). Hope they fix this soon.

Cadence lock seems better for me, still present but less often and not 50+ % of the runs anymore...

got garmin support contacted me via email
they advised to go to local disty, who does not have any of 235s shipped in :)

though, there is a small hack
i found 4.1 image and there is some downgrade plan scheduled

for me, it is absolute non sense when you should try to find PREVIOUS version while current build is glitchy
and the fact that garmin supports PLATFORM device (i.e. software enabled features) via service centres in the 21st century

--------------
and trick has failed....
so, left to garmin's mercy to fix poor FW

0 Former Member over 9 years ago

Same issue here, but afaik you can only roll back beta firmwares and not final versions. So stuck until garmin fixes this...

But when I run, and do a walking warmup with the run-activity ready and hr already on, it doesn't happen too often. So I guess it's some 'trying to determine and not registering yet'-thing. Although, 3-4 minutes for that (as it shown on normal walks/hikes is a bit much). Hope they fix this soon.

Cadence lock seems better for me, still present but less often and not 50+ % of the runs anymore...

tried your advise
works fine
now, there are just 2 minor things left:
1. to fix 30BPM heart rate before i am actually dead
2. wait until garmin support will do thier job
my bet first will be easier :)