yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Pkt_Lnt:
From what you posted, I do not think the changelog entries you mention have anything to do with what you say the issue may be, but we can only make speculative guesses with no evidence. In my mind's eye of what you say, they do not seem connected, but in your mind's eye, they might be. We are not seeing minds eye to minds eye. Maybe we are both incorrect as to the real cause?

Again, not trying to be difficult, but only logs can answer that, so if you have problems, post logs. If you do not have problems, then give credit to leprechauns and fairies and Murphy's and Lubarski's laws. ;)

To get a logcat that the devs can use, use adb on your computer since it can record crashes and boot information that a logcat app cannot record. Here is a tutorial.

http://xdaforums.com/showthread.php?p=28181474#post28181474
[Xposed Framework Modules] spexwood:
I understand that logs are important ;)

At this time, I just wasn't trying to be like, "Help! I have this specific problem! How do I fix it!?"

I was just trying to see if based on my problem's description, if anyone could definitively say that yes, this was a common problem and yes it has been fixed.

Thanks for the alogcat link too. I'll try to use this if the problem occurs again. I could never get ADB working right on my PC though, but it's been a while since I've last tried, so I'll try it again if the need arises.
[Xposed Framework Modules] Sportfreunde:
What are the best GBox tweaks for better battery life (mainly on a wifi only tablet)? I like the ability to clear apps from the recently opened apps menu.
[Xposed Framework Modules] yousirname1:
Where is the lockring torch?
[Xposed Framework Modules] C3C076:
I am completely sure this is not GB related.

GB doesn't touch that part of system at all. The changelog line is about AppPicker which is internal part of GravityBox and doesn't affect any system part. Anyway, it would be interesting to see the logcat if it ever happens again, as already suggested.

In Lockscreen tweaks.

When enabled, torch can be toggled by long-pressing sliding challenge (unlock ring) handle.
[Xposed Framework Modules] trjlive:
GravityBox isn't designed to improve battery life. It is to enable additional functionality or tweak certain existing functionality in stock AOSP devices. The way GravityBox is implemented, it should have no real effect on battery life. Just make sure you read the compatibility section in the OP and understand what devices GB is designed for. The only instances I've ever seen of people claiming GB reduced their battery life were using it on TouchWiz devices, which are most definitely not supported. But on stock AOSP, GPE, or Nexus devices, you shouldn't notice any reduction just because of GravityBox.

Your battery is more likely to be reduced because you'll like using your device more after installing GravityBox. ;)

---------- Post added at 10:47 PM ---------- Previous post was at 10:42 PM ----------

The Galaxy S5, with the exception of the GPE version purchased directly from Google, is absolutely not supported by GravityBox. An OEM stock S5 runs TouchWiz, which has many known, major issues with GravityBox, and the solution is to not use GB with TouchWiz devices. There are other mod apps available that are actually designed for TW. If you do have the GPE version and you're experiencing a problem, then please post logcat of the error so that someone can help you. The OP contains all the details needed on how to report an error in a fashion that's actually useful for troubleshooting.

---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------

Following the back and forth on this conversation, unless I've missed something, I still do not see where you've specified what device and ROM you're using. That's basic information that is needed for any level of troubleshooting. I understand you're not getting the issue anymore after resetting your ROM, but if it does happen again and you post your logs, please include device and ROM information.

---------- Post added at 10:54 PM ---------- Previous post was at 10:50 PM ----------

From the logs posted in the Kaspersky thread, the issue seems to be with KIS 11 and Xposed, and really has nothing to do with GravityBox. Of course, there's no way to use GB without Xposed, so it boils down to if you want to use GravityBox, then remove KIS 11 from your device.
[Xposed Framework Modules] PunchUp:
I asked DooMLoRD and he said it can be done using the ROM. Kernel's not involved. So perhaps it can be done using GB. [MENTION=5008415]C3C076[/MENTION] any thoughts?
[Xposed Framework Modules] Borfas:
I suggest: a program on a phone brand. not all their phones.

so we understand? Well this program who did go. ie a market. I would like to make a donation to this program, but I wonder if it is worth to see my galaxy s5 with bugs from a program that is not for him and really change the system, and of course, loss of warranty.

