Yeah, we should probably have an entry in the context menu to force some app into being marked as mobile friendly.
Meanwhile, you can copy its desktop file into ~/.local/share/applications/ and append
X-Purism-FormFactor=Workstation;Mobile;
which should make it appear on the mobile friendly list.
I don’t quite understand where to find its “desktop file.”
About the toggle on the home screen, in my opinion it should be removed. Nobody will install an app unless they want it, and are willing to work around any adaptation limitations. If it doesn’t play nice, they’ll either adjust the scale or uninstall the app. [EDIT: Disregard. I had forgotten about docking/convergent usage.]
My 2¢ [clink, clink].
BTW, I take it that screen lock codes are still digits only, is that correct?
And is it now possible to change the user from “purism” to something personal? Or will that just create problems?
Thanks.
Usually in /usr/share/applications/
I have some dozen of apps on my phone that I usually use in docked mode, but that aren’t adaptive. They do however still have some basic utility when launched on phone screen. I don’t want them to clutter my launcher by default when I use my phone as a phone, but I do want them to be available when docked and on demand. I find form factor filtering very useful.
Didn’t work, even after reboot, if I understood what you meant. No big deal…I’ll just add it to favorites.
I totally spaced this aspect. Yeah, it makes sense to have the toggle, then. Maybe we’ll get an option to not use that feature later.
Thanks!
You can completely disable the filtering with:
gsettings set sm.puri.phosh app-filter-mode '[]'
and go back to default with:
gsettings reset sm.puri.phosh app-filter-mode
I think most of the improvements to the Camera app are being made in Byzantium.
I think that having an encrypted root file system out-of-the-box is only an option if running Byzantium.
There are no doubt dozens of functional changes that I am unaware of as I am still running Amber. I guess that now that @amarok has reflashed, the pressure is on me. 
Byzantium seems a lot more advanced, so I’m sure you won’t regret it. I’d be interested to hear about your experience, especially if you plan to preserve data and settings from Amber.
Plan? Hmmm. I’m still bogged down with Pwnkit on other computers so haven’t had time to reflash the Librem 5. I think my plan will be: wipe / start from scratch (as you did) and then just redo the 1000 things that I have done by way of customisations, settings, installs (which I can redo from my notes).
I am thinking of going LUKS (unlike you) so I suspect that preserving anything from Amber is close to impossible anyway (other than that the uSD card - not encrypted - should work ‘as is’ - so I am only referring to preserving anything on the eMMC drive).
I probably would have chosen encryption…if I had remembered that I had to specify a different image. (Or if the documentation had indicated that.) I suppose I could do it over. Now would be the perfect time.
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).
Some observations:
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.
Additional observations:
, but now include lots more apps than in Amber. [EDIT: This is only if "Show incompatible applications’ is enabled. Otherwise, normal time to populate.]
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.
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.
I don’t think it ever did? 
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 
I’d like to see your Librem 5 output of:
This should significantly help to @Marts (on how to proceed from …) as well.