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.
  • over 4 years ago in reply to 9635560

    If I don't move the data displayed (top half of screen then bottom half of screen), I overlay with a checkerboard (a custom font) and shift that every minute.  Sounds like it's possibly the draw lines.

    Sounds like a clue!

  • over 4 years ago in reply to jim_m_58

    I'm on a pc, too.

    It really does look like the CIQ4 devices simply object to either the time taken or something else using dc.draw() methods.

    I'm happy in that the font method of doing AOD is actually a gazilliion times easier than what I had been using, but it is a fact that I have precisely zero dc.draw() burnin protections that work.

  • over 4 years ago in reply to 9635560

    I'm just trying to figure out why it's working for some and not for others.  This isn't something that everyone sees.  I'm on a pc.  Are you on a mac?

  • over 4 years ago in reply to 9635560

    Also, as I am not able to edit posts on this forum for some arcane reason...

    I have also posted that using the exact same visual effect (stripes overlaying a design):

    1. Using a 64 bit tile font with black and white, I can get a valid display on Venu 2 lowPowerMode

    2. Using the exact same design, and same stripes, drawn using dc.drawLine() I get a lowPowerMode burnin exception that turns the screen off

  • Former Member
    Former Member over 4 years ago in reply to 9635560

    Thank you mate. 

    I have actually been able to identify the root cause of this issue, and an accurate way to reproduce it. 

    I have to step away from my Mac for a bit but when I come back I'm going to prepare a little demo video, make a little writeup for you guys, and then post some sample code. By the end of today there won't be any dispute that this is absolutely a firmware bug.