yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] twatts723:
Yeah, that's kind of the same way I did it. Once unroofed, the OTA was offered through system update section of settings menu. I'm not saying the different builds are carrier matched, but it sure seems everyone on a T-Mobile phone gets the M build, and I think Verizon phones get E. And D and I are maybe everyone else..? I mean, I know everyone keeps saying every nexus phone is identical, but it sure seems like we're gonna have to get some kind of different build when we get our WiFi calling enabled, unless all the other phones are gonna just have a menu for it that doesn't do anything... right?
[Nexus 6  General] BigDig:
Peca, v APN settings, kudeto e by default IP6, smeni go na IP4, napravi save I probvai. IP6 poniakoga se ebava pri slab signal...
[Nexus 6  General] Pecata:
Blagodarq, shte optiam, misleh si da probvam mejdu drugoto...shte vidq dali shte go napravi sled kato go smenq....
[Nexus 6  General] Jsunn:
Full system image for "M"

Hi All,

So I am trying to keep up with all of the different factory images. Is the "M" version for T-mo the only one that came as a partial update or did "D" and "I" come out like "M"?

Has anyone done a full comparison for the differences between the builds?

Thanks,

Jason
[Nexus 6  General] xxsanioutlawxx:
On T-Mobile, just got the M firmware last night after clearing data and force closing "Google Services Framework". About damn time!

Edit: went from 5.0.1 to "M"... Guessing it's a T-Mobile ROM from talks on XDA...
[Nexus 6  General] psrobinson:
That worked for me too

I did the clear data and force close of GSF and after a couple of tries that worked great. I was getting pretty tired of waiting.
[Nexus 6  General] :
I'm going to disagree only to the point that Tmob is the ONLY carrier with a 47M designation for the Nexus 6.. All others are on 47i. WHY?

They aren't ALL the same roms from Googs. VZW is different. So is Sprint.

The OTAs are fd up and googs know this.
[Nexus 6  General] tylercarter:
Any of these builds will work with any nexus 6. So tell my why its a tmo build.
[Nexus 6  General] stevessvt:
I know my 611 calls wouldnt go through on D or E, but works fine on M.
[Nexus 6  General] yankeesfan714:
Maybe M is only for tmobile to fix the duplicate SMS problem?
[Nexus 6  General] stylz3:
I just received my notification. T-mobile nexus 6 64gb in long Island, NY
[Nexus 6  General] NastyNeil:
I sideloaded 5.1M yesterday and it is running great. Only one issue I ran into, that I hope is not persistent, is I got a whole slew of texts from yesterday, this morning. They all flooded in at once. Sounded like I hit the jackpot on the slots. Anyone else experience this?
[Nexus 6  General] masterxchief:
I have had it happen a couple of times now. The phone stops receiving text messages until I reboot then everything starts flooding in. The only reason I even noticed is because I couldn't get my 2 factor auth code to login to gmail.
[Nexus 6  General] NastyNeil:
Are you on T-Mobile as well?

---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------

I had been on 5.1D but flashed back to 5.0.1 then sideloaded 5.1M. Never had this happen on D. Only issue I had on D was the first day I had it T-Mobile had some SMS/MMS issues. Hope it doesn't become a persistent thing.
[Nexus 6  General] jcarlm:
I'm on D build and 611 works just fine for me.
[Nexus 6  General] stevessvt:
On T-Mobile? Mine would immediately hang up after dialing 611, every time.
[Nexus 6  General] dave2metz:
Quick question fellas....I am currently running the M build, but I was wondering if the L build has a different radio? Thanks for the help
[Nexus 6  General] xdatastic:
It's an i not an L.

Same radio too.
[Nexus 6  General] jcarlm:
Yes on T-Mobile.
[Nexus 6  General] PunishedSnake:
Cuz only the n6 with a tmo Sim got the ota for M.

Verizon came with E

I is for everyone else
[Nexus 6  General] badpanda:
I never got a ota M build update from T-Mobile to this date...
[Nexus 6  General] music_ismath:
This is happening to me as well (tmob + LMY47D)

Did you notice any other issues? Did anything improve dramatically by switching to M?

I'm seeing much better reception in my area, assuming it's because I can get band 12 now. So I'm just going to stick with D until everything settles down, unless there's a big reason not to...
[Nexus 6  General] SFVDan:
Ok, I finally could stand the suspense no longer and my latent desire to have the M build overcame my patience. This was, as advertised, easy peasy! Except for having to find the latest Mac version of adb. Who knew you needed 1.0.32 to do the sideload!

Learn sumptin' every day, I guess!

#happyasaclam
[Nexus 6  General] yankeesfan714:
Did you try deleting data from google framework services?
[Nexus 6  General] stevessvt:
This was the only obvious problem and fix that I saw. Seems to be working well on M.
[Nexus 6  General] stylz3:
M seems to be the best option here. I would highly recommend flashing this version of 5.1 as I haven't experienced any of the double text messages or unexpected hang ups with phone calls that many others experienced on D & E
[Nexus 6  General] papeshfoo:
I got the OTA last night, now I'm noticing that my emails aren't coming in unless I manually refresh inside the gmail app. No clue if its affecting my texts or not, but its pissing me off. I've rebooted twice and its still not fixed.

Sent from my Nexus 6
[Nexus 6  General] bouyark:
Same issue with emails

You're not alone. I am having the same issue as well after receiving the OTA two days ago.

I've cleared data on my GMAIL accounts, deleted both accounts and re-installed them and rebooted on numerous occasions.

The problem still exist.
[Nexus 6  General] Pecata:
Do you have this issue while on Wi-Fi or on LTE?
[Nexus 6  General] NastyNeil:
Did you clear Google services framework first to force the OTA? I've heard of that causing problems with receiving emails.
[Nexus 6  General] papeshfoo:
Both, and yes I cleared the data to force it.
[Nexus 6  General] bouyark:
I did clear Google Services framework to force the update.

If I am on WiFi or LTE, the not receivers email occurs.

Edit, my phone re-boited by itself, I am now receiving emai notifications.

I am not sure, if there is any connection.
[Nexus 6  General] Ingenium13:
That's why. Clearing data messes up push notifications. Google has said not to do this to try to get an OTA.

Sent from my Nexus 6
[Nexus 6  General] Knight-Rider:
Anyone having issues with making calls on new 5.1 update from T-Mobile? When I make calls the screen goes black and I can't wake up the phone, nothing at all. I've rebooted and that didn't seem to work, anyone else getting this?
[Nexus 6  General] xdatastic:
Your screen protector is blocking the proximity sensor. Top left of the speaker.
[Nexus 6  General] Knight-Rider:
What? Are you serious? It wasn't happening before, I have a tempered glass protector.
[Nexus 6  General] xdatastic:
Yep, there were some sensor updates, made it more sensitive to being covered by the protector. Get one that doesn't cover the sensor.

I had same issue and cut my cheap plastic one away and now its all good.
[Nexus 6  General] Knight-Rider:
Thanks for the heads up just bought the phone a few days ago and I get an update thinking it broke my phone lol. Thanks again!
[Nexus 6  General] Pecata:
Opitah i tova i na rabota kudeto LTE nqma stabilen signal pak mi napravi sushtiq nomer. Neznam kakvo drugo moga da probvam...osven da izklucha VoLTE nacqlo za da ne pravi takiva nomera. Neznam Band 12 kato doide tuk moje da ne pravi taka veche-znam li i az...blagodarq vse pak.
[Nexus 6  General] efrant:
[MENTION=4240132]BigDig[/MENTION] [MENTION=2253720]Pecata[/MENTION]

Please post in English or add an English translation to your posts. Any further non-English post will be deleted.
[Nexus 6  General] Pecata:
Sorry. Here is what was said:

I have been having issues with the dialer when LTE signal is weak, where if I attempt to make a call the dialer just says Dialing and it never completes the call. If I attempt to end it-it never hangs up until I reboot my phone. This happens ever since the 5.1 update. I have attempted all the builds and I am currently on the 47M and I still have the issue with T-mobile. Sometimes it happens on H as well if VoLTE is eanbled and the signal is weak.

What BigDig was suggesting is to try and select in the APN settings IPv4 instead of IPv6 and try it this way-I did and I just had another Dialer freeze at work.

I am turining off VoLTE until T-mobile fixes it in my area...I am not sure if we need another software update to address this issue or it is on the T-mobile's end.

Thanks once again and sorry for posting on another language-I will make sure I post in English from now on.
[Nexus 6  General] robertc88:
Got the update today so rocking 5.1 now. I'll need to give it a few days for impressions but the N6 seems very smooth with it so far.
[Nexus 6  General] DesignGrits:
Actually I work at a high level for a major carrier in the US, Google sends the builds to the carrier and the carrier then modifies the builds and pushes them out in batches. Part of my job at work is managing deliverables for device updates which includes the Nexus 6.

