yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] osm0sis:
Really really minor, but the stock KitKat battery icon seems to be 1px wider than GB's, so the battery percentage overlay seeming slightly off center could be fixed by updating GB's with the latest stock. :)

Really great work on the KK version. The fix for the bottom Clear all Recents and putting it to 50px margin to clear the nav bar is working great!
[Xposed Framework Modules] C3C076:
Actually, I wanted to avoid that to keep commit cherry-picking between kk source code branch and jb branch easier.

But it looks like I will have to do it, anyway, since there's no support for SDK filtering in xposed repository to appear any time soon...

For now I completely unpublished GB from Xposed repo because it's too confusing...
[Xposed Framework Modules] c@p:
+1

Tapatalked by neXus 5
[Xposed Framework Modules] Peanuts.:
Would it be possible to have the volume button, adjust media volume? Instead of ringer volume when pressed?
[Xposed Framework Modules] Nbsss:
Sub

Awesome stuff bro
[Xposed Framework Modules] karanrajpal14:
Everything working well! Great job! Appreciate it :D
[Xposed Framework Modules] zouden:
Hardware keys not changing

I have a problem with the hardware keys (navbar) not changing function. Yesterday I could toggle the torch by long-pressing the home button, but after a reboot this morning it's back to the default behaviour and I can't change it. Toggling the setting in GravityBox does nothing, and disabling/enabling gravitybox (and rebooting in between) hasn't fixed it. Any ideas?

edit: fixed it - apparently we need to have "override system defaults" checked in navigation bar tweaks (separate to hardware keys).
[Xposed Framework Modules] Adrian.Chandra:
problem with latest nova launcher beta

Great module, love it, powerful even on custom rom

Navigation bar kept showing when using latest nova launcher beta. Im on Catacylsm 25 nov rom. For now i just set the height to 0%, posible on catacylsm.

And is it posible to change the margin of pie control ? I like to move it to be nearer to egde of the screen.

Thanks
[Xposed Framework Modules] Oz4225:
How i can do transparent statusbar?

What id(in color picker) for transparent statusbar?

Thanks
[Xposed Framework Modules] 77kdv77:
in 2.7.6 battery percents were placed after battery icon. in 2.8.0 they are before icon. why? in previous version it was better…
[Xposed Framework Modules] yanleites:
Hi.

Great Apk ! Thank You!

I saw last version in the Xposed Framework Updates, and I don't see the 2.8 version there now...

Any solution ?!

Thank You
[Xposed Framework Modules] dannyben:
That looks silly with the white status bar icons to the left & the blue ones to the right. Any way to change the left ones to blue too?
[Xposed Framework Modules] ItzMar:
I'm still running the old version from xposed installer on my Nexus 5 stock.

There is no option to enable torch with a hardware key for my device.

Does this version have anything implemented for hardware keys that the nexus 5 has?
[Xposed Framework Modules] Adam3Sixty:
I have a quick question.

I used to use JKay Framework when I was on 4.1.2 and now I am totally loving this as I am running 4.4

However, on JKay there was a "dim screen" quick setting toggle that basically made the screen really dark, it was great for using my phone in bed at night.

I was just wondering I'd there was any way u could look at the JKay framework things, or even talk to him, about adding this feature to GravityBox??

So far, I have no problems with GB at all, couple bugs but nothing that has made me wanna uninstall, lol.

Here is a link to his S3 framework thread, he is now working on the S4.

http://xdaforums.com/showthread.php?t=1807819
[Xposed Framework Modules] frikakwa:
Incredible! :rolleyes:

Read this for the answer!

I do not want to moralizing but ... only reading 8 pages could be a great thanks to the Dev! :silly:
[Xposed Framework Modules] yanleites:
Understood...

Thank You !
[Xposed Framework Modules] emd2009:
I'm on nexus 5 with 4.4.2 and the auto rotate quick tile is not displaying.
[Xposed Framework Modules] Napzter:
Hi C3C076,

I wanted to help samsonbear with the german translation and improved many strings to get everything more consistent. :fingers-crossed:

I also translated some missing strings.

Perhaps you can include it in your next release.

Btw, thank you so much for this awesome app! :victory:

Cheers,

Napzter
[Xposed Framework Modules] maritimesbob:
Hello,

