You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
Alteration (enhancement/optimization) of existing feature(s)
New behavior
Description
According to this datasheet, the SSD1306 OLED has a register that can be used for fade out. This is missing from earlier revisions of the datasheet, but it did work on the OLEDs I have (only a single pair from the same source). It would be nice if this could be used instead of the DISPLAY_OFF when the OLED times out.
I have created a branch with a prototype implementation. I've just replaced the DISPLAY_OFF and DISPLAY_ON commands with the equivalent using the fade register.
This register also supports a blink mode, but that is not so relevant for me.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.
stalebot
added
the
stale
Issues or pull requests that have become inactive without resolution.
label
Jun 2, 2021
Feature Request Type
Description
According to this datasheet, the SSD1306 OLED has a register that can be used for fade out. This is missing from earlier revisions of the datasheet, but it did work on the OLEDs I have (only a single pair from the same source). It would be nice if this could be used instead of the DISPLAY_OFF when the OLED times out.
I have created a branch with a prototype implementation. I've just replaced the DISPLAY_OFF and DISPLAY_ON commands with the equivalent using the fade register.
This register also supports a blink mode, but that is not so relevant for me.
The text was updated successfully, but these errors were encountered: