Ok, it was much easier than I believed. I just had to
select vcard from folder_id;.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):
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
Ok, it was much easier than I believed. I just had to
select vcard from folder_id;.Alas, my Nexus 5 didn't get to celebrate it's symbolic 10 year anniversary, I can't get it to boot any longer.
While waiting for a new UT device I have to 'go Lineage' for a moment. And I was hoping to find a way to import, directly or indirectly, the -salvaged just in time- contacts.db file into Android.
Any ideas? Can for instance syncevolution be run outside of UT?
When typing inside the address bar of morph-browser an URL key is added to the keyboard layout.
My fingers don't like the shrunken space bar, and my mind isn't always immediately aware of the sudden layout switches.
One solution would be an upstream change at maliit/keyboard. But the corresponding Github ticket has so far not generated a lot of enthusiasm.
So, I'm looking for a workaround. I already tried temporarily mounting root as rw, and then soft linking the non-standard layouts (Keyboard_en_email.qml, Keyboard_en_url, Keyboard_en_url_search.qml) to the standard one (Keyboard_en.qml) inside the /usr/share/maliit/plugins/com/ubuntu/lib/<lang>/ folders. But this didn't help.
Any other advice?
@davenothere According to this link, you should still be fine data-wise even if 3G bands will be phased out: https://www.frequencycheck.com/carrier-compatibility/zLtEl/google-nexus-5-lg-d820/cricket-wireless-united-states
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.
I went through the remaining QA flagged topics (~ https://github.com/orgs/ubports/projects/25), or at least those my knowledge and device allowed me to test, and added my findings for RC 2021-W10 and Nexus 5 in the according Github threads. All seems more or less fine.
Some oddities I encountered turned out to be present already in OTA-15 (System Settings freeze when resetting Launcher, Morph pop-up dialogs out of screen) and some I could not reproduce so far (my home Wifi network temporarily not showing up in, and the Telephone app freezing once at call hang-up).
I would like to share these 3 things though:
after upgrading from OTA-15 to 2021-W10, my GhostCloud app somehow lost my NextCloud account details (~ "No account available yet. Please add an account to continue.). Indeed, strangely my NextCloud account wasn't in my System accounts (could it be it wasn't there before?). Adding it did not change the GhostCloud message however. And, even more strangely, when moving back to OTA-15 my GhostCloud app disappeared from the Launcher, and I can't even find it again in OpenStore... I must be missing something (sleep?)...
When connecting my phone to an external monitor through Slimport, and then disconnecting, the indicator menu icons got stretched out (and only restarting could change this). This doesn't happen on OTA-15.
Switching back to the stable channel and pausing the Ubuntu Touch v13 download, I afterwards didn't manage to continue the download (pause button was greyed out and update was shown as "0 bytes of 452.0 MB"). To continue the download, deleting cache+config+data of System Settings app was needed (in UT Tweak Tool). This doesn't happen when I pause the RC 2021-W10 from within OTA-15.
@cliffcoggin Sure. In the past I had already at one point replaced the battery with a new one, without notable difference in battery life. But, maybe back then a software issue was at fault, whereas now it is indeed the battery itself. So, I might indeed try out the other spare batteries I have.
@flohack Thanks! That's great news. Judging from Github commit timestamps, and apart from your latest setting modification related to CPU idling, the port however doesn't seem to be on top of anyone's ToDo list. And according to your related forum post some issues still remain. Do you nevertheless believe the port will land soon? And is there anything I, as end-user, can help out with to speed up the process?
@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.
@cliffcoggin Thanks! As far as I know there are no replacement batteries on the market with a significantly higher capacity than the original one (2300mA). I believe this is the battery you are referring to. It's also just 2450mAh. Wouldn't you expect a similar battery life in case of similar battery capacities?