• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 584 views
  • Users 0 members are here
Options
Related

long boot times (and usb disconnect times) on Fenix5

rinserepeat
over 3 years ago

Does anyone know offhand what causes long boot times on the Fenix5, and the same happens after the USB disconnect

Over a minute to power-on. Maybe longer.

There are less than 60 activities on the watch which I know is a choking point for the Fenix even twenty-five firmware versions later

I suspect it is something corrupted.

The USB FAT passes a chkdsk so I know it's not the filesystem.

I suspect it's some app or some other data it doesn't like and waiting for a timeout, or it's scanning a bunch of something.

  • 0 over 3 years ago

    It may be due to the amount of data, Such as maps etc..... When I update various maps and KMZ maps it usually takes a bit longer to boot up on my Fenix 5x.. Same if I have transferred a few new routes and POI's via Basecamp.....

  • 0 over 3 years ago in reply to rockncrag

    appreciate that attempt at a reason, however my fenix is almost fresh after a forced reformat

    there's something else going on, I assume something is corrupted somewhere already, they have really poor file management

    I know it gets sluggish after 60 activities but there's less than that and I trim the metrics/sleep folders to make sure there aren't too many files on the watch which is another known choke point

    I'm also getting screen burn-in after three years, it's like they purposely built in obsolescence

  • 0 over 3 years ago

    just to follow up on this and try to help the next person, it was a corrupted FIT activity file

    I use the "download heartrate" feature for my HRM-TRI and every once in a blue moon the watch will do something bad and corrupt the FIT file because it re-writes it (and deletes the original)

    every other day or so I delete old activities from the watch so it will sync faster (how stupid is that requirement) and apparently I eventually deleted the corrupted FIT file, which then allowed the watch to boot fast, I was not aware it scans all the FIT files on boot