Hi,
Here is my first app "Taquin" a simple and classic puzzle game, that I have just published on the OpenStore and the source here: https://gitlab.com/AloysLiska/taquin

Please be indulgent, that's a beginner work, but I would appreciate your feedback on the app, on the code,etc.

QML and javascript were new for me (I have software skill and I mainly developed in C).
To begin with QML, I use : https://doc.qt.io/qt-5/qml-tutorial1.html, and https://mimecar.gitbook.io/qt-course/
And for javascript I use : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide.
And of course I use the UBPorts documentation.

My editor was Kate (default editor of Kubuntu), simple and sufficient I think for a simple app.
When you begin, there is a lot to learn, so I did not want to use something new for me (like Qtcreator or another editor).

For the next version of Taquin, my objective is to allow user to select an image in its gallery.

Enjoy the app (kind of game useful to kill time)!

@Lakotaubp, I fully charged the battery as you said, but it was the same problem, it was stuck in the first screen.

I tried to start the phone on bootloader by holding pwr and vol down buttons, but I never succeed!

I tried UBports installer, but last version 0.1.21 does not work with my FP2, I have the issue:
Fastboot: Unknown error: downloading 'boot.img'...OKAY [ 0.360s]booting...FAILED (remote: bootimage: incomplete or not signed)finished. total time: 0.361s

I add this problem before, see:
How to manually upgrade from OTA-3 to OTA-4 and @advocatux suggested to use the UBports installer V0.1.12.

I launched this version and it finally works!
I had to select manually the device to FP2, because device was not automatically detected. I reboot with pwr+voldown or pwr+volup+voldown buttons several times, after several reboots, it succeed to detect the device, and the update procedure went till the end successfully.

Now I have the OTA 8 and all my data.

Thank you @AlainW94 and @Lakotaubp

Hi,

The docker images, used for Clickable, accumulates on my hard drive and I run out of space!
I run Kubuntu 20.04 on a disk of 120GB, and I have another larger disk for my /home.
Until now I did not care where this images where stored, and I was a bit surprised to run out of space.
Docker images are stored in /var/lib/docker so they uses space on my 120GB disk.
And I have many images:

XXX@XXX:~$ docker image ls
REPOSITORY                    TAG                                            IMAGE ID       CREATED         SIZE
clickable/amd64-16.04-armhf   16.04.5                                        de10b0785b01   12 days ago     3.24GB
clickable/amd64-16.04-amd64   16.04.5                                        46cf1141cef4   12 days ago     3.44GB
clickable/amd64-16.04-amd64   <none>                                         7e758494f183   2 months ago    3.42GB
clickable/amd64-16.04-armhf   <none>                                         6236c98e71a1   2 months ago    3.2GB
clickable/amd64-16.04-amd64   <none>                                         e3075a8131f7   2 months ago    3.42GB
clickable/amd64-16.04-armhf   <none>                                         79e9333e49e6   2 months ago    3.2GB
clickable/amd64-16.04-amd64   <none>                                         0b3ce64ac2a1   4 months ago    3.21GB
clickable/amd64-16.04-armhf   <none>                                         60280ecc7f75   4 months ago    2.97GB
clickable/amd64-16.04-armhf   16.04.5-52e346f1-7f68-4acf-b25a-f909a7f151de   d5a088555e63   6 months ago    3.06GB
clickable/amd64-16.04-amd64   16.04.5-e6f90001-5335-4b61-aaaf-ee27ec05ca9a   f2ae84741742   6 months ago    3.28GB
clickable/amd64-16.04-amd64   <none>                                         5c90fa6d0219   7 months ago    3.24GB
clickable/amd64-16.04-armhf   <none>                                         274d61c78369   7 months ago    2.99GB
clickable/amd64-16.04-amd64   <none>                                         ca2295f385c8   8 months ago    3.22GB
clickable/amd64-16.04-armhf   <none>                                         ac0efb3e90f9   8 months ago    2.97GB
clickable/amd64-16.04-armhf   16.04.4-qt5.9                                  70ee31165bda   8 months ago    3.32GB
clickable/amd64-16.04-amd64   16.04.4-qt5.9                                  020f92dc47d1   8 months ago    3.73GB
clickable/amd64-16.04-armhf   <none>                                         b05354f06d34   8 months ago    3.32GB
clickable/amd64-16.04-amd64   latest                                         221fafae479b   8 months ago    3.22GB
clickable/amd64-16.04-armhf   latest                                         e21dd4f44f87   8 months ago    2.97GB
clickable/amd64-16.04-amd64   <none>                                         b287ba7b39ee   10 months ago   3.16GB
clickable/ubuntu-sdk          16.04-armhf                                    d29e7ad6f85d   13 months ago   2.89GB
clickable/ubuntu-sdk          16.04-amd64                                    534d93e2668b   13 months ago   3.16GB
clickable/ubuntu-sdk          <none>                                         d146e1f7df02   14 months ago   3.17GB
clickable/ubuntu-sdk          <none>                                         1de64d532fa1   14 months ago   2.9GB
clickable/ubuntu-sdk          <none>                                         77906c8157f9   16 months ago   2.86GB
clickable/ubuntu-sdk          <none>                                         4b671c33afef   16 months ago   3.13GB

