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

NEW - Forerunner 945 Beta 4.41

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.

Changes made from version 4.40 to 4.41:

  • Updates to improve phone connection reliability

Installation Instructions

  1. Connect your Forerunner 945 to your computer using the USB cable.
  2. Download and unzip Forerunner945_441Beta.zip. Place the GUPDATE.GCD file in the \GARMIN folder of your device's internal storage drive.
  3. From the RemoteSW folder in the unzipped download, copy the GUP3303.GCD into the \GARMIN\RemoteSW folder on your device.
  4. Disconnect your device from the computer, approve the update on the watch, and wait for the update to finish.
  5. If you would like to revert to the last public release software, place the GUPDATE-440.GCD file in the \GARMIN folder. Rename GUPDATE-440.GCD to GUPDATE.GCD before disconnecting your device. NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.
  6. To downgrade your peripheral software, place the GUP3303-501.GCD from the RemoteSW\Downgrades folder into your device's \GARMIN\RemoteSW folder.
  • Does anybody know how good is battery life on this beta?

    4.40 release is good but not as good as it was on 4.20, where I've had approx. 7.5 days in smart watch mode, whereas on 4.40 I have 6.5 - 6.8 days.

  • So far, my battery's been about the same as the other builds since I got my 945 in September. That is, most days it's around 12%/day. Sometimes, it's gets down to 8%/day. And, frequently, it jumps up to 25%/day for no good reason.

  • Thanks, Ray. I've had higher battery drain with one of third party watch face. The battery could drop just by 5-6% from morning till late night, but when I woke up the next morning, I saw that battery have dropped by another 10-11%, though PulseOx sensor was always of. So, because of this strange night drain the overall daily drain was 16-17%, it has gone when I switched to another watch face, so I've made a conclusion that the watch face the one is using matters a lot, even if the particular watch face has no obvious reason to be consumptive

    1. connection with garmin mobile app still is unpredictable sometime connects, most of the time not. And that’s the main reason for the update. On the FR screen the phone symbol is green and says connected open app. My app is open and in the app my Forerunner is greyed out and the green dot is not available. When i try to connect my watch with the phone in settings (hamburger) then the symbol of gem comes forward and it spins, but doesn’t connect. eventually it reports download GCM for a better experience.I am on IOS 13.4.1 and GCM 4.29.2
    2. my heart rate in a very easy run was at least 45 - 50 beats too high during the whole run (connected with HRM run strap) My power was 209 at average so my heart rate should be between 110-120
  • It's still the same for my watch with this Beta, I have to restart the bluetooth of my phone to connect my watch to garmin connect.

    And it has a higher battery drain than before.

  • It's still the same for my watch with this Beta, I have to restart the bluetooth of my phone to connect my watch to garmin connect.

    And it has a higher battery drain than before.

  • I have this problem since IOS 13 came out. 

  • Changed the battery and wore the watch over my long sleeve so the ohr couldn’t interfere with my chest hrm run. But still heartrate s wat too high. Easy run shouls be around 110,-120 bpm. But the run is in gcm with an average of 151 and a max. Of 173. My max heartrate in the lab was 152. Belt was wet before the run and clean. 

  •  When it come to HR from an external monitor the 945 just records what the chest HRM reports. The fault is not in the 945. What yo can try is to enable HRV logging on the 945 and look at the HRV data, as this clearly shows when the data is corrupted. Runalyze.com is my preferred option.

    This is what good HRV data looks like:

    And this is what poor HRV data looks like:

    This was the cool down (good) and warm up (bad) I did this morning. The warm up gave a max heart rate of 180 (should have been 130 or so). I'll monitor this on my next runs but if this continues it is an indication it is time to replace the strap on my HRM (which is a Polar H10, generally considered to be one of the better ones available)

  • Thanks, I reviewed my training from april 22 th and i see a good hrv graph in Runalyze. After that i went to 4.41 As of april 24 th i don’t see any hrv in Runalyze so the hrm must be at fault. It isn’t the battery because i replaced it after the 24 th, and both runs after the fw update  don’t show hrv. Are you on 4.41 also? Or just a coïncidence ?