Granted it's not exact for what one might have gotten on their device, and you can't limit it to last 24 hours. But its's as reasonable a rough overview of changes as the aforementioned GitHub search query, I think.
AFAIK, nobody is working on support for Wireguard currently. Most device kernels also don't have support for it. I guess there is a way to do it only in user space, but I am not sure what all the requirements are.
If you want to open feature requests about what needs to be done to support it, and perhaps provide some pull requests for them, I'm sure it would be greatly appreciated.
Over in the Sailfish universe we have SeaPrint (by me)... so if someone wants to port it, feel free to get in touch.
No CUPS dependencies, strictly speaking no dependencies at all other than Qt, but poppler is needed for working with simpler printers.
qtubuntu-camera is a piece of software that allows Qt applications to use cameras on Android devices through hybris. Adding these new values means that Qt applications can use them. It does not mean that they will start using them automatically.
There needs to be a change done to the camera-app software, which uses qtubuntu-camera, to support the new flash and exposure modes. There is a Merge Request filed to enable more flash modes: https://gitlab.com/ubports/apps/camera-app/-/merge_requests/154. However, there is no merge request filed to enable more exposure modes. If you like, you can help us test and create these changes as needed.
As @jezek and @lduboeuf suggested this thread is very long and far to hard to follow. So I will lock it. A fix has been posted so please as asked try it and report issues in the normal way and let's see how it goes.
@thomas-k8s Nah, you lose the native XMir windowing with that. I'm more partial to how we did it in the days before libertine's release back in 15.04 (still chroot, not libertine's proot which seems more restrictive, but using XMir with matchbox-window-manager to provide some semblance of window managment)
Nowadays, I'm looking into something similar, but using the Gentoo Prefix in place of the chroot, so it runs unprivileged. Obviously will generate a LOT of I/O so if anyone else goes this way, I highly recommend running the bootstrap as far as it will let you using an NFS root mounted into the home directory somewhere (mine is .local/system) and then copy it to device and finish the bootstrap using an NFS-mounted TMPDIR (because bootstrap will only let you go so far before portage tells you that it needs root permissions for some reason when bootstrapping straight to an NFS shared folder)
@emphrath No problem, I've tried a lot of things that most people would find "useless" under ubPorts while working to make my trusty Nexus 7 a portable workstation. I've been tempted to add WINE to my setup again, but I don't want to deal with setting up an i386 chroot running on the device (since LXC doesn't function correctly for me, can't create LXC containers, oddly the Android container works fine).
In case I didn't mention it previously, yes, it requires qemu-user-static installed and you have to have an i386 chroot to install and run WINE/32.
@povoq thanks for the reply. I figured it would take time, I prefer the UT setup or navigation, the slider. But not going to lie the battery and speed of lineageOS is something to work towards to. Id imagine if UT has the same speed and battery life as lineageOS, our operating system would be a lot more desired. I think this is why a lot of people get into linux in the first place, bring back life to a old system.