yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] kingvortex:
This module cycles pin/pass/pattern. It's as close as you're going to get to what you want, as true randomisation would lock you out of your device.

Anyway, this is off topic in here, so if this isnt what you want, then further requests should be made in the module request thread here. ?
[Xposed Framework Modules] trjlive:
Are you referring to the relative bottom or the physical bottom? The option in GB to keep navbar on bottom actually keeps the navbar on the physical bottom of the device, which can in turn end up being on the relative side of the screen when rotated in landscape orientation. So to clarify, the "keep navbar on bottom" will keep the navbar on the side of the screen adjacent to the LED light, regardless of which way you rotate. The stock Android method keeps the navbar on the relative bottom of the screen, which changes as you rotate the device.

However, let me also mention that there are several bugs, even with stock AOSP like Nexus and GPE devices, when you mess with the location of the navbar. C3 has tried to fix them as best as he could, but they still exist. So if you enable the option to keep navbar on physical bottom of device, you may get some problems with certain apps or sometimes the keys are non-responsive. This is just a result of GB having to brute-force some code to keep the navbar in the same physical location, and the OS doesn't like when that happens. So you can use this function and it will generally work, but just understand that there are some bugs that can't really be improved any further.
[Xposed Framework Modules] afrizal87:
Thanks brauw!!
[Xposed Framework Modules] ahow628:
Oh, wow. Ok. Seems like some rewording could help significantly since a Google search turned up this same misunderstanding now that I know about it.

"Forces navbar on the bottom in landscape mode" to me means it is in the down direction since the term bottom is relative to the orientation as far as I understand it.

Perhaps some help text that says something like "Forces navbar to the right edge in landscape mode on device that move it to the bottom such as the Nexus 7 and 10." Or something similar.
[Xposed Framework Modules] xswistaqx:
I've found a bug related to PIE controls and Sony 4.4.2 on Xperia Z.

If I enable PIE and disable the navigation bar through the master switch in navigation bar submenu the call button disappears in the dialer app. Also two additional blank options appear in the dialer's submenu.

An easy workaround is to set the navigation bar's size to 0% for all layouts and the call button will be in it's place.

I don't think that this is GravityBoxs' fault. Seems to be Sony's fault but maybe you'll find a workaround and even if not then maybe someone will find my solution helpful ;)
[Xposed Framework Modules] Neoistheone2000:
Don't know if it's already a feature or not but is there a way to disable the PIN requirement when a VPN is setup?
[Xposed Framework Modules] trjlive:
This is a standard Android security feature, and not something that can be easily changed. Though, personally, I'm not sure why you'd want to risk someone gaining unauthorized access to your VPN account if your device is lost or stolen.

There are some hacks to disable the PIN when using VPN that seem to work on some devices but not on others. Take a look at this thread, see if any of these hacks work. If not, there's probably not much else you can do.

http://xdaforums.com/galaxy-s3/help/vpn-password-lock-t1717892

Another option, just set a pattern lock as a simple left to right or right to left line, then you can quickly unlock with a swipe.

---------- Post added at 10:25 AM ---------- Previous post was at 10:16 AM ----------

Yes this is definitely Sony's fault, they change so much of the underlying Android core code, that's one of the reasons why your device isn't supported. You can use GravityBox for any features that work on your device, but there are known bugs and some features just don't work properly.
[Xposed Framework Modules] ahow628:
Alright, I tried the navbar options every which way on my Nexus 7 2013 and none of them put the navbar on the right edge in landscape.

Ended up finding the Phab7 Xposed module which is working so I'll just stick with that for now.
[Xposed Framework Modules] vishal91:
after enabling Gravity and after first reboot i loss my expandable volume panel .............

Can any one help me knowing how can i enable Expandable Volume panel ? :confused::confused:
[Xposed Framework Modules] kingvortex:
Media tweaks -> Expandable volume panel.
[Xposed Framework Modules] aoprea:
I cant find option for quiet hours ... Like in cm 11... Not exist in gravitibox 3.2.5 ?
[Xposed Framework Modules] fbf2201:
It's under Ultimate notification control
[Xposed Framework Modules] kingvortex:
It's in the Ultimate Notification Control section. In that section, press the overflow key.

