I am opening a separate thread to start a discussion regarding next steps of Tama port. I would like to start with the thanks to all who took time and tested AOSP10/aarch64 SFOS port and helped with the feedback. In addition, the port was made possible due to the help of fellow porters. The feedback of Sony AOSP team is very much appreciated as well.
State of AOSP10/aarch64 based port for Tama is far from the best. We have several issues that are originated from AOSP10 and the used blobs with the latter being suspected for the main ones. Here I will give a short overview of the issues and try to compare the state of the port to the one we have used earlier - based on AOSP9/arm32 SFOS.
There is a significantly larger power drain in AOSP10. When tested on the same device in flight mode, drain is jumping to 0.9%/h (AOSP10) from 0.25%/h (AOSP9). Such jump has been observed in AOSP10 without SFOS as well. In general, it does feel that the drain is larger than before when you use the device as a daily driver as well. In part, it can be mitigated by a small governor switching off power hungry CPUs making it possible with my usage to get just below 3%/h during a day. What is causing the drain I don’t know, it is possible that something is off with the BLOBs as well. Issue: Power consumption while idling · Issue #154 · sailfishos-sony-tama/main · GitHub
When showing just Lipstick, there is frequently a choppiness in transitions. In addition, on XZ3 there are either glitches in form of lines (video Power consumption while idling · Issue #154 · sailfishos-sony-tama/main · GitHub) or some spectacular pixelation (Xperia Tama port: AOSP10/aarch64 release - #15 by Pasik2). So far, within apps there are no such problems and it could relate to singlesurface rendering issue mentioned by AOSP developers. Issues with GPU are attributed to kernel 4.14 and BLOBs. At least transitions and XZ3 line glitches can be sorted out by bumping GPU minimal frequency, not sure about pixelation. That may increase the power consumption, although it hasn’t been tested. Issues: Frame rate low for compositor on idle · Issue #143 · sailfishos-sony-tama/main · GitHub and hybris-10 XZ3 glitch on screen while swiping or unlocking · Issue #150 · sailfishos-sony-tama/main · GitHub
On XZ2, wireless charging looks to be mostly gone - works very rarely (less than once in 10 times probably).
There is some oddity with LED (doesn’t always blink for new email notification unless it is on charger; seems to be SFOS issue noticed for Xperia 10II as well), VP9 videos don’t always resume after going in/out of browser, screen goes to max brightness for a moment when you switch it on. Few niggles were solved by patching AOSP10 (act dead mode, echo during calls), so those are resolved for SFOS. Current list of issues for AOSP10 based port are marked by a separate label in the issue tracker.
While Flatpak has been compiled for aarch64 and the apps can run, this is without any hardware acceleration. I didn’t manage to make hardware acceleration work on AOSP10/aarch64 SFOS base after spending some time trying to do it. It is probably possible, but would require a fresh look by someone. In general, Flatpak on AOSP9/arm32 is a mixed bag - it is working, but current Flatpak platforms don’t support this arch anymore. So, we don’t have much apps available for arm32 either.
Camera is usable on AOSP10 based port. It doesn’t crash, with the Advanced Camera performance has been better than with the one bundled with SFOS by default. For me, manual focusing mode with Advanced Camera works the best. Still, camera flash on AOSP10 based port is not in sync with photo taking. So, using flash is no go on AOSP.
See better summary from others: Camera issues · Issue #153 · sailfishos-sony-tama/main · GitHub
As the port is not ideal and has significant shortcomings compared to AOSP9/arm32, we would have to discuss what to do and which solution to choose. I would not expect any BLOBs updates for AOSP10 anymore as development has shifted to AOSP11. So, the state would probably be as it is now with the hardware support.
We have several options:
Stick with AOSP9/arm32 port. Main disadvantages are absence of camera and Flatpak support doesn’t probably matter soon as arm32 is phased out.
Switch to AOSP10/aarch64. Will get better camera, no Flatpak support and I cannot promise that it will come. Several bugs rooted into AOSP10/BLOBs combo.
Those solutions are available now.
In principle, it is possible to develop new ports:
Switch AOSP9 to aarch64. I would expect it to be way less effort than it was to make AOSP10/aarch64 based one, which took months. Main advantage is that probably (notice that it is not 100% sure), Flatpak will work with HW acceleration.
Make a port based on LineageOS 17.1 which, in turn, runs on top of stock android. So, camera is expected to be better than AOSP10/aarch64. Issue with LineageOS is that they already switch to Android 11, Android 10 builds are disappearing from the servers. XZ3 is not officially supported by LOS 17.1, only 18 (but this cannot be used for SFOS yet). It is again a lot of work to make it happen and I would not be able to rely on Sony official BLOBs as AOSP-based solutions can. Flashing would be more difficult. Quality of LOS 17.1 is unknown to me, mainly tested that it is possible to get it running but proper testing will be needed first. Flashing LOS turned out to be mixed bag for me with the official instructions not leading to working image. In general, I am not keen on this solution myself as it is a step away from what was done so far.
Would be great to hear opinions of others, whether you managed to test AOSP10/aarch64 port or not.
Edit 8 Jul: added camera flash out of sync in AOSP
Edit 8 Jul 2: LED blinking/non-blinking has been also noticed on Xperia 10II (Xperia Tama port: discussion on future direction - #10 by Pasik2)