suggest a program for a phone model.

I wonder how you managed to collect so many fans .... give 800 euro phone .... and you'll see that .... bang a lag or bug of a Program .. what program? xposed is a very useful application, but need to run perfect application for your phone model and not the international program (how does this op) A man tries to put software on millions of phones and all have a small bug problem.

finally this program is exempt s5 yet.

I understand that the phone works perfectly application?

congratulations sir for this app.
[Xposed Framework Modules] Thijssie909:
Hi C3C076, I am on GPE 4.4.3 and with the 3 dot menu disabled the recents menu isn't working anymore. I tried to configure it within GB explicitly when double tapping home it should open recents, but that didn't help.

Strangely enough, when I set up a gesture within XGELS settings (double tap home screen) to open the recents menu, it does work.

Is there a difference between using the home button and gesture kind of stuff? Is there a different command executed? Would be nice to have the recents menu back by just double tapping the home button.

Thanks!
[Xposed Framework Modules] Orphee:
Hello,

Thank you for this great module !

I'm currently using it on my Motorola RAZR HD XT925 and it is working great.

I just have a little graphical bug on quick shortcuts :

WIFI and DATA pictures are truncated.

For WIFI you don't see the picture at all, only the little sync arrow when enable.

For DATA as you can see on the screenshot it is cut on the TOP. I think it is the same for WIFI.

Is there something to change to correct this ?

Thank you !
[Xposed Framework Modules] DSA:
Yep, the ROM you are using or your phone
[Xposed Framework Modules] C3C076:
Typical motorola incompatibility which GB already handles, but not for your device model, yet.

Attach the log file exported from xposed installer so I can add this device to the list.
[Xposed Framework Modules] C3C076:
Post more info about your device and attach xposed log which can be exported from Xposed installer app.

Also make sure, that if your device has software buttons (navigation bar) you have to enable master switch in "Navigation bar tweaks" for key actions to fully work.
[Xposed Framework Modules] joaor10:
Hi, I'm having the same problem in the navbar as some users mentioned already. Nexus 10 with rastakat 4.4.3 ROM... Isn't it an AOSP ROM?

Enviado do meu Nexus S através de Tapatalk
[Xposed Framework Modules] DSA:
Aosp - yes

Stock - no
[Xposed Framework Modules] fbf2201:
It's maybe based on, but it's not pure AOSP.
[Xposed Framework Modules] Thijssie909:
I am on the HTC One. Attached the logs etc, but can't see any real GB errors...
[Xposed Framework Modules] Orphee:
Here it is,

For your information, I'm currently using soak test Motorola 4.4.2 ROM, the official OTA is not yet released.

Thank you :)
[Xposed Framework Modules] ffejy462:
You won't see any noticeable gains in a wifi tablet. However, a phone (I guess a tablet with a data plan also) has the potential to see significant battery savings using smart radio and to a small degree, unc. I enable smart radio when I know I'll be in a poor reception area for a while. Battery drain, for me, in a poor reception area, is roughly 4-5%/hr vs 1% normally. With smart radio, for me, in a poor reception area, is 1-3%/hr.
[Xposed Framework Modules] spexwood:
I'm running stock 4.4.2 on an LG Optimus G Pro.

The ROM is rooted of course with really only Gravity Box, App Settings, and YouTube AdAway installed. The only other mods done were disabling the Home button from waking the phone screen (done via a simple keylayout edit) and a custom bootanimation. However, I did have SlideAside ported from teh LG G Flex at the time of my last crash session. I don't have it installed right now though, nor at the time of the crash before last.

So other than these things mentioned, I am running pure stock.

Oh wait, I also System Tuner installed. I have it set to put the CPU into Powersave governor and disable cores 1,2,3 whenin deep sleep.

I also have the following One-Clicks enabled: ROM, Kernel, Storage Access, Reduce device lags

I don't think it's System Tuner causing this though because I've tried uninstalling the app when the crashes occurred and then rebooting, but it did nothing to fix the problem.
[Xposed Framework Modules] DSA:
so, you're not running a compatible rom then...
[Xposed Framework Modules] schallwert:
Whenever I have an app broadcasting media (music, games..), I only get the option to change media, and alarm volume. Otherwise I get all volume controls. Is this intended?

