Database Develop

Latest nightlies break Gravity Box Quick Settings

Don't know if this has been reported, but the last couple of nightlies cause certain GB QS tiles to be blank (e.g. data, location), and the battery tile to register 0%.
Sent from my Nexus 4 using Tapatalk

bruce7373 said:
Don't know if this has been reported, but the last couple of nightlies cause certain GB QS tiles to be blank (e.g. data, location), and the battery tile to register 0%.
Click to expand...
Click to collapse
Installed GravityBox on 2013-12-08, worked nicely. Upgraded to 20131210 nightly via OpenDelta today, having to reinstall Xposed framework now.

husky69 said:
Installed GravityBox on 2013-12-08, worked nicely. Upgraded to 20131210 nightly via OpenDelta today, having to reinstall Xposed framework now.
Click to expand...
Click to collapse
Reinstalling the Xposed framework didn't help.
Sent from my Nexus 4 using Tapatalk

bruce7373 said:
Reinstalling the Xposed framework didn't help.
Click to expand...
Click to collapse
It helped for me. I had to open Xposed framework app again and to reinstall the framework parts, reboot- and it looks like GG works again.

It's always been the case that the framework had to be reinstalled and it does reactivate GB, but the QS tiles are still messed up. Are you saying you're not having this problem?
Sent from my Nexus 4 using Tapatalk

GB/XPosed also say explicitly not to use them with custom ROMs, or at your own risk.

dibblebill said:
GB/XPosed also say explicitly not to use them with custom ROMs, or at your own risk.
Click to expand...
Click to collapse
True that. It was working on N4 up until the 12/9 update. I tried reinstalling GB and restored data from a Titanium backup and it seemed to work... until I rebooted again. Ah well, I can live without those tiles if everything else is working.
Sent from my Nexus 4 using Tapatalk

dibblebill said:
GB/XPosed also say explicitly not to use them with custom ROMs, or at your own risk.
Click to expand...
Click to collapse
Yup. While I am a big fan of Xposed, and GravityBox is awesome on devices without custom firmwares, use of either of them is an unsupported configuration that is invalid for bug reports.

Entropy512 said:
Yup. While I am a big fan of Xposed, and GravityBox is awesome on devices without custom firmwares, use of either of them is an unsupported configuration that is invalid for bug reports.
Click to expand...
Click to collapse
Is there anything that comes close to being a viable alternative?
Sent from my Nexus 4 using Tapatalk

I read somewhere that 4.4.1 broke GB.
Sent from my Nexus 7 using Tapatalk

The main reason I installed Gravity Box is because of the customizable QS tiles and the lockscreen shortcuts. I believe sooner or later these features will be implemented on OmniROM. Then I won't have the need for it.
If your tiles are messed up after restarting / updating, try to disable Gravity Box from Xposed framework app, clear the Gravity Box settings, reboot, re-enable Gravity Box, reboot again, customize Gravity Box and try not to restart the phone again because you will face the problem again.

Quick Settings
Omni will have Quick Settings customization ?

timbalong said:
Omni will have Quick Settings customization ?
Click to expand...
Click to collapse
I'd be very surprised if it didn't. But I doubt it's up high on priority list...

Another reason to use GB is their circular battery has the correct kitkat color (not always 100% white) and it's vertically aligned with the rest of the icons.

I noticed that toggles, that mess up are "flippable" ones. I don't use that exclusive feature of omnirom, so it would be very nice if developers added checkmark in settings that would disable this feature.
p.s. Hoped that new 4.2.2 omni update will fix this problem, but it didn't.
p.s. 2. If you want to use other features of GG, just don't touch quick toggle settings, or they will mess up after reboot

