yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dave_id:
hello

i'm on xperia Z and since I upgraded to kitkat, there's a feature that won't work the same as it used to be.

it's when you close every apps except the running one, no matter what I do, it always closes all apps when it was working on previous rom...
[Xposed Framework Modules] Jrhoop:
Any ideas? Still doing this with latest 4.4.4 GE Rom from Danvdh and also v3.2.1 :(

Installed another xposed torch app and that works?!

Confused.
[Xposed Framework Modules] C3C076:
Make sure you are not blocking camera permission from GB.
[Xposed Framework Modules] Jrhoop:
Beauty! Thanks so much for easy fix.
[Xposed Framework Modules] trjlive:
The only Xperia device that is supported by GravityBox is the Xperia Z Ultra Google Play Edition, purchased directly from Google. Any other Sony device is not supported, and you use GravityBox at your own risk and fully accepting that some features might not work or could even cause problems.

Just because some features used to work, is no guarantee they will continue to work. Either a ROM or a GB update might break any/all GB functionality. That's the unfortunate reality of using a mod on a device it was never intended to be used on.

Of course, this is also all clearly spelled out in the OP, under the compatibility heading, which I'm sure each and every person who downloads GB reads, right? ;)
[Xposed Framework Modules] dave_id:
I hear you loud and clear but wanted to tell about it anyway as it's most certainly a little bug, the other features are working fine...
[Xposed Framework Modules] C3C076:
Even if it was a little bug, there's no way of squashing it without being able to see at least the xposed error log which can be exported from xposed installer.
[Xposed Framework Modules] dave_id:
thing is it's not really producing a visible bug, and I'm not sure it's in the log...

will find it and post it here
[Xposed Framework Modules] dave_id:
hello again,

here is the part from xposed logs i think is matching the "bug", please tell me if I'm wrong

thanks!

View attachment 2819326
[Xposed Framework Modules] AutomaticFailure27:
Might not be related or anything but has anyone else noticed a slight increase in battery drain when upgrading to 3.2.1? I reverted back to 3.2 and battery is back to normal.

Also, I noticed on Purity, that when I have GB installed, even if the option is unchecked for the NavBar, it seems to change my DPI to stock after a reboot. I uninstall GB and reboot and it's back to where it was set.
[Xposed Framework Modules] mdamaged:
Please read the first post on Compatibility.

GB is made for stock ROMs, not custom ROMs, if you like GB features, simply as your ROM developer to add that feture to your custom ROM.

Remove your present ROM, and install a stock ROM, xposed, and GB, and if the problem persists, then you got a bug to report, but right now, you got nothing.
[Xposed Framework Modules] AutomaticFailure27:
Oh I understand that, and Purity is pretty much a close-to-stock experience. It's just more that I have the navbar controls turned off in GB and it still ends up displaying it incorrectly. Since it's off, I would think it wouldn't effect the ROM side of it.
[Xposed Framework Modules] mdamaged:
Then you misunderstand how xposed+GB works. Regardless, it makes no sense to use GB with a custom ROM, it's like using a custom ROM inside a custom ROM.
[Xposed Framework Modules] cadarn07:
Most of gravity boxes features are hooked all the time. This way you don't have to reboot when enabling features. This is why you are having compatibility issues even with options turned off.
[Xposed Framework Modules] ffejy462:
Just out of curiosity, are any of the included apps in the l preview backwards compatible with 4.4.2-4.4.4? I plan on messing around with it tomorrow... Thanks
[Xposed Framework Modules] deeevan:
Have you checked Miscellaneous Tweaks - Clear all recent tasks behaviour? Default behaviour is tap to clear all. I switched it to clear all but current
[Xposed Framework Modules] dave_id:
yes I did , in fact the two options are doing the same thing:

if i tap or long press with the two options, it clears everything...
[Xposed Framework Modules] hinuk:
Hey guys I know that my touchwiz 4.4 archiport rom isn't supported, but is there anyone that is using gravitybox+touchwiz and has got that date next to clock to work.

This bug has been also on 4.3 jb touchwiz roms and gravitybox jb version.

Any other setting seems to work without a problem but that date setting don't seem to do anything, I can even move my clock to center and change it's color but that date just don't show.

And again sorry that I'm asking about touchwiz rom problem as I know that this app is just meaned to be used on pure android, I was just hoping that maybe here someone has battled with same problem and has an answer for me.
[Xposed Framework Modules] fatspirit:
Maybe you could find something specially crafted for TouchWiz: http://xdaforums.com/xposed/modules/index-xposed-modules-collection-post-t2327541
[Xposed Framework Modules] C3C076:
Hard to find a solution when I can't see the source code of the ROM.

But just for curiosity, try with attached APK.
[Xposed Framework Modules] dave_id:
thanks a lot!

unfortunately,it's doing the same behaviour , no matter what I'm choosing pressing long or tap

everything is flushing!
[Xposed Framework Modules] C3C076:
I'm willing to give it another shot if you

1) provide me with the complete xposed log (containing device info GB prints out)

