Hi. This is a well known problem and not due to a faulty sensor. It's a problem between Bluetooth and typically mobile phones with Android. The recent Android 13 update appears to have made it worse. Google, who provide Android are apparently looking into it, but have been for 6 months or more...