yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Lancez:
Been running GB KK for a while and love it, but long press back button won't kill most of apps, ebay, amazon, google calender, Drive, Hangout, to name a few. am running latest 4.4.2 stock on Nexus 5.
[Xposed Framework Modules] C3C076:
Version 3.0.1 available

Changelog 3.0.1 - 31/03/2014

- Fixed volume key crashes on Xperia devices

- Notification control: implemented default settings

--- when enabled, all apps that have no active explicit settings will automatically use default settings

--- introduced trial period to allow users to check if notification control submodule works on their device

- Clear all recents:

--- fixed clear all key being stuck in navbar under certain conditions

--- workaround for AOSP bug that kept recents panel active in the background under certain conditions

--- fixed clear all key coloring in Pie (thanks to SilentException)

--- further optimizations (thanks to SilentException)

--- potential fix for SystemUI crash on Xperia devices

- Navigation bar: option to disable camera icon in lock screen

- Phone: fixed Home key not responding during non-intrusive incoming call

- Media: take increased music volume steps into account for safe headset volume

- Reorganized Clock settings (thanks to Minty123)

- Added Malay translations (thanks to zamzameir)

- Updated Russian translations (thanks to gaich)

- Updated Chinese (Traditional) translations (thanks to Eric850130, knight00931, momomok)

- Updated Polish translations (thanks to xtrem007)

- Updated Spanish translations (thanks to jvbferrer)

- Updated Chinese (Simplified) translations (thanks to liveasx, logicmd)

- Updated German translations (thanks to Minty123, LibertyMarine)

- Updated Japanese translations (thanks to WedyDQ10)

- Updated French translation (thanks to ch-vox)

- Updated Italian translations (thanks to pesa1234)

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

- Updated Slovak and Czech translations
[Xposed Framework Modules] SleemLDJ:
Thanks for the update.

(Xperia user)
[Xposed Framework Modules] petrus764:
Tried searching, but didnt find anyone asking about it.

Would it be possible to implement quicktoggles in the notification area? Like the CM feature. There are lots of apps that offer this functionality, but they all suck. CMs solution is really neat and open source, but I don't know how easy it would be to implement.

For reference, I'm talking about http://i.imgur.com/S7rU7rO.png
[Xposed Framework Modules] mnsk:
Clear all recent system ui crash is fixed in Xperia KK but long press function to keep the recent app only is not working.

Both long press and single press is performing the same function.

Also can you also please look into call vibrations in phone tweaks, they are not working too.
[Xposed Framework Modules] Enhanced:
Awesome update. Love the trial period for the LED Notification. Only suggestion here with it is to allow an "always on" option for the LED as I've never liked it blinking. Maybe allow the "on time" to be more than 3000ms, or is there a reason why that is limited (battery/resources, etc.)?

Secondly, is there an option to make the navigation bar completely transparent at all times and not just on the launcher/homescreens?

Thanks!
[Xposed Framework Modules] Tonio78r:
Seems like bugs on Xperia devices are fixed (volume adjustement was the problem for me) :)

Thanks :good:
[Xposed Framework Modules] nadiros:
Ewe....reminds me of Android 2.3 Gingerbread. Its funny how CM does this yet leave other mods out cuz "its not in the Android guidlines" lol.. Classic CM !
[Xposed Framework Modules] petrus764:
Not that anyone cares what this reminds you of, the icons and tiles are taken straight from quicksettings, only thing that's changed is the tile size and icon labels have been removed. So from a design point of view, they really are just as much in accordance with the design guidelines as quicksettings themselves.

In any case, I find them handy and would very much like to be able to use them with any aosp rom without having to install a crappy 3rd party app from the play store. Since a couple of people thanked my post, I'm guessing that a few others would appreciate this feature as well.
[Xposed Framework Modules] hedgegee:
Thanks for the update! :laugh:
[Xposed Framework Modules] nadiros:
Ok so my personal opinion vs you speaking for "anybody" [emoji15]

I guess what I meant was this :

You are referring to a legacy feature that also has a multitude of apps on the playstore to provide this functionality.

I cant speak for anyone especially the developer, however with xposed modules it is generally the rule that if it can be done with an app, then that's the way to go.

But by all means, choice is great [emoji4]
[Xposed Framework Modules] kolyan:
I am on stock N5, LED for 1st Hangouts SMS doesnt trigger the light, 2nd seems to work

Also is there way to enable LED for missed call?

Edit: just noticed that GV also doesn't work....it worked fine, then I missed phone call which didn't have any LED notification, then I missed GV text, and light was defaulted to stock color instead of the one I picked in app
[Xposed Framework Modules] dems86:
What is so crappy about Power Toggles?
[Xposed Framework Modules] C3C076:
The main goal was to get rid of SystemUI crashes, not to completely fix the feature. I can't do that as changes made by Sony to default recents implementation are unknown to me (no source code, no device).

The similar applies to call vibrations. Sony uses own non-AOSP dialer, which is another black-box.

N5 has a bug that prevents LED from working until device is unlocked at least once before receiving any notification.

Missed call notification fix is activated as soon as "Default settings" are enabled or you have explicitly activated notification control for "Phone" app.

The reason why you saw the different LED color is probably because there was another notification that came first - before GV (what's GV, btw?).

It could easily be your missed call notification blinking.

Android system has some kind of default logic that I am not sure I completely understand. But it seems like the LED is activated for the first notification that arrives. Subsequent notifications won't change LED if it's already blinking.

GB doesn't change the way how LED is controlled by the system. The only thing it does is that it modifies notification properties (doesn't control LED directly - system takes care of it).
[Xposed Framework Modules] xiayi:
Would like to hear the author's comments on these feature requests.

- Support for custom unlock ring icons.

- Change the padlock position on the unlock ring.

- Hide the status bar on the lockscreen.

- Display brightness percentage on the quick settings tile and the slider.

- Remove the top/bottom shadows when the status/navigation bar are transparent.

- Turn off the sound effects in the stock camera app.
[Xposed Framework Modules] ddskier:
I believe that I have identified a bug with 3.0.1. Since upgrading the recent tasks button throws a systemui has stopped error.

I have narrowed it down to having the RAM bar option enabled under misc tweaks. Running stock 4.4.2 nexus 7 2013.

Anyone else seeing this error?
[Xposed Framework Modules] trjlive:
Just keep in mind that the shadows actually do serve much more than just a cosmetic effect, they are functional. If you use Google Now, or have a very light background wallpaper, you'll notice the shadows prevents the status bar and nav bar icons/text from completely disappearing into the lighter elements below. With a darker background, the shadows aren't necessary, but in order to be able to completely deactivate them (if it's even possible), you'd have to ensure some way to maintain legibility of the nav/status bars with a light/white background.

---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------

I have updated to version 3.0.1, running a stock 4.4.2 Nexus 5. I also have the ram bar option enabled, along with a recent-button-long-press action. I have no systemui error (or any error) when using recents button, either normal press or long press. All functionality is as expected. So it doesn't seem to affect the Nexus 5.
[Xposed Framework Modules] sneaker8650:
Thanks for the Info, didnt know, there is a difference, between LG Stock and "Google KitKat Stock". :o
[Xposed Framework Modules] Ramnathe P:
"Disable Button Backlight" feature doesn't work for GT-I9000 Galaxy S. Please fix this. Thanks
[Xposed Framework Modules] DSA:
You have quoted the entire first post

Please fix this

Thanks
[Xposed Framework Modules] keyman91:
Hi, thank you for this amazing app. However, I have a problem on my device which is a LG G2 D802 running the stock LG 4.4.2 software. When I have GravityBox enabled, sometimes when I press the recents key, none of my recent apps will show up and I will have to press it again to make the apps show up. I have disabled all Xposed modules but GB and it still happens, however if I disable GB, the recents key will work fine.

I have attached the debug.log file and here's a video demonstrating the problem.

https://www.youtube.com/watch?v=dwEaNMhuIek&feature=youtu.be

I never used to have this problem back on JellyBean, however I recently upgraded my device to KitKat and now I have this problem.

Thank you
[Xposed Framework Modules] frikakwa:
LG G2... AOSP? :silly:
[Xposed Framework Modules] mnsk:
Ok sad to hear that :(

Nonetheless appreciate your work. Thanks!
[Xposed Framework Modules] onesolo:
Hmm, I have 3.0.0 installed but it doesn't appear the update on 3.0.1 on the Xposed app... any ideas?? Only manual update??
[Xposed Framework Modules] cadarn07:
3.0.1 appears in the xposed installer for me. Try a reboot if nothing else triggers the update and see if that helps.
[Xposed Framework Modules] The Tallest:
OK so I'm having an issue where it's either not recording a video when it says it is or it records but the video can't be played.

There's a link to my Debug file.

https://www.dropbox.com/s/yu70dp6uj45hd0c/debug.log
[Xposed Framework Modules] C3C076:
Yet another device specific incompatibility "thanks to" lg modifications. Things to try:

1) disable clear all key and rambar in misc tweaks

2) don't assign any actions to recents key in "navigation key actions". Keep them "Default".

