Database Develop

Development shouldn't factor in smartphone decision making, should it?

So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.

Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
Click to expand...
Click to collapse
That's a very narrow perspective. There are lots of reasons one might want to flash a ROM or kernel; the "one size fits all" mentality of other vendors such as Apple and Microsoft need not apply here. Custom ROMs open the door to different features that the OEM might not have considered or wanted to spend time on, and allow the creativity of the general public to enhance the phone in ways that are unique to them or only fits a certain niche that wouldn't be profitable for a big company to try and cater to. It certainly isn't just about "fixing issues".
Though custom ROMs certainly aren't the only feature I would look for in a phone, I might hesitate before buying a phone that little support or, even worse, a locked bootloader with no current workaround or hack for the simple reason that even if there's nothing I'm interested in today, there might be something cool that I want to try out tomorrow.

MaxCarnage said:
there might be something cool that I want to try out tomorrow.
Click to expand...
Click to collapse
If you had bought something like the Moto X one year ago, what feature made by the ROM developers on the Nexus 4 would you really want to try out?

I've been debating this myself. I have a Nexus 5 now that I'm testing with TMO prepaid for a month. So far, the phone is really nice and as you said, the level of development is astounding. BUT, I have to leave VZW in order to keep the phone. That's very hard to do when I get a hefty discount on the service and still have unlimited data. I can get LTE pretty much everywhere I go. With TMO, I'm lucky to get Edge data in some places or even a signal at all inside buildings.
I love the look and feel of the X. It's is a great piece of hardware and with the Dev edition, I could stay on VZW. I also like the fact that it runs basically stock Android along with additions that are actually useful and well done. The dev community is very limited though and will most likely stay that way. Moto was quick to get the 4.4 update out but it remains to be seen if that pace will continue. You would hope so but nothing is guaranteed. The X2 may be out next year putting the update schedule for the current model on the back burner.
I had the original Nexus One and the Galaxy Nexus. I've always been a diehard AOSP guy. Every phone I've owned in between has always been on a custom AOSP based ROM in order to get close to that Nexus experience. I'm attracted to custom ROMs not because they fix bugs, but because they allow me to always stay on a current version of Android (no waiting for carrier updates) and add some nice features to the basic AOSP design. Custom kernels can also improve overall performance and battery life even if you decide to stay stock otherwise. The Nexus line will always have the edge in this regard.
I wanted to be blown away with the N5 and content with TMO but I'm second guessing my decision each day.....
darkgoon3r96 said:
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Click to expand...
Click to collapse

I am running the N5 stock and have no reason to root or flash a custom Rom. Never thought I would say that about my phone but I am actually content with the N5 the way it is. There are some cool features that devs add in but then you get sucked into this never ending flashing frenzy which I have been in for years.
It is good to actually enjoy the phone now and keep the software on it for more then a few days. lol
Anyway, the screen alone on the N5 is enough for what I consider a big step up from the Moto X. I have friends with Moto X's which I actually recommended to them since they are on Verizon and it was being offered for free on contract. I do think it is a great phone with some great features. Not enough there to sway my decision to get one over a N5 though.
I do applaud Motorola for their unbelievable quick update and I bet we start to see some other maunfacturers start stepping up their game as well. We have seen this recently with HTC also.
The question to ask yourself is what is important to you. Another good thing with the Moto X is it generally stocks with the stock Android feel so it almost resembles Nexus software.
Bottom line, when I turn on my N5 after playing with the Moto X, the Moto X does not in any way make me want to buy one for myself.
---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------
fallingd0wn said:
I've been debating this myself. I have a Nexus 5 now that I'm testing with TMO prepaid for a month. So far, the phone is really nice and as you said, the level of development is astounding. BUT, I have to leave VZW in order to keep the phone. That's very hard to do when I get a hefty discount on the service and still have unlimited data. I can get LTE pretty much everywhere I go. With TMO, I'm lucky to get Edge data in some places or even a signal at all inside buildings.
I love the look and feel of the X. It's is a great piece of hardware and with the Dev edition, I could stay on VZW. I also like the fact that it runs basically stock Android along with additions that are actually useful and well done. The dev community is very limited though and will most likely stay that way. Moto was quick to get the 4.4 update out but it remains to be seen if that pace will continue. You would hope so but nothing is guaranteed. The X2 may be out next year putting the update schedule for the current model on the back burner.
I had the original Nexus One and the Galaxy Nexus. I've always been a diehard AOSP guy. Every phone I've owned in between has always been on a custom AOSP based ROM in order to get close to that Nexus experience. I'm attracted to custom ROMs not because they fix bugs, but because they allow me to always stay on a current version of Android (no waiting for carrier updates) and add some nice features to the basic AOSP design. Custom kernels can also improve overall performance and battery life even if you decide to stay stock otherwise. The Nexus line will always have the edge in this regard.
I wanted to be blown away with the N5 and content with TMO but I'm second guessing my decision each day.....
Click to expand...
Click to collapse
Why not go to a MVNO that uses AT&T towers? Would still be much chepaer then Verizon and they offer much better coverage then T-Mo.

[email protected] said:
I am running the N5 stock and have no reason to root or flash a custom Rom. Never thought I would say that about my phone but I am actually content with the N5 the way it is. There are some cool features that devs add in but then you get sucked into this never ending flashing frenzy which I have been in for years.
Click to expand...
Click to collapse
Don't you want to improve the Audio and the battery life by trying out the kernels and the mods made here?
Anyway, the screen alone on the N5 is enough for what I consider a big step up from the Moto X.
Click to expand...
Click to collapse
I assume you mean resolution? I was under the impression that 1080p and 720p are not that different under daily usage?

It all comes down to your habits. I love flashing new ROM's, I sometimes try multiple ROM's per week. So for me, development means a lot. It's why I switched from the S4 to the N5. The S4 just received 4.3 and was locked down by Knox. Plus, with the N5 being an unlocked phone, you can flash any ROM on any carrier, so you won't ever have to drool over another carrier's ROM.

mjs2011 said:
It all comes down to your habits. I love flashing new ROM's, I sometimes try multiple ROM's per week. So for me, development means a lot. It's why I switched from the S4 to the N5. The S4 just received 4.3 and was locked down by Knox. Plus, with the N5 being an unlocked phone, you can flash any ROM on any carrier, so you won't ever have to drool over another carrier's ROM.
Click to expand...
Click to collapse
I also flash a ton of ROMs every week and also used to enjoy it, but I am getting tired of it now... I want to live life more than flash ROMs (if that makes sense)

darkgoon3r96 said:
If you had bought something like the Moto X one year ago, what feature made by the ROM developers on the Nexus 4 would you really want to try out?
Click to expand...
Click to collapse
Anything and everything. The top reason I don't even consider not getting a Nexus device anymore is the development scene. Look, you're viewing the huge development community on the Nexus line as people who are "fixing" a "broken" stock image. That's not really true. The stock image is perfectly fine. The developers are merely making things that they deem better than how stock handled it. For instance, a developer might think that the on-screen buttons are too large on stock, taking up way too much screen real-estate. They would then develop a way to remove it, but still be able to navigate. They might make something like PIE controls. Now, I may agree that the buttons really are too large, but I like the nav bar. So I might just resize it, instead of working around it.
I guess the point I'm making is, all of those modifications you see to "improve" the stock image are there to "improve" it, but what counts as an "improvement" is completely subjective. There are different people in the world with vastly differentiating opinions about things, so they will make something to improve something else as they see fit. The development sections here on XDA are merely huge repositories of any modification that anyone who was willing to make, made. Looking at them all as collectively-required flashable improvements isn't how it should be viewed. That's the beauty of having a large development community. You can pick and choose, depending on your personal opinions, which modifications are improvements and flash them. Another way to think of it is cookie-cutter vs modular. Do you want a phone that appeals the masses,;a one-size fits all, or a phone that is completely customizable?

