• Replies 7 replies
  • Subscribers 19 subscribers
  • Views 675 views
  • Users 0 members are here
Options
Related

Just enough luminance?

myaro

Among the group, who has successfully used the new 10% "luminance" threshold instead of the 10% "lit pixels" threshold?

I'm exploring ways to try the luminance route, and I'm finding it hard to get the right luminance to uniformly "dim" the screen.  I'm trying to take the "easy way" out and just paint a semi-opaque black rectangle over the entire screen -- with just the right amount of "alpha" so that it hits the luminance threshold.

But I'm finding big differences between the amount of "dimming" I need to apply for various themes. For example, between these two themes on the same watch face app, I'd need to apply drastically different "dimming" layers.  The bright moon one would require a lot more darkening than the "deep sky" one with a black background and stars.

I see a few options:

- Configure different "dimming" parameters based on each theme (tuning it myself, with some themes needing to be darker than others)

- Get more complicated and "dim" specific parts of the screen (e.g. the background by itself)

Any tips or ideas?  What has worked well?

  • Sounds logical to me: using semi-opaque black rectangle means IMHO that you reduce the luminescence by a given percentage. Starting from a darker picture you get a darker result. Darker result means less luminance. What am I missing?

  • in reply to flocsy🤠

    I was trying to see if anyone came up with a more clever way of "picking" the correct darkness given whatever is dynamically on the screen.

    Is there any kind of built-in "current luminance used" function I missed in the docs, which can be used?

    To hack it, I made a temporary Setting/Property I could tweak at runtime to control the "dimming.  Then I went theme-by-theme, finding the right % darkness for each theme to get it just under 9.5% luminance.  Very manual, and I'm not sure that's super reliable for testing all cases/devices.  But it's my current solution.

    It would be really swell if Garmin provided a simple "turn down the lights" function that turned it down, however much necessary, to just render the same thing but darker.  I appreciate the flexibility to do something more "custom" here, but I think most developers just want "the same thing but dark enough."

    Anyway, i shipped my updates as is, but I'm open to hearing other clever solutions to solving this.

  • in reply to myaro

    How do you check the current luminance used?

    Maybe just a linux issue, but the only relevant option I could find is "Screen Burn-In Simulation", and it doesn't show anything when in high-power mode.

  • in reply to Matei C.

    You want to look when the app is  in AOD/low power mode as that's when it's used.

  • in reply to jim_m_58

    Thanks Jim, I'm looking for the high-power luminance. My face is working fine on MIP devices and AMOLED simulator, but it disappears after one frame on a real Venu 4, and my best guess was exceeding the 10% luminance threshold in high-power mode.

    Does the 10% only apply in low-power mode?

  • in reply to Matei C.

    As far as I understand it's only low power/AOD which is how the watch runs the majority of the time.

    By "one frame", to you mean after a 1 minute update?

  • in reply to jim_m_58

    Less than a second after initial render. Thanks for the information! It's probably something else entirely then, I'm doing a lot of "dynamic" rendering. But having trouble accessing the logs on that Venu 4 (I get them fine on a Tactix 7, with the same mtp / .txt setup) and I have several dozen questions for you and the rest of the dev community, better if each has their own post and I don't pollute this very sensible thread with irrelevant tangents.