yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] A1ps:
Since updating to 4.4.3 notification LEDs have stopped working properly. Sometimes they flash upon receiving email, text etc Sometimes they don't. I've reset everything and rebooted but still getting same scenario.

I haven't added anything new other than 4.4.3.
[Xposed Framework Modules] C3C076:
Mine work exactly the same way as they did on 4.4.2. But I've seen quite many people complaining in 4.4.3 discussion thread. Some posted that disabling and reenabling pulse notification light in display settings helped.
[Xposed Framework Modules] trjlive:
The notification LEDs work fine on my Nexus 5 running 4.4.3 with only GravityBox Xposed module. Are you running any other Xposed modules? If so, I would disable everything except for GB, then reboot, and see if the problem still exists. Sometimes another module can cause conflicts with GB, even if it doesn't really have anything to do with the LEDs. These are complex modules, and have so many hooks into things, that sometimes the bugs are caused by the last thing you'd expect. Also, you didn't mention what device and ROM you are using.
[Xposed Framework Modules] A1ps:
I'm running a N5 and stock ROM, a couple of other xposed modules. But these have never affected LED notifications before. Only these last few days.

I also tried disabling LED notifications in android settings. This also didn't work.
[Xposed Framework Modules] jacknicholson:
For those odd times I feel compelled to know the exact time, Hamt Clock has served me well since I was on Gingerbread. It's crude, but then, it's a flashing clock.

That said, XuiMod will add seconds to your status bar. From what I gather, it seems to be compatible with GravityBox.

I recall my LED was a little wonky after I first received my N5, although I've somehow since forgotten to notice if it's still a problem. At any rate, this appears to be an on-and-off bug for a select few Nexus users, dating back to the N4. We can at least rule out a hardware fault for you.

In which case, much as no one (except trjlive, apparently) likes to do this, more often than not a clean flash will generally unlock all the secrets of the universe. Worst case scenario, you can just restore a nandroid if nothing radically improves.
[Xposed Framework Modules] A1ps:
JM

Now the odd thing is I'm getting a blue LED flash for Gmail or XDA - even though I haven't added these to notifications!

I've checked and it doesn't seem to be an app option. So can only assume its coming via GB!

PS no way am i going through a fresh restore!!! LOL!
[Xposed Framework Modules] jacknicholson:
Be sure you haven't mistakenly set your UNC Default settings to blue. Otherwise, the easiest way to know would be to disable your modules, one by one, sending yourself a few emails along the way. Might as well begin with GB first.
[Xposed Framework Modules] A1ps:
Just checked and default settings are set to Off.

I might just uninstall GB and then reinstall. Good idea???
[Xposed Framework Modules] LibertyMarine:
don't know wheter this has been posted yet... but on 4.4.3 HTC One M7 Google Play Edition the Home-Hardwarebutton doesn't work properly,... so when I doublepress it, GravityBox doesn't recognize it.. but normally without gravitybox the key works perfectly..

just as some kind of bug report... if you need more information, pls tell it
[Xposed Framework Modules] Jsilver73:
When I use the nav bar and set long press actions they work for a while then when I short press I only get the long press action. Any help with this much appreciated as I have only just started using this as recently switched to ge for daily driver and gravity box makes it much nicer :)
[Xposed Framework Modules] Pkt_Lnt:
You are not using an AOSP or GPE ROM, that is the problem. Read post #1, especially the RED PARTS.
[Xposed Framework Modules] Jsilver73:
Errrm - AFAIK dandvh is a pure GPE ROM?
[Xposed Framework Modules] Pkt_Lnt:
Google Play Edition? Comes on the phone you buy from Google Play Store? Is davidvh a Google programmer?
[Xposed Framework Modules] C3C076:
Check out Navigation key actions / Disable doubletap for home key. I can't remember what its default setting is but might be disabled.

Make sure you have turned on master switch for navigation bar in navigation bar tweaks section. That's a requirement for some navbar key actions to work properly.

(Turning on master switch requires reboot)
[Xposed Framework Modules] Jsilver73:
No I don't think so. I'm not really sure about programing etiquette, would this then be pure AOSP?