I noticed this also and it was asked about in the t-mobile note II omnirom thread. Someone said that if you disable the module, reboot, clear app data, re-enable the module, reboot, then just leave all the tiles as is (for example, don't modify anything) then the tiles survive a reboot. Kinda defeats the purpose, since you can change anything but at the very least all the tiles still work and you can still flip them without it breaking. Hopefully it gets fixed soon

The title of this thread is not entirely correct. Omni didn't break GB; KitKat is moving forward, 4.4.2 is progressing and GB is an xposed module that's not keeping up the pace for now (not that it should, thought).
Native customization will be coming soon, I believe. Omni devs are working on the foundations, we can't ask from them to drop that to get their hands on customization right now. But it's on the roadmap, and considering how fast they brought us a clean code and stable KitKat, that will probable come fast.
For now, we got other options too. For example, there are apps that bring toggles to the notification drawer without needing xposed.
Sent from my GT-I9300 using XDA Premium 4 mobile app

Title for this thread should be "Latest nightlies doesnt work with a mod that is recommended not to be used with omniRom"
Sent from my phone using some app

I've been trying to fix this the past few days, glad to know it's not user error but lack of official current support. GB should definitely take the opportunity to merge or stand out as a reliable module very soon. Once someone else takes what they have and can keep up, who knows.

Let me join this discussion to make things more clear.
I don't intend to write too many lines about GB's history, its main goal and policy but I'd like to mention one important thing.
GB is basically a non-flashing custom ROM which primary goal is to bring custom-rom like experience to closed-source platforms (like MediaTek) which currently don't have opportunity to have custom ROMs built from source.
Later while evolved, the secondary goal was established - to bring custom-rom like experience to devices running stock Android.
What I see happening around Xposed Framework recently is that people are basically often turn to using it to "patch" what they can't find in a custom ROM. However, Xposed modules (especially the complex ones) should not be used to supplement missing features in custom ROMs built from source. The best option for a user is to go ask devs of the custom ROM he uses and request those missing features. (This is also clearly mentioned in GB's official thread). People don't combine two ROMs in one device to get more features, neither (thanks god it's not possible!)
GB is not here to keep track of what's changing in all custom ROMs available out there. It is simply unmanageable. GB is here to extend the stock Android experience just like any other custom ROM does.
And words like "GB can't keep up pace with KitKat" sound funny. Actually, it keeps up with stock KitKat pretty well.
I understand these words come from people who have zero experience with GB, but anyway.
GB is currently fully compatible with the latest stock KitKat and is even bringing Dialer tweaks in upcoming version which none of custom ROMs have to this day (flip actions, call vibrations, etc.).

Anyone enabled ART in dev options? On 442 unrooted?

I am afraid to touch it. It is set to dalvik by default.

aviwdoowks said:
I am afraid to touch it. It is set to dalvik by default.
Click to expand...
Click to collapse
Does not hurt.. I have used it for a while -finally back to Dalvik because Deus Ex (sorry, I am an occasional gamer) did not work (FC) on ART. Actually did not have the feeling that ART faster/ snappier was (as it was claimed on 4.4) -but not worse than Davlik neither.
I guess it is your choice; but look out for app compatibility.

ART is not quite ready for primetime. Doesn't hurt to try it. I went back to Dalvik. Some of my apps didn't play nice with ART.
Sent from my Moto X.

Been running ART for more than a month now, I think. I don't have any real exotic apps so it works fine with all of them so far.

Xposed on LG G3 running ART

I have a stock rooted LG G3 that's running ART (and has made a world of difference) . I read that xposed runs on Dalvik. Will I have issues loading Xposed with ART selected, or am I playing with fire?
I've read original post, but I would like some feedback from users who attempted.
-- Yeah, I'm an idiot. Just reread the non-support of ART, sorry for my stupidity!

schmoof said:
I have a stock rooted LG G3 that's running ART (and has made a world of difference) . I read that xposed runs on Dalvik. Will I have issues loading Xposed with ART selected, or am I playing with fire?
Click to expand...
Click to collapse
Xposed will automatically switch you back to Dalvik without prompting you
Honestly, ART is great, but its not THAT noticeable
Sent from my m7spr

Thanks. I guess I'll switch manually back to Dalvik to avoid bootloops. Can't wait until it's officially supported, as my battery life has been noticeably better.

So glad I made the change back. I've opened up a whole new world of mods.

Odd clock behavior

I have used my moto x as a droid pod so i have no cellular connection and my home wifi is screwy so i can't set automatic time and rely on it. The time doesn't set itself when using automatic options. which is fine with me i can just do it manually no problem, right?
Wrong, i haven't really discovered a pattern yet but it seems that every time i reboot my clock sets itself ahead 1h 3m. i think after a series of reboots its totally wrong now. my time currently is 9:50pm and the clock on the phone is 2:58am. the clock in recovery is in synce with the os time but it also skips ahead with reboots i think as i said i really havent determined a clear pattern among issue
any advice? build.prop edit? i did my first edit this evening and it made me feel like a fricken genius so im cool with that but i doubt that there is anything wrong with build.prop. my OS is heavily modified with exposed framework using Xblast and/or gravity box. any help appreciated and will be thanked therefore.

me myself and i said:
my OS is heavily modified with exposed framework using Xblast and/or gravity box
Click to expand...
Click to collapse
i'd start there. recover from stock firmware and start over.

640k said:
i'd start there. recover from stock firmware and start over.
Click to expand...
Click to collapse
ill try thanks for the response

[PSA]Using Xposed causes LAG!

If you are using Xposed framework on the Note 4, Secure storage will fail to process and save data, which leads to a Sensor service hangs, which causes the laggy experience some of you have been having.
This was an issue back on the S5, it is fixed by using this module XSecureStorage by @wanam or disabling S Health.
However from what I have heard this doesn't fix Private Mode.

