@ChromiumOS-Guy Thanks. I will try soon.

@PhAndersson My knowledge of apparmor is basic unfortunately. In particular, interaction with dbus is something I never looked at before UT, and bluetooth and network management with apparmor is totally unknown to me. Yes my suggestion of using network bluetooth was not very well thought out, I was believing that maybe there was special in associating the two, as if there was a right called network_bluetooth. My bad This said, there is something that bothers me in your log: it suggest that there is a denial in the sending FROM the server (the systemd service) TO your app. Usually when a sending is denied, it is the sender that is lacking rights. So following this idea, it could be the system itself that is missing a configuration. However, see above, I have no idea how rights are managed for the bluetooth services. Maybe all that is needed is to add an apparmor profile for the obexd executable, but often the obvious solution is wrong. Note that if you want to test it, there is no need to turn your rootfs r/w, with overlay or bind-root you can 'add' stuff in read only directories. Sorry not to be more specific, but going deep in system administration takes time and concentration and I'm currently in other stuff.

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

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

@DJac I don't know what you ordered and what you received so I can't have any opinion on that. Well, I'll post again the possibilities I see: 1) the hardware you got is defective 2) the hardware you got is functional, but there may be several submodels of the phone and the new camera is not 100% compatible with the previous one. 3) something else was damaged when the phone did fall. 4) there are problems with the repair. Whatever the reason, if you asked for the exact same model that was included in your hardware and you got another variant, the vendor has made a mistake and you can ask for a return.

@gpatel-fr after thinking about it i think i would side with the others .....im talking about the equivalent of including the bootloader in any linux or windows install ....currently you must bring your own bootloader .....very not typical also all source code is verifiable ...i do think your concerns are unjustified ....however they are valid concerns

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

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/

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

@yuu-ä3 System settings offered the upgrade and unwisely I applied it only to find the phone more-or-less bricked. After a few false starts (see my posts) I was able to restore 20.04. My advice: DON'T TOUCH 24.04 on OP6 or 6T until there is an announcement about the port (Unless you are able to contribute to the porting work)

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

@HarryBass note that in the issue I linked to, there was a mention of using instable (bleeding edge) to fix the problem. However you may risk other problems using instable, of course.

@lduboeuf Will do, thanks.

@gpatel-fr Well i turned the phone off all night and this morning the battery showed up in the bar and it can access the settings.. i d turned the phone off multiple times yesterday but it hadn't helped.. i ll just consider this some mystery.. thanks for the support anyways

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!

@pparent No, it doesn't use a popup. After clicking that field another page does open. I do agree, I too don't see why this should fail. Its not a special function. It might have been simply bad luck or rather bad timing. Maybe the requests had not been synced to this client but my laptop already had them. But I decided to ask anyway, just in case you might have had an idea. So I guess lets not worry about this.

@pparent As I like it so far I'm going to do my best. It's quite a challange and I like challenges even if they are hard... EJ

@Keneda The site won't allow me to create an account to log in, wether that's by design or a bug, I don't know. The forums are the main part for me.

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