Low Power Mode - Simulation always triggers burn-in protection

Former Member over 5 years ago

I'd like to develop a watch face for Venu that displays some info in low power mode. I've tried to use the Analog sample code to see how this is done. When I run the Analog code in the simulator, I always get the burn-in protection triggered. In my own code, when the watch is not "awake", I'm issuing a dc.clear() and still getting the burn-in protection. I'm missing something here. Any suggestions or additional examples to help me figure this out?

Thanks!

jim_m_58 over 5 years ago

See https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-3-1-now-available

The Venu uses Burnin protection (for the AMOLED display), and when in low power mode there are things you need to take into consideration, like no more than 10% of the pixels can be on, and no single pixel can be on for more than 3 minutes. The Analog sample doesn't have this logic. I'm not sure any of the SDK samples do

"file>view Heat Map" in the sim helps to see what's going on

Also see https://forums.garmin.com/developer/connect-iq/f/q-a/192673/how-to-enable-an-always-on-mode-for-venu-amoled