Do not make issues about the service being killed by the system (they will be closed)

[KieronQuinn]

Due to OEMs clearly not caring and killing every background service in sight (including accessibility services - image requiring something like Tap, Tap to be able to use your phone, only for it to be killed constantly) in the name of "battery optimisation", there has been an influx of issues related to the app being killed by the system.

Please make sure you have followed the steps in the app to help prevent the service being killed by the system, including those on https://dontkillmyapp.com/, this is the only known way to prevent the app being killed. It is also recommended you reboot your phone after running the steps for good measure, to reset any settings that may be cached.

Beyond this, there is no magic code that can make the system not kill the app, so I cannot do anything about this. Therefore, issues related to this will be tagged with "Service Killed" and be closed.

[waxwepa]

After weeks of careful observation, I am 99.9% sure Samsung does not kill Tap, Tap completely, because when it does not execute the screenshot command, I nevertheless get the haptic feedback. I found out that if I reimport the app's settings, proper functionality is restored 100% of the time. I love this workaround and I was wondering if you could not implement an automatic restore, say every 30 minutes, once you know you are running on a Samsung device. Excellent work anyway. Paul

[KieronQuinn]

After weeks of careful observation, I am 99.9% sure Samsung does not kill Tap, Tap completely, because when it does not execute the screenshot command, I nevertheless get the haptic feedback. I found out that if I reimport the app's settings, proper functionality is restored 100% of the time. I love this workaround and I was wondering if you could not implement an automatic restore, say every 30 minutes, once you know you are running on a Samsung device. Excellent work anyway. Paul

A previous version had an auto restart, it didn't make any difference. If it's giving feedback but not running screenshot, that can only mean one thing - the accessibility service is dead (as that is what runs the screenshot action). It's impossible for an app to restart accessibility (the system has to do it), so there's nothing I can do.