[MyL5] Australia/New Zealand

Normally I wouldn’t. Due to habit with my existing phone I expect I would put it on charge at 20%.

It is however difficult to avoid the occasional shut down due to low power unless you can watch the phone like a hawk.

perhaps the issue would be partially mitigated by having an audio alarm system ON that says “help ! i’m dying !”


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. :slight_smile: 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 :grin:

1 Like

Today I tested … Telstra

Country: Australia
Provider: Telstra
Modem: BM818-T1
Calls: in and out, OK
SMS: in and out, OK
Data: OK (slow)

SIM already activated in another phone. SIM moved temporarily into the Librem 5.

Various APNs offered but this time I was smart enough to check the APN on the original phone before removing the SIM, so I knew to choose telstra.internet, which was one of the APNs offered.

If only I knew how to see which LTE band is being used for data. However it should be using B28 (the band that is missing on the -E1 and -A1 variants).



Seems to work well enough. There were a few hurdles to overcome (like the fact that I don’t really know what I’m doing) but the internet had most of the answers.

I do wonder what will happen if I were on a call when the battery became ‘low’.

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).

@irvinewade, I added your info to the wiki. Thanks.

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.


Today I tested … shortening the unlock PIN.

If I recall correctly, changing the PIN via Settings / Details / Users enforces a minimum length of 6, which doesn’t really work for me, particularly while I am stuffing around a lot.

From root, setting the PIN with passwd purism seemed to do the trick. I didn’t even have to reboot for the lock screen to pick up the new, shorter PIN.

I did take a copy of /etc/shadow before doing this, just in case … :wink:

My battery warning script does not seem to be working after all. :frowning: Works when run interactively from an ssh shell. Does not work when run from cron. When run from cron gives

aplay: pcm_write:2053: write error: Input/output error

(I’m using the aplay command to play a WAV file.)

It is the same user executing the script either way.

1 Like

Hi, I am about to order a Librem phone from Aus. Can you tell me what the option for “Modem” is or should be? Sorry I am very un techy. Also what is the wait time appox?


Tested OK for calls / text / data on Vodafone’s network and on Telstra’s network. I haven’t got around to testing on Optus’s network yet, although I am not expecting problems.

I don’t really know. Not short. The answer may become clearer in a week or so. Purism has to clear a global backlog of, I would suppose, thousands of phones.

1 Like

Thanks Irvine,
I will order the phone and look forward to its arrival.
Cheers Gerzy

1 Like

Today I tested: Dictionary

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.


More comprehensive testing:

uSD card: SanDisk Ultra C10 U1 512 GB

read test with: hdparm -t /dev/sda
write test with: dd if=/dev/zero of=test bs=1048576 count=200 conv=fdatasync

(speeds in MB/s meaning decimal MB, not that it makes a huge difference)

With the card in a USB 3.0 card reader connected to a USB 3.0 port in a middle-of-the-range x86 computer …

read: about 85 MB/s
write: about 37 MB/s

With the card moved into the Librem 5 …

read: about 7 MB/s
write: about 10 MB/s

read speed rises to 11 - 12 MB/s if tested with

dd bs=1M count=200 iflag=direct if=test of=/dev/null

where test is a 200 MiB file on the uSD card. Create with:
dd if=/dev/zero of=test bs=1M count=200 conv=fdatasync


Redoing the test of the eMMC drive but using only dd and using a 600 MiB file …

read: about 57 MB/s
write: about 22 MB/s

That’s better!


Did you rate your experiences (UX) here?

Today I tested: Contacts Importer

My starting point was 200+ contacts as schema valid LDAP data in LDIF format.

I thought the easy way to do this would be: import as a new address book into Thunderbird, then export address book as VCF, then scp the VCF file to the Librem 5, then use Contacts Importer.

And that did basically work. Certainly saved a lot of error prone typing!!

On the other hand, the original content wasn’t perfect and, as expected, the GIGO principle applies.

Other comments:

  • Thunderbird produced VCF 4.0 and I wasn’t sure whether Contacts Importer would support that version, but it seemed to go OK.
  • Company contacts, as opposed to individual contacts, all imported with a unique name of the form system-address-book:pas-id-uuid and I had to key in the name by hand (but that’s not so important - I was more worried about error prone typing in phone numbers). The actual problem crept in during the Thunderbird step.

I’m declaring victory on that.