Initial Reports of lockups during activies, particularly Ultras ?

Hi.
We have thread about OHRM consistency an accuracy. (no worse then F3HR)
We have thread about GPS accuracy (again no worse then F3/F3HR)

One thing that while infrequent, seemed to plague Ultra runners more ( > 50k) was lockups during an activity.
Usually a hard reset was needed to recover, sometimes if lucky you would be able "resume" but you'd have a section of flat-lined in the GPS track.

Any early reports from F5x users about lockup? Anyone run any Ultras? wooded, vertical, technical type of stuff to really challenge the "new" processor??
  • Never had and issue with the F3 up to 17 hours as long as I used smart if using 1 second the file was so much bigger the watch really struggled taking about 10 seconds of activity per hour to open and view a 1 second file

    I also have a vivoacive HR which has a much faster CPU/ memory size and it's much faster as I would think the F5 will be
  • I have a 50K on Saturday - I was planning on wearing the F5X with navigation and live track on - if it survives that then it should be OK! :-)
  • Never had and issue with the F3 up to 17 hours as long as I used smart if using 1 second the file was so much bigger the watch really struggled taking about 10 seconds of activity per hour to open and view a 1 second file

    I also have a vivoacive HR which has a much faster CPU/ memory size and it's much faster as I would think the F5 will be


    i had, in the past, always used 1sec recording one. Believed that general consensus was that lead to more accurate GPS tracks. Yes after a 50miler or so, the F3 could be very slow to load an activity.

    there were earlier reports (with the F3) that using the 3D vertical and ascent settings could lock up the device. I wondered if that happened. Except that the last 50m I did, that was turned off. Not sure why the unit would lock up. I happend 3 or so times for me. really upsetting 35miles into an event to find you just basically crashed and will have a trashing activity file. I never had that issue at shorter distances.
  • Former Member
    0 Former Member over 8 years ago
    I have a 50K on Saturday - I was planning on wearing the F5X with navigation and live track on - if it survives that then it should be OK! :-)


    On Sunday I did 33 miles, 1 second recording + GLONASS ON, bluetooth off, sound off, backlight 5%, everything else on. I was using Map Navigation with the map on most of the time and tracked perfect. 40% Battery left after 6 hours of running. No lockups and was using the buttons a lot.

    Was a little disappointed about the battery as the Fenix 3 was a lot better with this regard but I still need to tinker with the setting, maybe turning off wrist HRM and steps.
  • Historically on the F3 Glonass used about 10% more battery and using the navigation features also uses at least 2% more per hour

    I would think the using the 5X map full time would be a pretty big power user ?
  • On Sunday I did 33 miles, 1 second recording + GLONASS ON, bluetooth off, sound off, backlight 5%, everything else on. I was using Map Navigation with the map on most of the time and tracked perfect. 40% Battery left after 6 hours of running. No lockups and was using the buttons a lot.

    Was a little disappointed about the battery as the Fenix 3 was a lot better with this regard but I still need to tinker with the setting, maybe turning off wrist HRM and steps.


    With the F3 during a similar run would you also have all that turned on? How much battery would be left on F3? Was it turn by turn navigation?
  • Former Member
    0 Former Member over 8 years ago
    With the F3 during a similar run would you also have all that turned on? How much battery would be left on F3? Was it turn by turn navigation?


    Best I got with a breadcrumb trail screen was a 100 mile run in 17hrs with just less than 10% left. I would always have over 50% left with 50 mile runs from 7 to 8 hours. I can't remember if I turned off step tracking but always turns off BT, WIFI, HRM sensor.

    I think it just needs some tinkering and I'm hoping they bring out a charger to charge on the go.
  • Best I got with a breadcrumb trail screen was a 100 mile run in 17hrs with just less than 10% left. I would always have over 50% left with 50 mile runs from 7 to 8 hours. I can't remember if I turned off step tracking but always turns off BT, WIFI, HRM sensor.

    I think it just needs some tinkering and I'm hoping they bring out a charger to charge on the go.


    17hr Hundred, 7-8 hour 50m? You must have quite the trophy room, those are top elite numbers? I'm significantly slower than that. My 50s tend to be in the 11 to 13 hour range. and my only hundred, Superior in 2015, was about 35.

    needless to say, I need to recharge during runs. You're making it on a 1 charge. Very nice
  • Historically on the F3 Glonass used about 10% more battery and using the navigation features also uses at least 2% more per hour

    I would think the using the 5X map full time would be a pretty big power user ?


    I dont have my F3 anymore, pretty sure I have GPS+GLONASS on. I never used navigation on the F3. I would leave the map on, but that just shows where you went, cant imagine that used much/any battery.

    it would be cool to have a solid breakdown of which feature cost what in terms of battery life.
  • On Sunday I did 33 miles, 1 second recording + GLONASS ON, bluetooth off, sound off, backlight 5%, everything else on. I was using Map Navigation with the map on most of the time and tracked perfect. 40% Battery left after 6 hours of running. No lockups and was using the buttons a lot.

    Was a little disappointed about the battery as the Fenix 3 was a lot better with this regard but I still need to tinker with the setting, maybe turning off wrist HRM and steps.


    i just reread this. "map navigation with the map on most of the time". In your follow up you said breadcrumb. Did you preload some route and your F3 was actually navigating? Or was it the standard "map" screen. that is just display only of the current track up to that point, but is not navigating/following some preloaded track.