@libremax said: The printing system is not included in the Ubuntu Touch images due to a lack of space for the root filesystem on many device models. Work is currently underway to be able to increase the size of the rootfs. Is there a way to determine if my device (Nord N10 5G) might have enough space for larger root filesystem ?

@domubpkm to handle imported files differently in messaging app, would be a task to solve there. tedit can only hand over a file to messaging app. What that does with the file is defined there. tedit has no control over that. I added the share option to read only mode page too. I simply didn't think of that yet. (Build here: https://gitlab.com/Danfro/tedit/-/jobs/14268879889/artifacts/file/build/aarch64-linux-gnu/app/tedit.danfro_3.6.1_arm64.click)

@gpatel-fr I seemed to see that at the end of booting the smartphone (before I entered the pin code) when switching to stable, the screen showed the correct time (H) and very quickly went to H-2.

@brenno.almeida welcome

@lduboeuf said: did you reported the issue to the porter ?. I plan to do so when I have time.

@Keneda Sometimes, such severe restrictions can also lead to a huge surge in innovation and creativity.

@E-Z-Tux idk the chip manufacturer for this tablet but research this: if Mediatek: bootrom bypass & sp flash tool if Qualcomm: EDL mode & Download tool

@oldbutndy yes that is the desktop version .....i desperately want to give you something to test but the ut version is still just too broken im going for EXACTLY the same thing in both desktop and UT versions ....that is not easy as you would think ...i promise soon i will have something for you ...im actually excited your excited

@projectmoon Can you do journactl -r | grep 99captive_portal ?

@pparent Many tries later - with a failed speechmessage too - unexpected: sending a picture works fine up to now. Later I will send you a screencast of the failed picture insert before. Btw: installing the screencast App failed... AppStore always returns to the green "installieren" button!

PS: Now I use a skript (systemctl --user stop greenline.service) and use it with a Desktop link. This works perfectly for my WhatsApp usage. This way, I can stop all WhatsApp data usage completely if I don’t need Greenline for a few days.

No, no change. I'll open an issue; that'll be more efficient. I've started the French translation on Weblate.

@MrT10001 hey, i was able to unlock my bootloader i found a guide on XDA to edit my registories on windows regarding USB ports. Usb3fix.txt FOR ANYONE READING THIS. PLEASE SAVE THOSE LINE IN A TEXT FILE AND CHANGE THE EXTENSION TO .bat AND THEN RUN IT AS ADMINISTRATION. then i could run the unlock.cmd file and it ran flowlessly. thank you for your help.

@tidip https://forums.ubports.com/post/80091 You can also use the msmDownloadTool to completely reset everything, if you suspect you had a bad flash at some point. See the forum, same category as the above link.

@steffend I understand now why my search for Pixel9a on the forum didn't get anything, it because of the space... and that's why I don't include it to make searching easier.

you need to go to settings and set your usb to tethering ....there is your internet connection it should just work when you plug it in and connect ...if im understanding you correctly?

One of the most interesting parts of this for me is the focus on mainline kernel support. A lot of alternative mobile/Linux devices struggle long-term because of outdated vendor kernels and limited maintenance. If the hardware can stay close to upstream Linux, that could make the device much more sustainable over time for the UBports community.

@ikoz i see, so it is that easy on public hotspots in general unregardless of the os i use, that uhh sucks

Since this is not a device question, I will move it to Support and mark it as a solved question.

Thanks! I dived into the issue a bit more, and it seems like the problem lies in the default mapping in /etc/subuid file. The first OS regular user created usually has the assignment 100000:65536 in /etc/subuid. I decided to assign the values (231072:65536) from the user that succeed with the podman pull command to the user with previous 100000:65536. With the new values, podman (and therefore, clickman) runs without issues. I don't see any conflict on the default range assigned, but definitely that new assignment seems to fix it. Hope it helps for those that run into it