yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] DeKiesel:
Hi,

I am running GB on aokp on my galaxy s5.

The navbar is always on, even when the master switch is set to deactivated. Is this a compatibilty issue and i should forget it or is there a workaround?
[Xposed Framework Modules] fatspirit:
Turn it on, set height to 0. And yes, it's incompatibility.

---------- Post added at 15:08 ---------- Previous post was at 15:04 ----------

Try NoVPNMonitor module.
[Xposed Framework Modules] Tel864:
Just a thought since I see Moto mentioned lately. I've been running GB on 3 Moto G 3rd gen's, all on MM since the MM soak test I was in with no problems at all.
[Xposed Framework Modules] gmi78:
Magic module:good:

Its possible to add an option for swipe2sleep on navbar?
[Xposed Framework Modules] nupi:
Little confused regarding Xperia MM. I thought that was a non stock ROM but there are Xperia fixes in the change log and it seems to work reasonably well. What's the current stance on that?
[Xposed Framework Modules] iamelton:
the rom is not officially supported (as stated in OP), but if there are debug/error logs and help in testing provided, C3C076 has been able to enhance GB to fix issues in the rom..
[Xposed Framework Modules] fatspirit:
Stock is not always equal to AOSP. Stock firmware on Nexus phone is AOSP, but stock firmware on most Sony devices is not.
[Xposed Framework Modules] karige:
In-call vibration not workin
[Xposed Framework Modules] Nergal di Cuthah:
Wow, try reporting this again, but this time give some information.

Or was it your intent that we be psychic and know your device, rom, logs without any input from you
[Xposed Framework Modules] karige:
Moto g 2014 ,stock ROM MM. Tried the module on/off then restart, also tried the in-call vibration option on/off reboot but all in vain. Still can't activate the in-call vibration. Thanks again for my concern.
[Xposed Framework Modules] TENN3R:
Just wanted to try on TW (yes I have read the warnings for only AOSP compatible)

But everything works for me so far, I tried almost everything, using S6 android 6.0.1, so just telling you it works with no problems, crashes, slowdowns or something :good:
[Xposed Framework Modules] mayanks_098:
I'm using Nexus 6p. Just for testing, I enabled Notification heads up feature (from statusbar tweaks). Now whenever I was receiving a whatsapp message, it shows a whatsapp floating notification at the top of the screen. The notification hides all the other content on the screen, i.e. it is displayed "on top" of everything. I have to swipe it away (from top) or wait for it to disappear (which is now set to 1 seconds from earlier 5 seconds from the same notifications heads up settings). Thing is both these are inconvenient and break the flow of things I'm doing because you keep getting whatsapp messages so frequently.

The only solution I have found so far is to disable gravity box and reboot. But then I loose all the gravity box tweaks as well. Is this a bug? Is there a solution?
[Xposed Framework Modules] buffal0b1ll:
Untick notification heads up and control them with system settings.apps.app.allow peeking
[Xposed Framework Modules] C3C076:
Enabling master switch for heads up itself doesn't change any app notification behavior apart from controlling global heads up window timeout. Additional heads up behavior is controlled only within Ultimate notification control which allows to set default rules and per-app rules.
[Xposed Framework Modules] mayanks_098:
thanks. i have tried disabling notification heads up already, but that doesnt work. only when i disable gravity box, the problem goes away. ill try "allow peeking" to see if solves the issue.

I know. But the thing is nothing is enabled inside Ultimate notification control either. Strange.
[Xposed Framework Modules] Darayavahus:
Hi there. I have found a minor issue.

I can't adjust the duration time of expendable volume panel in. It hides after 10 sec or even more, or when I click on the screen. Changing time in these settings doesn't make any difference at all.

Using xperia z3 with marshmallow 6.0.1 based on stock kernel

Gravity ver. 6.1.1

EDIT : I'm terribly sorry. Made some forum research. It comes out, that it was the Twilight app interfering with accessibility somehow. Don't know how to fix it though..
[Xposed Framework Modules] cge_95:
Hi,

I can't anymore turn ON/OFF expanded desktop from Tasker by sending action: gravitybox.intent.action.TOGGLE_EXPANDED_DESKTOP with extra set to hwKeyValue=1 or -1, it always behaves as toggle.

Is there a known issue about it ?

