yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] ffejy462:
I am. LG uses their own lock screen rather than the AOSP lock screen. This is why none of the lock screen tweaks work. Lg's jellybean roms still had the code for aosp lock screen, but lg removed all traces of aosp lock screen in their kit kat roms. Fyi, nearly everything in gravitybox works with the g2 except for lockscreen and recents. If you haven't already, I'd highly recommend g2 xposed by black Dino and g2 tweaks box by p toti. G2 xposed isn't being developed any longer, but most of the features work (development stopped right after kit kat was released for the g2). G2 tweaks box has a few really nice features from the g3 and the developer routinely recommends gravitybox.

G2 tweaks box :

http://xdaforums.com/showthread.php?t=2549923

G2 xposed :

https://play.google.com/store/apps/details?id=com.tinyroar.xposedlgg2
[Xposed Framework Modules] C3C076:
Greetings to all from Egypt. Just to let you know I'm still alive and will be able to catch up with GB related activities hopefully starting next week. See you soon.
[Xposed Framework Modules] davelee1054:
Yes thank you for being of absoluely no help whatsoever. Anyway I have fixed it on my own thank you.
[Xposed Framework Modules] frikakwa:
What you had to do without asking first! Your rom is not supported... you have to do it yourself! No need to be arrogant!
[Xposed Framework Modules] nsxla:
I have the same issue. Anyone have an answer to this?
[Xposed Framework Modules] Romiui:
[MENTION=5008415]C3C076[/MENTION]

GravityBox Now Not Support 4.4.4 KK .. =) ..

Any Idea Or Any Help With That ? ..

Waiting New Update ! // ...
[Xposed Framework Modules] trjlive:
GravityBox works 100% perfectly with Android 4.4.4 KitKat... on the devices it was designed to be used with.

So if you're having problems with it, I would recommend you post some more information about your problem if you want help. Also, make sure you've read the OP and are using GravityBox on a supported device.

Device, ROM, logs, errors, even just a screenshot would help.
[Xposed Framework Modules] swat4samp:
I'm on stock nexus 5. For me, long press recents key action do not work at all. It worked for back key which i set it to kill foreground app. How to resolve it?
[Xposed Framework Modules] Romiui:
thanks for fast response !

any way : i was using the gravitybox on my moto g with stock KK 4.4.2

it was working perfectly !

today i receive new update to my Moto G with KK 4.4.4 , but after that the gravity box give's me message " gravitybox system framework not responding, existing , "

Thats all !..

if any solution ! please Help me out !
[Xposed Framework Modules] kingvortex:
Well, this part of trjlive's post covers your situation.

Your device isn't supported.

Having said that, C3C076 has said before that he will look at errors that mean that GravityBox crashes, so you should provide the Xposed log and a logcat if you want any assistance.

Edit - It appears that this is a known error. You should try what trjlive suggests below.
[Xposed Framework Modules] trjlive:
Well, for one, GravityBox was simply not designed for your device, so compatibility is not guaranteed, and in fact there are many well-known issues with using GB on devices it's not intended for. But then there are also many people who use GB on their unsupported devices with relatively few issues. It probably comes down to specific devices, and what other mods you have installed, as well as what parts of GB you actually use.

Just so you know, "stock Moto" is as far away from stock Android as is Samsung's TouchWiz or Sony's Xperia. Motorola just made a skin that simulates stock Android, but the underlying core code of a Moto device is very much custom. This means that you will have problems using a mod that was designed for pure, stock Android, as GravityBox is. GravityBox only works 100% on devices with unmodified, pure AOSP, which is at present time, essentially the Nexus and GPE line of devices.

In the future, perhaps more devices will come with pure Android. But in the meantime, when using GB with these heavily-customized devices, such as your Moto G, you'll just have to work around any compatibility issues. Most of the issues that come up have to do with the status bar and nav bar mods. These are two of the main areas that Moto, along with other OEMs, make major changes to, which in turn breaks GB's ability to apply its modifications.

