Update: Received with new batteries (EFast 10A 3500mah), unfortunately the problem still persists. I ran the firmware update again, as the problems I am seeing are very close to the problems listed in the pi forums. (https://forums.raspberrypi.com/viewtopic.php?t=381933) I have been using it for the past week on and off.
Problem: screen turns off, forced power off, 50/50 if it will reboot or show light green light instead of booting. Parrot OS and Bookworm, Parrot OS more often. Keyboard stays lit.
Trigger: High CPU usage, multitasking. Not just high CPU, but occurs when the CPU is at max 2.4Ghz, and I am using multiple apps at once. Or using the CPU at max and using the GPU at max (1080p video).
What I have done/tested: ran a meter across the power board, everything tests good to the main board. Monitor CPU, battery voltage and CPU temp. No constancy with the failure. Double-checked all connections. Reseated the core.
Next steps/thoughts: 1) Going to underclock the processor, see if that changes the issue. 2) I have an adaptor coming for the mini-hdmi. See if the pi is failing or something up with the display.
Hello.
I’m curious about something.
I’m using the lastest image and I do get sudden shutdowns at 50%-70%
When I try to turn it on (or when you’re rebooting), it shuts down as soon as the screen gets a signal (It’s not displaying anything, it’s black, but it’s turned on)
I speculate it’s software related because I still have my original image and when I switch to the stock version, the issue “is solved”
I did ran the battery calibration tool at 99% and I discharged de battery down to 55% then I shut it off because I was going to bed. Today, I tried to turn it on to no avail until I plugged a charger. Do I need to do the full battery cycle in one sit? (full charge, script, drain, full charge)
Also, it’s worth metionig that it just seems to need to pass the “turn on screen” screen stage. Once the screen is turned on, and the tux logo shows, you can unplug and work just fine.
@Rex this is what I got:
Linux clockworkpi 6.12.21-v8+ #2 SMP PREEMPT Sat Apr 5 17:04:59 ADT 2025 aarch54 CNU/Linux
I went to the cafetería (one story down) and when I looked at the uConsole, it was off (it turned off on its own). When I plugged it again, the battery was at 34% I unpluged it to see if the uConsole was forced to shut down, it has not, The battery right now is at 24% very light workload (just navigating the raspi-config)
I’m looking at this link https://www.raspberrypi.com/documentation/computers/configuration.html hoping to find the location of the power management options (like … at what percentage and time of inactivity should the console shut down, what happens if plugged or unplugged, when should it turn off the screen, etc) because the stock DE doesn’t have those options (or I haven’t found them) Plasma does have them but I have avoided installing it (it’s a bit slower)
EDIT
It just turned off haha
Edit 02
I’m at the office. I will run the uname command on the stock image once I get home (a couple of hours from now)
@Rex clearly I’m an idiot. Cm5 arrived, and since my uconsole is likely months away and I have a cm4 board for my devterm I figured i would try it. Now I know the cm5 is picky so right off the hop I wrote to 4 different brands of sdcard. I’ve done nothing to the config because I didn’t see anything mentioned (I am male so 100% chance I missed it). But all 4 do the exact same thing. First boot on for about 5min then powers off. Every boot after it shuts off almost immediately. I’m ASSUMING the 1st boot is doing the resize then fails to actually boot. Figured I’d start here for ideas.
If you are using a CM5 and DevTerm in the config.txt before you boot you need to edit it. comment out the uconsole in the [pi5] section and uncomment devterm.
Careful it does run hot!
Not sure if this has been mentioned (I believe it has, but not 100 sure) I just removed the batteries and the battery module. assembled it again and, at 17% battery, the console started and seems to be working.
i tightened the battery module a little bit more, not sure if that made a difference or if I just need to remove the batteries when this happens (would be a hassle haha)
i was never sure if the pins of the battery module should just touch the ports on the main board or if they should be inserted. i assume they just need to touch based on the whole design philosophy.
i will keep testing and switching between the stock and Rex’s images and hopefully get more data.
it’s worth (and important) to mention that when I arrived home, I switched to stock image and the console was unable to keep up, either shutting down or dying on me. After the tightening, I started the console with Rex’s image and it was able to go past the screen activation. I’m writing this on the uConsole, battery standing at 15% right now.
Will keep working till I either get to 0% or it shuts down before reaching zero charge..
I hope its just a case of the PEBCAK
will keep you informed
That will cause problems, they need to be inserted. With the battery tray at a 45° angle insert the battery tray from the front of the main boards connector not from the top, then lay flat.
a far better choice
