yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Triggeh:
What I did:

backup > install xposed.apk > reboot > install xposed framework > reboot >install gravitybox.apk > reboot > enable GB module in xposed > error.

The only thing i did differently was reboot two more times inbetween steps, regardless i tried it again with less reboots (what you said) and it still won't work. I just tried some other modules and they work fine. This seems to be an issue with GB not xposed.

Yeah I did reboot after enabling (well being greeted by the error) I thought that was kind of obvious and forgot to include it wouldn't of posted here without trying to reboot.

I think you missed something, i don't need to reinstall/uninstall GB I can't install it in the first place without getting the error. I already tried installing old versions aswell after doing a complete reinstall of xposed.

My device is in my signature, anyway its a XT1039 Moto G 4G/LTE Stock 4.4.3 Super SU 2.01 Root

I just did a complete wipe of my device and still get the error when trying to enable GB in xposed.
[Xposed Framework Modules] trjlive:
There's your problem, you are trying to install GravityBox on a device it was not designed for. You really should have read through the OP in its entirety, you would have known this already and could have saved yourself all this trouble.

GravityBox is designed for

pure AOSP

- basically this means Nexus and Google Play Edition devices. Your Moto G is

NOT

pure AOSP. No matter how close to stock it looks, it is not pure AOSP. From the OP (a quote I actually wrote a while ago):

The

only

Moto device that is supported by GravityBox is the Moto G Google Play Edition, purchased directly from Google with no carrier branding.

So if you decide to use GravityBox on a device/ROM it wasn't designed for, you do so at your own risk, and without any support. GB is not intended to be used with your device, so the result of trying to install it is completely unpredictable. I would suggest you look for Xposed mods that are actually designed for Moto devices.

Also, if you're so inclined, you're always free to fork the GravityBox source code and tweak it to work with your device. The source links are also in the OP.
[Xposed Framework Modules] Triggeh:
Well i don't have any carrier branding as I purchased it seperate, however the op is a little misleading as it says GB works on close to vanilla 4.4 etc.

sorry for bothering you.
[Xposed Framework Modules] trjlive:
The problem is, your device isn't even close to vanilla AOSP. Again, you have to realize that it doesn't matter what the ROM's skin looks like. It's what the code underneath looks like. Motorola has changed so much of the core AOSP code, just like Samsung or HTC, that GravityBox can't find the certain hooks to do what it needs. Your device is no different than a Samsung device running TouchWiz in this regard.

And because the OEMs (Moto included) obfuscate and close-source their code, there's really no way to troubleshoot these issues. And the dev doesn't even have access to these Moto devices, so he can't even reverse-engineer it. That's why GB only supports pure, unmodifiedAOSP, which essentially means Nexus and GPE devices, or close-to-pure ROMs based on Nexus or GPE devices.

And as I said before, since you do have the device, you're more than welcome to contribute to the project by forking the GB source code and tweaking it to work better with Moto devices, and submitting pull requests.