Unless you bought it direct from Moto or Google, which not everyone does.
[Nexus 6  General] jcarlm:
Then tell us why Google has not release the factory image for M? Or has anyone figure this out yet?
[Nexus 6  General] :
No other carrier has a M build. This fixed something that was broken in the previous builds, otherwise why push this build out, while the rest of the world gets 47i genius?

You should have been able to figure that one out. WTF. These devs think us out here are studpid and don't do research. Man I tell you, no wonder why people lose respect for devs sooner or later, they whine when they don't get a thanks, after begging for it in the Post 1, 2, 3, 4 and 5 just because. LOL

Seriously, you guys do great work, but when I person makes a factual statement, do your fn homework!

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM ----------

Exactly.. If the DEVs looked at the Google page for the builds, they'll find NO M build there.. WHY??

https://developers.google.com/android/nexus/images

Theres the link Devs.. No do any of you see a M build anywhere? NO!!

M is a Tmobile Build. maybe it works on other phones. Yippie. But the Other roms Fd up Tmobs ability to receive calls on anything other than 3g...

I don't know.. Maybe I am just a stupid flasher who doesn't know what he's doing. Or maybe I did my homework, unlike the devs in this case!
[Nexus 6  General] jcarlm:
I'm on D build and everything works as should on T-Mobile.
[Nexus 6  General] Circaflex:
of course it would, why wouldnt it? Everyone needs to realize there are no carrier specific builds, every build will flash on every nexus and will work with every carrier. The only difference has been radios, some offer better service in certain regions/carriers, but the builds themselves are unified
[Nexus 6  General] yellowman82:
1. You seriously need to relax and what your stating and all the homework you've been doing at the end of the day is YOUR opinion and SPECULATION because it's going both ways since google hasn't put in no kind of info about these being carrier specific YET.

2. Why in the WORLD are any of you guys even worrying about these being carrier specific or not I mean this is a nexus right? My last phone before the nexus 6 was an LG Flex and that thing had no development what so ever so I was stuck with it for a whole year until I got my hands on this beastly nexus 6 and do you think I'm on here asking folks or devs what radio and bootloader build I should flash? Heck no I got a nexus for a reason so I'm flashing until i find what works for me.

3. I know it's all your opinion but from my point of view you calling out the devs like you just did is so disrespectful bro seriously, the reason these devs tell these folks what you pointed out is because it's very annoying seeing " Hey is it OK for me to flash this radio on such and such carrier?", " hi would this radio or bootloader build work for my carrier?" I mean seriously they trying to avoid all these questions when all they need to do is flash it check if it works for them if it does stay on it if it doesn't then flash on to the next one like honestly that's the simplest thing any of these folks could do. At this point no one should worry about these damn images and radios being carrier specific just flash until you find what works for you it's that simple and quit with the asking about these being carrier specific it's all speculation until google themselves decides to put in their 2 cents.
[Nexus 6  General] Circaflex:
you are incorrect, I has no issues with calls on VoLTE with Tmobile using the D, E, or I build. M is not a "Tmobile Build" all it did was ship with a radio that worked with tmobiles VoLTE, you can sideload it on any carrier, your idea/label of Tmobile build is incorrect. Nexus is unified, we do not have carrier specific builds unless notated by Google.
[Nexus 6  General] yellowman82:
Well since you haven't had any problem on T-Mobile with all them images then maybe he's just a stupid flasher like he stated.

But honestly you Guy's are confusing a lot of folks with these speculation that hasn't been even confirmed with google and some of you guys are the reason we have all these folks asking in almost every ROM thread all these question about if they are able to flash X radio or images on the carrier they are in it's really just silly.
[Nexus 6  General] Circaflex:
I agree, too many uninformed users spouting off information because they read some blog on it or some other clueless user said it so they repeat it, creating a snowball effect.

If there is ever a build that is only for a specific region or carrier, it will be notated on the images website by Google. Take a look at the Nexus 5, there was one image specifically for a region.

