[Q] Stock 4.4.4 + Xposed Framework or Cyanogenmod 12/other roms - Moto X Q&A

I recently rooted my moto X 2013 and used cm12 for about 1 week. It's solid but i prefer active display over ambient display and the ability to use shake for camera & moto voice. Today i switched back to stock and got xposed framework. I'm already liking it more than cm12. what do you guys prefer?

I prefer stock roms :fingers-crossed:

Stock. Everything works as it should, and I am so accustomed to xposed and its feature set that I couldn't think twice. I need a daily driver phone wise and this phone has been fantastic.
Sent from my XT1060 using Tapatalk

stock for sure. it's like having aosp but better cause everything works. especially with xposed.

You can do something like Carbon or CM11 with Xposed. Its much powerful than CM12 which is still in nightlies and has few major bugs like call audio, BT etc

Stock or stock-based rom with GravityBox.

Eclipse FTW!! Xposed hacks and slashes your framework. Eclipse is stock based so everything works and mods are hard coded like they should be. Just my opinion.

nhizzat said:
Stock or stock-based rom with GravityBox.
Click to expand...
Click to collapse
That and YouTube Adaway are all I need..so far.
I threw smooth progress bar on there too just for fun.

I tried cm12 a couple of days ago. It a really nice, but I just couldn't handle not having gravity box, just because I use it for custom vibration patterns for notifications going to my watch.
I was also surprised how much I missed Active Notifications, especially the quick swipe to on when I pick it up. That was the feature I thought was the silliest when I bought the phone. Go figure... Back to eclipse I went.

Related

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.).

[Q] Touchless control and active display is not working for CyanogenMod on my moto x

Hi guys,
I recently flashed new CyanogenMod 11 on my moto x and I lost active display and touchless control app can anyone tell me how do I get back these two app
You don't.
Someone correct me if I'm wrong, but the only ROMs that have Touchless & Active are stock-based ROMs. So AOKP, AOSP, PA, & CM ROMs do not have these features.
I tried using Peekbut not as good as stock AD
Arak-Nafein said:
You don't.
Someone correct me if I'm wrong, but the only ROMs that have Touchless & Active are stock-based ROMs. So AOKP, AOSP, PA, & CM ROMs do not have these features.
Click to expand...
Click to collapse
I installed peek and it worked but it's not so great as stock. Is there no rom's that support stock Active display and touchless?
vinay.k10 said:
I installed peek and it worked but it's not so great as stock. Is there no rom's that support stock Active display and touchless?
Click to expand...
Click to collapse
That the reason i stay with the stock rom. But just wondering which specific features do you want of CM?, because you can implement nearly all with modules on Xposed Framework, especially with GravityBox.
Touchless and active display
alberturer said:
That the reason i stay with the stock rom. But just wondering which specific features do you want of CM?, because you can implement nearly all with modules on Xposed Framework, especially with GravityBox.
Click to expand...
Click to collapse
Ya I have xposed and gravity box which is good but not accurate lik the stock one :/.
I am getting back to stock now having location issue and exchange servers and camera not working well on Cynogenmod 11
There is a Play store app that is similar to active display I believe, but that is the best you'll get.
And it will use far more battery, as it won't run off the low voltage core.
If you just want to flash ROMs but keep Moto features you should check out Eclipse or Krypton. Also checkout Faux kernel (not a rom but still modding fun and great battery life boost got me). AOSP implementation of active display is pretty awful compared to native active display, in my opinion.
Will v give that a try. Right now I'm in PAC ROM and so far it's good but still as you said native active display is the best
Sent from my unknown using XDA Free mobile app
vinay.k10 said:
Will v give that a try. Right now I'm in PAC ROM and so far it's good but still as you said native active display is the best
Sent from my unknown using XDA Free mobile app
Click to expand...
Click to collapse
I tried using PAC for a few days. The battery drain for me was terrible. Every time I pulled my phone out of my pocket the screen was on. I think I screwed up by having active display and their notification screen enabled. Additionally, the 'blame the split screen' crashes were amusing the first few times but quickly became infuriating.
I'm currently trying out slimrom on my moto x. It doesn't have active display, but it's probably the smoothest rom I've used on the phone. I'm using an app from the Play Store, DynamicNotifications, which is a better option, imo, verse the built in AOSP version (which I believe is based on AcDisplay, but I could be completely wrong about that).
I'm going to give slim a try for a few days, but I don't think anything will work as well Eclipse.
If you're set on an AOSP rom, give slim a chance. If you want a feature packed AOSP rom, check out LiquidSmooth (http://forum.xda-developers.com/moto-x/development/rom-liquidsmooth-v3-1-moto-x-ghost-t2781356). I think LS has the same features or almost the same features as PAC, but it didn't crash nearly as much on my device. I actually made it a full week before switching back to Eclipse.
I will try LS this time
seangrimes590 said:
I tried using PAC for a few days. The battery drain for me was terrible. Every time I pulled my phone out of my pocket the screen was on. I think I screwed up by having active display and their notification screen enabled. Additionally, the 'blame the split screen' crashes were amusing the first few times but quickly became infuriating.
I'm currently trying out slimrom on my moto x. It doesn't have active display, but it's probably the smoothest rom I've used on the phone. I'm using an app from the Play Store, DynamicNotifications, which is a better option, imo, verse the built in AOSP version (which I believe is based on AcDisplay, but I could be completely wrong about that).
I'm going to give slim a try for a few days, but I don't think anything will work as well Eclipse.
If you're set on an AOSP rom, give slim a chance. If you want a feature packed AOSP rom, check out LiquidSmooth (http://forum.xda-developers.com/moto-x/development/rom-liquidsmooth-v3-1-moto-x-ghost-t2781356). I think LS has the same features or almost the same features as PAC, but it didn't crash nearly as much on my device. I actually made it a full week before switching back to Eclipse.
Click to expand...
Click to collapse
I am still facing blame on split screen error :/ and battery drain fast as i see from past 2 days and the boot is very slow compared to other roms I have used so far

