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

Edge 830 9.75 new error message - Temperature to low backlight will be limited

Did anybody else get this? I got it unexpectedly this morning with a temp around 1 degree Celsius.
I rode on a bit lower temp several times during  the last weeks and  this error never appeared.

What should limited backlight in case of low temperature mean?
For me it would make sense backlight limited in case of high temperature...

  • Yes, my Edge 530 also started to show this message after 9.75 update. Can't find anything from settings to disable this.

  • Same here, Edge 530. Exactly as your, below 1 degree. Irritating. 

  • same here.  .. in addition it happened that some minutes after turning it of (stand-by) it enables the backlight - without displaying something  .... (maybe to compensate the energy savings ...!? :-) )

  • Got an idea what it is for. Energy saving as low temp may limit the battery.

  • Sure, but 530/830 ought to take it into consideration whether the battery level is 95% or just 20%.

    Can you all please elaborate  what the battery level of your device had approximately when you got this brand new warning and limitation?

  • Anyway Garmin fitness/cycling team is not better in transparency than its outdoor team. I mean if you properly read the release notes

    Changes made from 9.73 to 9.75:

    • Added CIQ security fixes and improvements.
    • Improved indoor trainer non-power workout step transitions.

    Changes made from 9.50 to 9.73:

    • Fix Firstbeat stats resetting on power cycle
    • Add informational prompt when pairing a non-Garmin Radar sensor.
    • Add informational prompt to update RCT715 to get more features
    • Improved CIQ data fields so that copies of the same field don't limit adding unique fields

    you get no warning that your device will be impacted after detecting a temperature being under a certain threshold.

    I am quite sure that this change in the code was not done by a mistyping of some programmer.

  • way above 20% in my case, it was even on fully charged device (over 90% of power)