[APP][LP][XPOSED] GravityBox v5.6.0 - tweak box for Android 5 [23/09/2018]

Search This thread

slimshouki

Senior Member
Dec 5, 2012
713
142
It's hardly possible to have similar effect than on KitKat due to nature of recents in LP. They have completely different layout and functionality. E.g. it's possible to dismiss only those tasks that are visible since there are no views at all for those tasks that are currently not on screen. So GB has to clear visible stack than check if there are more tasks available, and if yes, wait a bit until recents panel creates views for those tasks that should become visible and only then it's possible to dismiss them. This results in effect you described. I was trying many different approaches but this is the best I could come up with so far (spent quite a lot of time with it to figure it out). If there's anyone having experience with different implementation seen in some of the custom ROMs that seems to work better, I can look into it again.


I was kind of waiting for who is going to be the first to ask this :)
Long-press would be suitable but cannot be used as it's already occupied.
Looks like having another option is inevitable.


I highly doubt GB has anything to do with this app. I just don't see any reason. GB is operating within system processes like SystemUI and services. It doesn't change anything about 3rd party apps.

I was skeptical about that but now i am sure its GB causing the issue. I disabled all other modules except GB and its still causing the symptoms. As soon as I disabled GravityBox, everything come back to normal. I tried this on different device and its working fine. May be because i modded systemui and android. Policy. Jar before appling xposed? But why thjs specific app
 

trancinguy

Senior Member
Feb 4, 2013
352
82
Hi, a fatality had occurred:

05-31 09:09:57.971 W/ContextImpl(1257): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1327 com.ceco.lollipop.gravitybox.ModHwKeys.showAppLauncher:1463 com.ceco.lollipop.gravitybox.ModHwKeys.performAction:1141 com.ceco.lollipop.gravitybox.ModHwKeys.access$53:1114 com.ceco.lollipop.gravitybox.ModHwKeys$13.beforeHookedMethod:580


05-31 09:14:24.002 I/ActivityManager(1257): START u0 {act=gravitybox.intent.action.LAUNCH_ACTION flg=0x10008000 cmp=com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity bnds=[447,1532][648,1784] (has extras)} from uid 10024 on display 0


05-31 09:14:24.030 V/WindowManager(1257): addAppToken: AppWindowToken{1f2fd66c token=Token{1038631f ActivityRecord{191b36be u0 com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity t1036}}} to stack=1 task=1036 at 1


05-31 09:14:25.144 W/PackageManager(4790): Failure retrieving resources for com.ceco.lollipop.gravitybox: Resource ID #0x0


05-31 09:14:26.066 I/ActivityManager(1257): START u0 {act=gravitybox.intent.action.LAUNCH_ACTION flg=0x10008000 cmp=com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity bnds=[648,1532][849,1784] (has extras)} from uid 10024 on display 0


05-31 09:14:26.071 V/WindowManager(1257): addAppToken: AppWindowToken{200249a3 token=Token{37c254d2 ActivityRecord{27c1e35d u0 com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity t1088}}} to stack=1 task=1088 at 0


05-31 09:14:28.381 I/ActivityManager(1257): Killing 32300:com.ceco.lollipop.gravitybox/u0a97 (adj 9): remove task


05-31 09:14:28.466 W/ActivityManager(1257): Scheduling restart of crashed service com.ceco.lollipop.gravitybox/.GravityBoxService in 1000ms


05-31 09:14:28.466 W/ActivityManager(1257): Scheduling restart of crashed service com.ceco.lollipop.gravitybox/.RecordingService in 11000ms


05-31 09:14:29.555 I/ActivityManager(1257): Start proc 18009:com.ceco.lollipop.gravitybox/u0a97 for service com.ceco.lollipop.gravitybox/.GravityBoxService


05-31 09:14:29.587 W/XPrivacy(18009): Hooking package=com.ceco.lollipop.gravitybox


05-31 09:14:29.708 E/AndroidRuntime(18009): FATAL EXCEPTION: IntentService[GravityBoxService]


05-31 09:14:29.708 E/AndroidRuntime(18009): Process: com.ceco.lollipop.gravitybox, PID: 18009


05-31 09:14:29.708 E/AndroidRuntime(18009): *** at com.ceco.lollipop.gravitybox.GravityBoxService.onHandleIntent(GravityBoxService.java:46)


05-31 09:14:32.916 I/ActivityManager(1257): Process com.ceco.lollipop.gravitybox (pid 18009) has died


05-31 09:14:32.916 W/ActivityManager(1257): Scheduling restart of crashed service com.ceco.lollipop.gravitybox/.GravityBoxService in 4000ms


05-31 09:14:35.224 W/ContextImpl(1257): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1327 com.ceco.lollipop.gravitybox.ModHwKeys.showAppLauncher:1463 com.ceco.lollipop.gravitybox.ModHwKeys.performAction:1141 com.ceco.lollipop.gravitybox.ModHwKeys.access$53:1114 com.ceco.lollipop.gravitybox.ModHwKeys$13.beforeHookedMethod:580


05-31 09:14:56.632 I/ActivityManager(1257): START u0 {act=gravitybox.intent.action.LAUNCH_ACTION flg=0x14008000 cmp=com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity (has extras)} from uid 10022 on display 0


05-31 09:14:56.643 V/WindowManager(1257): addAppToken: AppWindowToken{27ba4286 token=Token{adae761 ActivityRecord{1a53fac8 u0 com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity t1090}}} to stack=1 task=1090 at 0


05-31 09:14:56.752 I/ActivityManager(1257): Start proc 18122:com.ceco.lollipop.gravitybox/u0a97 for activity com.ceco.lollipop.gravitybox/.shortcuts.LaunchActivity


05-31 09:14:56.807 W/XPrivacy(18122): Hooking package=com.ceco.lollipop.gravitybox


05-31 09:15:04.357 W/ContextImpl(1257): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1327 com.ceco.lollipop.gravitybox.ModHwKeys.showAppLauncher:1463 com.ceco.lollipop.gravitybox.ModHwKeys.performAction:1141 com.ceco.lollipop.gravitybox.ModHwKeys.access$53:1114 com.ceco.lollipop.gravitybox.ModHwKeys$13.beforeHookedMethod:580
 

C3C076

Recognized Contributor
Dec 15, 2012
7,744
24,599
Bratislava
ceco.sk.eu.org
Those are warning only. What "fatality" do you exactly mean? Something crashes or it's not working?
Also, why is Xpricacy hooking GB package? Don't try to remove any permissions from GB. They are all needed for GB to function properly. I'm not using any unnecessary permissions.
 
Last edited:

trancinguy

Senior Member
Feb 4, 2013
352
82
That's the wired thing out only said it had crashed but updated normally. But then I looked at the logcat then saw:

05-31 09:14:28.466 W/ActivityManager(1257): Scheduling restart of crashed service com.ceco.lollipop.gravitybox/.RecordingService in 11000ms


05-31 09:14:29.555 I/ActivityManager(1257): Start proc 18009:com.ceco.lollipop.gravitybox/u0a97 for service com.ceco.lollipop.gravitybox/.GravityBoxService


05-31 09:14:29.587 W/XPrivacy(18009): Hooking package=com.ceco.lollipop.gravitybox


05-31 09:14:29.708 E/AndroidRuntime(18009): FATAL EXCEPTION: IntentService[GravityBoxService]
 

C3C076

Recognized Contributor
Dec 15, 2012
7,744
24,599
Bratislava
ceco.sk.eu.org
That's the wired thing out only said it had crashed but updated normally. But then I looked at the logcat then saw:

05-31 09:14:28.466 W/ActivityManager(1257): Scheduling restart of crashed service com.ceco.lollipop.gravitybox/.RecordingService in 11000ms


05-31 09:14:29.555 I/ActivityManager(1257): Start proc 18009:com.ceco.lollipop.gravitybox/u0a97 for service com.ceco.lollipop.gravitybox/.GravityBoxService


05-31 09:14:29.587 W/XPrivacy(18009): Hooking package=com.ceco.lollipop.gravitybox


05-31 09:14:29.708 E/AndroidRuntime(18009): FATAL EXCEPTION: IntentService[GravityBoxService]
RecordingService provides screen recording. Does it work? If not make sure you use "stock binary" in GBs screen record settings.
 
  • Like
Reactions: trancinguy

Pi3rluigi

Senior Member
Sep 21, 2011
739
179
Turin
I found this, check attached
Mi3w, Ivan's 5.1.1 Lollipop
f41e1eb6025507d29fb7fca184b6263e.jpg
c717fc3b9d7729253e8d42096edc9360.jpg


Inviato dal mio MI 3W utilizzando Tapatalk
 

C3C076

Recognized Contributor
Dec 15, 2012
7,744
24,599
Bratislava
ceco.sk.eu.org
Double navigation bar height settings

Inviato dal mio MI 3W utilizzando Tapatalk
Incorrect translation for language you use.
First option is for height in portrait mode, 2nd for height in landscape mode (tablet devices that have horizontal navbar in landscape instead of vertical one).
 

