[Bug]: T-Beam S3 Supreme OLED "Shutting down..." about firmware HOT 4 CLOSED

It sounds a little bit like your user button may be stuck down / shorted? Is there any chance you could test it with a multimeter or anything?

from firmware.

from firmware.

Still no luck with the CLI on 2.3.9 hey? Might be best to try troubleshoot on 2.3.4 for now? Do you think you could take a look at the debug output on 2.3.4, to see if there are any clues? There's a serial monitor button at https://flasher.meshtastic.org, if you don't have another preferred method.

I don't personally have this hardware sorry, so it makes it tricky to problem solve, but I'll do what I can!

from firmware.

Thanks for the input.
So I have rolled back to 2.3.4 and the problem still exists.
I have attached two log files, and it has taken around 30~40 minutes from start for it to show.
Looking at both logs, the even is logged - but there is no hint as to why.
First log, event is at 10:17:44 1976 (approx. 33 minutes from boot)
Second log, event is at 11:00:16 2318 (approx 38 minutes from start)
I also note, that there doesn't appear to be any logging of the user button presses. In the later log, i have pressed the button several times, to try and wake the screen (which it doesn't succeed in doing). I can see from the log, that the sending of the manual beacon appears to be logged.

meshtastic-log-2024-05-12T10-18-28.813Z.log
meshtastic-log-2024-05-12T11-04-00.697Z.log

from firmware.