@k.nacke Sorry, there were snap connections that I had not set, so git-confined could not access the ssh keys. I have corrected it now and it works. I have successfully cloned the docs repo.

Did you try : https://open-store.io/telegram ?

Hi @Rondarius. Thanks, but that's overkill for my use case.

@Wheeling-Pigeon Indeed. And either 9S/Pro/India...All share the same motherboard hardware&firmware + same built image...

Not the only one. I was also surprised plugging in my usb-c headphones did nothing. Generally it should be noted that this is about headphones with an usb dac. There are also adapters and headphones that pass through analog audio over the usb-c connectors, and those apparently work. These are the open issues that have been reported so far: https://gitlab.com/ubports/development/core/packaging/usb-moded/-/issues/6 https://gitlab.com/ubports/development/ubuntu-touch/-/issues/1912 https://gitlab.com/ubports/porting/reference-device-ports/halium13/volla-phone-quintus/volla-algiz/-/issues/3

@johndoe said in using Ubuntu Touch as o/s for IoT devices with RPi/Rockchip: A specific mobile DE, you could also look into, is Phosh. But it will probably not work with your remote access software. Whereas Lomiri is known to work with VNC at least. And it is in the debian repo's as @Vlad-Nirky already mentioned.

@lduboeuf Running /usr/share/ofono/scripts/get-tech-preference outputs Technology preference: nr. Running /usr/share/ofono/scripts/get-serving-cell-info tells me Radio Access Technology = lte, but I don't know if that helps

@domubpkm Thanks for the info! calls are my biggest issue, they just keep calling all day every day.

@kugiigi ah! Keen eye. I assumed it was set to automatic, but it was indeed set to manual. I've reset back to auto and am now able to see the different channels, so I am checking for updates. I'll report back once it finishes spinning

@oldpaint said in gcc 9.4 compiler in docker images: I thought I would start with the Botan library so I ran the command 'clickable build --libs --verbose' and that provoked a download of the correct docker container for my phone, arm64. I can't seem to provoke a download for the desktop docker container, amd64. I tried 'clickable desktop ...' but no joy. You could try 'CLICKABLE_ARCH=amd64 clickable build --libs --verbose' or 'clickable build --arch amd64 --libs --verbose' in order to specify the architecture. Your architecture should also be defined in your manifest.json file. (The app template should provide a manifest.json file by default. It is maybe under data/. You can read about it here: https://clickable-ut.dev/en/latest/usage.html ) The architecture will probably be whatever architecture is specified when executing clickable (likely arm64 by default).

Had there been an update with volte support being added to UB touch now ? I have a oneplus 6t running 20.4 I think it is. I have us cellular and can't get any mobile calls or data or Anything to work. Since us cellular is t mobile I was hoping there was a way to make it work.

@dobey said in Using apt to install package: the supported way to do that is within a libertine container. Can you elaborate a little more? How to create a libertine container? How to use it to install apt/deb? Edit: found this https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html

@kugiigi Thaaaanks!!! The reset button in the tweak tool did the trick. I did change the edge sensitivity when I was docked so maybe I accidentally change some scaling too.

@RJDan These are mostly specific to the desktop use case but obviously these things will also land on UT, maybe not immediately but definitely in the future.

said in Is there a better browser somewhere?: @Fuseteam could you please give me a clue how to install uFirefox? I downloaded several .click files from builds artifacts and tried to install them with OpenStore, but gives an error "the package could not be installed. Make sure it is a valid click package". As well itried to install the from command line, but there are errors too phablet@ubuntu-phablet:~/Downloads$ pkcon --allow-untrusted install-local firefox.fuseteam_142_arm64.click Installing files [=========================] Finished [=========================] Fatal error: No such file /home/phablet/Downloads/firefox.fuseteam_142_arm64.click, or unknown or unsupported content type phablet@ubuntu-phablet:~/Downloads$ sudo click install --all-users firefox.fuseteam_142_arm64.click --allow-unauthenticated [sudo] password for phablet: Cannot install firefox.fuseteam_142_arm64.click: Signature verification error: debsig: firefox.fuseteam_142_arm64.click does not appear to be a deb format package This is resolved, please ignore the question. Somehow I really downloaded several files corrupted. Simple re-download helped.

@markpousee Your device does not feature on the devices list. What version of UT are you running, and how did you install it originally?

@Keneda So side-loading the xenial apps did work. They start up fine but I have not had a chance to figure out how to get them to connect to my server running torrent yet. It looks promising though.

interesting, all phone clients add trailing slash resulting in accessing something like //remote.php/webdav/Readme.md instead of the correct one /remote.php/webdav/Readme.md got it fixed on proxy