It’s already there - new phones ship encrypted. I’m not sure whether changing the encryption key after reflashing is documented somewhere (as otherwise you get the same key as everyone after flashing the same image), and ideally we would like to have it automated anyway, but all the pieces are there now in byzantium (which is already the default when reflashing).
1 Like
One more thing … I always get annoyed that the screen comes on when you plug it into a dock or power cord. You intuitively press the power button to deactivate the screen, but then it comes on again … I am not allowed to press the button - that wears me out: D
Please add the option … “Show display on connect - on/off” under power settings
2 Likes
Forgot to mention on thing that bugs me daily. Lack of auto-brightness. You can turn it on, but it seems to sway around somewhat randomly. At present it’s not useful that I can tell.
This is mainly an issue as, I spend a lot of time inside and keep the phone brightness low when doing so. If I forget to turn up the brightness before going outside it can be really hard to see enough to login and do things
2 Likes
Yes. To do things like … adjust the brightness. I got caught out by that the first time I took the Librem 5 with me when I went out (mid-summer Oz, blinding sun). In situations like that, voice control would be nice. Maybe Librem 5 v2 for voice control and in the meantime better auto-brightness. Or maybe overload the function of the volume control in some way??
1 Like
- the heating problem isnt solved during decrypt password entry, which is especially dangerous because the l5 switches on on plugin; not giving the password should switch the phone off after a while
- the status bar on top doesnt come down on swipe but on click; same thing with the arrow
- typing is terrible cause the spacebar is near the up arrow; space doesnt end number entry which would be helpful; setting the cursor pos in the url entry is near to impossible
- the screen scrolling is still not smooth
- i didnt find a way to switch off the lock screen - during testing this gets anoying
- i cannot mark text in the browser instead a menue pos up but i cant choose something
- in the calculator the kbd os up while the calculator already has one
- manuy dialog arent designed for the screen and sometimes i m stuck becuse i cannot close it
This is written on the L5 
4 Likes
Touch the globe icon and then “Terminal” in the keyboard to switch to the terminal keyboard layout and it has arrow keys for moving backwards and forwards?
I wish it defaulted to “Terminal”. I guess that’s another minor gripe.
Probably not the answer you want, but it is possible for you to alter existing keyboard layouts and/or add new keyboard layouts. That’s the beauty of open source. You aren’t stuck with someone else’s design choices.
i tab where i want the cursor which works most of the times but not in that bar. i dont want to change layout, navigate and so on. i just wonder what happens there: the balloon is in the text, if i drag it it jumps like hell…
altering the kbd layout isnt an option cause i like the spacebar exactly there
the arrow should move but i doubt i can do so in limited time 
Yes, this annoys me, too. The workaround is to minimize everything and swipe the dialog box away, then maximize the original screen. On top of that, many dialog boxes don’t have an “X” to close them, even if you could see them on screen. (Is this some bizarre design choice of app developers?)
(This is not Purism’s fault, of course.)
I second that!
how do you minimize everything and see dialogs?
the ts lags alot, often the letters dont come through
Tap the ^ key, bottom center.
Ah - thats not “minimize” for me but it doesnt always allow to kick away dialog, sometimes i needed to kill the entire program
1 Like
I would like to refine my comment however: I wish the user could configure what the initial keyboard layout is (and I would choose “Terminal”).
I don’t actually want to impose my choice of layout on anyone else as the initial layout that ships with the phone. That can stay as it is.
1 Like
Is the naming scheme correct? I installed the latest update 5.13.16 and after reboot, uname -r still says 5.13.0. Shouldn’t it say 5.13.16 ?
That’s correct - this is how kernel packaging in Debian works to track ABI compatibility. Debian additionally adds the patch version to the description, which is something we could do as well (but don’t at the moment)
Librem 5:
Linux evergreen 5.13.0-1-librem5 #1 SMP PREEMPT Thu Sep 23 11:20:41 UTC 2021 aarch64 GNU/Linux
Debian amd64 box:
Linux debian 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 GNU/Linux
1 Like
Interesting. If I run
dpkg --list | grep linux-image
I get
rc linux-image-5.11.0-1-librem5 5.11.15pureos1~amber1 arm64 Linux 5.11 for the Librem 5 and its devkit
ii linux-image-5.12.0-1-librem5 5.12.2pureos5~amber1 arm64 Linux 5.12 for the Librem 5 and its devkit
ii linux-image-5.13.0-1-librem5 5.13.16pureos1~amber1 arm64 Linux 5.13 for the Librem 5 and its devkit
rc linux-image-5.9.0-1-librem5 5.9.16+librem5.2 arm64 Linux 5.9 for the Librem 5 and its devkit
ii linux-image-librem5 5.13.16pureos1~amber1 arm64 Linux kernel for the Librem 5 and its devkit
So now I see since there is only one entry with 5.13.0 that I run 5.13.16pureos1~amber1
Strange… this makes uname -r almost useless.
Now about the above my L5 seems to have 4 kernels installed. Do I need them all? Can I remove them safely? How?
Your log says you only have two kernels installed. Using grep made you miss the legend
purism@evergreen:~$ dpkg --list linux-image-*-librem5
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-============================-========================-============-==========================================
rc linux-image-5.11.0-1-librem5 5.11.4pureos1+gitlabci1 arm64 Linux 5.11 for the Librem 5 and its devkit
rc linux-image-5.12.0-1-librem5 5.12.2pureos4+gitlabci1 arm64 Linux 5.12 for the Librem 5 and its devkit
ii linux-image-5.13.0-1-librem5 5.13.16pureos1+gitlabci1 arm64 Linux 5.13 for the Librem 5 and its devkit
rc linux-image-5.9.0-1-librem5 5.9.16pureos0 arm64 Linux 5.9 for the Librem 5 and its devkit
rc means Remove/Conf-files - so the package is uninstalled, but some config files may remain until you apt purge the package.
1 Like
Oh, OK lets see:
[purism@pureos ~]$ dpkg --list linux-image-*-librem5
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±============================-=====================-============-============
rc linux-image-5.11.0-1-librem5 5.11.15pureos1~amber1 arm64 Linux 5.11 f
ii linux-image-5.12.0-1-librem5 5.12.2pureos5~amber1 arm64 Linux 5.12 f
ii linux-image-5.13.0-1-librem5 5.13.16pureos1~amber1 arm64 Linux 5.13 f
rc linux-image-5.9.0-1-librem5 5.9.16+librem5.2 arm64 Linux 5.9 fo
So If say I want to remove 5.12.0 should I do
apt-get purge linux-image-5.12.0-1-librem5
if I understand correctly. Thanks.
Yes, although you don’t need to remove 5.12 manually - it’s going to get removed automatically once we switch to newer kernels, as IIRC only two most recent kernels are kept installed by default.
2 Likes
Does Purism have basis testcases? Some script hammering the kernel / library for functionality?
I tried a v4l test script i wrote long ago which immediatly runs into errors. The v4l module seems to misbehave which would explain that some cam apps (cheese for example) dont work.
How is testing done @Purism?
There’s no stress testing, but we have a basic test to check that hardware is in working order. The software still has known deficiencies that need to be fixed first, so testing hasn’t been prioritized compared to that.
What does “ending number entry” look like?
This cannot be altered in the keyboard, but the arrow will eventually respond to a swiping motion instead of a click, solving that problem.
I had this nearly done, but camera work took over. Sorry.
2 Likes