It only applies to notifications, not phone calls.
[Xposed Framework Modules] aoprea:
Loool.... Very bad position of menu for quiet hours ... Thanks
[Xposed Framework Modules] GBP85:
While I didn't try any of the hacks on the thread that was linked, I simply just reconfigured my router to use OpenVPN and that doesn't require a secure lockscreen.

Personally, I would love to see the requirement removed from Android myself. I only VPN into my home network when I don't trust the network I'm connected or if the connected network blocks me from accessing basic services like Google. Yes, I have been on a public WiFi and my phone cannot connect to Google services, and their IT crew doesn't understand what I tell them. :(
[Xposed Framework Modules] trjlive:
Why is it a bad position for quiet hours? It's a setting of Ultimate Notification Control and only applies to notifications, so it's in the UNC menu. Putting the option anywhere else wouldn't make any sense, it would only serve to confuse users who would think the quiet hours were for the entire device. But I'm curious, where would you suggest the notification quiet hours menu be put?
[Xposed Framework Modules] cadarn07:
It's possible that he/she doesn't mean it should be moved to another spot in the app, but that the UNC UI should be reworked so that the quiet hours option isn't up in the top right corner. There are a million options in GB (more or less, haha) and I can't think of another place in the app that uses a three-dot menu in the corner like that. That's made many new users miss it completely.

That being said, I don't really think it's a big deal (once you notice the menu, you don't forget) but it might be what the other person was talking about.
[Xposed Framework Modules] yojlik:
Did something change in the current version? Ever since updating I am getting a "Headphones disconnected" toast frequently. I can't tell what's triggering it but it happens when the screen comes on... sometimes. I've never seen the toast before updating.

The only changes I've made was to change the nav bar to Android L icons. I can't remember if the toast appeared before rebooting to enable nav bar options (I had never used them prior to yesterday).

Has anyone seen this or even know what I'm talking about?

edit: Now that I'm looking into this it seems like something that (seemingly random?) apps have caused for years. I see search results and screenshots dating back at least two years. I haven't installed any new apps and it looks like only one could have anything to do with the audio at all.

Now I'm thinking it isn't GravityBox at all, which unfortunately makes things harder to diagnose.
[Xposed Framework Modules] denzel09:
This doesn't happen on my side. Last gb version. Never seen that toast. Are you sure that before it does not appear already?
[Xposed Framework Modules] yojlik:
Yeah, just doing a search for "headphones disconnected nexus 5" it seems like this is something that happens. I wonder if there's a way to trace what app is generating a toast... Is that something that would show in the log?
[Xposed Framework Modules] drawde40599:
Dose the HTC one (m8) GPE fall into this "issue"
[Xposed Framework Modules] denzel09:
Mmm good question.. Try to download from play store SysLog app and take all logs. Then at same time you can use CatLog for a real time monitor. You should got it in these 2 ways.
[Xposed Framework Modules] yojlik:
I've never used SysLog before. This tool will work nicely in trying to track it down, thanks much! :)
[Xposed Framework Modules] lostangelintx:
I'm not having any luck running this. I may not know enough to play with xposed, but I'm trying anyway.

All I get is this (attached screen shot) when I try to run it.

Running stock rooted unlocked s-off HTC One M8 (ATT variant)

Anyone can help me? I'm not sure how to get log files, or anything like that. Rookie here for the most part. Sorry.
[Xposed Framework Modules] jonnyg1097:
Are you trying to run the app from a restore done? I've only gotten that message before when I did a restore on my phone after flashing a rom. I only fixed that by uninstalling it and reinstalling it.

Also be sure to restart your phone before opening it up for it to work. And making sure it is activated in the modules section.

If those are already done then I have no idea.
[Xposed Framework Modules] nadiros:
-Deleted-
[Xposed Framework Modules] Ok_Kaleidoscope5109:
Hi [MENTION=5008415]C3C076[/MENTION]. I use UNC only for Heads Up control for the Dialer so I get the unobtrusive dialer that pops up. The default settings for LED is set to "Original (From App)" because I use Light Flow.

Here's what I noticed though: when Gmail comes in, my phone beeps and notifies as expected, but the light that flashes is white (Light Flow is set to green). When I power my screen on check my Light Flow widget, it shows that Gmail has triggered a notification. After I power the screen back off (notification still active), the light starts flashing green.

So I wondered if it was Light Flow malfunctioning... so I played around with it, but still nothing. I then checked UNC and the LED option was "Original (From App)." I thought this meant that UNC doesn't override anything and has a hands off approach. But I tried "Off" for the sake of trying that out, and guess what? Incoming Gmails flash green immediately.

Is that what's supposed to happen? I know having UNC and Light Flow is dangerous, but shouldn't the Original option never touch LEDs to begin with? It shouldn't make sense that I had to switch it to "Off." If anything, "off" should disable the blinking LED, no?

The way I see it is that before this dilemma, I didn't even have UNC a week ago. To me, no UNC should behave like "Original (From App)," meaning settings are untouched, and before UNC, my Light Flow settings were PERFECT. So it seems to me UNC seems to be adding some additional behavior to the LED even though it shouldn't under the default settings.

I will say however, that when I tested by texting myself, Light Flow took control immediately without the need to refresh my screen on and off. It seems to be an issue for Gmail. Hangouts also causes my phone to blink without turning UNC to "Off"
[Xposed Framework Modules] trjlive:
Well, for starters, I'm going to recommend you go back to the OP and read it all the way through. You'll learn that your device is not supported by GravityBox. You are using an HTC One M8, with Sense framework. GravityBox is only designed for pure AOSP, which means Nexus or GPE devices.

So even if you get it GravityBox to run, you're going to have problems with some parts of it. I would encourage you to learn how to use ADB and Fastboot so you can recover from a problem that might occur when installing a mod that was never designed to be used with your device. Lots of people use GravityBox on devices it wasn't designed for, some of them work, some of them don't. But if you do choose to use GB on an unsupported device, then you're pretty much on your own for support.

But I will give you a direction to try, the message you are getting is indicating that the GravityBox framework is not properly installed and activated. Please review this linked post, which details the step-by-step of reinstalling Xposed and GravityBox. You don't necessarily need to go through the entire removal process (the first few steps), but just follow along and ensure you followed all of the installation and activation steps, basically steps 5 and on.

http://xdaforums.com/showpost.php?p=53488211&postcount=8326

Even with your device not designed for GravityBox, the framework should at least try to start, which it's not even getting to. This is usually because you haven't activated the GB framework in Xposed (step 13 in the linked post above).
[Xposed Framework Modules] C3C076:
Actually, when option in UNC is set to "original" GB doesn't make any changes to led whatsoever. It skips that part so original led is preserved. What you may be experiencing is a long lived KitKat bug in the lights system library which causes led to misbehave for very first notification received after device is freshly booted (white led shortly flashes once). Unlocking device, clearing notification and turning screen off makes all upcoming notifications behave correctly. By the way, non-intrusive call doesn't require UNC. It's enough to enable it in the phone tweaks. If you want it with heads up then also master switch for heads up should be enabled. UNC is then there only in case you want to change behavior of heads up on per app basis.

Furthermore it is not recommended to mix more different led control apps together. Results can be unexpected.
[Xposed Framework Modules] lavemetoo:
For me the same on my Z1C with newest KK 4.4.4. Build 14.4.A.0.108

After installing 3.2.5, rebooting the phone and starting I have the same error:

Xposed Framework does not answer. Ending
[Xposed Framework Modules] trjlive:
Well, in the first place, GravityBox was never designed to be used on your device. Though if you're not even getting Xposed to install correctly, that really has nothing to do with GravityBox. You need to figure out your Xposed problems first before even trying to install GravityBox. But even if you get Xposed working, you're going to have problems with GravityBox, it is only designed to be used with pure AOSP - in other words, Nexus or GPE devices.
[Xposed Framework Modules] Ok_Kaleidoscope5109:
So to answer the Heads Up issue, I only want heads up for the incoming call (I like the Omni implementation, but now how it still prevents you from interacting with the rest of the screen), so I enabled unobtrusive incoming call, heads up master control, and then set Heads up for Dialer only, which requires me to use Default Settings in UNC and set Heads Up to "Off."

Regarding the LED behavior, I can assure you my phone is booted, and has been for the past 3 hours so this isn't my first notification.

With UNC Default Settings as "Original" for LED: Gmail causes white flashing light. Powering screen on and off immediately allows Light flow to take control, and it starts flashing Green.

With UNC Default Settings to "Off" for LED: Gmail causes green flashing light (matches Light Flow settings).

The reason I posted here was because if you uninstall Gravity box Unlocker, meaning UNC doesn't exist (or rather start fresh with ONLY a Free GB installation), LightFlow can take control of my Gmail notifications with no issue. This means that there seems to be some conflict occurring when UNC is enabled, and the "Original" option is selected. However I understand that having two apps controlling LED can be potentially troublesome, so I also posted on a Light Flow thread, so maybe the developer can investigate. I just find it weird because the "original" option to me should be a hands off option that shouldn't cause any problem. Its odd that "Off" which seems like it could be more conflicting because on one hand Light Flow has LEDs it activates, and on the other hand GB UNC is saying to turn all LEDs off, seems to actually work out better for my case. So yeah, I guess thats why I suspect there seems to be something quirky going on with UNC and the "Original" setting for LED.

Edit: lemme take a closer look tomorrow. My internet is running like crap right now.
[Xposed Framework Modules] TNSMANI:
Thank you. Have done that. You seem to have thought of every possibility:D
[Xposed Framework Modules] lavemetoo:
nevertheless it runs under 4.4.2 - but ok, if it was not designed for Xperia Stock ROM, I have to live with this :crying:
[Xposed Framework Modules] C3C076:
I can't give you the exact cure because I have zero experience with lightflow so don't have enough knowledge how it could conflict with UNC. But I have previously seen people having troubles with using anything led control related when lightflow was installed.

I can only give you two more explanations to make things clear.

- non-intrusive incoming call is totally independent of UNC. So there's no need to set anything for dialer in UNC. Incoming call notification is ongoing for which heads up is completely disabled. Only standard clearable notifications can show heads up. Incoming call is an exception which is implemented "outside" of UNC control.

- led mode "Off" means to forcibly disallow led blinking for notification. "Original" mode is the one that preserves led as it was intended by app sending notification.
[Xposed Framework Modules] btnetro:
I have a small issues with GB on motorola moto x, the network mode toggle is not working, I mean I switch to 2g-3g-4g but the switch is not actually happening. I will submit a bug report later but maybe somebody had this issue before and could advise.
[Xposed Framework Modules] kingvortex:
Read the first post fully. If you're not running an AOSP rom, then don't submit a bug report, because your device/rom isn't supported and modifications won't be made to fix non working functions for it.
[Xposed Framework Modules] nabobcoffee:
Is there a way to reduce the DPI settings of the AOSP heads up notification. it so huge on my note 3. I tried finding it in app settings but couldn't. Thanks
[Xposed Framework Modules] nomisch:
It works ok on my Z1C running stock KK version 108 (4.4.4)

I have rooted the phone and installed xposed framework 2.6.1 without trouble.

GravityBox is running Ok_ish on the device.

- Statusbar tweaks are not working

- Quicksettings tweaks are not working

- I heard Lockscreen tweaks are not working netiher (did not try myself)

- UNC is working

- Other tweaks seem to work

I am not asking for any support as I know Z1C is not supported. It is only to warn people that some tweaks are not working.

I still love the idea of GB ...
[Xposed Framework Modules] furbyx92:
Try with system ui DPI, but maybe it modify status bar size and lock screen too... So at your own risk. :)
[Xposed Framework Modules] SedyBenoitPeace:
Guys i noticed a strange thing...on my Gravity Box there aren't lockscreen settings...is this possible? Or is there something wrong on my phone? I have the lockscreen targets (that i changed in a past version) and they work fine...but if i go to GB Menu there isn't the "lockscreen tweaks" screen... I have a Nexus 5 with stock 4.4.4 kitkat and franco kernel!
[Xposed Framework Modules] aavvaallooss:
So strange. I have this option has always
[Xposed Framework Modules] do_salah:
Yup just to double quote this person i can confirm the Z1 Compact does have issues with status bar and quick settings.

