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

I downloaded the SDK Platform Tools and got it on my phone. The following command: In the terminal "adb reboot fastboot" and I am in the bootloader. [image: 1780662434586-handy.png] When I give the command "Fastboot OEM Unlock" the following message appears: [image: 1780662860936-terminal.png] Who can help or has an idea

@Keneda The grid-scale 20 issue is still present (5.6.2026) in stable 24.04 and daily version. Did I miss something?

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

@wally I did this to switch from my RN9P running 24.04 to the NP1 running 26.04. I simply replaced the /home/phablet/.local/share/history-service folder from one device with the one from the other. No problems at all.

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.

@ChromiumOS-Guy agree with you and @keneda on apt usage - any naive usage of apt is very dangerous. Can't agree on sending pictures with sms (mms is the word), it works out of the box if wifi is disabled (that is, only cellular network is used).

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

@gpatel-fr Oh, wow, I would have never thought of checking after a restart... Let me just link that here: https://forums.ubports.com/topic/12289/changing-message-sound-requires-restart

@ubuntushop said: Why not just fix the problem.? You mean instantly ? How could that happens ? This sure will be fixed, but be patient, this is not a trivial task to maintain and fix such an OS with so few Devs involved...

Please use pure English on forums, use deepl if you need translation. And avoid double posting. And you should go on Google play site if you search for a number to reach them. I don't know it.

@PhAndersson said: the Pixel is able to get its time from the traditional GSM networ My memory is a bit dim on the subject and it's all hearsay anyway, however I remember I was said otherwise. Sorry to not be more precise however my meter says that I posted 563 posts in 9 months, so I finding precise details in the answers I got in all theses threads is not an attractive proposition. It could be that the Pixel is able to save clock and this ability was lost on more recent phones. @PhAndersson said: use your phone as alarm clock when you travel not sure it's a huge priority - there is an obvious workaround: do not stop your phone during the night.