2) SystemUI.apk (ideally both, oone riginal deodexed and another one decompiled)
[Xposed Framework Modules] dave_id:
ok I will do that, thanks!

...for the decompiled systemui.apk, I'am afraid I don't know how to do that!
[Xposed Framework Modules] dave_id:
View attachment 2819880

View attachment 2819882

here is what you asked ...without the decompiled apk, sorry about that
[Xposed Framework Modules] RaffNix1982:
Hi c3c076,

Is it possible that u add an option to show the calendar week in the statusbar beside the clock like the option which shows the date?

Thanx from satisfied User

Gesendet von meinem Nexus 5 mit Tapatalk
[Xposed Framework Modules] claytonjn:
I'm assuming the screenshots were from your actual device, but did you by any chance try running the preview in an AVD emulator? I've been trying to get it working (creating AVD from Nexus 5 Device Definition) but when I start the emulator I just get a black screen. I ended up leaving it running for five hours and in the logcat it's just repeating the following code continuously:

06-27 06:55:18.773 10138-10138/? E/android.os.Debug﹕ failed to load memtrack module: -2
06-27 06:55:19.734 10201-10201/? E/SurfaceFlinger﹕ hwcomposer module not found
06-27 06:55:19.735 10201-10201/? E/SurfaceFlinger﹕ ERROR: failed to open framebuffer (No such file or directory), aborting
06-27 06:55:19.737 10201-10201/? A/libc﹕ Fatal signal 6 (SIGABRT), code -6 in tid 10201 (surfaceflinger)
06-27 06:55:21.889 10235-10235/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/default/accept_ra_rt_table: No such file or directory
06-27 06:55:21.889 10235-10235/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/eth0/accept_ra_rt_table: No such file or directory
06-27 06:55:21.889 10235-10235/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/lo/accept_ra_rt_table: No such file or directory
06-27 06:55:21.889 10235-10235/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/sit0/accept_ra_rt_table: No such file or directory
06-27 06:55:23.402 10236-10268/? E/AudioFlinger﹕ no wake lock to update!
06-27 06:55:23.444 10236-10236/? E/AudioFlinger﹕ int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.r_submix (No such file or directory)
06-27 06:55:24.256 10237-10237/? E/memtrack﹕ Couldn't load memtrack module (No such file or directory)
[Xposed Framework Modules] jacknicholson:
http://www.decompileandroid.com/
[Xposed Framework Modules] C3C076:
Um... Not sure. Haven't tried in emulator, yet. Try playing with the virtual device properties. Even by editing ini file directly.
[Xposed Framework Modules] trjlive:
I also loaded up the L preview on my Nexus 5 earlier today, and have been using it all day. I'm actually really impressed with how smooth and fast it is, and haven't run into any app incompatibilities so far, but then I've only installed my main apps I use on a daily basis. I really like the direction Google is going with the UI and color scheme, though I'm still not sure I like the changes to the notification and quick settings, just feels awkward to use in my opinion. But probably just because it's different, and I'm used to how it is with JB/KK.

Though I've realized one major thing I'm missing: GravityBox. I have become so used to being able to tweak certain settings to my desired preference, that going back to an unrooted, stock ROM, even a preview of an upcoming version, is still a bit frustrating. So I'll be restoring back to 4.4.4 so I can use GB again.

