@Linus67 Well, there are always questions, it's not in dry cloths yet! The OS is on the phone, after an auto-boot after the installation was completed, Ubuntu ran a system update. After completion, a reboot was executed.... Then / and since then the phone has stayed hanging at the point after every boat (picture) [image: 1780725868182-boot.png] Text (It couldn't be better): The Bootloader is unlocked and Software integrity cannot be guaranted. Any data stored on the Device may be available to attackers. Do not store any sensitive data on the device Visit this link on another device: g.co/ABH PRESS POWER KEY TO PAUSE BOOT No matter what I press, the quiet button and the start button or just the start button... this picture always appears ?? I once had a screen with Ubuntu and various options when I plugged in the USB cable, but I couldn't replicate this event. Any idea? Event. Android back on and the whole thing from the beginning? Did I miss something??

@mariogrip Hello Marius. As the NP1 doesn’t have a fingerprint reader, I’d like to temporarily disable the login password. I’ve tried everything in Settings/Security/Lock & Unlock to change how the device is unlocked or to change the password, but nothing works. Is it the same for you? The UI returns wrong passphrase... Even change password doesn't work.

@AdFundum did you find a command that works from the terminal/adb shell? If so, does that command work if you make your app unconfined? Its possible that UT does not have an app armor policy that fits your use case, and that's the cause of your problem. From the list of policy groups I cannot see anything that would allow a confined app to change the background image. https://docs.ubports.com/no/latest/appdev/platform/apparmor.html

@kugiigi I noticed with this method DNS querrys are still visible on WiFi router if you Use DNS Blocklists in your WG config If I run a DNS leaktest on UT it only show vpn DNS but if I inspect my DNS querrys in router the router can still see the DNS querrys so something is not working with this method

@Futura For the record I don't remember having seen this problem on my FP5.

@laaglu said: Probably the issue can be marked solved, I do not know how to do that / who can do that https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved Read carefully first and second posts.

@uwahl I guess you missed git issues are not resolved so still present

@magnusajber No, but there are things you can do. Have a windows PC to hand with Lenovo Software Fix installed. This is the easiest way to return the tablet back to stock Android and the instructions in the fix tool are helpful and intuative. The device has to be the 3Gb/32Gb or 4Gb/64Gb version. The 2Gb/32Gb version is stuck on Android 10 (Android 11 runs very poorly on it, UT runs a lot better). UT can be installed on it, but it involves doing other things to get Android 11 on it. Fastboot is good, it means you can run the device through the UT installer again assuming you had Android 11 on the device. On the installer tick all the boxes (wipe data etc). Leave the device alone and let it do it's thing. Moving it while downloading UT and pushing it to the device may cause an issue due to a loose connection.

@Vlad-Nirky Thanks for the reply! Yeah, my understanding is this generally works smoothly. I just wondered if my issue was a one-off, or uncommon but sometimes encountered. I suspect my database is just screwed up somehow. pragma integrity_check didn't find anything wrong, but that's as far as I got. Anyway, not looking for support, just thought I should see if any others experienced something similar. Congrats on your NP1! And 26.04, very cool!

@fischer.poco Du musst das Handy kurz mit Wifi verbinden um den OEM unlock zu aktivieren. Mit Wifi sollte der Schalter nicht mehr inaktiv sein.

@gpatel-fr Yes, like I wrote before, now it works. Thanks for the info with Gitlab!

@dl8aax This should be possible through python with fpdf and use this python inside your qml app.

FP 5 24.04-2.x Daily Using as daily driver, calls all working well. Had problem with screen going dark a week or do back fir a few days but that's been it of late. For a development build with just daily available it been very stable if that makes sense. Does still have both versions of Morph showing at present which is a little awkward to use.

@Moem No, please do.

@Zer0 said: I can post again Sorry for the hiccup

And some pics: [image: 1780593457929-photo_2026-06-04_08-50-30.jpg] [image: 1780593457952-photo_2026-06-04_08-50-38.jpg] [image: 1780593457970-photo_2026-06-04_08-50-42.jpg] [image: 1780593457991-photo_2026-06-04_08-50-46.jpg]

Hallo Pparent, thanks for the hint

gpatel-fr said: I realize belatedly that I did not think of giving some advice about the problem of returning back to a newer version once the goal of revert to a previous one has been achieved. It would be easy to imagine that it will be easy, but it's not as straightforward as following the usual procedure. When going from 1.1 -> 1.2 -> 1.3, history of these upgrades was recorded. If the phone is rudely returned to 1.1 and the user asks it to update back to 1.2, it will look at this history and conclude 'I have nothing to do !'. So the way to go in this case is to delete all this history in the lower part of the phone screen by swiping to the right and pushing the red trash button for all theses updates, and then the normal update behaviour will be restored back to normal.