It seems to me that power consumption with "MC-Term" is higher than needed:
I use: T-Deck Plus with MC-Term firmware version 0.9.10.
With the "Ripple GUI" formware I could leave the device running for a whole day on battery (i.e. 24 hours at least). With "MC Term", after I came back home after 19 hours, it was off due to empty battery. (I do not know at which time it went off).
It is still only a "feeling", not a whole measurement process, but does the software put the hardware into sleep and not doing activity when not in use?
(What I see is that in the "Neighbor RPTs" screen, the seconds continue to tick, so I am wondering if software stays active even if no LoRa data is received and screen is off.)
It seems to me that power consumption with "MC-Term" is higher than needed:
I use: T-Deck Plus with MC-Term firmware version 0.9.10.
With the "Ripple GUI" formware I could leave the device running for a whole day on battery (i.e. 24 hours at least). With "MC Term", after I came back home after 19 hours, it was off due to empty battery. (I do not know at which time it went off).
It is still only a "feeling", not a whole measurement process, but does the software put the hardware into sleep and not doing activity when not in use?
(What I see is that in the "Neighbor RPTs" screen, the seconds continue to tick, so I am wondering if software stays active even if no LoRa data is received and screen is off.)
<!-- github-sync-id:4004884843 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It seems to me that power consumption with "MC-Term" is higher than needed:
I use: T-Deck Plus with MC-Term firmware version 0.9.10.
With the "Ripple GUI" formware I could leave the device running for a whole day on battery (i.e. 24 hours at least). With "MC Term", after I came back home after 19 hours, it was off due to empty battery. (I do not know at which time it went off).
It is still only a "feeling", not a whole measurement process, but does the software put the hardware into sleep and not doing activity when not in use?
(What I see is that in the "Neighbor RPTs" screen, the seconds continue to tick, so I am wondering if software stays active even if no LoRa data is received and screen is off.)