Successful Reflash to Byzantium

I think it’s an (optional) argument to the flash script.

Exactly.

I don’t want to have to do this three times - so if I ever want encryption then the reflash from Amber to Byzantium is the time to do it.

I believe that all portable devices should use encryption, not because we face state actors in our threat model etc., but just because portable devices are more readily lost or opportunistically stolen. At the very least it is a courtesy to my friends, relatives and colleagues whose contact details will appear on my phone (at least until the calling and emailing apps support LDAP).

1 Like

Some observations:

:slightly_smiling_face:

  • GNOME Weather picked up my location and displayed the forecast.
  • GNOME Maps found my semi-precise location (within 30-ish meters) even though I was indoors, sitting by a window. (I didn’t notice how quickly it happened, as I only checked Maps after some time sitting there.) [EDIT: It finds a fix very quickly upon opening Maps.]
  • Default sound quality for phone calls seems pretty good on both ends. (unscientific, brief test, talking to myself on two phones)
  • Quite a few colorful backgrounds can be selected from Settings. You can also add an image of your own.
  • There are more options available in the Settings than with Amber, including various toggles for docked use.
  • Superimposed dialog boxes have controls to dismiss them without having to minimize the app to swipe away.
  • Display has 5 resolution (scale) settings.
  • Automatic date/time works instantly on connection to network.

:slightly_frowning_face:

  • Initially bluetooth started scanning as soon as I turned it on, but now it seems to have stopped working, and turns itself off when closing Settings. Still shows as enabled in quick settings area. My Android doesn’t see the L5, either. [EDIT: A reboot directly from the BT settings screen brought back functionality.]
  • Settings>Privacy>File History & Trash doesn’t scale to screen (in default resolution). Some of the other settings panels take a second or two to scale, sometimes.
  • Still no UI option to remove unwanted Online Accounts cloud links (i.e. Evil Corp 1, Evil Corp 2, etc.).
  • In the Store, it’s necessary to enable “Show incompatible applications” to find all matching software when using the search function. Some of that software likely adapts to the screen even if it’s not officially labeled “compatible.”
  • Timeout for screen lock still doesn’t obey my chosen interval. (Screen locks immediately when display blanks or power button is pushed.)
3 Likes

If you both want to flash it encrypted, I suggest doing so with this branch https://source.puri.sm/Librem5/librem5-flash-image/-/merge_requests/13 as it should generate a new encryption key (the default passphrase is still 123456, that doesn’t change). Though you’ll need to make sure that you have cryptsetup-reencrypt and uuu installed, and unfortunately the flash needs to be run as root. This avoids the lengthy process seen in the other thread.
I did so this past weekend, and it worked for me.

On the device you plan to flash from, this is what I did, and be sure to follow the instructions it gives you once the image is downloaded.

git clone https://source.puri.sm/angus.ainslie/librem5-flash-image.git
cd librem5-flash-image
git checkout luks-flash
sudo  ./scripts/librem5-flash-image --dist byzantium --variant luks --skip-cleanup

At the moment yes, but phosh 1.15 should be available for update either tomorrow or the day after, and this adds a keyboard button to the lockscreen numberpad to open it up. Don’t change your password to non numeric until you see that in the lock screen.

4 Likes

Additional observations:

  • The software categories (i.e. curated, and presumably, adaptive apps) in the Store take a long time to populate :slightly_frowning_face: , but now include lots more apps than in Amber. :slightly_smiling_face: [EDIT: This is only if "Show incompatible applications’ is enabled. Otherwise, normal time to populate.]
  • I think charging is capped at 80% by default now. [Edit: It’s not.] :slightly_smiling_face:
  • Terminal-style keyboard seems to be the default in the terminal now, even if “English (US)” (dependent on your region) has the active button enabled. :slightly_smiling_face:
  • Selecting “Terminal” keyboard in other apps applies system-wide (as before), and does not persist after reboot (as before). :neutral_face:
  • Calendar is very nicely adaptive now, which it wasn’t in Amber. :slightly_smiling_face:
  • There’s haptic feedback on power up now. :slightly_smiling_face:

:+1:

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:

D’oh!!!
Changing user password still allows digits only:

4 Likes

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:

5 Likes

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

3 Likes

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).
purism@pureos:~$

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