just to clairfy...mine is laggy all the time. I am probably wrong considering it is 830am but it said s-health and private mode only...does that mean that module will only fix the lag
when using s-health?

installed XSecureStorage but S health still hang. it's really a difficult decision: use xposed for full control, or uninstall xposed for smoother operations...

RomBox said:
installed XSecureStorage but S health still hang. it's really a difficult decision: use xposed for full control, or uninstall xposed for smoother operations...
Click to expand...
Click to collapse
What if you "freeze" S health using ROM Toolbox?. Does it still cause problems?

are you using ART or DALVIK as your runtime?

Shtihi said:
are you using ART or DALVIK as your runtime?
Click to expand...
Click to collapse
You can't use Xposed with ART yet.

Batfink33 said:
What if you "freeze" S health using ROM Toolbox?. Does it still cause problems?
Click to expand...
Click to collapse
disabled S Health use TB and installed xposed back, so far no lag noticed...

Got my Note 4 last night, and it lagged right away straight out of the box.
If you boys are only getting lag after installing Xposed you're lucky!!! lol
Although I was planning to install it, I might think twice after your thread. How bad is it exactly?
For example my settings always stutters if I open it and start trying to scroll straight away. If I wait a couple of seconds, it's usually fine.
Same goes for pressing recently used apps button, and scrolling through the card stack. If I give it a second it's ok, but if I try straight away it's lag city.
So far I've found 0 difference between the Note 4 and the S4. Maybe I'm just unlucky!

prophet42 said:
Got my Note 4 last night, and it lagged right away straight out of the box.
If you boys are only getting lag after installing Xposed you're lucky!!! lol
Although I was planning to install it, I might think twice after your thread. How bad is it exactly?
For example my settings always stutters if I open it and start trying to scroll straight away. If I wait a couple of seconds, it's usually fine.
Same goes for pressing recently used apps button, and scrolling through the card stack. If I give it a second it's ok, but if I try straight away it's lag city.
So far I've found 0 difference between the Note 4 and the S4. Maybe I'm just unlucky!
Click to expand...
Click to collapse
TRY THIS I hope this helps as much as myself
https://www.youtube.com/watch?v=RAXtjgrfgEY

asia559571 said:
TRY THIS I hope this helps as much as myself
https://www.youtube.com/watch?v=RAXtjgrfgEY
Click to expand...
Click to collapse
First think I did out the box =)
Along with removing touchwiz, switching off certain google now features (such as "OK Google" detection), and removing flipboard.
Always slowed the animations down since the days of the Galaxy S 3. S Voice and health are the first things I remove since the S5.
It helps a little, but unfortuntely the lag is still there (well unless I leave it a split second for it to load).
But that's something I can live with. Thanks anyway. Anyone who doesn't done it, it will help.
Although one interesting side effect is the accessability options mess up, so now the calculator talks to me lol.
But hopefully that will be addressed soon. There are other threads on that subject.

Wanam xposed module already has these functions built in. Been using it since day 1. No need for a separate module guys

badwolf94 said:
If you are using Xposed framework on the Note 4, Secure storage will fail to process and save data, which leads to a Sensor service hangs, which causes the laggy experience some of you have been having.
This was an issue back on the S5, it is fixed by using this module XSecureStorage by @wanam or disabling S Health.
However from what I have heard this doesn't fix Private Mode.
Click to expand...
Click to collapse
I don't know but I think you are posting wrong information.
I've been using xposed and secure storage on FireKat without any lagging or secure storage issues.
My Note runs buttery smooth and 100% stable since day one.
Cheers ?
Sent from my SM-N910T using Tapatalk

Rayan said:
I don't know but I think you are posting wrong information.
I've been using xposed and secure storage on FireKat without any lagging or secure storage issues.
My Note runs buttery smooth and 100% stable since day one.
Cheers ?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false

sawdoctor said:
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
Click to expand...
Click to collapse
Yeah this pretty much, the thread was made back when Note 4 first came out and their wasn't any custom ROMS available. All of the ROMS to-date have the necessary fixes enabled.

I have both private mode and S Health running without any problems or lag. Running Firekat v. 8, Xposed. Disabling secure storage in Xposed is the key.

sawdoctor said:
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
Click to expand...
Click to collapse
I wish it was as simple as editing the Build.prop file... But no, for some reason DynamicKat's Secure Storage does not work for me even though it comes with the required settings on build.prop
No matter what I throw at it, paches, fixes, editing build.prop, disabling SHealth, xposed modules, etc, it simply refuses to work.
But the good thing is that at least on Firekat it does work flawlessly as I've mentioned before.
Cheers!

wipe cache and data of s health in app settings, you will have it running again, I have no lags