[Q] ROM which retains Moto Features

Basically I'm looking for a ROM which retains custom features like Active Display (don't like the custom one from Play Store), the wrist flick for camera, Touchless control, etc. I've already used Eclipse and it's a great ROM however recently it's minor glitches have gotten in my way.
Try Krypton or Epsilon. They are both in the Dev section. I think Epsilon is GSM only though. I'm running Krypton and it is very good.
core2kid said:
Basically I'm looking for a ROM which retains custom features like Active Display (don't like the custom one from Play Store), the wrist flick for camera, Touchless control, etc. I've already used Eclipse and it's a great ROM however recently it's minor glitches have gotten in my way.
Click to expand...
Click to collapse
Glitches? I have been running it since it came out with out one problem.
PiousInquisitor said:
Glitches? I have been running it since it came out with out one problem.
Click to expand...
Click to collapse
My biggest problem is the Dialer crash when swapping calls. I'm kinda forced to switch calls a lot at work and it's not working for me without that feature.
core2kid said:
My biggest problem is the Dialer crash when swapping calls. I'm kinda forced to switch calls a lot at work and it's not working for me without that feature.
Click to expand...
Click to collapse
Oh yeah. Forgot about that. I think you can replace the nexus dialer with the stock Moto X one and the bug goes away.
core2kid said:
Basically I'm looking for a ROM which retains custom features like Active Display (don't like the custom one from Play Store), the wrist flick for camera, Touchless control, etc. I've already used Eclipse and it's a great ROM however recently it's minor glitches have gotten in my way.
Click to expand...
Click to collapse
The stock ROM retains these features.

Xposed status on Lollipop?

Sorry, been out of the loop for awhile, but is Xposed working yet on Lollipop? It was the main reason I went back to Kit Kat a few months back. Thanks.
Yes, for quite a while now. Altough not all modules are working, but I've found that most of the main ones do. Like, Wanam, native clipboard, greenify, etc.....
Still not in the Play Store I see. Waiting until it's perfect?
Running cmremix and been using xposed for quite awhile I have no issues with it

What would you want in a Mofo-ready img?

