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 in reply to Johnny.ConnectIQ

    Yes, I can call requestUpdate  during low power and even without onPowerBudget consequences - but it means that I can put requestUpdate  in onPartialUpdate and forget about power budget (of course users eat me for battery draining :)).

    Yes, I have var IsLowPower but can use the way you've written because system call every minutes onUpdate and onUpdate in others situations and I have to trust system not my var, for me important is if it's called onPartialUpdate or onUpdate.

    I've asked about it because on fenix 5 I have an error probably connected with trying use loadResource during low power but I use it only in onUpdate. And if this error occurs in first onPartialUpdate calling requestUpdate it resolves problem but I don't want to call it in each onPartialUpdate.

    I described t in forums.garmin.com/.../fenix-5-plus-14-00-bad-serve-onentersleep.

Comment
  • over 4 years ago in reply to Johnny.ConnectIQ

    Yes, I can call requestUpdate  during low power and even without onPowerBudget consequences - but it means that I can put requestUpdate  in onPartialUpdate and forget about power budget (of course users eat me for battery draining :)).

    Yes, I have var IsLowPower but can use the way you've written because system call every minutes onUpdate and onUpdate in others situations and I have to trust system not my var, for me important is if it's called onPartialUpdate or onUpdate.

    I've asked about it because on fenix 5 I have an error probably connected with trying use loadResource during low power but I use it only in onUpdate. And if this error occurs in first onPartialUpdate calling requestUpdate it resolves problem but I don't want to call it in each onPartialUpdate.

    I described t in forums.garmin.com/.../fenix-5-plus-14-00-bad-serve-onentersleep.

Children
  • over 4 years ago in reply to _psx_

    we had recently introduced "penalty" on "loadResource" called during low power mode, as that may induce disk i/o, and cause additional power drain.

    is there anyway you can move the loadResource to say, onShow or onLayout, once the resource is loaded to memory, you can use it whenever you want w/o being penalized.

    we can move further discussion to the other thread you opened.