It should be running indeed, and it does work for me…
Is there an effect and then difference if you run these commands in a dark room with a minimal brightness (as root)?
echo 1 > /sys/devices/dsi_panel_driver/hbm_mode
echo 0 > /sys/devices/dsi_panel_driver/hbm_mode
The first command brightens the screen and the second one returns it back to what it was. However, the “washed out” effect is still there and it’s identical before and after running the commands.
Also, using manual or automatic brightness adjustment doesn’t seem to make any difference. However, I’m not really bugged about this undesired colour banding, it’s just aestetchically unpleasing.
Since the workaround doesn’t work for some of us, there has to be more to the mystery… Could it be any help, if I uploaded the pictures before and after installing package? I used my partner’s iPhone to take the photos and they are asleep right now, so I could upload the tomorrow.
That’s indeed mysterious. So, that could mean there are differences in hardware, too, or this is affected by the Android version the device was on before it was flashed… I upgraded to a too new Android and firmware before flashing SFOS, what about you?
I didn’t update the phone after purchasing it and therefore I believe it was on Android 11. I just followed the installation guide and since Android version 11 was recommended, I went with it.
Now we just have to wait for more answers to that question, the Android version could be a crucial factor here…
Hmm weird. Actually already uninstalled it. After the new installation it seems to work now.
Worked instantly when i installed the app.
Thank you so much!!
I can finally enjoy the phone and focus on other things that need some tweaking!
I´ve installed it in my Xperia III and works great!!!
Thanks…
Now the screen looks awesome !!!
Thank you! Kiitos!
X10 III looks so much better now in the darkness!
I made a fresh reflash with 4.5.0.21 (on Xperia 10 III), and this color banding problem appeared (and is really noticeable with washed out colors, and black is not black anymore).
This didn’t happen before. When i bought the phone in May 2022, I initially flashed it with the latest release (4.4.0.64) and have been updating it with OTA to the latest release now available (4.5.0.21). A couple of days ago i reverted it to Android (62.0.A.3.109, Android 11) to pair my new activity tracker (to get the authentication key, and yes, there was no other way) and i reflashed it with the latest SFOS release.
@direc85’s “Brightness Fix for Xperia 10 III” helps (a very big thank you for that), with only one minor annoying thing: after a reboot color banding is back, until i turn screen off and on again, and then the fix kicks in again.
Any thoughts? I’m thinking about flashing my phone with an earlier Sailfish release (4.4’ish or something). Maybe something was changed along the way that didn’t apply with OTA updates?
I flashed my 10 III with Sony’s Android 13 (62.2.A.0.525) using EMMA, and then reflashed with SFOS. Color banding and yellow/green tint seem to be gone, without using the “Brightness Fix” or any other such workaround. Not a single time I’ve noticed any banding or tint, in any light. Additionally, no person I spoke with confirmed hearing any echo. It’s been three days now and I haven’t noticed any negative effects, either.
I’m having the same good call quality experience on latest Android 11 AOSP I flashed early of Dec '23.
Just tested now to wife’s iPhone 15 - zero echo or call quality problems, also on speakerphone.
People complained repeatedly about this on my previous X10II, which I think I could take out of the drawer and try flashing a newer AOSP release on it 
as discussed in Anyone flashed Software binaries for AOSP Android 12.0 – Kernel 4.19 – Seine on Xperia 10 ii? - #7 by wetab73
Official docs Updating the Vendor Image | Sailfish OS Documentation
EDIT Well, problem is there are no newer Android 10 releases since Dec 2020, but I think 11+ aren’t compatible on X10II?
Did you suffer from the brightness issue before? And it was resolved with the flashing? And you are sure it’s not there anymore?
If so, I could give this a try next month (when I can experiment with my daily driver again)…
Yes.
Yes.
Right after flashing Android 13 (62.2.A.0.525) and then restoring SFOS, I disabled the brightness fix service. It was some four days ago and since then I haven’t seen the color banding issue or the yellowish tint a single time. So I guess it is safe to assume that it is gone. Together with the echo issue which is also absent.
I’d recommend you to do it the way I did it, i.e. use dd (in recovery mode) to backup rootfs and home (/dev/sda79 partition), flash Android 13 using EMMA, and then simply restore SFOS from backup using dd. This way you can change the underlying Android version and quickly and easily get back to the exact same system you’ve had…
Please see Full dd backup of rootfs and /home as flashable images - #26 by wetab73
Don’t know if it’s just me but it feels like the latest 4.6.0.15 fixed the low brightness color issues?
It’s not fixed on my X10III, and there’s nothing pointing to it in changelog either.
What fixes the color banding / tint issue is flashing SFOS on top of either Android 12 or 13 base. Nothing else.
Does the issue cover weird, flashing colors and some broken gradients on low brightness? I had this issue even on stock Android 13
Same, 13 base didn’t solve the issue for me as well.
Instead of the obvious stains in blacks that go away with the fix (max brightness) in 11 base, with 13 base unfortunately there’s still some discoloration in some areas that won’t go away.
Haven’t seen any, not even a single time, since the very day I started using Android 12 or 13 base.
Maybe some screens are different… In my case either A13 base or X10 III brightness fix on A11 fixes greenish colors, but I still have flashing colors, weird gradients and other defects on low brightness, no matter of base/AOSP binaries used.