darkgoon3r96 said:
Don't you want to improve the Audio and the battery life by trying out the kernels and the mods made here?
Click to expand...
Click to collapse
Battery life has been great on stock for me. Absolutley no complaints here. I have ran so many custom kernels on prior phones and never saw a large boost in battery from them. Lots of times it would actually be worse.
The speaker volume can definitley use a boost and the camera needs some fixing. I know there is some dev work for both of these issues but I am going to hang a little and see if Google fixes it. If not, I might think about rooting solely for those 2 things. If Google fixes it, absolutley no reason for me to root this time around.
Anyway, as a prior flashoholic there is no better phone then a Nexus for people who like to flash Roms and like every feature on the sun. No other phones custom Roms work as good as they do on a Nexus.

Development is like the first determining factor for me when buying phones.

darkgoon3r96 said:
I assume you mean resolution? I was under the impression that 1080p and 720p are not that different under daily usage?
Click to expand...
Click to collapse
Screen size. A 5" screen starts the sweet spot for a device that uses on-screen buttons. I always felt shorted on prior 4.7" screens with on screen buttons. Like there wasn't enough viewing real estate. Sure you can remove the on-screen buttons but then you would need something that always to longer to activate then the actual buttons being present.
I also think the quality and colors of the N5 screen are just gorgous.

darkgoon3r96 said:
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Click to expand...
Click to collapse
I just got rid of my moto x for the N5 for this very reason. The moto x is a great device and probably the best carrier controlled device to date.
That being said, it drove me nuts to be locked down with a locked bootloader and no development. Knowing the n5 is open and has all the Dev support means I have control over MY phone, not AT&T and not Motorola.
After dealing with the locked down s4, I promised myself I would never get another device without an unlockable bootloader. I caved when the moto x came out and as I said it's one amazing device but at the end of the day, I'll be sticking with nexus devices from here on out.
To me it's not worth giving up that freedom but for you it may not matter.
Sent from my Nexus 5

Development totally cones into it for me. One of the biggest considerations.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

brooksyx said:
Development is like the first determining factor for me when buying phones.
Click to expand...
Click to collapse
rootSU said:
Development totally cones into it for me. One of the biggest considerations.
Click to expand...
Click to collapse
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
capathy21 said:
That being said, it drove me nuts to be locked down with a locked bootloader and no development. Knowing the n5 is open and has all the Dev support means I have control over MY phone, not AT&T and not Motorola.
Sent from my Nexus 5
Click to expand...
Click to collapse
If I do get the Moto X, then I will get the Developer Unlocked model.

brooksyx said:
Development is like the first determining factor for me when buying phones.
Click to expand...
Click to collapse
Same here, after my first Nexus phone, I could never go back to a phone that didn't have a strong dev. community behind it. For me; tablets and phones are as much about the journey of playing with ROM/kernel/mods as they are a communication device.

darkgoon3r96 said:
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
If I do get the Moto X, then I will get the Developer Unlocked model.
Click to expand...
Click to collapse
No stock rom mod can touch the stability and features of cyanogenmod. It is the only way to do anroid. In fact I prefer iOS over stock android. But CM is awesome.

brooksyx said:
No stock rom mod can touch the stability and features of cyanogenmod. It is the only way to do anroid. In fact I prefer iOS over stock android. But CM is awesome.
Click to expand...
Click to collapse
To be honest, CM's future plans SERIOUSLY excite me.. Like that recent conversation feature

CyanogenMod, AOKP, AOSPA support, along with great kernel devs. The Nexus 5 is essentially guaranteed support for these things, and these are things I like.

darkgoon3r96 said:
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
Click to expand...
Click to collapse
Who said anything about roms or features? Its all about kernels.
But if you look at ROMS like PAC, you'll see what features true roms can offer over xposed
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

[Q] Is the dev community for this device very small?

I just got a Developers Edition Moto X and I love the device, but coming from the HTC One, it has come as a shock to me how different each forum is.
I'm very surprised we haven't got a stock ROM for the 4.4.2 update that is flashable with TWRP/CWM.
Is it because of the locked bootloaders? Did the device not sell well?

From what I've read here is that most people are happy with the stock ROM with root. As the ROM is so close to Vanilla Android, there is not a lot of development in ROMs for this phone. Also most want to keep Active Display and/or the Touchless Controls. I just got an OTA for 4.2.2 on my retail unlocked Moto X (also referred to as the T-Mobile version).
As far as the boot loader goes, to my knowledge only the Verizon retail and AT&T retail Moto X's are locked. All the other models can be unlocked by requesting the unlock code from Motorola. And I think the phone sold well. It definitely could have used a lot more marketing help to compete with the larger manufacturers.

