@MrT10001 Thank you. So I am less anxious. We'll see tomorrow what happens

@nielsbasjes said in Enabling MAC randomization: Is this the right direction or is there a simple, clean and reliable way of enabling MAC randomization. If you don't know about it, @fredldotme is a pillar of UT, certainly the second ranked; so if he don't advise for a 'simpler, cleaner' solution, you can assume that there is no obvious one. Having the rootfs read-only is certainly a solid part of the core tenets of UT.

Here would be my current starting script for wayland is there a way to do better to solve some of the problems? @fredldotme @klh #!/bin/sh # Input method (probably does nothing as it is for X11 normaly) export GTK_IM_MODULE=Maliit export GTK_IM_MODULE_FILE=lib/aarch64-linux-gnu/gtk-3.0/3.0.0/immodules/immodules.cache # Prefer Wayland export GDK_BACKEND=wayland export DISABLE_WAYLAND=0 export OZONE_PLATFORM=wayland export QT_QPA_PLATFORM=wayland export XDG_SESSION_TYPE=wayland export WAYLAND_DISPLAY=${WAYLAND_DISPLAY:-wayland-0} export GTK_USE_PORTAL=1 export DCONF_PROFILE=/nonexistent export XDG_CONFIG_HOME=/home/phablet/.config/signalut.pparent/ export PATH=$PWD/bin:$PATH dpioptions="--high-dpi-support=1 --force-device-scale-factor=2.75" gpuoptions="--use-gl=egl --enable-gpu-rasterization --enable-zero-copy --ignore-gpu-blocklist --enable-features=UseSkiaRenderer,VaapiVideoDecoder,ThreadedAnimation --disable-frame-rate-limit --disable-gpu-vsync --enable-oop-rasterization --enable-threaded-compositing" sandboxoptions="--no-sandbox --start-fullscreen --kiosk" waylandoptions="--ozone-platform=wayland --enable-features=UseOzonePlatform" exec ./opt/Signal/Signal $dpioptions $gpuoptions $sandboxoptions $waylandoptions

Status: Base: Ubuntu Touch 20.04 (Halium 9). Goal: Enable the fingerprint sensor. Action: Extracted proprietary binaries (service + libraries) from OxygenOS 9.0.12 and placed them in /vendor. Fixes: Manually created libtls-padding.so (via a symbolic link to libcrypto.so) and .rc/.xml files. Blocker: The service fails to start (ps -e returns no result). Logs (dmesg, logcat) no longer show avc (SELinux) or "not found" errors. Manually starting the service (/var/lib/lxc/android/rootfs/vendor/bin/hw/android.hardware.biometrics.fingerprint@2.1-service) immediately results in a segmentation fault. Question: "Is this segfault a known incompatibility issue with Halium 9 on the SDM845? Is there a kernel patch or an alternative driver I need to use?"

@Thomas I presume your choice between a de-Googled Android and Ubuntu Touch should revolve around whether you want Ubuntu as your Operating System on the phone or not. We take security seriously and we're slowly catching up, see encryption of your data being a thing on 24.04.

I could cross-build now before it was amd64 insted of aarch64 but did not start because lib: libgtksourceview-5.so.0 missing

@arubislander Regarding containers not having access to the internet: It might be the device is using "Paranoid Android Networking" in the kernel, stemming from Android, which limits use of sockets to a special group ID. To device maintainers wanting to support LXD, you will want to check whether CONFIG_ANDROID_PARANOID_NETWORK is in your kernel tree (simply grep recursively for it) and if so, set CONFIG_ANDROID_PARANOID_NETWORK=n in your defconfig. I've since fixed this on the FP4 and verified working networking on the FP5.

@Moem The banks in the UK are really pushing you to use their app. For example if you log in on a browser, it will push you to authenticate with your app on your phone or tablet. The banks have close the vast majority of counters and now run a service (no cash withdrawals) where a van goes from community to community on set days for all banks to cater for those who don't online bank. Likewise if you do need a big cash withdrawal (i.e over 1000 euros) then they question you like you are a naughty child. (Think of Greta Thunberg saying "how dare you withdraw your own money, how dare you!). Then to work you now have to have an authenticator app and I have to have the M$ authenticator, no choice. If I don't have it I cannot get into works systems! The UK is really going to rack and ruin......

@t12392n [image: 1762793186208-image20251110_174327764-resized.jpg] [image: 1762793188172-image20251110_174405414-resized.jpg]

Sorry ...not about 24.04-1.1 A follow up of my second daily test , thumb down ,receiving messages last an update , well ,it worked after first reboot upon new daily revision , but stop after second reboot !!? encounter boot freezing in bootloader unlock warning stage ,same happend one month ago before daily stopped receiving messages. Strange , plugged the phone to pc , to reinstall stable , forgot usb setting was in usb Tethering(here french=Partage de connection usb) , suddenly it picked up all those ''not received'' messages !!?!! Tried to reproduce it , could not . Back to stable , receiving messages. Note ; daily here = 24.04-1-x , stable=24.04-1.0 one+ n10 Looked at logs a little , honestly not knowing where to look exactly , wont share any , but you can suggest or ask for some !