sneak peek + double tap how can work this on Sony Xperia 10? [answered]

Thank you @spiiroin, I was unaware that the command is actually valid. (Everyday is a school day!)

Thank you very much - I test this and it works perfect. I will try this in the next time. I hope it works for me. Now I can also test the double tap features with proximity. I have follow lines now:

mcetool --set-ps-on-demand=disabled
mcetool --set-lpmui-triggering=from-pocket,hover-over
mcetool --set-doubletap-mode=show-unlock-screen
mcetool --set-fake-doubletap=disabled 
mcetool --set-doubletap-wakeup=proximity

Is the order of these commands important or can I use the commands in any order? I ask, because double tab not work afte the first test. Maybe I have to restart the mcetool.service...

Sneak peek works now fine only the double tap not. Because I try this and now double tap works but only in the 5s lpm mode from the display. I found it here and create also a new help file with all new commands.

mcetool -M unlock (-M is the same like --set-doubletap-mode=)
mcetool -z proximity (-z is the same like--set-doubletap -wakeup=)
mcetool -i enabled (-i is the same like --set-fake-doubletap=)
mcetool -E enabled (-E is the same like --set-low-power-mode=)

What is wrong. I will this use everytime?

I still fail to find any concrete refference to Xperia 10 & Xperia X proximity sensor being faulty in the same way as the XA2 one is.

Am I missing something or has this change been simply done for all Xperia devices, to reduce difference between device configuration, at athe cost of regressing the functionaliry of unaffected devices ?

Unfortunately is this bug also on Sony Xperia 10 with 3.2.1.20. It seems to be a result from the charging of the cell phone. Previously, it worked over 6h but after charging overnight, it the sensor was not active more. But I found a very simple way to fix it. Respo installs the "ShellEx"app and enters the systemctl restart sensorfwd command there. Then you are only asked for the pin of the phone but not for the root password and the Sendor is ready to go again !!! My idea for an SFOS update would be to simply restart this service when charging end or start. I will check if the charging the realy reason is in the next time...