I do not know exactly which ones I shall keep, so I will delete all of them (by using the appropriate docker commands), and then do a clickable update to reload required images.

So no question, just to share, but I will be interested if anyone has recommendation, or info to better handle this.

Thanks @cibersheep for your answers, I succeed to do what I want with Content Hub and a C++ plugin to manage file deletion and renaming.
I wrote a a sample app available here: importwithcontenthub, with many (too much!) comments.
This sample app allow user to import an image, the image is stored (so that it is available on next app launch). And when user imports a new image, it is stored by overwriting the last one (only last imported image is stored).

@luksus , on FP3 (OTA-23), I confirm that microphone stop working in recorder app after a phone call.
I also succeed to restore microphone by doing:

• recorder app is open, no recording in progress
• open the phone app and make a call
• during the call, launch a recording in the recorder app: the mic works again
• close the call and close the phone app, the mic still works in the recorder app

Thank you @advocatux.
I have the version: com.ubuntu.camera 3.0.1.765

Hello,
I have exactly the same issue on my Fairphone2. I just had it, install UT successfully (15.04 rc). I install telegram application from the open store, but I cannot search a group, there is no button for that. When I go to contact or to new group, it is in endless loading loop. In the scope, when I try to search, I have no keyboard and I cannot paste in the search field.
I do not know what t do.

Hi,

Just to say that now with UT 16.04, no more problem, I can connect by ssh from my phone (ssh client) to my PC (ssh server) by using the public/private key authentication.

Hi,
If it helps, I did a sample app (with many comments) to manage import of a file with content hub, see:
https://gitlab.com/ubuntu-touch-applications/sample-applications/importwithcontenthub

Yes! it is working with last clickable version (6.23.3).
Thank you @lduboeuf !

@luksus , on FP3 (OTA-23), I confirm that microphone stop working in recorder app after a phone call.
I also succeed to restore microphone by doing:

• recorder app is open, no recording in progress
• open the phone app and make a call
• during the call, launch a recording in the recorder app: the mic works again
• close the call and close the phone app, the mic still works in the recorder app

Hi @homer,
I have sometimes the issue with video recording and also with the Recorder app.
After rebooting the phone, the mic works again, but fail again after a while.

@AppLee , the issue you mention is related to fairphone2, and I don't think the issues are related.
I own a FP2 and a FP3, I have the issue of "no sound recorded" only on the FP3.

@opolork, yes I have the last camera module (the one with 12MPix). And the torch/flash does not work.

Hello @opolork
For info on my FP2 (with OTA-22), the video recording is working well, quality is good.

@cesar-herrera
This link give useful info on android partitions:
https://forum.xda-developers.com/t/info-android-device-partitions-and-filesystems.3586565/

Being interested in this topic, I did this recently: listing the partitions on FP2 device with Ubuntu Touch OTA 22:

• Connect FP2 to PC
• on PC run: adb root (note: can be avoided, and may not work on some device like on FP3 for example)
• then: adb shell

in shell, list partitions with parted (because gdisk is not installed)
run: parted -l (or run sudo parted -l if shell not in root)
and for example I get this:

