Log shows uptime timestamps instead of actual timestamps #32

Closed
opened 2026-10-27 15:35:09 +01:00 by adam · 1 comment
Owner

Describe the bug
In the Log text timestamps seem to reflect the time since boot/uptime when an event occurred. It seems more logical to me that the timestamp shown is an actual timestamp, similar to the timestamps shown in Channels.

Which device are you using*
LilyGO T-Deck Plus

To Reproduce
Steps to reproduce the behavior:

  1. Go to Mgmt
  2. Click on the arrows until you are in the Log screen
  3. Check the time stamps

Additional context
If there is a good reason for using relative time since boot for the logs, maybe a toggle to allow the user to choose between the two options makes sense?

**Describe the bug** In the `Log` text timestamps seem to reflect the time since boot/uptime when an event occurred. It seems more logical to me that the timestamp shown is an actual timestamp, similar to the timestamps shown in Channels. **Which device are you using*** LilyGO T-Deck Plus **To Reproduce** Steps to reproduce the behavior: 1. Go to `Mgmt` 2. Click on the arrows until you are in the `Log` screen 3. Check the time stamps **Additional context** If there is a good reason for using relative time since boot for the logs, maybe a toggle to allow the user to choose between the two options makes sense? <!-- github-sync-id:3839914562 -->
adam closed this issue 2026-10-27 15:35:09 +01:00
Author
Owner

as soon as you got the correct time, it will automatically switch to the "Time" indicator, if no time is loaded - Uptime is the way to go.
Improved in v0.9.5!

as soon as you got the correct time, it will automatically switch to the "Time" indicator, if no time is loaded - Uptime is the way to go. Improved in v0.9.5! <!-- github-comment-id:3790973372 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#32