Complete
over 4 years ago

WERETECH-11147

Fixed

The burn-in protection on Venu2(s) devices with CIQ4 falsely triggers and turns off the display

I have ported several watch faces with Venu1 AOD support to the Venu2 and Venu2s devices.

My AOD modes are straight forward. I'm using a dense pattern clearing every 2nd pixel row or column on the screen alternating each minute starting with the first row/column or the second row/column.

This ensures that less than 10% of the pixels are on and no particular pixel is on for more than 1 minute.

On the Venu2 the simulator detects a screen burn-in. On the Screen Burn-In Simulation window it looks like the overlay pattern is ignored.

Also some drawing artifacts are missing on the burn-in screen for example the minute and hour hands.

I'm in contact with 2 other developers who have similar problems with at least some of their watch faces.

I already uploaded my watch faces with Venu2 support to the Connect IQ store and received feedback from a user who also owns a Venu1 that

the AOD is not working on his new Venu2. - It turns off the screen.

So this is potentially not only a problem of the simulator but also of the actual device.

Here is a screen recording of the problem in action highlighting the differences between Venu1 and Venu2:

https://drive.google.com/file/d/123bDerdGzCovWEcJlxonKbRBSo96lqrq/view?usp=drivesdk

Manuel B.
Parents
  • over 4 years ago

    Hi,

    A small but interesting finding that gives a workaround:

    Following the discussion in the forums, I swapped from dc.draw to draw my overlay to using a font to draw my overlay.

    Seemingly, drawtext is quicker or something and Venu 2 appears to work with my overlay as text.

    And... as another interesting finding (that might well be a bug report in its own right) it seems that some devices (definitely VenuSq) take into account parts of the screen drawn at y = -1 so I have had to fudge my dc.drawText command to start at y = -3 for safety.

    G

Comment
  • over 4 years ago

    Hi,

    A small but interesting finding that gives a workaround:

    Following the discussion in the forums, I swapped from dc.draw to draw my overlay to using a font to draw my overlay.

    Seemingly, drawtext is quicker or something and Venu 2 appears to work with my overlay as text.

    And... as another interesting finding (that might well be a bug report in its own right) it seems that some devices (definitely VenuSq) take into account parts of the screen drawn at y = -1 so I have had to fudge my dc.drawText command to start at y = -3 for safety.

    G

Children
No Data