Have learned this is a known bug in the specific model I am using.
Still haven’t found a workaround but will update if I do.