@rocket2nfinity said @oldbutndy The one from the Devices page, or the manual instructions from his page https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_Nord_N10_5G/Global_BE86AA/Q/OnePlus_Nord_N10_5G_Global_OxygenOS_10.5.7.zip Yes, that is the one I had found & merged the OEM T-Mobile BE2028 info into, then renamed it from global to the T-mobile name, and installed it (No more T-mobile logo at boot) & booted OK, but still boot loader locked, and requesting token.

Uhmm.... I'll be honest, I don't know how to take your last few posts. I'm not sure what you are trying to tell me.

@libremax Indeed, Ubuntu Touch is cited as a potential operating system available, provided that porting is considered. To be continued...

@delijati Noble (24.04) does not work with the Xiaomi Mi A2 yet. Tried it many times and still no luck. Stay with 20.04 stable and you will have a good experience.

I think the biggest difficulty for average users is not using Ubuntu Touch itself, but the procedures for unlocking the bootloader and, in most cases, downgrading the Android version, which requires studying and mastering procedures that are often quite complex, depending on the type of device. Indeed, officially supported, pre-installed and partner devices (Volla, somehow Fairphone and soon - Brax3 in particular) allow Ubuntu Touch to be used ‘out of the box’. Ubuntu Touch was designed in the spirit of ‘Ubuntu’, i.e. very simple, user-friendly and intuitive to use, at least for basic tasks. Many Ubuntu Touch users on Telegram threads have no IT skills and are very happy with UT. It all depends on the specific needs of the users. Most of the apps available in the OpenStore are great and very easy to use, but it is true that the catalogue is currently very limited, and WayDroid offers compatibility with certain Android apps, but unfortunately not those covering proprietary IoT applications. I would add that since 2020, when I started my experience with Ubuntu Touch, I have noticed a clear improvement in the performance and overall stability of the system. From this point of view, the gap between Android and iOS has narrowed considerably. To conclude, I personally use UT as a second device (holidays, leisure time), and am extremely happy with it!

@delijati Do you want to setup your RasPi as an OTA server for UT? Or are you looking to set up your RasPi to receive OTA updates?

Anyway in the long run we will hopefully switch to Wayland when Mir2.x is included in the system, and then the OSK will be handled differently that it currently is. Not sure whether the 24.04.2 branch will include Mir2.x .

@PhAndersson Right, while searching for another problem, I just stumbled on something that looks like an answer. there is in this directory: /etc/dbus-1/system.d a bunch of files configuring the authorizations for dbus; for example (taken for its brevity): cat com.lomiri.UserMetrics.conf <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <policy user="usermetrics"> <allow own="com.lomiri.UserMetrics"/> </policy> <policy context="default"> <allow send_destination="com.lomiri.UserMetrics"/> <allow receive_sender="com.lomiri.UserMetrics"/> </policy> Now, it's sure that the system.d directory does not seem the right place for a user level service. At the moment I have no clue where a file configuring the dbus authorization for the org.bluez.obexd service should be created. But I tend to think that creating one is the proper thing to do because I don't see a reason why obexd should be forbidden to send message to its agents. It should be allowed whatever security reason there is to block general message sending. So this could be the proper way (TM) for your application to run confined.

v0.2.0 is released Changelog: Battery status sync: added kdeconnect.battery support. Multimedia controls (MPRIS). Theme settings: new Settings page with Bright/Dark/System themes and consistent readable palette across surfaces/text. Notification improvements: IDs standardized to strings with backward-compatible conversions on receive; new “keep on remote devices” toggle (skips cancel sends);. Find‑My‑Phone: ringing support with notification and volume boost. UI polish: service install prompt simplified (“Daemon is installed.”) and layout fixes.

@lduboeuf done https://gitlab.com/ubports/development/apps/lomiri-calendar-app/-/issues/260

Hello and thank you for your answers. My main objective is to get rid of Android (except the obvious parts for the Halium container) on my device. Also I really would like to run close to mainline, but this is more a dream than reality. With the addition of snap and easy integration of waydroid, I can seamlessly migrate over and use most of the snap programs I already use. I know that I cannot do an "apt install whatever", this is a little sad but I know where it comes from. I did not find some of my preferred programs in the Open Store or they where severely outdated (Element). I am aware that the Open Store uses click (I think was the name) packages, and is therefore another format other than deb or snap. Regarding the installation. The installer does not state which version will get installed. This is what stopped my attempt, as is would like to know which version gets installed if I where to click on install The installer mentions a specific stock Android version (for Halium) to be installed, which implies that 20.04 would get installed. Then again, my target version is 24.04 and I am not sure if my device could be upgraded to reach this version. I got the impression, that this is not quite sure, which I hoped to get confirmation here for. I have no problem first installing the older version and then upgrading to the recent version, but would only do that if it is certain that it is possible.

Updates since my last post: I disabled more useless kernel features I had to add some code to keep the pstore feature working The WLAN and the Bluetooth driver are now compiled into the kernel The artifacts.zip now contains a vbmeta.img file to simplify the installation The repo now includes a script to disable the ugly "Orange State" warning. customizelk.py patches the lk.img from the stock ROM to just return from the function which displays the message. This also avoids the additional 5sec wait time. Please note that this is purely cosmetic. Have fun, Kai

@gpatel-fr Sad! OnePlus usually had superb hardware for the price. Well, at least there is a decent lineup of OP phones that can still be ported.

@HarryBass said in Delivery of incoming text messages (SMS) randomly: thread as (hopefully) solved? you can turn the thread into a question and mark it as solved yourself. I don't know why there is this feature in this forum but it's how it is.

@Sander - Wow. Thank you so much!! This is amazing!! I never thought to try to tap somewhere else. This is absolutely awesome and makes using the terminal a pleasant experience, even on a phone! Thanks again for sharing this gem!!

@ezst036 I see nothing in the ofono log relative to a failed send. So the problem must happens in a previous layer - very possibly in lomiri-messaging-app itself. Using journalctl -e and searching for lomiri-messaging-app could be more interesting. It is just dawning to me that you never specified from where are coming your pictures - photos you take when creating the mms or files that you got by another way ? if the latter, it may be that the file format is not known to Ubuntu Touch. When you create a photo using Ubuntu Touch it's a well-known format that UT has no problem to process.

@tigermoth Best to look it up in the documentation that your provider makes available. You can't try it out like that. If your provider only offers VoLTE for voice calls, then that's really the only option to make calls, and VoLTE does not work on the Pixel 3a.

@Moem Thanks for the info and for the hard work of the contributors.