yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] C3C076:
Actually, that's not a bad idea. Will think about it. There shouldn't be any side-effects as NT_WCDMA_PREFERRED is a fall back value in case Setting was not found in the database. But there can be other issue as well.

Provide xposed log, not logcat.

Btw, "essenatially stock" doesn't mean the ROM dev didn't make changes in PhoneWindowManager (part where expanded desktop logic takes place) that could break GB compatibility. I recommend to backup your current ROM and flash the factory image to see if expanded desktop works there. But I suppose it does as you are the only one reporting this for Nexus 7 2013.

In logcat I can see a quite lot of errors coming from other modules. Also StrictMode violations which could mean some module is trying to read it's prefs from disk too frequently making too many I/O operations which certainly affects performance. I recommend to disable all modules but GB, check if things improve and then start enabling other modules one by one to see when issues start again.

Also I can see ART crashing and it is not a good sign as it can have many side-effects related to xposed framework and modules' functionality.
[Xposed Framework Modules] Ok_Kaleidoscope5109:
[MENTION=5008415]C3C076[/MENTION] Hi it's me, the annoying guy again!

I'm not sure I understand how the Notification Ticker setting works. Once I turn it on, the only options I have are "Default" and Always Disable. From my understanding Default is just standard Android behavior right? Is there any way to force Notification Ticker to be the default? It doesn't seem to work the way I thought it would similar to that "Restore Notification Ticker on Lollipop" module.
[Xposed Framework Modules] dioxide95:
I will disable all others and keep GB enabled. I don't understand one thing though, I had exactly the same modules on Android 5.0.1 and it never crashed/lagged. How is it possible now?

And I request you to tell me what to do with the ART crashing, please? I know it is a bit off topic. I did a clean flash of stock 5.1.1 and now I'm facing problems.

---

Nexus 5, Android 5.1.1 (Stock LMY48B), ElementalX 4.02, Xposed 3.0(alpha2), Viper4Android Audio, rooted (duh)
[Xposed Framework Modules] htr5:
Anyone else having issues with the double tap to sleep?

When you double tap to sleep and then press your power button to wake the device, the notification slider is halfway down.

I use swipe to unlock and have to first slide the notification panel away.

Edit: the issue only occurs if the double tap is in the part of the status bar the slides down to quick settings.

[Running GPE 5.0.1 for S4 and latest GB]
[Xposed Framework Modules] GabbyWC:
One of the GravityBox QuickSettings features I occasionally use is the compass. When I align an over-the-air antenna or satellite dish, for example, should I aim according to the magnetic or true azimuth number? There's usually about a 10° difference between them.
[Xposed Framework Modules] ARAVIND_PAVAN:
----DELETED----
[Xposed Framework Modules] C3C076:
Not annoying at all :)

Ticker policy options have some history behind. Feature was introduced in KitKat and had following policy options:

- Default (obeys system behavior)

- Disable on lockscreen

- Disable on secured lock screen

- Always disable

2nd and 3rd are not relevant on Lollipop, as there's no real status bar on lock screen. It's basically a notification panel with header showing signals (and other info) making those options obsolete.

In LP, Default means ON and Always disabled means OFF.

Hard to tell what's causing those fatal signals. I am not experiencing any on stock 5.1.1 with xposed + GB + EX kernel. I'm not using any other mods, whether xposed or "flashable" ones. So I assume it's most likely related to some changes/other mods you flashed on top of your system?

Maybe it's somehow related to differences between LP 5.0 and 5.1. I didn't test this feature on 5.0 so I am not completely sure. Such a glitch is not present on 5.1 (at least on my device).

I'm not sure I understand. When I align phone to point to 0 degrees, arrow is perfectly in line with screen edge. See attachment.

Strange. What device/system are you using?

I'm using this feature on all of my 3 devices running JellyBean, KitKat and Lollipop. Never failed on any of them.

Looks to be something special, either related to your device and system it's running or maybe sensor driver? Hard to provide the answer and even harder to provide a solution. Maybe try posting complete xposed error log.
[Xposed Framework Modules] dioxide95:
XInstaller was the culprit. Everything fine now. Cheers GB!

---