And yes the OP says it works on close-to-vanilla AOSP (which your device isn't), and it is also very specific about what devices it doesn't support, if you were to read the entire OP. There is actually a paragraph that

specifically addresses Moto devices

and explains this.
[Xposed Framework Modules] ffejy462:
I still think you missed a reboot! Lol.

Backup, Install framework apk, enable framework, reboot, install gravitybox, enable gravitybox, reboot.

Anyway, as already noted, there will be issues since you are (trying to at least) running it on a unsupported device.
[Xposed Framework Modules] trjlive:
Another thing you could look into, is installing a Moto G Google Play Edition ROM onto your device, which will be vanilla AOSP code and GravityBox should work just fine. I have no experience with this, as I've never owned this device, but a quick search on XDA came up with several threads about how to do this, including this thread.

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

Again, I have no idea if this will work with your device, but I wanted to bring your attention to this possibility.
[Xposed Framework Modules] Triggeh:
I didn't i just forgot to mention that i rebooted after getting the error when enabling it. I wouldn't post here if i didn't already try rebooting. I tried reinstalling everything before posting.

But as you said it's probably just my device, I will have to try again when a GPE rom comes.

No GPE roms for the 4g/LTE version yet (XT1039 & XT1045)

I would like to mention that other people with the same device have got GB working without GPE.
[Xposed Framework Modules] C3C076:
Yeah. Glowpad View (ring) control has an array of targets starting with zero index on the right and continuing in counter-clockwise direction. I'm filling them in "for" loop in order as they appear in the settings. It's simply a question of doing a "for" loop in reverse order.

What about attaching an xposed error log that can be exported from within Xposed Installer app? That could maybe be give us some hints. Although it's an unsupported device, module should be able to load not throwing "system framework not responding" error. So it looks like something's special at your end.
[Xposed Framework Modules] trjlive:
That makes perfect sense, thanks for the explanation. I figured it was something like that, they're enumerating from right to left. Anyway, good to know there's a reason for it. :)
[Xposed Framework Modules] jacknicholson:
Until you provide more information (logs), that last statement strongly (albeit not certainly) suggests that there's little anyone here can do, as both the device model and ROM can be ruled out as definite causes for your installation issues (ie. the issue lies squarely with your setup). I think the best advice anyone can suggest at the moment is to ensure that Xposed and GB were installed immediately after a clean install of both your system and data partitions (remembering that a factory reset generally won't undo modifications made to the system), to guarantee that there isn't anything else fouling up the install process. As well, it's often recommended to root using the SuperSU binary before installing Xposed (vs. Koush's Superuser, etc).

That said, I have a feeling you'll say you've already done all this. ;)
[Xposed Framework Modules] Triggeh:
Log: http://puu.sh/a1LZx/101b3c361f.log

Nothing was dumped in the logs when i encounter the error from trying to enable GB module so i assume that log is what you want

Yeah I did wipe those partitions, no luck.

As for other people running it on my device (NO GPE and STOCK): http://xdaforums.com/showthread.php?p=53989827

Was talking to other people with the same model (xt1039) outside of XDA and they had it running on stock aswell.
[Xposed Framework Modules] nachordez:
The daughter of a friend of mine, 7 years old had the following conversation with him:

- Dad, if you find in the street an envelope full of money, what would you do with it?

- I would carry it to the police, of course.

- Yes. But if you REALLY find an envelope full of money, what would you do?

- ........... Well, I'll probably keep it.

XD

from gt-p5110
[Xposed Framework Modules] champofthesun:
I'm not sure if this is a bug (if someone can try to replicate this and confirm it, that will be great). This problem occurs when I have the navigation bar set to "Always on bottom" and while it is in landscape mode, the back button opens up Google Now, instead of going back. :confused: It's the only option (besides enable) I've change under the navigation bar settings.
[Xposed Framework Modules] yochananmarqos:
It works fine for me on my virtual Nexus 7 in Genymotion. What device & ROM are you using?
[Xposed Framework Modules] C3C076:
Looking at the log, I can confirm what I wrote earlier is true. Xposed framework didn't try to load GB module at all.

This is probably a consequence of xposed framework not being installed correctly, or GB module is not activated withn "Modules" section in the xposed installer app.

When xpose framework works OK, you should see something like this in the log:

Loading modules from /data/app/com.ceco.kitkat.gravitybox-4.apk
Loading class com.ceco.kitkat.gravitybox.GravityBox
[Xposed Framework Modules] C3C076:
A good one :D

In situations like that one I always try to imagine myself being on the opposite side of the story.

That will make you take action immediately.
[Xposed Framework Modules] nachordez:
I can guess... Wouldn't you be like that, wouldn't you work so hard to do this marvellous piece of software for us all!