Running 4.4.2. just to give you guys headsup

Thanks for the great work
[Xposed Framework Modules] SedyBenoitPeace:
EDIT: I found the problem...if i change from light theme to dark and viceversa the voice appears again...i noticed a little bug (that maybe is related to another Xposed Module and not to GB) because if i close GB and then open the voice is gone again...i need to make the switch with the theme and it appears.

With dark theme i noticed that the "lockscreen tweaks" voice is overlayed to gravity box's bar...i can made a screen if [MENTION=5008415]C3C076[/MENTION] wants :)
[Xposed Framework Modules] C3C076:
??? This menu is not available only on android 4.1. No clue how that could have happened. Are you using official GB?

Also check your build.prop. ro.build.version.sdk should be 19
[Xposed Framework Modules] SedyBenoitPeace:
Of course that I use the official GB.. I downloaded from official xposed repository.. However like you can read I solved the problem and I noticed a bug (that is not necessarily related to GB).. This is the screen that shows what happens :

View attachment 2850921

Do you see where is the voice? Is overlayed to gravity box bar.. I suspect that the problem is of "Tinted and translucent status bar" module that i use..

I can help in some other way?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Xposed Framework Modules] C3C076:
I see. I can't give you other advice than to start disabling modules one-by-one until it fixes itself.
[Xposed Framework Modules] SedyBenoitPeace:
Fixed! Like I thought it was a problem with "tinted and translucent status bar" module.. I disabled the profile for gravity box and all works fine (without disabling modules or reboot the phone).. Thanks to all for help!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Xposed Framework Modules] srqrob:
C3C076