And test to see if it gets better or not.

Try playing with the settings (type of binary, resolution) to see if you can find combination that works.

For screen recording debugging, it would be better to see a logcat of recording session rather than xposed log. Thanks, anyway.
[Xposed Framework Modules] keyman91:
Thank you for the help, I had the recents key set to toggle torch on long press. Disabling it and setting it back to default has fixed it. Now I can enjoy having GB enabled again :)
[Xposed Framework Modules] The Tallest:
Thanks for the help. Messing about with the settings got it to work. It's a great app. I just sent my wife a video on how to update the Moto Boot Animation App on the phone. She's had a smartphone longer than I have and she still can't do the most basic stuff. LOL
[Xposed Framework Modules] wardawgmalvicious:
For the signal cluster settings, when I enabled and my icons were white, a partial connection would show an orange color, however when I switched the icon color to a blue color (ff33e5b5) it would no longer turn orange. Is this by design or just a byproduct of changing from stock color? Just curious.

-wardawgmalvicious

Rooted N5/N7 2nd Gen

MultiROM TWRP

Franco Kernel

Stock 4.4.2 w/ GB & XUI

-Sent using Tapatalk
[Xposed Framework Modules] C3C076:
It changes. But not color but transparency. When partially connected, icons are less contrasty.

You have to use "gravitybox icons" for it to work.
[Xposed Framework Modules] shaunfrazier:
Does this work with art?
[Xposed Framework Modules] claytonjn:
This is based on Xposed Framework. Does that work with ART?
[Xposed Framework Modules] JoeDoom:
The Xposed dev has said he working on a compatible version but likely wont be released until ART is mandatory on devices.
[Xposed Framework Modules] wardawgmalvicious:
Oh gotcha, I thought that too, it did work with the "stock icons" before, and I switched to the gravity box icons, and still couldn't see anything. I'm not going to though I guess. I appreciate the reply!

-wardawgmalvicious

Rooted N5/N7 2nd Gen

MultiROM TWRP

Franco Kernel

Stock 4.4.2 w/ GB & XUI

-Sent using Tapatalk
[Xposed Framework Modules] claytonjn:
Actually, last I heard he said it definitely won't be released until ART is the default - and not just the default in AOSP, but the default on actual devices being released.
[Xposed Framework Modules] JoeDoom:
Well hopefully it gets sorted out by the time the Nexus 5 successor is out. I can't imagine a world without Xposed and GravityBox anymore!
[Xposed Framework Modules] shaunfrazier:
OK.. Well I really like the art.......... Is this as awesome as I hear?.. I have been changing Roms for a long time and up until this phone I was on a new one every week or so. This android 4.4 is impressive as hell.
[Xposed Framework Modules] wardawgmalvicious:
I have MultiROM installed, and I had never tried another ROM other than stock. With MultiROM I tried just about every ROM, and I was not impressed with any of them as much as I am with stock and Gravity box with a few other modules, but GB is the meat and potatoes of what makes my phone "mine". I highly recommend going Dalvik and Xposed with GB as the first module you install. Its amazing. I haven't tried ART personally but I simply cannot give up GB for ANYTHING! Its that awesome.

-wardawgmalvicious

Rooted N5/N7 2nd Gen

MultiROM TWRP

Franco Kernel

Stock 4.4.2 w/ GB & XUI

-Sent using Tapatalk
[Xposed Framework Modules] shaunfrazier:
Thanks for the opinion.. I'll give it a shot tonight after work.....
[Xposed Framework Modules] Maxr1998:
For me, it's absolutely the same :)

Nothing's better than stock (y)

Sent using my nexus⁴ running Stock 4.4.2 with Xposed, GravityBox, XThemes and hells-Core B45 KK
[Xposed Framework Modules] wardawgmalvicious:
Stock with GB gives you just about every option, if not every option.

-wardawgmalvicious

Rooted N5/N7 2nd Gen

MultiROM TWRP

Franco Kernel