Christophe
[Xposed Framework Modules] ithehappy:
A query, would the disable Heads up and restore ticker notification option work on Marshmallow TouchWiz ROM?
[Xposed Framework Modules] fatspirit:
Why don't you try? Since GW is incompatible with TW that's the only way to find it out.
[Xposed Framework Modules] tokyostomp:
I was wondering if there were any plans to make the ExpandableVolume a standalone module like what was did with the ICS version. I've tried that one and it doesn't work with MM.

I'd like this as I am running a rom (Venom on a HTC One M9) with some redundant features and while it doesn't interfere with it, i'd like to lighten my load and minimize any possible problems.
[Xposed Framework Modules] fatspirit:
This was probably made by someone else since source code is available.
[Xposed Framework Modules] iamelton:
certain features working in the custom rom does not mean that the rom is supported (by the dev)..

it is still not supported.. read OP carefully..
[Xposed Framework Modules] likurik:
:good:
[Xposed Framework Modules] Ofthecats:
Is anyone having conflicts with LED management apps? I use light manager.

In ultimate notification control, if LED is set to either original or off, light manager does not show LED.

If I have Gravitybox LED is set to override, it works but overrides the color set in light manager.
[Xposed Framework Modules] blk_jack:
Does binding long press recents to switch to last app work for anybody?

Just loads recents for me, no matter what button or modifier I set it to.

This could be because I'm running the Sony concept ROM which is pretty much AOSP and from what the logs show, GB is detecting it as Xperia, which leads me to think that that could be affecting things since Sony's software is usually a lot more modified than what I'm running.

Or it's not fully functional yet! Either way I'm just curious.
[Xposed Framework Modules] C3C076:
Well, this shut down dialog doesn't come from GB. It comes from the system. What GB does is tells the power manager to reboot to recovery. System handles the rest, including showing reboot dialog. Pitty they changed that. Not sure if I can do something about it.

It's already there and working fine here.

Check the third post for info about System tuner.

TL;DR: don't use it when using QS management in GB.

Note, that if your device has soft keys (navigation bar) it is necessary to enable navbar tweaks to have full support for Key Actions.

Another reason could be incompatibility between your ROM and GB.
[Xposed Framework Modules] blk_jack:
You were right with your first theory. I didn't have the full navbar tweaks enabled. Once I enabled it and rebooted, the switching between last app worked perfectly. Thank you!
[Xposed Framework Modules] FcukBloat:
thanks mate actually I was using the stock "clear all" button (probably a sony addition as in aosp it shouldn't be present by default?) but after adding the one in GB it works fine :) only problem is that now I have two buttons for the same thing, but well can live with that :o :p
[Xposed Framework Modules] PeQuEsan:
Any chance to add feature to autoexpand notifications in lock screen and headsup also? I'd say no because in marshmallow when you pull down a notification box it expands notification bar instead of showing expanded content inside same notification. But I must ask. :) Current notifications in headsup and lockscreen are pretty much useless if you've got let's say 10 unread whatsapps... :(
[Xposed Framework Modules] slashshek:
Is it possible to add the feature that long press of 'clear all recent button' to clear all but only keep the current app

Which like KK version

Thanks for the app so much
[Xposed Framework Modules] ptzink:
Volume keys skip track bug

C3C076, thanks for the awesome work on GB. I purchased the unlocker a while back and never upgrade android until there is a compatible version of GB. :)

Most everything seems to be working well for me, but I wanted to report a bug with the "volume keys skip track" on GBMM on the Nexus 5. The first long press of the volume up button (while the screen is off) will just increase the volume as will subsequent long presses. I did notice however that if I toggle (quick press) the volume down button and then long press the volume up button, it will skip to the next track as expected. However, subsequent long presses do not advance the track unless you first quick press the volume down button again. The same is true in reverse when trying to go to the previous track. Strange behavior. If you would like a log, let me know.

Thanks again for the great work!
[Xposed Framework Modules] C3C076:
I could reuse the stock one. All I need to know is image button resource name.

Can be found out only by decompiling SystemUI and checking xml layout for recents panel.

Hmm. Never came across such issue. It works pretty consistent for me on my N5 using Shuffle player.

What about other xposed modules? If you run more, you can try disabling all of them but GB to check if behavior changes.
[Xposed Framework Modules] zeekx4:
I was just reading through the thread for comments on this feature. While using Google Play Music, the feature depends on the output device. When I listen via speakers, the long-press works as intended. While streaming to Chromecast, the long press doesn't work at all. I also tried ptzink's method of tapping, then long-pressing, without any effect. It seems that volume media controls do not work in Google Play Music when casting.

