[Verizon Motorola Droid Turbo General] ChazzMatt:
Here's why I started using xposed with modules in the first place and why I stopped...

On my 2013 LG Nexus 5 phones (mine and my wife's), I was eventually forced to run xposed/Gravity Box plus some other modules, because my long-time favorite ROM I had been using since 2011 gen3 Galaxy Nexus went off the rails. During the time I used my LG Nexus 5, the ROM team -- which covered several devices -- got some new militant members who started locking out settings choices. :(

Android is about choice. I understand it was their ROM, and they can do what they wanted -- but their ROM design philosophy drastically changed from when I first started using the ROM. Previously they had default choices (DPI, etc) for each device, but also supplied tools or alternate menu choices to change those if you wanted something different. They suddenly decided all those settings would be only their way. Some apps do not work well with miniscule DPI; it was documented -- they didn't care. They loathed stock DPI, no matter the device -- they insisted it be 70% of stock, no matter what stock was. While I could use Build Prop Editor to change DPI, they also disabled AOSP Recents for their own inferior version of Recents they had designed. At first they gave a choice of their own Recents or AOSP Recents, but then in the next stage of militancy they disabled AOSP Recents, so you HAD to use their version. And you couldn't "Clear All" with one touch.

People then started installing Gravity Box to enable AOSP recents (the code was still there). The ROM team then stripped out the code so you couldn't use Gravity Box to enable AOSP "recents", and especially "Clear All Recents" with one touch. (That was my first taste of Xposed, to give me back customization choices that ROM team had taken away.) Well, you could do that at first -- use Gravity Box to enable AOSP Recents -- but when they discovered people were doing that and telling others in the ROM threads how to do it, they even stripped out the AOSP Recents code! So, it was going to be their way or no way. :rolleyes: I don't understand why they turned on their users like that. It was a great, fast ROM and until then you could customize it how you wanted.

I wasn't the only one who felt they went awry. Many "unofficial" versions of the that ROM started popping up, which restored the choices they had removed -- but not in time for me. I ditched the ROM and went to stock Google AOSP + xposed/Gravity Box with a few other modules to create what I wanted.

Then, after owning two different generations of Nexus phones (4.65", and 4.95"), in late 2014 Google screwed up and released the 6" Nexus 6 instead of something more reasonable (like the 5.2" variant they were testing as late as mid-August 2014). So, I bought two 64GB Moto XT1225 (for about $700 each) which was basically the 5.2" version of the Moto Nexus 6 Google wouldn't release. No custom ROMs were available yet for the XT1225, so I just kept rooted Moto stock with xposed/Gravity Box + other modules.

I used it with KitKat 4.4.4 on my XT1225 and I even used it with Lollipop 5.0.2 on my XT1225. I was very glad they were able to adapt Xposed to work with ART instead of just Dalvik.

But Gravity Box module in particular has a warning NOT to use it with heavily customized ROMs or there will be conflicts. And CM is a heavily customized ROM. When I switched to CM, I stopped using Gravity Box. Also CM was customized enough I didn't need the other xposed modules (for audio levels, Qi charging sounds, etc.) There was only one function not replicated on CM, and I decided I could live without it. IF something is messing up on my phone, I wanted to be able to tell if it was a bug in CM without having to worry I was the one messing up the phone by having xposed/modules conflicting...

I've been using CM for over a year now, so I'm not coversant with the current state of xposed. I was surprised you still have to flash the "alpha" files first before flashing Xposed installer. Seems by now, it would be well out of alpha -- been almost 1.5 years! -- and that the devs perhaps would have made it be an easier 1-step process.