SDK4 requiresBurnInProtection new devices

Hi,

Is this a bug or is this me?

I am migrating some watches that handle requresBurnInProtection mode by drawing a much simpler and smaller watch face.

The same code with the sizes adjusted for the size of the screen ALWAYS triggers a burnin error in the simulator as soon as I go into low power mode, despite the drawing being correctly replaced and resized to very small...

Am I doing something wrong or should I file a bug report?

0 9635560 over 5 years ago

in fact, it triggers a burn in error even if I have this as my burn in mode onUpdate

		dc.setColor(G.COLOR_BLACK,G.COLOR_BLACK);
    		dc.clear();

0 Travis.ConnectIQ over 5 years ago

Are you doing anything that would access the filesystem (loading resources, or accessing Storage/Properties) during the onPartialUpdate? There was a change that went in that makes it so that filesystem access results in your apps power budget.

0 Travis.ConnectIQ over 5 years ago in reply to Travis.ConnectIQ

Sorry, I'm confusing terms... I'm referring to power budget and you're very clearly talking about burn in protection.

0 9635560 over 5 years ago in reply to Travis.ConnectIQ

Exactly, and as per my two line example... not loading anything (or doing anything).

Simply going into low power mode in simulator triggers burn in warning. I suspect a simulator bug, but I am prone to human error so...

0 jim_m_58 over 5 years ago in reply to 9635560

Are you sure you're running your burn in code when you think you are? Putting in a println is an easy way to check.

0 Manuel B. over 5 years ago in reply to Travis.ConnectIQ

I can confirm that there is an issue with the burn in protection (simulation) of the Venu2(s). What I'm observing is hard to put in words. That is why I created a screen recording of my watch face running on the Venu compared to the Venu2.

Hope this helps to fix the issue.

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

0 9635560 over 5 years ago in reply to Manuel B.

Definitely a bug in simulator with CIQ4.

This is what I see when I go into low power mode.

For Venu, it correctly recognises I have cleared the screen.

For Venu2, it takes a reading prior to me clearing the screen.

0 BenW0828 over 5 years ago

I'm still seeing this issue for the Venu2 and 2s only -- using the same exact code that works perfectly on the Venu. Have any of you figured out how to avoid this problem?

0 jim_m_58 over 5 years ago in reply to BenW0828

See https://forums.garmin.com/developer/connect-iq/i/bug-reports/the-burn-in-protection-on-venu2-s-devices-with-ciq4-falsely-triggers-and-turns-off-the-display

Looks to be fixed in the 4.0.2 SDK that's available as of today.

0 BenW0828 over 5 years ago in reply to jim_m_58

Oh perfect! I had updated and was still seeing the issues. Another restart and it looks good to go!