Tap, Tap uses sensor data from your device in the background, which can be quite intensive on the CPU and battery. Some OEMs also may include features in their software that are designed to kill high-power apps that are in the background, which you will need to exclude Tap, Tap from for it to continue working.

Disabling the system battery optimisation to allow Tap, Tap to keep running in the background varies from device to device, and may involve several steps. In almost all cases you will be able to simply exclude Tap, Tap rather than disabling the feature for the entire system.

To disable the standard Android battery optimisation for Tap, Tap, use the option in More > Battery & Optimisation in Tap, Tap. If Tap, Tap is able to detect a further OEM feature, it will also give you the option to open the settings page to disable that for Tap, Tap as well. For other cases, please see dontkillmyapp.com

As mentioned above, the core of Tap, Tap uses sensor data in the background, and runs this data through a machine learning model. This can be quite power intensive, so there are a number of ways to limit how often the model is run, and make it more efficient.

• Use Low Power Mode if you can. This special mode, available on some Pixel devices, uses the low power CPU (also known as the "context hub") to run all sensor monitoring and the machine learning model. This is the best option if you can use it, but be aware that you will need to use Shizuku or Sui for it to function, and it is only available on Pixel devices which have the Quick Tap feature officially.
• On many devices, you may be able to use the "Tensor Low Power Mode". Try enabling it in the Advanced settings, and reboot. If the gesture still works, keep it enabled. If not, disable it again and reboot. This option was previously enabled by default, but was discovered to be causing issues with freezing and the gesture not working for some, so is now opt-in. It takes advantage of the NNAPI framework in Android, which is more efficient than running the machine learning operations in software.
• Use your selected gates wisely. Not all gates were created equal, there are some that are "passive" and some that are "active". Active gates are able to temporarily disable the sensor monitoring while they are blocking - which can save battery significantly if used correctly.
  • If you are using an "active" gate that will often be blocking, such as the Lock Screen Showing gate, put it at the top of the list. If the service encounters an active gate as the first one that is blocking, the monitoring can be switched off temporarily, but if the first blocking gate is passive, the sensor monitoring will need to continue. A list of active and passive gates can be found below.
  • If you have multiple active and multiple passive gates, put the active ones first.