Anyway, it's been interesting using the preview, but I'm just not ready to give up Xposed and GravityBox. You just don't really know how much you depend on GravityBox until you're missing it all day. So, job well done by you, you've got me hooked! Haha! Cheers man, you do amazing work, keep it up! :good:
[Xposed Framework Modules] fbf2201:
Regarding root of L preview, check Chainfire's Twitter.

You need to copy /system/etc/install-recovery.sh to /system/bin/install-recovery.sh
[Xposed Framework Modules] tlf55:
Is that normal that head up notification is showing Google play store notification (update/installing app..) even if it's not ticked in UNC ? and default settings are OFF of course..
[Xposed Framework Modules] C3C076:
Lovely to read. Thanks :)

I'm exactly on the same boat regarding notification area and regarding how quick settings are designed.

On the other side, it's only about coping with a change and adapting to it. Thus a little training for changes happening in real life :)

I kept preview on my phone for 2 hours just to quickly go through it and get in touch with new experience.

It's a good move from Google they decided to release it so developers can start adapting their apps to be ready when it's official.

What I've been feeling recently is that many people are prone to treat it as a daily driver. So on the other hand, this is probably going to have some interesting consequences I was trying to summarize at the end of this post: http://xdaforums.com/showpost.php?p=53714807&postcount=1278

These notifications come from the Package Manager (android system), so blacklisting play store app won't help here.
[Xposed Framework Modules] tlf55:
Don't have enabled head up notification for this too .. :)
[Xposed Framework Modules] Cr4zZyBipBiip:
So. My phone is on 4.4.4. I did a hard reset, no lag when I change the luminosity. I install your xposed app...and my phone is laggy when I change luminosity... I don't understand...
[Xposed Framework Modules] fbf2201:
Can you make an option for transparency?
[Xposed Framework Modules] mjaquino1989:
Not working on samsung galaxy note 10.1 lte. I read the op i guess its really not mean for my device.???
[Xposed Framework Modules] fatspirit:
Yep.
[Xposed Framework Modules] cL0uD`:
Since 3.2.1 update I often can't pick up the phone. When I'm doing something and get called, the screen blinks and stays on my activity, and the call screen stays background, I can't get to it, can't do anything actually, cause during incoming call onscreen buttons don't work. Rolled back to 3.2.0, fine so far. Anyone else experiencing this?
[Xposed Framework Modules] LifeAsADroid:
+1

Great job [MENTION=5008415]C3C076[/MENTION] getting us addicted, lol.
[Xposed Framework Modules] C3C076:
You didn't mention your device/ROM. But heads up is the only major thing that changed compared to 3.2.0. So if it's causing issues on your device, turn it off. Also check out the first post for compatibility info.

Moreover, if you have been using standalone heads up module, you have to disable heads up manually (refer to that module thread) since it left heads up enabled even when you disabled/uninstalled module. (Don't know whether it's been fixed already or not).
[Xposed Framework Modules] cL0uD`:
Nexus 5 stock with xposed, it's in my signature.

When I get a call, heads up is blinking for a second and then I get stuck on my current screen. With 3.2.0 heads up works.

And yes, I had heard it module previously, before it appeared in gravity, but I think I disabled it before uninstalling. But I'll double check this, thanks.
[Xposed Framework Modules] nachordez:
Don't trust in people seeing signatures: Tapatalk does not show them [emoji106]

from Nexus 4
[Xposed Framework Modules] jfriend33:
Latest version causes tons of strange things.

Even with allow all rotations unchecked and lockscreen rotation off, even my home screen rotates. Also the dialer does too. And it always defaults to speakerphone.
[Xposed Framework Modules] cadarn07:
If the latest version does indeed cause "tons of strange things" for you, my guess is an unsupported rom. What device/rom are you using?

Out of the few things you mentioned - do you have any other modules or apps that affect rotation? XGels module as well as many apps will allow you to rotate your homescreen. And the dialer is an app, so it's going to rotate anyway (GB doesn't prevent default rotation in Android). The default to speakerphone issue seems outside of GB. Regardless, deactivate GB and reboot and see if any of this stuff changes. If it doesn't, then GB isn't at fault; if it does, you're probably on an unsupported device but if not, please report that so it can be looked into further.
[Xposed Framework Modules] jfriend33:
Problems only happen with this version of gb enabled.

