Database Develop

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

On-contract AT&T/Verizon Nexus 6 will come with bloatware?

And here's why I think this.
Currently, AT&T sells the 2nd generation Moto X (the non Pure Edition phone) for $99 on contract. But, on their store web page it markets itself very interestingly/devilishly:
Key features include:
5.2” HD display
Qualcomm® Snapdragon™ 801 quad-core processor
13MP camera with 4K capture
Pure Android™ experience
Moto voice control
Did you catch that? Yes, folks, this is what they are going to do with the Nexus 6 as well. If they can just throw around the label "Pure Android Experience", that means they think we are stupid and they will go ahead and put the pre-loaded bloatware, locked bootloader, carrier start up splash screen, etc.
They will most likely have a Nexus 6 Pure Edition that sells only on the Google Play store for $624529789498249824
The title of "Nexus" no longer means anything.

Not to say it's impossible, but I don't think that the use of the phrase "Pure Android Experience" means anything significant. It's just something that Moto uses to sell the Moto E/G/X with a minimal skin.

gtalum said:
Not to say it's impossible, but I don't think that the use of the phrase "Pure Android Experience" means anything significant. It's just something that Moto uses to sell the Moto E/G/X with a minimal skin.
Click to expand...
Click to collapse
Minimal != Pure

gtalum said:
Not to say it's impossible, but I don't think that the use of the phrase "Pure Android Experience" means anything significant. It's just something that Moto uses to sell the Moto E/G/X with a minimal skin.
Click to expand...
Click to collapse
They are trying to capitalize on the appeal of the vanilla android experience of the Nexus brand as well as the ignorance of those who have never owned a Nexus phone before. Some call this "false advertising".

Technically it does have a pure Android experience since Google forced Moto to use a more pure experience. That said since this is a carrier oriented device the carriers can do whatever they want with it.
Nexus devices have and always had been free from Carrier BS. The only exception was the Verizon Galaxy Nexus when Verizon wanted to control the device updates not Google. Considering the release for this is wide it means that they have to comply with Google's wishes if they want to carry the devices and sell them.
That said however since the Droid Turbo is also coming out as well as a GSM variant for AT&T it would be no surprise if AT&T and Verizon will be pushing for sales on these devices and not the Nexus 6 since they have more control over these devices and can cut off support at any time creating planned obsolescence. One of the main things the Nexus is free from.
The Nexus will be sold from all carriers free of BS if they comply to Google's contract on the matter. That said they will not be forced to upsell them. They will be more likely to upsell any other device out there aside from the Nexus just so they can still have control. If Verizon or AT&T try to add anything to the Nexus devices that tarnish its design then Google has all the power to cut the contract and remove sale of the devices through AT&T and Verizon.

Dr Faustus said:
Technically it does have a pure Android experience since Google forced Moto to use a more pure experience. That said since this is a carrier oriented device the carriers can do whatever they want with it.
Nexus devices have and always had been free from Carrier BS. The only exception was the Verizon Galaxy Nexus when Verizon wanted to control the device updates not Google. Considering the release for this is wide it means that they have to comply with Google's wishes if they want to carry the devices and sell them.
That said however since the Droid Turbo is also coming out as well as a GSM variant for AT&T it would be no surprise if AT&T and Verizon will be pushing for sales on these devices and not the Nexus 6 since they have more control over these devices and can cut off support at any time creating planned obsolescence. One of the main things the Nexus is free from.
The Nexus will be sold from all carriers free of BS if they comply to Google's contract on the matter. That said they will not be forced to upsell them. They will be more likely to upsell any other device out there aside from the Nexus just so they can still have control. If Verizon or AT&T try to add anything to the Nexus devices that tarnish its design then Google has all the power to cut the contract and remove sale of the devices through AT&T and Verizon.
Click to expand...
Click to collapse
I seriously hope you are right, but I just can't see AT&T giving up that kind of control. I can imagine, however, that this will go down just like the Moto X where there will be the Google Play/Pure Edition version of the phone and also the carrier version of the phone. Shame on AT&T trying to pawn off their bloatware-infested Moto X as "Pure Android experience".

