I definitely don’t have any weird tint. I probably have the echo; but presumably using a sensible volume level and having my head between the speaker and microphone works quite well (so that net complaints are like one or two). And since it was stated not to affect speaker mode, i really do wonder how people get into the situation.
I’m back on Sailfish OS, and i have also flashed my 10 III with Android 13 and ASOP binaries 11, no echo and no wierd tint on my device…
3 Likes
Well, contrary to you, I did have quite heavy tinting and color banding with Android 11. If updated OTA to the very last Android 11 version (which required locking the bootloader, as otherwise OTA updates are not available on Android and EMMA did not offer those latest A11 versions), those issues were somehow lighter and fixable using e.g. the 10 III Brightness Fix, but if SFOS was flashed on top of the highest Android 11 version available via EMMA, those issues were even stronger and Brightness Fix not always worked.
With Android 13 the problem is completely gone (without any sort of fix), so yes, for me it does the magic.
In my case it required keeping the volume at (or below) 70% or else people were complaining about disturbing echo. With Android 13 there is no echo regardless of volume level (and it is sometimes really helpful to be able to set the volume at 90-100% to properly hear the other person), so also in this case I can’t refrain from praising that benefit of having SFOS running on top of Android 13.
Yeah… so curious what the root cause differences are here 
not sure if there’s any realistic path to finding out.
Depending on new devices compatibility, this problem might or might not fade into oblivion soon. Regardless, SFOS becoming officially “latest (currently A13) available AOSP-tested/compatible” would be nice for those not interested in switching devices.
I stated elsewhere that it’s a hardware issue for those who have it.
There are two different screens for the 10iii and one Android user got a new 10iii when he returned his for this very common issue. The A13 blobs seemingly fix the dodgy screens. I have yet to test this as I was hoping could we could replace the blobs alone.
If I find the thread, I’ll update this post.
[I don’t have the echo issue].
2 Likes
So nobody in this thread who has experienced echo (for callers, and when using to hands-free mode, specifically at high volumes) or seen the colour banding / green tint (especially at low display brightness) when originally using Android 11 as a base for flashing SailfishOS, has used the last Android 12 base (i.e. 62.1.A.0.675) for re-flashing SailfishOS, right? Just nosy, because that is still covered by Jolla’s statement in contrast to Android 13.
Side note: Because no issues became obvious when using an Android 13 base does not imply that there are none.
OTOH, I assume that Jolla is glad that some people test this combination.
Also, AFAICS, nobody has (just out of curiosity) tried utilising the Android 12 binaries (Lena, Kernel 4.19) with SailfishOS, yet?
Note, that one can flash and re-flash Sony’s software binaries at any time without altering an extant SailfishOS installation.
I just wonder if the Android 12 binaries make a difference and if so, for the better or worse (e.g. WRT these issues: [1], [2])?
BTW, I do not own an Xperia 10 III, but maintain this guide, hence my curiosity.
2 Likes
I did try to use Android 12 binaries with SFOS. None worked.
I did not try to flash SFOS over Android 12, simply because it is not offered by EMMA, meaning that it takes too much work to get it (you need to start with Android 11 as offered via EMMA and then make multiple OTA updates to eventually be offered Android 12 update). Moreover, to get OTA updates you need to relock the bootloader. Too much hassle for my liking. So, instead of that, went stright ahead to Android 13 (which is available via EMMA) and found it working just fine.
4 Likes
The thread I mentioned above, I perhaps overinterpreted it.
One Android update largely fixed the problem for maybe half of users. A later one fixed it for everyone. One user never had the problem. So it could have been different screens or it could have been regional variations. Sony presumably figured it out but never explained it. Given Jolla’s relationship with Sony, maybe they could ask them.
3 Likes
OK, so for test I flashed Android 12. Actually, it took flashing Android 11 via EMMA, re-locking the bootloader and then spending several hours applying multiple OTA updates: 3 or 4 Android 11 updates and then 3-4 Android 12 updates up to the highest available Android 12 version (then an update to Android 13 was offered, which I cancelled).
The actual Android 12 version that I have is 62.1.A.0.675 (the latest available).
I’ve called several people and they said that there is no trace of echo, even with max volume level. The display doesn’t exhibit any trace of color banding or tint, either. So those problems seem to have been fixed already in (or before) that Android 12 update. I will keep using it, as in such case there’s apparently no need to use Android 13.
Actually, I haven’t noticed any differences compared to Android 13. Neither advantages, nor problems.
P.S. I’ve used SFOS restored from rootfs/home image made using dd.
5 Likes
Wow, this is much appreciated! I really did not mean to trigger so much effort, but now we know for sure. I will utilise your findings for my install-guide.
Thank you very much.
4 Likes
You’re welcome! I actually did it out of sheer curiosity 
I was also interested in checking if it would have any positive impact on 10 III’s power consumption. Unfortunately, it remains the same.
P.S. I wouldn’t bother to do it if I didn’t have the rootfs and home backup, which allows to fully restore everything with such an ease. Warmly recommended!
2 Likes