AOD display in watchface flickers

Call garmin support.

trudelta,

as suggested I contacted Garmin uk support and they have passed the issue back and said as the fault is not occurring on Garmin stock faces it must be the 3rd party watch face that is the problem.

/cfs-file/__key/communityserver-discussions-components-files/600/IMG_5F00_1335.MOV

That does not make sense because in AOD mode, the watchface is only allowed to execute by Garmin once per minute.  Any display changes faster than that indicate a Garmin software or hardware problem.

I created the AOD/AOS test watchface to prove this. Watch the count values or HI and LO power updates. Note the count values before entering and after exiting the AOD display, and you can see how many times the watchface software actually updated the screen.  If it flickered 20 times and the LO count only increased by 1 or 2 then it proves that it is a Garmin problem.

  Don't compare to Garmin stock faces because they are written in a totally different way, using functions that are not made available to 3rd party watchface developers.  

Trudelta, thanks for your help.

I don't seem to have a way forward on this as I said Garmin are telling me its not there problem and not really helping

I totally understand what you are telling me

I am just the end user trying to get a fix on this. 

Its a pity as this is my favourite watch face but I can't cope with the battery drain/flicker: today 9% in under 3 hours.

I think I finally found a fix.  Garmin was of no help.  Please use the contact developer link on any of my app description pages to send me a message telling me what watchface you need fixed.

Some 3rd party watchfaces indeed flicker, I'm not sure if they need to sync with the watche's AOD refresh rate, or what's happening. 

But as long as the Garmin default watch faces don't flicker in AOD I'd say its an issue with the way the 3rd party watch face is coded. 

Don't compare to Garmin stock faces because they are written in a totally different way, using functions that are not made available to 3rd party watchface developers.

From actual testing I am 99.9% certain that the root cause is on the Garmin side (hardware or software; more likely hardware).  I have filed a bug report with Garmin.