from Nexus 4
[Xposed Framework Modules] iSadic:
Thank you but I think you've misunderstood my request. I want to say that it would be awesome to open the heads up notification directly in a floating window (like Floatifications do). But now I'll use the request section. Thanks again and sorry for the wrong section.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Xposed Framework Modules] BEDBOI2:
The first time I went into "navigation keys actions" an alert was shown, I dismissed it thinking it would shown again, but that's not the case, so how can I see it again, or know what it said?
[Xposed Framework Modules] champofthesun:
Nexus 5 stock/rooted
[Xposed Framework Modules] PeterImmel:
I have a problem:

Under

Ultimate notification control -> Default settings -> Active Screen mode

I activated Heads up.

Now, if i get a notification, my screen turns on and the heads up-popup is only shown for a blink.

Under

Statusbar tweaks -> Notification heads up -> Timeout

I put 4s.

Is this a bug or am I doing something wrong?

(Moto G // pa_falcon-4.4-20140706B_LINARO // 3.4.96-XPerience-07CM)
[Xposed Framework Modules] aavvaallooss:
Yes. You have a problem called Moto G
[Xposed Framework Modules] C3C076:
It says that for actions to completely work for navigation bar keys it is also necessary to enable master switch in Navigation bar tweaks section.

It's a known issue that has already been fixed but not officially released.

I'll be releasing another small update in couple of days before I'm gone for a vacation.

I'll just need to wait for other potential bugs to pop up.

Edit: here's the post containing fixed APK so feel free to try it to find out whether it fixes it also on your (not fully supported) ROM.

http://xdaforums.com/showpost.php?p=53970352&postcount=9221
[Xposed Framework Modules] shmotog:
Ok please then tell me how do I set lockscreen timeout setting on nexus 5? How did you set it?

Help [MENTION=5362940]trjlive[/MENTION] [MENTION=5008415]C3C076[/MENTION] anyone
[Xposed Framework Modules] C3C076:
Screen off timeout for lock screen? I don't think there's such option in Android but prove me wrong :)
[Xposed Framework Modules] shmotog:
well i think so too but apparently [MENTION=5362940]trjlive[/MENTION] seems to think its apparently possible on nexus 5 and since i have a moto g it cant be done but can you do it through gravitybox [MENTION=5008415]C3C076[/MENTION] i just want a way to set that annoying 3 second timeout on the lockscreen that moto g has. :(
[Xposed Framework Modules] LifeAsADroid:
If you want this functionality right now install the standalone Heads Up Notifications module and the XHalo Floating Window module. Those two work together to do exactly what you want it to do.

---------- Post added at 10:02 AM ---------- Previous post was at 09:59 AM ----------

If other people with your exact device and ROM have GB running fine, it's something with either you or other apps / modules you have installed, not with GB or your phone.
[Xposed Framework Modules] vogelap:
Completely deactivate ULTIMATE NOTIFICATION CONTROL?

I am a loyal user of GravityBox [KK] on my rooted Verizon Galaxy S4 (4.4.2). I want to $upport the development, so I purchased the GravityBox unlocker.

However, one of the features of the unlocker is ULTIMATE NOTIFICATION CONTROL. I don't want that... I am happy with the way Android default notification works.

Is there some way to remain a $upporting member and COMPLETELY disable UNC? Even enabled (as it is by purchasing the unlocker) and not-configured, UNC turns off notifications I like (such as red light while charging, etc.).
[Xposed Framework Modules] kingvortex:
If you don't configure UNC or activate the default setting then it shouldn't affect stock notifications. It doesn't for me, although we have different devices.

LED while charging is a setting in the "Power Tweaks" section, not in UNC, just FYI. ?
[Xposed Framework Modules] vogelap:
Thank you for your reply.

It's weird... After I installed the unlocker and rebooted, my device started doing three things... a> running hot, b> eating battery like crazy, and c> not lighting the red light when charging. I rebooted several times since, and now it's sitting there with the red light happily glowing while charging. I didn't do anything in GB other than Backup my settings...

Strange.
[Xposed Framework Modules] #sharath:
The clear all button in recent apps screen is not clearing the last open app eventhough i've chose to clear all the apps in the settings.
[Xposed Framework Modules] kingvortex:
Well, being that your device/rom (and mine) isn't supported, strange behaviour and things just not working can be expected.

The features I want work just fine for me, so I purchased the unlocker even though there's no support for my device. ?
[Xposed Framework Modules] vogelap:
Same here... I hope that sometime my device/rom is officially supported... Maybe my donation will help with that.
[Xposed Framework Modules] C3C076:
1) Is your device Xperia? Recently there was a compatibility adjustment made because xperia has some additional view in the recent list that prevented "clear all but current" work.

2) if not 1) check your clear all settings. There are 2 modes - clear all and clear all but current.
[Xposed Framework Modules] #sharath:
Mine is Xperia,but running AOSP 4.4.3.

I have set to clear all in the settings. I think compatibility adjustment broke it. With previous update it was working.

I don't know how many Xperia devices are out there running pure AOSP ROMs.

May be you can add a checkbox to enable/disable compatibility mode for Xperia devices.
[Xposed Framework Modules] trjlive:
I think I may have misunderstood what you were asking about. My apologies if I led you to believe that GB could adjust the lock screen time out. I was just trying to make the point that GB doesn't affect the default lock screen time out behavior. So whatever your ROM provides as the time out, it would be the same before or after GB is installed.
[Xposed Framework Modules] 22sl22:
[MENTION=5008415]C3C076[/MENTION] thanks for this awesome xposed module, been using it for a long time now.

Any chance of an option to include Left clock under Clock options? The one feature this is missing in my opinion :good:
[Xposed Framework Modules] scuba4436:
Hi,

I really love GB to mod my stock, rooted Nexus 5. Thanks for this nice app.

But I'm missing an option:

A search box in the settings, like in Android L Preview settings.

Because, knowing there's an option for a specific setting but not finding it, is very annoying. Any chance to implement?

Thx in advance.
[Xposed Framework Modules] DoctorStrange96:
Can't reorder QuickSettings tiles

The title says it all: I can't reorder QuickSettings tiles. If I try to do this, the GravityBox control UI force closes. If I enter

# logcat | grep AndroidRuntime

in a terminal whilst running GravityBox settings, and after trying to access the tile reorder option, that is what I get (see attached screenshot).

Any tips on what may be causing this?
[Xposed Framework Modules] mdamaged:
What device and ROM?
[Xposed Framework Modules] shmotog:
cheers [MENTION=5362940]trjlive[/MENTION] however i remember you mentioned you can change default timeout on your nexus to 2 mins for lockscreen...how do you do it on your nexus? i see on your signature you are on stock rom so is it like an in built setting in nexus which is missing in moto g? i mean basically what im looking for is some way, any way, to increase the timeout when you are on lockscreen (the keyguard that comes up when you press power button). much appreciate if you can help me out mate.
[Xposed Framework Modules] trjlive:
Well, on my Nexus 5, the keyguard timeout seems to obey the screen timeout in Settings --> Display --> Sleep. I have that set to 2 minutes. I then set my lock timeout to 5 minutes after sleep in Settings --> Security --> Automatically Lock. I have Power Button Instantly Locks enabled on that same screen.

So if I use the power button to turn off my display, which also instantly locks the screen, then if I press the power button again to turn on the screen, it will be waiting for me to input my PIN. The screen will stay on for 2 minutes. However, after about 90 seconds, the screen dims, but it waits the full 2 minutes before turning off. If I change the screen timeout to 5 minutes, the keyguard also follows and stays on for 5 minutes.

I've never messed around with these settings on other devices, so I just assumed this was standard behavior, that the keyguard obeyed the screen timeout. I just tried the same scenario with my 2013 Nexus 7, also running stock 4.4.4 with GravityBox, and it also behaves just like my Nexus 5. So perhaps there's something Moto did that is overriding the default behavior.

