@foxx This is getting very off topic, politics are not that related to the issue. I never said that you cannot use your camera, it just has to be interfaced through Halium. You can quickly make an app with Qt that captures frames from the camera, and maybe use the Qt Networking framework to broadcast.

@foxx said in How to use camera via terminal v4l on Pixel 3A:

Canonical tried to push Unity using pretty useless Ubuntu Touch, when actual problem was on hardware manufacturers' incentives layer to make unified drivers, so some organization could make actual linux, not gnomes and package managers without underlying layer.

That's why they wanted to become the manufacturers themselves and started crowdfunding Ubuntu Edge, which would have been an awesome device but it never reached its funding target.

Probably government could oblige manufacturers to provide drivers , which should comply with some POSIX

People don't understand any of these. Politicians not only don't care about privacy, standards etc, but are busy pushing those stupid laws forbidding end-to-end encryption, I wouldn't expect anything from them.

The world is far from perfect and it will always be like that, so you have to make compromises.

@foxx How does termux work better? Even if you have a rooted device, you still aren't using the familiar GNU/Linux stack. Termux is still an emulator, it modifies the syscalls, and you don't have access to every directory.

In UT you can do everything you would on a desktop Linux distro but it is more difficult, mainly due to relying on hardware abstraction.
The only solution to this is using an upstream kernel with complete driver support. This is however a much harder task than the already hard porting process. PostmarketOS does that, and that's why almost none of their devices work fully.

All manufacturers should mainline their device drivers but none do, instead they use ancient downstream (often bugged) kernels so they can release their product quicker (and cheaper).
There are exceptions such as the Pinephone(s), which have full mainline kernel support, and allow using devices such as camera in the same way as in a normal Linux device.

In my view, Ubuntu Touch does solve a problem. It is the closest you can currently get to a normal GNU/Linux system, while retaining the phone's intended functionality (telephony, camera, etc).

@foxx You can only see cameras through Qt, see this post for more details.

@Charly Snap doesn't make sense for these small standalone utilites. Also fdisk doesn't exist as snap and rsync packages are only some outdated third party programs, which I would never install.

@LITTLEFisky It could be something with your environment, have you tried using installing with another Linux distro (e.g. Ubuntu)? It can work from a VM or live USB.

The "cannot read data from undefined" seems like an issue reported from JavaScript, that's why I'm saying it's an issue on your environment.

@Charly The first time you open the shell (through ssh) it says "the system has been minimized", which was done to reduce the rootfs size. You can use these programs under Libertine or run a local build of them (preferably statically linked).

@LITTLEFisky I was able to install UT on an UsU unlocked device (see this post) without an issue. Have you tried another distro? The errors seem to be unrelated to the installer.

@arubislander IIRC, all desktop apps based on a framework other than Qt are currently uconfined, but Mir 2 should fix that (see the discussion around the problem for uWolf).
If it were unconfined just to access the filesystem directly (without content hub), it would use the separate read/write access policy.

@mr_growl If you disable requiring password to login (just swipe to unlock), it will also disable encryption.

But just running the fastboot command will work (if it throws any error, it likely means your fastboot build is broken and you'll have to use the official one from Google).

@mr_growl Why don't you formtat through the built it in option in TWRP or even better via fastboot: fastboot format:ext4 userdata? (the partition name may differ)

Also, when the block device shows up as dm-something it is encrypted.

@pparent It's open source: https://github.com/fredldotme/vscodium-click-packaging.
From quick look it bundles all the needed libraries in the click and is unconfined, so not ideal,

@pparent VSCodium has been working since 16.04. I think it's in the store.

@evilgenius use the waydroid helper app from the openstore.

I think Lomiri's developers are testing it on bare metal, no VMs. You might want to ask on https://t.me/UBports_Lomiri .

@domubpkm uWolf should support DoH, it may even be default. For other apps, the standard linux way (edit /etc/resolv.conf) will always work, and this is what the script you are referring to does.

@Simmonz If you are familiar with mtk client you can unlock the bootloader from there too since Volla devices have mediatek chipsets.

@techwryte It has already been ported to raspberry pi 3/4. See rootfs builder repo. You can build the raspberry image yourself, or grab an older image . I think the default rootfs would also work if you keep the fat partition.

@oldpaint That's the default for Ubuntu 20.04, the new 24.04 images have gcc 13.

@ANDROID2468 There are images for pinephone, pinetab and pinebook. However both pinephone pro and pinetab 2 are supported, so probably the image works for both pro and non-pro?
An older (2023) image is certainly for both phone versions: https://gitlab.com/ook37/pinephone-pro-debos/-/jobs/5124896891/artifacts/download?file_type=archive .