Very interesting points actually:
I will start moving builds to OBS as we have it working now.
Re VP9: that was mainly found via journal or logcat, donāt remember now
Re camera flash: we have something way more interesting - you get a flash firing just before making picture. So, exposure is set assuming flash and the picture is taken without it. As a result, mostly black square is what you get as a photo 
Re overexposure: I donāt know where exposure is calculated. Would expect it to be in the BLOBs
Re lipstick: In our case it is probably due to some AOSP10/BLOBs bug. At least AOSP developers told that there are some issues with rendering of singlesurface (whatever that means). As we can resolve it by bumping GPU frequency, I think we are good now.
Re Sony related or not: hard to judge. AOSP/Sony is using QCOM BLOBs. Whether they have similar bugs on other devices, I donāt know
The beta release fixed the slow framerate issue. The phone feels nice. 
Beta is prepared for release, not released yet. Wanted to test a bit before tagging it.
Hehehe. Saw the update on github and followed the alpha to beta OTA thinking we are good to go.
No harm done. The only think i noticed was that i didnāt have zgovernor installed and i got a āno such packageā message. Everything else was on point.
At least we know that works.
Its good to know that OTA works. I presume that zgovernor issue was a response to uninstall request in the beginning of the instructions, right?
Yes. There was nothing to uninstall.
As there were no requests on keeping AOSP9 and all of those who have been testing AOSP10 based builds seem to be OK with it, I am going to conclude this discussion and we are switching to AOSP10 based port.
My own impression of AOSP10 based port are positive. Few days ago zgovernor has been updated and takes care of GPU scaling to ensure that the glitches are absent or very rare on XZ3 (as far as I know) and interaction with Lipstick is smooth. The power drain seems to be OK (handles similar amount of time as earlier for me), but I will leave it to others to compare.
Since this is a discussion thread for the tama port has anyone discovered apps (that have aarch64 support) in the store and donāt install?
So far only corereader is the one i found but there could be more.
I reflashed my xz2c last week to sf4.1 and I am very happy with the results. Itās great to have the camera working and the only downsides so far have been 2 unprovoked crashes. It feels a good bit faster; the battery can be erratic depending on whatās open, so I try to keep apps to a minimum. Thank you Rinigus and others who made this possible.
Speaking of crashes -and with the fear of jinxing it- iāll just say that my uptime as i type this is 41 days.
Goes to show the quality of the port and OS from a stability POV.
Update: battery more erratic in hotter weatherā¦at 28C outside, the phone on my car seat overheats a lot with a few apps open. Then suddenly drained to zero and shut down. Unfortunately didnāt have battery buddy open to warn me.
btw - I noticed a couple of new issues open in Github page by rinigusā¦ Maybe some update activity coming soon.
It is related to encryption of /home using new implementation. Some work is still needed, though.
@rinigus Having problems with installing xz2c . When trying to install the phone is never recognize for transfer the sfos build
It keeps saying in termonal using Debian, nsearching device to flash while the phone seems to be in fastboot with blue led colour
~/Downloads/Sailfish_OS-4.2.0.21-h8324-0.4.0.1$ sudo bash ./flash.sh
Detected Linux
Searching device to flashā¦
Found H8324, baseband:, bootloader:waiting
Found 1 devices: BH903W2DBZ
Fastboot command: fastboot -s BH903W2DBZ
Flashing boot partitionā¦
< waiting for BH903W2DBZ >
Sending āboot_aā (20268 KB) FAILED (Write to device failed (Protocol error))
fastboot: error: Command failed
While it doesnt recognize it, I took off the cable and plock it again in fastboot and this is what it says
@delocoyo: is it possible that you use USB3 port on the laptop? Or maybe there is some issue with a cableā¦
If youāre sure the phone is unlocked, usually this type of error can be fixed with
I have change to another computer, and it has help. One with Ubuntu has done the work. Thanks guys. Now time to enjoy Sfos in my compact.