@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.

I just read through this post and want to add that lately, I have that exact issue on my Volla X (24.04-1.2 stable). I'll test the script and report back. In my case this goes hand in hand with not being able to receive calls. I can initiate calls, but it takes around a minute until a call is established (until the ring sound).

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

@jrgood78 I have had this on other devices after an INCELL screen replacement, more recently a OP 6T. The screen works in Android but not on UT. You could try going back to Android, making sure everything works, then reinstalling UT and see if the screen is picked up. BTW, INCELL is a type of screen that is cheaper and more hard wearing than more expensive OLED screens. They are not as vibrant colour wise than OLED screens and if the fingerprint reader is under the screen, that usually won't work with n INCELL screen replacement.

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.

@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.

@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 ?

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

Nur als Info. Aktuell ist der OP8T port "auf Eis gelegt". Der lief zwar recht gut unter Focal, aber machte echte Problem mit Noble. Da Focal quasi vom Tisch ist, macht es wenig Sinn einen Port dafür offiziell zu veröffentlichen, der nicht zukunftsfähig ist.