But on that subject, I do remember coming across an article, perhaps here on XDA, but could also have been on one of the other Android sites I read, that explained how to manually change the keyguard timeout to a value different than default. I skimmed over it, but I remember it required making changes to a file somewhere (perhaps build.prop), and warned that any ROM update would reset the value back to default. I'll see if I can find that article again, as it might help you out.

---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------

Looks to be an incompatibility between GravityBox and your ROM. I'm sure you read the OP before downloading GravityBox and confirmed your device was compatible, right? The only time I've seen issues with GravityBox FC'ing when messing with status bar options was on non-Nexus and non-GPE devices - in other words, devices that GravityBox is not designed for. Please reply and mention what device/ROM you are using so we can help you further.
[Xposed Framework Modules] DoctorStrange96:
I'm actually using Android on a x86 device, not ARM (in this case, my laptop). Have you ever heard of Android-x86? So. This is what I run. And as far as I know this thing is almost untouched AOSP (at the UI level, of course). The only UI change I've spotted is an additional "power off" tile in the quick settings. May this modification be the cause of the crashes? Or may it be just the fact that I'm running GravityBox on a non-ARM Android system? I don't know.
[Xposed Framework Modules] trjlive:
Actually that's probably the cause of the crashes, yes. Most people think that just because the UI looks like vanilla Android, that the OS itself is also vanilla. That's the common misperception about Moto devices. But it really doesn't matter what the UI looks like, it's what the underlying core code looks like. AOSP is not even designed for x86 devices, so the Android x86 Project makes significant modifications to to the core codebase to allow it to work on the x86 chipset. But this means that the Android x86 core is a long way away from being pure AOSP.

GravityBox

only supports pure, unmodified AOSP

(not just the UI, the core codebase), which at this time,

pretty much means either a Nexus or GPE device

. So your laptop running a completely custom-built branch of Android, is entirely unsupported, untested, and really there's no telling what kind of problems you'll run into.

Android x86 is very much experimental, it's kind of along the same lines of trying to iOS on a Nexus device. While someone might be able to get it to boot, any apps that are depending on the core code being stock will fail to work properly because in order to make iOS work on a Nexus device, requires a lot of core changes and hacks.

Because of the complexity of GravityBox, there is a lot of possibility for core changes to affect the ability of GB to function properly. That is why the supported device list is very specific and concise. Nexus and GPE devices are the only supported devices at this time. Anything else, and well, you're pretty much in experimental territory, and nothing is guaranteed to work properly.

I know this probably isn't the answer you want to hear, but the reality is that if you're going to use GravityBox on a device it wasn't designed for, you just have to accept that things may not, and probably wont, function 100% correctly. If you're developmentally-inclined, you can always fork the GB source code and work on making it work better on your device, the source links are in the OP.
[Xposed Framework Modules] DoctorStrange96:
Yeah, but what can I do, it's the truth... I know that Ax86's core is massively different from AOSP's and the only thing in common between the two is the UI. And because of that I can also say that the problem really is the fact that my system is not "100% pure" Android.

And unfortunately I have zero programming/coding skills to adapt GB to Ax86 and/or other Android-based systems with radical changes at their core codebases, so... Guess it'll have to stay the way it is now. But actually, this feature of reordering the QuickSettings tiles is the only one that doesn't work. Apart from this, no other problems, despite the fact I'm running GB "on a device it wasn't designed for", as you said.

If I only could buy myself a Nexus device, be it either a 5 or even a 4... ?

Anyways, thanks for clarifying it all. My regards.

And sorry for my English (maybe I made some grammar mistakes). And the two question marks were meant to be an emoji (which the site doesn't support).
[Xposed Framework Modules] cableghost:
I can't seem to get Heads Up working; it may be due to a prior conflict. I had installed and used the separate Xposed Heads Up mod, which worked. Then I uninstalled it, upgraded to GB Pro (3.2.3), enabled Head Up Master Switch and set Default UNC...Heads Up will not function. Thoughts?
[Xposed Framework Modules] DoctorStrange96:
Which ROM are you running, and on which device?