However, with all that said, the specific error you're getting, about the "system framework not responding", is usually caused by the GravityBox module not being activated properly in Xposed. Installing an OS update would certainly break Xposed, and you need to re-install Xposed into your system, as well as re-install GravityBox.

Look at this step-by-step post I wrote a while back, it's for removing and reinstalling Xposed and GravityBox. You don't need to do the first few steps, but start with step 5, and follow each step exactly. You must reboot at all the correct times,

you can't skip reboots

, and you must ensure you properly activate Xposed and reboot,

BEFORE

you try to install GravityBox and activate it.

http://xdaforums.com/showpost.php?p=53488211&postcount=8326

With a correctly-installed Xposed, you should be able to install GravityBox and use some of the features, albeit unsupported, and you understand that some parts of GB simply won't work with your device. But you should be able to use a good 50% of the features pretty well, I would say.

Update: Also, if you installed the 4.4.4 updated as an OTA official update from Moto, you may have lost root as well. In that case, you'll need to re-root your device before installing Xposed again. Remember, if you're going to use a modded device, you should always reject any OTA and manually install an OS update after you've taken the steps to maintain your root and other mods. OTAs can cause serious problems for rooted/modded devices.
[Xposed Framework Modules] Romiui:
Thanks ! .. Problem Solved ! .. =)​
[Xposed Framework Modules] m0han:
this statement would look nice in the op.

[MENTION=4528127]Romiui[/MENTION], you could consider converting to Moto G "Google Play Edition".......

http://xdaforums.com/showthread.php?t=2635706.
[Xposed Framework Modules] Conte Mascetti:
Can you add please aospa lockscreen notifications?

From GNexus
[Xposed Framework Modules] trjlive:
Feature Requests

