[Xposed Framework Modules] i5lee8bit:
Lol, well it's all good. I didn't even bother with White List mode before, as I''ve been using Black List mode. There were some VERY STRANGE instances to get some of my banking apps 100% working, where for some reason I needed to SPECIFICALLY Black List (but the default blacklisted status of being left alone on the White List for some reason never worked, freaking weird man) and/or add to Compatibility mode, or a combination of both or one or the other. TD Bank (which has since started working again), Chase app (Compatibility mode, if I want to be able to see bonus cash back offers section show up), and Wells Fargo app were among the weird ones.

Plus, along with a bunch of these banks finally updating their biometrics API integrations, it's also less annoying to need to WhiteList each app, one by one, that still need FingerFace to use Face Unlock. I'm now only down to 2 of them - PayPal (c'mon PayPal, seriously??? get with the times!!) and Capital One - yet Capital One's CreditWise app uses the new biometrics API while their main banking app still uses the old fingerprint API - really Capital One? Who's in charge of your mobile development team??

ANYWAY, with all that said I finally switched to White List mode. And along with that, I lost having the [volume key cursor control] mod working. So I did some quick investigating. C's source code for GB shows that the mod is tweaking the functionality of android.inputmethodservice.InputMethodService. So I took a quick look at the Android source: https://developer.android.com/reference/kotlin/android/inputmethodservice/InputMethodService. Which ultimately turned out to be a waste of time, because the solution was a lot simpler than that (at least the solution for me, and hopefully for everyone). At first, I tried to whitelist Input Devices (com.android.inputdevices), reboot, but it didn't work. I then tried to whitelist both Input Devices as well as Gboard, reboot again. Volume key cursor control worked immediately after reboot. It turns out com.android.inputdevices had nothing to do with it. Only the keyboard app being used (although I'm assuming - I don't use any other virtual keyboards on my phone) needs to be whitelisted for this option to work immediately upon reboot. Do note that removing Gboard from whitelist does not make the mod stop working (at least until reboot), nor does enabling the app in whitelist make the mod start working before rebooting (even if you toggle the setting on/off in GB). For those who don't know, it was a limitation in GravityBox [Q] that on some devices the option needed to be toggled off and back on to work, after reboots.

The behavior seems to have changed in Android 11 - and furthermore it seems that the behavior is invoked upon sometime in the boot process. For whatever reason, the virtual keyboard app / input method targeted by the mod needs to be whitelisted and read by the EdXposed module during the boot process.

So, @C3C076, I believe the solution to:

is to simply whitelist whatever your "input device" method (virtual keyboard app) is. In my case, whitelisting Gboard. I would assume if you have multiple keyboards installed, you would want to whitelist each one but I haven't tested this at all (see next post). Hopefully all this word barf helps you clear this particular issue out of your list. I dunno, maybe with your ninja coding magic skills you can come up with something more elegant, or something that better directly targets the issue. :)

PS: Pixel 4 XL on Android 11 (duh). Oh, and I can't liiiiiiive without my volume key cursor control baaaaeeeee~~~~!!! 🤪🤪