Attachments

  • uploadfromtaptalk1433061906084.png
    uploadfromtaptalk1433061906084.png
    185.5 KB · Views: 596

Pi3rluigi

Senior Member
Sep 21, 2011
739
179
Turin
Incorrect translation for language you use.
First option is for height in portrait mode, 2nd for height in landscape mode (tablet devices that have horizontal navbar in landscape instead of vertical one).
It should be added , near the second
"tablet only "

So people like me that don't read all, don't bore you
[emoji2]

Inviato dal mio MI 3W utilizzando Tapatalk
 

scottnet

Senior Member
Aug 28, 2010
70
12
Tainan
feature request

1. Hide notification from certain app in the lock screen.
eg. I would like to hide Power Toggle in the lock screen.

2. Add "Auto brightness" toggle in the QuickSettings tiles.
*That's why I still need to use Power Toggle.
 
Last edited:

vkk178

Senior Member
Feb 6, 2012
757
137
Bangalore
Using GB in multi-user environment is kind of tricky. The thing is, that user only sees:
- system apps
- apps that he installed himself
This means, if you installed GB on primary account, secondary user won't have access to it. This means all the GB resources needed are unavailable while secondary account is active. This breaks features that need continuous access to GB resources. Recents panel is one of those: After changing user, recents panel is recreated but it can't find any resources during initialization since there is no GB APK available. In theory (didn't try it myself) it could be enough to simply install GB under secondary account with the same settings. You don't even need to open it to adjust settings. APK in secondary account is only needed for accessing resources such as images, strings, etc. When you make any GB configuration changes under primary account, you have to reboot for them to be applied to secondary account. It is not possible to have separate GB configs for different user accounts.

Btw, it doesn't crash on my N5 - it just simply does nothing. So logcat taken during crash would be welcome to at least prevent it.


1) boot into custom recovery and try wiping cache
if it doesn't help then:
2) boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list file
Looks like the latest 5.1.2 update fixed this crash[emoji106] .I'll keep an eye out .

Sent from my Nexus 7 using Tapatalk
 

C3C076

Recognized Contributor
Dec 15, 2012
7,744
24,599
Bratislava
ceco.sk.eu.org
1. Hide notification from certain app in the lock screen.
eg. I would like to hide Power Toggle in the lock screen.

2. Add "Auto brightness" toggle in the QuickSettings tiles.
*That's why I still need to use Power Toggle.
Tile will be considered. But it's already possible by using quick app tile and attaching "toggle auto brightness" GB action to it.
 
  • Like
Reactions: scottnet

RusherDude

Senior Member
Aug 24, 2012
2,013
614
It's hardly possible to have similar effect than on KitKat due to nature of recents in LP. They have completely different layout and functionality. E.g. it's possible to dismiss only those tasks that are visible since there are no views at all for those tasks that are currently not on screen. So GB has to clear visible stack than check if there are more tasks available, and if yes, wait a bit until recents panel creates views for those tasks that should become visible and only then it's possible to dismiss them. This results in effect you described. I was trying many different approaches but this is the best I could come up with so far (spent quite a lot of time with it to figure it out). If there's anyone having experience with different implementation seen in some of the custom ROMs that seems to work better, I can look into it again.

