Skip to content

feat: keep power button duration in RTC_DATA_ATTR#447

Closed
osteotek wants to merge 1 commit intocrosspoint-reader:masterfrom
osteotek:feat-pwr-duration-rtc
Closed

feat: keep power button duration in RTC_DATA_ATTR#447
osteotek wants to merge 1 commit intocrosspoint-reader:masterfrom
osteotek:feat-pwr-duration-rtc

Conversation

@osteotek
Copy link
Member

@osteotek osteotek commented Jan 20, 2026

Summary

  • keep power button duration required to wakeup in RTC_DATA_ATTR to avoid reading from flash on every button press

AI Usage

Did you use AI tools to help write this code? < PARTIALLY>

@osteotek osteotek changed the title feat: keep power button duration in RTC feat: keep power button duration in RTC_DATA_ATTR Jan 20, 2026
@osteotek
Copy link
Member Author

osteotek commented Jan 20, 2026

This only works when the device is connected to USB 😭 . Apparently, it disconnects the battery when going into deep sleep, and RTC attributes are probably cleared.

@DavidOrtmann
Copy link

This only works when the device is connected to USB 😭 . Apparently, it disconnects the battery when going into deep sleep, and RTC_DATA is probably cleared.

I think Larry found a solution for that: bitbank2/bb_epaper@2404ab6

@osteotek
Copy link
Member Author

osteotek commented Jan 20, 2026

This only works when the device is connected to USB 😭 . Apparently, it disconnects the battery when going into deep sleep, and RTC_DATA is probably cleared.

I think Larry found a solution for that: bitbank2/bb_epaper@2404ab6

I wonder how much it affects battery life in sleep mode.

@ngxson
Copy link
Contributor

ngxson commented Jan 22, 2026

Light sleep does affect battery life significantly as it's ~20 times more power consuming than deep sleep.

Just wondering though, the partition table does have spiffs, why can't we use it to store or cache some settings?

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.

3 participants