GravityBox main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience. This means it is not possible to “completely deactivate” particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can’t find elsewhere. This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good. GB being a complex module, it shouldn’t be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there’s no way you can deterministically say which one’s going to win. They can even lose both.
If you experience weird issues after installing GB, even if you didn’t activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM. It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device – it won’t work.
GravityBox [Q] has been tested on – OnePlus 7 Pro running OxygenOS 10 – Nexus 5X running Pixel Experience 10
This procedure assumes you have working Magisk installation. 1) Install Riru and EdXposed modules using Magisk Manager 2) Install EdXposed Manager app 3) Reboot and open EdXposed Manager app to check if EdXposed works and is active 4) Install GravityBox and enable it in EdXposed Manager 5) Reboot