Related
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
Is it just me or does it seem like a lot, not all, but a lot of the devs have moved on to other devices?
If so, it makes me sad to see that the first real Google phone was so quickly abandoned.
kungpowchicken said:
Is it just me or does it seem like a lot, not all, but a lot of the devs have moved on to other devices?
If so, it makes me sad to see that the first real Google phone was so quickly abandoned.
Click to expand...
Click to collapse
How exactly are you defining this as "the first real google phone?"
Do the nexus devices not count?
kungpowchicken said:
Is it just me or does it seem like a lot, not all, but a lot of the devs have moved on to other devices?
If so, it makes me sad to see that the first real Google phone was so quickly abandoned.
Click to expand...
Click to collapse
The other issue is custom features. Moto X users love active display and touchless control, and other than that it is AOSP. there is very little reason for development besides debloated / odexed roms, of which there are plenty
kungpowchicken said:
Is it just me or does it seem like a lot, not all, but a lot of the devs have moved on to other devices?
If so, it makes me sad to see that the first real Google phone was so quickly abandoned.
Click to expand...
Click to collapse
This is the first phone I felt didn't need a custom ROM. I just installed xposed and gravity box and it's golden. Love this phone.
Unfortunately, the stock rom and features being so good has doomed development for this phone IMO. It's a bit expected since this is what I've wanted since my earliest days with with Android. Moto did a great job with it.
There isn't much demand for custom ROMs, especially since it's already running nearly stock (with useful enhancements that would be lost). If you want the miscellaneous customization options included in most ROMS, just install Xposed Framework and grab one of the various modules available (gravity box seems to be the most popular)
anotherfiz said:
The other issue is custom features. Moto X users love active display and touchless control, and other than that it is AOSP. there is very little reason for development besides debloated / odexed roms, of which there are plenty
Click to expand...
Click to collapse
I have to agree there. I unlocked my Moto X but only to root it and put Xposed framework on it. After that I installed Gravity Box to customize it how I wanted.
CyanogenMod 11 is official for it but its not posted here. Dhacker forgot to make a Moto X thread. Its under msm8960dt instead of xt1060 etc.. as they unified all the Moto X builds: http://download.cyanogenmod.com/?device=moto_msm8960dt
The things I gave up using CM 11 when I tried it that brought me back was lack of NFC HCE support (Google Wallet Tap and Pay wont work), Touchless Control, and no Active Display. Granted ACDisplay app has made great strides and, once they get the gravity wake features enabled, I would not mind using that instead of AD. GW issue is something though that bothers me.
I think the only time I will consider a rom for this phone is once Motorola stops updating it and a new version of Android comes out that CyanogenMod is building from.
I too have to agree with what most people have been saying about the X. All of my previous Android phones were Samsung phones. I was a serious flashaholic with them. AOKP was my favorite on my S3. I hated touchjizz with a passion. Now, with the X, I'm completely satisfied with running stock. I never thought that would happen. All I have that's custom on my X is Faux's kernel. And, I'm happy as a clam.
Sent from my XT1053 using XDA Premium 4 mobile app
Yup.... This really isn't a "flashing"phone. Its an enjoy stock and the moto features and use gravity box to customize phone.
Very few seem to be using the ROMs that are available.... And as said, its cause you lose all the custom moto features, which are a big reason people bought the phone to begin with.
Also, the dangers of downgrading have played a part in people not wanting to mess with it too much I think.
I loved my x, and still recommend it to anyone I know looking for a phone....but yeah, I passed it to my wife for an n5....cause I was bored. Lol
Maybe you should try a similar move? Unless you're content. Cause unless the moto features make it to custom ROMs.....development won't pick up anytime soon. Maybe when updates end, then custom ROMs may pick up.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I'll simply add that my 2 cents echo's those above - the phone does what I want it to do, and well. Its already running the up to date OS, which on prior devices was my main reason for flashing in the first place.
ROM development should pick up after our phones are dropped from OTAs. For the time being, stock does everything you need and it's crazy stable.
I bought this phone so I didn't have to rely on development.
Xposed framework seems to be all I need on this phone at least until it starts falling behind on future ota's as I plan on keeping it for a while.
Xposed Framework is more than enough to fill any custom rom desires.
Moto X is pratically AOSP with lots of really useful features like Active Display that I can't imagine living without now.
As much as I love AOSP and have loved using custom roms, Moto did too good of a job to warrant the constant flashing of nightlies, restoring backups, getting all my apps back, testing builds for bugs etc. I do still enjoy trying out different roms from time to time just for fun.
With all that said, I'm enjoying the stock based roms, and the stock rom + xposed. My plan is to continue using stock based roms and every month or so try a custom kernel, see what combination gives me the best battery life and smoothness, enjoy having a bug free phone, and taunt my friends with the awesome moto goodies (they really seem to envy touchless control, as they should!)
Honestly, once we stop receiving OTA's, I'll start looking for a new device. But, damn, it's going to take something special to force me to make a change.. A DE Moto X with unlimited data on Verizon, what the hell more could a guy want?!
Sent from my XT1060 using Tapatalk
DonKilluminati23 said:
As much as I love AOSP and have loved using custom roms, Moto did too good of a job to warrant the constant flashing of nightlies, restoring backups, getting all my apps back, testing builds for bugs etc. I do still enjoy trying out different roms from time to time just for fun.
With all that said, I'm enjoying the stock based roms, and the stock rom + xposed. My plan is to continue using stock based roms and every month or so try a custom kernel, see what combination gives me the best battery life and smoothness, enjoy having a bug free phone, and taunt my friends with the awesome moto goodies (they really seem to envy touchless control, as they should!)
Honestly, once we stop receiving OTA's, I'll start looking for a new device. But, damn, it's going to take something special to force me to make a change.. A DE Moto X with unlimited data on Verizon, what the hell more could a guy want?!
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Its crazy how vzw makes you lose your unlimited data if you upgrade. At&t doesn't. But yeah I was going to get the gs5 but changed my mind. I'm going to hold off to see what the moto x+1 is going to be like. I'm pretty interested in the iPhone 6 and see what it has to offer also. But going to keep my x till later on in the year.
MOTO X SLAPPED
[email protected] said:
Its crazy how vzw makes you lose your unlimited data if you upgrade. At&t doesn't. But yeah I was going to get the gs5 but changed my mind. I'm going to hold off to see what the moto x+1 is going to be like. I'm pretty interested in the iPhone 6 and see what it has to offer also. But going to keep my x till later on in the year.
MOTO X SLAPPED
Click to expand...
Click to collapse
I actually just used all the upgrades on my family plan through best buy and kept the unlimited data, some glitch in the best buy system, used mine on an iPhone 5S and sold it. But yeah it sucks you have to jump through hoops and get lucky to keep unlimited with Verizon.
Sent from my XT1060 using Tapatalk
i dont agree. development is not dead. if you look at the newest custom roms then you see 99.9% everything works. there is nearly every custom rom available.
there is just not too much kernel developers. it is ok because they also dont develop their kernels like before, they just import a kernel source from vendor and patch it with experimental features and you can not modify them without pay their apps. just remember siyah kernel and you know what i mean...
Its not like it needs it a whole lot. Its already running just about stock, already on a new build of KitKat, and has a lot of features you can't add in with another ROM like touch less control. We have xposed modules so what more can you ask for?
Sent from my XT1056 using Tapatalk
I havent found one ROM that doesn't have an issue albeit small issues but issues all the same. Why flash a ROM that takes away touch less control and notifications and in my opinion doesn't run any better than stock., just to have small issues. There is just no benefit that I could find. The best ROM I tried was gummy but the stock email app continuously tried to load emails killing the battery.
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
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.
Hey guys, I'm pretty sure no one has seen me in the G Flex section. I did work for the M8, G3 etc back in the day. I just picked up a G Flex the other day with T-Mobile excited to put Lollipop on it. Came home and searched the threads to see there isn't lollipop for it nor is there any AOSP ROMs for it. I understand the issues behind it but I just wanted to say these issues doesn't prevent ASOP running on our G Flex. There's still possibilities. I came from the ZTE Zmax, and we had 1 dev working on our phone and got CM12.1 up and running with full stability in a month. I read somewhere that LG confirmed that the G Flex will NOT get lollipop because of some issues that was causing it to be buggy. LG basically stalled development on the G Flex until the 18 months that Google gave as an requirement for Software updates was over. The 18 month period for the G Flex ended back in May. So LG basically used that as an excuse to not update our phone, which is very stupid and it sucks but we have developers in this community that are smarter than LG Devs. We don't need a kernel source to build a functional kernel, even though a source would help tremendously. The ZTE Zmax, ZTE Awe ($30 phone), LG Tribue ($40 Phone) are all running CM12.1 with no kernel source and locked Bootloaders. For sensor and Audio issues you could simply TRY and use libs from other devices that compare like the G2. That's what the dev for the ZTE Zmax did. I see development started for lollipop but ended months ago. I also see a couple people working on CM11 and others quietly working on their own CM12 build. I'm not here to criticize, because I know this kind of stuff isn't easy. I'm just simply giving advice on something that may or may not have been tried yet. It's been almost a year since lollipop launched and you would expect a Flagship device to have lollipop or at least an AOSP ROM by now. Android M is being launched in a few months. Let's get this project back up and running and don't stop until its finished! We have plenty of donators including me. If help is needed ask other experienced Devs, CM Devs, even Devs on the Android Forums. This phone has way too much potential to just forget about.
I'm already accepting that we may not get anything and gotten used to a tweaked stock rom. There's a reason cheaper phones have lollipop already, they're going to have larger user bases by default. There is really no reason to pick up a flex even under an upgrade deal when there are plenty of competing phones that already have thriving communities, and I wish I did more research before I got mine. So really it comes down to someone only picking it up to get something different and even hindered.
That said, if some crazy dev does decide to pick the phone I'll be pleasantly surprised but preaching like this forum has been for weeks now isn't going to do anything when we have no devs actively working or even looking at us. I'm really hoping I get proven wrong and I'm definitely ready to throw some money at a reputable dev but seriously now, we don't even have stable cm11 ports and people are hoping for lollipop.
RushNY said:
I'm already accepting that we may not get anything and gotten used to a tweaked stock rom. There's a reason cheaper phones have lollipop already, they're going to have larger user bases by default. There is really no reason to pick up a flex even under an upgrade deal when there are plenty of competing phones that already have thriving communities, and I wish I did more research before I got mine. So really it comes down to someone only picking it up to get something different and even hindered.
That said, if some crazy dev does decide to pick the phone I'll be pleasantly surprised but preaching like this forum has been for weeks now isn't going to do anything when we have no devs actively working or even looking at us. I'm really hoping I get proven wrong and I'm definitely ready to throw some money at a reputable dev but seriously now, we don't even have stable cm11 ports and people are hoping for lollipop.
Click to expand...
Click to collapse
That's the problem, that fact that Lollipop is almost a year old and we don't even have 4.4.4 KitKat. We're about 2 years behind. This is why I said, lets go around and recruit. There are some Devs that don't even need the device in hand to build. They build and use testers. It seems like when there are kernel related issues Devs give up because they have little to no kernel knowledge. There's ways around that. Like I said, the CM11 port may not be stable but its still silently being worked on, just not finished in the timeframe people expect. And I've seen a couple people quietly working on their own CM12 builds. CM12 is already booting, its just in the same condition as CM11, which no one figured out how to fix yet, which is Sound, Bluetooth etc. I believe this device will get Lollipop soon, but only if people are eager and motivated to get the job done.
Sent from my LG-D959 using XDA Free mobile app
Just want to say that im finished with the Flex. Just Sold it and bought an Huawei Mate 7... and it is just awsome FU LG! Never again!
mckoffly said:
Just want to say that im finished with the Flex. Just Sold it and bought an Huawei Mate 7... and it is just awsome FU LG! Never again!
Click to expand...
Click to collapse
I have my Huawei Mate 2 with lollipop. It goes for 2 days with heavy use when it had Android 4 so I'll have to see what it will do now. The reason I put it down was because the camera sucked but with the update it seems to work fine. I love the LG form factor with the power and volume buttons and even the gui is cool but I'll try the Mate 2 and see. Mate 2 has a brighter screen, but the lg has wifi calling so lots of pluses and minuses. My fried got the Mate 7. Awesome phone but he was used to the long batter of the Mate 2 so returned it.
You guys MIGHT wanna check out playfulgod's CM11 thread, all the new development from the past month has been going on there. We now have sound working!!!
The d959
Does anyone know if the latest cm11 build with sound and data for the d959 will work? Saw the multiple .zip files but none for 959 in the main thread(cm11)
Read! Reply over there BTW, more likely to get help. And he's gonna build for d959 when data works on lswhateveritscalled. Sound works on all.
I know we've all heard it before. I ditched this phone to basically get lollipop. But after a few weeks I realized what I'd been hearing since launch. I don't hold this screen right up in my face. I don't care about pixels. What I do care about? The awesome size and battery life. Mine never stutters. Forget lollipop. I'm fine with the flex the way she is. I would like to see more development. But if we get it we do and if we don't we don't. I still have an awesome and powerful phone and cm12.1 would run awesome.
wcr84 said:
I know we've all heard it before. I ditched this phone to basically get lollipop. But after a few weeks I realized what I'd been hearing since launch. I don't hold this screen right up in my face. I don't care about pixels. What I do care about? The awesome size and battery life. Mine never stutters. Forget lollipop. I'm fine with the flex the way she is. I would like to see more development. But if we get it we do and if we don't we don't. I still have an awesome and powerful phone and cm12.1 would run awesome.
Click to expand...
Click to collapse
http://www.phonearena.com/news/Comp...ow-leaks-includes-Samsung-Sony-and-LG_id74400
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
/me lurks
This thread is a good initiative...flex forums have been so dead over the months, it pains me to see such a great phone relegated to the grave...here to help..can donate and test