I accidentally reflashed… well, sort of accidentally.
I started going through the motions despite the fact that the LED wouldn’t illuminate or indicate anything. However, once I connected to the computer, it started the flashing process anyway. FYI, @dos .
So now I’ve got a brand new install of byzantium LUKS variant.
I’ll have to set everything up again… or maybe I’ll flash crimson just to check out its current state. Thoughts, @FranklyFlawless ? I’m not using the L5 as my main phone yet, anyway.
P.S. I noticed right away that plugging into a wall socket still doesn’t initiate charging unless I power down. I was hoping that would be sorted with a new install.
Strange that there was no LED, though. This was with VOL-up + Power-On (battery in). I don’t know if it would have flashed, had I connected at that point, but:
I then switched to battery-out/HKS-engaged/VOL-up, and then cable-connect. At that point, I did get an LED during the actual flashing.
Two new issues I’m experiencing since the latest reflash:
1_ At power-on, before LUKS password input screen, the “Librem 5” splash appears as normal, but then doesn’t advance. I usually wait a minute or so, and if it doesn’t continue to the LUKS password screen, then I do a hard reboot with the power button. (Whether the device is doing some kind of periodic, routine systems checks during the stuck splash screen, I don’t know. And, actually, I do seem to get this issue after I’ve rebooted due to a misbehaving app.)
2_ Sometimes wifi is absent after boot-up. (Nothing to do with the killswitch.) I don’t know if it would eventually enable itself, but I just reboot in order to get it back.
Possibly it is verifying a file system that was improperly unmounted, specifically the /boot file system since by definition it can’t verify the root file system until after you have entered the LUKS password.
To be honest, I wouldn’t expect the fsck to take long on such a small file system unless it actually finds problems and then doesn’t handle that situation well. (I don’t think I’ve ever had a fsck issue on my Librem 5, so I don’t know what the interface looks like at that point.)
If you really wanted to deep dive on that with some troubleshooting, you could instead of booting up the phone, boot Jumpdrive on the phone and then fsck each file system on the host computer (three file systems if you also have a µSD card).
For most misbehaving apps, kill (or equivalent) is far more friendly than a reboot of the phone. On the other hand, if it’s phosh misbehaving then a reboot may be needed.
IIRC, everything was frozen and I couldn’t dismiss the app on the screen or launch the terminal. I’ll try to pay attention next time it happens. Thanks.
Well my USB ethernet dongle works well on my Librem 5 … but WiFi or ethernet, you need it set up and known to be working before you experience problems, so that you can verify whether you have lost access via ssh - and if you haven’t lost access then that opens up additional troubleshooting options.
Today I got the stuck(?) “Librem 5” splash on a shutdown, and it was because I didn’t wait for an app to completely shut down. I was not able to ssh in over wifi.
I allowed the splash some time to sort itself out, but after several minutes of nothing happening I powered it down manually.
OK, I also get that “Unknown app” message. After I continue with the power down anyway, then I see the splash screen that doesn’t want to proceed. So then, if I understand it, a hang, as described in that post, is causing the misbehaving app?
