Questions....
I am currently running the Brazilian Stock Moto Android 6.0 ROM and I am loving it. However, I find myself missing the VoLTE from Verizon. That got me wondering about the available ROMs for the Turbo. If I understand correctly,
- If I want Android 6, my only options are this one, Kang, and CM-based ROMs, including ComputerFreek and Bliss. And those two ARE CM-based, correct? There are no other Marshmallow ROMs with stock Moto software, right? Chop chop for flashlight, etc?
- If my assumptions are right in that first part, I should ask: which ROMs include VoLTE?
Thanks for your help!
Sent from my XT1254 using Tapatalk
Marshmallow ROMs (I'm too lazy to provide links because XDA's app would make it a pain, but they're basically the at the top of the Droid Turbo/Moto Maxx Android Development forum):
AOKP
CM13
RR 5.7.X
Brazilian ROM (Stock Based)
Unofficial CM 13
MoKee 6.0
Bliss 6.4
Nexus Experience (NX)
AICP (in the AOKP thread)
(I think that's all of them.) All are CM based except for my Brazilian ROM.
VoLTE:
@computerfreek274's modified stock (Lollipop)
Stock Lollipop
Currently no CM based custom ROM supports VoLTE, nor my Brazilian ROM (stock based)
Thanks!
Sent from my XT1254 using Tapatalk
iiWoodstocK said:
Marshmallow ROMs (I'm too lazy to provide links because XDA's app would make it a pain, but they're basically the at the top of the Droid Turbo/Moto Maxx Android Development forum):
AOKP
CM13
RR 5.7.X
Brazilian ROM
Unofficial CM 13
MoKee 6.0
Bliss 6.4
(I think that's all of them)
VoLTE:
@computerfreek274's modified stock (Lollipop)
Stock Lollipop
Currently no CM based custom ROM supports VoLTE, nor my Brazilian ROM (stock based)
Click to expand...
Click to collapse
You left off Nexus Experience.
We have 8 Marshmallow ROMs currently if we count yours. It's not really a "custom" ROM -- except you customized it to work on all Quarks! (and did a good job)
Current custom Marshmallow ROM list for Droid Turbo/Moto Maxx/Moto Turbo
http://forum.xda-developers.com/showpost.php?p=68810980&postcount=39
None of the Quark Marshmallow ROMs at this point in time allow Verizon VoLTE.
ChazzMatt said:
You left off Nexus Experience.
We have 8 Marshmallow ROMs currently if we count yours. It's not really a "custom" ROM -- except you customized it to work on all Quarks! (and did a good job)
Current custom Marshmallow ROM list for Droid Turbo/Moto Maxx/Moto Turbo
http://forum.xda-developers.com/showpost.php?p=68810980&postcount=39
None of the Marshmallow ROMs give Verizon VoLTE.
Click to expand...
Click to collapse
DARN. I had an inkling I was missing one (actually 2 if I found AICP, though it doesn't have its own thread..)
iiWoodstocK said:
DARN. I had an inkling I was missing one (actually 2 if I found AICP, though it doesn't have its own thread..)
Click to expand...
Click to collapse
Right. I left off AICP ROM because
1) it doesn't have Ambient Display (which makes it a non-starter for most), and
2) the ROM maintainer (who also has Bliss and AOKP) isn't really actively supporting it with a separate thread like the other two.
It may be an interesting "project" but without Ambient Display (or the Moto Display in your stock Marshmallow ROM) what unique feature does AICP ROM have the other 8 Marshmallow ROMs do not? (For instance the Quark Resurrection Remix and Bliss ROMs have the ability to use most Moto apps. Your own stock-based ROM can use all Moto apps by default. AICP does not have that functionality.) And if you don't like Ambient Display/Moto Display, you can just turn it off on any of those 8 ROMs; you don't need to install a ROM with that feature lacking.
arizonaomnia said:
I am currently running the Brazilian Stock Moto Android 6.0 ROM and I am loving it. However, I find myself missing the VoLTE from Verizon. That got me wondering about the available ROMs for the Turbo. If I understand correctly,
- If I want Android 6, my only options are this one, Kang, and CM-based ROMs, including ComputerFreek and Bliss. And those two ARE CM-based, correct? There are no other Marshmallow ROMs with stock Moto software, right? Chop chop for flashlight, etc?
- If my assumptions are right in that first part, I should ask: which ROMs include VoLTE?
Thanks for your help!
Click to expand...
Click to collapse
@iiWoodstocK answered this, but I'm going to differentiate slightly.
There are two stock-based ROMs --
@iiWoodstocK Marshmallow Motorola ROM adapted from the XT1225 which will run on all Quarks, since he added CDMA prop lines and used custom kernel from @bhb27.
ComputerFreak274 Lollipop ROM based on Verizon's stock firmware. (Verizon has not released the XT1254 Motorola Marshmallow ROM yet, and may never do so.)
Neither of those ROMs are "CM-based". @bhb27 kernel is based on CM kernel, yes, but @iiWoodstocK's ROM is otherwise pure Motorola Marshmallow for Quark.
Currently, only ComputerFreak274 Lollipop ROM allows Verizon's VoLTE because it hews very closely to Verizon's firmware.
In another post higher up I gave a link to all the Marshmallow ROMs. No Quark Marshmallow ROM currently has Verizon VoLTE. @bhb27 (official Quark TWRP dev, Resurrection Remix & Mokee ROM maintainer, dev for several Quark apps) is still working on it, but with Verizon it's not something you just turn on and turn off -- there's also something on the carrier side that also allows it. @bhb27 is also limited in that he lives in Brazil, has an XT12225 and does not use Verizon. Somehow ComputerFreak274 ROM has it, and either he's not sharing the secret or maybe he doesn't even know why.
ChazzMatt said:
@iiWoodstocK answered this, but I'm going to differentiate slightly.
There are two stock-based ROMs --
his Marshmallow Motorola ROM adapted from the XT1225 which will run on all Quarks since he added CDMA prop lines and used custom kernel from @bhb27.
ComputerFreak274 Lollipop ROM based on Verizon's stock firmware.
Neither of those ROMs are "CM-based". @bhb27 kernel is based on CM kernel, yes, but @iiWoodstocK's ROM is otherwise pure Motorola Marshmallow for Quark.
Currently, only ComputerFreak274 Lollipop ROM allows Verizon's VoLTE because it hews very closely to Verizon's firmware.
In another post higher up I gave a link to all the Marshmallow ROMs. No Quark Marshmallow ROM currently has Verizon VoLTE. @bhb27 (official Quark TWRP dev, Resurrection Remix & Mokee ROM maintainer, dev for several Quark apps) is still working on it, but with Verizon it's not something you just turn on and turn off -- there's also something on the carrier side that also allows it. @bhb27 is also limited in that he lives in Brazil, has an XT12225 and does not use Verizon. Somehow ComputerFreak274 ROM has it, and either he's not sharing the secret or maybe he doesn't even know why.
Click to expand...
Click to collapse
CF's ROM has it because his ROM is built on stock. I don't believe he had to add it in especially since one of his more recent posts he stated he's been able to port the settings for VoLTE to his WIP Marshmallow ROM, but not functioning VoLTE itself.
iiWoodstocK said:
CF's ROM has it because his ROM is built on stock. I don't believe he had to add it in especially since one of his more recent posts he stated he's been able to port the settings for VoLTE to his WIP Marshmallow ROM, but not functioning VoLTE itself.
Click to expand...
Click to collapse
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
ChazzMatt said:
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
Click to expand...
Click to collapse
I wonder which Verizon devices have volte capability on custom roms. I was going to do a spreadsheet, but I haven't had time.
koftheworld said:
I wonder which Verizon devices have volte capability on custom roms. I was going to do a spreadsheet, but I haven't had time.
Click to expand...
Click to collapse
On various devices, I can't find any for Verizon with VoLTE that are not just stock modified ROMs.
The Nexus devices are the exception, like the Nexus 6.
My brother is getting an LG G3 VS985 for Verizon. I would love to root it and put on custom ROM like Resurrection Remix, but I can't find that VoLTE/Advanced Calling works with custom ROMs. I either get "no" or no answer when I ask the question in various forums.
ChazzMatt said:
On various devices, I can't find any that are not just stock modified ROMs.
The Nexus devices are the exception, like the Nexus 6.
My brother is getting an LG G3 VS985 for Verizon. I would love to root it and put on custom ROM like Resurrection Remix, but I can't find that VoLTE/Advanced Calling works with custom ROMs. I either get "no" or no answer when I ask the question in various forums.
Click to expand...
Click to collapse
Hopeful bb can find the right info from the logs that were provided. Would a huge win for those of us with Verizon as a network.
I *think* I've read Victara CM has Verizon VoLTE. Not 100% sure...
ChazzMatt said:
Then there must be some "flag" , some piece of code, in Verizon's firmware that says "this is a Verizon phone" or something. By him porting just the VoLTE settings to a Marshmallow ROM and VoLTE is not working means even he doesn't know what that "secret" piece of code is.
Back in the Microsoft DOS days when they were battling DR-DOS, Caldera who owned DR-DOS accused Microsoft of stealing DR-DOS code. (of course they did). Microsoft denied, denied, denied. Caldera file a lawsuit . In the final stage of the lawsuit, DR-DOS creator Gary Kildall had a card up his sleeve which he did not reveal until then. A demo in front of a judge. Microsoft technicians set up a custom built pristine PC with ONLY Microsoft DOS software. Microsoft oversaw all the installation and made sure no one else touched the computer.
Dr. DOS creator Gary Kildall then sat down at the "Microsoft" PC and typed in a simple keyboard command. In HUGE LETTERS a splash screen appeared which said displayed his name and copyright notice. He had hidden that in their code just for this kind of PROOF. Microsoft lawyers immediately requested a recess, followed by a generous multi-million dollar settlement offer tied to non-disclosure agreement. (No one has been able to find it since, because allegedly part of the agreement was to "license" the code and remove that notice.) Press reported $150 million, but allegedly it was actually even higher.
Part of the lawsuit also focused on anti-competitive measures from Microsoft, that Microsoft also purposely made PCs malfunction if Dr-DOS was installed, so people would thing Dr-DOS was buggy. Microsoft executive emails were found discussing this very tactic. But they weren't above STEALING code from Dr-DOS to put into Microsoft DOS. So, even though Dr-DOS was not installed on that demo PC, still the founder was able to call up a DR-DOS splash screen.
And yes, I read all this in a article years ago, which I cannot find now because maybe Microsoft lawyers are very zealous?
My point is something like that may be in Verizon firmware to allow VoLTE for Verizon devices? Some hidden code.
Click to expand...
Click to collapse
Wow, I used Dr DOS!!!!
Related
Kind of an off-topic question here, but I'm serious. The Moto X is nearly a year old, and has been rooted/bootloader unlocked since the beginning. Why does every good rom have some sort of hardware problem? (namely audio-related) Every rom I want to try, I back off because they are reported to be buggy. With my Atrix 4G, there were some amazing daily driver roms that I used. But there seems to be no rom that is stable enough to use for the Moto X, or am I wrong? Your guys input on the best current rom? I am willing to go the CM nightly route, because it intrigues me.
Stock stock stock. What's wrong with stock and Xposed? Stock rom is fast and stable. And technically a consumer edition Moto X is NOT bootloader Unlockable. Plus gaining root access is a PITA.
Sent from my XT1060 using Tapatalk
DroidOnRoids said:
Stock stock stock. What's wrong with stock and Xposed?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Theming support with stock and Xposed sucks balls. I can't install any good theme. HKThemeManager gives me a "sh: applet not found" error when attempting to fix a theme (I have apktool installed properly and all Xposed modules updated), and most themes won't convert properly for XTheme Manager (errors on rebuild).
I miss being able to theme my phone like I could using 90% of the Atrix 4G roms with the CM/T-mobile theme engine. I really want to stay stock with my Moto X too, because of the motorola features, but the X-posed theme devs (Xtheme and HKTheme) seem to lack in support. XTheme Manager seems to have ceased in development, as it doesn't support CM11 and hasn't been updated in nearly a year. HKThemeManager is being updated recently, but my Moto X doesn't seem to work with it properly, and the developer is quite unresponsive and/or unable to help.
Even when a theme does work, it isn't "complete" like using it with the CM theme engine as intended (due to restrictions with Xposed.
If you have any thoughts on the matter, or other ideas, I'm all for it.
We have Eclipse! But in truth there have never been many "Booted" phones til lately.
K, we have cm, slim, aokp, gummy, PAC man....etc. But, most prefer stock, so they can keep their moto features....the reason many bought the phone. Also aosp/cm roms don't have the moto features.
There are a few stock based roms that have the moto features, but probably not the themes.
And many consumer moto x's can be unlocked, not just dev editions. Its only verizon, at&t and RW that can't be unlocked. Maybe a couple overseas kinds too.
And you can't flash any ROMs without root...and its getting to a point that without an unlocked bootloader, you won't have root.
Really gotta research before buying a phone these days. Forget root exploits, cause like the X, they may not work on future android versions. If you want root, get a phone that you definitely can unlock the bootloader. Nothing else is a sure thing.
kj2112 said:
Really gotta research before buying a phone these days.
Click to expand...
Click to collapse
I bought the Verizon Moto X Developer Edition. I know what I'm doing. I'm just frustrated with Theme support for Xposed.
kj2112 said:
K, we have cm, slim, aokp, gummy, PAC man....etc.
Click to expand...
Click to collapse
Most of those have a problem with speakerphone working, among other audio-related issues. Even some stock-based roms have issues. Seems like this phone just wasn't meant to be customized. To be honest, the phone runs amazingly. Battery life is shocking, to say the least. I just want more control over the appearance of my phone UI. That's all I want.. I just wondered if there was an answer to that besides buggy custom roms...
Do you think the "sh: applet not found" error I'm having with HKThemeManager might be related to me installing busybox with this?
Drakonas said:
I bought the Verizon Moto X Developer Edition. I know what I'm doing. I'm just frustrated with Theme support for Xposed.
Most of those have a problem with speakerphone working, among other audio-related issues. Even some stock-based roms have issues. Seems like this phone just wasn't meant to be customized. To be honest, the phone runs amazingly. Battery life is shocking, to say the least. I just want more control over the appearance of my phone UI. That's all I want.. I just wondered if there was an answer to that besides buggy custom roms...
Do you think the "sh: applet not found" error I'm having with HKThemeManager might be related to me installing busybox with this?
Click to expand...
Click to collapse
I agree. The X is amazing....but....boring. Lol. That's why my wife happily took mine and I got an N5.
kj2112 said:
I agree. The X is amazing....but....boring. Lol. That's why my wife happily took mine and I got an N5.
Click to expand...
Click to collapse
I probably should have gotten the N5... however I will wait to see what comes around for this phone..or if anything comes around for better theming on stock. (The Ex-Themer Xposed modules look promising) Don't exactly have the income to purchase another phone.
EDIT: Well apparently the HK Theme Manager developer either doesn't know what he's doing, or is developing with a pre-Jelly Bean phone, because his app is incorrectly writing files to my Moto X's SDCard.
"Incorrectly" as in not writing them at all. His app throws constant errors stating "File not found" with files the app should be creating. (for example: The copy of the extracted resources not being found before changing the files, or the apk that was repacked not being able to be found when trying to sign the apk)
Can someone that knows what they're doing step up to the plate and make a WORKING theme management Xposed module?! OMG. *Prepares to throw tables
I returned the N5 and got this phone, no regrets at all.
Sent from my XT1053 using Tapatalk
If I wanted a Moto X without Moto X features, I would have bought a different phone.
eksasol said:
If I wanted a Moto X without Moto X features, I would have bought a different phone.
Click to expand...
Click to collapse
But I don't want a Moto X without Moto X features. I want a Moto X with theming features that work, which doesn't seem to be a thing right now...
The development will flourish once Motorola ceases their support. And as far as I can say, we will have active display and TC as an inbuilt feature in the future versions of android as google has Already patented it. (for eg. you can see in Project Ara phones)
Necessity is the mother of invention, as you can see now there is no need for roms at the moment since stock is kickass, so less development.
:angel:
DaRkRhiNe said:
Necessity is the mother of invention, as you can see now there is no need for roms at the moment since stock is kickass, so less development.
:angel:
Click to expand...
Click to collapse
True, but my guess is that once TC and AD become fully available to custom rom devs, this phone's development goals will change, as I feel that those two features are the main reasons people are staying with stock.
Drakonas said:
True, but my guess is that once TC and AD become fully available to custom rom devs, this phone's development goals will change, as I feel that those two features are the main reasons people are staying with stock.
Click to expand...
Click to collapse
After official updates end....people will have to pick: Moto x features, or latest greatest android version. Guarantee our X will stick with last update and keep the features.
Well, wife has it now....if it were mine when support ends, I'd probably flash the latest greatest and live without the moto features.
kj2112 said:
if it were mine when support ends, I'd probably flash the latest greatest and live without the moto features.
Click to expand...
Click to collapse
When this happens, do you think you'll go with a custom rom, or would nightly CM be something you would go with?
Drakonas said:
When this happens, do you think you'll go with a custom rom, or would nightly CM be something you would go with?
Click to expand...
Click to collapse
Nothing against CM....but I haven't used cm in a long time on any device. Just not for me.
But that's just me....many love it!
And I'm not into nightlies either....I prefer stable builds...even tho its less exciting. Lol
kj2112 said:
And I'm not into nightlies either....I prefer stable builds...even tho its less exciting. Lol
Click to expand...
Click to collapse
Yeah I would probably agree. I want a stable rom that I don't have to worry about. Granted this app makes me want to try CM out.
I'm just kind of surprised there isn't basic ROMs with simple features like advanced reboot, aosp data signal icons, volume warning removed, adblocking, basic things that people generally want. I know everyone says just use xposed but I really prefer to use ART.
This and the Nexus5 are the only phones I've had that didn't immediately get cm. Nightlies are great depending on the moderator and how often they update.
I don't see the point of CM on the MotoX. It's like replacing a bug free stock android build plus great features with a buggy stock android build with different, not as great features.
CM is great to replace bloated UI ROMs. *ahem *touchwiz. Once this phone becomes obsolete I'll probably get the fastest specced phone and CM it... or whatever Motorola puts out next
KJ said:
K, we have cm, slim, aokp, gummy, PAC man....etc. But, most prefer stock, so they can keep their moto features....the reason many bought the phone. Also aosp/cm roms don't have the moto features.
There are a few stock based roms that have the moto features, but probably not the themes.
And many consumer moto x's can be unlocked, not just dev editions. Its only verizon, at&t and RW that can't be unlocked. Maybe a couple overseas kinds too.
And you can't flash any ROMs without root...and its getting to a point that without an unlocked bootloader, you won't have root.
Really gotta research before buying a phone these days. Forget root exploits, cause like the X, they may not work on future android versions. If you want root, get a phone that you definitely can unlock the bootloader. Nothing else is a sure thing.
Click to expand...
Click to collapse
Great points all around. My old reasoning for wanting roms on my old Razr M was to have a more updated version of Android. With the X I have that without the hassle.
Sent from my Moto X
Just out of curiosity, why hasn't there been any custom roms or development ?
I really hope someone is working on root for non pure edition.
Development was pretty light with the 2013 version too. The combination of limited market (dev edition only) and the near stock experience, and the loss of what makes the Moto X special, means not very many people are seeking an alternative.
What about kernels? Surely we could benefit from custom kernels and keep all our moto x a pure android experience, correct? Like possible for color cal and battery life? :silly:
Custom roms ya custom kernel can come only after motolola releases its kernel sources
My impression was since its " pure edition" it would be developer friendly .
dia_naji said:
My impression was since its " pure edition" it would be developer friendly .
Click to expand...
Click to collapse
It is developer friendly. There just isn't a lot of development for the reasons listed above.
Restola said:
Development was pretty light with the 2013 version too. The combination of limited market (dev edition only) and the near stock experience, and the loss of what makes the Moto X special, means not very many people are seeking an alternative.
Click to expand...
Click to collapse
This, I have a Droid Maxx and the wife has a Moto X. We enjoy the anti Samsung, pure Google experience enhanced with touchless and active display. No reasons to try any AOSP Roms. Development is so light for the Droid Ultra/ Maxx that CM dropped support for it, but that is due to how good the stock ROM is. I ran Paranoid on my RAZR Maxx HD but still moved back to stock because it is smoother and has better cell reception. All the cool little functions are just that, cool. Paranoid's implementation of their dynamic status and notification bars are the best I've seen, much better than the xposed modules. But at the end of the day, it is about functionality and useability. Stock Motorola Roms are very good, just need to debloat all the Verizon crap in my case. As far as kernels, hopefully faux123 will do something with the new Moto X. I'm running his kernel on my Droid Maxx and Moto X and it definitely enhances the phone more than any aftermarket Roms could. The reason why I hangout in the Moto X forums is because there are not a lot of us Droid owners and the Moto X forums is where we get most of our stuff. I'm running a Moto X port on my Droid Maxx for example. This holds true for the new Droid Turbo also which I am definitely interested in. That is if there's a way to unlock the bootloader. Unlocked bootloader with 3900 mAH battery and 21 mp camera and the Moto X experience? I'm in, still have an upgrade available! But I don't foresee the bootloader or root being available for these new phones for a long while. In the mean time, I'll enjoy my unlocked Droid Maxx and Moto X and continue to lurk around here. Lol
You can use Xposed Framework, I think, with the 2nd Gen. Moto X. It will give you many of the popular features from custom roms that aren't in stock Android.
The only other reason I can see for custom roms on the Moto X (at least as far as it concerns me) is that I think they can be better for privacy and getting rid of under the hood bits of code that might be abused for marketing/tracking purposes. Also I think the CyanogenMod Account is a more secure way to track and remotely wipe your phone, than the Android Device Manager. At the end of the day, I trust Cyanogen to have my security and privacy in mind more than Google or Motorola. But I don't think this is enough that people will feel motivated to develop a lot for the Moto X (for the reasons already stated above).
I can't see development being any busier than the quiet 2013.
Too many Moto limitations... Like bootloaders not being able to be unlocked on some big carriers. And as said, no custom features on aosp/cm roms. Downgrade issues.... If it's like the 2013. Etc.
The X's are not for flashaholics .... That's for sure.
jdubya42 said:
I really hope someone is working on root for non pure edition.
Click to expand...
Click to collapse
The pure edition root method by jcase works fine on other devices. I rooted my xt1093 last week, seen some Brazilian carriers' rooted (also non pure, xt1092 maybe?), and I'm 100% confident it'll work for any moto x with an unlockable bootloader.
Am I wrong in thinking that only the pure edition has an unlockable bootloader?
Where to find stock firmware? For verizon?
jdubya42 said:
Am I wrong in thinking that only the pure edition has an unlockable bootloader?
Click to expand...
Click to collapse
Yes, quite wrong. Search and Google are your friend here.
Only Verizon cannot be unlocked presently AFAIK.
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
cornpollen said:
Where to find stock firmware? For verizon?
Click to expand...
Click to collapse
I don't think any carrier branded X has made this available yet...
Well thats why I didn't know that. I have the VZW model.
cb474 said:
You can use Xposed Framework, I think, with the 2nd Gen. Moto X. It will give you many of the popular features from custom roms that aren't in stock Android.
The only other reason I can see for custom roms on the Moto X (at least as far as it concerns me) is that I think they can be better for privacy and getting rid of under the hood bits of code that might be abused for marketing/tracking purposes. Also I think the CyanogenMod Account is a more secure way to track and remotely wipe your phone, than the Android Device Manager. At the end of the day, I trust Cyanogen to have my security and privacy in mind more than Google or Motorola. But I don't think this is enough that people will feel motivated to develop a lot for the Moto X (for the reasons already stated above).
Click to expand...
Click to collapse
I have mine rooted and running Xposed with GravityBox and it works just as well as my original version Moto X did. I don't see the need for a custom rom, though I might try CM once there is a version for it.
Well as someone said, even the Moto 2013 had very very little development. But I would love to see a Custom ROM based on Moto's software itself. Cleaning out small bugs and unrequired services and maybe add couple of extra features.
I just received my Moto X (2nd gen).... I should have looked on the forums first... Without custom ROMS - I'll most likely just send it back to Moto...
I like the options the custom roms bring. I like choosing the toggles I desire in the window shade, custom themes, etc... Not being able to do those things... Meh - I have been tweaking my experience since 2007. I don't like the idea of just running a plain Jane rom.. This sucks as I really like the hardware... Almost enough that I would spend the time trying to learn to make a custom rom myself... But, I can't expend the time to learn, debug, etc... Sadly, I'm too busy with my day job...
As long as you're not on Verizon, Xposed modules should be able to give you all the customization choices you'd ever need.
I was hoping for custom Lollipop roms and Xposed won't work on Android 5.0 (and, it is uncertain if it will ever work on Lollipop).....
Never seen such a low dev contribution for any of my Android devices. My moto is pretty much perfect, but there's always ways to improve it. Why is there so little activity on it? Are we just waiting for Cm or PA to support it?
Was it really necessary to start another 1 of these threads.. There's already 2 that are active.. Read and post there
We are waiting for you to make us a ROM! Get cracking!
CWick4141 said:
Was it really necessary to start another 1 of these threads.. There's already 2 that are active.. Read and post there
Click to expand...
Click to collapse
Where?
And I'd love to, but I'm useless
Serious answer.
The Moto X has a lot of proprietary code for things like moto assist, active display, and the low power ir sensors. Additionally, there is no official source for lollipop like there is for Nexus devices...making it difficult for ROM builders.
The Moto X (2013) had very little in the terms custom ROMs as well. There will probably be a few ROMs in the future, but don't expect a ROM community like there are for Nexus devices, it just won't happen.
That being said, the Moto X is damn near perfect straight out of the box. I am an avid flasher, and I really don't feel like I'm missing out on much with the stock experience on the Moto X.
Center status bar clock/date is really the only thing I miss.. Possibly a kernel but stock with trickster seem to be working well
I'd love to get Xposed modules back for some minor cosmetic and functional tweaking, but otherwise this phone is close to perfect already.
chrisrozon said:
I'd love to get Xposed modules back for some minor cosmetic and functional tweaking, but otherwise this phone is close to perfect already.
Click to expand...
Click to collapse
Yeah, Xposed is a total game changer. That's one of the main reasons I'm keeping both my X and N5 on KK for the foreseeable future.
mprziv said:
Serious answer.
The Moto X has a lot of proprietary code for things like moto assist, active display, and the low power ir sensors.
Click to expand...
Click to collapse
People say that, but this is often true of Samsung devices and devices like the HTC One, but they still get development.
People also say that because the Moto X is such a close to stock device, there is a lack of interest in developing for it. I don't believe that either, because if that were true there would be no development for Nexus devices and, of course, those are the devices that get the most development.
mprziv said:
Additionally, there is no official source for lollipop like there is for Nexus devices...making it difficult for ROM builders.
Click to expand...
Click to collapse
I think this, in fact, is probably the one and only reason there is no development for Moto X devices. I don't know that much about what is needed to make a ROM, and someone can correct me if I'm wrong, but without the source for proprietary drivers for various hardware components in a device, you're kind of stuck.
What puzzles me is that Motorola promoted the "Pure Edition" as an unlocked edition of the 2nd Gen Moto X. But if they're not going to provide the source code needed for development, why did they bother? It's like a developers edition of a phone that's only good for non-developers.
I also don't really see how it benefits Motorola to block development. It's a relatively small portion of users who even bother with custom ROMs. But is the most enthusiastic portion of users, who can really help spread the buzz for a device. In addtion, custom ROMs often come up with smart ideas that later get adopted in stock ROMs. So their is a potential symbiotic relationship there. As it is, it just seems like Motorola alienates some of the biggest Android fans.
mprziv said:
That being said, the Moto X is damn near perfect straight out of the box. I am an avid flasher, and I really don't feel like I'm missing out on much with the stock experience on the Moto X.
Click to expand...
Click to collapse
Yeah, it's nice. With Xposed, as others say, it can be modified in similar ways as ROMs. But there are still some Motorola built in elements that I'd rather not see, so it's not pure stock, as is often suggested.
My real hangup is that ROMs, like Cyanogen, are much better at stripping out some of the most egregious tracking code. Providing privacy enhancements (again not just at the user feature level, but in the underlying code). And generally eliminating things that don't serve users, but do serve marketers/manufacturers. That's more important to me than a lot of the user interface modifications found in ROMs.
So with Xposed you can get an user interface experience that's pretty similar to a lot of ROMs, but their are other benefits that may be missing.
If I could get an official version of Cyanogen for the 2nd Gen Moto X, it would be a near perfect device to me. As it is, I still hesitate. Of course, there's the extremely similar Nexus 6, but I'm not into that huge size.
cb474 said:
People say that, but this is often true of Samsung devices and devices like the HTC One, but they still get development.
People also say that because the Moto X is such a close to stock device, there is a lack of interest in developing for it. I don't believe that either, because if that were true there would be no development for Nexus devices and, of course, those are the devices that get the most development.
I think this, in fact, is probably the one and only reason there is no development for Moto X devices. I don't know that much about what is needed to make a ROM, and someone can correct me if I'm wrong, but without the source for proprietary drivers for various hardware components in a device, you're kind of stuck.
What puzzles me is that Motorola promoted the "Pure Edition" as an unlocked edition of the 2nd Gen Moto X. But if they're not going to provide the source code needed for development, why did they bother? It's like a developers edition of a phone that's only good for non-developers.
I also don't really see how it benefits Motorola to block development. It's a relatively small portion of users who even bother with custom ROMs. But is the most enthusiastic portion of users, who can really help spread the buzz for a device. In addtion, custom ROMs often come up with smart ideas that later get adopted in stock ROMs. So their is a potential symbiotic relationship there. As it is, it just seems like Motorola alienates some of the biggest Android fans.
Yeah, it's nice. With Xposed, as others say, it can be modified in similar ways as ROMs. But there are still some Motorola built in elements that I'd rather not see, so it's not pure stock, as is often suggested.
My real hangup is that ROMs, like Cyanogen, are much better at stripping out some of the most egregious tracking code. Providing privacy enhancements (again not just at the user feature level, but in the underlying code). And generally eliminating things that don't serve users, but do serve marketers/manufacturers. That's more important to me than a lot of the user interface modifications found in ROMs.
So with Xposed you can get an user interface experience that's pretty similar to a lot of ROMs, but their are other benefits that may be missing.
If I could get an official version of Cyanogen for the 2nd Gen Moto X, it would be a near perfect device to me. As it is, I still hesitate. Of course, there's the extremely similar Nexus 6, but I'm not into that huge size.
Click to expand...
Click to collapse
Samsung and HTC etc. devices get Dev because they are bloated with touchwiz/sense etc., there is not a lot to do on the moto x besides throw some aosp, or cm roms at it, but then you lose the "proprietary" features that the moto x has (which is its selling point, if you bought this phone not because of active display or moto voice then you really bought the wrong phone).
Not a lot of incentive for a Dev to work on the moto x, not much can be gain only loss....I.e. You goto cm or aosp you lose not gain...for the most part. Really not a lot of incentive to work on this phone. Sure there might eventually be a cm or even pa or aosp ROM but who really wants that over stock with xposed?
Sent from my XT1095 using Tapatalk
cb474 said:
People say that, but this is often true of Samsung devices and devices like the HTC One, but they still get development.
Click to expand...
Click to collapse
There is nothing similar to active display and touchless control on Samsung's touchwiz or HTC's sense.
dobbs3x said:
Samsung and HTC etc. devices get Dev because they are bloated with touchwiz/sense etc., there is not a lot to do on the moto x besides throw some aosp, or cm roms at it,...
Click to expand...
Click to collapse
As I said in the post to which you claim to be replying, if that were the reason not to develop for the Moto X, then there would also be no developement for Nexus devices, since they have no bloat and arrive pure stock. The point of custom roms, obviously, is not just to get rid of bloat, but to add lots of features that do not exist elsewhere. Indeed, some roms are made so that people can have an HTC Sense or Samsung Touchwiz type of experience on a non-HTC or non-Samsung phone. Roms are hardly all about returning phones to a stock experience. So I think that argument is obviously wrong to anyone who thinks about it for a minute.
Look at the OnePlus One. It ships with Cyanogen. Zero bloat, already has the most popular custom rom on it. If this argument had any merit, there would be no development for it. But in fact there is tons of development for it. Because it's a totally open device and OnePlus One encourages development.
dobbs3x said:
...but then you lose the "proprietary" features that the moto x has (which is its selling point, if you bought this phone not because of active display or moto voice then you really bought the wrong phone).
Click to expand...
Click to collapse
You wouldn't lose the proprietary features if Motorola released drivers necessary for them to work, as other cell phone manufacturers do, so this point begs the question (again, as I already said in the post you were supposedly responding to).
*
mprziv said:
There is nothing similar to active display and touchless control on Samsung's touchwiz or HTC's sense.
Click to expand...
Click to collapse
Samsung has their own weird hardware button layout, heart rate monitors, HTC has the oddball two lens camera in the M8. It doesn't matter what the feature is. All that matters is that there's some extra piece of hardware in there and it's going to need a driver and access to the hardware for developers to use it in a custom rom.
The difference, I believe, is that Samsung and HTC release the proprietary binaries and other source code, which makes it possible for developers to develop for their phones. Motorola, for whatever reason, has chosen not to do this. I think that is the only reason their is no development for the Moto X. So I think people are actually just misunderstanding what the problem is with development for the Moto X. (If some developer out their wants to chime in with more explanation of this, I'd be happy for some confirmation.)
All the other reasons people are repeating here are made up reasons that I think have nothing to do with how development actually happens. Repeating them, because someone else somewhere in the forum said it, does not make it true.
Motorola, it seems, just doesn't want people to develop for their devices and they prevent that by not releasing the binaries and source necessary to do so.
*
The point can even be taken another step. Because the hardware on the 1st and 2nd Gen Moto Xs is so nice and generally liked and because the 2nd Gen Moto X is in fact the basis for the Nexus 6 and extremely similar to it, I think that if the binaries and source code necessary were available, there would be a lot of development for the Moto X. So it has nothing to do with all the reasons people say about why there's no need to develop for the Moto X and everything, I believe, to do with Motorola blocking developers from developing for the Moto X.
Or maybe it's just the fact that it's a mediocre device that a lot of devs aren't going to purchase. I'm sending mine back after 4 days with it. Love the build quality, but I can't live with the mediocre screen, crappy camera and poor battery life.
Most devs, "dev" for popular devices and sadly, the moto x isn't one of them
I do not see the hate towards this device to be reasoned, at all. Battery (not so ****ty as I thought it would be, very similar to Nexus 5 so you can not linger on that )and camera (I also believe it to be better then Nexus 5's) are the payoffs of a great phone. What is wrong with the screen, NRG?
I had the first gen moto x, it has lots of development but they are all cm or aosp based Roms. Pretty much a dozen different Roms with either cm or aosp as the base. There is nothing special with them. Just someone is bored and wanted to try making a ROM. They bring nothing really useful to the device unless you really just like cm. Which you should of bought the one plus or a nexus. Trust me all the Roms developed for the first gen moto x are nothing crazy, just rehashed cm and aosp.
NRGZ28 said:
Or maybe it's just the fact that it's a mediocre device that a lot of devs aren't going to purchase. I'm sending mine back after 4 days with it. Love the build quality, but I can't live with the mediocre screen, crappy camera and poor battery life.
Most devs, "dev" for popular devices and sadly, the moto x isn't one of them
Click to expand...
Click to collapse
If you consider the X to be mediocre, I'd love to know what phone you think is high end. I burn through Android phones like they are candy, and to me, the X is hands down the best smartphone ever made. Sure there are phones with better screens, cameras, and battery life, but they all have other compromises, some that are far worse. The X's screen is only mediocre when side by side with a nicer one, the camera is more than sufficient, and my battery life has been amazing. There has never been an Android phone this mature and elegant, with performance to boot. The software is as close to perfect as you can get (talking KitKat here, I'm not sold on Lollipop), and the overall user experience is second to none, at least in my eyes. To each their own I suppose, but I just can't fathom how anybody can call the X a mediocre phone.
Why would you install a custom rom on the Moto X?
I think it is a compliment to the device there is no development and urgent need for different software. What is somebody going to improve software wise that isn't already present?
shadowspring said:
Why would you install a custom rom on the Moto X?
I think it is a compliment to the device there is no development and urgent need for different software. What is somebody going to improve software wise that isn't already present?
Click to expand...
Click to collapse
Exactly, its amazing. People buy a new Samsung , HTC or LG phone and immediately want to change everything on it. That doesn't say much for the original intent of the manufactures. With the Moto X line, most are completely satisfied with it right out of the box. Something those other phones can claim.
dobbs3x said:
Samsung and HTC etc. devices get Dev because they are bloated with touchwiz/sense etc., there is not a lot to do on the moto x besides throw some aosp, or cm roms at it, but then you lose the "proprietary" features that the moto x has (which is its selling point, if you bought this phone not because of active display or moto voice then you really bought the wrong phone).
Click to expand...
Click to collapse
Is that true ?
I was going to unlock bootloader and root this nice device in order to put some tweaks (DPI change, Apps Control, Ad blocker...), but if I lose the active display this is not going to be good...
I also would like to add that this phone is less famous than others blockbusters from HTC, LG or Samsung (at least in France). Developers seem to go to where there are many users for their ROMs, excluding Nexus' line. This and that Motorola doesn't release the binaries and source...
StiiLe said:
Is that true ?
I was going to unlock bootloader and root this nice device in order to put some tweaks (DPI change, Apps Control, Ad blocker...), but if I lose the active display this is not going to be good...
I also would like to add that this phone is less famous than others blockbusters from HTC, LG or Samsung (at least in France). Developers seem to go to where there are many users for their ROMs, excluding Nexus' line. This and that Motorola doesn't release the binaries and source...
Click to expand...
Click to collapse
You wont lose any features just from unlocking and rooting, only if you flash a custom ROM that doesn't have them built in.
As of every hour and every minute now we seeing new ROMs popping up for various devices now and but seems that the development for our ghost has come to end??
Well something requested by us is simply rejected by the senior members with all due respect.
For example:I recently demanded for a stock like Marshmallow based rom coming with all the special moto features like display,voice,etc.. but they rejected and recommended to try the cm 13 which loses all the Moto functionalities!?
Hence I finally put a request for one more time to build special type of ROMs for our moto devices just like the XOSP(Xperia open source project) and honourable name it as "MBOSP"(MotoBlur Open Source Project).
As much as i would love to have such rom, Moto X is 3 years a old device and I don't think anyone will work this much for an older device. I am using official CM13 by @Megatron007 and it is great. Maybe you should request the devs of existing roms to add Moto functionalities in their roms.
There can't be a Marshmallow stock rom, because there isn't a Marshmallow stock rom to start with.
There can be if built from aosp
LOL no
There can be atleast a stock like!
At this point I just want to have my verizon 1060 bootloader unlocked. I got it after it had been updated with no chance of putting cyanogen on it
I demand a working Nougat rom right now!
Those damn developers should do something to earn those salaries paid by XDA.
minimum a donation xD by users
"For example:I recently demanded for a stock like Marshmallow based rom..."
What are you paying?
I've been with my stock Droid Turbo since it released in October 2014; I'd like to upgrade to something newer, but nothing I've found has fit my requirements (big battery, <5.5" screen, non-glass back, headphone jack, no notch, Verizon compatible, preferably unlocked/unlockable). So far, my Turbo still does the job, so I've stuck with it; however, its battery is showing its age, and it hasn't gotten an update in quite some time. Obviously, I can replace the battery at some point, so that's not a problem; the issue of updates, on the other hand, is.
I've unlocked my phone long ago when Sunshine first released to root it, so that's not an issue. My issue is that this is my one and only phone, so I need it to be stable and I'm looking to have all of its features working. I know from browsing ROM threads in the past they've typically had issues with either stability or features not working, so I've been hesitant to jump ship from the stock ROM. I'm a security professional, though, so it bothers me how behind this phone is on security updates. I'd like to move beyond Marshmallow as well, but the security updates are my main concern.
So, with all that said, I'm looking to get some opinions from users of the Quark ROMS out there. As stated, stability and feature functionality are the most important things for me. Please let me know which ROM you would recommend for my situation, and why. I know the best solution would be to trial different ROMs myself and see which works best for me; but between work, family and kids, the time just isn't there to be without a phone I know I can rely on - so I'm seeking your advice.
Thanks in advance!
(If you've got any suggestions for a phone upgrade, feel free to chime in with those as well.)
I have been using NepoRood's AOKP ROM for about a year. It's great but since he broke the screen of his Turbo, he hasn't updated the ROM. I flash BHB27's kernel and hope the security updates in the kernel are enough.
lots of stable roms available with EVERYTHING working,
calsurferpunks LOS 14 is very stable and smooth
Viper OS is exceptionally smooth and fast, also very stable
RR 7.x i would not reccommend as it was a bit less stable than the above selections, but it has ALOT of features and is stable enough for a mention
i could not get AOSPExtended or mokee to work
didnt try CRDroid very long but seemed similar to RR 7.0
have not tried others yet, if i like a ROM upon trying it, i usually trial it for a month or more to get a good idea of the long term stability/usability of the ROM
This is not an endorsement of any ROMs. In the 3.5 years I owned three Quarks, I first used rooted stock Kitkat wth xposed/Gravity box, then Lollipop CM, then Resurrection Remix (both Marshmallow, then Nougat).
However, I keep a list of current ROMs for Quarks (Droid Turbo/Moto Turbo/Moto Maxx) and I read through all the ROM threads. I help when I can, when people have issues. So, I've seen a lot... The three ROMs I see people praise most often and seem to have less issues with are:
@bhb27 RR - Resurrection Remix (Nougat)
@calsurferpunk's LOS (Nougat) -- sort of a hybrid of RR and official LOS; it doesn't have the plethora of options RR has, but I never used all the options in RR. However, it does have LED notification and Moto apps Google Play permissions and a few others.
@NepoRood's AOKP ROM (Nougat) -- but now not updated as often as he owns another device.
Most of the other ROMs on the list are also fine. I am not criticizing them in any way. We appreciate all the ROMs this device has and all the hard maintainers do to help users. All the Nougat ROMs are compatible with ALL Quarks -- Droid Turbo/Moto Turbo/Moto Maxx. They're all the same phone (the way an LG G3 is an LG G3, no matter whether bought in UK or Canada. Some even have the exact same radio bands. Moto Maxx XT1250 = Droid Turbo XT1254, with same radio bands, same FCC ID. XT1250 runs on Verizon with a Verizon SIM card. BOTH the Moto Maxx XT1250 and Droid Turbo XT1254 were sold in the U.S. by different carriers, but they were the EXACT same phone. Point is, Motorola really messed things up by calling this phone different model names for different carriers/different parts of the world.
None of the LOS-based custom ROMs would be possible without @bhb27's kernel work, however. He not only maintains two ROMs, he also codes our "stock" LOS kernel, besides having an advanced standalone kernel and his TWRP work, plus apps like Turbo Toast.
OTHER
You don't say what carrier you are with. IF you are on Verizon with your Droid Turbo, and IF you want Verizon Volte, then you need @computerfreek274 stock-based Marshmallow ROM. It's the ONLY ROM that has VoLTE and Wi-Fi calling -- and only then for Verizon. Some Droid Turbo users on Verizon still use an LOS-based ROMs as they feel the many options those ROMs offer (like the nifty LED notification and security updates) are worth not having VoLTE. But others use this stock-based ROM because it's debloated Verizon firmware, has battery and speed tweaks, and they NEED Verizon VoLTE.
NOTE: No other Quarks have VoLTE and the Droid Turbo only has it on Verizon when using stock firmware or stock-based ROM. This ROM is only compatible with Droid Turbo (or Moto Maxx XT1250, since they're really the same device).
Click the link and look through the list.
Thank you all for your responses! They more or less affirm what I thought, but it is good to hear it directly rather than what I've gathered from bits and pieces in other threads. I'll have to give them some more consideration.
Chazz, I am on Verizon, and I would prefer to keep VoLTE, if I could. I didn't think any ROMs other than the stock-based one had gotten VoLTE working though; I knew there had been some development on it, but last I had seen, that development seemed to have stopped.
Does computerfreek's ROM get the new security patches baked into it, or is it on the same patch level as stock-from-Verizon? If it's at the same level, it wouldn't really cut it for me as those security patches are my main concern. I've considered it for the features before, but I decided that wasn't worth the wipe and resetting/reinstalling everything on my phone.
bigdav1178 said:
Does computerfreek's ROM get the new security patches baked into it, or is it on the same patch level as stock-from-Verizon? If it's at the same level, it wouldn't really cut it for me as those security patches are my main concern. I've considered it for the features before, but I decided that wasn't worth the wipe and resetting/reinstalling everything on my phone.
Click to expand...
Click to collapse
No, this is where the LOS ROMs excel, especially the ones where the maintainers are active and keep the ROMs updated. They have the latest Android security patches.
This is from that CF ROM thread a few months ago, and I can't find any information to refute it:
17th September 2017, 09:51 PM
Spott07 said:
No. This ROM is based on stock from Nov 2016, and does not have any security updates after that date.
Even the latest revision, ver 1.0.8, of CF's ROM was released a few months ago, before the Blueborne vulnerability set was announced, and so obviously could not contain any applicable updates.
Click to expand...
Click to collapse
Whereas you can see the update date in the title of these two threads:
ROM update! RR-N-v5.8.5-20180414-quark-Mod.zip
[ROM][Quarks][LOS 14.1 Unofficial][7.1.x][2018-04-17]
Both have April 2018 security patches.