There is a link to the thread in my signature - like I said - built from official GPE source code. It is vanilla android.
[Xposed Framework Modules] LibertyMarine:
yeah it was enabled... so that I can doubletap.. the strange thing is that I imported the settings from 4.4.2 to 4.4.3 and the only tweak that doesn't work anymore is the doubletap ... but it's only on the home button, the back button works fine
[Xposed Framework Modules] cadarn07:
This is the description of that ROM:

"This is the latest build for the I9505-G Google Edition S4 official from Google/Samsung, I have made quite a few optimizations to the ROM and added the tools necessary to give it the features (100% working features that is) of an AOSP ROM, Google edition does not use open source proprietary which mean's Bluetooth, and most importantly the camera will work way better out of the box since Samsung builds this ROM (Full HDR support, 1080p video recording, no green lines on the front cam)"

I might be wrong but that does not sound like vanilla android. It's swirl at best.
[Xposed Framework Modules] Jsilver73:
OK, I give up then :eek: thought it was vanilla, maybe I'm mistaken. Thank you for taking the time to have a look though, I'll continue this discussion on the ROM thread and see what other users experience is.
[Xposed Framework Modules] cadarn07:
Don't get discouraged - your ROM is closer than many to vanilla. Most of Gravity Box's features will probably continue to work just fine for you. There just won't be a solution for the inconsistencies here and there.
[Xposed Framework Modules] C3C076:
Well, back button doubletap is my own implementation as there's no such feature in AOSP. While for home button native doubletap feature that's in AOSP is reused. I have to check if anything changed in this regard in 4.4.3.

Edit: seems to be working fine here
[Xposed Framework Modules] ImbaWind:
Hi dev, I dropped my n4 last time and the navigation bar part of the digitizer isnt working so i increase the navigation bar by 20% as a workaround. Until ytd it seems that the digitizer had gone worsen that it cant detect my touch even i increase it to 150%, I think 200 % would be enough so i hope gb will have the ability to increase the navigation bar height by 2x or higher in nex update so i can continue using my phone without using pie control.

Thanks in advanced
[Xposed Framework Modules] LibertyMarine:
I think there was a mistake during the installation process ... because after I reinstalled the Xposed Framework almost every bug dissapeared.. so this wasn't an issue with GravityBox

thanks anyway for helping me !

LibertyMarine

Edit:

After restarting my phone the double tap on menu button doesn't work anymore

Edit:

It only doesn't work if I have software navigation key enabled... so because some apps show the three dots menu, I enabled the navigation menu to set the height to 0% that the navigation keys are not shown ... but I'll look for a workaround myself ;)
[Xposed Framework Modules] Synthic:
Thanks for the very speedy update to 4.4.3 compatibility! I just have a small request. Since GravityBox is home to a plethora of visual tweaks already, would it be possible to add an option to change the appearance of toast notifications to that of Jellybean?
[Xposed Framework Modules] JoaoVr:
Is there a option to hide gravitybox icon without using other 3rd party pluggins?
[Xposed Framework Modules] XieTzu:
The manufacturer of my mobile will update soon my terminal model to KitKat. Will my Paypal ID be valid for GravityBox KK if i've contributed to the version for JB or I need to make a new donation to unlock some features in KK version?

Enviado desde mi bq Aquaris 5 HD mediante Tapatalk
[Xposed Framework Modules] C3C076:
You can use your existing id.

But the question is about compatibility. KitKat version doesn't fully support mtk devices so more incompatibilities can be expected compared to JB version.
[Xposed Framework Modules] XieTzu:
Oh, ok, I didn't know! Anyway, thank you!

Enviado desde mi bq Aquaris 5 HD mediante Tapatalk
[Xposed Framework Modules] Nezam:
Does this allow me to record screen with audio via mic? that too for unlimited time??

Thanks
[Xposed Framework Modules] C3C076:
Yes, but it's temperamental and device dependent. There's an option to use alternative screen recording binary which supports audio and up to 30 minutes of continuous recording.
[Xposed Framework Modules] xI mEzMeRiZe Ix:
This mod is amazing. A few requests for things that I miss from CM:

1) By default, when immersive mode is active, either manually or automatically by an app, using the volume rocker makes the nav and status bars appear. CM made it so that only the volume indicator would appear and the system bars would remain hidden.

2) CM has an option to block gesture touch events, which means that swiping from the edge in immersive mode to show the nav and status bars won't register a touch event in the current app. This is extremely useful when viewing documents or reading books because it prevents you from accidentally scrolling when gesturing to make the nav and status bars appear.

