I have no idea what could possibly be causing this, but as there have been three separate reports of this issue I am now acknowledging its existence as something that isn't device-specific. I originally thought the problem came from the accessibility service as that has been a point of many headaches in the past, but as it persists after reinstallation I am now thinking it might be something to do with the devices backing up & restoring SharedPreferences after installation. Maybe it's creating some scenario that shouldn't exist and I haven't accounted for somewhere despite having gone through the setup routine countless times in the past to ensure its perfection. Anyway, I'll try declaring the option to disable backups in the manifest of the next release and see if it makes any difference.
I have no idea what could possibly be causing this, but as there have been three separate reports of this issue I am now acknowledging its existence as something that isn't device-specific. I originally thought the problem came from the accessibility service as that has been a point of many headaches in the past, but as it persists after reinstallation I am now thinking it might be something to do with the devices backing up & restoring SharedPreferences after installation. Maybe it's creating some scenario that shouldn't exist and I haven't accounted for somewhere despite having gone through the setup routine countless times in the past to ensure its perfection. Anyway, I'll try declaring the option to disable backups in the manifest of the next release and see if it makes any difference.