Nexus 5, Android 5.1.1 (Stock LMY48B), ElementalX 4.02, Xposed 3.0(alpha2), Viper4Android Audio, rooted (duh)
[Xposed Framework Modules] mikeoswego:
Aiming specs for satellite dishes and OTA antennas are always based on true north (the north pole.) Magnetic north moves and is currently close to Ellesmere Island in northern Canada. In the old big dish days, polar mounts were used and they were aligned to the pole star or north pole.
[Xposed Framework Modules] GabbyWC:
Here in North America, there's a web site called TV Fool that's used to calculate aiming coordinates for over-the-air antenna reception. If you look at the image I've attached to this post, you'll see that it has both true and magnetic azimuth numbers. In their FAQ page at http://tvfool.com/?option=com_content&task=view&id=57, they state the following:

Azimuth

Azimuth direction for the transmitter (0=North), relative to true north.* The numbers have been color coded according to the transmitter direction for easier identification of channel clusters.* Transmitters coming from approximately the same direction will have similar colors, matching the colors in the outer ring of the radar plot.

Magnetic north readings are also provided for easy compass pointing. *When using a compass for orientation, the "North" end of the needle should point to the red colored "N" on the radar plot.* You can use the magnetic north azimuth values (in parentheses) to aim your antenna via compass.
[Xposed Framework Modules] GabbyWC:
So I would use the true north number to aim with a compass on a smartphone and the magnetic north number with an actual compass? If you look at my reply just before this one, the FAQ from TV Fool suggests using the magnetic north number with a compass but I suppose that doesn't apply to smartphones like the Nexus 5?
[Xposed Framework Modules] mikeoswego:
This has gotten pretty far off topic.. All compasses, electronic in a cell phone or not, point to magnetic north. Some compass apps have an option to display true north based on your location and the known deviation from magnetic north. I would take a normal compass and see how it compares to what your phone displays and then you will know.

Here is an article on this topic: Magnetic North and True North
[Xposed Framework Modules] GabbyWC:
Thanks for the clarification, mikeoswego. I didn't mean to go off-topic but I appreciate your informative answers.

C3C076, I have a couple of quick questions for you. Is GravityBox compatible with the Google Nexus Player running the stock Android ROM? The Nexus Player is an x86-based Android TV device which you've probably heard of and there are more technical details about it at http://kodi.wiki/view/Google_Nexus_Player. Ever since the Android 5.1 update for this device, Google strangely decided to remove the three dots / hamburger menu option from installed apps. This isn't such a big deal if the app is updated to work around that but most apps are not fully accessible with this OS-imposed menu limitation. Do you think GravityBox could somehow restore that functionality on Android TV devices running Android 5.1? Now that rovo89 and romracer have released x86 versions of Xposed, I have the framework installed on my Nexus Player. I'm just hoping that somebody who's skilled with modules can re-enable the full three dots / hamburger menu functionality on Android TV that was there in v5.0.
[Xposed Framework Modules] cashinoda:
Tested on both MOAR Rom and Xtrestolite running 5.0 SM G900P
[Xposed Framework Modules] C3C076:
I don't have experience with Android TV and thus don't know to what extent it's different from normal Android. GB has an option to force overflow menu button that's there since KitKat but not sure whether it works or still makes sense on lp.
[Xposed Framework Modules] GabbyWC:
Thanks for the suggestion, C3C076. I just installed GravityBox on my Nexus Player, rebooted to enable the module, enabled the "force overflow menu button" option in miscellaneous tweaks and restarted again. This option does not seem to work on Android TV, unfortunately, but maybe that's something which is just the result of it not having been fully tested on Android 5.0+. If you could eventually get this feature working on the current Android version, it would be a huge benefit for Android TV owners if it also works on their devices.
[Xposed Framework Modules] tonyp:
If it was there and got removed you might want to look through the sources to find the commit where it's been removed exactly, then it would be a lot easier to fix that with Xposed.
[Xposed Framework Modules] DSA:
you are reporting bugs on an unsupported rom...
[Xposed Framework Modules] ARAVIND_PAVAN:
sir I'm just requesting to look into it and if it doesn't work at all then I wouldn't have talked anything it's working but a slight bug that's why I've reported if it's really unsupported rom and if OP tells that I can't help then I'll leave it

sorry if I caused any inconvenience

------->>SENT FROM MY PIECE OF GLOWING

----------->>GLASS MADE BY MICROMAX