Please let me know if I can provide any logs or additional info. I can also try some testing, if it would be helpful.

By the way: N5, stock, rooted, ElementalX, and newest Xposed/GB.
[Xposed Framework Modules] ptzink:
Yeah, very strange. For more info, I was listening to music with the stock Google Play Music player (boy, Google does suck with naming things, eh). Also, the only other xposed modules I am running are SwypeTweaks, YouTube AdAway, and Greenify. Doesn't seem like any of those would affect media control, but I will try disabling them this afternoon. Thanks.
[Xposed Framework Modules] Hawtpants:
Hi there! Just a few quality of life suggestions:

- option to remove page navigation dot on home screen

- option to remove icon labels on home screen

- more options to customize the lockscreen.. currently I am using a lockscreen replacer (acdisplay) because GravityBox doesn't work for this on Zenfone 2.
[Xposed Framework Modules] Blade2014:
1. Use custom launcher

2. Use custom launcher

3. Zenfone 2' ROM is not on the supported list of roms
[Xposed Framework Modules] Hawtpants:
I don't want to, I want to remain as stock as possible to prevent instability and memory issues. ZenUI could as well be supported, since everything works except for the lockscreen shortcuts.
[Xposed Framework Modules] SergioRmz:
You can use Nova. You can customize it and the look is still like stock launcher plus it's really stable.
[Xposed Framework Modules] Saad_aslam:
Phone locked.

Length of my PIN was more than 4, I checked the Quick Unlock feature, rebooted the phone and now the phone is locked. Not unlocking after I enter my PIN.

Please help. Thanks.

Nexus 5.
[Xposed Framework Modules] Ja_som:
Reboot to TWRP > Advanced > Terminal command

Create a file /data/data/de.robv.android.xposed.installer/conf/disabled,*reboot to system, open GB disable Quick Unlock. Via your root explorer delete file "disabled" and reboot device, or reboot to TWRP and delete that file...
[Xposed Framework Modules] cge_95:
I tried to downgrade GB to several versions and I can say that this feature was broken between 6.08 and 6.1.0 since the latest working version is 6.0.8

Christophe
[Xposed Framework Modules] C3C076:
There must be some accessibility service active that causes longer volume panel timeout (15secs). GravityBox doesn't change timeout when it is overridden by some accessibility service. Might change in the future as this seems to be a trouble for many.

GravityBox Actions went through a massive rework. You should use different extra: enable (boolean), values: true to turn on ED, false to turn off ED.

All ticker functionality has been completely purged from AOSP since Marshmallow. There is no easy way to get it back using xposed.
[Xposed Framework Modules] silentvisitor:
[MENTION=5008415]C3C076[/MENTION]

Hi,

Got a very minor issue.

Battery tile showing different values. Value in tile stuck at 14%. Other is fine.

Please see screenshots.

Thanks !
[Xposed Framework Modules] grubber24:
Could you please tell me how did you get that notification bar? Live the customization you have done!

Moto X 2014 XT1092
[Xposed Framework Modules] silentvisitor:
Sure.

Its a combination of 2 Xposed modules :

Android N-ify

Gravitybox 6.1.1

And my wallpaper ;)

Here it is. Enjoy :good:
[Xposed Framework Modules] grubber24:
Thanks for the image! I have both the modules. Can you elaborate how you did it?

PS: I am running stock 6.0 on Moto X 2014.

Moto X 2014 XT1092
[Xposed Framework Modules] silentvisitor:
Enable Android N-ify and set portrait custom image for Quick Setting Tile in Gravity Box.
[Xposed Framework Modules] grubber24:
I have already done that. (Screenshots attached). Do I need to do anything else for getting it? Thanks in anticipation.

Moto X 2014 XT1092
[Xposed Framework Modules] silentvisitor:
You're using very old build of Android N-ify.

Use latest Experimental #43 from its thread.
[Xposed Framework Modules] silentvisitor:
Here's my setup.
[Xposed Framework Modules] grubber24:
Ahh! Got it working finally. Thanks a lot![emoji3]

Moto X 2014 XT1092
[Xposed Framework Modules] silentvisitor:
Glad to be of help :good:
[Xposed Framework Modules] Giozer:
Hello.

I have a Nexus 6P, with stock ROM rooted.

