I'm a new user, and since installing recently, I've been very happy with the Enpass feature set and value offering. One major gripe, however, is its CPU use on Android.
I'm on a Samsung Galaxy S9 running Pie (April security patch level, recent kernel), with what I believe are quite common Enpass settings. As long as Enpass is running (which I prefer it to be so I can enter my PIN, not always my rather long master code), it will continually gobble up more or less all available CPU (at least >1 full core), to the point that my phone gets hot, and maintenance tools find it necessary to warn me about the anomaly taking place in my system. Needless to say, this also has a very adverse effect on battery life, which has dropped drastically since I set up Enpass.
Clearly there's a bug here. Is it known? What help can I offer to isolate and pin it down? And until such time, what workarounds should I be looking at, apart from stopping Enpass from running in the background? I've seen scattered posts alluding to the accessibility service, so that's where I'll start experimenting first.
Any help would be greatly appreciated, be it from staff, subject matter experts, or even just a "me too" from anyone who's seen anything similar to this.
Thanks.