yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] yojlik:
While aoprea is being kind of rude, I don't think it's out of line to suggest that the settings UI could use an extreme overhaul. It's grown to an absurd size since I've started using GravityBox but more importantly it's so feature-rich and laden with dependencies (i.e. this option does this in conjunction with that) that it's really tough if you haven't been following the thread and keeping up on changelogs to know what everything does or how to access things.

I want to be clear, what [MENTION=5008415]C3C076[/MENTION] has done is great and I've donated and love the project. I also understand that if you're rooted, running Xposed, and setting up GravityBox there's a natural barrier to entry that normal everyday users are not going to go through. That being said, there's never any harm in focusing on the UX as though not everyone using GravityBox is a giant nerd.

It's probably not worth doing at this point in the project's life, what with major changes like Android L and the move to ART coming soon which will probably significantly change both the use case for GravityBox and the implementation both of GravityBox and Xposed, but I don't think it would be a bad thing if there were a feature freeze for a cycle so a solid effort could be put toward reimagining the UI (which is essentially a really large settings tree).

As an example, I'd point people to the recent overhaul of the paid LightFlow app. That powerful app was a nightmare to set up if you weren't knowledgeable about what you wanted to do before you started. It used recommended UI elements from different eras (an initial landing page with iconography, Holo settings, Card UI in the notifications) and was a jumbled mess. The new app uses a very easy to follow layout that leaves no functions hidden and follows current (soon to be deprecated) Android UI themes while not trimming the overall utility of the app.

While GravityBox likely won't benefit too much from Material Design, elements like master switches in the action bar or clearer toggle states and explanations for features would be a welcome change to the app and if this project survives the move to ART I'd encourage [MENTION=5008415]C3C076[/MENTION] to consider thinking about such things not just to clean things up for the users, but as a way to get better at thinking about UX from the beginning of developing as it's as much an art as a science and it's something that makes good developers great.
[Xposed Framework Modules] vladomirus:
Function application icons on the ring unlock screen - does not work! (KitKat) Why write that this function is works?
[Xposed Framework Modules] kingvortex:
Because it does work on devices running unaltered AOSP roms.

I'm not sure why you keep complaining in here when that is made clear in the first post and you've already been told that support for your device is limited.
[Xposed Framework Modules] fruity101079:
Many thanks for this module! I deleted all the others and keep only this one (I guess... :) )

Today, after the update I noticed a little bug.

I changed the height of the navigation bar, and am using the Android L icons.

I tried to change this height (trying to get it the transparent wi4hout success), when I notice that the white circle (appearing when you press a button) is offset the black back bar.

I navigated through the options, tried some things. I successfully got back to my settings (80% height) without this offset.

But I don't know how...
[Xposed Framework Modules] vladomirus:
What makes you think that I'm complaining? I'm just asking. Not yet so clever as you.
[Xposed Framework Modules] kingvortex:
Saying something doesn't work is complaining, especially when you've been told that your device isn't supported and it clearly says several times in the OP that only AOSP roms are supported. All features work for supported devices/roms.

Please stop asking/complaining about non working features. It's futile and fills the thread up for no reason other than to prove you didn't read the OP before installing this module.

If future, if something doesn't work, then it just doesn't work on your device. Nothing can or will be done to alter that.
[Xposed Framework Modules] Joseiyo:
I activate Status quicksettings titles but nothing happens. I have a rooted Samsung S4 9505. Anyone else happens the same?
[Xposed Framework Modules] kingvortex:
I suggest you read the first post carefully, paying special attention to any sections in red text.
[Xposed Framework Modules] yojlik:
As is seemingly stated every other post including the exchange directly above this one, this module is for AOSP devices. TouchWiz devices are not AOSP.

I'll admit I'm astounded by how many people can root their phones and start installing anything and everything without doing even the least bit of research into what they're doing. I mean really, who is looking at things to do to their $700 device (which they aren't happy with or they wouldn't be looking to change so much) and just blindly installing the first thing they come to without looking at what it is they're installing?

It happens so often you'd think I'd be jaded but really, it never ceases to just blow my mind.

Edit: I want to be clear here, I understand English is not your first language Joseiyo. As an American I can appreciate that if most of the resources for doing stuff like this was in a foreign (to me) language I'd pretty much blindly operate. Americans are spoiled thinking the world revolves around us and therefore see no need to learn other languages so I empathize. I really do. I don't want to be harsh because let's face it, if I had to deal with everything being in Portuguese or Mandarin then I guess I'd just get off the internet. XDA is a multicultural community and is much better for it so please don't take offense. There is an Xposed module that does what you want but for TouchWiz called Wanam Xposed, perhaps look into that.
[Xposed Framework Modules] TNSMANI:
Please read the OP especially the red-lettered words.

---------- Post added at 07:51 PM ---------- Previous post was at 07:36 PM ----------

If your above post is not a complaint, I do not know what is ("Why write that this function works?").

What are you "asking" here? Your device is not compliant and you know that. It is working for all the compliant devices.

If it does not work for you, grin and bear it.
[Xposed Framework Modules] vladomirus:
Once again I repeat - not all as smart as some here. You could just answer and not to spew bile to other...
[Xposed Framework Modules] ffejy462:
Maybe I'm in the minority, but I don't think we need three (or more) replies every time somebody requests help with an unsupported device.

Edit: before I get flamed, let me clarify, replies without new and helpful information...
[Xposed Framework Modules] mikeruss:
why not just ignore them, they would get the idea eventually and save the rest of us reading the same thing over again
[Xposed Framework Modules] Joseiyo:
Hey relax, as you can see I understand every English word you say. I've just made a simple question, but I have to admit that it was my fault not to read the first post; I thought that options like those maybe appear between brackets next to the options... It was my fault, I'm sorry. On the other hand I know everything I install in my phone and I've been doing it since I had a galaxy s, so I've rooted and installed lots of roms. I know what wanam lite and xposed are, believe me. And finally, it's becoming very common the fact of writing a discourse completely out of place and even judging people and trying to repair it by saying at the end of the paragraph "don't take offence"...

I appreciate gravitybox and because of that I made my donation, and the module for what I asked for is not important to me, it was just a simple question.

So my greatest apologies for my question and try to relax by doing something different like learning another language like Spanish for example; hey don't take offence, Spanish people like doing jokes, it doesn't matter where people come from [emoji12][emoji11].
[Xposed Framework Modules] danbest82:
+1

Is the battery bar coming in the future? I've searched the thread and don't see anything about it. I could have missed it though.
[Xposed Framework Modules] K-alz:
I wonder why settings don't stick after a reboot. Take for example the battery percentage text size. I have to re tick it every time I reboot. It's still checked, but just not affective until I change it to something else then recheck the one I want. Also some other things don't work (like some of the aosp settings and I'm guessing it's due to having a TW ROM not because of the module)

Phone: AT&T galaxy note 3

ROM: dynamic kat (thunderkat edition) 4.1 based on 4.4.2 international nc2 leaked TW firmware with GPE theme 4.1

Thanks for such a useful module.
[Xposed Framework Modules] ffejy462:
Unfortunately it's hard to ignore when unsupported device questions and the immediate unsupported device replies are more than half of this thread. I was just pointing out we don't need multiple replies saying nearly the exact same thing.
[Xposed Framework Modules] nadiros:
I Love GravityBox. When I first learned about Xposed I was blown away, and still believe it to be the most innovative development in Android. GB is the grand exposition of the concept, and its been awesome to see it mature.

That being said, I have (sadly) unsubscribed from this thread.

Its just become a clusterf**k and even the many, many good people who strive to support this kick ass module with a fantastic developer, can't save this from the endless onslaught of garbage.
[Xposed Framework Modules] fatspirit:
You may try to clean GB's data - someone with Samsung has reported that it was useful. Of course, yo'll reset your setting by that.
[Xposed Framework Modules] K-alz:
I'll do that and report back. Not that many settings to lose. Thanks

---------- Post added at 08:17 AM ---------- Previous post was at 08:09 AM ----------

Nope. That didn't work.
[Xposed Framework Modules] mikeruss:
sorry I wasnt clear

why do people bother answering questions about unsupported devices ?
[Xposed Framework Modules] aavvaallooss:
Empathy!!!
[Xposed Framework Modules] mdamaged:
Because then we'd be inundated with post after post of "[quotes own prior post] Bump", or "Any answer to this? [quotes own prior post]".
[Xposed Framework Modules] kingvortex:
Telling you the facts is not "bile". I'm sorry you feel that way, but that was not my intention.

You have already been told earlier that your device is not supported by this module. It is also written clearly in the first post of this thread, that you're supposed to read before even installing the module and especially before asking any questions at all.

So, now we've established that your device is not supported. This means that -

1. Some features may not work properly or at all for your device. They all work as intended on the devices/roms that the module was developed for and supports, so saying they don't work is futile.

2. Reporting bugs or non working features for your unsupported device is a total waste of everybody's time as the developer knows things don't work on unsupported devices and has stated that he will never fix them.

All this is written in the first post, which you are absolutely obligated to read as stated in the forum rules. If you haven't read them, I suggest you do so now, as it will make your time here easier. You should also read A message from the moderators, as that also contains lots of useful information for new users.

So, all clear now? I won't be replying to you again, as I should have just reported all these off topic posts to a moderator and will do so in future instead of trying to help you understand why things don't work for you.
[Xposed Framework Modules] frikakwa:
Your device is not supported... please stop spamming this thread! :p

#humor
[Xposed Framework Modules] Theberge43:
Hi, I've been using GravityBox for a while now and I love it. I even donated I think.

The only thing I don't like is related to the Battery Icon. I've just installed Tinted Status Bar which changes the color of the status bar to look like the current app. When that color is light (like white), it inverts the colors of the status bar icons. The only one that stays white all the time is the battery icon. From what I understand, even if I select stock battery icon from GB, GB still seems to theme it to look like the stock icon. Everything else changes ok.

Is there a way to run GB and get the real stock battery Icon at the same time?

When I deactivate GB everything is ok with Tinted Status Bar.

Thanks.
[Xposed Framework Modules] ffejy462:
I've noticed the same thing. I've tried several different modules to change the battery icon and they, so far, all appear to react the same way. Everthing but the battery icon changes, regardless of device. The only one that would change was the stock battery icon. On the apps with white action bars, I used holo themer module to change the action bar to black (some apps don't like the change however).
[Xposed Framework Modules] Theberge43:
Well, that s*cks ... at least I now know I'm not crazy :victory:.

Is it something that could be fixed ? Could we have a master switch to let the status bar alone in GB ?
[Xposed Framework Modules] Ja_som:
I tested it now. Tried stock, KitKat, ..., all. And all changed color to black when I have white statusbar.

Do you have enabled statusbar colors in statusbar settings?

Sent from my tablet./Odoslané z môjho tabletu.
[Xposed Framework Modules] Theberge43:
Hi, no StatusBar colors are not activated.
[Xposed Framework Modules] Ja_som:
So do it ;)

Sent from my tablet./Odoslané z môjho tabletu.
[Xposed Framework Modules] Theberge43:
You, sir, are a genius !
[Xposed Framework Modules] kinganu123:
Ever since 3.2.5, I've been having an mCastSocketMultiplexer.mWakeLock issue. The wakelock seems to not be releasing because it's constantly running and drains my battery REALLY quickly. Downgrading to 3.2.4 solved the issue for now. Any idea what could be going on?

I'm on stock with the Nexus 5
[Xposed Framework Modules] ricarp:
Hello, I'm on a Galaxy S5, and your module doesn't hide the AP/PM when it's checked to, and also it doesn't show the numeric keyboard when the phone aplication is opened.

Thanks for your wonderful work.
[Xposed Framework Modules] mdamaged:
TouchWiz?
[Xposed Framework Modules] ricarp:
I'm not sure, I have the gravity box 3.2.5 installed and the xposed installer
[Xposed Framework Modules] mdamaged:
Is the device a Google Play Edition(not sure if there is a S5 GPE...is there?)? ...or is it using Samdungs touchwiz gui?
[Xposed Framework Modules] ricarp:
Is not a GPE my S5 is a G900M, and bought from my service provider Samsung Touchwiz
[Xposed Framework Modules] mdamaged:
Then that's the issue, GB is not compatible with TouchWiz, as per the op.
[Xposed Framework Modules] ricarp:
Many thanks, but most of other settings worked well...
[Xposed Framework Modules] mdamaged:
No problem.

Yes, they often do, but it's still considered incompatible as well as unsupported.
[Xposed Framework Modules] ahow628:
I don't know if it is possible, but maybe C3 could have a pop up when opening GB that checks the build.prop and if you have something other than a Nexus or GPE gives you a warning about no support and things not working.

I'm sure many of the people with unsupported devices just download it while browsing the repository or hearing about it from a friend and never even see the first post.
[Xposed Framework Modules] jbdan:
Excellent post. The module is brilliant and I support it fully. I agree with you 100%.

N5
[Xposed Framework Modules] cd69:
No issues at all. Thanks C and hope you have a wonderful time off ??
[Xposed Framework Modules] sirs2k:
For some reason I'm still experiencing lockscreen crashes as soon as I enable any accessibility (greenigy, tasker, autovoice)

Using the latest GB with CM 11 4.4.4 (M8) or even earlier to that.

Very unlucky and hope we can find a solution.

Cheers
[Xposed Framework Modules] cadarn07:
Since you're on an unsupported ROM, don't get your hopes up. However, if you provide the proper logcat, the dev has been known to sometimes look into crashes like this to see if a fix is possible.
[Xposed Framework Modules] sirs2k:
Thanks for the quick reply. how do I get a proper logcat?

Update: Sometimes it says system.UI has stopped and when I disable lockscreen ring targets the problem goes away (this is a very important feature for me)

Are there any other ways I can have that many ring targets with other modules maybe?
[Xposed Framework Modules] cadarn07:
just type logcat into the xda search box. there are several guides on how to do it. an xposed log (from the xposed installer app) might be helpful as well. once you've captured the crash, copy the logcat and upload it somewhere and post a link to it here.
[Xposed Framework Modules] Miqueas111:
Hi all, I'm sorry if this already have been asked but I couldn't find the answer.

I can not get to work nicely the PIE controls on my Moto G. I've enable this and sometimes it works. Sometimes don't. It's hard. I enable the switch on Navigation Bar to hide it. Then active the PIE controls. But it doesn't work very well. Only want to hide the navigation bar, not the Status bar.

I have also a Nexus 5 and it's awesome with the PIE controls. Very responsive. Never fails.

A little help please?

Thanks all.

Edit: all my devices with Stock ROM right now. However I used to be in PA on my Moto G and it didn't work well then.
[Xposed Framework Modules] ahow628:
It looks like you are on CM, right? Isn't that a feature in the CM settings to have lock ring targets?
[Xposed Framework Modules] supertech1158:
I have a noob question. I have been using the screen recording feature in GB(KK). In normal screen orientation is works flawlessly, but in landscape orientation it only records the left half of the screen as if it doesnt recognize the screen rotation. Some of my apps im trying to record only work in landscape screen. Is there any way to fix the recording to adjust to the screen rotation? Btw I am having to use the option of running stock binary during recording.
[Xposed Framework Modules] Kocane:
Any other Xperia users here? I find that, unlike in JB, all the various lockscreen tweaks in GB doesn't work in Xperia 4.4.2. I've made sure that it's the AOSP Lockscreen that is being used and NOT the Xperia one, but it doesn't work. Not the ring targets, background, torch or anything...
[Xposed Framework Modules] hichem92:
suggestions

Please add the option to adjuste the transparance of stutbar and navigation bar in gravitybox kk and thanks
[Xposed Framework Modules] kingvortex:
Yes, me. I've activated the AOSP lockscreen on my Xperia Z a few different ways (Gem Xperia Xposed eyc) and the rings etc cannot be adjusted by GB at all. If you look in the Xposed log when the AOSP lockscreen is enabled, a long list of errors is thrown every time the device is locked, even when no customisations are activated.

I doubt it's a priority to get fixed, as our device isn't supported officially for this module.
[Xposed Framework Modules] cableghost:
UNC Default settings

Should I turn UNC Default settings to 'On', and select Heads Up to Off, all Heads Up messages stop displaying, including those apps I have specific settings for. If I disable UNC Default settings, I get Heads Up messages from my 'Active apps' and from some apps I don't have any specific settings for. I have attempted to set Heads Up 'Off' in those specific apps, but they still appear. Any suggestions? Yes, I've read the OP posts and have conducted a thread search; this might just be a ROM issue.
[Xposed Framework Modules] trjlive:
This is one of the reasons why Moto devices are not supported, as is mentioned in the OP, specifically about Moto devices. GravityBox is designed to be used on pure AOSP devices, which basically means Nexus and GPE devices. The

only

Moto device that is supported by GravityBox is the Moto G Google Play Edition, purchased directly from Google. You mention your Moto G is "stock", so I'm assuming it's a Moto-stock device and not the GPE device.

Motorola has changed a significant amount of the underlying core code on their devices (apart from the single GPE model), and as such it is not pure AOSP. In fact, Moto devices are as much custom as Samsung's TouchWiz or HTC's Sense. It's just that Moto installed a skin that resembles AOSP, instead of a custom skin like Samsung or HTC. But having a skin that looks like AOSP doesn't make the underlying code any less custom, which means that GravityBox will have problems with your device.

The options that have been brought up are to either not use whatever feature causes you trouble, or if you're familiar with development and code, you can always fork the GravityBox source code and see if you can tweak it to work better on your device. Source code links are in the OP as well. And if you are able to get it working better, you can submit your tweaks as a pull request to the Git repo.

While C3 has in the past fixed a few minor UI issues for Moto devices, he has stated he has no intention of ever spending serious debugging time and effort for these devices, primarily because he has no access to a Moto device. And once he spends time getting GB to work properly on one unsupported device, then everyone else will be expecting and demanding him to make it work on their various unsupported devices. It's just a can of worms that's best left closed. ;)
[Xposed Framework Modules] R3dbeaver:
Question: on my 4.4.2 Moto X,i don't think the manual brightness function works. It's the one where you can manually set the brightness level (and another thing, dunno why there are 2 settings) for each level for the auto adjust.

So is it not supported for Moto X? Or am I doing it wrong?
[Xposed Framework Modules] trjlive:
From your log, it appears you're using the Xolo Q3000, which GravityBox is not designed for.

Your device is unsupported

, so the fact that GravityBox doesn't work properly is to be expected. I would encourage you to go back through the OP, paying special attention to the "Compatibility" section. It's highlighted in red text because it's important to read and understand.
[Xposed Framework Modules] cadarn07:
Read the post above yours.
[Xposed Framework Modules] trjlive:
GB is not supported on Moto devices, with the exception of the Moto G Google Play Edition, purchased directly from Google. My quote from the OP:

---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------

How to properly request GravityBox features:

http://xdaforums.com/showpost.php?p=53967456&postcount=9200

---------- Post added at 01:44 PM ---------- Previous post was at 01:38 PM ----------

From your post sig, it appears you're using the Verizon Samsung Galaxy S3 (SCH-I535), correct? This device is not supported, due to the fact that some features don't work properly. Samsung did release a Google Play Edition of the GS3, which would be supported, but it was a GSM device, and as such would not work on the Verizon or Sprint network (as they are CDMA networks).

So the Verizon version is a TouchWiz device, and TW is known to have several major issues with GravityBox, due to the significant changes Samsung made to the underlying core code. See my posts above, they have to do with Moto devices but the reasons are the same for Samsung.