I recently installed Xposed and Gravity Box but I can not close the current application, use the Back button of the navbar.

In recent months I used a Sony Xperia Z1 and I could do this.

Maybe something wrong? Can anyone help me find the solution?

Another small problem: with the "Close all" button in the latest applications, you do not delete all applications with a single command, but if there are many applications I have to run the command multiple times. it's normal?

Thank you.
[Xposed Framework Modules] moriel5:
I bug that I noticed a long time ago (but forgot about due to other responsibilities), is that there's a (very) noticeable pause between pressing reboot (doesn't matter which kind) and the action happening.

No freeze, just the action happens a few moments after it should.

At first I had thought that it doesn't work, untill it rebooted in the midst of opening the settings.
[Xposed Framework Modules] Nergal di Cuthah:
on what phone? My nexus 6 shows a rebooting dialog box with a rotating circle. My assumption is the delay is apps and services properly ending
[Xposed Framework Modules] moriel5:
Doogee X5 Pro, running SnowCatPDA's AOSP 6.0 rom.

No spinning circle for me.

However, from Xposed Framework, not only there is no animation, there is no delay, either, it immediately reboots/whatever I chose.
[Xposed Framework Modules] silentvisitor:
Just noticed after a reboot QS panel shows a random mix of tiles from my ROM and GB. I have to go into QS Management and hit Save.

Any advice? :)
[Xposed Framework Modules] Nergal di Cuthah:
not use it with incompatible ROMs ;)
[Xposed Framework Modules] silentvisitor:
Seemingly its working quite good despite this warning ;)
[Xposed Framework Modules] Nergal di Cuthah:
ummm wait didn't you just report the opposite? [emoji6]
[Xposed Framework Modules] silentvisitor:
Ummm....no.....confirm ;)
[Xposed Framework Modules] Nergal di Cuthah:
huh? You asked for advice on QS showing your ROM's quicksettings as well as "GB" ones. An overwhelming number of reports of incompatibilities with other ROMs, that I've read in this and the Android5 version of GB threads, echo your exact issue or at least occur due to Quicksettings. The developer has, in the past, confirmed that the quicksettings s/he uses as template for (and to make up the deficiencies of) are the ones that AOSP provides. Thus my answer to read the section I included from the first post. (Done with winky face now, sorry)
[Xposed Framework Modules] silentvisitor:
Thanks for all help :good:
[Xposed Framework Modules] lulli1:
if I'm right, you use android n-ify module together with GB, isn't it? Uncheck n-ify in your xposed installer app, reboot, and check if your problem still exists.
[Xposed Framework Modules] silentvisitor:
Thanks for reply. Yes you're right.

I disabled QuickSettings in GB. I needed it only for Battery tile.
[Xposed Framework Modules] sankarshan:
I don't know if I can request for a feature here. So, my request is here.

Since ,there are HUGE number of settings/options in gravity box, it will be very much helpful if you can add a "search" option to search inside the app for a specific setting/option.

Thank you.
[Xposed Framework Modules] Reechings:
[MENTION=5008415]C3C076[/MENTION]

Any chance of making it so lockscreen opacity for custom images can be adjusted higher to remove the dark overlay? When I set it to 100% it still has the default overlay. The module Bright Lockscreen no longer seems to be getting updated and is causing some bootloops on newest version of xposed framework.

Thanks so much if possible!
[Xposed Framework Modules] C3C076:
Make sure to check Navigaction keys actions section of GravityBox settings how you have back key single-press action defined. If it's set to Default and back key still doesn't work, check if you run other modules that could introduce such anomaly.

Regarding "Close all". Depends if you have "Clear visible only" checked. If it's checked, only visible stack of apps is cleared.

GravityBox uses standard power manager API for rebooting. The rest depends on how system handles it and is device specific.

If vendor of your device messed this part then it's a pity.

This is already on my list but never got to it due to other priorities.
[Xposed Framework Modules] creeve4:
[MENTION=5008415]C3C076[/MENTION] I've found one minor issue related to the GravityBox Torch:

When the torch is turned on a notification is displayed that allows you to "Touch to turn off." When this notification is double-tapped from the lockscreen, the lockscreen is dismissed and after a delay of about 2 seconds, the home screen is then shown.

Also, when the Lockscreen torch feature is activated, it uses the GravityBox torch implementation by default. Will you consider adding the option to use the stock torch implementation?

