Well, to fix something I first need to see and understand it. I tried to test this problem out on 4 different devices and this problem didn't occur. Also, the mobile version has a long history - more than 2 years and this is the first time I heard about this.
It's very hard to track something without a sequence to reproduce the problem. It can be tied to your device's setup, other software and a pack of other possibilities. As a solo developer, I can't cover all of these.