3) I've mentioned this one before: name of connected bluetooth device in the bluetooth quick settings tile. Pretty self-explanatory.
[Xposed Framework Modules] C3C076:
Yeah. 2) and 3) are in my stack so I'll get to it one day.

But I'm curious about 1). I tried to show volume panel during expanded desktop on (set to full immersive mode) but the bars stayed hidden.

Screenshot attached.
[Xposed Framework Modules] ImpheOtus:
I don't know why long press is not working for you after some time, but one thing is for sure: danvdh GPe ROM is 100% compatible with GravityBox.

I've been using both since November 2013 and everything has always worked for me.

I'm now on danvdh GPe 4.4.3 and the ROM keeps working without a glitch.

Dan always develops from stock and just modifies some files to improve smoothness.

Keep trying. Wipe, delete data and start over. It should work and it shouldn't be difficult at all. I've never had any problems.
[Xposed Framework Modules] ffejy462:
Speaking of immersive mode, is there any way to change the delay from when nav keys are on screen to when they disappear? It's right around four seconds, which imo is a bit on the slow side. The three options (animation and duration), under developer options in device settings do nothing. If not, could this make into gb?
[Xposed Framework Modules] bundysoat:
QuickSettings reordering not work for me in AOSP ROM for Lenovo p780, anyone know why??

Some bugs more, brigthness in notification bar and anything more that i don't rember now.
[Xposed Framework Modules] A1ps:
C3C076 I know a while back that you said that due to the way the nexus works it wasn't possible to rotate LED notifications if you had more than one notification for different apps (email, hangouts, gmail etc).

But I just noticed the other day when on the rare occasion my WhatsApp had a group message the LED was flashing green. Then when I got an individual message the light changed to purple. these notifications were from the standard WhatsApp app.

This is a new thing I'm assuming has kicked in from 4.4.3.

With this in mind, do you think it may be possible to have the LEDs change colour if someone has several notifications?
[Xposed Framework Modules] comebui:
Gravity Box Heating issues?

Hey Guys,

I am new to GB and Xposed... However I can't seem to keep GB activated for long. it heats up the camera/flashlight area on my Nexus5.

This is my configuration;

Nexus 5 with Stock ROM 4.4.3 , Franco Kernel 53, Xposed Framwork with XGELS (active) and GravityBox 3.1.5

I noticed if I keep GB activated it drains battery faster than usual. The main issues is if I have the screen on it heats up pretty quickly.

I thought to do a clean install (Fully wipe) with the newly release 4.4.3 and even after that I can't keep GB active.

Not sure, if this is only me as I don't see anyone else is having this issue

Any help is appreciated.

--

Comebui
[Xposed Framework Modules] jacknicholson:
I'm not really sure what you mean by 'activated', but the issue is almost certainly not GB, especially after a clean flash of the stock ROM. I believe the only notable (partial) wakelocks involve either the torch or button backlight notifications being presently active, and very momentarily if you use the 'Last Screen' option for your lockscreen wallpaper. The only option that can be CPU intensive would be the data traffic monitor, which is disabled by default and can be set to only display when the download manager is active.

Try disabling GB entirely from the Xposed module list, for at least a few days, and you'll surely find another cause at fault.
[Xposed Framework Modules] comebui:
Thanks Jack..

Yeah at the moment I have it disable and everything is find and dandy.. the moment I turn GB back on it starts the problem... I had the same feeling that it could be the torch .. so disabled torch from GB settings. Also I never switched on the data traffic monitor.

