This eventually resolved, somehow…
I think it’s related to:
…where the firmware settings changed.
Since then, I’ve not seen any of the behaviour mentioned in this thread. The touchscreen, which I had disabled, has also re-enabled itself.
This eventually resolved, somehow…
I think it’s related to:
…where the firmware settings changed.
Since then, I’ve not seen any of the behaviour mentioned in this thread. The touchscreen, which I had disabled, has also re-enabled itself.