My Garmin and the sensors: are useless after something. The garmin goes to sleep after about 30 second gives 3 seconds warning then needs re powering up. But it goes into one of two moods screen powered and screen blank. This is worsened by a sharp corner when it springs to life 25% round the corner then the display persists for the last part of the ride. But it still freezes the screen. So you need to hit power up to get a refresh.
Now I also got the message that turning the screen on wasted battery. After two training rides I found the cadence sensor is uselesr as you can never see it.
As a software developer, I am acquainted with waterfall and agile Development, So please prod the development manager.
Now the sleep setting has not shown on my 810 (now with my brother), or on the 1030 until a week ago, I am suspicious that an update caused the powered down garmin to pick new software and uised 5% of the power. The only setting I can think of that might be involved is the Back light persistence one. But this sleep are apples and pears. And the ethos in the devopment team I was in was:
Fix things but don't change behaviour, so new parameters had no effect because the default was unless set it would behave as before.
Is it agile development that introduces:
Sleep untested.
Map for navigation (fisher price limitation) you get the entry and exit roads and a distance and time count down from 30 seconds away (the 810 was perfect at 15-20) and unlike the 810 shows no side turnings. Visual of the road topography is easy, watching a countdown number is for sitting still with your phone.
So all in all I believe Garmin development is Agile, something as bad as waterfall, unless testing is onerous.
Can we have a version without these bugs by February and possibly a pre bugs release quickly.
Also With software we receive no information, Could the 1030 show a short precis of the changes when booted with new software. Dismissable by a tap.
