yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] trjlive:
Just to clarify a few things, the fact that GravityBox is designed for and only supported on pure AOSP (Nexus and GPE devices) doesn't mean it won't work on other devices, it just means that it's not been tested on those other devices, and its functionality and stability can't be guaranteed. There are many users who use GB on unsupported devices every day, and for the most part, it works just fine for them. But even if there's just one feature that doesn't work properly, the device is considered unsupported, simply because the developer doesn't have the resources to allow him to debug and adapt GB to each and every device.

So as you've discovered, all but one feature of GB works well on your device which is unsupported. But this just means that when you have problems, the developer isn't going to spend time trying to fix those problems. The same goes for users of Samsung, HTC, Sony, and Moto devices, and others. While most features will work without problems, for those who do have problems, they just have to live with them. And most problems people have is with features that tweak the status bar and navigation bar, mainly due to the fact that OEMs tend to make drastic modifications to these elements.

And one thing to keep in mind, while it's rare, it has been known to happen, at any time either a ROM update or a GravityBox update could break something major sending your device into a bootloop. That's why I always recommend, if you're going to use an app on an unsupported device, make sure you are familiar with and know how to use ADB and Fastboot, in the event an update does cause a bootloop, you can recover from it.

It's not that C3 purposefully introduces bugs for other devices, it's just that if some new code works great on Nexus and GPE devices, but causes unforeseen complications on a Samsung device, well that's just how it goes. The main issue being that without OEM ROM source code available, there's very little he can do to debug GB for these other devices. With Nexus and GPE devices, it's easy because the source is always available. But OEM's source is closed and not made publicly available. So until OEMs start releasing sources for their ROMs, the best we can do is just cross our fingers and hope GB mostly works, but also understand that

C3 is doing the best he can with what he has to work with

. :good:
[Xposed Framework Modules] cableghost:
Moto Droid RAZR M

Stock ROM, rooted

KK 4.4.2
[Xposed Framework Modules] trjlive:
I suggest you go back and review the OP, please read the entire post, as there is even an entire paragraph devoted to explaining the issue with Moto devices. But I will quote the relevant details below.

From the OP:
[Xposed Framework Modules] DoctorStrange96:
So this explains why I saw some Moto G users complaining about bugs with GB... Well, not just with GB, but with other Xposed modules too.

And Motorola making some of us think that their devices run an almost 100% pure Android...
[Xposed Framework Modules] jacknicholson:
You may have to run a line in terminal, depending on which version of the dedicated Heads Up module you installed. Check the first entry of that thread's FAQ for more information. Failing that, throw a stone anywhere here and you'll probably land on a post about GB compatibility issues.

Are you sure? My N5's lockscreen times out after about 10 seconds, irrespective of whatever I've set my display timeout. PIN or slide, and the same for my other devices. I'm under the impression that this is AOSP standard, but I've been wrong before.
[Xposed Framework Modules] LifeAsADroid:
Le sigh, the reason why I still have to use the Heads Up Notification module and LightFlow instead of paying for the "pro" features in GB and having a single module to do it all as one. Thanks a lot Motorola.
[Xposed Framework Modules] trjlive:
Uggh I feel like a dolt now, I have a Tasker profile that controls the lockscreen screen timeout to mirror the screen timeout time. I disabled Tasker and my lockscreen goes back to the AOSP default regardless of the screen timeout as you mentioned. Which I actually like better, I had forgot about setting up that Tasker profile a while ago.

I was just playing with advanced profiles, came across a post somewhere that showed how to extend the lockscreen timeout for people that need longer to enter their PIN, and had forgotten about it until now. I was actually annoyed that my lockscreen would stay on for so long, I didn't want my screen timeout to be too short but don't need my lockscreen to stay on for so long. So now deleted the Tasker profile and I'm back to default behavior, and much happier too! :D

So very sorry for any confusion or misleading comments, I have been so swamped at work lately, and really need a SSD and RAM upgrade for my brain. It's been lagging like an old Moto Xoom with Honeycomb installed. :P
[Xposed Framework Modules] cableghost:
Yeah, but all other GB functions work for me.

Thanks, [MENTION=5321044]jacknicholson[/MENTION]...that was a meaningful answer; I'll look into it.
[Xposed Framework Modules] sweeds:
I'm on GB 3.2.4 with Pro features enabled. I don't see Heads Up feature under app settings in the Ultimate Notification Manager. What am I missing?
[Xposed Framework Modules] mdamaged:
Look in Statusbar tweaks.
[Xposed Framework Modules] sweeds:
Exactly. You must first enable Heads up globally from status bar settings. Thx!
[Xposed Framework Modules] C3C076:
The error that shows in the screenshot you attached is a fatal error that is not even related to whether xposed module is/isn't compatible with your device. Tile reordering screen is unable to find XML layout file that is basically a definition of how tile reordering screen looks like

setContentView(R.layout.order_tile_list_activity);

It looks like there is no such resource as "layout.order_tile_list_activity" in the APK.

This can be a result of

- modified version of APK (by decompiling/changing/recompiling)

- APK compiled from custom modified sources (containing changes that could introduce the bug)

Edit: there can also be a problem if device has no touchscreen. Tile reordering is available only on devices with touchscreen.

Edit2: I removed that restriction so you can try testing with attached APK.
[Xposed Framework Modules] TNSMANI:
Charging LED

My device and set up are in my sig.

In my Nexus 4, the charging LED is not working, though I have unchecked the 'Disable Charging LED' check box in Power Tweaks in GB. I have also enabled the ' Pulse notification light' in 'SETTINGS>Display' . In UNC, I have enabled the default settings for all and specific settings for some apps.

It was working earlier but I do not know from when it stopped. I am now having GB 3.2.4 with donation pack. The LED works for other notifications.

I installed Light Manager and tested the charging LED. It works with Light Manager.

Am I missing something?

Thanks in advance.
[Xposed Framework Modules] C3C076:
GB doesn't have an option for turning on the charging LED. The one and only option is to disable it if user finds it intrusive.

Charging LED depends on the lights native library. Nexus devices have no support for native charging LED in that lights library.

LightFlow uses some kind of a trick for charging LED but it's definitely not a native support.

Also check this post about N5's charging LED support. http://xdaforums.com/showpost.php?p=53512888&postcount=8356

You can analogically achieve the same result on your other devices.

The only thing to do is to find lights.xxxx.so for your particular device that has charging led support.

I recommend getting some OmniROM release for those devices and take lights.xxx.so from there.

Here's how Omni added native charging support to N5's native lights library.

https://github.com/omnirom/android_...mmit/2b8636625a5fec47bb6b9a65f490b6d3864025cb
[Xposed Framework Modules] TNSMANI:
Thank you for the explanation and ways to get it working.

Before enabling UNC in GB, I was using Light Manager and after enabling UNC I uninstalled Light Manager. May be I continued to believe that the LED was working! My bad:(. I know that Nexus 4 does not have charging LED support.

Let me go through the links posted by you and get back here if necessary.

Thanks once again.
[Xposed Framework Modules] nomisch:
Great module

Hello,

Thank you for your work, the module is really great !!

Works almost flawlessly on my Z1 Compact (Sony stock rom, kit kat 4.4.4, rooted)

Only bug spotted: when changing battery icon in statusbar, upon restart both battery icons are shown (old and new one). Going to the module and selecting again the battery icon solves the problem. (This bug has already been mentioned and you replied indicating implementation problems due to specificities of the SONY stock ROM)

Feature request (already asked as I have seen) - Timeout for LED notifications (like stop blinking after 1,5,10 or 30 minutes)

Something that could be useful would be a full comprehensive manual. Your module has a LOT of options and it might be a bit complex for newcomers to understand all the possibilities/functionalities. Having a kind of manual for each option with screenshots would be amazing. I am sure a dedicated user will do that at some point.

Thanks again !
[Xposed Framework Modules] trjlive:
Yes the problems with the status bar tweaks are a well-known bug of using GravityBox on an unsupported device, and have been mentioned before in this thread. It is a result of Sony having made major changes to the Android core. As you know from the OP, GravityBox is only designed for pure AOSP, which means Nexus or GPE devices. OEM devices, even stock OEM, are still considered a custom ROM in the eyes of GravityBox, as they are significantly customized by the OEM. This means that you will experience bugs, which simply can't and won't be supported.

As for your feature request, please refer to this post which explains where you should add it, as the developer has stated many times he doesn't follow or read feature requests posted in this thread. http://xdaforums.com/showpost.php?p=53967456&postcount=9200

As for a "manual" of sorts for GravityBox with screenshots, this is something I have considered doing myself and providing to C3 to add to his OP. I have given it a bit of thought on how I'd structure it, but it just comes down to time, of which I haven't had much extra lately. I may still do this, though, and if anyone is interested in contributing, contact me and we'll work something out.
[Xposed Framework Modules] gizzymobaby87:
I love most of the features of gravity box, but I'm unable to find a feature that allows the status bar to become FULL transparent... am I missing something or does it not exist??

Hiding persistent status bar apps can be a bit buggy too, though I'm sure with all the devices and roms out there it's hard to get it working on everyone, just wanted to make you aware :)

For me to buy this app it would need the full transparent status bar and the ability to change battery/Wi-Fi/signal icons... that would just make this mod perfect then. Here's to hoping to see them in future updates :)
[Xposed Framework Modules] Ja_som:
http://xdaforums.com/showpost.php?p=53128671&postcount=7751
[Xposed Framework Modules] baysakhal:
Is this ok when heads up is showing constant notification which really started to annoying me?! It was ok in the previous version of GB.
[Xposed Framework Modules] shmotog:
thank you [MENTION=5362940]trjlive[/MENTION] that was very helpful. Yes its definitely an issue with moto g, tried it with someones galaxy ace and theirs does the same thing as yours does. your suggestionm about changing Settings --> Security --> Automatically Lock helped in the sense that at least now that i increased it to 1 min (from 5 secs) it at least does not properly lock instantly after the screen dims. thank you.
[Xposed Framework Modules] vladomirus:
GravityBox KitKat

Why do we need a road, that does not lead to the church?

Why do we need GravityBox KitKat, which 99% of the functions do not work in this KitKat?
[Xposed Framework Modules] mdamaged:
What are you on about? Everything in GB works for me. I'm going to guess you're probably using some custom ROM that is not supported. Yeah, let's go with that.
[Xposed Framework Modules] fbf2201:
What??? :confused:
[Xposed Framework Modules] C3C076:
You can disable heads up for app those notifications come from. Additional per-app control is available under Ultimate notification control.
[Xposed Framework Modules] baysakhal:
Sorry, but I dont have it at all. Where can I find it?
[Xposed Framework Modules] C3C076:
The second menu from the bottom (just above About).

I'ts a premium feature, available to those who donated to the project either via PayPal or by buying "GravityBox Unlocker" package from the play store.
[Xposed Framework Modules] baysakhal:
Been there, done that! Thanks for hard work mate, keep it up!
[Xposed Framework Modules] nadiros:
Congratulations on your very third post! Being poetic and artsy may be nice and all, however this is a development forum. Please, for your own sake, and honestly the sake of those who truely want to help those who need it * Always search, and always read before posting. Google is your friend. You have a device probably worth several hundred dollars and if you wanna mod it or whatever, is it not worth a bit of time to get to know what you're doing....if anything to avoid errors that waste time and induce stress?

After doing what you can with you own time and effort, come on back and reword your question (if one still remains) to include at the very least, the device you are using, the ROM/firmware you are using, and any logs you might have gathered.

This is good practice and will greatly improve your time here at XDA.
[Xposed Framework Modules] TNSMANI:
We have reached the Church by travelling on the right road. You seem to be in the wilderness having taken the wrong road.

Let me guess, you did not read the OP and you have an incompatible device/ROM. Read the red lettered words and wisdom will dawn.
[Xposed Framework Modules] Egozy:
Hi, I would like to post a suggestion (Or maybe I've missed it?):

Make it possible to use the 'Navigation keys actions' (like long-pressing the menu or home key) in lockscreen.
[Xposed Framework Modules] fatspirit:
You don't like navigation ring for some reason? And, AFAIK, those keys are not shown while lockscreen is active.
[Xposed Framework Modules] vladomirus:
GravityBox KitKat

Ok. I have official ROM for ZP998 (needrom.com). Installed by Gravityboks and the first same function - to add applications on unlock panel does not work, although the ROM 4.2 (JB) this function to work. I'm can still be a long list, but a lot of functions are not working on 4.4 (some it work)
[Xposed Framework Modules] TechnoSparks:
Switch for each main modification?

Hello. I have a request to make.

With all respect, I understand that GravityBox does not fully supported (and may conflict) on custom ROMs (which I mean some things won't just work or may conflict). I faced this issue with my Cyanogenmod and I apparently didn't find a workaround (systemui crashed when i use navigation rings). Though I am really comfortable and like GravityBox, it is just so hard for me to actually forget it, thus this suggestion.

I am aware of the OP, but yea sometimes we have to try to see if GravityBox might work or not on other ROMs :D

It is not a request to support CM ROMs but rather, a request to have each function to have a main switch. Since GravityBox runs on Xposed, it is modifying system in the lowest system level. I believe this is why some of its functions conflicts with some native ROM settings(?).

This "main switch" I suppose is, what I imagine, when disabled, GravityBox won't interfere with the system. With current main switches available in GravityBox, they are all meant to turn off a feature completely; rather than leaving the feature (untouched) to be natively modified with the native ROM's settings in which, what I am hoping to see.

If some settings in the Ultimate Notification Control section has the main switch, why wouldn't any others. What I love the most with GravityBox is the App Launcher. With such feature implemented, someone may now finally ignore all other tweaks and only activate the applauncher settings. For me myself, I would disallow GravityBox to temper with navigation bar rings target, while using other GravityBox tweaks.

Thank you in advance. This is just a request. Though it would be great to be taken into consideration, however, I understand if you wish to disagree with my request. :)

Edit: Sorry for posting on the discussion thread, apparently there are not any computers near me. But look at the brighter side, some BBcodes might give this post some nice clarifications :D
[Xposed Framework Modules] bgcngm:
MTK support on the KK version of GravityBox is in a very early stage, so please do not complain about it. The development can only take place and continue if one has a device to test, otherwise it is almost impossible to have the same level of support found on JB version.
[Xposed Framework Modules] DoctorStrange96:
Yeah, looks like the problem really is that my device (my laptop) doesn't have a touchscreen. However, I configured my touchpad to work as a pseudo-touchscreen, and the option worked (here's a screenshot to prove it). So I didn't actually need to download and install the APK you provided. But thanks anyway.

And C3, you made really great work with GravityBox. Congratulations, mate.

EDIT: I've got a request. Can't you please stop GB from enabling all its extra QuickSettings tiles after the module itself gets activated for the first time? This turns the QS drawer into a hell of a mess with that whole load of toggles.
[Xposed Framework Modules] stfudude:
I'm having a problem with UNC: when I press the "preview" button, in a specific app or in the default settings, the screen turns off but doesn't turn on back. When I manually turn on the screen, I can see GB notification for a brief period before its cleared.

I want to test how Active Mode with Heads Up display works. ATM I don't have enough idea of how it works. Would someone kindly explain it to me?

Oh yeah one more thing:

to those with UNC feature unlocked:

How do you guys use Heads Up?
[Xposed Framework Modules] mdamaged:
The test is for the LED. If you want to test the UNC, send yourself an email or sms.

What do you mean by how do we use heads up? You enable it, then go into UNC and select what apps you want it to be used for.
[Xposed Framework Modules] stfudude:
I have submitted a feature request to

always

show Heads Up notifications in the lockscreen instead of showing it momentarily with Active Mode feature (UNC).

I hope you guys will upvote it because IMO this feature will make our lockscreen 90% similar to Android L's lockscreen notifications.
[Xposed Framework Modules] mdamaged:
I re-read your last post, hell I never even noticed a notification when I did the test, must go away quick!
[Xposed Framework Modules] stfudude:
So this is where I'm wrong. Thanks for clarification.

I'm kinda confused with how it's supposed to work. What I had in mind were:

1- Heads Up when in full screen apps that hide status bar (eg. games). *(without turning on Expanded Desktop mode)

2- Heads Up in lockscreen every time I turn on the screen until I cleared the notifications.

From what I gathered, Heads Up is only shown momentarily in lockscreen when Active Mode is turned on (with Heads Up). That's why I submitted a feature request.

What about #1? Is it possible to do that? I'd hate to see popup together with ticker, it's just redundant. But when the status bar is hidden, it makes a lot of sense to have Heads Up because we couldn't see the ticker. Forgot to mention one important thing: I'm really not fond of Expanded Desktop as I like to see the notification and status bar (Wi-FI, Bluetooth, alarm, etc) icons.

I hope you understand what I wrote.
[Xposed Framework Modules] mdamaged:
Besides Default, the options are, Always, When expanded desktop hides status bar, and off.

...there are also other options such as DnD (won't show any while that app is in foreground), show expanded, and show ongoing notifications.

FWIW, I upvoted your idea.
[Xposed Framework Modules] stfudude:
Forgot to mention one important thing: I'm really not fond of Expanded Desktop as I like to see the notification and status bar (Wi-FI, Bluetooth, alarm, etc) icons. What I understand is that if I select "when expanded desktop hides status bar", the heads up will only shown when I turn on Expanded Desktop.
[Xposed Framework Modules] mdamaged:
That would be correct. I have it so there's no nav bar at all, I only use pie, and status bar is shaded up, hidden, till I pull down.
[Xposed Framework Modules] trjlive:
I'm going to make a recommendation to you that will help you get much more value out of XDA.

Read the OPs before you post.

It's a core rule of XDA, that you will read and try to understand before you post something. You will not get spoon-fed on XDA. It is expected that you will make an effort to help yourself first, if you expect anyone else to try and help you.

I've looked over your 4-post history, and it's obviously apparent you don't bother to even read anything before posting. Continuing like this will only annoy other users and developers, and you'll likely not get any answers. All of your prior questions, in your 4 posts, were already answered in the thread's OP before you even posted. All it takes is a few minutes to read, and you can save yourself the frustration of not getting any responses.

XDA is a developer's site, hence the name "XDA Developers" in the site title. Non-developers are welcome to browse and post questions in the appropriate threads, provided they follow the rules and respect the developers. Part of that respect is reading the dev's OP before you post something. Posting without reading the OP is tantamount to disrespecting the developer, so why would he want to reply to you?

And to answer your question as to why "99% of the functions do not work" on your device, well the answer to that is also in this thread's OP. GravityBox is designed for certain devices and ROMs, not all devices and ROMs. So I suggest you go back and read this thread's OP to find out why it's not working on your device.
[Xposed Framework Modules] stfudude:
If that's the case then I'm gonna make another feature request to show heads up only in full screen apps without turning on Expanded Desktop.
[Xposed Framework Modules] trjlive:
Just as an FYI, you can enable heads up mode, then set the default behavior in UNC to not show heads-up, then enable heads-up on the per-app overrides on just those apps you want to see them. That's what I've done. That way, I still get normal notifications in most apps, but there are those particular apps I want the heads-up. This works perfectly for me. :good:
[Xposed Framework Modules] stfudude:
Do you use Expanded Desktop all the time?
[Xposed Framework Modules] trjlive:
Nope, in fact I've only ever used it a couple times as an experiment, but I decided I like to see the status and nav bars. I like the normal status bar notifications for most things, but a few apps, like Gmail, Tapatalk, Hangouts, Whatsapp, maybe a couple more, I like the larger, actionable heads-up notifications.

My thought, if it's just an alert telling me something, leave it in the status bar. But if it's something I need to act on or reply to, then I like to see the larger notification. With this config, any new app still gets standard notifications, unless I go in and change its per-app setting to enable the heads-up mode. It's kind of like, everything is default unless I go and set the app to enable heads-up. Seems to work the best for me.
[Xposed Framework Modules] gizzymobaby87:
Thanks for the link, I do already have translucent mode enabled, but translucent is all it is, not transparent :/ Ah well nevermind, thought I'd ask to double check as I seem to be using 3 different mods just to make the changes to the status bad I want, so I was hoping to get rid of at least 1 of them :)