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

@pparent said in French ID app interoperability.:

This is no longer relevant at this time:

hmm, it did not take long for this beast to resurrect:

https://www.lemonde.fr/pixels/article/2026/01/22/le-gouvernement-n-a-pas-renonce-a-acceder-au-contenu-des-discussions-sur-les-messageries-chiffrees_6663627_4408996.html

@domubpkm said in Working hours - Agenda:

Still strange not being able to set the minutes.

if the code is storing begin work in an integers variables called businessHourStart and businessHourEnd, there is no way that you will be able to register minutes since there is no variable called businessMinuteStart... Some code refactoring (and UI) would be needed for that.

@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):

certain types of D-Bus requested are blocked by AA (such as AuthorizePush

I have actually taken a look at the ubtd code and as I understand it AuthorizePush is a method defined by ubtd for obex.

Looking at the Ubuntu touch bluez code with some dismay, it seems that this method is defined quite officially to allow the obex daemon to send data to a client, squarely fitting your use case, so why is there no apparmor policy for that ? As a wild guess, it looks like an oversight by Canonical that was forwarded by Ubuntu Touch - or even an oversight by Debian, forwarded by Canonical, forwarded by Ubuntu Touch. Maybe a bluetooth policy should exist.

Or maybe it already exists ? looking at usr.sbin.cupsd in my Kubuntu 24.04 installation, I see a string 'network bluetooth'. Maybe adding that to your apparmor profile could strike gold ? Absolutely wild guess of course

@hacknorris

I think that the silent mode only refers to the phone. For the slider, it's explicit: it is for the phone ringing. For general sound level, the hardware buttons are working in the browser.

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

@DJac

Sorry but getting back to my 4 points, the only one were this is not working because of a hardware problem is 2): the new hardware is not compatible with the driver.

Android is (probably) not like Windows where when you pull a device from your computer and plug another in its place the system downloads another driver from the Internet: phones are not devices where you can plug and use new hardware.

So if the 2) point is correct, the driver installed with Android matches exactly the old camera, and not the new one. Since UT uses the Android drivers, I don't see a way forward with this camera.

@domubpkm

I'm afraid that the values are defined as integer in the code.

@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):

prevent me from publishing it on the OpenStore

Not sure of that actually, there are applications with a big red scary warning, that do not prevent them to be published.

Also, IIRC the idea on phone OS is that the app is shipped with granular authorizations policy and the user grant these rights or not. I don't see why you could not ship a granular apparmor policy for the app if you wanted to do so.

@projectmoon said in Trying to revive 'ubtd' (Bluetooth file transfer):

I think any spawning of external processes that are not inside the app's ~/.local/share directory require unconfined.

If 'running an external process' means 'activating a service' via dbusk, not 'spawning', it can be done from confined I think. I did not check how exactly is working this application.

@ChromiumOS-Guy said in More Apps Please!!:

did you need to config bindmounts or did it just work?

no bindmounts necessary; flatpak --user does not use any service.

I did some fiddling at some point with the (local) mime configuration but I am not sure it was needed, it was when I was trying to make it work using the extracted debian packages, it was really difficult and using nix solved it.

I have tried mostly Kde apps, they need all

export QT_FONT_DPI=280

and some

export GALLIUM_DRIVER=d3d12

To test some apps, the initial dialog boxes are the most annoying since there is no keyboard.

The thing that stunned me was with Okular (the Pdf viewer) when I realized that I could zoom by pinching the screen, while it was the desktop version ! that's why I am most interested in Kde apps, they are more mobile oriented because of Plasma mobile I think.

@ChromiumOS-Guy said in More Apps Please!!:

also for keyboard thats an easy fix you need to include a cache file look to ufirefox/uwolf for example on how to get gtk apps to use maliit

I thought first of compliing a Ubuntu touch driver for each Kde pack but it's not obvious to learn to compile various stuff for UT, especially at things that no one other than a core dev would touch. It would be a cleaner fix though

@PhAndersson

Great ! have happy file exchanges with your car

@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):

AuthorizePush

this is denied; I never dabbled much with Apparmor, and certainly not with UT; I notice with some dismay that there are no apparmor logs and I have no clear idea on the better way to enable them unfortunately.

For now, I have only one positive thing to say: in the application that worked with 16.04, the template was set to 'unconfined'; while this is not generally a great idea, to advance your testing maybe it could be worth a try to add it to the apparmor profile ?

@pparent said in More Apps Please!!:

I made a pull request to correct that

Unsure what you wanted to correct, I hope it's not to publish Chrome on the Ubuntu Touch store, Google may object to that

@DJac said in changing camera - not recognized:

i will try lineageOS

If the problem is my point 2 (different hardware working but not 100% compatible) it could work since it may use a different driver version, since as far as I know this OS use native drivers (not Android) to access hardware. If it's another of the 4 possible problems I enumerated, nothing you can do at the software level will change anything.

@ChromiumOS-Guy said in More Apps Please!!:

i will be continuing development of xdg-desktop-portal backend

Yes more support for freedesktop standards is exactly what is needed for these needs.
FTR I tested a bit using crackle to install flatpak and running it with --user, it can install quite a few flatpak apps, main problems are the virtual keyboard, file access (that's where your effort would be great) and clipboard (could be solved by the future updates for wayland...). I was able to start a game of Gnu chess and play a few moves

@MrT10001

I don't quite remember what the installer did when I flashed my phone (happy memories... not ) but from browsing v2/checkDownloads.ts I'd say that the installer is saving stuff in a sub-directory called 'download' from the current directory when it was launched.

@ezst036 said in How can I troubleshoot broken SMS?:

the text side of my text messaging.

as I understand it, if ofono is working and sms is configured, sms get in; mms have another, distinct configuration. Also, I have understood recently that UT has a lack in the media configuration that could explain that files are not played correctly (nothing related to MMS per se, just that MMS have sometimes very particular formats), and of course UT don't receive MMS behind Wifi. Quite a few wrinckles.

@developerbayman said in Ubuntu Touch on Redmi Note 9:

eliminating this annoying step

actually there was an effort to do that at least for one port (not Xiaomi)

https://github.com/ubports/installer-configs/pull/299

I know because I actually argued that it could be dangerous. Devs judged that my fears were unjustified, however the PR is still stalled because 3 approvals are needed and one of the code owners has something else to do it seems. So things are advancing at a snail pace on the installer front. Unsure if it will be committed one day, unsure if this solution will be extended to other ports (you'll notice that there were considerations of antirollback protections that could be a blocker for other ports).

@DJac

this is an extract of dmesg yes ? not looking good at first sight.
However, should I understand from your previous post that you reinstalled Android (8) and that the camera app crashed ? If the cam don't work under Android, there is little hope that it will work under UT since UT use Android drivers.