sucks that mine is locked

zewone said:
I just got a Developers Edition Moto X and I love the device, but coming from the HTC One, it has come as a shock to me how different each forum is.
I'm very surprised we haven't got a stock ROM for the 4.4.2 update that is flashable with TWRP/CWM.
Is it because of the locked bootloaders? Did the device not sell well?
Click to expand...
Click to collapse
I find that stock rooted with Xposed and the Gravity Box module are all I need ... I too got the dev edition as well, if for nothing else rooting after OTAs we be less of a hassle
Sent from my Nexus 7 using Tapatalk

Well we do have a stock flashable 4.4.2 ROM there's actually 2 one for the 1052 and kangakat ,both are for the gsm version and I do believe they will also work on the CDMA variant If you swap out the build prop, we also have custom Roms, slimkat, cm11, gummy.pacman, Liquid smooth and beanstalk
Sent on my Gummy running Lenoto X

Hikikomori-Otaku said:
From what I've read here is that most people are happy with the stock ROM with root. As the ROM is so close to Vanilla Android, there is not a lot of development in ROMs for this phone. Also most want to keep Active Display and/or the Touchless Controls. I just got an OTA for 4.2.2 on my retail unlocked Moto X (also referred to as the T-Mobile version).
Click to expand...
Click to collapse
I completely agree with this. ROMs like CyanogenMod or AOKP aren't likely to support Active Displays, or "Okay Google Now" voice commands, or flicking the wrist to unlock the camera.
Also, I think the fact that there's a big split between the Dev Editions and Moto-Maker hurts things more. A lot of people of Moto-Maker, and they're very limited on what they can do with their phones compared to Dev Edition. Then you add in the fact that there are GSM/Verizon/Sprint versions all mixed AND the phone hasn't sold well, and things are very limited.

zewone said:
I just got a Developers Edition Moto X and I love the device, but coming from the HTC One, it has come as a shock to me how different each forum is.
I'm very surprised we haven't got a stock ROM for the 4.4.2 update that is flashable with TWRP/CWM.
Is it because of the locked bootloaders? Did the device not sell well?
Click to expand...
Click to collapse
not to worry. even though a lot are pleased with stock out of the box, there will be ROMs. we can still tweak, improve, and slim it down some. i officially ordered mine yesterday and it is the DE/T-Mob variant XT1053.
just like others have said, the device hasn't been advertised as much as it should be, esp with the deals that keep going on with it. if it would stay at $300 for 16gb/$350 for 32gb, they would sell like hot cakes.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
DogzOfWar said:
I completely agree with this. ROMs like CyanogenMod or AOKP aren't likely to support Active Displays, or "Okay Google Now" voice commands, or flicking the wrist to unlock the camera.
Also, I think the fact that there's a big split between the Dev Editions and Moto-Maker hurts things more. A lot of people of Moto-Maker, and they're very limited on what they can do with their phones compared to Dev Edition. Then you add in the fact that there are GSM/Verizon/Sprint versions all mixed AND the phone hasn't sold well, and things are very limited.
Click to expand...
Click to collapse
the GSM unlocked on Moto-Maker is the exact same as the Dev Edition. i think this is confusing a lot of people.

Custom roms ?

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

[Q] Third party roms? CM, AOKP, Slim, etc?

Hello all,
I am looking to pick up a Moto X (xt1095) to replace my xt1053. I am a little dismayed however at the lack of availability of roms for the device.
I am used to having CM or Slim or at least gravitybox running, and it looks like none of these are working yet for this phone. Is this simply because of the recent release of Lollipop and the scarcity of the Moto X or is there some underlying problem?
Basically, is there hope for the future?

Probably has more to do with most devs not touching Moto because of how developer hostile they were years ago. Also I suspect most are waiting to see if the Lenovo takeover pushes moto into a more "old moto" stance on devs again.

I was wondering the same, the phone has so much potential, why no development at all?