root@ubuntu-phablet:~# parted -l
Error: /dev/mmcblk0rpmb: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc) 
Disk /dev/mmcblk0rpmb: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Model: MMC BWBC3R (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem msftdata
2 134MB 135MB 524kB sbl1
3 135MB 135MB 32.8kB dbi
4 201MB 201MB 32.8kB DDR
5 268MB 269MB 1049kB aboot
6 269MB 280MB 10.5MB splash
7 280MB 280MB 512kB rpm
8 336MB 352MB 16.8MB boot
9 403MB 403MB 512kB tz
10 403MB 404MB 1049kB pad msftdata
11 404MB 406MB 1573kB modemst1
12 406MB 407MB 1573kB modemst2
13 470MB 2617MB 2147MB ext4 system msftdata
14 2617MB 2651MB 33.6MB ext4 persist msftdata
15 2651MB 3322MB 671MB ext4 cache msftdata
16 3322MB 3339MB 16.8MB recovery
17 3339MB 3340MB 1573kB fsg
18 3355MB 3355MB 1024B fsc
19 3355MB 3355MB 8192B ssd
20 3423MB 31.3GB 27.8GB ext4 userdata msftdata

Thank you @luksus

I retry with the 0.8.9-beta, I succeed to install UT without error

For those who will install, be patient, the installation seems long on the phone (screen "installing updates", then reboot...).

Next step for me, restore my user data (from a FP2)...

Thank you @keneda ,
Here is the complete error message:

Error: adb:preparesystemimage: Error: {"error":{"code":1, "cmd":"adb -P 5037 shell mkdir -p /cache/recovery"},"stderr":"mkdir: '/cache/recovery': Required key not available"}

For info, I rewrite the message, I was not able to copy-paste, the UBports installer does not allow it!

And I have created this issue:
https://github.com/ubports/ubports-installer/issues/2449

Hi
I try to install UT with UBports installer v0.9.1 beta.

I think I prepare things correctly:

• Android 10 was present on the phone and updated to last version: 3.A.0135
• bootloader unlocked and developer mode enabled
• in installer, I select:
  • channel: 16.04/arm64/android9/stable
    Why is it android9? I was expecting a basis on android10!
  • wipe userdata checked
  • Bootstrap checked
• I follow instructions and phone was in recovery mode when this error occured:

I try again and same error occurred.

Do you have an idea how to solve this?

To erase docker images, I use docker command rmi, for example for IMAGE ID = 4b671c33afef

docker rmi 4b671c33afef

Then, after deleting all images, doing clickable update does nothing!

But just build your app with clickable or clickable desktop and images are reloaded.
This gives:

docker image ls
REPOSITORY                    TAG       IMAGE ID       CREATED       SIZE
clickable/amd64-16.04-armhf   16.04.5   de10b0785b01   12 days ago   3.24GB
clickable/amd64-16.04-amd64   16.04.5   46cf1141cef4   12 days ago   3.44GB

Hi,

The docker images, used for Clickable, accumulates on my hard drive and I run out of space!
I run Kubuntu 20.04 on a disk of 120GB, and I have another larger disk for my /home.
Until now I did not care where this images where stored, and I was a bit surprised to run out of space.
Docker images are stored in /var/lib/docker so they uses space on my 120GB disk.
And I have many images:

XXX@XXX:~$ docker image ls
REPOSITORY                    TAG                                            IMAGE ID       CREATED         SIZE
clickable/amd64-16.04-armhf   16.04.5                                        de10b0785b01   12 days ago     3.24GB
clickable/amd64-16.04-amd64   16.04.5                                        46cf1141cef4   12 days ago     3.44GB
clickable/amd64-16.04-amd64   <none>                                         7e758494f183   2 months ago    3.42GB
clickable/amd64-16.04-armhf   <none>                                         6236c98e71a1   2 months ago    3.2GB
clickable/amd64-16.04-amd64   <none>                                         e3075a8131f7   2 months ago    3.42GB
clickable/amd64-16.04-armhf   <none>                                         79e9333e49e6   2 months ago    3.2GB
clickable/amd64-16.04-amd64   <none>                                         0b3ce64ac2a1   4 months ago    3.21GB
clickable/amd64-16.04-armhf   <none>                                         60280ecc7f75   4 months ago    2.97GB
clickable/amd64-16.04-armhf   16.04.5-52e346f1-7f68-4acf-b25a-f909a7f151de   d5a088555e63   6 months ago    3.06GB
clickable/amd64-16.04-amd64   16.04.5-e6f90001-5335-4b61-aaaf-ee27ec05ca9a   f2ae84741742   6 months ago    3.28GB
clickable/amd64-16.04-amd64   <none>                                         5c90fa6d0219   7 months ago    3.24GB
clickable/amd64-16.04-armhf   <none>                                         274d61c78369   7 months ago    2.99GB
clickable/amd64-16.04-amd64   <none>                                         ca2295f385c8   8 months ago    3.22GB
clickable/amd64-16.04-armhf   <none>                                         ac0efb3e90f9   8 months ago    2.97GB
clickable/amd64-16.04-armhf   16.04.4-qt5.9                                  70ee31165bda   8 months ago    3.32GB
clickable/amd64-16.04-amd64   16.04.4-qt5.9                                  020f92dc47d1   8 months ago    3.73GB
clickable/amd64-16.04-armhf   <none>                                         b05354f06d34   8 months ago    3.32GB
clickable/amd64-16.04-amd64   latest                                         221fafae479b   8 months ago    3.22GB
clickable/amd64-16.04-armhf   latest                                         e21dd4f44f87   8 months ago    2.97GB
clickable/amd64-16.04-amd64   <none>                                         b287ba7b39ee   10 months ago   3.16GB
clickable/ubuntu-sdk          16.04-armhf                                    d29e7ad6f85d   13 months ago   2.89GB
clickable/ubuntu-sdk          16.04-amd64                                    534d93e2668b   13 months ago   3.16GB
clickable/ubuntu-sdk          <none>                                         d146e1f7df02   14 months ago   3.17GB
clickable/ubuntu-sdk          <none>                                         1de64d532fa1   14 months ago   2.9GB
clickable/ubuntu-sdk          <none>                                         77906c8157f9   16 months ago   2.86GB
clickable/ubuntu-sdk          <none>                                         4b671c33afef   16 months ago   3.13GB

I do not know exactly which ones I shall keep, so I will delete all of them (by using the appropriate docker commands), and then do a clickable update to reload required images.

So no question, just to share, but I will be interested if anyone has recommendation, or info to better handle this.