Skip to content

Fix ThinkNode M1 e-ink screen blanking after display auto-off - #3649

Closed
plainsbuilder wants to merge 1 commit into
meshcore-dev:devfrom
plainsbuilder:fix-m1-eink-blank
Closed

plainsbuilder wants to merge 1 commit into
meshcore-dev:devfrom
plainsbuilder:fix-m1-eink-blank

Conversation

@plainsbuilder

Copy link
Copy Markdown
Contributor

Summary

Fixes the ThinkNode M1 screen going blank shortly after boot on 1.18.0 (#3612, #3601).

Since 1.18.0, GxEPDDisplay::turnOff() wipes the panel to white and hibernates it. The M5, M8 and T-Echo build with AUTO_OFF_MILLIS=0, so on those boards it only runs when the user asks for it. The M1 still inherits the 15 s default from UITask, so its screen gets wiped 15 s after every boot. Since the random BLE pin is only shown on the home screen, a new phone can't pair, and waking the screen with the button often doesn't redraw until a second press (the status bar goes missing).

This adds an opt-in EINK_KEEP_IMAGE_WHEN_OFF flag. When it is set, turnOff() only switches the backlight off and stops refreshing, leaving the last frame on the panel, which is how the M1 behaved on 1.17.1. It is enabled for the two M1 companion envs only, so the other e-ink boards keep the new behaviour.

I didn't go with AUTO_OFF_MILLIS=0 for the M1 because it has no BACKLIGHT_BTN. Its backlight is switched from turnOn()/turnOff(), so with auto-off disabled the backlight would never come on from a button press. This is meant to get M1 users working again while the common e-ink behaviour discussed in #3612 is worked out, happy to rework it if that goes a different way.

Testing

Verified on a ThinkNode M1 with ThinkNode_M1_companion_radio_ble:

Also flashed stock 1.18.0 on an original T-Echo for comparison. It is not affected (AUTO_OFF_MILLIS=0, so turnOff() is never called on a timer) and was stable, which is why the change is scoped to the M1.

All five M1 envs build clean against current dev, plus LilyGo_T-Echo_companion_radio_ble, ThinkNode_M5_companion_radio_ble and ThinkNode_M8_companion_radio_ble as a regression check for the shared GxEPDDisplay change.

@fdlamotte

Copy link
Copy Markdown
Collaborator

Thank for this PR,
The issue has been dealt with in this PR: #3659
This will be followed-up with somme cli toggles which should come in the week to configure the behaviour according to one's taste

@fdlamotte fdlamotte closed this Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants