Hey guys,
I really do enjoy having the Moto app around, specially for voice commands, since I have a ton of tasker stuff on my phone.
I wish I could find a good way to keep the Moto app and still be able to use custom ROMs.
Is that possible?
If so, how?
Do you do that?
If so, how did you do it?
Every input is apreciated.
Thank you.
I haven't used it for a while, but you should try installing XPosed Framework.
The specialized Moto functions like Voice, their active display, etc need other parts of the stock ROM and kernel and will not work with a custom ROM like CM, etc. Like the other poster said, try installing Xposed and that will add most of the customization options of the custom ROM to your stock Moto ROM.
I have a non dev Moto X from Verizon (XT1060, first gen). It is currently running 4.4.4. What is the most I can do with it? Reading several threads, I am unable to find a conclusive answer regarding this. Looks like sunshine doesn't work nor do most one click tools. My goal is to flash a debloated ROM at the very least if possible.
You won't be able to flash any custom rom without an unlocked bootloader and that's that really. At most you could root(when possible) and manually uninstall bloatwares from the stock rom. I'm glad I had troubles upgrading my phone initially and was able to read about sunshine app on time.
Sent from my XT1060
to the moon and back at least, of course try krypton, or maybe even the modded 5.1 for the 1060, I prefer krypton but the modded 5.1 came a long way quickly I just wasn't feeling the change from simplicity (less options but works perfect for me) of Moto Assist, to the more complex options in LP :/ Check out the respect threads for each rom!
Safestrap only works for 4.4.2 no?
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
channing173 said:
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
Click to expand...
Click to collapse
The CM Quark dev @Skrilax_CZ just bought a 2nd phone so he can test CM13 while still keeping CM12.1 going on his main phone.
http://forum.xda-developers.com/mot...xx-xt1225-cm12-0-pre-release-t3060089/page100
Rule #1 of Fight Club: Never ask for ETAs.
Sent from my DROID Turbo using Tapatalk
Patiently waiting here too ...
Patiently waiting here too. Marshmallow changes look interesting.
and Thanks in advance,
You'll know as soon as you see a changelog here http://www.cmxlog.com/13/quark/
Sent from my XT1254 using Tapatalk
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
EnderKR said:
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
Click to expand...
Click to collapse
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was released.
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have -- or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with that ROM let me use my phone the way I wanted, giving me choice back while still using that ROM. The problem with using xposed + custom ROMs is xposed modules are only guaranteed to work on AOSP ROMs that have not been heavily modified. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in the example I gave, "clear all recents".
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options... but I'm comfortable with CM12.1. (CM dev @Skrilax_CZ brought the first custom ROM and kernel for our Quarks, all others that followed are based his work -- especially the kernel.) I'm running CM12.1 on both my Quarks and have been for months. But the point is both Resurrection Remix and CM12.1 are way more advanced than Motorola stock 5.1, as they are both 5.1.1 + custom features.
NOTE: There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else, but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus, Resurrection Remix and even CM12.1 would have the security updates stock ROM does not.
I'm running CM12.1 plus Moto Camera because someone ported the Moto camera for CM users, and CM12.1 has all the other functionality I need (just different names).
ChazzMatt said:
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was .
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with the ROM let me use the phone the way I wanted, giving me choice back while still using that ROM. The problem with that is xposed modules are only guaranteed to work over ROMs that have not been heavily customized already. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in my case, clear all recents.
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options, but I'm comfortable with CM12.1. BOTH are way more advanced than stock 5.1, as they are both 5.1.1 + custom features.
There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus Resurrection Remix would have the security updates stock ROM does not.
Click to expand...
Click to collapse
Fair enough, I appreciate the input. I'm still pretty new to the custom ROM scene, so there's lots to learn. Why not, I'll give Resurrection Remix a try. Sounds like people love it, and I really like the Moto features so I'd want to keep those. Thanks for the advice
I honestly just like the "all my devices are the same" so all my devices that can run cm.
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Hurts not having stock mm I'm guessing?
Sent from my XT1254 using Tapatalk
Skrilax_CZ said:
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Click to expand...
Click to collapse
koftheworld said:
Hurts not having stock mm I'm guessing?
Click to expand...
Click to collapse
Not necessarily. That didn't stop @Skrilax_CZ from giving us Lollipop (March 2015) before Motorola released stock Lollipop for any of the Quarks. April 2015, Moto Turbo XT1225 was released with stock Lollipop 5.0.2 -- that was the first Quark with stock Lollipop from Motorola. @Skrilax_CZ beat them by using CM12.0 (Lollipop 5.0.2) with Kitkat 4.4.4 kernel, until Motorola publicly released Lollipop 5.0.2 kernel code. (Even though Motorola gave the Moto Turbo XT1225 5.0.2 in April 2015, they didn't release their Lollipop 5.0.2 kernel code publicly for devs to use until a few weeks later.)
Point is, we had Lollipop for Quark before Motorola gave Lollipop to Quark!
And we had CM12.1 (Lollipop 5.1.1) months (mid-April 2015) before Motorola finally gave just 5.1 to the Droid Turbo XT1254 in July 2015:
Skrilax_CZ said:
15th April 2015, 03:37 PM
Done. I have also moved to CM12.1 from now on, so I'll not be backporting latest set of patches back to CM-12.0
Click to expand...
Click to collapse
@Skrilax_CZ used CM12.1 (Lollipop 5.1.1) first with Motorola's 4.4.4 kernel code and then Motorola's 5.0.2 kernel code, until Motorola finally released Lollipop 5.1.x kernel code (September 2015).
Motorola never gave the other Quarks Lollipop 5.1 -- the Moto Turbo XT1225 and Moto Maxx XT1225 officially still have 5.02. and the U.S. Moto Maxx XT1250 (same identical device as the Droid Turbo XT1254, even the same FCC ID) is still "officially" stuck on Kitkat 4.4.4 -- unless you root and install custom Lollipop 5.1.1. ROM. But thanks to devs like @Skrilax_CZ we've had Lollipop 5.1.1 since April 2015!
So, NO, we do not have to wait for Motorola's slow roll-out of stock MM for our Quarks.
____________
mrkhigh said:
I honestly just like the "all my devices are the same" so all my devices that can, run cm.
Click to expand...
Click to collapse
Same here. When I help friends and family, I install CM so I know exactly where all the settings and options are. Two LG G2 phones, a Nexus 7 tablet all owned by other friends or in-laws. My wife's and my Quark XT1225. For some reason I never rooted my wife's Nexus 9 (yet) -- but when I do, it will have CM.
I also install Nova launcher and set all those options the same all all devices (including non-rooted Nexus 9). My wife said, "But my tablet looks like my phone." I replied, "Exactly." That was my intention.
If something isn't acting right, I can quickly diagnose it without having to remember it's set up differently or has an entirely different ROM.
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
IonAphis said:
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
Click to expand...
Click to collapse
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
http://forum.xda-developers.com/showpost.php?p=64573429&postcount=1050
cadenmiller60 said:
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
kitcostantino said:
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
Click to expand...
Click to collapse
Few things to note and remember that the DPI for the two devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
GreaterLesser said:
Few things to note and remember that the DPI for the too devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
Click to expand...
Click to collapse
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
kitcostantino said:
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
Click to expand...
Click to collapse
Well for WiFi, Radios, Bluetooth, etc doesn't the drivers need to be added to the build.prop for the system to actually use them? If possible you could use a build.prop for the turbo in Carbon and just tailor it a bit, theoretically of course. I know it's more complicated than I'm making it sound.
lol. yes, but i get what you mean. in older roms (cm10, cm11) to port, youd copy/paste all of the set perm recursives. in cm12.1 i dont know where to start pulling things from. mind you, i know its not as simple as it used to be because of the new dat format. guess i should read up a bit. lol
Hi everyone
I had a Verizon XT1060 DE that was rooted and unlocked on KitKat. The flashlight/camera flash came loose and it had to be RMA'd over a year ago. Not long after, I got a sweet deal on a LG G4 and the new Moto X (still bootloader locked) sat in a drawer. The LG G4 softbricked during a Verizon OTA update last week and they've sent me a new one (now in the same drawer), and in the meantime I picked up the 2013 Moto X.
This morning I unlocked the bootloader, installed twrp 2.8.6.0-ghost, and rooted with SuperSU. I'm excited to have the Moto X back as my main phone (I missed it, for sure) and I'd love to debloat all the verizon crap.
Can anyone recommend to me a good method for debloating? I'm sure I did it on my old Kitkat Moto X, but it's been years and I can't remember and surely there's some good updated info.
If this has been discussed previously, please just post a link if need be.
Thanks again everyone. Glad to be back using XDA again
Also, if anyone wants to chime in with a recommended ROM that will accomplish the same for me. I've never installed a custom ROM but I wouldn't mind trying.
I like AOSP, but I'd try a CM rom or anything really. My requirement is a debloat ROM that everything works. I need this phone for everyday use, so I need to make calls, take photos, use the flashlight, etc. If there's bugs that have a known fix, that works for me, but I can't run a ROM with decreased functionality.
Please post a link if you have a suggestion.
Thanks again everyone.
I've been using Resurrection Remix for a few weeks now and it works great as my daily driver (I have a XT1060 DE as well). The ROM is fast and everything works, as far as I can tell. Look at the Moto X XDA homepage for the page and details, or try this link: http://forum.xda-developers.com/moto-x/development/rom-ghost-resurrection-remix-5-6-8-t3371948
Good luck!
-Troy
bkoltai9 said:
Also, if anyone wants to chime in with a recommended ROM that will accomplish the same for me. I've never installed a custom ROM but I wouldn't mind trying.
I like AOSP, but I'd try a CM rom or anything really. My requirement is a debloat ROM that everything works. I need this phone for everyday use, so I need to make calls, take photos, use the flashlight, etc. If there's bugs that have a known fix, that works for me, but I can't run a ROM with decreased functionality.
Please post a link if you have a suggestion.
Thanks again everyone.
Click to expand...
Click to collapse
I've only tested Resurrection Remix becuase its the rom with lot of feature from other rom too and its stable for everyday use and I write from my Moto X (XT1052).
For everyday use I suggest to avoid (as now) all 7.x roms because usually have broken microphone and/or camera (only video or photo too) with can be important for many people, so i advice you to stay with 6.0.1 roms right now
Hi all,
I need your help to suggest me a good custom ROM and how to install that on my Moto x 2014. I am really sick and tired of my 2 year old phone as it is now very slow, battery backup has become poor.
I will be really thankful to you people.
You can do as we all here.. read the threads.. coments and try different roms.. the one that better suit your needs, the one you choose.
To not leave you unanswered, personal recommendation, nexus rom or mokee.
I'd say Dirty Unicorns for Nougat, or maybe the new Oreo ROMs that have popped up lately I'm running Lineage 15 and it's awesome.
It sounds like your bootloader is still locked though, am I right?
Jemec26 said:
You can do as we all here.. read the threads.. coments and try different roms.. the one that better suit your needs, the one you choose.
To not leave you unanswered, personal recommendation, nexus rom or mokee.
Click to expand...
Click to collapse
Flipz77 said:
I'd say Dirty Unicorns for Nougat, or maybe the new Oreo ROMs that have popped up lately I'm running Lineage 15 and it's awesome.
It sounds like your bootloader is still locked though, am I right?
Click to expand...
Click to collapse
That's right. Currently I am using 6.0 marshmallow stock version. Neither I know how to unlock bootloader.
Basically, it's been 2 years and i was scared tweaking the OS, but now I am fed up with my phone's performance though it has 801 Snapdragon and 2gb of RAM.
I need to know from- how to unlock bootloader to how to install custom ROM.
To unlock the bootloader just Google "unlock bootloader XT 1095". There are tons of tutorials.
Then you need to install a custom recovery, I'd suggest TWRP. Again, Google is your friend for the how-to's.
Finally, you have to download a ROM and corresponding Google Apps (aka GAPPS package) and install them using the custom recovery.
In terms of which ROM, I'm currently using the unofficial Lineage OS 15 from Andersonmendes and it's a beast. Super smooth and great battery life. Be sure to flash the version from October 10th.
Cheers and good luck in your modding journey!
fabiozon said:
To unlock the bootloader just Google "unlock bootloader XT 1095". There are tons of tutorials.
Then you need to install a custom recovery, I'd suggest TWRP. Again, Google is your friend for the how-to's.
Finally, you have to download a ROM and corresponding Google Apps (aka GAPPS package) and install them using the custom recovery.
In terms of which ROM, I'm currently using the unofficial Lineage OS 15 from Andersonmendes and it's a beast. Super smooth and great battery life. Be sure to flash the version from October 10th.
Cheers and good luck in your modding journey!
Click to expand...
Click to collapse
Thank you so much Fabiozon
I would recommend you the AospExtended 4.6 rom, been using it since it came and had no problems so far.
I recomanded the final rr 5.8.5 nougat.
Stable excelent battery and full extras.
If you are not about customizing your OS a lot, you might consider Lineage 14.1. it receives updates and security patches on a weekly basis.
EDIT. By the way NX Rom is quite good too. Nearly nexus device experience. You can have a dark theme for all UI, so you won't need a Substratum theme just for that.
I'm on AOSP Extended just because it has "advanced ambient display", where you can add double-tap to interact with it (not double tap to wake).
On other roms I keep waking the phone accidentaly when ambient display activates and I touch the screen (in example: when walking with the phone in my hand)
NeriL said:
I'm on AOSP Extended just because it has "advanced ambient display", where you can add double-tap to interact with it (not double tap to wake).
On other roms I keep waking the phone accidentaly when ambient display activates and I touch the screen (in example: when walking with the phone in my hand)
Click to expand...
Click to collapse
You're not taking about AOSP extended 4.6, are you? Because that one doesn't have these nice settings.
EDIT. Sorry, a quick research solved it. First, we need to disable "double-tap to sleep" in Ambient Display settings.