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 jim_m_58

    Hi Jim, one can argue that this is what I'm doing. In onUpdate() I always draw my watch face the exact same way except I force the background and other large areas to black.
    In the end I check if protection against burn in is required. If so I overlay a pattern of black lines. This pattern shifts with one pixel each minute.

    This approach has worked with the Venu1 and D2 Air devices just fine.

    With the Venu2 and CIQ4 it almost seems as if the 2 burn-in rules have changed in a way that does not allow the watch face to violate the rules temporarily even if the pixels are cleared again before leaving onUpdate().

    I had an idea how I could workaround this problem simply by drawing into a bitmap buffer, doing the overlay there and then draw the bitmap to the screen.
    Only problem is that the Venu2 only has 124kB vs. 500kB on the Venu1.
    This fact combined with the higher resolution will also make this approach impossible. :-(

    Of course the above theory does not explain why the burn-in protection triggers for others when they just clear the screen with black color.

  • over 4 years ago in reply to jim_m_58

    Hi Jim, one can argue that this is what I'm doing. In onUpdate() I always draw my watch face the exact same way except I force the background and other large areas to black.
    In the end I check if protection against burn in is required. If so I overlay a pattern of black lines. This pattern shifts with one pixel each minute.

    This approach has worked with the Venu1 and D2 Air devices just fine.

    With the Venu2 and CIQ4 it almost seems as if the 2 burn-in rules have changed in a way that does not allow the watch face to violate the rules temporarily even if the pixels are cleared again before leaving onUpdate().

    I had an idea how I could workaround this problem simply by drawing into a bitmap buffer, doing the overlay there and then draw the bitmap to the screen.
    Only problem is that the Venu2 only has 124kB vs. 500kB on the Venu1.
    This fact combined with the higher resolution will also make this approach impossible. :-(

    Of course the above theory does not explain why the burn-in protection triggers for others when they just clear the screen with black color.

  • over 4 years ago

    Hi Jim, one can argue that this is what I'm doing. In onUpdate() I always draw my watch face the exact same way except I force the background and other large areas to black.
    In the end I check if protection against burn in is required. If so I overlay a pattern of black lines. This pattern shifts with one pixel each minute.

    This approach has worked with the Venu1 and D2 Air devices just fine.

    With the Venu2 and CIQ4 it almost seems as if the 2 burn-in rules have changed in a way that does not allow the watch face to violate the rules temporarily even if the pixels are cleared again before leaving onUpdate().

    I had an idea how I could workaround this problem simply by drawing into a bitmap buffer, doing the overlay there and then draw the bitmap to the screen.
    Only problem is that the Venu2 only has 124kB vs. 500kB on the Venu1.
    This fact combined with the higher resolution will also make this approach impossible. :-(

    Of course the above theory does not explain why the burn-in protection triggers for others when they just clear the screen with black color.

  • over 4 years ago in reply to jim_m_58

    No, I am not.

    And as per the OP, this all works perfectly in Venu and Venu Sq.

    It is only with the CIQ4 (wearable2021 and venu2/2s) that it crashes.

    But for the record the relevant onUpdate code is...

    ////

     function onUpdate(dc) {
            /////////////
            // Handle AMOLED burn in protection EG: Venu
            if(protectAgainstBurnIn(dc)) {              return;         }
    /////
    And if the sum content of my protectAgainstBurnIn method is:
    ////
    dc.setColor(0,0);
    dc.clear();
    ////
    I can see the error.
  • over 4 years ago in reply to 9635560

    Are you doing something in onUpdate like setting the background to be something other than black before you check if you're in low power for the venu devices?