I think i should just leave well alone and not come into these types of threads, so many new users arguing and spreading incorrect information it makes my head hurt. When you try and correct the information or provide credible information you are met with these same users criticizing your information telling you to do research and homework, it is almost as if owning an Android device, specifically a nexus, makes you some sort of computer god who knows everything related to linux and android.
[Nexus 6  General] yellowman82:
Exactly I know that feeling and it does make my head hurt too when I see it in the development ROM threads and staying away from this kind of thread/topic would be a great idea. Me personally I've been ignoring these kind of topics but seeing that post above from that specific member just kinda got to me and I just had to put my 2 cents in but they really are taking this carrier specific thing to far.
[Nexus 6  General] Circaflex:
You do realize users who bought the device from moto or google direct were running on Verizon at launch right? All devices are the exact same hardware wise, they are indeed unified. I can use a tmobile n6 on sprint verizon att just as i can use a sprint or vzw on any carrier, all bands are included on each device. This is exactly what I'm talking about you're being very vocal with false information confusing users.
[Nexus 6  General] yellowman82:
Wow he's a so called navy veteran and it's amusing how inappropriate and childish a grown man could act and seems racist at that. Pretty sure XDA won't miss him since XDA doesn't tolerate this kind of behavior.
[Nexus 6  General] twatts723:
I think maybe there's a breakdown in communication here. Yes, all builds obviously work with all the nexus 6s. But maybe if the build LMY47M is only sent OTA to T-Mobile phones, its a build for T-Mobile. Thus, the radio that works best in T-Mobile phones. Its just like when.I had my note 3. There were ROMs from the international phone that worked error free on my T-Mobile note 3, but it was still built for the international note 3. LMY47M is definitely built for the T-Mobile nexus 6, but of course its gonna work on all of them, because they are all the same phone. Everybody's right, sheesh. :good::good::good:

:highfive:

Let me edit this to say the LMY47M is built for T-Mobile carrier network/sim. There, don't jump my ****...
[Nexus 6  General] mgerbasio:
That's pretty much what T-Mobile said. There was a change in the way 5.1 handles the radio settings and sim for carriers, now it gets built into the OS release. Any build will work on any carrier but the carrier specific builds will have slightly better radio and network performance when paired with the OS build and carrier properly. If you consider that a custom OS or not, no idea.
[Nexus 6  General] LordGrahf:
I'm starting to give up hope on a factory image ever being released.
[Nexus 6  General] jcarlm:
The point I'm making is that I am on D build and all the T-Mobile features as in 611, hd voice and etc. work just fine for me. A lot of people are saying that they need M for this to work.
[Nexus 6  General] Pecata:
Let me just make sure we are clear-you are running the 47D build with the 47D radio and when VoLTE is enabled and you have LTE signal and dial 611 it goes through?
[Nexus 6  General] Lucke:
doesn't work for me on the 47D build. just states "call ended" and leaves the dialer.
[Nexus 6  General] funcrusher:
Same here. [MENTION=639488]Lucke[/MENTION]

Not that I care, but for the sake of the discussion.
[Nexus 6  General] music_ismath:
Same for me
[Nexus 6  General] jcarlm:
I can call 611 no problem. No volte, just now noticed that. 611 goes through but my phone good to either H or 3g.
[Nexus 6  General] FormeriPhoney:
For the record, I got my Nexus 6 today from Motorola.

Out of the box it was running I build.. Checked update on wifi and there was none.

Few hours later I put my tmo sim in and I was prompted soon after for an update, ending up being LMY47M
[Nexus 6  General] vvveith:
Same here.

Stock 47D. Cannot dial 611. Call ended, Leaves dialer. Told T Mobile about the issue back about a week ago. They said they'd be passing the information up stream and found it very unusual that the phone would behave that way no matter what build number you were running.

Just to clarify: Running stock, no root on 64 gig version of phone.
[Nexus 6  General] jcarlm:
I can call 611 no Problem on D.
[Nexus 6  General] music_ismath:
Can the people with LMY47D on T-mo make VoLTE calls at all?

I'm not sure how to test this myself or I would. Does it only work between T-mo customers for the moment?
[Nexus 6  General] funcrusher:
I believe the issue is that it doesn't work when volte is activated.

---------- Post added at 08:29 AM ---------- Previous post was at 08:26 AM ----------

Yes.

If you're on LTE and make a phone call, look at your LTE indicator - if it stays on LTE while in the call, then it's working.

No, it will between different providers.
[Nexus 6  General] jj14:
So strange - never realized there was an OTA from "I" to "M". By any chance, did you capture the OTA URL?
[Nexus 6  General] FormeriPhoney:
Sorry I didn't. Just got the ota in the notification and let it do its thing. I've been jumping back and forth between this and my note 4 so I wasn't really paying attention.
[Nexus 6  General] Pecata:
Yeah, that's what I thought. You don't have Enhanced LTE enabled in the settings, do you?

I was using this build and when Enhanced LTE is enabled VoLTE worked but the 611 over VoLTE didn't. Also sometimes when I try to dial a number with a weak LTE signal the dialer will freeze on Dialing and I had to reboot my phone to fix it.
[Nexus 6  General] Smallsmx3:
Anyone else have the issue where when you go to settings and you go to select preferred network type and it says LTE but nothing is selected? And if you select it it will eventually become unselected again ? I don't think it effects anything but still somewhat annoying
[Nexus 6  General] jcarlm:
I have it enabled.

---------- Post added at 12:15 PM ---------- Previous post was at 12:09 PM ----------

I was going to unlock, roll back then ota M but it looks like 5.1.1 is right around the corner.
[Nexus 6  General] twatts723:
New build, new radio, still can't get service in my tin shop in at LTE area :eek:
[Nexus 6  General] Pecata:
Yes, I have noticed that too. Funny thing is if you select 3G or 2G it sticks...I don't know if it means anything either but I agree that it's strange.
[Nexus 6  General] Smallsmx3:
Didn't happen on D, right now I'm on Chroma which is I with M stuff in it and it stays selected. I go back and forth between the two, I keep thinking that I'm missing out on some magic that is in stock M but they perform identically
[Nexus 6  General] twatts723:
Yeah its like that on mine too, but it seems like its enabled though. Just not showing the dot. Like maybe its cosmetic, just a $hitty job by google testers and it slipped by em
[Nexus 6  General] galaxys:
Yep, probably sharing some smoke at the time! :D :eek:
[Nexus 6  General] funcrusher:
It happens to me on D.
[Nexus 6  General] Jsunn:
OK, so I'm now on 5.1 and tried the 611 test.

With enhanced 4G LTE enabled, the 611 call doesn't connect at all. It goes strait to call ended...

So, until they come out with a new radio do I just leave it turned off?

Thanks,

-Jason
[Nexus 6  General] simms22:
works fine here. im in nyc, where are you? maybe its just a local tmobile issue, about 611. and why would you want to disconnect from volte because its not getting 611 anyways, unless you dont have volte in your area?
[Nexus 6  General] Jsunn:
I'm in DC. How can I test the VoLTE actually functions?

I also updated to "I" manually, I didn't do the OTA update to "M".

-Jason

---------- Post added at 07:53 PM ---------- Previous post was at 07:35 PM ----------

OK, I just called my voice mail and the LTE indication stayed on in the status bar. Does this mean that VoLTE is working?

I guess I need friends to call.

611 still doesn't work.

-Jason
[Nexus 6  General] simms22:
yup, thats volte, voice over lte. and if you ever need to call 611, just disable volte :)

---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------

oh, im on I as well, not on M.
[Nexus 6  General] noodles2224:
You don't need to disable VoLTE to dial 611. It works just fine with it on.

Sent from my Nexus 6
[Nexus 6  General] funcrusher:
It only works like that on M, I believe.
[Nexus 6  General] justin24:
So I downloaded the OTA file from Android Central. I used WugFresh to start off fresh with the Drivers etc and when I go to Sideload it says it cannot detect Fastboot even though it just detected it. When I reboot the phone OEM unlock is not checked off even though I had it checked. What is going on? I am currently on the LMY47D build.
[Nexus 6  General] cam30era:
1st, once your bootloader is unlocked, you don't need to worry about that setting anyone. It's only important (vitally so) when you intend to unlock or relock the bootloader.

2nd, when you get to Sideload, unplug your USB cable and plug it back in.
[Nexus 6  General] justin24:
Thank You for that. I will give it a try.

---------- Post added at 05:30 PM ---------- Previous post was at 04:59 PM ----------

Well I unlocked the phone and tried to sideload the "M" build from the LMYD build and I still get the Fastboot message.
[Nexus 6  General] yellowman82:
Check and make sure that mtp is clicked off for the USB as in you don't want to transfer any files. I had that same issue where it wasn't detecting my device and reason was because mtp or whatever it's called was checked on for transferring files which instead you need it off so when you plug in your device again pull down your notification and uncheck mtp if that's what it's called.
[Nexus 6  General] justin24:
Tried and didn't work.
[Nexus 6  General] BigDig:
You can't go from D to M. You must be at 5.0.1 to be able to side load the OTA