-------->>PROUD KUNALKENE1797 FOLLOWER

------------------>>PAC ROM USER

----------------->>BLACK BOX USER

---->>A FLASHAHOLIC OF ROMS AND KERNELS

---->>HIT THANKS IF I HELPED OR REPLIED [emoji14]
[Xposed Framework Modules] kingvortex:
If you read the first post, it already says that no adjustments will be made to make GravityBox work with any custom rom. Please understand its absolutely impossible to make every feature work with every custom rom.
[Xposed Framework Modules] ARAVIND_PAVAN:
ok sir I got it now and sorry for the inconvenience and I'll delete post"s and I'll Kei the log file if OP can use it

------->>SENT FROM MY PIECE OF GLOWING

----------->>GLASS MADE BY MICROMAX

-------->>PROUD KUNALKENE1797 FOLLOWER

------------------>>PAC ROM USER

----------------->>BLACK BOX USER

---->>A FLASHAHOLIC OF ROMS AND KERNELS

---->>HIT THANKS IF I HELPED OR REPLIED [emoji14]
[Xposed Framework Modules] crackers8199:
Random feature request: would it be possible to put airplane mode toggle in the power menu?
[Xposed Framework Modules] dioxide95:
Use APM+ for all customizations to your power menu. Use GB for everything else! :)

---

Nexus 5, Android 5.1.1 (Stock LMY48B), ElementalX 4.02, Xposed 3.0(alpha2), Viper4Android Audio, rooted (duh)
[Xposed Framework Modules] crackers8199:
I use GB for the reboot in the power menu, nicer to have one module to do everything...
[Xposed Framework Modules] dioxide95:
Alright. Each to their own.

---

Nexus 5, Android 5.1.1 (Stock LMY48B), ElementalX 4.02, Xposed 3.0(alpha2), Viper4Android Audio, rooted (duh)
[Xposed Framework Modules] C3C076:
New version announcement

Version 5.1.4 available

Changelog 5.1.4 - 05/07/2015

- Signal cluster tweaks improvements for Moto devices running LP 5.1 (thanks to romracer)

--- enabled usage of the H+ icon

--- fixed data activity indicators

--- fixed hiding exclamation marks

- Navbar: changed cursor control icons (thanks to creeve4)

- Cellular tile: added option for Dual mode

--- allows similar behavior as WiFi and Bluetooth tile

- Fixed QS panel expanding unexpectedly on screen-on when peek disabled

- Launcher tweaks: adjusted for compatibility with Google App 4.8.10

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

- Updated French translations (thanks to ch-vox)

- Updated Russian translations (thanks to gaich)

- Updated Polish translations (thanks to xtrem007)

Complete commit history for 5.1.3->5.1.4

Note

It's summer holiday which means less work, more time with my family and desire to take a break from Android development for some time. I will be following the forum and try to solve major issues in case any come up.

Have a great summer time!
[Xposed Framework Modules] Ja_som:
Thank you...

Enjoy beautiful summer which we have now in Slovakia, today is hot as hell :)
[Xposed Framework Modules] Blade2014:
For your dedicated work, you Sir deserve a very looooooong holiday... But once the holidays are over kindly come back soon. We are waiting for your return...:p:)
[Xposed Framework Modules] rogers11:
Shouldn't the behaviour of the cellular tile not be exchanged when normalised (long press for settings )?
[Xposed Framework Modules] 089man:
Since update to new version, recent will open every any time. Also will open a pop-up with question what launcher I will used. I say every time nova launcher version but any time later the window with pop-up what launcher I will used comes again.

What can I do? I don't used stock launcher, used nova..

Also that recent window is open again and again.....

Used DU AOSP 5.1.1 ROM with pay version gravity box.

I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
[Xposed Framework Modules] C3C076:
No. Long press is for turning mobile data on/off.
[Xposed Framework Modules] C3C076:
This doesn't seem to be GB related. There weren't any changes that could cause such anomalies.

Maybe your system ui is crashing? May happen if running GB on a custom rom with qs management enabled in GB.
[Xposed Framework Modules] rogers11:
OK, but the behaviour of Wifi and Bluetooth is different. Just a little bit confusing. :)
[Xposed Framework Modules] 089man:
Since update to new version this comes every time. Not with old version...?

