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

Forerunner 245 series - Beta Software Version 8.78 - Now Available

Forerunner 245 (non-music) Download

Forerunner 245 Music Download

Notes:

  • For any issues that you encounter please fill out the form included in the download and attach it to an email to [email protected]. Please note that you may not get a response to the email unless we need more information on the issue you report.
  • Although this software is believed to be reliable, it has not yet been released for production and should be used at your own risk.

Change History

Changes made from version 8.60 to 8.78:

  • Added support for Connect IQ system 5.
  • Updated incident detection to better distinguish between supported and unsupported activities.
  • Modified the software update process to allow the user to defer the installation. This replaces the automatic install during the user's sleep window.
  • Other minor bug fixes and improvements.

Installation Instructions

  1. Connect your Forerunner 245 to your computer using the USB cable.
  2. Download and unzip Forerunner245_878Beta.zip. Place the GUPDATE.GCD file in the \Garmin folder of your device's internal storage drive. From the RemoteSW folder, copy the GUP3204.GCD file to the device's \Garmin\RemoteSW folder.
  3. Disconnect your device from the computer, approve the update on the watch, and wait for the update to finish.
  4. If you would like to revert to the last public release software, place the GUPDATE-860.GCD file in the \Garmin folder and rename GUPDATE-860.GCD to GUPDATE.GCD. Copy the GUP3204-611.GCD file from RemoteSW\Downgrades, place it in the device's \Garmin\RemoteSW folder and rename it to GUP3204.GCD. Disconnect the device to install. NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.
  • Mmm, still no sleep widget.

    Hopefully this fixes the bluetooth music connection issues present in 8.30.

  • Great that we see the changelog form sw 8.60 but that version was never public think and the changelog from 8.30 -> 8.60 is missing

  • I updated to the beta, and watched my battery drain 1% per hour afterwards

    Multiple restarts did nothing

    System\Reset delete all data also did nothing (though I suspect it's required for the next step to work)

    What DID fix it was charging it to 100% for an hour or so.     it's been 12 hours since I did this and it's still 99% charged!!!

  • I am currently experiencing a similar battery draining issue of about 0.7% per hour... I am hopeful that your fix will work for me.
    If it's not too much trouble, please post your results after a day or two... just to make sure it wasn't a temporary fix.

  • Hi,

    Amazingly, not only has it stopped the drain, it's losing a TOTAL of 8-9 % a DAY now.

    I have Ox turned off, but everything else if default.   At this rate I'll be getting 11 days out of the watch in between charges which will be fantastic

    1. Getting sleep tracking on point on all devices should be the top priority for Garmin. Sleep is important for sportsmen, yet a 50 EUR Fitbit device measures it better than a 900 EUR Garmin watch. A scientist on YouTube is putting the devices to the test, and found that only the Vivomove Sport comes somewhat close to the Fitbit watches. I personally have the same experience, but bought into the Garmin ecosystem. It can’t be that hard, yet for years Garmin seems uninterested to solve this issue. 
  • You better add the updated sleep tracking Garmin!

  • Very weird. Have drain issues since 8.20 and might try your "fix" cause nothing helped so far. That kinda sounds like a wrong / lost calibration of the battery.

  • I'd be very interested to see if this does help you

  • This helped me! I've had my 245M since launch, so I've obviously lost battery capacity. But would frequently take it off the charger as soon as it hit 100%. I left it charging past that point for about an hour yesterday. Including a 45 minute run, I only lost about 5% throughout the afternoon, while previously (also including an equivalent run) I would easily be down at least 15%. 

    There may be additional drain introduced throughout updates, but it definitely appears that battery calibration is an issue as well.