I've been working on my own customized Droid Turbo 5.1 img and right now, it's just about the same as Computerfreek's (SuperSU v. 2.49 beta, xposed romracer v.71, latest version of stericson's busybox, latest pon-3 build), minus his battery/signal/whatever he added to build.prop optimizations. Also, the HDR bug is completely fixed (although I hear that it's fixed in his latest build as well). I don't really know where to go from here. What are some custom ROM features that you would like to see baked in? If I can make something that is significantly different than CF's, I'll gladly release it to everyone.
firstEncounter also has a stock rooted image that can be installed with extras including xposed, busybox, adblock, tethering, . I personally don't need much more than that unless you want to get rid of a bunch of stock apps. I disable the amazon apps, most of the verizon apps, along with nfl, slacker, audible, imdb... Hopefully we get a bootloader unlock soon
someguyatx said:
firstEncounter also has a stock rooted image that can be installed with extras including xposed, busybox, adblock, tethering, . I personally don't need much more than that unless you want to get rid of a bunch of stock apps. I disable the amazon apps, most of the verizon apps, along with nfl, slacker, audible, imdb... Hopefully we get a bootloader unlock soon
Click to expand...
Click to collapse
FirstEncounter's image has the HDR bug though. Also, CF's image has tethering enabled. Tethering is pretty easy to add. I have no use for it myself, but if I ever go public, it will be in there. As for adblock, I'm pretty sure CF has that too. And yes, I plan on heavily debloating it. If the phone can live without it, it will be gone.
If the rumors are correct, we will have a bootloader unlock in the near future, so this all might be a moot point. Until it is though, it's a fun hobby.
Haven't had any issues with the camera on FirstEncounter image but with the CF mine locked up after the first picture until I turned off HDR. My battery life is also worse on the CF image, guess his tweaks aren't in line with my usage. Either way if you make something for yourself I'm sure a few ppl will give it a try. Not many options for us old root junkies itching to get their next fix [emoji3]
someguyatx said:
Haven't had any issues with the camera on FirstEncounter image but with the CF mine locked up after the first picture until I turned off HDR. My battery life is also worse on the CF image, guess his tweaks aren't in line with my usage. Either way if you make something for yourself I'm sure a few ppl will give it a try. Not many options for us old root junkies itching to get their next fix [emoji3]
Click to expand...
Click to collapse
Really? I tried flashing FirstEncounter's a few weeks ago and I got the HDR bug. Did you apply the patch or no?
In that case, maybe I will upload my image.
No issues with just the V2 and today I flashed the V2 + extras he bundled as an image.
someguyatx said:
No issues with just the V2 and today I flashed the V2 + extras he bundled as an image.
Click to expand...
Click to collapse
Interesting. Have you tried taking a picture with HDR on using the V2 + extras rom? If my theory about why the HDR bug happens is correct, that shouldn't work.
EDIT: Nevermind. He updated the images yesterday. He probably fixed the problem.
Yeah my phone camera usually stays on auto but I switched to HDR just to test and no lock up
Sent from my XT1254 using Tapatalk
Honestly, my battery life isn't that great. I'd love to try your image, op. The only thing I want is a black and red theme, but that is not an easy feat. I use nova/nova prime, so at least my launcher is themed. I just want all of the white backgrounds to be black. Well, and text to be red. Reasons I can't wait to have BL unlock. The Sunshine team says they are working on BL unlock. Time will tell.
dp. edit. something. lol. I have run this image for the last 24 hours. battery life seems equal to the tweaked/modded version, which I find odd. Signal reception has been better. overall, the img runs great. no glitches, freezes. literally zero issues. I don't use cerberus, but I used that version. excellent work at any rate, man. thank you!!! I will probably go back to the other one's new version, but I am tempted to just run this. Again, excellent work. Much appreciated.
1080 resolution option
TheSt33v said:
I've been working on my own customized Droid Turbo 5.1 img and right now, it's just about the same as Computerfreek's (SuperSU v. 2.49 beta, xposed romracer v.71, latest version of stericson's busybox, latest pon-3 build), minus his battery/signal/whatever he added to build.prop optimizations. Also, the HDR bug is completely fixed (although I hear that it's fixed in his latest build as well). I don't really know where to go from here. What are some custom ROM features that you would like to see baked in? If I can make something that is significantly different than CF's, I'll gladly release it to everyone.
Click to expand...
Click to collapse
http://www.xda-developers.com/xperi...ted-oneplus-2-unlockrootflash-guide-xda-tvuo/
referencing this article about the upcoming sony z5 I was wondering if kicking down our resolution a notch may improve performance? that and an upgraded audio experience is all I ask for in a rom. I love VIPER but even at it's best it's fairly buggy.
it wont improve performance to rock 1080p but it will make battery life insane afaik.

Categories

Resources