I have android 4.4 stock on my XT1080m.

My dialer never ever rotated nor did the home screen. I like the home screen rotation though.

Even with screen rotation off from settings display it all rotates.
[Xposed Framework Modules] cadarn07:
Your rom is not vanilla android - read the OP for more info. The dev will let you know if it's something he thinks he can tweak for you.
[Xposed Framework Modules] C3C076:
What [MENTION=4732590]cadarn07[/MENTION] already wrote applies. Moreover I don't see a reason for issues you mentioned. Nothing has been changed recently which could affect rotation functionality.
[Xposed Framework Modules] C3C076:
I forcibly blocked heads up for dialer at code level (except for missed call notification which comes from android telephony framework for which heads up is enabled and working). It's not even possible to change its behavior via UNC. So I find it weird it's happening on your device. My one and only explanation/assumption is that there must be something 3rd party that overrides block deployed by GB.
[Xposed Framework Modules] GermainZ:
Maybe he's using a special dialer app?
[Xposed Framework Modules] C3C076:
Yeah, I thought so, too. But he wrote he used stock which I automatically assumed applies also to dialer unless explicitly mentioned.
[Xposed Framework Modules] gregorina:
When you don't link ringtone and notification volume, are you able to have your ringtone on vibrate and have notification with volume?
[Xposed Framework Modules] qwahchees:
Out of curiosity, will this work on Android 5.0 or L?
[Xposed Framework Modules] knite75:
I'm using SlimKat rom on my Note 3.

After installing Gravitybox, the navigation bar appears. How do I turn it off? I have a Note 3, have no need for the navigation bar.
[Xposed Framework Modules] trjlive:
This is another reason why it's important to

read the OP

, and not just skim it, but

actually read it

. Your problem has already been addressed and answered in the OP, in addition to countless times in this thread. But I'll quote for you the important part, from a previous post that I wrote, and that C3C076 has been kind enough to include in the OP.

I've highlighted the important parts that apply to you:

So you are running a stock OEM ROM on a Motorola Droid Ultra Maxx, which is clearly explained that stock Moto ROMs are NOT stock AOSP, they are as much custom as TouchWiz or Sense. It doesn't matter what the ROM looks like on the surface, what matters is the code underneath. This is why the developer spent the time to detail what devices GravityBox does and doesn't work with.

You've been around XDA long enough now to know you should be reading the entire OP of any mod BEFORE you download and install it. It's extremely frustrating for developers to spend the time to document their app as much as possible, and then have users continue to ask the very questions they've already answered. Please,

for the respect of the developers here on XDA

, if you're not going to read the OP before downloading something, at least read it when you are having a problem, before you post questions or bugs.

---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------

Well, as Android L runs ART instead of Dalvik, and there is no Xposed for ART, and GravityBox requires Xposed, I would guess that GravityBox will not work on Android L.
[Xposed Framework Modules] C3C076:
No. Both are set to vibrate. It's a standard behavior by design.

There's no xposed framework for art runtime. This means no single xposed module will work.
[Xposed Framework Modules] trjlive:
You really should

read the OP

before asking something like this. You are using both a device and ROM that GravityBox was never even intended to be used it. GravityBox is

only designed for pure AOSP, meaning "Google Play Edition" and "Nexus" devices

. Anything else is unsupported - meaning

you get no support

and use it at your own risk. This is all clearly spelled out in the OP, as my previous post to another user who is using an unsupported device.
[Xposed Framework Modules] C3C076:
Just to add. I'm curious what you're missing in slimkat when you went for GB. Slimkat is one of the most comprehensive feature-packed roms out there. Guys like [MENTION=4790322]kufikugel[/MENTION] and [MENTION=3087740]Jubakuba[/MENTION] are very kind and open to the users so I'm sure they would take any of your requests into account if it's legitimate and interesting enough. So rather than supplementing features in custom rom built from source by using xposed (which could potentially degrade the overall rom experience) it would be better to ask the devs to implement them the standard and the most clean way - at source code level.
[Xposed Framework Modules] Gggggas:
First of all the heads up notifications work great on my Note 3 running Xnote v16.

