yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] trjlive:
No problem! Glad you got it working. I was going to say, sometimes the UNC options don't always switch off the first time you toggle the switch. I've also experienced that myself. Just toggling it again always fixes it. That, or also a reboot would probably have worked too.

---
[Xposed Framework Modules] C3C076:
You have probably checked "Ongoing" in UNC default settings? This is probably something you don't want. Ime switcher is an ongoing notification so it only picks up vibration pattern when ongoing option is set.

On a side note, ime switcher comes from the system itself so you can control its behavior (as well as other system's notifications) by changing UNC settings for "Android system"
[Xposed Framework Modules] jaferiqbal:
Battery icon disappears after every reboot. How to fix it ?

M on Parandroid 4.4
[Xposed Framework Modules] Mythos123:
forgive my dumb question, but could you possibly give me an example of an ongoing notification scenario, cause I don't really get what that setting does.

Nexus 5 & Tapatalk.
[Xposed Framework Modules] trjlive:
The answer is in the OP. Which you should have already read before even downloading this mod. So I suggest you go back and read it and then you'll know why you're having this problem and how to fix it.

---
[Xposed Framework Modules] jaferiqbal:
What i get from op is that maybe GB is conflicting with my custom ROM ? Is that what u referring to ?
[Xposed Framework Modules] trjlive:
What the OP says is that GravityBox is designed for and tested on vanilla AOSP devices. That means Nexus and GPE devices at this point in time. So, the inverse of that would be that GravityBox is not designed for, tested on, or supported on anything other than Nexus or GPE devices at this time. You're using GB on a ROM it wasn't designed for, tested on, or supported on. The fact that you have problems is entirely expected. That's why it's not supported. You're welcome to download the source code (links in the OP) and fix the bugs yourself, but this thread is not for providing support on unsupported devices and ROMs. So your options are: (1) uninstall GravityBox since it wasn't even designed for your ROM, (2) live with the bugs, or (3) download the source code and fix the bugs yourself.

---
[Xposed Framework Modules] Ok_Kaleidoscope5109:
The fix coming in the next version right? I didnt see an update yet since this post so I'm guessing you're waiting to roll up the update with other fixes/new features right? Just wanted to make sure I didn't miss anything.

Yeah, I would recommend removing the option of "Won't show ANY heads up while this app is in the foreground" from the Global settings page as its redundant with turning Heads Up to defaulting Off. Otherwise its a conflicting option to have two switches that do the same thing.

Regarding your latter point of extending DND on per-app basis to have "no heads up for notifications coming from app itself" that would be interesting too, but maybe too specific? I welcome the change, but I think its more important for global settings to have that option. I can't imagine where users would want heads up notifications for the foreground app, so to me it makes more sense as a global setting than a per-app setting. But go ahead and put it in both if you feel like it.... more power to the user right?

And finally just a suggestion from Paranoid Android's HALO which I find to be very similar to Heads up. Here are the options they have that I find could be useful to add for UNC for Heads Up (I feel they belong in the global setting page at least). The particular one I'm referring to is "Exclude topmost app" which is what we just talked about. Priority is unnecessary IMO as it just adds more work for you, but the other settings you already have like non-clearable. Anyway, the only option I feel strongly about is the "Exclude for topmost app"/"no heads up for notifications from the foreground app itself."
[Xposed Framework Modules] Seadra:
Waiting for the new update of GB for xt1033 Moto G dual sim. Hope to get update today. [MENTION=225651]op[/MENTION] any update on that?
[Xposed Framework Modules] bgcngm:
Please don't put pressure. Will be done when it's done! :mad:
[Xposed Framework Modules] aavvaallooss:
You can develope it by yourself if you can't wait
[Xposed Framework Modules] belek1979:
do you have any idea why <long press HTC 2 wake (elementalX)> stops working after installing GravityBox?
[Xposed Framework Modules] HyperCriSiS:
Hi,

can you plz add the possibility to change the functions of the recent button? :)

Greetings

Hyper
[Xposed Framework Modules] fausto975:
the enitede

It work on Omnirom 4.4.4?
[Xposed Framework Modules] ImpheOtus:
:cowboy:

I don't know... let me take a wild guess... maybe because your ROM IS NOT SUPPORTED!?

No... *sigh*
[Xposed Framework Modules] belek1979:
It is clean & official Android 4.4.4 Google Play Edition. But it's not ROM issue but GravityBox.

Custom kernel - ElementalX has sweep2wake, doubletap2wake, logo2wake with pocket detection.

Only long press logo2wake is broken. Phone wakes but stays locked (should be wake up and unlocked)

Some conflict with GravityBox and I wonder what is it - maybe I could do smth to make logo2wake&unlock work?
[Xposed Framework Modules] Skhulile:
I suggest that if possible we could rather get the Heads Up part from Gravity Box since it seems to work without any errors as well as it has more functionality. I like using Gravity Box but hate the fact that it is not really compatible with my device so I sometimes encounter errors and does not work well with Tinted Status Bar together with Dynamic Alarm. So if possible I would like to only have the Heads Up part only of Gravity Box

Thanks in advance
[Xposed Framework Modules] C3C076:
Version 3.3.0 available

Changelog 3.3.0 - 09/08/2014

- Added full support for Moto G Dual SIM running stock KitKat (except for carrier text options)

- Quick settings:

--- improved cast screen tile behavior

--- made precautions to avoid rare battery drain coming from Remote Display related to cast screen tile

--- added support for SIM 2 and network mode tiles on Moto G dual SIM devices

--- Network mode tile:

------ added option to choose to which SIM slot network mode tile applies (tile specific settings)

------ long-press on tile switches SIM slot without a need to dive into tile specific settings

- Signal cluster:

--- added option to hide mobile signal icons when SIM slots are empty (Moto G dual SIM)

- Heads up common:

--- show heads up only in case notification is for current user (in case of multi-user environments such as tablets)

- Ultimate notification control:

--- removed "Do not disturb" option from Default settings

--- added main screen with links to UNC features (improved user experience)

--- improved detection of statusbar visibility when heads up is set to show only when statusbar hidden

--- ActiveScreen: added option for setting heads up timeout (0 = until device is unlocked)

--- ActiveScreen: added option for setting heads up position

--- handle errors from package manager - potentially avoids rare crashes during app list loading

- Ring targets: improved unification of predefined/custom icon sizes

- Launcher tweaks: adjusted for compatibility with Google Search 3.6.13

- Improved compatibility with DynamicAlarm module (requires status bar coloring to be off)

- Navigation key actions: major rework which allows to bind Custom action to all key actions instead of using limited "Launch custom app 1/2"

--- removed "Launch custom app 1/2" from action list as well as related options for choosing custom app 1/2

--- added "Custom action" to the list of available actions which when set opens app picker for user to choose desired action

- Updated Japanese translations (thanks to WedyDQ10)

- Updated Russian translations (thanks to gaich)

- Updated Italian translations (thanks to valerioscifoni)

- Updated Chinese (Simplified) translations (thanks to liveasx)

- Updated Portuguese (PT) translation (thanks to bgcngm)

- Updated Spanish translations (thanks to jvbferrer)

- Updated Chinese (Traditional) translations (thanks to momomok)

- Updated French translation (thanks to ch-vox)

- Updated Polish translations (thanks to xtrem007)

- Updated Portuguese (PT) translation (thanks to bgcngm)

- Updated Slovak and Czech translations

Motorola Moto G Dual SIM has been officially added to the list of supported devices
[Xposed Framework Modules] vNa5h:
Hurrah for the update

Also a feature request..

Can there be a option to hide second sim if its inserted but not activated in dual sim settings

Tap-a-talked from the MOTOG
[Xposed Framework Modules] C3C076:
Probably in the future. I currently have only one micro Sim which restricts me from testing all possibilities.
[Xposed Framework Modules] m+a+r+k:
Just a heads up, but after latest update the Navigation Bar Custom Key settings disappeared. Yes I did a reboot.

Easy to put back, no problem but I'm left wondering what else might be missing...
[Xposed Framework Modules] C3C076:
Oh. I forgot to put that one in the change log. Key actions went through the major rework where it is now possible to use Custom action for any key action instead of previous "launch custom app 1" and 2.

Edit: changelog updated
[Xposed Framework Modules] CrashOverride93:
¿Would be possible to add a feature?

Hello, I'm looking for try to hide the "Flight Mode Icon" (air plane) that appears always when you enable it from settings's phone, on the top of the navbar. For now, I didn't finf any APP that make it, so will be possible try to add a new feature on the next releases, that make it?

Many Thanks...!!!
[Xposed Framework Modules] chavocarlos:
GB force close after update, I disabled all other xposed modules and using stock rom.

Regards.
[Xposed Framework Modules] C3C076:
Well, you'll have to provide more info than that to get help. What exactly FCs, what the steps to reproduce are, attach xposed error log + logcat taken during crash.
[Xposed Framework Modules] trjlive:
Probably the reason no one has made a mod to do that is because no one wants to hide the flight mode icon. Why would you want to hide the only notification that your device is in flight mode? Seems like it would be way too easy to forget to take it out of flight mode when you land, and then you'll miss calls and texts.

Anyway, if you really want to, just use the ongoing notification blocker feature in GravityBox. Enable flight mode, then the ongoing block option should list it as a notification you want to block. Block it, and reboot your device. Then when you go into flight mode, no airplane icon. Just tested this on Nexus 5 and it works. Though I also immediately disabled it, because with the amount I fly, I certainly don't want to forget and leave my phone in flight mode.

---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------

Remember, after any Xposed module update, you have to reboot your device BEFORE you try to launch the app. If you just update in Xposed, then try to launch GravityBox, then yes you'll get a FC. This is normal, expected behavior. This is why Xposed gives you the alert that you must reboot any time you update a module. This is one of those times where you really do have to follow instructions. ;)
[Xposed Framework Modules] Kozero:
Running Nexus 5 completely stock 4.4.4 and all that jazz, I encounter a slightly annoying bug. All my notifications are expanded, despite have "Expand all notifications" disabled. Even when I minimise them, once they reappear they're expanded again. This can be shown for example when taking a screenshot - it's expanded. I minimise and clear it, take it again, only for it to still be expanded. Am I missing something or is this a legitimate bug?
[Xposed Framework Modules] trjlive:
Well, while the Google Play Edition ROMs are supported, they are only supported in a stock configuration. Any modifications from stock can and will cause problems. Your modification comes in the way of a custom kernel, which changes the way the ROM does things. Since you mention HTC Logo 2 Wake function, I assume you're using the HTC One. Logo2Wake is not a stock feature, so the only way to use it is to use a custom kernel that makes system-level modifications.

Therefore, you should expect that not all features of GravityBox will work 100%, since your device is no longer 100% stock GPE. Many people use custom kernels without issue, but some people do have problems. You may experience bugs with GravityBox, with your ROM, with custom kernel functions, with apps, etc. Any time you make major modifications to your device (such as a custom kernel, which is about as major as can be, short of a custom ROM), you need to be prepared to handle possible bugs that come up, especially when combining multiple mods that make changes to system functions.

The first thing you should do when experiencing a problem with any mod, is capture a logcat of the problem, along with Xposed log. These logs can help you identify exactly what process is causing the issue. Perhaps it's a quick settings change that will fix it, or perhaps it will require you to stop using a particular mod or app. But without these logs, there's really no way to know for sure. So I suggest you capture the logcat and grab the Xposed log from when the problem occurs.

You asked what you could do to make logo2wake and unlock work better together. You can always download the source code for GravityBox and tweak it to work better with your device and custom kernel (source code links in the OP). If you are able to fix it and make it work, you can always submit a pull request to the OP dev and possibly have your fixes merged with the official codebase (at his discretion). Or just keep it as a custom build for your device and merge upstream updates as they come.

---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------

What device is this on? The only time I've seen this particular bug was on a Samsung device running TouchWiz. I've never seen it happen on a Nexus or GPE device.

Edit:

As mentioned by [MENTION=4775688]GermainZ[/MENTION] below, if you only have a single notification showing, it will always be expanded, regardless of any setting to disable expanded notifications. This is stock Android behavior. The "expand notifications" option simply extends the expanded state to all notifications. For example, if you have 3 notifications in your list, on stock Android, the first one would be expanded, and the other 2 would be condensed. If you enable always expand option, with 3 notifications, all three of them would be expanded. If you set the option to disabled, it reverts back to stock Android behavior, which is to always expand the first notification, and condense the remaining.
[Xposed Framework Modules] GermainZ:
Note that the first notification is always expanded by default. That's the stock Android behavior.
[Xposed Framework Modules] Kozero:
Ah, thanks for the information guys. I realise now they weren't expanded initially because I had Power Toggles enabled in the notifications, which I disabled once I installed GB. Thanks again, and sorry for wasting your time!
[Xposed Framework Modules] atz6975:
Hi, Thanks for this GB!

I use it on (stock+franco kernel) nexus5 and nexus7 and I always have extend desktop (hide nav bar + transparent status) and floating pie control.

While trying new Android Device Manager's lockscreen message feature, I found that there was no easy way to unlock the phone if you don't know to show the floating keys and press back or home to access the pin input screen.

So here is my feature request : if on lock screen offer option to keep nav bar + floating pie control.

Many thanks anyway. Amazing work (and patience)
[Xposed Framework Modules] geek-x:
Hi, thank you so much for your work on GravityBox, I can hardly do without it on my phone now, just thought I asked. Any chances of getting the ability to change app icons for stock Google Experience launchers right from GravityBox? :)
[Xposed Framework Modules] trjlive:
I know this has been brought up before, and if I recall, the response was that GravityBox is not and never will become a general theming engine, therefore tweaks to thematic elements fall outside the scope of GravityBox. Basically, tweaks to functionality of stock AOSP devices are in-scope, and so are generally implemented if C3 can find a way to make it work. Tweaks to the UI, like changing fonts, colors, icons, etc. are generally out-of-scope of the purpose of GravityBox. I'll leave it to C3 to make the defining decision, since it is his mod, but I don't believe anything has changed from the last time this was brought up, so I'm willing to bet he probably won't have any desire to implement icon theming functionality, especially since there are other modules that already provide exactly that functionality, and quite well I might add. ;)
[Xposed Framework Modules] charesa39:
You should give Xposed GEL Settings a try. It has a HUGE amount of mods for the Stock Google Now Launcher, including icon theming. It works great on my Nexus 5, 7 (2013) and 10. I believe even [MENTION=5008415]C3C076[/MENTION] recommended that route somewhat recently in this thread since there are so many launcher specific tweaks you can do with that module.
[Xposed Framework Modules] cheeze.keyk:
Battery Settings and Data Traffic Monitor doesn't work on my MTK 6582 device..any chance that could make it working on the next update please? thank you..
[Xposed Framework Modules] trjlive:
This is because MTK devices are not supported at this time. C3 has ordered a MTK device (though I don't think he's received it yet), so MTK support will most likely be improved in the future. However, will it be in the next update, unlikely. It will take some time once he receives the MTK device to make the necessary changes to the code.

So just use it as is for the time being, knowing that MTK support will likely be improved before the end of the year, but please don't push or continue to ask for MTK support. This has all been explained many times over in this thread, and the answers could be found easily just be searching for "mtk".
[Xposed Framework Modules] cheeze.keyk:
Thank you for enlightening me..[emoji317]
[Xposed Framework Modules] wmarcin:
Thanks for this wonderful module. Been using and loving it for awhile now. I'm on moto x and some things don't work, as expected, since it's not pure AOSP. But Torch used to work fine, until this update. Not sure if others are having the same issue.

... moto x vzw ...
[Xposed Framework Modules] trjlive:
Unsupported devices are always a gamble when an update rolls out. Some features that used to work may break, that's just an unfortunate side effect of using this module on a device it wasn't tested with. This update included several big updates and Moto G support. However, the Moto X is a completely different device, and very far from pure AOSP at that, so updates will always be a crapshoot for you. If that's a feature you depend on, you'd be best served by reverting to the last version that worked for you, and avoiding future updates. There's also the option of downloading the source code (links in OP) and tweaking and compiling a version of GravityBox that works better on your device.

---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------

Didn't see that this Q got answered. There are already options to change the functions of the softkeys. Is this not working for you? Please provide more information about your device and ROM.
[Xposed Framework Modules] wmarcin:
Thanks for a fast response. It's not a deal-breaker for me. I don't expect C3 to fix it if it only affects moto x, since it's not a supported device. I thought I'd report it, in case my device is not the only affected. Or, perhaps, a change was made in the recent update that could be easily reverted with no repercussions.

... moto x vzw ...
[Xposed Framework Modules] C3C076:
There weren't any changes to the torch functionality. Did you reboot after upgrade? What method of turning on do you use? (Tile, key action, ...)
[Xposed Framework Modules] wmarcin:
Thanks for checking. I rebooted twice. I use the tile. I'll try key action and let you know.

Edit: key action doesn't work either - from the shortcut, or quickapp tile. Thanks again for responding.

... moto x vzw ...
[Xposed Framework Modules] C3C076:
I suppose you didn't block any of GBs permissions like the one for Camera :) It is required for torch to work.
[Xposed Framework Modules] wmarcin:
You're a wizard. It turns out I did, and I didn't remember.! [emoji2]

Thanks again - sorry for wasting your time by being dumb and forgetful.

... moto x vzw ...
[Xposed Framework Modules] C3C076:
No problem. Knowing the fact I didn't change anything about Torch made me sure it must be something like that.
[Xposed Framework Modules] Schrotty35:
Is there an option for remove the 3 dot menue? Can i add the same color for status bar and nav bar?
[Xposed Framework Modules] flybiker:
Request for feature

Thanks for the wonderful module.. Is it possible to implement flip for speaker feature during a call, like in htc phones. GB has flip for silent and I think flip for loudspeaker during call would be a great feature.
[Xposed Framework Modules] :
[MENTION=5008415]C3C076[/MENTION] Thanks very much for the update!!!! :victory:

Running Condor Dual Sim here...

Thanks for the goodies for dual sim... :highfive:
[Xposed Framework Modules] trjlive:
What you are trying to do is entirely out of scope of what GravityBox is designed for, on several fronts. First, you're using a device that's definately not supported, and second, you're using a custom ROM that's also definitely not supported. I'm actually surprised you're not having more problems than you are. I don't know anything about the SGS3 or CyanogenMod ROMs, other than that they exist, and GravityBox isn't designed to be used with them.

I can tell you positively that GravityBox will not accomplish what you are trying to do

.

But I do know that

GravityBox is specifically dependent upon stock-AOSP code in order to do what it does

. That is why people have problems when using it with custom ROMs (which includes any OEM-custom or independent-developer-custom ROMs, such as Cyanogen). These ROMs have all sorts of custom code changes, which in part is what makes them custom, and adds features. But this also makes it impossible for GravityBox to do what it's supposed to do. The code it's looking for simply isn't there.

So I really can't help you with modifications on your device or ROM, since I have zero experience with them, and that's really out of the scope of this thread. But I can tell you that using GravityBox on a SGS3 is unsupported, as is using GB with CyanogenMod. So there you have 2 strikes against your device, where GB can and will run into problems.

What I would suggest, since you're using a custom ROM, is to contact the ROM's developer and ask that your feature request be added to the ROM. That's what custom ROMs are designed for, after all. GravityBox isn't designed to add features or tweaks to custom ROMs, it's designed to add features and tweaks to stock AOSP, which isn't something that would otherwise be changeable. You could also try creating your own thread specific to your issue, which is

"disabling the airplane mode icon in the status bar on CyanogenMod ROM on a SGS3."

That's really the issue you're trying to address, and not something GravityBox can help you with.
[Xposed Framework Modules] manos78:
Ok, I'll have patience. :angel:

Nevertheless, If I can do decompiling of the firmware in my devicem this will help you?

Thank you for you support and effort!
[Xposed Framework Modules] trjlive:
Completely OT,

Just have to say, love the profile photo! My girlfriend won't let me ever meet her (which wouldn't actually be that hard, since she's always out and about her in LA), she's afraid I'll leave her for Jennifer. ;)

/OT