yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Pariahnoble:
I'm on the nvidia shield tablet, so dang near vanilla aosp. Heads up notification isn't working, on this build or the previous one. It did however work on this device on 5.0.1 but ever since the switch to 5.1 it hasn't worked at all..... Heads up is crucial, didn't realize how much I rely on it when I have my shield hooked up to the TV. (console mode) [MENTION=5008415]C3C076[/MENTION] thanks for the hard work on this module. I feel it's essential for any stock rom, and recommend it to anyone that will listen. Great job.
[Xposed Framework Modules] GoJo ^^:
"Show launcher all drawer" set as a hardware key shortcut doesn't do nothing.. I got NOVA launcher, what's wrong?
[Xposed Framework Modules] s2d4:
Answer is in your question.
[Xposed Framework Modules] modhack4life:
Deleted
[Xposed Framework Modules] GoJo ^^:
s2d4 so NOVA isn't compatible..?! Can't believe it..
[Xposed Framework Modules] Anderson2:
Thank you for this amazing app.

I'm not sure I understand. I don't think I have trust manager enabled (see image). Is it possible to disable trust manager?

Also what is the difference between standard and see through?

Thanks
[Xposed Framework Modules] bagarwa:
I've got one feature request and a bug report.

Feature request -

Right now with "Normalize dual tiles" enabled, when I tap the network tile, the QuickSettings pane switches to data management pane where I can toggle data on/off and see data usage details.Or, I can quickly toggle data just by long-pressing the network tile. My request is - can WiFi and Bluetooth tiles be made to behave in similar way, while "Normalize dual tiles" is enabled?

Bug Report -

If the system UI restarts for whatever reason, QuickSettings pane resets to 3 tiles per row even though the "tiles per row" setting in "Quick Settings management" still shows whatever value I had set. (I have set it to 4). It doesn't use that until the next reboot.
[Xposed Framework Modules] mdamaged:
Yes, with Tasker.
[Xposed Framework Modules] creeve4:
[MENTION=5008415]C3C076[/MENTION]

I have attached some updated Navbar IME navigation icons that fit the lollipop style better IMO, I hope you like and can use them. I'm no good with Github and submitting requests.

Edit: learned some GitHub, submitted pull request.
[Xposed Framework Modules] agnostic-apollo:
great work!

im using this on lg g3 cloudyg3 rom, its stock based...

i know GB is meant for AOSP but lg g3 tweaksbox needs

google services framework and i dont have that in my phone..

i also need only a few things and they all work great except battery percentage is causing problems..

i want the stock battery style and percentage but gravitybox tries to take over and its causing errors probably because of the aosp thing...

xposed logs are attached.

could you add a disable button like other tweaks so it doesnt automatically take over.. if thats the problem. could you take a look?

if you dont change your app for me, ill understand completely, no hard feelings...

thanks
[Xposed Framework Modules] kingvortex:
If you select "None" in the battery settings, then it shouldn't touch the battery style.

Apart from that I doubt C3C076 will make any changes, especially for a device he doesn't own, as it states fairly clearly in the first post that he won't.
[Xposed Framework Modules] agnostic-apollo:
if i select none, the battery disappears,

yes i read that and was hesitant of asking and i dont want him to work specially for my device

but a toggle might be good for others too..
[Xposed Framework Modules] kingvortex:
Well, I can't speak for him, but a toggle isn't needed for supported devices so that might be a factor.
[Xposed Framework Modules] agnostic-apollo:
yeah i guess you are right..
[Xposed Framework Modules] alazizie:
Still disabling OVERFLOW MENU BUTTON doesn't work, it must be there some works around.
[Xposed Framework Modules] DeezNotes:
Lockscreen PIN scramble... Would it be possible to add this feature? It is found in CM ROMs (as well as a few others).
[Xposed Framework Modules] Pariahnoble:
I posted earlier that heads up is NOT working. I can get it to work if I turn it on in ultimate notification control. I checked, and heads up works WITHOUT being FORCED to pay on 5.0.1 on 5.1 it only works if i purchase? Really? The options for it are in the free to use section. Why must I pay to activate it on 5.1? When the options in the free part of the app work on 5.0.1? Heck I'm already down to 30 reboots in less than a day. I test kernels and roms for people. Can this be addressed/fixed?
[Xposed Framework Modules] yochananmarqos:
Yes, you did already post about it. I skipped over your post. Guess why? You neither provided details about your device / ROM nor any logs. It's working for everyone except you. Literally. I've been following GB since it's dawn just over 2 years ago now and not one single person has complained of such. You test ROM's & kernel's, eh? You should know better. I don't know any ROM or kernel dev's that will bother reading a post like this let alone replying to it without these details. Drop the attitude, please.
[Xposed Framework Modules] C3C076:
This feature is launcher specific. GB is designed for AOSP, thus "Show launcher drawer" works for Android Launcher only / Google Now Launcher.

For 3rd party launchers, you can check whether launcher supports "shortcuts" to its functions; which can be used when you set "Custom" key action for a hardware key in GB.

(In, app picker, that shows when choosing "Custom" action, switch from Applications to Shortcuts).

Direct unlock comes into effect when lock screen is fully locked (lock icon shows it's locked and there's no "floating" circle around it).

Then when you turn display on, PIN/pattern or whatever security screen comes up automatically.

See through allows you to see main lock screen that contains clock and notifications, while security screen is showing.

So you can still be able to peek on notifications even if main screen is covered by PIN/pattern or whatever security screen.

Well, SystemUI crashing is a non-standard situation and can have undesired side-effects (such as one you described).

The best would be to find out why it's crashing. So you can fight the cause instead of a consequence.

Logcat taken during SystemUI crash would be helpful to pinpoint that cause.

Thanks, I'll check it out when I have more time.

Well, changes made by LG are quite intrusive. Not only they changed Android class names, they also changed internal variable names.

Master switch for battery tweaks might be too complicated as there may be some other dependencies within GB that rely on it.

Anyway, I'll take a look if it would be possible to at least eliminate those "mShowPercent" floods in the log.
[Xposed Framework Modules] bagarwa:
Sorry, I didn't mean system UI crash. After changing different system colors via LPThemer or changing settings in XBridge, I have to restart system UI for those changes to take effect. Both of these modules have the "Restart system UI" option inside their app. That's what I use to restart the system UI. The changes I made using them take effect and QuickSettings panel resets to 3 tiles per row.
[Xposed Framework Modules] C3C076:
Oh. Restarting SystemUI is basically making it crash on purpose. This is not the best practice neither when it comes to themes, nor when it comes to modules. You never know what other side-effects this can cause (like memory leaks causing degraded performance over time, etc.).