I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
[Xposed Framework Modules] sansnil:
My two cents is that it would be nice to have the Wi-Fi, the data, and the Bluetooth tiles have the same behavior, but lower priority I suppose versus some other items.
[Xposed Framework Modules] C3C076:
Xposed log and logcat are required for me to be able to tell more...
[Xposed Framework Modules] C3C076:
Let me explain current behavior.

Previously we had cellular tile which:

- Opens detail screen on press

- Toggles mobile data on long-press.

Making it dual basically means that long-press action becomes press action and press action becomes label press action. Thus we have mobile data on/off on press, open detail on label press.

What could be additionally done would be to attach new long-press action which would e.g. open mobile settings.

Currently, there's no long-press action in dual mode so when tile is long-pressed it falls back to single-press which is to toggle mobile data.
[Xposed Framework Modules] 089man:
Have found the issue or bug.

In new version I set visible search bar in recent from standard to last option.

Than my reportet issue is available.

Now I set to standard and all works fine...

I9100 Tapatalk, DU AOSP 5.1.1 Lollipop
[Xposed Framework Modules] sansnil:
Ah, got it, that makes sense. Sometimes it trips me up because single press for Wi-Fi and Bluetooth toggles it on/off but I have to remember to long press the cellular tile to do that. I think adding a long press action to the cellular tile to open mobile settings would be perfect.
[Xposed Framework Modules] RusherDude:
Awesome feature, even if it doesn't look big, data actually was kinda broken in the quck settings. :good:

Review:

One bug: H+ never appears even after reboot :(, stays on H always. It should change to H+ when there's net activity right?

Just a small suggestion: the wifi panel is awesmoe with that accent color line while its scanning, could the bluetooth have the same while it is scanning for bt devices?? I don't know if this would be hard to implement but it would look amazing and over all consistent! (I don't know if this could also be implemente on the data one after turning it on until it got signal, would be awesome too haha.

Talking about the wifi panel, could you make it so the wifi panel into the QP isn't much bigger than the BT and Data panels? It looks OK in stock but with GB if you have a small QS panel it looks damn bad being that big.

About the "long-press" action, it would be AWESOME if this could be implemented:

a) When the dual tiles are normalized, long press would open the normal "label click" panel. This is so much needed right now :(

b) When dual tiles are normal, could you add the option to long press them (both the icon and label) to automatically open the "more options" option inside the sub panel, this means the proper settings section! I mean with

And on a roll, if you could add "long press" for every tile that has some settings section (examples: location. wifi hotspot, the screen options ones, sync, etc) would be cool also :P.

Thanks for the really hard work!
[Xposed Framework Modules] JaviLerma:
Hi [MENTION=5008415]C3C076[/MENTION], I have Moto E 2015 XT1527, and Gravity says isn't device XT, and don't work signals tweaks. Thanks
[Xposed Framework Modules] L.F.B.:
Wow, now my navbar is perfect! Thanks master CECO! :victory::good:
[Xposed Framework Modules] salimtn:
good for you

not yet for me :(
[Xposed Framework Modules] Ok_Kaleidoscope5109:
So Default = On = replace Heads Up with Ticker? Sorry I'm not completely understanding there.

Also I was using CM for the past week, so I doubt this feature is working properly because CM now has incorporated their own Heads Up mechanism. My AOSP Nexus 5 is currently with my parents, so I can't test at the moment.
[Xposed Framework Modules] C3C076:
GB is not able to identify your device as Motorola. I adjusted logic for your specific case so please test APK in attachment.

Signal cluster tweaks should work provided your device runs the same system like other Moto devices do.
[Xposed Framework Modules] JaviLerma:
Works!! Thanks very much
[Xposed Framework Modules] vanessaem:
Hello everyone,

Thread cleaned...

I'm not C3C076 as you all know but I just came here to moderate. Here's what's in the OP:

Now lets hope things are finally clear about this.

This is a general message to all. It's not always necessary for the Developer/owner of the thread to answer you directly all of the time. In addition, they will not always be available. Repeatedly posting about the same issue that has already been covered in OP is not helpful to anyone. This is a support thread where everyone can provide support for one another. Other people on the thread are more than capable of respectfully answering anyone's questions on here.

My next point, if someone asks a question and you don't want to help because you feel that a topic has already been covered, please don't respond and just ignore the post. It's that simple. Arguing with people solves absolutely nothing. Please respect each other and keep things civilized.

Regards...
[Xposed Framework Modules] C3C076:
Thanks for very detailed report. If only all users having issues would take time to do so :)