Stock 4.4.2 w/ GB & XUI

-Sent using Tapatalk
[Xposed Framework Modules] parker09:
Would be be possible to get Paranoid Androids pie controls instead of CyanogenMods version in the future?

nvm: saw http://xdaforums.com/showpost.php?p=50784744&postcount=4777
[Xposed Framework Modules] ddskier:
Stange it works on my samsung s4 ge. In only errors on my nexus 7.

Sent using Tapatalk 4
[Xposed Framework Modules] iLikeTurtuls:
I want to post a bug report because I narrowed it down to this app but I can't be the only one experiencing this?? When I make a call, the digitizer continues working when the screen is black, so I end up hanging up on people and muting them. None of my settings have been changed in the phone tweaks menu. Is ANYONE experiencing this too? And yes I searched.
[Xposed Framework Modules] dr.wtf:
don't know if a log was posted already but heres the one for the fc when pressing recent apps:
[Xposed Framework Modules] kolyan:
Thanks. GV is Google Voice. I see, so selecting LED settings for Phone App handles missed calls.

PS. Somehow in recent update dev of Lightflow was able to make it work flawless and all LED notifications work even first one with locked phone
[Xposed Framework Modules] GR0S:
I have a suggestion, is it possible to reduce vibration time on dialer keypad? It's extremely annoying on nexus 5, because of vibration defect.
[Xposed Framework Modules] bjam19:
RE: Battery settings - color change options

would it be possible to add an option to change the charging indication color from green (to say, idk, #33b5e5)?

visuals:

not-charging: https://s3.amazonaws.com/pushbullet...rirPLlBYcy/Screenshot_2014-04-01-21-30-18.png

charging: https://s3.amazonaws.com/pushbullet...UgGJMyc37p/Screenshot_2014-04-01-21-30-08.png

as you can see, the green looks weird when paired with the blue everywhere else (yeah I know the clock doesnt match perfectly, but thats for a different module with the same problem, which I've also posted to)

thanks!
[Xposed Framework Modules] joshsurber:
Andrew uses a hack that causes a flicker of the LED every so often, meaning this flicker is the "first" notification to the user. It's in settings as ΠΞXUЅ5 fix if I remember right. (I ditched the bygones of LightFlow when Ultimate Notifications was added to GravityBox)

Tapatalk | ΠΞXUЅ5 | Stock KitKat 4.4.2 | Xposed Framework
[Xposed Framework Modules] A1ps:
My LED notifications in N5 have stopped working altogether. Nothing at all! All I did was update to 3.1. No other changes at all.

I've redone all the settings but still no luck.
[Xposed Framework Modules] nadiros:
Its not GB. You are using Touch Control app or just a kernel with s2wake/s2sleep correct?
[Xposed Framework Modules] frikakwa:
Did you try to lock / unlock your mobile once before testing notifications? This was already mentioned to do it first.
[Xposed Framework Modules] Masoud.Ser:
hi

GravityBox v3.0.1 is with problem

after Activate Battery percent text icon removed

please help

my device; xperia z1compact- f 4.4.2 rooted
[Xposed Framework Modules] fbf2201:
You're not running pure AOSP, hence GB is not 100% compatible. And that's why GB doesn't support non AOSP roms.

And btw, it's all mentioned in the first post.
[Xposed Framework Modules] StathisA:
thanks for the great application, i doubt i would switch to android if it wasn't this.

I have a rooted nexus5 and i have one question. is there a way to hide the google search bar from the "homepage" with this app??

I must be missing it but i wouldn't think its missing from the best customization app in android.For now i use the XPosed GEL Settings app to hide the search bar, but i'd delete it in a heartbeat if GravityBox does that as well.
[Xposed Framework Modules] nadiros:
No atm GB doesn't have this function.
[Xposed Framework Modules] StathisA:
Thanks for the prompt response. I do hope it will be added in the future!
[Xposed Framework Modules] CruxHumanus:
Question/suggestion:

Is it at all possible to eliminate the contact splash screen during a call? If, for instance, an unobtrusive incoming call is selected in settings, I would like the call/contact information to remain in the notification area. Also on this subject, would it be possible to answer/decline/end calls using hardware buttons?

I imagine the sample scenario would go like this:

A call is received in an unobtrusive mode, I answer using a volume up key without having to pull down the notification shade, a status bar icon indicates that a call is connected and ongoing, I then end it with a volume down key - all without leaving the activity I was engaged with before receiving the call, not even pulling down the notification shade.
[Xposed Framework Modules] kolyan:
My "Nexus 5 fix" is off, everything still works fine and no flicker. Actually the setting is called "Nexus 5 force led reset" now that I looked....by in any case its OFF
[Xposed Framework Modules] ImpheOtus:
Question: how are you going to decrease volume during a call?
[Xposed Framework Modules] CruxHumanus:
I suppose it wouldn't be possible to achieve in the described scenario, using the hardware volume buttons. I, for one, would find such trade-off an acceptable one. Maybe, instead of sliding the finger over the status bar to control brightness could be optionally converted to control volume in such cases.
[Xposed Framework Modules] C3C076:
It's been fixed in v3.0.1. Now MCC specific safe headset value is automatically increased together with volume steps

It's been confirmed earlier that it's the side-effect of dt2w or similar kernel features. Looks like panel remains active when screen is off.

Some kernels offer this feature with possibility to use only the bottom 1/3rd of the screen. But not sure if that automatically means that the top 2/3rd is inactive.

1) try with all other modules disabled to see if FC remains

2) logcat taken during systemUI crash is needed to track issue. Xposed log is of no help here.

