Display goes black after not reacting to a notification

Hi everyone,

I would like to ask for your advice. I am trying to adapt several of my watchfaces to AMOLED models, and in one case, I am facing a problem where the display goes black if I receive a notification and don't react to it (let it fade out). In that case, the display goes black after the notification disappears. Another way the display goes black is when I cover the display with my palm; the display goes black after I raise my hand.

I read a few posts here on the forum and found some mentions of a similar problem, but I think it was more of a device issue. This is probably not the case for me, because my other watchfaces adapted to AMOLED work fine. I have, of course, compared my watchfaces and did not find any differences that could give me a clue (onHide, onShow, onSleep, etc.).

Do you have any idea what could be the root of the problem?

Thanks!

Top Replies

All Replies

0 jim_m_58 6 months ago

When onUpdate is called in a watch face (any display type) you must always update the entire display Are you doing that?

The system clears the dc right before onUpdate is called on some devices. The sim doesn't show you this,

0 JohnFitzMontti 6 months ago in reply to jim_m_58

Yes, I do it. On MIP displays, it works fine, even on touch displays (no issue with the display being covered by the palm).

0 jim_m_58 6 months ago in reply to JohnFitzMontti

On AMOLED, is AOD on or off?

0 JohnFitzMontti 6 months ago in reply to jim_m_58

Yes, AOD is on.

0 jim_m_58 6 months ago in reply to JohnFitzMontti

If you are in AOD "mode" there's limits as to what can be displayed. The amount of pixels on, how long a pixel is on for, brightness, etc. In the sim

If you exceed the limits, the watch face goes black. You can see how your WF acts in the sim with File>View Heat Map

What you are saying is something I've not seen and I started adding support for AMOLED when the first venu was announced.

0 JohnFitzMontti 6 months ago in reply to jim_m_58

Yes, I know the rules, in Heat Map is everything ok.

0 jim_m_58 6 months ago in reply to JohnFitzMontti

Which device? I may have one, or one in the same family, where I can try my WFs. But I think it's a bug in your code.

0 JohnFitzMontti 6 months ago in reply to jim_m_58

I am using Fenix 8 51mm. Thank you for your effort.

And you are right, it is probably bug in my code, but I can not find it, so I am looking for any ideas how to solve it.

0 jim_m_58 6 months ago in reply to JohnFitzMontti

Try looking at a watch face I posted in this thread.

https://forums.garmin.com/developer/connect-iq/f/discussion/349473/simple-example-wf-that-shows-a-bunch-of-things

Burn in protection is just one of the things it shows. I don't have anything in the f8 family, so I can't try that. but you can add your f8 to the sample I posted.

0 flocsy🤠 6 months ago in reply to JohnFitzMontti

You wrote that other watchfaces you wrote work correctly, only one doesn't. So I guess you'll need to concentrate on the differences. Pick one that has the most similar code to the problematic. Do small changes, build it, put it on the watch for testing... Repeat...