Ok, it was much easier than I believed. I just had to

• query the contacts.db (I used DB Browser for SQLite) as select vcard from folder_id;.
• select all results, copy and paste them into a text file and save this file as contacts.vcf.
• open this file in Android, confirming that contacts need to be imported.

Mir, Wayland, Lomiri, HAL, Halium HAL, HIDL, libhybris, nuntium... it might be just me, but -and despite your laudable and countless efforts to explain them- my head still spins every time these terms come up. Are there by any chance already architecture diagrams available that explain these components/libraries/frameworks and there interaction? If not, you might consider creating them. Not only to quench the thirst of curious laymen like me, but also to lower the entry threshold for new developers.

Thanks, advocatux!

I had actually already seen that thread and I had already tried to follow the advice given there.

So I tried again, but without too much hope it would now work. But -O ye, of little faith- it did work! The different outcome might be related to the installation of the ClockworkMod ADB driver earlier today (http://adb.clockworkmod.com/), see step 6 below.

For future reference I will list the different steps (as the terms are not identical as in your list):

1. Open Device Manager, fold out "TP-LINK Android Phone"
2. Right click item "Google Nexus ADB Interface"
3. Select "Update Driver" on Driver tab
4. Select "Browse my computer for driver software"
5. Select "Let me pick from a list of available drivers from my computer"
6. Assure "Show compatible hardware" is checked and select "USB Composite Device" (I'm inclined to believe previously only "Google Nexus ADB Interface" was available, and the new device might have come along with earlier installation of the ClockworkMod ADB driver).
7. Select Next, wait for driver installation and close.
8. The device auto-mounts immediately!!!

a boring 3 here as well

If time allows (given the philosophical and more general nature).

As an end user I'm more and more confronted with semi-necessary apps that I can't install on my smartphone (as they are only available for the two mobile OS'es the world seems to know about). It used to be only Whatsapp, and I actually owe UT a debt of gratitude for that, but now I also note increased pressure from utility providers (banks, phone, insurance, electricity) to make use of their dedicated apps. The recent state developed Covid-19 tracking apps could be another example.

How do you experience this? Have you already persuaded some business app developers to open up to UT? And are there reasons to hope for a more UT friendly app future (~ increasing mobile Linux user base, converging app development technologies,...)?

@taiga-woods Thanks. I would indeed want to try out that battery case I referred to. The problem is that I don't find it anywhere. Your sustainability argument is however also very compelling, so I might go for the OISLE battery extension after all. In any case, I will share my experiences, if any.

note to self: RTFW (i.e. rtf wiki) before posting ... the bug trackers are listed at https://wiki.ubports.com/wiki/UBports-Bug-Trackers/da00bef and my 'bug' was already listed here https://github.com/ubports/notes-app/issues/2