Yes, do a fast release.
Currently (before last OTA) there are so much fixes, that the stable users have to wait for one or two months.
I think it's better to get fixes to stable channel quick.

FP2, findings and differences to legacy version:

• camera does work with gstreamer-droid patch and is superfast
• after turning flightmode off, it is not needed to enter SIM-pin again
• waking up from sleep is delayed by some (5?) seconds, what makes it hard sometimes to answer a call, because you have to wait until the swipe is working
• I can't get a MTP USB connection, when I unplug the device, my pc informs me about using another network connection, lsusb identifies the device as:

Bus 003 Device 007: ID 0fce:7169 Sony Ericsson Mobile Communications AB FP2

Is that gstreamer-droid based camera only a Halium-thing or will it also come to current ports?

@jezek :

please try the following command in the terminal (on the phone):

rm -rf .cache/mediascanner-2.0/ .cache/unity-thumbnailer/ .cache/gstreamer*/*

Then reboot.

This always fixed it for me, whenever this issue appeared again.

I have just added the kodimote app to the openstore.

@Flohack : oh you got me wrong a little bit. I did not create my own port.
I just wanted to host the images I built out of Ratchanan´s port, since no prebuilt images are served yet.
It is for the users, who are not able to download all sources or can't build it by themselves, but like to test the halium port.

@peat_psuwit , @Emphrath : wooow, the flash works with the camera app ... I am speechless
This is with Halium and latest gst-droid patch.

An FP2 with new camera module and working flash... I still can't believe it.
Thank you so much @peat_psuwit .

Hi,

I've been investigating the forum, ubports website and google (and youtube) very hard, but could not find a clear answer, except of some beta implementation for the nexus 5.

Could someone please tell me, what the state of widi-implementation for each officially supported ubports-device is?

Thank you very much.

Okay.
I can confirm that the problem is the android-tools package of manjaro-community package.
I uninstalled it, and installed the android-sdk-platform-tools AUR-package.

Now it works, although I am not shure, if the installer is using the AUR package or if it is using it's own tools?!

I encountered the same issue sometimes in the last weeks. And fixed it the same way, as you did.
I am on Edge channel.
Mostly it happened when deactivating hotspot again. But because the hotspot did not deactivate properly, the wifi was not usable anymore and I needed to reboot.

But since nearly a week the issue seems to be gone, at least for me.

Since Fairphone managed to run Android 9 on the FP2, would it be possible to create a Halium 9 Port with this GSI thing?
https://www.fairphone.com/en/2020/06/18/fairphone-2-gets-android-9/

@Abuabdellah No.
You would need something like "optimus-switch" or "optimus-manager" or "bumblebee", etc.
That depends a bit on which distribution you are using. On Ubuntu there is a similar tool, called "mate-optimus".

@Abuabdellah so it is automatically starting in nvidia mode.

Are you on a laptop?
If so, can you try to run the laptop in "internal gpu only"-mode, and run clickable again?

Hm ok.
So if you are on a laptop (I assume this, because of the "9300m" chip), theoretically it has to be possible to run clickable with the cpu's internal gpu, and not with the dedicated nvidia one.

So please try AppLee's suggestion.
And you could run clickable in verbose mode clickable --verbose desktop, that we can see the docker command, which is used by clickable.

Do you have the package "nvidia-docker" installed?
And are all requirements met, which are mentioned here: https://clickable-ut.dev/en/latest/commands.html#clickable-desktop-nvidia ?

Edit: So as you have a docker version > 19.03, the nvidia-docker package no longer seems to be needed.
But the nvidia-container-toolkit.

@Fla for me it works with the rootfs from 12 days ago. So I assume it could be caused by the rootfs build you have used.

I just created a new build of the halium and the system images:
https://drive.google.com/open?id=19xoNR-h-G1m8RUpJjA_6VTLWXvH40FH-

I am not sure, if there are changes in halium, but @peat_psuwit did add the minimum brightness fix to the FP2 device config. Therefor this should work out of the box now.

For installing follow this instructions:
https://docs.ubports.com/en/latest/porting/installing-16-04.html#install-halium-boot
From "Install halium-boot" until "Install system.img and rootfs". That should do it.

For the camera to work fast and with flash, follow this instructions.
Or just "wget" this script on your phone's terminal and execute it.
Don't forget to install the patched camera app.

Felgo Documentation:

Felgo is a cross-platform development SDK based on the popular Qt framework. Felgo app and games are created within Qt Creator. Felgo's main language for writing source code is a declarative language called QML together with JavaScript.

The Felgo SDK includes all the components you need to develop professional cross-platform apps and games.

Sounds interesting.

@Fla When you flashed your phone with the Halium 7.1 version, you took the images I provided to you and you also needed to download the current rootfs (dev) build from the CI-Server.
So you just can download the new rootfs build and flash your phone again with that command:

path/to/halium-install -p ut path/to/rootfs.tar.gz path/to/system.img

(Perhaps there is a way to flash the rootfs only? Hm, perhaps it is possible to flash the phone with the ubports-installer without flashing the boot-partition and the system-image, I don't know.)

After doing that, you need to make changes, which you did to the rootfs, again. For Example the droid-cam patch.

@Fla hm perhaps the issues are unique to my phone, wifi module and/or battery.

No, I did not built another image yet. But this is also not necessary, when there are no changes in halium for FP2.
So you just can take the "old" halium and system build and flash it together with the latest ubports build.