phalanx_x said:
I seriously hope you are right, but I just can't see AT&T giving up that kind of control. I can imagine, however, that this will go down just like the Moto X where there will be the Google Play/Pure Edition version of the phone and also the carrier version of the phone. Shame on AT&T trying to pawn off their bloatware-infested Moto X as "Pure Android experience".
Click to expand...
Click to collapse
Again, "Pure Android Experience" Applies to OS level, not so much the apps.
For example, The past few MOTO DROID devices were Pure Android OS, but still had bloat. Same for Moto X devices too. Pure Android Experience is a selling point to those who want to have a less lag ridden experience carriers still have control on what goes onto the OS with apps.
A fine example of this is T-Mobile HTC G2, the upgrade from the original consumer android phone the G1, had a locked bootloader and T-Mobile apps loaded onbard. The overall experience offered a Pure Android Experience, but still was carrier controlled with app bloat and a locked down OS. It was not a comparable Nexus Pure experience.
To contrast to the Nexus 4 and 5 on T-Mobile, bootloaders were easily unlockable and there was no bloat. They were no different from the Google Play sold Nexus devices. In the press release for the N6 it was said that the device will be sold on all major carriers (if they meet compliance with Google's intent with the devices). That means if they fail meeting the compliance of Google's intent with selling the N6 through them, they cannot sell the device through the retailer.
In a sense, it seems Google is treating their Nexus series like Apple treats their iPhones, which in reality is a very good thing since Apple has an iron grip over iPhone's control over carrier BS. I am looking forward to this change if this is the case, we all should.

Dr Faustus said:
Again, "Pure Android Experience" Applies to OS level, not so much the apps.
For example, The past few MOTO DROID devices were Pure Android OS, but still had bloat. Same for Moto X devices too. Pure Android Experience is a selling point to those who want to have a less lag ridden experience carriers still have control on what goes onto the OS with apps.
A fine example of this is T-Mobile HTC G2, the upgrade from the original consumer android phone the G1, had a locked bootloader and T-Mobile apps loaded onbard. The overall experience offered a Pure Android Experience, but still was carrier controlled with app bloat and a locked down OS. It was not a comparable Nexus Pure experience.
To contrast to the Nexus 4 and 5 on T-Mobile, bootloaders were easily unlockable and there was no bloat. They were no different from the Google Play sold Nexus devices. In the press release for the N6 it was said that the device will be sold on all major carriers (if they meet compliance with Google's intent with the devices). That means if they fail meeting the compliance of Google's intent with selling the N6 through them, they cannot sell the device through the retailer.
In a sense, it seems Google is treating their Nexus series like Apple treats their iPhones, which in reality is a very good thing since Apple has an iron grip over iPhone's control over carrier BS. I am looking forward to this change if this is the case, we all should.
Click to expand...
Click to collapse
Doesn't Google own the Android OS?? The way I see it, Google has full rights to claim their devices are 100% "Pure Android". Anyone else... not so much.
But as for iPhones, the carriers locked all their phones... doesn't the very purpose of the Nexus phone get thrown under the bus if carriers were to lock the Nexus 6?

phalanx_x said:
And here's why I think this.
Currently, AT&T sells the 2nd generation Moto X on contract (the non Pure Edition phone) for $99 on contract. But, on their store web page it markets itself very interestingly/devilishly:
Key features include:
5.2” HD display
Qualcomm® Snapdragon™ 801 quad-core processor
13MP camera with 4K capture
Pure Android™ experience
Moto voice control
Did you catch that? Yes, folks, this is what they are going to do with the Nexus 6 as well. If they can just throw around the label "Pure Android Experience", that means they think we are stupid and they will go ahead and put the pre-loaded bloatware, locked bootloader, carrier start up splash screen, etc.
They will most likely have a Nexus 6 Pure Edition that sells only on the Google Play store for $624529789498249824
The title of "Nexus" no longer means anything.
Click to expand...
Click to collapse
Really please put down the bong ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 01:01 PM ---------- Previous post was at 12:53 PM ----------
phalanx_x said:
Doesn't Google own the Android OS?? The way I see it, Google has full rights to claim their devices are 100% "Pure Android". Anyone else... not so much.
But as for iPhones, the carriers locked all their phones... doesn't the very purpose of the Nexus phone get thrown under the bus if carriers were to lock the Nexus 6?
Click to expand...
Click to collapse
Android is built using the Linux kernel and is open source ....that's the only reason that oems have to post up the source code etc ... but they don't have to unlock bootloaders etc and the drivers and other parts of the os like sense can be closed source ...

nexus6R3plicant said:
Android is built using the Linux kernel and is open source ....that's the only reason that oems have to post up the source code etc ... but they don't have to unlock bootloaders etc and the drivers and other parts of the os like sense can be closed source ...
Click to expand...
Click to collapse
Oh.. ok... what would happen to me, as a independent Android OS developer, if I came up with something and then called it "Android Lollipop 5.0.1" ?

phalanx_x said:
Oh.. ok... what would happen to me, as a independent Android OS developer, if I came up with something and then called it "Android Lollipop 5.0.1" ?
Click to expand...
Click to collapse
Nothing as long as you follow gpl .... you see how many versions of Linux are out there.... like cyanogen mod they only got a cease and desist from Google back in the begins for putting gapps in their roms ...which is why you have to flash the rom and then gapps when flashing aosp roms ....it's only the google apps that are closed source
But you could get a letter from their lawyer if they have copy write any of the Lollipop name etc

nexus6R3plicant said:
Nothing as long as you follow gpl .... you see how many versions of Linux are out there.... like cyanogen mod they only got a cease and desist from Google back in the begins for putting gapps in their roms ...which is why you have to flash the rom and then gapps when flashing aosp roms ....it's only the google apps that are closed source
But you could get a letter from their lawyer if they have copy write any of the Lollipop name etc
Click to expand...
Click to collapse
So... Google owns the Lollipop 5.0 Android.. got it. So, why are carriers saying their version of Kitkat/Lollipop is "Pure"?? How can they get away with that?

phalanx_x said:
So... Google owns the Lollipop 5.0 Android.. got it. So, why are carriers saying their version of Kitkat/Lollipop is "Pure"?? How can they get away with that?
Click to expand...
Click to collapse
Motorola is the only one saying pure .... but is the closest to true aosp . Motorola puts very little on top of android and makes many optimizations to make it run better etc
Sony is kind of close also ... htc has sense , samsung is touchwiz , lg has their own ... its just a user interface on top of android and its the reason samsung devices always lag .

Pretty sure all the n6 devices will have the same hardware and have an unlockable BL, also since the hardware is all the same the code names should be the same, and as such the factory images from google should be flashable. Now if ATT goes the Verizon way and handles the n6 like the Gnex, than thats gonna be an issue.

The hardware is the same. So, even if the carriers bloat them up, you can simply flash the OEM images that Google releases. Now, if the carriers are allowed to lock the bootloaders, that may be a problem. I'm hoping that Google at least keeps that from happening., or someone like Geohot finds a way to break it. We won't know for sure though until the carrier versions are available and someone tries to unlock one of each.

Moto is basically AOSP so calling it pure isn't a longshot

According to an Ars Technica interview, all Nexus 6 devices (even the Google Play version) will automatically install carrier bloatware during setup. The phone will detect which SIM card you're using, and download the apps that carrier wants on the phone. It's called "Play Auto Install."
At first this sounded appalling, but I realized it's actually a good thing. Thanks to this feature, carriers will no longer install apps in the System partition. You can uninstall their apps just like apps from the Play Store.

NOTashwin said:
According to an Ars Technica interview, all Nexus 6 devices (even the Google Play version) will automatically install carrier bloatware during setup. The phone will detect which SIM card you're using, and download the apps that carrier wants on the phone. It's called "Play Auto Install."
At first this sounded appalling, but I realized it's actually a good thing. Thanks to this feature, carriers will no longer install apps in the System partition. You can uninstall their apps just like apps from the Play Store.
Click to expand...
Click to collapse
If this is true, all you have to do it start the setup with a sim then insert it after setup.

NOTashwin said:
According to an Ars Technica interview, all Nexus 6 devices (even the Google Play version) will automatically install carrier bloatware during setup. The phone will detect which SIM card you're using, and download the apps that carrier wants on the phone. It's called "Play Auto Install."
At first this sounded appalling, but I realized it's actually a good thing. Thanks to this feature, carriers will no longer install apps in the System partition. You can uninstall their apps just like apps from the Play Store.
Click to expand...
Click to collapse
This is perfect. Fastboot, FTW!

Here's the except from Ars:
Ars: How much control do carriers have over the Nexus devices? People think back to the Verizon Galaxy Nexus, and it got slower updates.
Burke: I don't think we're going to do that. There is carrier testing that has to happen, you can't get away from that, but we're trying to have our updates be frequent. I think the carriers are learning and realizing that's a feature they want. I think these are getting more efficient, and we're getting better at it. Play Auto Installs are also really important.
Ars: Play Auto Installs? What?
Burke: So the idea is as part of setup, Verizon might have some apps that you want like an app that tells you how much you used that month in terms of charges. There's legitimate use cases where you want apps, but you also want those apps to be treated like any other app. What happens now is when you've got a Verizon SIM in the device, it actually installs Verizon apps as part of the setup flow, and then you can remove them if you want as part of the Play Infrastructure. And Verizon can update it.
Cohen: They're not on the system partition.
Ars: Oh ok, so you can remove them?
Cohen: Yes.
Click to expand...
Click to collapse
If you could avoid installing bloatware by inserting the SIM card after setup is over, that would be great — but I don't think Verizon would let that fly. Verizon would probably want their apps to be installed anytime their SIM card is used. It's not 100% clear what will happen until someone tries it.

WIFI calling implementation ?

Any one know how Tmobile plans on implementing wifi calling for the nexus 6 been an stock android rom? you guys think all AOSP roms would be able to get wifi calling once this patch goes live?

traicer said:
Any one know how Tmobile plans on implementing wifi calling for the nexus 6 been an stock android rom? you guys think all AOSP roms would be able to get wifi calling once this patch goes live?
Click to expand...
Click to collapse
Honestly, I expect Google to implement it just like Apple does. Develop the feature directly into the device and firmware and then allow minor updates to work with other carriers such as US Cellular and Sprint. If they don't bake it into "AOSP" then I doubt third party AOSP built devices would support it.

altimax98 said:
Honestly, I expect Google to implement it just like Apple does. Develop the feature directly into the device and firmware and then allow minor updates to work with other carriers such as US Cellular and Sprint. If they don't bake it into "AOSP" then I doubt third party AOSP built devices would support it.
Click to expand...
Click to collapse
yes, i'm hoping its an android thing and not a T-Mobile thing.

Can We Get a Carrier Specific Rom List Please

Here is the reasoning behind my request.
I am on Tmob and have a N6. I was fine stock rooted on 5.0 then 5.0.1. Then I decided to try a few roms. One that said it was for ALL carriers, didn't allow me to get calls unless I was only in 3g.
T-mobile is the ONLY one using a 47m ROM. All others are at 47i, why is there a difference? The radios most likely. I am 95r and 98r doesn't work on TMobile very well.
Can we get a Thread for EACH Carrier? They aren't all the same, at least from my experience. Sprint, VZW are different and have problems. I hear VZW users need to use 98r for "best results"
Go ahead, blast away. Just waiting for the "senior ops" to go to town on this one!

I'm on vzw and every ROM I've tried is fine. Have you updated to the latest image from google. Or are you still on 5.0.1

navyvet420 said:
Here is the reasoning behind my request.
I am on Tmob and have a N6. I was fine stock rooted on 5.0 then 5.0.1. Then I decided to try a few roms. One that said it was for ALL carriers, didn't allow me to get calls unless I was only in 3g.
T-mobile is the ONLY one using a 47m ROM. All others are at 47i, why is there a difference? The radios most likely. I am 95r and 98r doesn't work on TMobile very well.
Can we get a Thread for EACH Carrier? They aren't all the same, at least from my experience. Sprint, VZW are different and have problems. I hear VZW users need to use 98r for "best results"
Go ahead, blast away. Just waiting for the "senior ops" to go to town on this one!
Click to expand...
Click to collapse
With many phones, Samsung in particular - there are massive hardware differences that require several separate forums to manage.
With the nexus 6, the hardware is identical on all of them.
There are 2 specific builds that are slightly different and as you mentioned, they are M and I.
What we think is (but unproven) that M is for T-Mobile USA and I is for Australia. We have no concrete proof of that. Nor am I sure what the differences are. If you're using stock-based ROMs, try to stick to M builds.
As for AOSP, I'm not sure anyone knows what the difference is for T-mo. Maybe one day we'll find out.

rootSU said:
With many phones, Samsung in particular - there are massive hardware differences that require several separate forums to manage.
With the nexus 6, the hardware is identical on all of them.
There are 2 specific builds that are slightly different and as you mentioned, they are M and I.
What we think is (but unproven) that M is for T-Mobile USA and I is for Australia. We have no concrete proof of that. Nor am I sure what the differences are. If you're using stock-based ROMs, try to stick to M builds.
As for AOSP, I'm not sure anyone knows what the difference is for T-mo. Maybe one day we'll find out.
Click to expand...
Click to collapse
Thank You for the Reply.. I would agree with the thinking about M. Like I stated a non-M build killed the incoming calls unless my phone was on 3g with Enhanced 4g unchecked.
I was just asking for a Carrier Specific Rom thread thats all.

toknitup420 said:
I'm on vzw and every ROM I've tried is fine. Have you updated to the latest image from google. Or are you still on 5.0.1
Click to expand...
Click to collapse
Im on a 5.1 with 95r and 47M is my Build (nocturnal rom) its a Tmobile N6.. All other roms killed incoming calls unless I was stock rooted. CleanRom 2.0 and 2.1 with either 98r or 95r had same results. I like @scrosler roms, but can't live without getting business calls.

navyvet420 said:
Thank You for the Reply.. I would agree with the thinking about M. Like I stated a non-M build killed the incoming calls unless my phone was on 3g with Enhanced 4g unchecked.
I was just asking for a Carrier Specific Rom thread thats all.
Click to expand...
Click to collapse
Yeah. I think its a good idea to have a thread that lists all t-mo compatible ROMs, but first we need to learn what the actual difference is. Perhaps its just a RIL or something. In which case, there may just be a flashable zip required.
I just think we need to know more at this stage.
@efrant, do you know the differences? @simms22?

the aosp roms were missing code that made the tmobile devices not receive calls on lte, that has been fixed and should be in all roms that have been recently updated. i use terminus, which includes the code, so tmobile users get calls on lte, and volte is working. besides that issue that has been fixed, all carriers will work on any aosp rom. theres no such thing as a carrier specific nexus rom.

simms22 said:
the aosp roms were missing code that made the tmobile devices not receive calls on lte, that has been fixed and should be in all roms that have been recently updated. i use terminus, which includes the code, so tmobile users get calls on lte, and volte is working. besides that issue that has been fixed, all carriers will work on any aosp rom. theres no such thing as a carrier specific nexus rom.
Click to expand...
Click to collapse
Was the code added to aosp by Google? Or is it a community commit?

rootSU said:
Was the code added to aosp by Google? Or is it a community commit?
Click to expand...
Click to collapse
AOSP contains only Android OS nothing proprietary (proprietaries are included as a standalone) but when Google provided the binaries--proprietary libraries, applications were missing which caused VoLTE not to work properly. Myself and Sykopompos worked on the blobs and having VoLTE working, they were pulled from the factory image / deodexed OTA.

zephiK said:
AOSP contains only Android OS nothing proprietary (proprietaries are included as a standalone) but when Google provided the binaries--proprietary libraries, applications were missing which caused VoLTE not to work properly. Myself and Sykopompos worked on the blobs and having VoLTE working, they were pulled from the factory image / deodexed OTA.
Click to expand...
Click to collapse
this

[Q] Verizon Nexus 6

This may be a dumb question and i feel like a complete noob asking it but........... .....
I bought a Nexus 6 from Moto and had it activated on VZW before VZW
had it as a phone (which may not matter).
I want to ROM my phone, and i am use to seeing a separate thread
for each Networks' phone (att, vzw, tmo ...etc)
So essentially what do i need to know about ROMing
the nexus 6 activated on VZW?
(Also i know I'm late to the ROMing game on this phone
but i guess its better late than never)
Thanks!

All nexus 6s are the same. You can flash any rom your heart desires

I do believe that some carriers have made specific ROMs for the N6 because of small tailor made features, T-Mobile for example baked on so that nexus 6 phones on their network could turn on Wi-Fi Calling
Sent from my Nexus 6 using XDA Free mobile app

dynamo147 said:
I do believe that some carriers have made specific ROMs for the N6 because of small tailor made features, T-Mobile for example baked on so that nexus 6 phones on their network could turn on Wi-Fi Calling
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Can i use a rom that says Wifi calling specific?
specifically Chroma?
(any roms you guys recommend that
are customizable?)

Kreateablaze said:
All nexus 6s are the same. You can flash any rom your heart desires
Click to expand...
Click to collapse
Literally any of em? the guy below said some are targeted at certain ones, can i still flash em?
BlissPop or Chroma?
thanks

Yes any of them. Chroma will work, and if you wanna use blisspop that will work too.

Kreateablaze said:
Yes any of them. Chroma will work, and if you wanna use blisspop that will work too.
Click to expand...
Click to collapse
Do you recommend any as far as customization?

That's up to what you want in a rom. Look at the features of each one and decide for yourself on what looks like you would want.

Kreateablaze said:
That's up to what you want in a rom. Look at the features of each one and decide for yourself on what looks like you would want.
Click to expand...
Click to collapse
yeah ill stop with dumb questions.
Thanks!