Is it possible to change the soft keys (ie assign the recent apps button as menu) on the nav bar with this module in KitKat?

Thank you.
[Xposed Framework Modules] tonyp:
And this will never change. Actually it's a good thing if your phone freezes you can reboot it that way, as plugging the battery is rather difficult.

Being able to boot into recovery is important as well. While this is a (minor) security concern it gives you the chance to reset your device in case you bricked something.

This doesn't affect the normal users who didn't unlock the bootloader because unlocking requires a data wipe, so they're protected.

We power users (or should I say nerds?) are affected, but that's our choice. And I prefer to be able to recovery my device without the need of expensive hardware or sending it in like with other devices (nokia, apple, etc.) over a slight better protection of my data.

Otherwise kernel devs would have a really hard time on android...
[Xposed Framework Modules] dgwood12:
Anyone that can confirm the following problem?

I have a Moto X and set long press on my recent apps button to activate the torch. Normal press is set to default. I can activate the torch with long press but cannot use the normal press functionality...

I also tried to set another key to try pull up recent apps and that doesnt work either. I guess it could be one of two things... Either the recent apps functionality doesn't work or the misc tweaks I set on the recent apps screen (ram bar and clear all) broke it.

Sent from my Moto X
[Xposed Framework Modules] natezire71:
Already confirmed that long press actions for the recents button on MotoX don't work. Read. ?
[Xposed Framework Modules] FSRBIKER:
You can do this but you need to install the app Recent Task (by kaija), then set this app as a Custom App. Choose the Custom app as the single or long press action and whatever other function you want as the other.

Natively there is no other way with the Recents button on the Moto X.
[Xposed Framework Modules] dgwood12:
Awesome! Great solution. Works perfectly. Thank you!

Sent from my Moto X
[Xposed Framework Modules] necrologo:
Hello c3c076, first of all congrats for your module!

Are you planning to make a full customizable navbar with the possibility to add new button and resize the dpi of the navbar itself (like in costum roms)?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Xposed Framework Modules] C3C076:
Not really. There's app launcher key for quivk access to up to 8 apps. Will support shortcuts in the new version.
[Xposed Framework Modules] maritimesbob:
A fully customizable nav bar and being able to change change soft keys and dpi would be fantastic as an option. Not sure but I think he replied that it won't happen unless he was responding to another post?
[Xposed Framework Modules] MaKTaiL:
Can you bring the wifi and data indicators on status bar from Jelly Bean?

I miss seeing if the connection is being used. Also make the colors turn orange on status bar when the connection is not working.

Two awesome features I am missing on KitKat. :)
[Xposed Framework Modules] IImanuII:
Me too

Inviato dal mio Nexus 4
[Xposed Framework Modules] albsat:
Checking every hour for the new version. :) :)
[Xposed Framework Modules] jirafabo:
I use Nova. And I do use gestures (up swipe, specifically) to hide/unhide my dock. However, I had this same setup on the N4 with Rootbox ROM and Pie controls setup and had no problems with them clashing. I swipe up in the middle of the screen to control the dock.

Also, I notice there are less PIE options, like being able to control the size and location of the active/sensor area.
[Xposed Framework Modules] Henryy97:
Er.... I dont but they automatically turn on....
[Xposed Framework Modules] eurochild:
+1 for the nav buttons order and bravo for this amazing mod !!!:good:
[Xposed Framework Modules] madsponge26:
if possible hold back to kill will be add in gravitybox? just wondering..
[Xposed Framework Modules] SpazoQC:
its already there
[Xposed Framework Modules] madsponge26:
mate, i cant see the settings of hold back to kill.
[Xposed Framework Modules] C3C076:
As far as I understand, issue is there only with volume rocker wake enabled.

Thus I am wondering how you could simulate the same scenario (volume rocker wake) without GB enabled.

Volume rocker wake is disabled on stock by default.

Scratch that
[Xposed Framework Modules] haahaaah:
info

missing disable simcard 2 and the notification unused simcard2 on this modules dev (like GravityBox JB i mean). thanks before
[Xposed Framework Modules] trjlive:
What device and ROM are you using? I don't think there are any dual-sim devices that GravityBox is designed to support.
[Xposed Framework Modules] Jazz__75:
Problem whit the notification led:

Gmail set to red but it notify me whit only one flash not red:

help
[Xposed Framework Modules] :
master it still didn't work. here the log file. :crying:
[Xposed Framework Modules] haahaaah:
i use Lenovo p780 android 4.4.2 vibe ui. before i use same device with android 4.2.1 & GravityBox for JB work fine to disable that feature.

but when upgrade to 4.4.2 & i use GravityBox for KK, i not find that feature again to disable simcard2 & the unused simcard notification :(
[Xposed Framework Modules] :
sorry for double posts. my browser got weird.
[Xposed Framework Modules] fbf2201:
Even though it worked before, doesn't mean it's compatible. You use it on your own risk. An update of your rom or GB might break any feature or in worst case even lead to a bootloop.
[Xposed Framework Modules] spaboleo:
Hey guys,

is there any chance to include an option to move the "emergency call" button on the lockscreen towards the top?

The bottom position is causing some issues with the "Double-Tap-to-wake" feature, that many of the custom kernels provide these days.

Many kernels just allow a few centimeters of the bottom of the screen to be the active double-tap area to either a) save battery or b) prohibit accidental wake.

If one taps in that area once to often (maybe because the initial tap gesture wasn't recognized, or the touch when getting the phone out of the pocket was counted as the first of the double-tap) the emergency call button is hit and the dialpad is opened.

Moving the button to the top would prevent this.

Thanks in advance :good::o
[Xposed Framework Modules] kenkiller:
Not sure if this is correct, but here is what I got from alogcat.

http://pastebin.com/rChJi4mr
[Xposed Framework Modules] trjlive:
If you had read the OP, then you would already have your answer. In any event, your device is not supported. And as mentioned in another reply, just because it used to work doesn't mean it will continue to work. You are using a mod on a device it was never intended to be used on.

The GB source code is publicly available should you wish to try to debug the issue you're having on your own. But then, there is a reason why GB is only supported on certain devices, and it's simply because customs ROMs introduce too many code changes which causes problems with GB. Hence the device compatibility list on the OP.
[Xposed Framework Modules] C3C076:
Currently, support for MTK devices is very limited in KitKat version.

I don't have a device to develop on. [MENTION=455439]bgcngm[/MENTION] already implemented some of the MTK specific features, but it was during the short time he had Lenovo device borrowed.
[Xposed Framework Modules] C3C076:
Notification LED doesn't work correctly for the very first notification that arrives after device is booted.

That's a known issue affecting Nexus devices. All subsequent notifications should behave OK.
[Xposed Framework Modules] TNSMANI:
After reading this exchange, I first tested the " short press sleep tile" and the result was (as expected) the phone went to sleep ie. the screen switched off. The surprise was when I tested the "long press sleep tile" and the result was I got the Power Menu. This was what [MENTION=4788168]walkwitmeinhel[/MENTION] was asking for.

The point is that though using GB all this time, I did not know about this particular long press action.

It is a different matter whether the same will work on the phone of [MENTION=4788168]walkwitmeinhel[/MENTION].

I have the Nexus4 with stock 4.4.3, Xposed and GB current versions.

And thanks again [MENTION=5008415]C3C076[/MENTION] for all the updates which are working flawlessly.
[Xposed Framework Modules] MontAlbert:
Sorry if this has already been asked but I tried searching on the mobile app it found Bugger all...

Is it possible to bring slim recents to this module? Is this in future plans or very far down the list of things to do?

Thanks
[Xposed Framework Modules] C3C076:
Out of ideas... I give up. Looks like Samsung engineers added some additional security which disallows me to control

USB tethering from within SystemUI even if I synthetically add the necessary permissions...
[Xposed Framework Modules] :
oh no, this is madness :( anyways, i still thank you for you help and app :victory:
[Xposed Framework Modules] kenkiller:
Err....is this any useful?
[Xposed Framework Modules] C3C076:
Not really... You're the only one from thousands of users reporting such issue. This might be something special, local. I don't really have a clue...
[Xposed Framework Modules] A1ps:
I'm having MAJOR issues notification LEDs. The above problem being one of them even well after booting. Sometimes I get LED notifications absolutely fine. Then randomly theyll stop altogether.

I'm considering removing GB and then reinstalling. I have a premium version so IG I reinstall will I get premium version back?
[Xposed Framework Modules] bgcngm:
You'll get premium version back as long as you enter transaction ID again. ;)
[Xposed Framework Modules] Dan1234567890:
I do not know what is wrong with my setup of QH, but 95% (maybe all, I'm not sure) of WhatsApp and viber notifications makes default sounds during quiet hours - auto. It must be something wrong on my side because I do not see that others have this "issue" or that anyone reported something like this. I noticed this couple weeks ago, maybe month, before it was OK as much as I remember... Here are my settings & log. I have pulse notification enabled in display settings (did turn on/off, as suggested in case of problems).

View attachment 2791574View attachment 2791575View attachment 2791576
[Xposed Framework Modules] Pkt_Lnt:
Screenshots of logs are truncated and incomplete.
[Xposed Framework Modules] Dan1234567890:
Does this help? http://pastebin.com/Yi7Szkg5

I didn't think log would be of big help, because I thought I was setting something wrong.

First time I'm using pastebin, hope I did it right... Just looking at pasted log, I do not know how this email got inside... [emoji51]

EDIT: now comparing log which was exported to "sd card" from xposed installer and the one pasted on pastebin, I noticed that the end is missing... Probably pastebin could not save such a long log, so it is "truncated" it at the end....? If this is also not enough, I will try to upload it as a file. Thx for looking at it. [emoji1]
[Xposed Framework Modules] s1l3nt:
Is it possible to add a feature to enable/disable home button wake?
[Xposed Framework Modules] C3C076:
Well, this is due to how those apps are designed. QH in Notification control is meant for notifications only. If the app uses additional way of playing sounds (e.g. by directly using Ringtone manager or media player) to the standard one provided by notification manager, those won't be handled by notification control. Quiet hours in UNC apply only to the sounds that are part of notifications themselves.
[Xposed Framework Modules] Dan1234567890:
Thank you for the answer, I read around the xda that WhatsApp doesn't use standard Android notification system, but what surprised me is the fact that I have not seen to many issues like this been reported in the thread. And since this is the case, that means that nobody has QH working for WhatsApp and Viber and I thought that would be the majority of notifications that people are getting...

Thanks for the explanation :)
[Xposed Framework Modules] C3C076:
Yeah.

Btw, GB is not the only one. E.g. check out cyanogenmod Jira (bug tracker) for the same issue.

https://jira.cyanogenmod.org/browse/CYAN-3962

There's also a link to a standalone xposed module written specifically for Whatsapp
[Xposed Framework Modules] Neverendingxsin:
Hmmm changing the navigation bar height doesn't seem to work on the latest PA 4.4 RC1
[Xposed Framework Modules] DSA:
The clue to your answer is in your actual post
[Xposed Framework Modules] Neverendingxsin:
I know it's not officially supported on non stock Roms but thought I'd see if anybody had the same issue because it worked on the last version and the other nav bar tweaks work.
[Xposed Framework Modules] sherlock5545:
Had the same issue so I just removed any sort of sounds from WhatsApp notification setting. If that's an option for you, than try that.

Sent from my Nexus 5
[Xposed Framework Modules] Dan1234567890:
Thx for the idea. I would preffer to have sound with notifications during day, so I installed this app from the playstore for "quiet hours" and set it up in the same interval as Gravity box QH, so GB QH silence notification LED, and this app silence notification sounds. :good::cowboy:
[Xposed Framework Modules] sherlock5545:
By the way, anyone knows what's the difference between Reboot and Soft Reboot on the advanced power menu? I saw it rebooted the device but having a look in About Phone shows the counter hasn't been reset.

Sent from my Nexus 5
[Xposed Framework Modules] jacknicholson:
Playing on sherlock's suggestion, another potential solution would be to disable notification sounds from WhatsApp's settings, set one in UNC, and see if GB's Quiet Hours respects that.
[Xposed Framework Modules] Dan1234567890:
that would be great solution! :highfive: can't think of reason why it wouldn't work! I already set it up in UNC, just waiting for some notifications and GB QH to kick in, and will report back with results.:cowboy::good::good: I'm sleeping app uninstalled already, as well. :)

p.s. ran out of thanks for the day :rolleyes:
[Xposed Framework Modules] Pappe18:
Any chance to have more than 4 custom brigthness levels with gravitybox?
[Xposed Framework Modules] C3C076:
It's device dependent. E.g. we have 9 on N5.
[Xposed Framework Modules] fatspirit:
http://xdaforums.com/showthread.php?t=620337
[Xposed Framework Modules] Asad Khan 2085:
I don't know if it's me or anyone else having this problem.

Whenever i change my settings and reboot it does always same 1st time when i installed gravity box and restarted my phone...

on restarting a msg popout "Viber has stopped working" and phone restarted again i think about 4 times. Then i somehow managed to uninstall viber and then everything was OK.

But last night i changed my settings and restarted my phone this time it said "PHONE" has stopped working" and restarted again and again about 4 times...

Can somebody tell me is it a bug or something wrong with my GT-N7100

Sorry for my bad English... :)
[Xposed Framework Modules] MU24R:
Did you find a solution?
[Xposed Framework Modules] trjlive:
The answer is right there in your post. You're using a GT-N7100, which is a Samsung Galaxy Note 2. You really should go back and read the OP, especially the bright, red text under "Compatibility". The Note 2 is not pure AOSP, it's not a Google Play Edition device, and it's not a Nexus device. Therefore, you're trying to use GravityBox on a device and ROM it was not designed for, so you're bound to have problems. If you decide to use GB on an unsupported device, you do so at your own risk, and without any support.

---------- Post added at 11:33 AM ---------- Previous post was at 11:18 AM ----------

The reason GravityBox is not supported on custom and OEM ROMs is because there are simply too many variables and changes to the core code base from stock AOSP. And without many of the ROM's sources available, and without access to every device, it's just an impossible task to develop GravityBox to be compatible with everything. Not to mention, many custom ROMs have competing features, which cause all sorts of complex problems, that the only solution is to simply remove GravityBox.

That's why the developer made the decision to only support stock, vanilla AOSP, Google Play Edition, and Nexus devices. These three categories have minimal differences in the code base changes, so making GravityBox work the same way across all of them is a much more feasible task.

What this means for you, however, and for anyone else choosing to use GravityBox on a device or ROM it wasn't designed for, is that just because GravityBox used to work on a previous version, there is no guarantee that it will continue to work on future versions. At any time, a ROM or GravityBox update could break any/all GB features, or worst case, send your device into a bootloop.

When updates and new features are rolled out in GravityBox updates, they are done so after being tested on the supported devices. So if an update causes a conflict with an unsupported device or ROM, it's just an unfortunate reality. If you choose to use GB on a device and/or ROM it was never even designed to be used with, you do so at your own risk, without any support, and should fully expect to encounter bugs and problems.

And for anyone who feels so inclined, GravityBox sources are publicly available, links are in the OP. Feel free to take the code, debug it for your device, and make change to make it work better with your device.
[Xposed Framework Modules] C3C076:
[MENTION=5362940]trjlive[/MENTION]

I admire your patience to explain in such a great detail again and again and again :) thanks for your time!
[Xposed Framework Modules] Neverendingxsin:
Sadly not yet.

Thank you for the in depth reply, I really expected some short unhelpful response but this is truly helpful :)

What this guy said ^^^
[Xposed Framework Modules] ffejy462:
Maybe just reply to those who didn't read the op, a link back to the op.... Just a thought. I don't know about you, but it's almost as frustrating as people not reading the op, seeing yet another reply that says almost the same thing on every page. Don't get me wrong, I'm all for helping, but I'd guess nearly half of posts in this thread are those who didn't read the op and the corresponding reply to read the op. Sorry, had to vent.
[Xposed Framework Modules] Dan1234567890:
Ok, just to report back; after a lot of testing, I managed to do something. I disabled notification tones in WhatsApp for group and individual messages and set up override notification sound in UNC and GB UNC overtook control on sounds and GB QH respect that. [emoji106]

On viber I couldn't do that, if I set up no sounds on app level, UNC override notification sounds can not overtake control. So result is in no sounds when notification arrives, regardless of GB QH. But I didn't have enough viber messages for more detailed testing, will report back if I come to some conclusion. [emoji1] Thanks for the idea, once more [emoji106]