@AppLee said: On FP5 after a fresh reboot I got down to 2.3GB just tried with my FP5 and build 288, htop reports 3 Go with some resident apps, and 4 Go logged-in on Gitlab with either Morph or Firefox.

Hi @Mario.CH Thank you for your clarifying post. I understand and am in 100% agreement with your point. Perhaps I should/could have worded my point a bit differently and open to suggestions for articulating this or any disclaimer (as when this is posted for public, it will be important to clearly set the correct expectation for new people to still do their own research and verification!). I think the value of the sheet is to see, at a high level, all the possible devices and to decipher the easier ones to self unlock and cell bands they use (versus ones that may have more complications or to avoid the specific variants that cannot unlock for example). To help narrow the choices to a few good ones. Of course, before deciding and purchasing a specific device on the used market, each person needs do their own research! The spreadsheet is not a substitute for that and the spreadsheet may not be 100% correct nor will it have all the specific details. Just high level important ones). I hope that helps clarify my thoughts with the function/purpose of the spreadsheet and I'm open to how to best articulate. Thanks for your input and thoughts.

A new release of muttum have just been released. Main changes are: The user interface has been updated to better fit with mobile and dark style. You can give up a party to reveal the solution English dictionary has been updated Note I've split the gitlab repository to build and publish the package for the OpenStore. It's available on : https://gitlab.adorsaz.ch/muttum/org.muttum.muttum-lomi

@shengchieh I noticed something in your reply. When you tapped "OEM unlocking" the toggle that says "On" is for the Developer Settings as a whole. If you scroll down further on that page there should be an option specifically for "OEM Unlocking" that you need to toggle on

@contrarian This link from the device's UT page appears to be working https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_Nord_N10_5G/EU_BE89BA/Q/OnePlus_Nord_N10_5G_EU_OxygenOS_10.5.7.zip

@DawsonR2 Looks like the artifacts I used were deleted for being out of date because there was a new commit which does update to 24.04.2 so that's really nice. But it looks like gitlab did not allow the artifacts for that one to be uploaded because they were too large https://gitlab.com/redstar-team/ubports/lenovo-tab-m8/lenovo-tab-m8/-/jobs/16054313222 so let's ask @k.nacke, is there anything you can do about this to upload the files somewhere else, or maybe split them into 2?

@gpatel-fr As the subject of Gigaset being the same as Volla devices has come up before on the Forum it may be worth restating a couple of things. The UBports community can and will do everything possible to help and assist with installing, fixing, developing and running Ubuntu Touch on all the Volla devices listed. And yes we do have a good and close working and sponsorship arrangement with Volla. Regardless of how similar Gigaset hardware is or the OS on them is or is not to that on Volla devices, Gigaset devices are not supported by the UBports Installer or Ubuntu Touch as the OS. If you try and install UT on Gigaset devices you and you alone are responsible for that and any issues that arise. By all means use the Off Topic section of the Forum to discuss the pros and cons of doing so (that is what OT is for) if you wish but please keep it out of the main Forum it just confuses things. Last point there are no "official members" on the Forum. The Forum is for everyone who use and works on or develops anything to do with UT. It is a great and thriving community and everyone is welcome to take part. The UBports Foundation as a charity is a legal entity that as such does have "official" parts the Board of Directors, Membership Committee and the Board of Trustees. All made up by members of the UBports community.

@brenno.almeida I submitted the issue on GitHub, sorry if it's not well done, it's the first one I've done hahaha

It would be especially important for national alerts since the missing part could contain key instructions or location details. Hopefully this can be improved in a future update.

New comming 2.5.0 version As requested in the application comments, a folder page as been added Also the following improvements have been done: Remove utilities pages from the page selector Fix adding RSS feeds not working Change weblate repo, Thanks to Danfro, use now https://hosted.weblate.org/projects/ubports/launcher-modular/ Update French translations, thanks to Libermax Update Dutch translations, thanks to Heimen Stoffels

@whoami_phone said: the screenlock simply cannot read the default intended brightness value before storage decryption this seems most likely to me. For your information, the main dev for this feature is not everyday on this forum, and especially in this period - however when the holiday period is finished I think you will probably get expert advice, have some patience. If for some reason this does not happen, you could try to ask on the still open issue for home encryption. (the fact that it's still open could be an oversight or it could mean that it's still somehow a work in progress)

@mihael said: I tried to find a previous post about this but no success - so forgive me if this was asked before: It seems that the app camera can only access one of the several cameras on the back of the device - is this a known limitation? - is there a workaround? - a fix? - a work in progress? The Camera Test app from open-store (https://open-store.io/app/camera-test.jakub snowrider does not identify any other back-facing camera. Devices that I checked and found this issue on: Oneplus N10, Nothing Phone 1. I’ve noticed the same limitation on some devices. It may be related to how the OS exposes multiple rear cameras to apps. Hopefully, camera support will improve as device-specific integration develops.

@Vlad-Nirky They're all just the usual XDG DIR's. "/home/phablet/*" Nothing unusual

@lduboeuf thanks for the tip. There is minimal information in the commit log but that's not unusual sadly.

@CiberSheep said: I didn't understand your answer In the case this means 'I still don't understand', the OONI says that sites like ubport's ones are not targeted by themselves, but are subjected to bans because technically blocks can't target single web sites but whole IP blocks. It even says that most collateral damages are on Cloudflare, the CDN used by Ubports web sites, since Cloudflare gives access to huge number of different web sites using a few IP addresses. So the idea I was floating boiled down to use 2 IP addresses for each ubport site, one for the current Cloudflare setup, one with another Cdn (a Cloudflare competitor) so that IP mix-ups with football pirates could be less likely. Of course this is easier said than done.

@Vlad-Nirky Thank you very much for this helpful information. It actually should have been my job to find this post. I had exactly the same workflow for killing the Calendar app. I’ve since managed to fix it without reinstalling UT. In my case, downloading the app to the Downloads folder and re-registering it brought the Calendar app back. phablet@ubuntu-phablet:~/Downloads$ click register --user=phablet calendar.ubports 1.2.0 After removing all the leftover Calendar files with rm -rf ~/.local/share/evolution/calendar/ rm -rf ~/.config/evolution/ I was able to reconnect everything properly again. (Mailbox and Nextcloud) Many thanks to everyone for your support on this sunny Sunday afternoon!