Overview
Some banking apps on Android show a security warning, or refuse to work, while an Accessibility service is turned on. This is the bank's decision. The warning comes from the banking app, and Hoverwatch cannot control it.
Why banking apps do this
An Accessibility service can see what is on the screen and perform actions for the user, such as tapping buttons. Malicious apps can misuse these abilities to spy on the screen or control the device without the owner's input. For that reason, many banks react to any Accessibility service that is turned on, no matter which app it belongs to.
Is Hoverwatch the cause?
Indirectly. The bank reacts to any active Accessibility service, including the one Hoverwatch needs — most Hoverwatch features do not work without it. The check itself is run by the banking app, under the bank's own security policy.
Can this be bypassed?
No. There is no supported way around the bank's check, and you should not try to. The bank decides how its app responds to an Accessibility service.
What you can do
When you need the banking app, turn the Hoverwatch Accessibility service off for a while:
- Open the phone's Settings and go to the Accessibility section. Menu names differ between phone models, so the path on your phone may vary.
- Find the Hoverwatch service, which appears as Sync Service, and turn it off.
- Use the banking app.
- Turn Sync Service back on. For the steps, see Restoring permissions for the Hoverwatch app.
While the service is off, features that depend on it, such as call recording and social app monitoring, stop working.
Summary
Whether a banking app runs while an Accessibility service is on is up to the bank, and there is no supported way around that check. The only option we can offer is to turn Sync Service off for the banking session; turn it back on as soon as you are done.

Comments