I run a Sony ROM and I know these OEM skins are not supported. Just being curious if it's an incompatibility with the ROM or intended behaviour.

Anyway, does anyone happen to know an alternative for expanded volume controls?
[Xposed Framework Modules] trjlive:
Well, now that explains the problem, your LG Optimus G Pro is

not supported by GravityBox

. Even though it might be "OEM stock" from LG, it's not "stock AOSP Android". LG's stock ROMs are just as much custom as TouchWiz, Sense, Xperia, CyanogenMod, etc. LG has changed enough of the underlying core code that it's considered a custom ROM in the eyes of GravityBox. And without LG devices and source code available, there's very little the developer can do to help.

This is why you were asked several times what device and ROM you were using. If we had known this info sooner, we could have avoided much of the back and forth trying to understand what the real issue was. The OP is very specific about the devices GB supports.

There are only 3 specific categories: pure AOSP, Google Play Edition, and Nexus devices.

These are the only 3 categories of devices that GB supports. If you choose to use GravityBox on a custom ROM, like many other users do, then you also do so at your own risk and with the understanding that things probably won't work fully.

And even providing logs and screenshots won't help, because without access to the source code from LG, it's nearly impossible to debug the GravityBox code. So the problems you were experiencing were very likely due to the fact that the LG stock devices are very much "custom" compared to pure AOSP and GPE/Nexus devices.

Feel free to take the GravityBox source code and work on debugging and tweaking it to work better on your device if you want, the links to the Github are in the OP. That's really as much as you can expect from the developer and this thread.

---------- Post added at 04:16 AM ---------- Previous post was at 04:12 AM ----------

Most likely an issue with your Sony ROM, which GravityBox doesn't support. It's not just a "skin" that's on your device, it is known that Sony, like many of the other big OEMs, make drastic changes to the core code, thus causing incompatibilities with GravityBox, which is expecting the code to be stock AOSP.

Even seemingly simply tweaks can cause major issues when the OEMs make lots of core changes, and without source code available to debug with, there's next to nothing that can be done, besides just not using GravityBox on a unsupported device.

As for an alternative to GravityBox, you'll probably get better responses asking that question in your device's thread, most people on this thread probably won't know much about mods for unsupported devices.
[Xposed Framework Modules] raven6681:
Strip Unicode

Hi,

Any plans for the future for striping unicode option in kitkat?

Regards,

George.
[Xposed Framework Modules] tlf55:
In addition of my suggestion of keeping led active until we don't dismiss the notification as a feature.. There's a bug with Ultimate notification conrtol.. The Override feature doesn't work well.. like with Stock samsung messaging app. :)
[Xposed Framework Modules] fbf2201:
Is there a stock Samsung messaging app with AOSP? I don't think so.
[Xposed Framework Modules] tlf55:
So what ? I don't use this xposed mod to customise visualy my Rom, but only to use torch on lockscreen and for this ultimate notification control feature .. I don't use other feature cause i'm aware that it won't work or wouldn't work correctly :)
[Xposed Framework Modules] fbf2201:
Just because you want a certain feature to work, doesn't mean it will work. You obviously have a not supported rom and Samsung probably deals differently with notifications.
[Xposed Framework Modules] NovaSlim:
Any GB feature could be broken on a Touchwiz ROM(even some that are currently working for you could be broken with the next Touchwiz or GB update), that is why it is not supported. So it is no wonder that the stock Samsung messaging App on yours is not working.
[Xposed Framework Modules] tlf55:
Okay no problem then sorry for this :)

Envoyé de mon SM-G900F en utilisant Tapatalk
[Xposed Framework Modules] OGroteKoning:
I am in a similar boat as you. I love GB and I know very well that it doesn't support TW, but some features I like works well (like remapping keys; small changes to the status bar; removing persistent notification icons). For notifications, I use LightFlow. It would be fantastic if a separate module can be done for the SM-G900F, but without a handset, it is impossible for [MENTION=5008415]C3C076[/MENTION] to build it (and then there are time constraints, life and others). So I use features what I can and those that doesn't work doesn't get used.
[Xposed Framework Modules] C3C076:
really, no GB errors in the logs. I would start with disabling other modules step by step. it's possible there's something conflicting.

