yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] C3C076:
Just for curiosity. Android L has native support for silencing notifications for certain amount of time (very similar to quiet hours implementation, using the same method I use). Now here comes the interesting part. It doesn't work for WhatsApp. This means, after L is out, WhatsApp devs will need to reconsider their implementation since I'm expecting quite a large pressure from the users. They have been constantly ignoring the reports their app doesn't behave well with QH features on custom ROMs but they always made a statement that they were not going to adjust app for custom ROMs. I'm confident Android L will be a game changer :)

Developer options / Show touches.

If you can't see "Developer options" menu in Android settings, go to "About phone" and quickly tap on "Build number" several times.

"Developer options" menu will appear right on top of "About phone" in root of the Android settings.

You can use PayPal channel instead of Play Store channel.

Using PayPal, you can decide yourself what amount is suitable for you to make a donation.
[Xposed Framework Modules] el_smurfo:
Darn.... Pay pal is pure evil... Hopefully you can do a summer play store sale sometime...
[Xposed Framework Modules] C3C076:
Just a hint. There's also another way of obtaining unlock ID: Contributing to the project somehow by e.g. providing/updating translations for your language.
[Xposed Framework Modules] trjlive:
If you want to pay your own amount, use PayPal. If you want to purchase through Google Play, the price is set at $4 USD. That's less than a cup of coffee at Starbucks, and GravityBox will last a lot longer than a Venti Cafe Latte. ;) Or you can contribute to the project, like C3 mentioned, and receive a complimentary license as a thank you.

So there are three very accommodating options for you to pick from, which is two more than just about every other app on the Play Store. It's one thing if you simply can't afford the $4, then go with one of the other two options that would allow you to pay less while still showing respect for the countless unpaid hours of development that has gone into developing this module. But don't expect a developer to change his ways to accommodate a user who won't change his own ways to donate a paltry $4.
[Xposed Framework Modules] ffejy462:
Gravitybox is well worth it (even on unsupported devices). I've donated a couple times. I know others have gone above and beyond to make a donation as well. Maybe sign up for Google rewards and "earn" play store credits...
[Xposed Framework Modules] C3C076:
Version 3.3.2

Version 3.3.2 available

Changelog 3.3.2 - 19/08/2014

- Quick settings: toggle auto-brightness on/off on brightness tile long-press (when brightness tile behavior overriden)

- Heads up common:

--- added option for choosing heads up position (applies only when keyboard is not showing to avoid interference http://youtu.be/m3xD9z0k5oM )

--- added option for choosing heads up transparency level

--- improved handling of non-intrusive incoming call

--- fixed heads up sometimes stuck after non-intrusive incoming call is answered

- Ultimate notification control:

--- Active Screen: added option for choosing heads up transparency level

--- Active Screen: avoid keyboard popping up for heads up on lock screen

--- fixed crash when orientation changes during app list loading

- Power tweaks: allow users to choose custom sounds for battery charged/charger plugged/unplugged events

- Navigation bar/pie: optimized behavior of dynamic clear all recents key

- Key actions: fixed issues with the recents key causing action reset

- ExpandedDesktop: don't show status bar when swiping from navbar area in semi-immersive mode - e.g. avoids showing status bar

when user has Pie controls within navbar area

- Display tweaks: affect button backlight behavior only when option for button backlight mode is other than default

- Misc tweaks: added option for FakeID vulnerability patch (thanks to Tungstwenty@XDA for original Xposed module - https://github.com/Tungstwenty/FakeIDFix):

--- patches new security vulnerability labeled "Fake ID" (Google bug 13678484) - http://bluebox.com/technical/android-fake-id-vulnerability/

- Updated Italian translations (thanks to valerioscifoni)

- Updated French translation (thanks to ch-vox)

- Updated German translations (thanks to LibertyMarine)

- Updated Russian translations (thanks to gaich)

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

- Updated Slovak and Czech translations
[Xposed Framework Modules] remicks:
This. A million times this. This Xposed module is the single greatest thing to happen to rooted phones since Xposed itself. I happily paid the $4 for the unlocker even though I don't use the extra features. Been using this on my Moto X, LG G2, and on my M7 (when I run AOSP based ROMs). Fantastic work by a fantastic dev, I suggest everyone who can afford to donate or buy the unlocker should do so immediately. Kudos for the great app buddy.
[Xposed Framework Modules] el_smurfo:
Yeah, that was some pretty weak late night whining in my part... Purchased through Play, and sorry about that
[Xposed Framework Modules] ultimahwhat:
Heads up notification transparency works well after update. Would be neat to add option to opacify heads up upon interaction/expansion, similar to volume control slider. Great module, really the main reason I stick with xposed, thanks [emoji106]
[Xposed Framework Modules] momomok:
any way to verify if the FakeID patch is successful? :D

(coz those scanner apps cannot detect it)
[Xposed Framework Modules] ahow628:
With my kids, we call it "over tired" when they get so grumpy and tired that they can barely function.

In any case, this is probably my most used app and I'm glad you see the value in it as well!
[Xposed Framework Modules] bgcngm:
You should assume that patch worked in case you don't see any related errors on Xposed debug log right after the following entry: "GB:PatchFakeId: Patching FakeID vulnerability".
[Xposed Framework Modules] valk791:
[MENTION=5008415]C3C076[/MENTION] thank you so much for brightness tile. I think the other tweaks in brightness management above will be more than welcome from many users for avoid the battery drain.
[Xposed Framework Modules] jbdan:
Curious C3... I've noticed some slightly abnormal behavior with auto brightness since updating to the latest GB ver. It's not a deal breaker by any stretch of the imagination but was wondering if you knew why. Or, it might just be a random one/two time occurrence. No changes on my end stock ROM Nexus 5
[Xposed Framework Modules] C3C076:
No brightness related changes either. Apart from tile long-press to toggle auto-brightness on/off which certainly doesn't affect how auto-brightness behaves.
[Xposed Framework Modules] el_smurfo:
UNC

So, I've been playing with UNC this morning, trying to replace LightFlow. I have a red LED set for gmail, 1000ms on, 2500ms off, but it only lights up once, then never again? Could the active screen somehow be interfering? Shouldn't the LED blink until the notification is cleared?
[Xposed Framework Modules] C3C076:
No. Standard android behavior is to dismiss led as soon as screen is on which has logic behind it - why do you need led when you're already checking your phone?

I had to change this standard behavior for active screen feature so the led is kept active when screen comes on and comes off after timeout (situation when user is away from device so he/she is able to see led after returning back to device later).
[Xposed Framework Modules] slimm2:
Thanks for the update. But still the same issues... :(
[Xposed Framework Modules] el_smurfo:
Well, for many of the other active display apps, such as ACDisplay, the screen coming on dismisses the LED notification. Lightflow does not operate this way, so when I return to the phone, the LED is still blinking which is the behavior I am trying to replicate.
[Xposed Framework Modules] C3C076:
Please, search the thread before posting (XDA rule no.1). If you checked earlier discussion of last few weeks you would already know that MTK support is planned for the future -after I receive thl 5000 I bought for development.
[Xposed Framework Modules] C3C076:
That's exactly how active screen feature in GB is done. It keeps led on until you start interacting with device.
[Xposed Framework Modules] slimm2:
Nice to hear, I hope you enjoy that phone :)
[Xposed Framework Modules] el_smurfo:
Can it also be made to work with ACDisplay or Dynamic Notifications? Perhaps if the screen is only on for 5s or less, the LED notification is retained?
[Xposed Framework Modules] slickdap:
The new update has a very annoying bug

I noticed when I have my charger in, this weird background music keeps playing. Even when I Unplug it, the music doesn't stop. This only happens when I set the charger plug in sound to silent. Anyone else have this issue? I'm using a T-Mobile Galaxy s5.
[Xposed Framework Modules] Rydah:
i came here to report that too. no sound is selected for charging and unplugging...
[Xposed Framework Modules] C3C076:
I can't reproduce such behavior. I am getting no sounds when I select "None". Also be aware that this feature affects only when cable is used for charging. Standard wireless charging notification is not affected thus will always play (standard android behavior).
[Xposed Framework Modules] Rydah:
Yeah, I'm connected via cable charging and when i plug or unplug is plays my default ringtone even though all settings for it are set to none. Just started after the last update, I've wiped my data for the module, still playing the sounds... I've disabled the module, rebooted and no more sounds...

HTC One (M8) Running Stock 4.4.3 W/ Sense 6
[Xposed Framework Modules] jdubya45:
+1 for me...getting the "over the horizon" song on my Sammy playing over and over and OVER.
[Xposed Framework Modules] C3C076:
Well, give my greetings to Samsung/HTC for changing the standard AOSP way of how sound URIs are interpreted by ringtone manager...

Until I make adjustments (which I shouldn't be doing for unsupported devices), download mp3 containing only silence from somewhere and use it within GB charging sound settings.
[Xposed Framework Modules] Rydah:
Apologies on behalf of HTC. -_- For now, I just applied some sounds that are a bit more pleasant than my ringtone. lol

Thanks for your support.
[Xposed Framework Modules] C3C076:
I would be interested in seeing contents of /data/data/com.ceco.kitkat.gravitybox/shared_prefs/ com.ceco.kitkat.gravitybox_preferences.xml when options in GB are set to No sound. Can you attach that file here?
[Xposed Framework Modules] Rydah:
sure, one min. plz

EDIT:

Here you go.
[Xposed Framework Modules] C3C076:
Please, test attached APK for me and report back. Thanks.
[Xposed Framework Modules] Rydah:
that did the trick!
[Xposed Framework Modules] jbdan:
Perfect thank you. Guess it was just a random one time occurrence. Thanks for the great work as always!
[Xposed Framework Modules] galaxys:
3.3.2 is working a treat on my LG Gpad! Luv the new change log features! :cool:
[Xposed Framework Modules] aavvaallooss:
Which is the reason why 'Fake ID patch' is well detected using BlueBox scanner if applied from Tungstwenty module but no from GB? Just curious
[Xposed Framework Modules] anuajayan:
I too hav the same issue. .how to rectify it?
[Xposed Framework Modules] Pkt_Lnt:
read back a few posts....... backward is often more efficient than forward when up against the wall........
[Xposed Framework Modules] anuajayan:
Ya sorry..now itz fine..it worked..
[Xposed Framework Modules] anuajayan:
There is no stop or pause button for my screen recording. How to rectify it? Please help me out.
[Xposed Framework Modules] Pkt_Lnt:
Nevermind, You have an unsupported ROM.
[Xposed Framework Modules] anuajayan:
So no solution for this!!
[Xposed Framework Modules] jceballos:
Hi congrats for the good work with GB I don't need a custom ROM anymore.

I've noticed when I enable active screen my proximity sensor is on all the time while the phone is locked, is this harmless for the proximity sensor? I'm worried it might stop working due to excessive use. Is there a way to access the proximity sensor just before turning the screen on and keep it unused otherwise so its not in use all the time?

It would be something like this:

If a notification arrives then check the proximity sensor to see if the phone is covered (i.e. in pocket) if not then turn screen on, else keep screen off
[Xposed Framework Modules] C3C076:
Fake id module modifies bb scanner behavior by hooking on it via xposed and trick it to thinking there's no such vulnerability which is against GB's policy not to modify behavior of 3rd party apps.

For reliable results, listener for prox sensor events needs to be kept registered. It is not possible to read actual prox sensor state without listener registered. Since registering listener and receiving current sensor status event takes some time it would delay the active screen feature if done when notification comes. I didn't hear myself it's bad for the sensor. But anyway, I'll try to look if there could be another way around.
[Xposed Framework Modules] yochananmarqos:
Of course there is. However, you're using GravityBox on an unsupported ROM. Please read the OP before posting per XDA rules.
[Xposed Framework Modules] C3C076:
Expand notification with finger to see action buttons.
[Xposed Framework Modules] el_smurfo:
Acdisplay active mode has a small delay, and I don't notice that the sensor is always on. The code is open source and is a much nicer implementation IMO, take a look and see if the developer is OK with you using this portion of his code.
[Xposed Framework Modules] C3C076:
Thanks, but I would like to try to improve it myself. For me, it's much more exciting to find out and learn than to copy behavior from somewhere else.

Whole ultimate notification control is written from scratch by me and I would like it to stay that way.
[Xposed Framework Modules] m0han:
:cool: :good: doing great in the process!
[Xposed Framework Modules] Sam7777777:
Sir Latest update is buggy, kept playing music in background and took me some time to figure out it was this update which caused this

Had to revert back to previous version

N8000 touchwiz 4.4.2
[Xposed Framework Modules] freecore.mc:
I have the unplug/plug charger screen on disabled/unticked & I've rebooted but screen still turns on when I plug in charger (using Samsung s5)
[Xposed Framework Modules] mokorottyu:
Same problem. A ringtone starts to play when I connect the charger... Nothings run (music, movie player), and I can't stop it,:( I had to restart the phone... I had activated the statusbar brightness slider(or what), and the tap the statusbar to sleep.

Note 3 - n9005
[Xposed Framework Modules] tuniel:
again, read the OP. your device/ROM is not supported.

[MENTION=5008415]C3C076[/MENTION] posted a workaround few posts before yours.
[Xposed Framework Modules] jk77:
http://xdaforums.com/showpost.php?p=54926689&postcount=10516

Thanks a lot !!
[Xposed Framework Modules] yojlik:
Honestly given the support load with people using this on unsupported devices I don't understand why you haven't purposefully introduced things that make GravityBox unusable on them. Maybe I'm just cold-hearted or just sick of half the posts in this thread being either a question about why something doesn't work on their unsupported device or someone telling them their device is unsupported, but I'd just force the "always on while charging" ringtone to be a loud squeal and then just leave it.

Given the hassle these users cause it would seem to be in everyone's favor to simply do everything you can to prevent their use of the project.
[Xposed Framework Modules] kingvortex:
A lot of us (probably most people) that use the module on unsupported devices don't ask questions in the thread or expect any support. Is it fair to punish us as well?

I find the module very useful and would be extremely disappointed if this happened.
[Xposed Framework Modules] yojlik:
Fair or not, it's not my place to judge. I just said I'm surprised [MENTION=5008415]C3C076[/MENTION] hadn't done it as he's the one who is having to deal with the support problems. If I were in his place I would not be willing to do it, but I'm not him.
[Xposed Framework Modules] mokorottyu:
OK, I understand, I just "report" the problem. Until the last update it works fine
[Xposed Framework Modules] GermainZ:
The only problem is that you're using an unsupported device, you're on your own. Features may or may not work. Features that used to work may or may not break at any moment. Newly introduced or modified features may or may not make your device boot loop. In short: your device isn't supported. :)
[Xposed Framework Modules] kingvortex:
Then it's a good job you're not the developer of this module. Such a move would be petty, in my opinion. From what I've seen of C3C076, he wouldn't do something like that anyway as he seems to be a fair minded individual.

If anything were to be done, a database (maybe crowd sourced) of functions that don't work on some devices could be created and those functions could be disabled by detecting the device/rom type on install. That would be a fair solution, but I don't expect C3C076 to do this, as it's outside his intentions for this module. I simply just don't use the few things that don't work on my device.
[Xposed Framework Modules] GermainZ:
A warning (shown at the top of the screen in GB, in red) for unsupported devices might actually be feasible… unless I'm underestimating how many AOSP ROMs there are.
[Xposed Framework Modules] kingvortex:
If people do not read the clear sections on compatibility listed both in the description in the Xposed installer and this thread, then they're also perfectly capable of ignoring such a warning.

It's a strange attitude. "I know, I'll install this Xposed module that can do absolutely anything to my device, but I won't bother to read the description first!" :D
[Xposed Framework Modules] GermainZ:
A warning that's in your face whenever you open GravityBox can't be ignored as easily as the description/OP that you can just swipe away, though. ;) Will that stop complaints? No, but it will probably reduce them and it should be fairly easy to implement.
[Xposed Framework Modules] kingvortex:
You would be surprised what people will ignore! I agree that it would probably decrease the amount of questions about unsupported devices a little though.

It's disappointing that the increase of popularity of Android has also increased the amount of people that just want to make their phone "cool" and do not want to actually read up on things before using them or flash mods/roms without having a clue how to recover from problems caused by them.
[Xposed Framework Modules] marcelser:
got the point, but...

Hi,

I'm also one of this not supported device guys as I use a sammy rom. I completely understand that these roms are not supported and that we should not ask for assitance when using Gravitybox on such a rom. As someone said, features may break at any time or make your device bootloop or whatever. So I never before asked for a solution if something didn't worked as expected because I know I'm on a unsupported device and I'm fine with that. I would be also fine with a warning banner in Gravitybox for unsupported devices and text which says do not to ask for support.

But I'm not on a stock ROM because I want to. I'm on a stock ROM because there is no Vanilla AOSP ROM for "Galaxy S4 active", the only KitKat Roms that exist are either CM11 nightly (or based on it) and the sammy rom. So both unsupported and apparently the Sammy ROM is more stable and compatible with Gravitybox then CM. There maybe Vanilla ROMS for normal "Galaxy S4" but not for other S4 Variants like "mini", "zoom" and "active" (which I have) that have a small xda communiy and only few rom cooks. So owners of this phones like me are forced to use an unsupported ROM and we are nearly in the same situation like the people which had the MTK6589 phone which for which Gravitybox was developed for initially. Count yourselves lucky if you have a phone which has such a ROM.

Therefore and as this sound playing bug makes Gravitybox for all sammy rom users completly unusable and it seems there is already a fix (as C3C076 already posted a working version) I kindly ask to fix it (or just disable it) for next/upcoming official releases.

Thanks a lot for your understanding and I'm really sorry to ask for assistance this one time for my unsupported ROM.

Best regards,

Marc
[Xposed Framework Modules] Pkt_Lnt:
You were reporting a problem that was already fixed so you wasted space because you did not read back a couple pages or search.

I like the red flag warning, then require a pin code that is at the bottom. Call it a qualification test to use this awesome code! :D
[Xposed Framework Modules] shag_on_e:
Okay, first issue ever found is a weird one. After this newest update, as soon as boot is complete, a Verizon ringtone continuously plays over and over again. I figured out which one it was then deleted it from /system/media/audio but after reboot it kept playing somehow! Very strange, it sounded echoey, and there was no processes I could find at quick glance that were running to play it. I'm running a Verizon GS4 stock NC5 4.4.2 rooted and Xposed. I will reproduce and provide logs during lunch today. Thanks
[Xposed Framework Modules] Ja_som:
Are you kidding...
[Xposed Framework Modules] trjlive:
Wow, seriously?!? Did you even bother to read the couple posts DIRECTLY above yours? This is the kind of posting that really is frustrating for those of us trying to provide help in this thread. How can you expect anyone else to try and help you, if you can't even try to help yourself first??
[Xposed Framework Modules] shag_on_e:
Not at all. I don't kid about android, and I know my way around the system. Been modifying for a long time now. That's why I mentioned how strange it was. I knew it was GB because immediately after the update and reboot this ringtone kept playing over and over. I unchecked GB from Xposed and no tone. Checked it back, ringtone plays. No way to stop it, rebooted several times, deleted the file being played, nothing except disabling GB worked.
[Xposed Framework Modules] trjlive:
If you had read through the last two pages of posts, you'd see this has been widely reported to be an issue on unsupported devices (which includes your Verizon GS4). C3 is working on a fix, but it's not exactly high priority since it works just fine on supported devices. You can try this patched apk he posted earlier. Otherwise, will just have to wait for an updated version.

http://xdaforums.com/showpost.php?p=54926689&postcount=10516
[Xposed Framework Modules] sadonlyone:
same here using samsung s4 i9505: boot loop sound. version 3.3.1 worked fine. we'll have to wait, I guess.
[Xposed Framework Modules] bgcngm:
What haven't you understood? The .apk that includes the fix to that problem was already released (read above posts).
[Xposed Framework Modules] trjlive:
This is just one of those circumstances where a new feature was introduced and tested on supported devices, but unfortunately causes a problem on unsupported devices. These types of things can and do happen, there is absolutely no guarantee that GravityBox will continue to work on an unsupported device. At any time, an update may break things, which should be expected. You should always keep a safe copy of the latest version apk that works for you, in the even you need to revert back. This is just an unfortunate side effect of using a module on a device it wasn't designed for.
[Xposed Framework Modules] grisu59964:
Hello,

thanks for this really nice Xposed module which is the main reason why I keep the stock firmware on my phone.

As I saw some misspelled words in the German translation, I want to provide a corrected version which is attached to this post.

The main reason is the word "Standart" that has to be spelled "Standard" – which is a common mistake.

I hope my changes will be integrated.

Regards
[Xposed Framework Modules] bgcngm:
Wouldn't you prefer to submit your translations directly through Github? It is much more convenient for us to include such updates.