All non expandable notes on the statusbar cant be expanded on the heads up too. For example a facebook invitation text is cut in half just like on the statusbar.

Can this be modded so we fully expand it on the heads up?
[Xposed Framework Modules] trjlive:
Sure, you can mod it any way you like. The links to the source code are in the OP. But as for the dev modding it to work on your unsupported device, I wouldn't count on it. If you were using a supported device and having an issue, then you have something to post about. But if you choose to use GB on a device it was never even designed for, you do so at your own risk and with no support. If some features work for you, that's great, and you're always welcome to download the sources and mod it to work better on your device.
[Xposed Framework Modules] jbdan:
Could the latest update have caused quiet hours to not work on a Friday night (weekend) or show the moon icon in the status bar? It's worked for me during this past week but just noticed when I got a SMS. I've tried turning the module on then off

N5
[Xposed Framework Modules] Goldenmeadow:
Status bar transparency?

Hi!

I just installed xposed and GravityBox v3.2.1 on my Nexus 4 (stock 4.4.4 with root). I like an idea to have one app to manage lots of things. Thanks OP!

Just quick question - I saw lots of nice screenshots of home screens tuned using GB. But I can't find some type of guide... There are simple things but there are things I didn't use before like PIE control...

And main question: I can't find transparency settings for status bar and navigation bar... Do I miss something?

Thanks!
[Xposed Framework Modules] trjlive:
Glad you found GravityBox, welcome to the thread! You're going to enjoy your Nexus device a lot more now that you've got the best tweaking app installed on it. The developer has been amazing about implementing new features, and is very active in this thread to help users out.

GravityBox enables the underlying transparency functionality in the ROM, but it's still up to the specific launcher you're using to implement it. As far as I know, the N4 is using the same stock launcher as the Nexus 7 (both years), which does not support transparent status bar or nav bar. However, there are other launchers in the Play Store that do support transparency, as long as the ROM supports it, which is what GB enables. I would recommend you look at the Google Now Launcher, which is a free download for any Nexus or GPE device. It is the same launcher that the Nexus 5 ships with, and is my preferred launcher. I also use it on my N7 (2013) and the transparency works perfectly.

As for the customization of home screens/nav bars/status bars, it really come down to playing with the options until you find what you like. There's not really a full guide that shows every option, just a description of what the options are in the OP. The nice thing about GB, is that because of the way it's implemented, you can toggle options on and off, and tweak settings, without having to reboot (with the exception of a few select features, that simply don't implement on-the-fly very well). So you can play with the settings and immediately see what it does. And if it doesn't work, or you don't like the result, just reverse what you did. And worst case, if you get things so messed up you can't get it back to default, just uninstall GB, reboot, and reinstall GB and you'll be back to square one.

Since you're using GB on a supported device (Nexus 4) and with a supported stock ROM, you shouldn't have any compatibility problems. In fact, GB runs perfectly well on the stock N4. Though I would suggest you stay away from custom third-party ROMs, even those "based on stock", still include enough underlying changes that can cause issues with GB. But you should be very happy with GB running on your device. And of course, if you have any problems or questions, there are lots of us here in the thread who are very familiar with GB and the devices who can help you out.

Cheers! :)

---------- Post added at 09:41 PM ---------- Previous post was at 09:37 PM ----------

Hmm, I know a few revisions back there was an issue with the calculation that determines when the weekend starts (Friday night is considered weekend, and Sunday night is considered weekday), but C3 had fixed it with an update. I wonder if the issue has cropped back up again?

I'll watch my device tonight and see what happens when the quiet hours is supposed to kick in. It's about 9:45 PM out here in L.A., I have quiet hours starting at 11 PM on weekend nights (which should be tonight), so I should know in about an hour and 15 minutes if it's kicking in properly.
[Xposed Framework Modules] HamBone625:
Running GB KK on a vzw retail moto x and immersive doesnt work at all): hasnt for some time i was hoping one of the updates may have fixed it but nope..
[Xposed Framework Modules] jbdan:
Thanks for checking trjlive. Yeah mine won't come on its weird. Although it has worked all week since the latest update. I remember when it had issues defining when the wknd started and yes the very next update it was fixed. Appreciate you :beer:

N5