As far as I remember we are not dealing with GB not working but random reboots when scrolling lists to which I previously said that I'm sure they are not GB related. But we can only continue speculating until we see the logcat of crash (if it ever happens again?)

What about modules by wanam made specifically for touvhwiz. Did you give them a try?
[Xposed Framework Modules] C3C076:
Any feedback on Apk I provided here?

http://xdaforums.com/showthread.php?p=53421083
[Xposed Framework Modules] OGroteKoning:
So you want me to use an inferior module... Hmmmmmm...

Just kidding

Yes I have, I have that module on my phone [MENTION=5008415]C3C076[/MENTION], but that module is not nearly as advanced as yours (therefor disabled currently). It doesn't have key remapping and it doesn't block ongoing notifications. If it had those, I probably would not have used GB. Also, a very much used feature of your module on my phone is the App launcher. Since using it on my N5, I can't live without it.
[Xposed Framework Modules] tlf55:
Same for me, i have wanam module on my phone too, but GB module is so much more complete that i can't live without it :)

Since i resolved the issue with override vibration with stock messaging app (i just disabled vibration in the app and kept override vibration in GB) the only thing Ultimate notification control is missing is that as i said before : add a feature to keep led working until dismissing the notification :)

Anyway thanks C3C076 for your module, thanks for your hard work ! donated before and wouldn't hesitate to donate more because your work is usefull for everybody in android world :)
[Xposed Framework Modules] PVL_93_RU:
Can confirm - enabling cursor arrow keys for the navbar no longer offsets the default navbar buttons

But having enabled both arrow keys and (in my case) additional navbar button such as Menu key, putting out the keyboard, and then interacting with the status bar or sometimes even with the overflow button still causes the offset and the appearance of both arrow and additional keys close together, but I guess this is not a bug but a feature, right?

Screenies below:
[Xposed Framework Modules] OGroteKoning:
Oh and another very nice feature your module allows [MENTION=5008415]C3C076[/MENTION], is double tap to sleep on any open area on the home screens when used with Nova launcher. Thanks for that too! [emoji3]
[Xposed Framework Modules] C3C076:
Yes, menu behavior is by design as I already mentioned.
[Xposed Framework Modules] C3C076:
I don't remember having such feature in gb :)
[Xposed Framework Modules] PVL_93_RU:
Ah okay. But if I understand the intentional behavior of the menu/custom key close to cursor arrow keys, can the Back/Home/Recents navbar buttons offset be.. um... "fixed" I guess?

Not a request or anything, just a question
[Xposed Framework Modules] OGroteKoning:
Nova launcher has gestures, one of which is double tap. Mapping your module's "go to sleep" to that gesture makes it possible. Your module is the only one (or one of very few modules at least) that has a sleep feature that makes this possible.
[Xposed Framework Modules] C3C076:
Nope without redesigning default AOSP layout of navbar in relation to menu key. This is something I'm not planning to touch.
[Xposed Framework Modules] ffejy462:
Yes! I've been using that action as well for a long time with Nova and gb on every device. Works great!
[Xposed Framework Modules] BakaB:
disable charging LED doesn't seem to work.

Galaxy S4 - 4.4.3 GPE ROM
[Xposed Framework Modules] Orphee:
Hi, I understood how your check works, so I edited my build.prop to set "XT925" until you add "RAZR HD" to the model names.

I don't know why Motorola decided to change the name from XT925 to RAZR HD (it is its commercial name)

It works and the signals are OK :)

Thank you !
[Xposed Framework Modules] spexwood:
First, I was only asked ONCE for my ROM and phone. Not "several times."

Once I was asked, I responded promptly.

I was asked several times for logs though and each time I replied that I'd supply them if the problem occurred again since after the factory reset, the issue would take about a day to start again.

And while my ROM isn't AOSP. nothing explains why I've been able to use Gravity Box flawlessly for about 6 months until recently. I mean, yes not all features cause issues, but there are a lot of smaller tweaks that work great on my phone, such as making the volume rocker change volume up/down depending on how to phone is rotated, the advanced reboot menu, hiding the battery icon, and the torch from lockscreen using Home button. In addition, on the Optimus G Pro's XDA forum, Gravity Box was even recommended on many threads because it worked so well for our device.

