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.

@rocket2nfinity OK. I will look for those. I copied the detailed posts into 2 files to edit steps into numbered checklists, and merge & highlight important details. Trying to ensure I don't leave out a critical step. hopefully simplify troubleshooting failure. Or, if lucky/successful, repeat the process.

@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.

It works To do it on the smartphone with fingers is a little bit fiddly. Then I used the end of pencil with a kind of rubber, than it was easer Thanks again!

How is the Installer progressing to work with Apple Silicon (i.e. M1, M2,M3,M4 and now M5 CPU's) based PC's and Laptops? There are still questions (in one of the Telegram channels) on why devices are not working on Noble when it is available to download on the installer before soft bricking the device. Could Noble be removed from these devices installer until it is resolved?

@DJac Yep! If you want, you could scroll to top, click the gear icon near the blue reply button, Mark as a Question, then Mark as Solved. Helps with forum tidiness.

@muskist I have bought this up with the installer developers as there is some devices where the upgrade to Noble fails - OP6/6T, Lenovo Tab M10 TB-X605F/L, Xiaomi Mi A2 to name three... I know the OP6 and 6T is being worked on. I guess (and I am assuming, dangerous, don't assume) they are awaiting porters to bring the devices on as Focal worked, Noble should work.

here you dont even need to download them anymore you can play them in your browser .....im actually starting to reconsider my holding back stance only by space considerations ....i mean really ...this is my morty... https://playclassic.games/games/nes-games/

@arubislander Ah! Apple issue. Apology completely forgotten.

@pparent going back to this problem, do you still see it ? In a previous post, I said: I have found a 'rogue' app that can reliably hang my phone. for the record, it is the command line tool nix-index installed via crackle. I have absolutely no interest,in this command now, it was just an experiment that turned into a total phone hang, but I was intrigued by this UT killer. So I started on a quest to install and configure systemd-oomd (yes, that's the system that made Canonical's reputation a bit worse). It was a bit difficult since I did not want to use apt, so it was all a game of building overlays mount and setting the configuration by hand. It was not pretty but now it seems to be mostly operational. I'm a bit pleased to see my first experiment come to a success. My UT killer was eliminated ruthlessly by systemd-oomd. If I start the accursed command via ssh, the ssh session used is killed, letting the other ssh sessions running. It I start it via terminal, the terminal is killed. I'm going to use the phone a bit with this config to check that the system is stable with this addition. After that, if you want to test it, I could help you in this adventure, it could be interesting. If this is really useful, it that could be an interesting addition to UT for the next 26.04 iteration. Smooth the rough edges ! fix some of the crashes...

Besides @vlad-nirky and @phandersson is anyone else going to Fosdem?