I really like GB customization......hate that I cant use it :(.... can't seem to figure out what's causing it... As other are not facing this issue... I now feel this has to do with some conflicting App... may be XGELS + GB + Franco Kernel ?

Or some other apps I have, like Tasker, App Ops etc.. I really don't know... I will keep on digging..
[Xposed Framework Modules] xI mEzMeRiZe Ix:
Are you on 4.4.3? I've updated my Nexus 7 and it works the same as in your screenshot, but on 4.4.2 it didn't work the same way.
[Xposed Framework Modules] C3C076:
It's not about it's impossible but more about a solution that wouldn't eat battery. For led to rotate colors, CPU must be online which would definitely drain battery.

I doubt they changed something in 4.4.3. I would say that's something that's controlled directly by WhatsApp. Maybe they use direct led control instead of notification led control.

I would try with stock or other kernel than franco which had lowered thermal throttling too much when I tried it resulting in phone getting hot easily. I'm happy with elementalx. It's rock solid stable for me, has improved performance and option for level of thermal throttling that can be chosen during installation.

Yeah. Most likely they changed behavior on 4.4.3.
[Xposed Framework Modules] trjlive:
Because GravityBox was not designed for your device and ROM. If you were to read the OP, especially the part about compatibility, then you would know that GB is only designed to be used with pure vanilla AOSP, Google Play Edition, and Nexus devices. The Lenovo P780 does not come with pure vanilla AOSP, nor is it a GPE or Nexus device. A custom ROM based on AOSP is still not pure vanilla AOSP. In other words, there is no ROM available for your device that is compatible with GravityBox. So if you choose to use GravityBox with your device, you do so at your own risk, and without any support, and understanding that there will be bugs and at any time it may stop working or cause more serious bugs.
[Xposed Framework Modules] A1ps:
Thanks mate. As you may well have figured out i know nothing about the mechanics of developing. Battery life is much more important than flashing LEDs.

But about WhatsApp - the odd thing is there hasn't been a WhatsApp update since 4.4.3 released. Strange!!
[Xposed Framework Modules] trjlive:
WhatsApp has always kind of gone around the standard Android method of notifications. This is why many mods that tweak the notification process in Android seem to have no affect on WhatsApp. They aren't sending notification through the system-wide GCM (Google Cloud Messaging) service. The app directly processes and displays its own notifications, sounds (if I remember correctly, they use the audio-stream, not notification-stream), and apparently, directly accesses the LED instead of using the Android LED hooks. Because of this, it also makes developing mods that allow the tweaking of WhatsApp notifications, as at any time, WhatsApp can change the code and method they're using, which breaks any of these custom methods that other devs have implemented.

As an example, this is why WhatsApp doesn't play nicely with Greenify, which supports GCM push notifications to hibernated apps. If you hibernate Hangouts, for example, and have the GCM advanced feature enabled in Greenify (in the donation version only), you will still get push notifications for Hangouts, because the are process through GCM, which Greenify intercepts, and then sends to the hibernated Hangouts app. With WhatsApp, notifications don't come through GCM, so if you hibernate WhatsApp, you'll never get any notifications or alerts. WhatsApp simply doesn't use the standard system-wide methods of presenting notifications to the user.

This also means that the WhatsApp process is always running, waiting for notifications from the WhatsApp servers. Because it doesn't use GCM, the process can't go to sleep and just wait to be woken by the GCM process. This does use more battery, though not a huge amount, I will give credit to WhatsApp for developing a listening process that isn't too battery-intensive. But they really should have used the standard GCM method, I just can't think of a reason why they wouldn't.

Hopefully that kind of helps clear it up a bit. :)
[Xposed Framework Modules] comebui:
Great Suggestion C3C .. flashed ElementalX kernel ...and activated GB and things are cooler now :good:

I don't want to get ahead of myself... But I am liking what I am seeing. (Will observe this for few days)

Only reson I want franco is the headphone boost kernel settings... that is the only thing which is missing from EleX .. I didn't seem to find any settings for it in the the XDA thread or elementalx.conf file.

Thanks a Bunch!!....

--

Comebui
[Xposed Framework Modules] jacknicholson:
Oh wow, I hadn't actually noticed over the past week (the ways we take things for granted, when they work as we want them to), but now that I have, I'm incredibly glad. I think this should be it. https://android.googlesource.com/platform/frameworks/base/+/ca4d040

Not to derail, but WhatsApp does actually use GCM (at least now), and will successfully receive pushes while hibernated. BBM, if I recall correctly, is the one that consistently maintains an open connection to their servers.
[Xposed Framework Modules] trjlive:
OT

Just wanted to mention a mod that might help you, I use the Viper4Android audio mod with my Nexus 5, and it has the ability to increase or decrease the dBm for the individual outputs (speaker, headphone jack, bluetooth). I know people are pretty polarized when it comes to V4A (either really liking it or really hating it), but I've never had a problem with it.