Thanks for the responses. I was hoping I suppose to at least see CM and some other mainstream developers already onboard, but I guess it's just because 3rd party devs haven't built around lollipop yet.
Same problem with Xposed.

Pan Skrzetuski said:
Hello all,
I am looking to pick up a Moto X (xt1095) to replace my xt1053. I am a little dismayed however at the lack of availability of roms for the device.
I am used to having CM or Slim or at least gravitybox running, and it looks like none of these are working yet for this phone. Is this simply because of the recent release of Lollipop and the scarcity of the Moto X or is there some underlying problem?
Basically, is there hope for the future?
Click to expand...
Click to collapse
Chris123NT said:
Probably has more to do with most devs not touching Moto because of how developer hostile they were years ago. Also I suspect most are waiting to see if the Lenovo takeover pushes moto into a more "old moto" stance on devs again.
Click to expand...
Click to collapse
There's a short thread in the General section with a developer looking for some files so he can start to build CM11 and 12. Several days old.

I got my pure edition on the way, and I also noticed the lack of ROMs. - I currently have an N5, my girlfriend really likes it so I'm going to give it to her for Christmas, was not really looking to upgrade, but oh well.
I really do hope the scene for this phone picks up a bit, otherwise I might just sell it and go back to N5... Unless the phone is so amazing that it will keep me from the ROM scene, but I don't know... I'm a flashaholic.
On the same subject - My friend got the same phone, but he mentioned needing to contact Motorola to get a bootloader unlock code so he could root it, is that a necessary step, or can that be avoided?
I understand the above step voids warranty, could also be why people are staying away from cooking ROMs for this.

Shemploo said:
I got my pure edition on the way, and I also noticed the lack of ROMs. - I currently have an N5, my girlfriend really likes it so I'm going to give it to her for Christmas, was not really looking to upgrade, but oh well.
I really do hope the scene for this phone picks up a bit, otherwise I might just sell it and go back to N5... Unless the phone is so amazing that it will keep me from the ROM scene, but I don't know... I'm a flashaholic.
On the same subject - My friend got the same phone, but he mentioned needing to contact Motorola to get a bootloader unlock code so he could root it, is that a necessary step, or can that be avoided?
I understand the above step voids warranty, could also be why people are staying away from cooking ROMs for this.
Click to expand...
Click to collapse
You just have to go to their website( https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a ) and follow their instructions to unlock their phone.. Contacting them is not necessary. Voiding the warranty has been the case for multiple phones, however it hasn't stopped devs before.. Doubt that is the case

I bought the pure edition yesterday, I did my research and figured it would be better than a nexus 6 (way to big for me) and bought it. I assumed there was plenty of Dev work, I mean its a near stock phone and will likely outsell the nexus 6, but there's not even an official build of CM!!! Even the gnex is getting cm12. I just don't understand it. Z

IRX120 said:
I bought the pure edition yesterday, I did my research and figured it would be better than a nexus 6 (way to big for me) and bought it. I assumed there was plenty of Dev work, I mean its a near stock phone and will likely outsell the nexus 6, but there's not even an official build of CM!!! Even the gnex is getting cm12. I just don't understand it. Z
Click to expand...
Click to collapse
That's funny cause CM is my least favorite of ROMs, they always seem to break things when they make changes, and ROMs based on CM are always left in the dark trying to catch up, fix whatever broke as result.
If there's not much being developed for this, I suppose I'd probably go back to 4.4 and work around it with xposed.

I think more development will come in time but I think most are waiting for stable 5.0 first. I look forward to gravitybox but personally I have never been as happy on any rom as I am AOSP(ish) and don't see the need with a phone like this to install any roms. It was more necessary back "in the day" to get rid of crapware and overbloated UI's (*cough* Touchwiz *cough*). Phones like the Nexus series, GPE editions, and the Moto X's have made me personally re-evaluate my interest in full ROM's.

If you guys were around when the original Moto x came out, then you'd remember that it also had a lack of roms and dev action when it launched... However now it's getting cm 12 like no one's business... I think it's just a matter of time before the roms start rolling in

Why the lack of custom roms and mods?

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.