My issues began on Kitkat sometime around the 3.1.5 update. So far I've been running 3.1.7 all day today and there have been no issues whatsoever, so the crashing could be fixed or it could be that SlideAside port I had.

If the problem still occurs, I'll still provide a log. As I said, GB has been working without issues on my phone for a long time. If anything, maybe someone could be nice enough to look at the log and help me figure out the cause, whether it's GB or not. I have no idea how to read the logs nor how to reprogram GB (so the source code is useless to me!!!).
[Xposed Framework Modules] C3C076:
Great , thanks for info. At least I know it's exactly the same adjustment that works for other moto's.
[Xposed Framework Modules] mitchst2:
[MENTION=5008415]C3C076[/MENTION]

Just to be upfront I'm running an HTC one m7 on sense 6. I'm fully aware all features won't be compatible and accept that and just use those that I know work.

The issue might simply be that of an incompatibility but on the off chance there's a simple explanation/fix.....

I've enabled navigation ring targets using a zero height navbar. Unfortunately this has disabled double tap home for recents. This may be down to Gravitybox or HTC's swipe up from home implementation or both in combination.

Is there anything I may be missing in settings or anything that you could easily implement?

If not I understand. Thanks for your time.

Edit (additional info)

If I set double tap back to recents in Gravitybox it works. Just not used to this layout.

Sent from my HTC One
[Xposed Framework Modules] trjlive:
Actually, it explains quite well why you're only having problems recently. Because your device and ROM are not supported, when new versions of GravityBox are released, they are not tested in any way against your device and ROM. Therefore, as new features, or fixing bugs on supported devices cause the GB code to change, it's then tested only on supported devices.

If all works perfectly on supported devices, then the update is released. Now if any of those code changes cause problems with unsupported devices, then that's just the way it goes. So it sounds like you've been using GB on an unsupported device for some time without issue, but a recent update has introduced some new problems. That's the unfortunate reality of using an app on a device and ROM it was never even designed for.

And just because GB is recommended on other LG threads doesn't change the fact that it is still not supported. The developer of GB has NEVER recommended this module for other LG devices. The only LG devices to ever be officially supported are the LG Nexus 4 and the LG Nexus 5, and even then, only when running the stock ROM. So those unofficial recommendations for other LG devices really mean absolutely nothing when it comes to compatibility.

Because these problems do not exist for supported devices, this really is a non-issue. You feel attacked because other users are trying to tell you that your problem doesn't belong in this thread. The very definition of "unsupported" means you won't get support for your problems. So coming here and trying to force the issue and get support is what annoys other users who are here trying to help users who actually are using a supported device.

Not really sure what else you expect here. LG has not released any source code for that device/ROM, the developer does not have access to that device/ROM, so trying to change GB to be more compatible is simply not feasible. You chose to use GB at your own risk, and you knew before you even installed it that it was not supported on your device. And if you didn't know all that, well you should have because it's all in the OP before you even get to the download links.

I'm sorry if this sounds harsh, but your posts come across as from someone who didn't bother to read the OP before posting, or if you did read the OP, you feel like it doesn't apply to you and you still deserve support, even though it's very clear in the OP what devices ARE and AREN'T supported, with no exceptions. So you're free to start your own thread and ask for help for your device, but this really has no further place in this thread.

Several posts asking for details about your device/ROM:

http://xdaforums.com/showpost.php?p=53431685&postcount=8216

http://xdaforums.com/showpost.php?p=53431759&postcount=8218

http://xdaforums.com/showpost.php?p=53435464&postcount=8226

You finally responded to the third request for more details.

---------- Post added at 01:02 PM ---------- Previous post was at 12:58 PM ----------

HTC makes drastic changes to the navbar code, so this is bound to cause incompatibilities with GravityBox which expects the code to be stock AOSP.
[Xposed Framework Modules] C3C076:
Thoroughly went through the code once again and found out the menu key misbehavior is really caused

by improper handling when cursor controls are shown and option to always show menu key is on at the same time.

Attached is the APK with some further adjustments to logic. Please, test. Seems to be working OK now on my N5.