The app utilizes amazing Xposed framework coded by recognized developer rovo89 which, briefly, provides interface for injecting code into any app, including system services, allowing modifications of applications and system services at run-time.
View This On Google Play
One of the biggest advantages of GravityBox is that it is not bound to any specific device. Actually, it should run on any device having vanilla Android 6 (ROM close enough to AOSP).
This project wouldn’t be possible without rovo’s Xposed framework, so huge kudos to him.
— CyanogenMod Pie controls
— Expanded Desktop
— Statusbar QuickSettings tile management with additional tiles and reordering /* work in progress */
— Statusbar icon coloring
— Statusbar Brightness Control
— Center clock in statusbar
— Battery indicator style
— Navigation bar tweaks including cursor control keys
— Low battery warning policy
— Disable LED flashing when battery low
— Disable LED while charging
— Advanced power-off menu (reboot, recovery)
— Volume key cursor control
— Skip tracks by volume key long-press while screen off (thanks to rovo89)
— More volume levels for music stream
— Option to control safe headset media volume
— Button for clearing all recent tasks at once
— Minimal brightness setting
— Autobrihtness levels adjustment
— Lockscreen tweaks
— Hardware/navigation key actions
— Notification drawer style (background color, image for portait/landscape, transparency)
— Button backlight modes (default, disabled, always on while screen is on)
— Dialer (Phone) tweaks
— Google Launcher tweaks
— Screen recording
— GravityBox Actions – interface for 3rd party apps
— Smart Radio
— Notification control (per-app notification LED/sounds/vibrations)
— Ascending ring tone
… more to come
Some words about GB’s main concept. One thing I didn’t like about xposed modules was that it was always necessary to reboot a device after making a change to some option. Since GB’s main concept was to turn MTK devices running stock ROM into something that’s close enough to a feature-packed custom ROM, I had to take a decision – for it to be as much comfortable as possible and to really behave like a custom ROM, I had to design it to support most of the preference changes to be done on the fly without needing to reboot a device. While this sounds nice, it also brings couple of “drawbacks”. For changes to be made on the fly, it is necessary to make some preparations when device starts. This means, even if you don’t use the particular feature, the necessary preparation/modification is already there and is waiting for the user to come and change that option.
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.
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 as if you installed ROM built from source for Nexus to some Xperia device – it won’t work.
Next thing, GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source (CM, PAC, …), 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.
And finally, the last. 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.
So in summary:
– this module is designed to run on vanilla or close-to-vanilla Android 6 (AOSP)
– supports “Google devices” like Nexus, HTC One Google play edition, and others running vanilla Android 6
– supports OnePlus 3T running OxygenOS 3.5
– Samsung Touchwiz, HTC Sense, MIUI, LeWa, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
– DO NOT USE WITH CUSTOM ROMS LIKE CM,AOSPA,ROOTBOX,AOKP,SLIM,CATACLYSM,OMNI AND THEIR OTHER CLONES… IT MAKES NO SENSE AND CAN CAUSE CONFLICTS AND UNEXPECTED BEHAVIOUR
– I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
– I will not provide any support for devices violating these compatibility rules.
1) Follow instructions for installation of Xposed Framework.
2) Download, GravityBox APK from the second post and install it.
Alternatively, you can download the latest GravityBox directly from Xposed Installer (search for GravityBox [MM] module).
3) Make sure GravityBox app is installed into internal memory. If it was installed into phone storage or external storage,
move it into the internal memory first (applies only to devices having additional or external storage)
7) Run Xposed installer, go to Modules menu and activate GravityBox by checking the checkbox
9) Launch GravityBox from app drawer or from Xposed installer and set options as desired
App Screenshots :
Requires Android : 4.1 and up
What’s New (Updated – December 25, 2016)
Added support for additional OP devices running OOS 3.5
— OnePlus 3 OOS 3.5 (beta 7)
— OnePlus 2 OOS 3.5.5 (official)
– Updated Russian translations (thanks to gaich)
– Updated Chinese (Simplified) translations (thanks to liveasx)
Download Size : 4.33 MB(APK)