Successful Reflash to Byzantium


For my use that will be excellent but really it should just remember what the user has chosen i.e. choice stored persistently. My choice to use Terminal shouldn’t be forced upon anyone else.

What is 80% of what though? This has always been confusing to me (even in amber).

Are you saying that somewhere it displays the charge percentage and that displayed value never goes above 80? If so, I think this is going to confuse users.

If you are saying that 100% is defined as 80% of the actual capacity of the battery then that is reasonable but some users may want to override that i.e. trade-off to gain time between charges at the cost of total battery lifespan.

1 Like

I was referring to charging of the battery being automatically stopped at 80% full. I’m probably wrong, and confusing this with one of /e/OS’s stated goals.

I’ve only charged once since flashing Byzantium; when I noticed that the red light had gone off during charging, I observed the charge was at 78% or so (which I interpreted as battery discharging slightly after charging stopped).

I’ll observe more closely at the next charge and see if it definitely behaves that way. I don’t see anything in the Power settings about limiting charging.

EDIT: @irvinewade, Charged again today. Red LED went out at 85% (That’s 85% according to the indicator), but the phone continued charging just fine. PowerStats shows battery capacity at 100%, i.e. healthy.

1 Like

I don’t think it ever did? :open_mouth:

Hence the portion of the text you quoted that says “as before”.

Ah, I interpreted it as “it does not persist anymore like it did before”, sorry :smiley:

1 Like

I’d like to see your Librem 5 output of:

This should significantly help to @Marts (on how to proceed from …) as well.

I meant “same as before” or “just like before.” I could have been clearer, I guess. :wink:

linux-image-5.16.0-1-librem5/byzantium,now 5.16.3pureos1 arm64 [installed,automatic]

1 Like

I got this update today. Sweet!
Nice work, phosh developers! Now we can set a more complex password.
:slightly_smiling_face: :+1:

Keyboard symbol, lower left:

Keyboard opened on lock screen:

Changing user password still allows digits only:


You can presumably change your password with the passwd command.

Based on past (bitter) experience though from other users, I would recommend that you create a second user to log in as (as backup in case you break purism) and make sure that it can sudo and enable the SSH server - so that you have a way to get in and fix problems if things go pear-shaped.

1 Like

What about the “Password should be 6 digits” directions in the screenshot above, and the digits-only keyboard?

I suppose that would only mean I can’t use that particular GUI setting to change the password in the future once an alphanumeric one is created in the terminal…? (Unless and until the GUI is updated.) But no other issues with going alphanumeric?

1 Like

Well, we should probably lift that restriction now that phosh can handle alphanumerical passwords :wink:


@dos, what’s the situation with changing user name “purism” to something else? Is that still not advised/possible?


I’d like to confirm following:
glxgears -fullscreen
Esc key to exit. Please post here your output after minute or so, as today is very good day for Librem 5, I guess again:

actually expecting average of +/− 140 FPS per second.

purism@pureos:~$ glxgears -fullscreen
733 frames in 5.0 seconds = 146.512 FPS
866 frames in 5.0 seconds = 173.064 FPS
891 frames in 5.0 seconds = 178.113 FPS
897 frames in 5.0 seconds = 179.223 FPS
882 frames in 5.0 seconds = 176.303 FPS
882 frames in 5.0 seconds = 176.184 FPS
875 frames in 5.0 seconds = 174.919 FPS
866 frames in 5.0 seconds = 172.967 FPS
878 frames in 5.0 seconds = 175.449 FPS
888 frames in 5.0 seconds = 177.509 FPS
885 frames in 5.0 seconds = 176.899 FPS
874 frames in 5.0 seconds = 174.614 FPS
862 frames in 5.0 seconds = 172.314 FPS
867 frames in 5.0 seconds = 173.383 FPS
880 frames in 5.0 seconds = 175.909 FPS
878 frames in 5.0 seconds = 175.543 FPS
861 frames in 5.0 seconds = 172.063 FPS
873 frames in 5.0 seconds = 174.549 FPS
879 frames in 5.0 seconds = 175.751 FPS
884 frames in 5.0 seconds = 176.724 FPS
890 frames in 5.0 seconds = 177.821 FPS
883 frames in 5.0 seconds = 176.437 FPS
910 frames in 5.0 seconds = 181.863 FPS
879 frames in 5.0 seconds = 175.762 FPS
X connection to :0 broken (explicit kill or server shutdown).

1 Like

Thank you @amarok! Let us patiently wait what @amosbatto have to say (explain how this happened and what this means). Just great! Thank you Purism so much!

1 Like
  • Notification messages are displayed on, and can be swiped away directly from the lock screen.

Very convenient.


  • Notifications can also be swiped away directly from the app drawer/home page.

Does presence of “notification message(s)” include very nice blue LED light slowly pulsing? I think I registered this briefly but not sure at this moment.

The blue LED appears for some items, e.g. software updates available, software updates installed, etc., but not for actions like completion of a screenshot. Probably calls and messages received also activate the LED, but I haven’t noticed.

1 Like

I just tested setting and dismissing an alarm in Clocks.

The repeating buzz/vibrate sounds at the requested time, the blue LED pulsates, the notification message is shown on the lockscreen if the power button is pressed, the notification message can be swiped away from the lockscreen, but the alarm cannot be turned off without entering the unlock code, opening the Clocks app, and stopping the alarm from there.

Bit inconvenient…not optimal.