Related
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

looks like a new beta is out: 12.25

derek87
over 2 years ago

who's going to take one for the team? ;)

in all seriousness, i think i'm going to stick with 11.12. especially since the change log doesn't seem to mention the cadence issue with 12.23 being fixed.

i'll be curious what some of your brave and sacrificial members find out if you choose to try out the beta.

  • 0 over 2 years ago

    fw 12.25
    gps 2.37
    wi-fi 24.76
    ciq 4.1.4
    bmx 9.0.2
    whr 9.00.02
    ant/ble/bt 24.76
    tsc 1.12
    sensor hub 20.05
    ete 6.14.6.6
    lha 2.1.2.4

  • 0 over 2 years ago

    Launched Garmin Express on my PC, nothing to see there. Someone mentioned "Garmin Express Web", what's that ?

    EDIT - ok so after unplugging my watch I'm offered the 12.25 update, could be more explicit when you launch Garmin Express, but hey...

  • 0 over 2 years ago

    Ciao, 

    installato 12.25 stamattina. Ho provato subito le mappe e....ancora i problemi noti. Se punto il mirino e tengo premuto il tasto START e seleziono una destinazione, il FR955 si spegne e poi dopo qualche secondo si riaccende. Altra cosa, il tasto + sulla mappa funziona discretamente, il tasto - quasi mai.

    Ho guardato il widget TRAINING STATUS -VO2 max e non vedo nessun grafico delle ultime 4 settimane.

    Queste sono solo le prime cose che ho notato con il 12.25. Speravo proprio che la navigazione fosse sistemata, tristezza.

  • 0 over 2 years ago

    Installing now, only things changed seemed to be firstbeat stuff (ETE and LHA).

    Got an intensive run tomorrow but an easy one on sunday, wonder if this indeed fixes those issues...

    The 'selecting a point to navigate to on the map' crash is NOT fixed at least, still reboots the watch (wth, come one already)

  • 0 over 2 years ago in reply to Albertone

    No way that that isn't fixed! 

    How is that possible why even bother to release a new beta with these bugs. 

    Any release notes for this release?

    Or is it maybe a fix for battery drain? 

  • 0 over 2 years ago

    12.25 has definitely fixed the battery drain issue so far. It's the same as if i only sync over wifi so pretty happy so far!!!

  • 0 over 2 years ago in reply to Mauricewal

    Changelog:

    • Fixed an issue that could cause inaccuracies in the reported primary benefit for Training Effect.
    • Fixed an issue where the map cursor wasn't drawn on some maps, which prevented navigating to a point on the map.
    • Fixed an issue that could cause large Strava segments to be rejected by the device, resulting in rapid battery drain.

    1: may be fixed. Needs testing.

    2: has been done the usual sloppy way. The crosshairs show now but selecting a destination from a list still reboots the watch.

    3: needs testing.

    Garmin sets a very low bar for deciding on sending betas to production. If it doesn't brick watches then they think it's acceptable quality.

  • 0 over 2 years ago

    Have you tried to test the most annoying bugs of 12.23 (GPS inaccuracy and battery drain for always-on sync) ?

  • 0 over 2 years ago

    To be fair, I AM happy if this at least fixes the training effort stuff as that messes up many other things... So I can understand them first making a hurry with this and get that fixed asap.

    And indeed, the 'fixed map cursor' is also correct as I now remember indeed not seeing the cursor (just a small square) and now I indeed see a cursor. Only thing is that was one of the least important issues for me, the watch crashing when selecting a location on the map on the other hand...

    Ah well, let's hope at least the training effect issues are solved with this. Would be a step in the right direction.

  • 0 over 2 years ago in reply to 2479576

    12.23 didn't introduce any GPS inaccuracies for me. With multiband on I've always had solid GPS tracks on all firmware versions.

    I've also not had the battery drain problem either. I was under the impression it's a Garmin<-->iPhone user issue. I'm on Android.