Not sure what other variables may affect behavior. This is something that requires me to go through the Android source to analyze and find out where weak spots could be. I'll try as soon as I can. BTW, is that notification ongoing or clearable? You said it worked 100% previously. Any exact settings you changed since then for that app or if it started after updating app to some newer version?

In GB, nothing changed regarding that feature since introduced which is weird enough.
[Xposed Framework Modules] byrong:
That particular notification is ongoing, but the behavior seems just as unpredictable for clearable notifications.

For example: I just ran a routine from Tasker that posts a clearable notification at the end. After turning off the screen and turning it back on, suddenly the ongoing notification was visible as well as the clearable one. Unfortunately, even this is inconsistent. I then rebooted the phone and the ongoing notification had its contents hidden once more. This time I ran literally the exact same task. After cycling the screen, however, instead of both notifications being visible like last time, now both had their contents hidden.

This is actually why I delayed so long in reporting this to begin with. It seemed to start very rarely at first whereas now it's the rule more than the exception (the contents being hidden, I mean). It's extremely frustrating to try to nail down because I can repeat the exact same steps and get different results.

I'm sorry I can't provide better detail on exactly which variables have changed since this feature used to consistently work. I definitely haven't changed any settings in Tasker, but it has certainly been updated. I'm currently on Android 5.1 and I'm 99% sure that this feature worked fine when I was on Android 5.0, but I can't definitively state that the upgrade from 5.0>5.1 is when the trouble started.

I realize what I'm describing is a nightmare to troubleshoot (i.e. the same exact steps can produce different results and there are a lot of variables I cannot eliminate). I appreciate any time you find to put into it in the future, but I completely understand if you can't get far with it. Since I'm the only one reporting it I have to assume that either the issue is not very widespread or not that many people are using the feature in the same way I am.

Thanks again.
[Xposed Framework Modules] electrolt:
Thanks for great work, awesome module, but, how to stop screen recording? And where I can find recorded video?
[Xposed Framework Modules] RusherDude:
Hey [MENTION=5008415]C3C076[/MENTION] , in the new version I found some things that previously worked broken :(

No errors on the xposed logs :(

For example, the Battery quick settings tile: It doesn't matter if you got the option to show or not the percentage, it is not shown. Also when trying to toggle the battery save mode, both with touching or holding the battery icon, the phone vibrates but nothing happens, no battery save mode, no notification, the icon doesn't turn orange (with the option enabled, like it did before), etc. The "temperature unit" and "swap actions" options work, but the other 2 explained don't. I remember testing those in a prior version and they worked good, I didn't update xposed to the last version, can this be a problem?

Thanks a lot for the hard work!
[Xposed Framework Modules] agentsmith988:
I've got an issue that I've been trying to figure out. I've got a Canadian Rogers Moto X XT1058 and cannot for the life of me figure out why I can't swap to the H+ icon from 3G. From the looks of it, I'm guessing that Rogers has modified their "vanilla" version of Android to use larger signal status icons (see screenshot with accompanying log) and it's causing the problem. Any thoughts? Or am I stuck with the oversized/3G signal status icons? FWIW, 3G displays regardless of if I'm on HSPA or HSPA+.
[Xposed Framework Modules] C3C076:
Expand screen recording notification to see action buttons.

Weird enough. Nothing changed regarding Battery tile since its new features have been introduced. I doubt it's related to xposed framework version. Might be some local temporary power manager issues. Did you try to reboot to see if the issue goes away?

Hard to tell as we don't have a clue what provider specific changes Rogers did to standard Moto system.

I recommend posting in the comment section of this commit.

https://github.com/GravityBox/GravityBox/commit/3848bd01b3019028676e24d884ec2ab587a1f799

Provide full xposed log as a text, not as a screenshot.
[MENTION=2476451]romracer[/MENTION] knows more about Moto running LP 5.1 since he owns one so he might be able to comment or help when he has time.

Regarding error coming from GB module, I checked the code and error is handled OK so it shouldn't cause SystemUI crash.

I guess SystemUI crash is most likely caused by unhandled exception in Lollistat module. Test with that module disabled to see if you get different results.