Burn in 24 hour Simulation not working?

Posting here to make sure I'm not missing something simple before reporting a bug, since I bet I'm doing something wrong...

In the simulator, while trying to run a screen burn-in simulation I am getting unexpected results. Specifically, burn in is not tripped, even though I think it should be. See below. (Simulator set to Venu 2.)

Basics of the watch face I am testing above. note that the center of the analog hands and the minute/chapter ticks and date window do not move. I run the 24 hour simulation and I get the following result:

Which I don't think is accurate, based on the rules as I understand them:

Less than 10% of the watch lit up (compliant)
No pixel on for 3 continuous minutes (definitely not compliant)

Given this, I wondered if my method for generating the watch face was getting me around the second rule sometimes, so I changed the low power mode to simply draw a static image with the basic drawing method:

But I get the same "all good here" message upon running a 24 hour simulation, and again is just a static image, which should trip the 3 minute rule. I also let the simulation sit on the screen for more than 3 minutes, and nothing changed.

So, I guess there are 3 potential conclusions here:

The 24 hour simulation is no longer working in terms of the 3 minute rule.
The 3 minute rule has been rescinded and the documentation is out of date.
My developer environment is out of date.

Has anyone seen this/can anyone pass along any thoughts?

My developer environment:

Eclipse 2022-03
CIQ 4.1.5

jim_m_58 over 4 years ago

I seem to recall that the 3min limit is no long the case on newer devices like the venu2. Try the same test on the venu.

coldheart over 4 years ago in reply to jim_m_58

Yep, just tested it on the Venu and it works as expected. Perfect.

Do you know if there is a list of what devices have the 3 min limit vs not? And if there is any way to check aside from pulling model name?

_psx_ over 4 years ago in reply to coldheart

The problem can be different. According to the user guide:

if you make tests during sleep time there will be no burn because real device switches off display so there is no burn (but of course full 24h should rise error).

There is another option in sim "Sleep mode" maybe it emulates display off so no bur too.

For safety, however, I would do a good AOD.

jim_m_58 over 4 years ago in reply to _psx_

"sleep mode" in the sim is a left over from the early days of CIQ, where on the Fenix 3, you could manually set when you are sleeping.

Don't confuse that with onEnterSleep and onExitSleep

There is the associated "isSleepMode() that uses that setting in the sim but is meaningless on real devices:

var isSleepMode as Lang.Boolean or Null

This has been deprecated

This member will be removed in Connect IQ 4.0.0

Determine whether the device is in sleep mode. Value may be null.

Since:

API Level 1.0.0

Supported Devices:

Returns:

Lang.Boolean

_psx_ over 4 years ago in reply to jim_m_58

I've expected just it is.

For me is strange that new amoled devices don't apply burn policy - I have not heard of a technology that prevents amoled burnout when turned on.

venu 2 user guide:

venu 2 sim, 4.1.5

dc.setColor(0, 0xFFFFF);
dc.clear();

jim_m_58 over 4 years ago in reply to _psx_

They don't use the 3 minute limit. Likely new HW as it's AMOLED devices with the Venu2 or newer. I use the same code as I do for earlier devices on everything.

The 10% rules applies to all AMOLED devices, even the new ones

jim_m_58 over 4 years ago in reply to jim_m_58

Umderstand the 3 minute rule is more burn-in relates, while the 10% rule is more battery related.

Unlike MIP devices, if a pixel is non-black, more battery is used to show that pixel, therefore the 10% max.

_psx_ over 4 years ago in reply to jim_m_58

yes, you are right