You're amazing. One of the best apps on Android. On vacation and still trying to help us all out. Thanks. Very glad I bought you some beer and encourage others to do same.
[Xposed Framework Modules] Blaze:
help

statusbar tweaks are not working on MOTOROLA MOTO G XT-1033, The Indian dual sim version....
[Xposed Framework Modules] nadiros:
Ya you'll be fortunate if anything works considering your device is unsupported for this module.
[Xposed Framework Modules] ahow628:
Is it Google Play Edition? If not, it is heavily modified Android and is not supported. Please read all of the original post in this thread.
[Xposed Framework Modules] alexandr1us:
bug on droid razr hd

GravityBox has bug on my verizon version of Droid Razr HD. Some icons don't show up well in toggles menu (see the wifi icon, it's half shown)
[Xposed Framework Modules] aavvaallooss:
If not AOSP/GPE you are not supported
[Xposed Framework Modules] C3C076:
I previously added some adjustment to moto devices regarding signal tile layout. Whether it's such a device is detected from build.prop variables. Your build.prop vars are probably different so GB can't recognize it as moto device.

A trick that would probably work would be to modify your build.prop :

ro.product.manufacturer=motorola

ro.product.model=razr

following full reboot. I strongly recommend doing a complete ROM backup before modifying build.prop. just in case.
[Xposed Framework Modules] alexandr1us:
Thanks for the reply.

ro.product.model is set to DROID RAZR HD for now. should i edit it to razr?
[Xposed Framework Modules] C3C076:
It's enough to remove DROID so it starts with RAZR
[Xposed Framework Modules] alexandr1us:
I changed the model to razr hd but system rebuilt the file so that there's still written DROID RAZR HD
[Xposed Framework Modules] trjlive:
You need to make sure you are mounting /system as read-write, it sounds like you're only mounting as read-only. So any changes aren't actually saved. How are you editing the build.prop? You should use a root explorer app. If you use ES File Explorer, then you need to ensure you're changing /system to read-write.
[Xposed Framework Modules] alexandr1us:
I know that, I'm not noob
[Xposed Framework Modules] the_happy_cannibal:
This change worked great for me. The wifi tile image lines up perfectly now.

Thank you.
[Xposed Framework Modules] Santi264:
Help Me

Hello i have a galaxy s4 runing android 4.4.2 and I cant make the lockscreen function. I know the post advices that i may not work with touch whiz but i wanted to know if there was a fix. Thanks
[Xposed Framework Modules] mdamaged:
Yes, don't use touchwiz.
[Xposed Framework Modules] nein7three:
I cannot change the navigation bar icons size. When I try, it does not change.

Also, when I reboot my device, all my preferences are back to default.