Nexus 5, stock 6.0.1, GB 6.1.1
[Xposed Framework Modules] moriel5:
Ah, thanks in any case.

Perhaps you could add an option to hook into Xposed Downloader's implementation? Since that way there is no delay.

And after updating the rom to v2, the issue is present only with the soft-reboot option.
[Xposed Framework Modules] Nitrooo84:
It would be very nice to be able to set a value for the auto-fading of the navbar buttons, so that you can select a specific intensity to which the buttons are faded and not hide them completely. Is this feature on your todo list?
[Xposed Framework Modules] lyim:
It compatible gravitybox in wolfloaf v3 mm rom ?
[Xposed Framework Modules] Nergal di Cuthah:
read post 1

It would be impossible for anybody to know every single ROM. If your ROM is AOSP (not near AOSP) it WILL work; if your ROM is near/based-on AOSP GravityBox will work only depending on what a developer has changed in the ROM. It is not suggested for someone in the second category (or ROMs based on CM, Touchwiz, Sense etc).

Basically You can try it and if it breaks things than the answer is no.

Also next time more details like what phone etc, because just tapatalk with some archaic name like SM-G935F just forces every reader (be they member like me or , more so, the developer) who might wish to help you search the internet to find what device it is, thus less likely to help with courtesy.

(To future readers its a Samsung Galaxy S7 Edge)
[Xposed Framework Modules] lyim:
How to change this background to black ?

---------- Post added at 09:42 PM ---------- Previous post was at 09:42 PM ----------
[Xposed Framework Modules] Nergal di Cuthah:
that looks very un-AOSP. Am I to assume you ignored the last response?
[Xposed Framework Modules] JohnHorus:
[MENTION=5008415]C3C076[/MENTION] I'm still having that issue where enabling volume long press to skip tracks disables volume control while the screen is off.

I also have the option to make media the default volume enabled, if that might make any difference.

Do you have any idea what might be the problem? Is there some log I could give you that would tell you what's going on?

My phone is HTC One M8, running the stock GPE ROM.
[Xposed Framework Modules] marbertshere:
I would say you should hit up the Samsung theme store and download a dark theme from there. GB is not going to play nice with TW.
[Xposed Framework Modules] moriel5:
This was in the Lollipop GB thread, gentlemen (sorry, couldn't resist).

But seriously, I think it would be a great additon to GB in general, not just in LP.

I would love to have the QS to be paginated.

Oh, and screen record is not working for me with GB binary, it fails to save.

Log imminent.

AOSP 6.0 x32 on Doogee X5 Pro, 3rd Party rom.
[Xposed Framework Modules] moriel5:
And here it is.
[Xposed Framework Modules] platon.77:
HI guys!!! Umi Touch Android 6.0 arm 64. have installed xposed framework and installer all as instruction. Gravitybox downloaded but doesn't work. System framework doesn't responce. What's wrong?
[Xposed Framework Modules] technolyze:
Changing volume while screen is off doesn't seem to work when 'Volume keys skip track' is enabled but lockscreen is set to none. I think it has something to do with ambient display? I'm on Nexus 5 though.
[Xposed Framework Modules] C3C076:
Hard to tell. I tested once again on my devices also with forced media control enabled and it worked just fine. Although it's a GPE ROM there still might be some differences in implementation compared to AOSP.

You can provide an xposed log but I can't promise I'll be actually able to do something about it.

This is not planned as such change is quite major and requires changes in QS panel layout which is something that's hard to achieve using xposed. Moreover such major change to layout could break compatibility with various devices where QS management already works to a certain level.

Alternative screen record binary is currently broken as I don't have environment for building AOSP from source that would allow me to build modified screenrecord binary myself.

This error is a result of module not being loaded by Xposed framework. Taking a look at xposed error log would tell why. Log can be exported from within Xposed Installer app.
[Xposed Framework Modules] C3C076:
I can confirm volume control doesn't work with lock screen disabled. Not sure why, though.
[Xposed Framework Modules] moriel5:
Thanks, although I'm a bit miffed, I undestand that it's better this way.

And what do you mean by not having the environment for building AOSP, in case someone can help you out with this.
[Xposed Framework Modules] ManDone.vRs:
Hy [MENTION=5008415]C3C076[/MENTION] , I just wanted to know why not safe volume warning is not working on my S7 Edge stock rom , rooted , odex ! Sorry for my noob question ! Everything else are working for me .
[Xposed Framework Modules] :
T read the op