Oh, so they made it a pain I see. No worries, thanks a lot for the great effort! :good::good:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 578
    GravityBox - all-in-one tweak box - Xposed module for devices running AOSP Lollipop
    Version 5.6.0 [Lollipop]

    Version for JellyBean is available in this thread: http://forum.xda-developers.com/xposed/modules/app-gravitybox-v3-1-4-tweak-box-android-t2316070
    Version for KitKat is available in this thread: http://forum.xda-developers.com/xposed/modules/app-gravitybox-v3-1-5-tweak-box-android-t2554049
    Version for Marshmallow is available in this thread: http://forum.xda-developers.com/showthread.php?t=3251148

    READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
    Version for Lollipop has been tested on Nexus 5 and thus should be compatible with all the Nexus devices running stock Google system. Starting with v5.0.3alpha, compatibility with Motorola Moto G Dual SIM (and potentially other Motorola devices) has been improved.

    Introduction
    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. 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 5 (ROM close enough to AOSP).
    This project wouldn't be possible without rovo's Xposed framework, so huge kudos to him.

    Feature highlight
    --- 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

    Compatibility
    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 5 (AOSP)
    - supports "Google devices" like Nexus, HTC One Google play edition, and others running vanilla Android 5
    - supports Motorola Moto G Dual SIM running stock Lollipop
    - supports Zopo Speed 7 running Lollipop 5.1 and potentially other MediaTek devices running Lollipop 5.1
    - 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

    As is detailed in the OP, GravityBox is designed to be used with stock, vanilla AOSP ROMs, not OEM and custom ROMs. In other words, Google Play Edition and Nexus devices. All OEM ROMs (TouchWiz, Sense, Xperia, Moto, etc.), and custom ROMs (CyanogenMod, ParanoidAndroid, etc.) differ significantly in their code base from pure AOSP. And as most of these ROMs are closed source, and the developer does not have access to all the devices, it means that GravityBox is not designed for, or tested on, these devices and ROMs.

    Even though the Moto devices look like stock Android, they are as much custom under-the-hood as TouchWiz or Sense. It's just that Motorola decided to implement a skin that resembles stock Android, rather than a custom skin like Samsung has done. But the changes to the core code mean that many of GravityBox's features will not work, and actually do cause some well-known bugs. The same goes for ParanoidAndroid, there are just too many changes to the core code for GB to be reliable.

    If you choose to use GravityBox on a ROM it was never intended to be used with, then you do so at your own risk, and without any support. You should always have a good nandroid backup and be familiar with ADB and Fastboot. At any time, a ROM update or GravityBox update may cause any/all GravityBox features to break, and worst case, send your device into a bootloop. This is just an unfortunate reality of using a mod on a device it wasn't intended to be used on. Any user who wishes to improve or fix bugs on their unsupported ROM is more than welcome to download the source code for GravityBox (links to Git in the OP) and work on debugging and fixing the bugs on their own.

    Prerequisites
    To use this module, the following conditions must be met
    - You have a device running Android 5 that's based on AOSP (vanilla or close-to-vanilla Android)
    - ROM must be rooted (XposedInstaller requires root to be able to install framework into system)
    - You have working custom recovery allowing you to make a backup before installing Xposed framework

    GravityBox Lollipop version has been developed and tested on Nexus 5

    Installation
    1) Follow instructions for installation of Xposed Framework alpha version for Lollipop
    In case of Lollipop 5.1, make sure to use unofficial Xposed Framework Alpha.

    2) Download, GravityBox APK from the second post, rename it to GravityBox.apk and install it.
    Alternatively, you can download the latest GravityBox directly from Xposed Installer (search for GravityBox [LP] 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

    8) Reboot

    9) Launch GravityBox from app drawer or from Xposed installer and set options as desired

    Videos
    - Xposed framework install plus gravity box module overview (thanks to Rootjunky.com & Marshall Williams)
    - Gravity Box - What is it and How to install it (thanks to @D3VI0US)

    Documentation
    Thanks to @cadarn07, there's a comprehensive and searchable User Guide listing
    all of the GravityBox features. It's an EverNote document located at https://www.evernote.com/pub/cadarn07/gravitybox

    Reporting bugs
    If you experience problems with certain feature, provide the full-detailed info that can help me
    to reproduce the bug and attach debug.log file you'll find in:
    /data/data/de.robv.android.xposed.installer/log

    In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
    crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
    Please, don't attach big logs. Only the portion where error is clearly seen.
    Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
    Remember, this app was developed and tested on one particular device so it is not guaranteed that
    it will work flawlessly on yours.


    Click here tor ead additional, more detailed info on Reporting bugs provided by @trjlive

    Multilanguage support
    Volunteers are welcome to translate GravityBox to other languages.
    Simply download this file: https://github.com/GravityBox/GravityBox/raw/lollipop/res/values/strings.xml
    Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.

    Source code
    GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/lollipop
    If you're a dev and have some ideas for additional features, feel free to fork it, work on it
    and send the pull requests.

    Copyright notice
    https://github.com/GravityBox/GravityBox/blob/lollipop/NOTICE

    Support development
    Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!

    Info about premium features and PayPal transaction ID verification system
    1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
    As of v2.9.5, there's one premium feature: Backup/restore of GB settings.

    2) If you contributed to the project by providing translations, code fragments, or by any other way
    you can apply for a free transaction ID by contacting me via PM.

    3) Be aware that there's a system that can identify potential transaction ID
    abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
    This can also happen when you previously exposed your ID in public forum and other users took
    advantage of it. If this is the case, contact me via PM so I can issue new, special ID.
    In case you own more devices, you can use one transaction ID on up to 10 of them.

    4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
    upon verifying your ID as verification system accepts requests only from official releases of GB.
    If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
    a special hash for your build.
    If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
    it is necessary to ask for new hash everytime your new custom version is released for public use.
    These rules are based on mutual trust so please, do not violate them.

    Credits
    - @bgcngm for his code contributions to the project
    - @MohammadAG for Xperia specific contributions to the project
    - @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
    - @peptonib for starting me up with this project
    - @Tungstwenty for Fake ID vulnerability patch
    - @simmac for app icon
    - @romracer for Motorola specific code contributions
    - THL W8 owners for providing support and feedback
    - CyanogenMod project
    - ParanoidAndroid project
    - SlimBean, RootBox, AOKP, OmniROM projects
    - Sergey Margaritov for ColorPickerPreference
    - All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, ...)
    - and finally, all those who keep the project alive by supporting me via donations (you know who you are)

    Changelog
    https://github.com/GravityBox/GravityBox/blob/lollipop/CHANGELOG.txt

    XDA:DevDB Information
    GravityBox [LP] Xposed Framework Module, Xposed for all devices (see above for details)

    Contributors
    C3C076
    Source Code: https://github.com/GravityBox/GravityBox/tree/lollipop

    Xposed Package Name: com.ceco.lollipop.gravitybox

    Version Information
    Status: Stable
    Current Stable Version: 5.6.0
    Stable Release Date: 2018-09-23

    Created 2015-02-22
    Last Updated 2018-09-23
    268
    Changelog 5.6.0 - 23/09/2018
    - QuietHours: additional enhancements and redesign
    --- rules for ligts/vibrations/sounds/ringer whitelist can now be set for each time range independently
    --- manual mode has its own set of rules that are independent of automatic time ranges
    --- initial ringer whitelist for newly created time range is inherited from manual mode settings
    --- added option for controlling current mode directly from the QuietHours settings
    --- reorganized settings
    --- !!! data structure changes render existing time ranges incompatible - need to be reconfigured !!!
    - Updated Ukrainian translations (thanks to burunduk)
    - Updated Turkish translations (thanks to Fatih Firinci)
    - Updated Russian translations (thanks to gaich)

    Complete commit history for 5.5.2->5.6.0
    75
    What's missing in version for Lollipop 5.1 compared to 5.0
    - unlinked ringer/notification control volumes cannot be controlled within Sound&notification settings, only within expanded volume panel.

    What's missing in version for Lollipop compared to KitKat
    - No ring targets in lock screen - obsolete in Lollipop as there is no ring security screen available
    - No ring targets in navbar - Google replaced search panel with completely different one
    having simple circle with one target. It's not using GlowPadView anymore. In order to implement ring targets
    as we know them from Kitkat would probably be to completely replace stock search panel with the one from Kitkat
    - Brightness control currently doesn't work in lock screen as status bar is covered with keyguard panel
    - and maybe some other smaller features I forgot to mention, mainly since they were obsolete in Lollipop
    Full commit history can be found in project's github.

    Other remarks
    - Although LP comes with native "quiet hours", I decided to keep UNC Quiet hours.
    There's a freedom of choice to either use stock Interruptions system or GB's quiet hours
    - Battery style and percent revised to support new status bar which has 3 modes: normal, keyguard, header
    - Brightness control now works with Auto adjustment turned on the similar way as brightness slider in quick settings
    - Low battery warning changed as there is no Low battery warning dialog anymore
    - Ascending ringtone has been reworked completely (thanks to CM12)
    - million of other small adjustments - you'll find out for yourself :)
    58
    New version announcement

    Version 5.1.0 available

    Changelog 5.1.0 - 16/05/2015
    - Adjusted for Lollipop 5.1 compatibility

    Important info
    - in case you are running Lollipop 5.1, make sure you have the latest unofficial Xposed Framework SuperAlpha for Lollipop 5.1 before installing GB
    - this version was tested on Nexus 5 running:
    --- stock 5.0.1 (LRX22C)
    --- stock 5.1.0 (LMY47I)
    --- AOSP 5.1.1 built from source (LMY47V)
    It is not guaranteed it will work on other, non-Google/non-AOSP devices, so issues should be expected.
    Make sure you have a nandroid backup before trying.
    - avoid using soft reboot feature as it will most likely cause your apps to be rebuilt (optimized) from scratch which takes some time
    - check the 3rd post to find out what's missing in version 5.1 compared to 5.0

    Complete commit history for 5.0.10->5.1.0
    46
    Plans are as follows.
    - to release another unofficial (super alpha) version of xposed framework for 5.1.0 and 5.1.1
    - to adjust GravityBox for compatibility with 5.1.0 and 5.1.1 (this will take some time).
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone