yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] mdamaged:
All they can do is have it taken off the store, and since the developer is not the one who submitted GB to the store to begin with, and while he may choose to revert the changes anyway, he may not care if it gets kicked off the store.
[Xposed Framework Modules] Thomas_BA:
Never downloaded it from the store as it is not from the developer. Anyway i hope it gets sorted out.
[Xposed Framework Modules] mdamaged:
Me too, FWIW, I think they could have PM'd or emailed the developer instead of calling him out publicly, kind of unprofessional.
[Xposed Framework Modules] DvTonder:
Its very simple. A feature in this app, that goes against the Play Store Developer agreement, has caused us, and I am sure other widget developers, real financial and reputational damage.

While it is fine here (provided the proper detailed disclaimer of breakage is provided so we don't have to deal with the support emails or the feature is removed), it most definitely does not belong on the Play store.
[Xposed Framework Modules] Thomas_BA:
As far as i know the original developer (here present) never uploaded it to the Play Store. The one on the Play Store is a recompiled version from somebody. The source is available for everybody. Normal download is this thread or Xposed repository.
[Xposed Framework Modules] iamelton:
you are barking up the wrong tree..

you should contact the one who submitted GB to play store (and he/she is not the developer of GB)..

for me i never download GB from play store.. and i dont care if it gets removed from that place..

this thread is the place to get it..

(strangely i get the feeling that the developer may also be quite happy to see it not listed on play store, though he never explicitly expressed this attitude..)
[Xposed Framework Modules] Mysticodex:
Since the second to last GB update on my Nexus 5 my camera crashes when I launch it. Restarting will fix the issue temporarily.

Any idea why this might be?
[Xposed Framework Modules] :
I'm not on omni, that is just saved In Tapatalk. I am on vanilla 4.4.2.

Please note that when 'master switch' is off it goes to default navring.

I see no setting anywhere as you describe.

Like I said I'm on vanilla 4.4.2 on a nexus 5. Only mod is the icons in navbar and status bar, but I just did those yesterday and I have been struggling with this for days.

Oddly that option doesn't exist in my GB. I am on newest version.
[Xposed Framework Modules] yochananmarqos:
I was wondering why lock screen widgets suddenly wouldn't collapse anymore. It's been awhile & I initially thought it was due to a Chronus or NiLS update. Thing is, I went as far as disabling GB, uninstalling Xposed, even flashing stock system.img, still doing the same. Nothing else modifies my lock screen, so I'm at a loss. Might just do a fresh backup with TB , factory reset & call it good. Not sure when it happened & what caused it, so restoring a Nandroid backup might not help much.

"Why report?" Did you read anything he said?

What does this have to do with GB being on the Play Store? Again, read the post, it's quite valid.

The Dev permitted it as he cannot upload to the Play Store in his country. He even posted a "How to install GravityBox" video on G+ today made by someone who directed to install GB from the play Store rather than the repository.
[Xposed Framework Modules] rush25:
[MENTION=471482]DvTonder[/MENTION]

There are many ROMs and even CM has the option to allow widgets on lock..

There should be no complaints for this from your side as you are also a CM developer(cLock) and it was completely unprofessional on your side to post on thread :( You could use PM :(

If by anyway because of a widget this xPosed mod stops then I am sure that a lot of flaming will occur

All the best
[Xposed Framework Modules] :
First off, let me start by saying I am a chronus donator. I love it.

Nevertheless, in consideration of who you are, don't you think you should attempt to find a solution with the creator of gravity box, instead of coming here with this bad attitude? Many of us find this feature incredibly useful, and maybe the widget devs should work on finding a fix with this developer, instead of coming here, essentially demanding he remove it.

This attitude goes along the line with why [MENTION=591147]Entropy512[/MENTION] and [MENTION=2162789]XpLoDWilD[/MENTION] decided to start their own project.

You should come here with respect, and attempt to find a solution. I don't know if you realize it or not, but you're posts are essentially flaming this amazing developer who does this for nothing more than to make people happy.

The thing is, this app developer is so nice and friendly. I am sure he will be glad to work it out with you. Read back on this thread and see how well he treats everyone. So I kindly ask that you, a respected developer, do the same.

I have interacted with you in the past and you have always been very friendly, so maybe your posts are being misconstrued. You should read back your first post and see that its very 'matter of fact', blaming GB for your bad reviews, without any sort true solution, aside from neutering a previously great feature.

You are ALSO free to make a disclaimer on YOUR app, or even a bypass or check at startup, that states it doesn't work properly with gravity box.
[Xposed Framework Modules] :
It would be nice to at least keep the feature with maybe a warning message for those of us who use it daily

Sent from Omni Nexus 5
[Xposed Framework Modules] fbf2201:
I agree with your post, since there are plenty of other roms, that also have that feature implemented - but not with the last sentence.

If there is a disclaimer, it should be on GB side, since the other devs can not predict which other apps or modules (developed or not yet developed) break their appearance.

Edit: Ok, it's not the last sentence anymore. But I think you know which one I mean. ;)
[Xposed Framework Modules] LiquidSolstice:
This. I don't know where everyone is going with their white knight attitude. C3 does amazing work and no one is doubting that, but let's be honest; app developers cannot account for changes that are made on the fly with something like the Xposed framework, and if you're going to put a feature in like that, the least you can do is add a reminder when toggling that says it's been known to break certain types of widgets.

App developers who make successful products should not have to suffer for the decisions of ignorant pseudo-power users (I say that because there are plenty of people who install the Xposed framework and use GravityBox, but don't have a single clue how either works). C3 has already very politely said that he will remove it, so I don't see why everyone else needs to get involved in this?
[Xposed Framework Modules] C3C076:
Check out the screenshot
[Xposed Framework Modules] :
Very very odd. That option simply doesn't exist, at all, on my GB install. I will uninstall completely and do a fresh reinstall to see if that helps. Very odd.

Edit: yep, clean reinstall of GB and that option appeared. I guess all the upgrades somehow did something that made that feature disappear. Very peculiar.
[Xposed Framework Modules] C3C076:
Option was added in 2.9.8. So you simply might have been running older version.
[Xposed Framework Modules] yojlik:
I am having an issue since updating to 2.9.8 yesterday that I didn't see reported. While I'm loathe to blame it on GravityBox, it's the only thing that has changed for me over the last day.

My Nexus 5 is burning battery like you wouldn't believe. I'm talking 15% or more an hour without any activity. The phone is warm to the touch as though it's constantly awake but the awake time in the battery screen would appear to be completely normal if it weren't for the steep dropoff. Nothing is reported as using any battery in the app breakdown. Rebooting didn't stem the drain at all.

I rolled back to 2.9.7 just to see if it makes a difference (I should know almost immediately) but I'm curious if it's just me who is seeing this.

I should also note that I've got very few functions of the app in use. I have the Quick Settings Tiles changed, the advanced reboot menu, and volume skip and expanded volume panel enabled, and the clear all recent tasks button enabled and that's it. I don't have the Smart radio enabled which is the only thing in GravityBox I could even see affecting awake time. This is on stock software.

Am I alone?

Edit: An hour and a half later and the phone is cold and still fully charged. I have to assume it was 2.9.8 that did it.
[Xposed Framework Modules] gaich:
[MENTION=5008415]C3C076[/MENTION]

A friend of mine doesn`t speak English, but knowing me as one of GB translators, he asked to make a feature request, if it is possible – his Samsung GT-I9195 Galaxy S4 Mini LTE lacks the navigation keys haptic feedback, can you include such an option?

He even knows how achieve this editing framework-res, maybe this can help:

In framework-res\res\values\arrays.xml the line <integer-array name="config_virtualKeyVibePattern"> is responsible for haptic feedback, and the values below represent the vibration strength. My friend edits system\usr\keylayout\ sec_touchkey.kl as well, adding

key 139 BACK VIRTUAL

key 158 MENU VIRTUAL

All this works until the rom is updated, then he has to edit those files again. Thus, he and other users would be very grateful if you can make an GB option to turn the navkeys haptic feedback on and off with an opportunity to change the vibration strength.
[Xposed Framework Modules] C3C076:
I don't see a reason for 2.9.8 to drain battery taking into account what has changed compared to 2.9.7. May be something specific about your setup, maybe some app, or maybe using soft-reboots instead of normal full reboots.

I use almost all of the GB's features and my current battery status says: 1d5h on battery, almost 2:30 SOT and 49% left.

While I could add option for controlling the vibe pattern I'm not sure about changing the key definitions. I have to find out where the .kl files are being processed and how the behaviour could be adjusted. I want to avoid GB to make modifications to system files as it's its main policy - to never modify a system files directly.
[Xposed Framework Modules] yojlik:
I don't see a reason for it either, there weren't any changes relating to anything I even had enabled.

I saw the conversation above about some feature changes so I'll just wait until those happen before updating or I might just stay at 2.9.7 as it does everything I want it to do. I just thought I should mention it in case it happens to anyone else because it's not like I've had any trouble with GB at all in the past.
[Xposed Framework Modules] chetanya95:
1.Ya I can use that but it would unnecessarily add more tile because I already use double tap on statusbar to sleep. Nevermind just asked for another feature

2.OK here it goes. I have enabled swap touch/long touch action on the data connection tile so when I enable my data connection through the tile on one touch sometimes it doesn't have connection and doesn't show the 3g signal. But the setting is still on and I don't get to know it until I long press the tile and open The data usage setting. So I wanted a change on the tile to show that my data connection setting is on.
[Xposed Framework Modules] C3C076:
When network signal tile overriden, the indication that the data connection is on is when there's no orange"x" indicator.
[Xposed Framework Modules] gaich:
If it is possible to make it without modifying system files, please add haptic feedback adjustment option, let`s say from 20 to 70 with a 10 points step. And if you could find a way to control sec_touchkey.kl process, it would be great, if it`s impossible, let it stay so, maybe you can add a note in haptic feedback adjustment tab about the opportunity to edit those files by user himself. It`s a proposal from my friend, but he`ll be happy just to have the adjustment option. Thank you!:laugh:
[Xposed Framework Modules] johan8:
Pls add secondary carrier support as JB version
[Xposed Framework Modules] DvTonder:
The only solution we have found is to 1) remove all lock screen widgets (you may have to uninstall the apps) 2) disable this particular gravitybox feature 3) reboot and 4) re-add your lock screen widgets. This way the lock screen flag will be set properly when the widget is placed.

CyanogenMod does not have this 'feature'. I personally vetoed/-2'd it when it was first proposed and submitted to gerrit way back when - for this very reason - it broke lock screen widgets.

Your statement "If by anyway because of a widget this xPosed mod stops then I am sure that a lot of flaming will occur" indicates that you may not understand the magnitude of this particular problem - its not "a widget" it is

ALL

widgets that depend on knowing whether they are on the lock screen or not and causes real financial/time and reputational damage to many devs. I would hope that users would take a moment to understand the ripple effect before flaming.

As an individual app developer, I can only break my own apps (and regularly do :)), but, when we venture into framework development, what we do affects all apps and even Android itself. We have to take our responsibility to ensure we don't break the Android API very seriously.

I respectfully disagree with your comparison of myself to xplodwild and Entropy - my tone was factual, not disrespectful.

It is important for both the developer

and

the users of GravityBox to know and understand the problem this feature causes.

I had just spent 5 days working with 3 of our users, through 17 debug builds and a multitude of layout and dimension xml, resizing logic and code changes only to discover that a core API I depended on has been bypassed. Now that we know the case, I did a full search through the history of support emails and refund requests we received and can clearly attribute several of them to this issue. We have also seen a marked increase of these reports over the past few weeks.

I have great respect for any developer that can do this type of development and tip my hat to C3C076.

Thank you.

You do have a point on the broader context. I suppose the big difference is that custom ROMs are not available on the Play store and their users and users getting stuff off of XDA tend to be more forgiving when things 'break'.
[Xposed Framework Modules] Pkt_Lnt:
The Play Store version of Gravity Box was not uploaded by C3C076, it is an unauthorized upload by someone else. You should contact that person, since most of us here download Gravity Box from the Xposed repo, knowing the Play Store version is unauthorized.

---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------

First, you should post in the Gravity Box Jelly Bean thread, this one is for KitKat.

Second, the feature you request is already there, for lock screen and notification panel.
[Xposed Framework Modules] DvTonder:
I know and I have. This however does not negate the fact that a function in GravityBox breaks widgets - both the dev and users here need to be aware of it as well.
[Xposed Framework Modules] Pkt_Lnt:
[MENTION=5008415]C3C076[/MENTION] has stated he will remove it, so it seems like the guy on the Play Store is where you need to focus attention.

I, like others, find your continual intrusion into this thread by another dev rather disrespectful; you can PM [MENTION=5008415]C3C076[/MENTION] if anything else is needed, you do not need to try and dominate the conversations in this thread. We really do understand what you are saying and [MENTION=5008415]C3C076[/MENTION] has stated he will remove it.
[Xposed Framework Modules] computerdating:
Hi, running 2.9.8 on a stock ROM, Nexus 5.

After updating to 2.9.8., my phone still vibrates in silent mode. This wasn't the case in 2.9.7. Not sure how to fix this. I don't use the quicksetting tile. I just use the rocker to put the phone in silent, or long press power and hit silent. Now there doesn't seem to be any difference between silent and vibrate modes.

Thanks.
[Xposed Framework Modules] rush25:
[MENTION=471482]DvTonder[/MENTION]

Sorry if my statements caused you unintended harm..I saw that feature on gerrit so said even CM has it ..btw I also use cLock so I have huge respect for you ..I say sorry again if my post hurted you but actually today GravityBox is undoubtedly the best module for us Nexus users who dont want to flash Custom Roms :)

Hats off to you for keeping your calm when we users were flaming (y)
[Xposed Framework Modules] iamelton:
dont u think it would be a better approach to pm the dev first for the matter, and discuss and let him decide if a public announcement should be made in this thread, instead of the approach that was being taken here?

actually im sure u should be convinced at this very moment that the dev is indeed quite friendly and open to discussions (by the fact that he agreed to remove the feature without too much hesitation)..

so while u might still hold a valid point and after all got what u desired, do u still think u took the best approach in dealing with the matter?

i think this is the reason why so many ppl here took the trouble to respond to ur posts..

[MENTION=4403217]Pkt_Lnt[/MENTION], ur previous post spoke exactly what was in my mind..
[Xposed Framework Modules] DvTonder:
With all due respect - I pointed out a real issue and am responding to statements and comments from other users directed at me that is on-topic, relevant and pertinent to this thread - this is is exactly what XDA forums are intended for. It certainly is not my intent to dominate this thread nor does 4 or 5 on-topic posts out of 4890 fall into the 'dominating' category.

I showed no disrespect to the developer or his thread. My interaction with the users here has been professional and respectful. I did not once attack, belittle, demean or presume to tell another XDA user what they can or cannot say. Unfortunately, I cannot say the same for some responses I have been getting.

I will continue to monitor this thread and will respond to posts directed at me as appropriate, however, my point has been made and I will refrain from the temptation to make it again :)
[Xposed Framework Modules] C3C076:
Just to add to it to make it more clear. It's true the "xposed apps" play store user put the GB in the store without asking me first. But he did ask after doing so and I agreed in a sense that OK, I don't think this project is suitable for being accessible via play store but didn't actually told him to remove it. I said OK, it's there, let's see what happens next. This means the last thing I want is this user to be blamed. It's my fault to a certain extent and I'll ask him personally to remove it from there. I think this should be done for each xposed module. Xposed is a very powerful tool and can be really dangerous, especially regarding security when misused. It won't take too much time for Google to take some actions when suddenly store is flooded with something that's not appropriate (like xposed modules are). While I'm a fan of xposed, I can see how dangerous it can be. This incident is just one example.

On the other hand, I still believe that there are too many users that are no power users and flash ROMs, anyway, having this 'feature' with tendency of targeting complaints against app developers, rather than the ROM developers.
[Xposed Framework Modules] farmaan7x:
Ya I am Android 4.4.2 n have 10gb of storage .I even tried clearing dalvik cache
[Xposed Framework Modules] Mac_Ad:
Unlock Ring Targets & Qucik Pulldown Size

I've tried to read as much of the recent history as possible to see if I could find any reference to this. It's very possible I missed it so here is my question.

I've successfully installed the Xposed Framework and consequently the Gravitybox KK on my Sprint Galaxy S4 with KitKat 4.4.2. it has worked on everything except the Unlock Ring Targets and the Quick Pulldown Size.

Unlock Ring Targets

Lockscreen Targets/Unlock Ring Targets = ON

I have set 5 ring targets

I have activated Show Battery Arc

Rebooted

The Lock Ring is still the default swipe ring

I verified the settings are still set and they are but the default lock ring is still persists.

Quick Pulldown Size

Statusbar Tweaks/Quick Settings Management/Quick Pulldown = Right

Quick Pulldown Size set to 40%

Reboot

Pulldown Bar still acts in default manner.

In both cases I rebooted just to be sure. There may be another setting I am missing but I don't know what that would be. I read another post that mentioned an "over ride defaults" from the Navigation bar tweaks but my versions doesn't seem to have that. There is a "Master Switch" setting and I did set it to "ON" just to check.

Hope I have given you enough info and that you may have an idea on what I have done wrong.

Thanks
[Xposed Framework Modules] C3C076:
If it's a custom rom or vendor modified ROM (e.g. touchwiz) the answer is in the main post - compatibility section.

Your info is complete enough but it would be more perfect if you attached a log file exported from within xposed installer app.
[Xposed Framework Modules] mitchst2:
[MENTION=5008415]C3C076[/MENTION]

You mention xposed as being potentially dangerous and I've read the same in xposed thread and obviously chosen to run with it.

A question I've often thought to ask but never got around to. Are the modules loaded onto xposed repository vetted in any way? I realise you are not responsible for the repository but thought you'd know the answer.

Sent from my HTC O'ne-xus
[Xposed Framework Modules] C3C076:
Modules in the repo could be most likely treated as harmless. Plus rovo is working on a moderation system where only modules that pass a review will be available there.

You can learn more about xposed and security from this discussion: http://www.reddit.com/r/Android/comments/1vjr2n/with_the_xposed_scene_exploding_at_such_a_fast
[Xposed Framework Modules] Mac_Ad:
I don't believe it is a touchwiz but how would I know that for sure. And how do I attach a log?
[Xposed Framework Modules] Mac_Ad:
Debug Log

Ok, figured out how to send myself a debug log. Here you go.
[Xposed Framework Modules] C3C076:
Omg. That's too many incompatibilities even in some of the parts where I wouldn't expect it. Looks like this ROM is heavily modified by Samsung making GB incompatible
[Xposed Framework Modules] Mac_Ad:
Well, it' has allowed me to take back some of my phone. So tired of Sprint and Samsung or Google, who ever it is deciding for me what my OS should be and how it should work. I am very appreciative of the few things GB has allowed me to take back control of. I am not pleased about the latest KK update at all. Anyway, appreciate your hard work and thanks for responding to me. Looks like my only option would be to install a new ROM but that does frighten me just a little bit.
[Xposed Framework Modules] claytonjn:
Out of curiosity, how do you propose that a company provide a phone without making decisions about how it should work?

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[Xposed Framework Modules] Mythos123:
[MENTION=5008415]C3C076[/MENTION]

is it possible to not play battery charged sound when phone is on mute?

Nexus 5 & Tapatalk.
[Xposed Framework Modules] chrisrozon:
It not about making decisions, it's about locking them in with no option to change.
[Xposed Framework Modules] claytonjn:
Have you ever used an iOS/OSX device? ;)

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[Xposed Framework Modules] A1ps:
Here you go guys. This is the other icon I get with new hangouts messages. I also get the original Hangouts icon too. I have to delete both icons on Notifications.

The only thing I'm running is gravity box and xposed.
[Xposed Framework Modules] yochananmarqos:
Yep, it finally dawned on me I needed to remove & re-add the lock screen widgets after disabling the offending feature. Thanks for the reply.
[Xposed Framework Modules] mdamaged:
You did not say what ROM. It looks to me you have something else intercepting the notification and displaying it's own icon for it.
[Xposed Framework Modules] A1ps:
Hi mate. I'm rooted but running a stock ROM.

I might try deleting hangouts and then reinstalling it.