Interesting. GB's notification control cannot currently control this. It would require some time dedicated to reverse engineering to see if hooking something within LED service would be of use.

But I would rather wait for 4.4.3 update where I suppose it's going to be fixed.

Did you manage to get it to work again?

Accept/Decline actions can be done directly from within non-intrusive incoming call notification which also has contact details.

I'm not sure I understand what you are missing there.

The other part about accept/decline using volume keys I find quite interesting.
[Xposed Framework Modules] dr.wtf:
i would but problem disappeared just like that...
[Xposed Framework Modules] CruxHumanus:
I'll try to explain myself from another angle, as I think I haven't presented my goal in a clear enough fashion.

Let's say you're in a car, have the phone connected via bluetooth to the car audio and running a navigation app. There's an incoming call. Firstly, I'd surely want it unobtrusive, otherwise, the call splash screen will cover my navigation app, which I obviously want to be kept displayed. Next, if I haven't got some car interface to answer the call with (buttons on the wheel, or such), then the current implementation will require me to pull down the notification shade and press the answer button. This action will demand me to focus on the screen and perform two actions. The mitigation would be pressing any one of the hardware buttons, volume up, for example, which will not require me focusing at looking at the phone, since I know where I have to press in order to accept the call. This is the first problem.

The second problem is that when I do answer the call, the call splash screen will be displayed for the duration of the conversation, while I want it hidden in the notification shade, so the navigation app would continue to be displayed. If not in the notification shade, then maybe something that's not covering a lot of the screen real estate, maybe a small 'card' with the basic call info and an 'end call' button (something reminiscent of the OmniROM implementation).

The main goal is to reduce interaction of the accept/decline/end call events, and more importantly, hide the ongoing conversation splash screen after a call had been accepted.

I hope I came through clearly this time :)
[Xposed Framework Modules] C3C076:
I don't think it's possible. InCallUi is an app. It needs to be focused in the foreground to work.
[Xposed Framework Modules] CruxHumanus:
It is possible to multitask with an ongoing call in the background, though. So isn't there a way to somehow emulate a multitask event immediately on call accept? Sorry if I am mixing up terminology here, I am just trying to stick to a certain logic here, while admittedly not really having much understanding of the android background processing.
[Xposed Framework Modules] C3C076:
Yeah, you're right, I forgot about this fact. The incoming call screen is the one that can't be escaped. You have to either accept or decline before being able to do other things. Anyway, it needs some research and browsing through the dialer internals for me to be able to say more.
[Xposed Framework Modules] CruxHumanus:
I sure do hope that some day you will find the time to research this topic, and that it'd turn out as a not too complicated of a task!
[Xposed Framework Modules] A1ps:
C3C076 I've tried everything but LED Notifications still not working properly. They do though work randomly.

Also, when they work, the colour I've picked for that specific notification isn't the colour that actually flashes (and I did check that I only had a notification for one app and not from any others :) )
[Xposed Framework Modules] claytonjn:
You could accomplish this pretty easily with Tasker, and probably most other automation apps.

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[Xposed Framework Modules] Jason_Nguyen:
View attachment 2665252 there's a small bug when I go into landscape apps the application launcher button doesn't fade like the others.