When a .notify file is written to /config/ultrahand/notifications/ while the Switch display is off (screen timeout or short power button tap — not full hardware sleep), Ultrahand immediately renders the toast overlay, which wakes the screen. The screen then turns back off after the overlay dismisses.
Expected behavior: Ultrahand should check whether the display is currently active before rendering a queued notification. If the display is off, the notification should remain queued and display the next time the screen is already on.
Impact: Sysmodules that write notifications during background activity (e.g. during a save sync while the user isn't actively using the console) repeatedly wake the screen. On a Switch this drains battery and is visible as the screen flickering on briefly with no user interaction.
Suggested fix: Before rendering a pending .notify file, check display/backlight state (e.g. lcdGetBacklightSyncContext or equivalent) and defer rendering until the display is active.
When a
.notifyfile is written to/config/ultrahand/notifications/while the Switch display is off (screen timeout or short power button tap — not full hardware sleep), Ultrahand immediately renders the toast overlay, which wakes the screen. The screen then turns back off after the overlay dismisses.Expected behavior: Ultrahand should check whether the display is currently active before rendering a queued notification. If the display is off, the notification should remain queued and display the next time the screen is already on.
Impact: Sysmodules that write notifications during background activity (e.g. during a save sync while the user isn't actively using the console) repeatedly wake the screen. On a Switch this drains battery and is visible as the screen flickering on briefly with no user interaction.
Suggested fix: Before rendering a pending
.notifyfile, check display/backlight state (e.g.lcdGetBacklightSyncContextor equivalent) and defer rendering until the display is active.