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 Edge 1040 Series Public Beta 14.13 Now Available

A new Beta software for the Edge 1040 Series has been released. Full change log, instructions, and software for installing the beta can be found in the link below.

https://www8.garmin.com/support/agree.jsp?id=15990 

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 14.12 to 14.13:

  • Updated to Training Status 2.0
  • Fixed issue with Di2/Remote actions going to previous page
  • Fixed Connect IQ issue with getting temperature data
  • Fixed changing data fields on workout data screen
  • Fixed auto lap by position
  • Fixed issues with eBike range
  • Made minor improvement to power calibration UI
  • Fixed various bugs and improved product stability

Changes made from version 12.16 to 14.12:

  • Added support for eBike Smart Range
  • Added Music Control widget
  • Added support for Intensity Minutes
  • Added support for Fitness Age
  • Added climb markers to elevation graph
  • Added support for the Tempe temperature sensor
  • Added support for Connect IQ glances on the home screen
  • Added Segment Time data field
  • Added support for startup.txt
  • Added support for turning off Daily Suggested Workout on main menu
  • Added support for returning to training loop using Di2/Edge Remote buttons
  • Improved capitalization behavior on the keyboard
  • Improved turn prompt responsiveness
  • Improved auto-pause responsiveness
  • Fixed issues related to Connect IQ
  • Fixed issues related to Real Time Settings
  • Fixed issues related to solar gain reporting
  • Fixed potential freeze with specific map locations in Europe
  • Fixed issues related to map zooming
  • Fixed issue with disabling turn guidance
  • Fixed various bugs and improved product stability
  • Can't be that. How can the same route works on Edge 830 with the Climb spot on and not working on 1040?

  • It would be great if you include the final of a climb using Climb Pro in your video - since Edge 1040 seems to work with a lag on Climb Pro as well

  • As always, Garmin's programmers did not disappoint. They fixed one thing they broke in the previous firmware version which was the control of the extra Di2 buttons, and they broke two more. Well, it's not that the "sharpen for corners" option is permanent. When there is a sequence of turns one after the other and the second one is different from the first, the E1040 will alert you to the first, but in the opposite direction than it actually is, and it seems to see the second turn in the opposite direction to the first. Then Strava segments: in the previous version of fw. they worked fine and this one had to be broken. You can see segments on the map while driving, although the "segments" option is activated in the E1040 and Garmin Connect, the segments are not displayed while driving. Do you employ middle school programmers? If you find it difficult to maintain correctness in the software, please make your codes open source and I assure you there will be no such indolence. The Edge 1040 is my last Garmin, and I have fenix6xpro, vienu, vivo, edge 1030+ and Explore, Varia Radars in various versions starting with Vector3. I'm sick of your ignorance and ignorance of the people who use Garmin products. I intend, as in the UK, to shock you with a class action lawsuit against Garmin. The middle has changed.


  • El video ilustra perfectamente el problema que ya viene de versiones anteriores

    • Actually also Power Guide works with a lag and eventually it shows you are climbing when you are already descending 
  • Programmers at Garmin, go on vacation and don't come back. It will be better for the devices and nerves as well as the mental health of the users of your devices. Imagine that the mobile receives fw. with beds like you releasing and it doesn't matter if it's alpha or beta, it's important that you prove that you are a loser. Imagine you are releasing fw. for mobile. And the situation is this: you can make a call from the mobile, but you can not answer the call, but otherwise you can send an SMS, but you know that someone sent you a text message, enter this function and it is empty there. Or maybe let's say one number can be called and rumery starting with the number 7 or 5 can not be called anymore. Do you have any idea what would happen with such a mobile? Then consider this because frustration is building up. Me and my koledzgy are fed up with these stupid games by Garmin and the peak was to release the 1040 with an underdeveloped fw. and treating users like beta testers.

  • Actually it worked perfect for me. Tomorrow next test…

  • This is really getting worse and worse. Coming back to 12.16 is almost not an option. This version broke now the trun-by-turn direction, so now we have:

    - Grade Lag in a point that is useless

    - Climb Pro with a super Lag that also makes it not a tool to be used anymore

    - Turn by turn, depending on the case, completely broken and erroing out. That includes warnings on Routes saying you are OFF route that in fact you are not.

    So the ONLY option I have, even after spending a lot of money with Garmin TOP product, is to go back to my Edge 830. This is ri-di-cu-lous. How can a company launch what is supposed to be your high-end product with a firmware that makes it a brick?

    I am not sure why after Vector 3 I still believe in this company. It is becoming very annoying. How can somebody uses Edge 1040 with those 3 items above completely broken???

  • You do realize this is a beta firmware. These things are normal in the beta world. If this was a final release then I could agree with what you said but dude you need to chill out. 

  • If there was an stable version you would have a point. BUT...we don't have any single stable version where we can use. I am only here at this page using this beta version because 12.16 sucks.

    So I don't think I am exaggerating here. The product I bought didn't have "STILL A BETA PRODUCT - USE IT AT YOUR OWN RISK" at the box...