Just a friendly reminder (or tip for newcomers who've missed this in past posts), there is a particular place that GravityBox 'Feature Requests' need to go, instead of getting lost in the midst of this thread. GravityBox uses the XDA 'Dev-DB' project format, which includes a 'Feature Requests' tab where you can submit requests, monitor the status of requests, and the developer can keep track of features under development.

There are often many feature request posts that are duplicates of each other, where a user posts the same request as another user did a day earlier, and this just clogs up the thread. Trying to keep track of feature requests in the main thread can be tedious and difficult to follow from a development perspective, which frustrates both the users and developer. So, by using the Feature Requests section, you can see if your particular request has already been submitted by another user, and simply add your input without duplicating it again.

I'm not trying to discourage any users from posting useful feature requests, in fact quite the opposite. I'm trying to help you make sure your feature request is accurately considered, and this also allows you to know the status, whether the request is accepted, in development, denied, postponed, etc. It also allows you to have more focused, on-topic discussion with other users who are also encouraging said feature, and communicate your thoughts about the feature directly to the developer.

Refer to the screenshot below, which illustrates where the 'Feature Requests' tab is for this project. Unfortunately, it's only accessible from the web interface, so if you're using a mobile app, you'll need to use a web browser app to access the Feature Requests section.
[Xposed Framework Modules] swat4samp:
Anyone?
[Xposed Framework Modules] kingvortex:
1. Wait longer than 3 hours before bumping the thread to ask your question again. Forum rules.

2. Provide more details than "it doesn't work" and logs from the time the problem occurred.
[Xposed Framework Modules] Techployee:
Hi,

I'm unable to change the battery to text or even colour, as well as change clock settings.. mainly anything to with the notification bar though I can change it's background colour.

I'm running MOTO G - KK4.4.4 with Nova

Any suggestions? Thanks
[Xposed Framework Modules] swat4samp:
I'm really sorry for that. And my problem is solved. I flashed some dalvik optimization files and rebooted and now it started working all of a sudden.
[Xposed Framework Modules] kingvortex:
Yes, I suggest you read the first post of the thread, paying close attention to any sections regarding compatibility.

Your device isn't supported, therefore some features will not work.
[Xposed Framework Modules] Techployee:
Ok thanks for that.
[Xposed Framework Modules] worktorest:
Is it possible for the charging led to work or is it still down?
[Xposed Framework Modules] trjlive:
Charging LED requires kernel support. It depends on your device. Nexus devices do not support charging LED. However, I know the HTC One (GPE) does support charging LED by default. So this isn't a GravityBox issue, it's just an issue of what features your device supports. What device are you using?
[Xposed Framework Modules] Miqueas111:
Hi, I used that app and all was perfect. Very easy. GravityBox works good. All options except the responsiveness of Pie controls. Sometimes good. Sometimes not. It's the same.

Only posting this since the user asked me.

Results: it's working the same that worked before converting to Google Play Edition. Nothing change.

People seems to be very sensitive I'm going to say I'm not complaining about this issue. I'm not asking anything. I'm just reporting.
[Xposed Framework Modules] trjlive:
Hey thanks for coming back and posting an update. I appreciate the information of how it worked for you.

So the Pie controls are still giving you trouble? Maybe you could do a logcat while bringing up the pie controls a few times, I could take a look and see if there's anything odd going on. They should be nice and smooth, especially when using the GPE ROM.

I'd really like for you to have the best experience possible, especially since you've gone to the effort to convert your device to GPE, which is 100% supported.

If you can get a logcat, attach it or upload it and post a link, and let me know and I'll take a look.

---
[Xposed Framework Modules] DavidTausen:
I'm using an icon set but the original icons still remain on the unlock ring targets.. is there a way i could have the alternative icons in the unlock ring targets? ...i'm using Flatro, in case that matters.

thanks for this AMAZING module, can't imagine my phone without it now that i've had it!
[Xposed Framework Modules] ffejy462:
Icons set by launchers are not implemented beyond the launcher, so typically apps added to lockscreen targets, navigation ring targets, etc will show the stock icon. You can use Unicon xposed module to apply icons system wide, however if your icon pack is missing an icon or two, then the stock icon will remain.

https://play.google.com/store/apps/details?id=sg.ruqqq.IconThemer
[Xposed Framework Modules] worktorest:
I'm using the samsung galaxy S4 gt-i9505 and on a google play edition rom running 4.4.3.
[Xposed Framework Modules] Reechings:
I love the option to use jellybean alarm and vibrate icons in the status bar but is there any way to make them the same brightness as the rest of the icons? I find they are really hard to make out on the translucent status bar. Thanks for all your hard work!

Tapped It!
[Xposed Framework Modules] DavidTausen:
oh, thanks! bought & works perfectly..
[Xposed Framework Modules] trjlive:
I don't know about that device, but I would suggest you look at whatever kernel the ROM is using and see if it supports charging LED. If the kernel and device supports it, should work.
[Xposed Framework Modules] C3C076:
Yes, could be related to changes to CC tile but not sure why it behaves indeterminately. Just providing more info what changes I made.

Standard tile behavior is that tile registers listener for remote displays as soon as quick settings panel becomes visible (e.g. user is expanding status bar) and gets unregistered when panel is collapsing. However, this default implementation caused panel hick-ups during expansion so I changed behavior to keep listener registered even if panel is collapsed. Most likely, in combination with some other conditions (like bug in remote display API, or "special" remote display hardware in your area) could trigger undesired behavior you described resulting in a wakelock and draining battery. Potential solution would be to make further adjustments to my logic that would make sure to unregister remote display listener when panel is FULLY collapsed and register it back when FULLY expanded (to avoid hick-ups). Not sure how feasible it would be until I take a look at the code, though.

Hmm, this is new to me. This could only happen when device is asleep. But this is not the case when device is plugged to AC/USB - as far as I know device is kept awake when plugged. So it doesn't make sense to me. Maybe there's something changed about kernel level power management that could be part of the latest KK firmware? Hard to tell. I'll try to reproduce myself, but if its due to device sleeping when plugged there is really nothing I can do about, I'm afraid.

Check this post: http://xdaforums.com/showpost.php?p=53512888&postcount=8356

This could also be related to your screen hardware/driver. I have seen previously issues with display not being sensitive enough on the edges.

Try increasing Trigger size. Also be aware that if "Centered trigger" option is set, pie activates only when swipe happens near the center of the screen edge.

-----------------------

Some info on MTK platform support will follow soon.
[Xposed Framework Modules] C3C076:
GB KK and MTK platform

Some info regarding MTK platform.

Since many new MTK devices with KK started to appear lately I think it's time to reevaluate GB's support for this platform and to think about what could potentially be done about it.

As many of you probably know, GB project was started to provide customization to the closed source MTK platform which had zero opportunity to have custom ROMs built from the source code.

The core extension to AOSP has been provided by MediaTek mainly to add support for dual sim board.

This extension was used unmodified by almost every smaller device manufacturer which resulted in many different devices being released by many different manufacturers but running almost exactly the same ROM which helped GB to cover all of them in one turn.

Then there was a second group of manufacturers - the bigger ones which went even further and provided another branding on top of MediaTek core (e.g. Lenovo) which of course had impact on GB compatibility (and thus are not officially fully supported by GB).

Now, while tinkering with the idea to add better support for MTK platform it is important to analyse if the situation is the same as it was for JellyBean such as if there's a group of devices made by smaller manufacturers which are AOSPish, having the same ROM across different device brands. If this is true, it would maybe be worth it to cover this group. To make it happen, I will need a "reference" device falling into this group. No problem of buying it myself using donation funds I received. I just need to have the "proper" one.

If the above is not true (in case even smaller manufacturers make their own changes to the system more extensively than what we've seen on JellyBean) so the group of devices running "generic MTK ROM" cannot be clearly distinguished, then it doesn't make sense at all since it's not

possible to make GB compatible with every MTK device running different ROM out there.

So to sum it up, if there's anybody who has more info on current MTK KitKat devices and their systems ( maybe [MENTION=4620757]m0han[/MENTION] ? ) feel free to provide it or even suggest a "reference" device as a representative of a broader group of different devices sharing the same ROM.

And finally, if decision to add better MTK support is made, it will be quite a large task that might take weeks.

Mainly due to the closed source platform which makes reverse engineering too complicated and time consuming.

This means it won't be possible to bring in new features into GB during this period of time. Instead, my idea would be to effectively use time window before xposed is ART compatible and before official L is released for trying to add MTK support.
[Xposed Framework Modules] worktorest:
[MENTION=752027]csc[/MENTION]076 is that for nexus 5 only, because I'm on a Galaxy S4.
[Xposed Framework Modules] ahow628:
Hey [MENTION=5008415]C3C076[/MENTION], welcome back.

While you were gone, there was some discussion about the repeated "X doesn't work on *unsupported device*!" Is it possible that at first launch, there would be a pop up that would say something along the lines of "We see you are using X. Some things may not work. See *link* for details." And have a link to the first post. The device could be pulled or checked against the build.prop maybe (don't know if that is possible even).

I don't think people are maliciously wanting support for unsupported devices or too lazy to read the first post. I think many people probably hear about it from their friends and install it without reading. A little warning might give them an idea of what to expect and might reduce thread clutter.

Thoughts?
[Xposed Framework Modules] C3C076:
Yeah, I've been thinking about it already. Problem is there's no 100% way of detecting whether device is/is not supported via build.prop. The only way would be to collect the build.prop info from all nexus/gpe devices to create a "match" list. This still wouldn't cover special cases like devices running custom AOSP ROMs built from source.

I suppose the best would be to display warning dialog with a link to the support thread for all devices at launch, even for those supported with a check box "don't show again".
[Xposed Framework Modules] yojlik:
For what it's worth, 3.2.5 has a battery drain in it somewhere. I'm not using the CC tile but do use modifications to the QSP. On 3.2.5 I lose 2%/hour and on 3.2.4 and prior I lose .3%/hour. (Both under identical conditions- strong wifi, idle, fresh from reboot at full charge.)

I didn't test it further (i.e. looking for wakelocks with diagnostic tools) but reading the thread I found these two posts and chalked it up to the same thing since there were only a few new features on 3.2.5 and I don't use UNC, pie controls, screen recording, or Heads Up.

I know a ME TOO! post doesn't do much to help but when diagnosing my huge battery drain a few months ago on GB (which turned out to be Xposed framework-related, not GB-related) I got a lot of historical and current data about my Nexus 5's idle drain and I'm sure that 3.2.5 has a hole in it somewhere.
[Xposed Framework Modules] m0han:
i knew there'd be light at the end of the tunnel. :good:

please take a look at Xolo Q3000. it is based on mt6589 chipset (quad-core), is dual-sim and now ships with kitkat 4.4.2 os.

mine came with jb 4.2.1, but now runs kitkat 4.4.2. i guess i can urge guys over here and here to test the new gb versions. :fingers-crossed:
[Xposed Framework Modules] trjlive:
Well, just as a comparison, I'm using stock Nexus 5 with GravityBox 3.2.5, stock kernel, and my device uses 1% every 2 hours (so about 0.5% per hour) when it's just laying around or in my pocket. I'm in ideal wifi and strong LTE conditions almost all the time.

This is also with full GPS and bluetooth left on all the time, I don't worry about disabling various radios since it's more of a pain to remember to turn them on/off when I'm using them, and I don't notice any significant drain just leaving everything on.

I have 2 Chromecasts on my wifi at home, and there must be at least a dozen on the wifi at the Google building I work at. I don't experience any freeze-ups or stuttering whatsoever. I don't use pie controls or screen recording, but I am using UNC and heads-up notifications, along with quite a few various other tweaks.

I'm running Xposed 2.6.1, on Android 4.4.4 KTU84P, with GravityBox 3.2.5. So I just wanted to mention, that even with the same device as you, and same versions, my battery life is excellent and I'm not noticing any GB-related drain whatsoever. So I'm not too sure about GB "having a hole in it somewhere" as you mention, that's causing your battery drain.

You said you have battery/wakelock stats? If you're getting drain, it should be pretty easy to tell what app is causing it. I'd be interested in seeing the logs or stats that indicate it is GravityBox draining your battery.
[Xposed Framework Modules] yojlik:
I said I didn't take any stats but I will next time I update if the problem seems to be there. The reason I didn't was back when I was tracking a 15%/hour drain :eek: (something I think anyone would agree is a problem) nothing showed up in battery monitoring apps as causing it, so I assumed the same would be true this time but when the same solution didn't work to resolve it I got a bit concerned. I don't micromanage my radios either, everything's always on.

All I have is anecdotal evidence based on historical performance and A/B testing between 3.2.4 & 3.2.5. I have no Chromecasts and don't use the casting tile at all.

I understand comparing battery usage is a fool's game which is why I didn't comment when it happened and I saw the posts. Once [MENTION=5008415]C3C076[/MENTION] looks into what [MENTION=1003321]PhyerFly[/MENTION] posted about, I'll update and take measurements.
[Xposed Framework Modules] ffejy462:
I never did see anybody else indicate that they had this same issue, but since [MENTION=5008415]C3C076[/MENTION] is back, I thought I'd bring it up again. For now, I just disabled heads up on the tablet so I don't miss a potential important email. The other users on the tablet reported the same thing, but I'm not certain if their emails were dismissed because they have iProducts.
[Xposed Framework Modules] Pkt_Lnt:
While an excellent idea, I am skeptical it will help. In the Xposed Framework, rovo89 did something similar when there was an install error, AND had what to do to fix it in bold red letters. Users would post screenshots of the error asking for help and others had to tell them to just read the bold red letters. :::facepalm:::
[Xposed Framework Modules] mdamaged:
You could have a sign with 4 foot high letters with it, a midget with lit fireworks jumping up and down on a unicorn while shouting it, a line of beautiful naked women with it tattooed in neon ink all over their bodies while beating them with the popup, and you'd still have the same people asking the same thing. Some people just don't care, it's genetics or something, they are the same people who just click "Next" without reading while installing things in windows and end up with 30 toolbars in their browsers and can't figure out why.

...though I'd be ok with the naked woman thing.