I tested one command line application and one GUI application.
The command line application was a little slow to start but ran normally.
The GUI application was basically unusable. It works normally on desktop Linux (and on Microsoft Windows). On the Librem 5 the main window doesn’t come up - just remains blank. So no GUI controls are usable. However, where keyboard shortcuts exist, the application responds to those, but still doesn’t work.
With Bluetooth, WiFi and the modem on - but the screen mostly off - and sshd in - with a couple of apps running - all doing “not much” … 8 hours 55 minutes before it shut down in a controlled fashion. This should be a fair indication of “standby” time (providing that Bluetooth, WiFi and modem all on is representative of how you use the phone).
The “low battery” notification came at 10%. The “critically low battery” notification came at 2% - and within a few minutes of that it shut down.
i wouldn’t make a habit of letting the battery reach such a low depletion state … but perhaps the firmware accounts for that and leaves some spare room … at least that’s how i remember it being by reading some OLD posts here on the Purism forum …
Oooh… that’t a good point: what kind of warnings are there and can user set them? How - GUI or edit a file? Something different than normal messages? Other actions possible/recommended when certain limit reached?
Blue light comes on because of the notification. However that is not distinguishable from any other notification (new SMS, new email) without pressing the wake/sleep button to activate the screen, at which point it will be obvious that power is low.
For the time being, I am happier for development resources to be expended on increasing the time-between-charges rather than on fancier notifications.
However since it is open source, go your hardest. At the very least, I think it would be easy enough to run a cron job every 10 minutes and if battery is at or below 10% then it will play @reC’s message or something less melodramatic, since you might be in a business meeting. LOL. Also, I don’t want to get emergency services involved. I might try this later …
Wow, that’s old school! Years ago my partner at the time had a Palm PDA that did that. One evening we heard a strange electronic shrieking noise that we hadn’t heard before, and it was the Palm running out of juice. We joked that it was like looking after a tamagotchi , which were also cool gadgets at the time
well, joke aside … the L5 simply needs to play the “Help ! I’m dying !” message in a MORSE code audio signal. how ? beep-beep beep-beep-beep beep beep beep-freaking beep … in a loop until it annoys everybody involved so much that they say “put it out of it’s misery already !”
Might be I’m catching what you are looking for. Try to drive what you need like this (as used from my side under Mobian, but it is actually just about how GNOME Settings are structured anyway):
Settings / Power, and there are three soft-switches that might be preferred to be used on daily basis / current needs (after within above mentioned option you enabled Mobile Data and, if needed, Data Roaming).
I don’t know how to see the exact band which is being used. We discussed this in another thread. Unfortunately, BroadMobi doesn’t publish its documentation. Maybe someone can find this info in the code of the driver. I haven’t looked.
I was going for a fully offline install i.e. install dictionaries locally, with localhost dictionary protocol (RFC 2229) server, and the dictionary client (command line and GUI). (The point of the offline install is twofold 1. works with slow, flaky or non-existent internet connection 2. the privacy benefit of not sharing my word lookups with the internet.)
Works more or less. In the GUI the output is annoyingly slightly wider than the screen. That’s with the sidebar disabled, since otherwise it’s never going to fit.
One thing that I couldn’t work out is how to get the GUI to ask the server to search all dictionaries. This works at the command line (by default). This is functionality of the dictionary protocol (specify * for the dictionary) but the GUI always seems to have one dictionary selected for use.