Anyway, I'll try to simulate such a crash when I have more time and nothing else to do; to see whether things at GB side can be adjusted to "survive" such activity.
[Xposed Framework Modules] Blade2014:
C3C076, kindly don't let you motivation down. Next for those who think that a patch is worth more than buying the full version, go do it. Better yet don't complaint about it here. As you are a genius in searching Google for the patch, also in the mean time, try to create some app, that is atleast 1% useful as gravity box. Then you will know the difficulty of the developers. Finally of you think that gb is not useful for you better not use it. Nobody is compelling you to use it...
[Xposed Framework Modules] Pariahnoble:
(I'm not gonna grab all the quotes so as not to take up space. But) to answer your question, no, I don't believe in pirating hard made products. But when I try to bring up (what is for me, myself) a problem with the app, being talked to like I'm a child is not something I'm prepared to accept. Truth be told, im still going to buy the app. I've used it longer than any other app besides mx player and Nova. That alone deserves my 3.46.

As for the issue itself. I'm on a stock aosp manufacturer rom (nvidia shield tablet stock ota 3.0, lp5.1) (and other apps that have their own method of tapping into LP built in heads up (Facebook) do work) And only when I turn on the heads up under ultimate notification control does it pop up. I've tried multiple times. And at each boot, my kernel control app pops a notification saying applying boot settings. It does not show up if I only have it turned on in the upper section, but does show if i have both the upper (status bar section think) and the ultimate notification as well. I can get logs, but I also am busy at the moment, it's midnight here.

Either way, Gb is great. This is the ONLY issue I've ever had. Look into, don't look into it. Either way I can get it to work regardless. Just have to wipe every 50 reboots.
[Xposed Framework Modules] C3C076:
Just going into some technical details to try to explain why things may be different for you between 5.0 <-> 5.1 heads up behavior.

In AOSP, default heads up decision logic is quite complex, but briefly, heads up shows for a particular notification when these main conditions are met:

- (notification is noisy (has sound or vibration) and is high priority) OR notification has a fullscreen intent (such as incoming call notification)

- heads up was not explicitly disabled by app that generated notification (by using public API extra flag: EXTRA_AS_HEADSUP)

- screen is on

- keyguard is not showing

- device is not day dreaming

There are more of them, such as dependency on current ringer mode (priority/none)

More details in shouldInterrupt function beginning at line 2078

Now, if OEM decided to change something in 5.1 regarding this decision logic, it will of course affect how heads up behaves on 5.1 and can be different than on 5.0

GB's notification control helps to tweak attributes that step into that decision logic - that's why you are able to make heads up work for notifications that don't have them by default in 5.1 (because of changed decision logic your OEM made in 5.1).

TL;DR: if your OEM decided for a different heads up logic in 5.1 compared to how it was in 5.0, this will of course make apps and their notifications behave differently.

Notification control in GB is an optional "upper layer" on top of default decision logic which allows to do further adjustments . It doesn't change anything about default decision logic as long as "Heads up mode" in notification control is set to "Default", thus uses whatever logic your OEM intended to make.
[Xposed Framework Modules] Pariahnoble:
Thank you for the info. With nvidia, there is no telling what they messed with (up) honestly. But at least I can "force" it to pop the heads up on all notifications by ticking the control in ultimate. But after probably 15 to reboots on a fresh flash, that option in ultimate (the only difference between reboots is that option being checked. With it on, heads up works like a champ. *shrugs* I dunno. May better minds than mine think on it. I just wanted to bring it to your attention, not start a flame war, and in no way intended to put down your work or criticize. Thanks for your work and time,and the info.
[Xposed Framework Modules] agnostic-apollo:
thanks a lot...
[Xposed Framework Modules] Midomad:
[MENTION=5008415]C3C076[/MENTION]

Could you please add

Long press lock icon to sleep and

Double tap to sleep on navigation bar

Cheers and thanks in advance.
[Xposed Framework Modules] nilanko:
[MENTION=5008415]C3C076[/MENTION] I know GB is not meant to work on CM but it used to work beautifully. Latest GB does work great on latest CM 12.1 for Moto E (condor) expect that the quick settings management tiles have completely stopped working :(
[Xposed Framework Modules] loldeXXXterlol:
Is this version for 5.1 or 5.1.1
[Xposed Framework Modules] Pi3rluigi:
It's working on 5.1.1

Inviato dal mio MI 3W utilizzando Tapatalk
[Xposed Framework Modules] Ja_som:
from 5.0 to 5.1.1
[Xposed Framework Modules] :
Thread cleaned a wee bit.

First, no warez talk is permitted on XDA....."unlockers" that bypass paid features included.

And second, how about we all post respectfully to each other. If you don't like something that's been posted, ignore it, or if warranted, report it. And if you don't like something about an app, move on then, try something else...the devs here do this for fun and share for free. :good:

Thanks,

Darth

Forum Moderator
[Xposed Framework Modules] agnostic-apollo:
[MENTION=5008415]C3C076[/MENTION] i asked about the battery percentage errors in my stock based lg g3, i just wanted to let you know that dont work on it for me.. gravitybox was causing a lot more trouble than just the battery percentage thing, so i decided to uninstall to even though its gonna be hard...

if i ever go aosp ill be back but thanks anyways.
[Xposed Framework Modules] Anderson2:
Rooted Nexus 7 2013 with 5.1.1, Nova Prime, and gravitybox for LL.

What are "trusted conditions" (referred to in direct unlock) and where do I decide what they are?

Thank you.
[Xposed Framework Modules] GoJo ^^:
Can't get floating notifications to run.. :(
[Xposed Framework Modules] adrman:
Set up your trusted conditions via "Settings/Security/Smart Lock"
[Xposed Framework Modules] cashinoda:
What device are you trying to run it on? Have you tried rebooting?
[Xposed Framework Modules] PIRATA!:
Hi there.

Did someone reported that this module can work (even if not at 100%) with Samsung Lollipop 5.0.1 deodexed TouchWiz roms?

I've read that someone used it, but would like to ask here either.

Tnx.
[Xposed Framework Modules] kolyan:
Does LED notification control work on Nexus 6?
[Xposed Framework Modules] Grzesiek1010:
long press volume up button to skip song dont work
[Xposed Framework Modules] Ja_som:
Works on my N7...
[Xposed Framework Modules] Rodeojones:
Is it possible to change (or completely remove) the carrier text from the lockscreen? I've looked everywhere and didn't see it.

Regardless, I've owned my N6 for two days and having this mod is fantastic. Thanks to all involved with making this possible.
[Xposed Framework Modules] dfcPE:
Yes, it works!

Enviado de meu GT-I9505 usando Tapatalk
[Xposed Framework Modules] abhi007.john:
Remove exclamation marks is not working.

I'm on cm12

Can somebody help?
[Xposed Framework Modules] Blade2014:
Cm ROM is not fully supported. AOSP and near AOSP ROMs are only supported. Read OP.
[Xposed Framework Modules] OrbitronX:
Greetings.

CM removed the intent tile and that's why GB can't manage quick settings tiles.

I have a fix for that and I've already tested it on 3 devices, it seems to be working.

Inside the archive below, you'll find 4 smali files.

Decompile SystemUI and copy those files in /smali/com/android/systemui/qs/tiles.

Recompile and you're done!

http://www93.zippyshare.com/v/3uYBvWzA/file.html
[Xposed Framework Modules] Fuzark:
Hey guys! I'm trying block quicksettings on lockscreen.

What in systemui i need edit? I already decompile systemui.

And i know that gravitybox already have a option to disable little peek when we tap on statusbar, but i like to know that to. I trying to learn about modify some systemui things.

Sorry about offtopic.
[Xposed Framework Modules] Raijin:
Dear [MENTION=5008415]C3C076[/MENTION]

What do you think about implementing something like this?

https://youtu.be/BUNMWsnVF90

Control cursor by swiping over stock keyboard.

To not interfere with swiping in keyboards, this could be done over the space bar.

This could have sensitivity and speed settings.

I had this feature in iOS Nintype keyboard and it was essential.

Thank you!
[Xposed Framework Modules] mdamaged:
You should put this in feature requests tab above, it will likely be ignored otherwise.
[Xposed Framework Modules] Raijin:
Thank you for the advice, I didn't saw it in Tapatalk.
[Xposed Framework Modules] PineSmokes:
When I use expanded volume or setting in this mod it causes my SystemUI to restart, I have disabled those settings since they won't work but I do like them any idea what the issue is? I'm using a Note 3, SM-N900T, deodexed stock ROM FOB6 v5.0
[Xposed Framework Modules] kingvortex:
This is your problem: Note 3, SM-N900T, deodexed stock ROM FOB6 v5.0

This module is intended for use with only the supported devices listed in the first post of this thread. You should read it for more detailed information, but basically some things just won't work on unsupported devices. :)
[Xposed Framework Modules] PineSmokes:
Can it be made to support more of these devices cuz it works perfectly except that setting which I'm sure could be updated to be fixed, so it's supported in my book hah
[Xposed Framework Modules] kingvortex:
You really should read the first post. :D

It clearly says the module won't be modified to make it work with unsupported devices. This is because it would be completely impossible for C3C076 to make everything work with every custom or OEM modified rom out there, especially when he doesn't own the device in question.

I myself use GravityBox on an unsupported device. I just don't use features that don't work.
[Xposed Framework Modules] PineSmokes:
Well thanks for your quick reply I normally read everything but I was too busy today but still curious hah.
[Xposed Framework Modules] salimtn:
Its 100% working with me

Thanks a lot [emoji5]

Any idea how to override cm12.1 navigation keys action with gravity box ? I can't change recent button
[Xposed Framework Modules] HorstiG:
Great, thank you
[Xposed Framework Modules] joro666:
Can you share your SystemUI.apk, or this must be done for each phone extra?
[Xposed Framework Modules] OrbitronX:
I have no idea. You could try it though and let us know.

http://www17.zippyshare.com/v/jzfiz7u1/file.html

The SystemUI found in the archive is for the build on the 20th of June.
[Xposed Framework Modules] joro666:
Its working nice. Thx!
[Xposed Framework Modules] goran_oh:
+1

Sent from my LG-D802
[Xposed Framework Modules] HorstiG:
I have the same Problems on AICP CM12.1 V9 Update 23.06, GB Quicktoggles don´t work any more . Thank you CM :crying:

What a cr...

Galaxy S5 G900f
[Xposed Framework Modules] DSA:
What was the point in posting this?
[Xposed Framework Modules] ksaad9:
Thank you very much for this module. I really love it. I have one problem though. The "direct unlock" option does not work with 3rd party lockscreens. for example AcDisplay. I hope you take a look and try to make it work.

Thank you very much for your work!
[Xposed Framework Modules] Fuzark:
If i add that line

<string name="pref_statusbar_disable_peek_title">Disable peek</string>

To strings.xml file of my systemui, it will work?
[Xposed Framework Modules] tanclo:
Thank you for your work. I've purchased the unlocker in support. I appreciate very much the quiet hours feature. It's very useful on my oppo coloros system (lollipop beta). While coloros does provide a basic 'do not disturb' feature, gravity box quiet hours allows the user to define quiet hours and fine tune on per app basis. Excellent features thank you once again.
[Xposed Framework Modules] HorstiG:
Can you read?

HGT - S5 G900F - Oneplus One - Tesla TTL7
[Xposed Framework Modules] redincali:
I'm not sure if you've done other modding, but if adding that line is the only thing you do then no. What you would be adding is a string reference only, not the actual mod for the "no peek".

~ via Xperia Z3, XDA App
[Xposed Framework Modules] C3C076:
GB is designed for modifying android system. It's not designed to make changes to 3rd party apps.

I'd like to avoid that at all costs.

Best way is to have a separate module for your 3rd party lock screen.

This is just a translation.

However, there's a source code of GB available so you can take a look at how it's implemented.

This is the particular commit: https://github.com/GravityBox/GravityBox/commit/3b534a67c39c9650a3b6094c417bb520f9ca83a0
[Xposed Framework Modules] Mariner_1712:
I would REALLY appreciate a "Nothing" long press option.
[Xposed Framework Modules] yochananmarqos:
Default is nothing, what do you mean? You could also try selecting Custom action, don't choose anything then cancel. It will end up as "(None)".
[Xposed Framework Modules] AmyClaraRose:
[MENTION=5008415]C3C076[/MENTION] hi could you add disable hardware buttons to your application please
[Xposed Framework Modules] justaway2:
I just updated my phone to 5.1 last night, and installed the new GravityBox. Is it just me, or is GravityBox for LP missing the nav bar long press options? I used to be able to set long press back button to kill foreground process. I can't find this setting anywhere now. The only similar thing I found was to add the additional custom button and set that to kill foreground process.
[Xposed Framework Modules] kingvortex:
The "Navigation keys actions" section isn't there?
[Xposed Framework Modules] justaway2:
Yup, it's still there. I found the setting.

It's been a long night :eek::eek:
[Xposed Framework Modules] KayDieWreath:
Great Mod!!

i love it especially the lockscreen app shortcuts :) can i request a plain white instagram icon please? :D
[Xposed Framework Modules] C3C076:
You can try to use your own custom icon.

- get icon of interest as a file and put it in phone storage

- within GravityBox lock screen shortcut slot for Instagram, long-press on icon preview

- choose/crop your custom icon
[Xposed Framework Modules] RusherDude:
Hey [MENTION=5008415]C3C076[/MENTION]

Today I randomly checked my xposed log.. and I found a veery spamming error: this one:

06-26 21:26:06.675 E/Xposed ( 1046): java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference
06-26 21:26:06.675 E/Xposed ( 1046):	at com.ceco.sbdp.ModSbdp$4.afterHookedMethod(ModSbdp.java:152)
06-26 21:26:06.675 E/Xposed ( 1046):	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:698)
06-26 21:26:06.675 E/Xposed ( 1046):	at com.android.systemui.statusbar.BaseStatusBar.removeNotificationViews(Unknown Source)
06-26 21:26:06.675 E/Xposed ( 1046):	at com.android.systemui.statusbar.phone.PhoneStatusBar.removeNotification(PhoneStatusBar.java:1411)
06-26 21:26:06.675 E/Xposed ( 1046):	at com.android.systemui.statusbar.BaseStatusBar$5$3.run(BaseStatusBar.java:467)
06-26 21:26:06.675 E/Xposed ( 1046):	at android.os.Handler.handleCallback(Handler.java:739)
06-26 21:26:06.675 E/Xposed ( 1046):	at android.os.Handler.dispatchMessage(Handler.java:95)
06-26 21:26:06.675 E/Xposed ( 1046):	at android.os.Looper.loop(Looper.java:135)
06-26 21:26:06.675 E/Xposed ( 1046):	at android.app.ActivityThread.main(ActivityThread.java:5254)
06-26 21:26:06.675 E/Xposed ( 1046):	at java.lang.reflect.Method.invoke(Native Method)
06-26 21:26:06.675 E/Xposed ( 1046):	at java.lang.reflect.Method.invoke(Method.java:372)
06-26 21:26:06.675 E/Xposed ( 1046):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
06-26 21:26:06.675 E/Xposed ( 1046):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
06-26 21:26:06.675 E/Xposed ( 1046):	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)

Again and again and again... The xposed log is MBs long now.

I noticed it just keeps being spammed even updating the xposed log without doing anything to the status bar.

I'm on Nexus 5, stock 5.1.1 LMY48B. Using the xposed alpha for 5.1.1 from 14/5/2015.

Thanks for your time!

PS: I noticed on the super alpha thread for 5.1 than romracer didn't update first post, but you posted some new version in there and so did dk_zero-cool few days ago? Maybe I should use those?

This is kinda a chaos lol, if the organizer doesn't update first post :(