I don't enable very many features, but I do increase the headphone output by 5 dBm which helps increase the volume when I plug it into my car's aux input. Otherwise, the audio from my N5 is so much lower than the radio volume, when I switch from aux to radio, the speakers would go from normal audio level to blaring loud. By increasing the headphone jack audio output, I've better normalized my car's audio levels.

I also use the equalizer settings for all my outputs, using the Acoustic pre-set, which gives me excellent sounding audio in my car, on my headphones (I use the Apple EarPods), and through a Phillips bluetooth speaker in my bedroom. The only thing that V4A doesn't seem to work with is using Chromecast audio. I sometimes stream my Google Play Music app to my living room speaker system through my Chromecast, and V4A has no affect on the audio, which makes sense, because it's really just sending data over wifi, V4A would have no idea that's it's audio data.

Anyway, just wanted to mention this, in case it helps you out with your audio needs. :)

/OT

---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------

Ahh, ok my bad then. I haven't used WhatsApp in quite some time, so it looks like they've changed to use GCM now. That's good to know, thanks for the info. So disregard my previous post, I should have prefaced it with the note that it was based on my last understanding of the app, which is from a while ago. Anyway, thanks for updating me. :)
[Xposed Framework Modules] den_breacker:
Would it be possible to implement a way to disable the fact that when I wake up my phone with the volume keys (my power button is numb), this also changes the volume.

This is kinda annoying when listening to music. Every time I turn screen on, the volume changes.

I would suggest that when screen is off, pressing volume only turns screen on. When screen is on, pressing volume changes volume.

Thanks in advance !
[Xposed Framework Modules] C3C076:
I wonder what device/rom. Since standard behavior is that volume rocker wake is blocked while music is playing thus volume is controlled instead of turning the screen on.
[Xposed Framework Modules] den_breacker:
Nexus 4 stock 4.4.3 (but this was also the case on 4.4.2).

when playing music: pressing volume turns screen on + lowers/raises volume.
[Xposed Framework Modules] C3C076:
I see. Behavior I described above is in effect only while "volume keys skip track" option in media tweaks is enabled.
[Xposed Framework Modules] den_breacker:
I don't have that option enabled.

I remember when using custom rom's in the past that I didn't had this 'problem'. So I guess they implemented volume rocker wake bit different.

But I like stock + GravityBox more than a custom rom :)
[Xposed Framework Modules] lawrencem11102532:
Double tap home to sleep

I have a stock 4.4.3 GPE One m8. On 3.1.4, setting double tapping the home button to sleep worked perfectly, but on 3.1.5 it no longer works. However, the double tap to sleep function works if I set it to the back button. I've already tried uninstalling and reinstalling gravity box and xposed and neither of those processes fixed this. Does anyone have another solution?

Thanks.
[Xposed Framework Modules] ffejy462:
Yes, no, maybe? I have looked through the build.prop, but didn't see anything... Any ideas?
[Xposed Framework Modules] xI mEzMeRiZe Ix:
Would it still be possible to add the option? I doubt my G2 will see 4.4.3 anytime soon.
[Xposed Framework Modules] edgeicator:
Is it possible to add a "Fast charge" tile for those with a kernel that supports it? I currently use a GB action tile tied to a tasker shortcut/task, but the icon doesn't change like the tasker script says it should. The icon updates fine when used through a 1x1 tasker widget. The script I am currently using is http://xdaforums.com/showpost.php?p=42947205&postcount=5
[Xposed Framework Modules] samyong76:
using gravitybox on v3.1.5 on bigxie's 4.4.3 KK rom.

double tap on menu isn't working even i didn't disable it in the ROM

I read in other forums that you could delete a certain line in the build.prop to fix this weird bug, but it still isn't working. but that line doesn't even exist in the build.prop for this ROM! so im wondering if it is something wrong the xposed module.

anybody else has the same problem as me?
[Xposed Framework Modules] cd69:
Hey C. Not sure if this has been raised already. Search didn't yield too many results. However in 4.4.3. The airplane mode does not stick. Basically it I enable and then disable airplane mode the only way to get the network back is to reboot. Just wanted to highlight. I am on stock running elemental. Thanks

Sent from my Nexus 5
[Xposed Framework Modules] C3C076:
Hmm. I use it everyday without issues. Could be network related?