Related
Any word on when we will be getting this for us Tmobile US users. Anxiously waiting for copy/paste funcitonality. Overall i like the phone, but some very spotty reception especially with 3g data connection.
I think as far as anyone knows the update is due to start rolling out from the 8th March... but it'll be the carriers that can delay it by a week or two
Yeah, I'm waiting for the update before I decide if I'm going to keep this HD7 or not. I love the big screen and I love the OS. But this phone has some serious reception issues. My Moto Defy and even my Nokia Nuron get much better reception in both voice and data. I'm not use to so many dropped called.
I hear ya, but wouldn't that be a carrier update, not NoDo that addresses these reception issues we have. Just thinking logically here, this is a software update, not radio or kernel correct? MS can't possibly know all the issues present for each carrier or phone that needs to be addresses. Soryr coming form android so maybe my understanding is incorrect.
JamesDax said:
Yeah, I'm waiting for the update before I decide if I'm going to keep this HD7 or not. I love the big screen and I love the OS. But this phone has some serious reception issues. My Moto Defy and even my Nokia Nuron get much better reception in both voice and data. I'm not use to so many dropped called.
Click to expand...
Click to collapse
I'm waiting with you. So far, the same disappointment. I also noted that prices have fallen significantly and people are getting rid of them.
It seems that as soon MS will do something good is this system will fail. Even though HTC has released several new models, but with Android on board.
HTC Europe v1.30 ROM was released over in the Mozart forums and build number confirmed final NoDo.
http://forum.xda-developers.com/showthread.php?t=984239
and this one:
http://forum.xda-developers.com/showthread.php?p=11917333#post11917333
I'm sure it's just a matter of hours for HD7... the pre-update went quick and smoothly, as well so should this one too.
Cheers
aquanaut88 said:
HTC Europe v1.30 ROM was released over in the Mozart forums and build number confirmed final NoDo.
http://forum.xda-developers.com/showthread.php?t=984239
and this one:
http://forum.xda-developers.com/showthread.php?p=11917333#post11917333
I'm sure it's just a matter of hours for HD7... the pre-update went quick and smoothly, as well so should this one too.
Cheers
Click to expand...
Click to collapse
Tmobile US sent you the pre-update?
Please confirm post above
Ya im confused too. I'm on Tmobile USA and didnt get a pre update yet.....
Please confirm/Explain
Me neither
From what I've gathered, the pre-update wasn't/isn't 100% necessary.
Any good news?
jimbonics said:
From what I've gathered, the pre-update wasn't/isn't 100% necessary.
Click to expand...
Click to collapse
the content of the update is necessary but the update process itself isn't because the contents of that update will be included in the NoDo update. Given the fact that the 8th was only a rumored date, I doubt its coming out today, but hey surprises are welcome!
Luisraul924 said:
the content of the update is necessary but the update process itself isn't because the contents of that update will be included in the NoDo update. Given the fact that the 8th was only a rumored date, I doubt its coming out today, but hey surprises are welcome!
Click to expand...
Click to collapse
i've been checking all day. nothing.
scriller said:
i've been checking all day. nothing.
Click to expand...
Click to collapse
same here... Ah well at least the fact that the update is out unofficially for dev/unlocked devices is a good sign.
devGOD said:
Tmobile US sent you the pre-update?
Click to expand...
Click to collapse
not I'm starting hate them
It's my understanding that the pre-update is not necessary. What T-mobile has done was include the pre-update WITH the NoDo update; this was noted as something carriers were allowed to do.
When does this combo update come? Who the hell knows.
nexus14 said:
It's my understanding that the pre-update is not necessary. What T-mobile has done was include the pre-update WITH the NoDo update; this was noted as something carriers were allowed to do.
When does this combo update come? Who the hell knows.
Click to expand...
Click to collapse
Microsoft themselves stated (while being scrutinized if carriers can block updates) that updates are bundled together by them (Microsoft) so that it won't have an effect on consumers who's carriers have blocked a previous update. The first update served two purposes: the first; was driver or firmware level upgrades that facilitate the upgrade process (which is why those small number of phones ended up bricking when the update went awry) the second was to see the worst case scenario that ended up happening to the Samsung phones. So to do list for initial update crossed out, time to release NoDo!
hope this helps
ej_424 said:
Any word on when we will be getting this for us Tmobile US users. Anxiously waiting for copy/paste funcitonality. Overall i like the phone, but some very spotty reception especially with 3g data connection.
Click to expand...
Click to collapse
http://www.wpcentral.com/trophy-and...=feed&utm_campaign=Feed:+wmexperts+(wpcentral) not sure if this will help probably not
check this link also this should get everyone on the right foot http://forum.xda-developers.com/showthread.php?p=10176994#post10176994
Can anybody confirm whether the radio & firmware updated ROM that XDA user Ansar posted over in the development section made it into the NoDo update ROM? I've heard good things about that radio update (saves battery, better signal etc.) and it'd be nice to know that we would also be receiving that updated radio and firmware.
http://www.androidcentral.com/cincinnati-bell-htc-one-could-skip-android-42-go-straight-43
If true this COULD happen On the major carriers as well, hence the "small" update recently.
I saw that article, and while I wouldn't really mind, I'm not sure if I believe it. Other countries have already gotten 4.2.2 for the GSM One.
nerv8765 said:
I saw that article, and while I wouldn't really mind, I'm not sure if I believe it. Other countries have already gotten 4.2.2 for the GSM One.
Click to expand...
Click to collapse
I am not familiar with the carrier, are they GSM or CDMA?
Kraizk said:
I am not familiar with the carrier, are they GSM or CDMA?
Click to expand...
Click to collapse
Pretty much everywhere but America
Sent from my HTCONE using Tapatalk 2
It does seem strange to me that we haven't seen 4.2.2 on the sprint htc one... As I recall on the HTC 4glte the update to 4.1 came fairly quick. I think HTC just said fk it let's release 4.3 which has back end features that we benefit from. 4.2 isn't such a big deal when HTC has highly customized version of android.
Sent from my HTCONE using xda premium
tsdeaton said:
Pretty much everywhere but America
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
No no sorry, I meant is Cincinnati Bell GSM or CDMA. BTW it appears they are GSM so why the delay I am unsure....
Kraizk said:
No no sorry, I meant is Cincinnati Bell GSM or CDMA. BTW it appears they are GSM so why the delay I am unsure....
Click to expand...
Click to collapse
No GSM carriers in the US have updated to 4.2.2. But, Europe and Asia have gotten the update, which does work on ALL GSM phones, in any country.
However, there are no CDMA carriers (maybe a few, but it's a very small number) outside of the US, so the CDMA version (Sprint) has no update yet.
nerv8765 said:
No GSM carriers in the US have updated to 4.2.2. But, Europe and Asia have gotten the update, which does work on ALL GSM phones, in any country.
However, there are no CDMA carriers (maybe a few, but it's a very small number) outside of the US, so the CDMA version (Sprint) has no update yet.
Click to expand...
Click to collapse
Yes I know this, My question initially was if anyone knew if Cincinnati Bell was GSM or CDMA. If they were CDMA I could see HTC saying the same for us. That is not the case, they are GSM which means skipping the update for them seems rather weird.
They are gsm
From My TweakedOut ONE
I would imagine that HTC has 4.3 and probably has probably had it for months now. I'm wondering who they're working with to release it to, as far as carriers are concerned.
NORCALkID said:
It does seem strange to me that we haven't seen 4.2.2 on the sprint htc one... As I recall on the HTC 4glte the update to 4.1 came fairly quick. I think HTC just said fk it let's release 4.3 which has back end features that we benefit from. 4.2 isn't such a big deal when HTC has highly customized version of android.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
This is exactly why I have been wondering why people are pissed about a lack of 4.2.2 on the Sprint HTC One. There aren't that many new features to justify the outrage and there aren't any performance enhancements... 4.2.2 is barely a step up from 4.1.2 (the main improvements relate to tablets).
numus said:
This is exactly why I have been wondering why people are pissed about a lack of 4.2.2 on the Sprint HTC One. There aren't that many new features to justify the outrage and there aren't any performance enhancements... 4.2.2 is barely a step up from 4.1.2 (the main improvements relate to tablets).
Click to expand...
Click to collapse
I disagree (regarding tablets), but that's mainly due to how fast Google's native implementation of quick toggles grew on me. It makes more Sense though for a 4.3 update, given that a fairly long time has already passed since the last point release and the relatively minor changes (compared to 4.0->4.1).
Then again, I'm also mildly concerned that the real story here is that Sprint's carrier testing is taking longer than it should and we'll just get a delayed 4.2.2 update instead.
Rirere said:
I disagree (regarding tablets), but that's mainly due to how fast Google's native implementation of quick toggles grew on me. It makes more Sense though for a 4.3 update, given that a fairly long time has already passed since the last point release and the relatively minor changes (compared to 4.0->4.1).
Then again, I'm also mildly concerned that the real story here is that Sprint's carrier testing is taking longer than it should and we'll just get a delayed 4.2.2 update instead.
Click to expand...
Click to collapse
If you want quick toggles, just installed ViperRom... The changes aren't important enough to justify spending a lot of resources into upgrading the OS. The main changes in 4.1.2 -> 4.2.2 are in tablets, specifically multiple user implementation in the tablet environment.
http://developer.android.com/about/versions/android-4.2.html
Multiple Users
--------------------------------------------------------------------------------
Android now allows multiple user spaces on shareable devices such as tablets. Each user on a device has his or her own set of accounts, apps, system settings, files, and any other user-associated data.
Click to expand...
Click to collapse
numus said:
If you want quick toggles, just installed ViperRom... The changes aren't important enough to justify spending a lot of resources into upgrading the OS.
Click to expand...
Click to collapse
Exactly what I wrote as far as corporate resources. As for ViperROM, I really don't think you're reading posts before you hit "reply."
but that's mainly due to how fast Google's native implementation of quick toggles grew on me
Click to expand...
Click to collapse
I use Power Toggles for any devices not running 4.2, but I've come to prefer this method. The EQS included in ViperROM frankly makes my eyes bleed.
numus said:
The main changes in 4.1.2 -> 4.2.2 are in tablets, specifically multiple user implementation in the tablet environment.
http://developer.android.com/about/versions/android-4.2.html
Click to expand...
Click to collapse
Granted. Again, I don't think you read my post very carefully. Your original post contended that there weren't any marked changes for phones, which is what I disagreed with-- not that the majority of changes went to tablets.
Rirere said:
Exactly what I wrote as far as corporate resources. As for ViperROM, I really don't think you're reading posts before you hit "reply."
I use Power Toggles for any devices not running 4.2, but I've come to prefer this method. The EQS included in ViperROM frankly makes my eyes bleed.
Granted. Again, I don't think you read my post very carefully. Your original post contended that there weren't any marked changes for phones, which is what I disagreed with-- not that the majority of changes went to tablets.
Click to expand...
Click to collapse
I disagree (regarding tablets), but that's mainly due to how fast Google's native implementation of quick toggles grew on me.
Click to expand...
Click to collapse
I don't think you wrote what you thought you wrote, or else you need to look up the word regarding... You specifically said you disagree with my assessment on tables.
As for quick toggling, I think you are overestimating the percentage of users who care to turn features off once they are turned on.
numus said:
I don't think you wrote what you thought you wrote, or else you need to look up the word regarding... You specifically said you disagree with my assessment on tables.
As for quick toggling, I think you are overestimating the percentage of users who care to turn features off once they are turned on.
Click to expand...
Click to collapse
I think you need to reread your post for the context.
(the main improvements relate to tablets)
Click to expand...
Click to collapse
FTFY.
And I think Cincinnati Bell is a joke as far as a wireless carrier is concerned. I live in the Cincinnati area, and their service is terrible. I don't see them getting an upgrade to 4.3 before anyone else. They usually trail behind everyone else in their release of phones.
Answers to this question are either totally unanswered or vague.
Can/will the M7 support VoLTE (Voice over LTE) or not? Three in the UK is upgrading it's network to support VoLTE in the 800mhz frequency range. It would be nice to have it if at all possible. Sadly there is very little info on whether the hardware supports it and if the software (Lolipop and mods) will support it or not on the M7.
Can we have a thread with solid answers as this is quite important for some of us who have reception issues.
deadman3000 said:
Answers to this question are either totally unanswered or vague.
Can/will the M7 support VoLTE (Voice over LTE) or not? Three in the UK is upgrading it's network to support VoLTE in the 800mhz frequency range. It would be nice to have it if at all possible. Sadly there is very little info on whether the hardware supports it and if the software (Lolipop and mods) will support it or not on the M7.
Can we have a thread with solid answers as this is quite important for some of us who have reception issues.
Click to expand...
Click to collapse
I've been searching and curious (without avail) about the same question. I'm currently using Viper/Venom ROM v9.0.0 that uses a base from the M9. The M9 supports VoLTE and thus the option appears in the menu on the M7. However it does not function and if you try to interact with it the phone service crashes. This makes sense since it was developed for M9 hardware. Does this mean it's totally not supported on the M7 from a hardware standpoint - nope. But without the proper software it's not going to happen. Is T-mobile (or whoever your carrier is) going to develop the feature? Probably not. Will google? Maybe, seems to be appearing on google phones as a standardized feature. Same for wifi calling...
sensati13 said:
I've been searching and curious (without avail) about the same question. I'm currently using Viper/Venom ROM v9.0.0 that uses a base from the M9. The M9 supports VoLTE and thus the option appears in the menu on the M7. However it does not function and if you try to interact with it the phone service crashes. This makes sense since it was developed for M9 hardware. Does this mean it's totally not supported on the M7 from a hardware standpoint - nope. But without the proper software it's not going to happen. Is T-mobile (or whoever your carrier is) going to develop the feature? Probably not. Will google? Maybe, seems to be appearing on google phones as a standardized feature. Same for WiFi calling...
Click to expand...
Click to collapse
With the AICP MM ROM for the m7, I called my mom and it said "VoLTE" in blue letters. I never really took notice of it until after I went back to Sense... I'm going to flash that ROM again and give you an update soon (if not I probably forgot, sorry). And btw I know this thread is very old but I just wanted to chime in and say what I've found
firedroidx said:
With the AICP MM ROM for the m7, I called my mom and it said "VoLTE" in blue letters. I never really took notice of it until after I went back to Sense... I'm going to flash that ROM again and give you an update soon (if not I probably forgot, sorry). And btw I know this thread is very old but I just wanted to chime in and say what I've found
Click to expand...
Click to collapse
So, that was an interesting and timely reply. I recently upgraded my M9 (s-on) to a firmware that is too new for MM CM so I went back to my M7 for a while. It's still on a sense based rom but I may give AICP MM a spin on my M7- thanks!
:edit
Now that I think about it, the only reason I upgraded to the M9 was for VoLTE, the M7 is the perfect size phone, god how ridiculous new phones are these days, every iteration just a liiiiitttle bit bigger. enough already lol /rant...
sensati13 said:
So, that was an interesting and timely reply. I recently upgraded my M9 (s-on) to a firmware that is too new for MM CM so I went back to my M7 for a while. It's still on a sense based rom but I may give AICP MM a spin on my M7- thanks!
:edit
Now that I think about it, the only reason I upgraded to the M9 was for VoLTE, the M7 is the perfect size phone, god how ridiculous new phones are these days, every iteration just a liiiiitttle bit bigger. enough already lol /rant...
Click to expand...
Click to collapse
I flashed AICP last night and called my mom again, but unfortunately no VoLTE... It's odd because I clearly remember seeing those blue letters when I was about to hang up :/ If I find anything new I'll post it here!
firedroidx said:
I flashed AICP last night and called my mom again, but unfortunately no VoLTE... It's odd because I clearly remember seeing those blue letters when I was about to hang up :/ If I find anything new I'll post it here!
Click to expand...
Click to collapse
Maybe, you didn't remember well, what you've seen? Because I think, it's impossible.
So this thread is a year old (time to re-activate it?), and I wonder about the same issue. I tried on the M7 with different firmwares (european latest hboot 1.61, GPE hboot 1.54), using LineageOS 14.1 (Android N 7.1.2), but with no constellation it's possible to activate VoLTE.
I figured out, that it depends on "the hardware", but IMHO that's not really the reason because the LTE radio chip performs LTE correctly. So I expect it depends in reality on the "radio firmware" to active VoLTE.
And I have never seen a radio firmware for the M7, which is able to perform VoLTE.
If somebody knows about a "patched" or "modified" radio firmware for the M7, to activate VoLTE, please let me know!!! (Because LOS 14.1 runs well, and is -- from the OS side -- able to perform VoLTE).
Thanks a lot,
samhhmobil
samhhmobil said:
Because LOS 14.1 runs well, and is -- from the OS side -- able to perform VoLTE)
Click to expand...
Click to collapse
Thats not true, Lineage in general doesnt support VoLTE. You can read about exacly this on AICP G+ page because a lot of people asked for VoLTE Support. Official answer was "as long as lineage doesnt implement it we dont have it" There are some unofficial Roms for other devices where the maintainer did implement VoLTE. The big problem with VoLTE is, in nearly every country and provider it has a different standard so its not just add something and it works for everyone.
But Guys, do you realy need LTE while your in a Call and 3G isnt enough? I think 42mb/s should be enough for everything and thats what you actually get while in a call. Btw our m7 only has an internal read and write speed at about 5-15mb/s so its useless :silly:
Maybe a stupid question but couldn't find this addressed anywhere. In the last couple versions TMO Nexus' have had their own version, I'm assuming because of WiFi calling, is that not the case anymore? Seems their all going to run MRA58K from what I see. I have the the OTA upgrade zip from my version but was thinking a clean install was better. Just didn't want to botch anything. Anybody know about this?
WiFi calling is built in now so yeah, just use the same version as everyone else.
snatale1 said:
Maybe a stupid question but couldn't find this addressed anywhere. In the last couple versions TMO Nexus' have had their own version, I'm assuming because of WiFi calling, is that not the case anymore? Seems their all going to run MRA58K from what I see. I have the the OTA upgrade zip from my version but was thinking a clean install was better. Just didn't want to botch anything. Anybody know about this?
Click to expand...
Click to collapse
There is only version of Android 6.0 (MRA58K). It is a unified build for all carriers. But you will loose support for LTE band 12 on T-mobile. There's another thread about that issue in this Q&A section.
cam30era said:
There is only version of Android 6.0 (MRA58K). It is a unified build for all carriers. But you will loose support for LTE band 12 on T-mobile. There's another thread about that issue in this Q&A section.
Click to expand...
Click to collapse
Band 12 works for me and many others, so not everyone loses it.
cam30era said:
There is only version of Android 6.0 (MRA58K). It is a unified build for all carriers. But you will loose support for LTE band 12 on T-mobile. There's another thread about that issue in this Q&A section.
Click to expand...
Click to collapse
That's not cool, at that point is anything affected buy letting the OTA come in vs flashing from Google's site? Or same thing either way?
JimSmith94 said:
Band 12 works for me and many others, so not everyone loses it.
Click to expand...
Click to collapse
After I flash, how do I go about verifying if I have Band 12 running or not?
snatale1 said:
That's not cool, at that point is anything affected buy letting the OTA come in vs flashing from Google's site? Or same thing either way?
After I flash, how do I go about verifying if I have Band 12 running or not?
Click to expand...
Click to collapse
do you have band 12 in your area? im in nyc, and dont. all i get is band 4.
snatale1 said:
After I flash, how do I go about verifying if I have Band 12 running or not?
Click to expand...
Click to collapse
I use SignalCheck Lite. I'm almost always on Band 12 (B12 in the app), but I just noticed that I'm on Band 4 today.
simms22 said:
do you have band 12 in your area? im in nyc, and dont. all i get is band 4.
Click to expand...
Click to collapse
Not sure, I'm in Richmond, VA I considered that though, seems I'm on Band 4 right now. It's a decently populated area with a couple million in the Metro but If you don't have it there, we probably won't for a while. Either way seems like by the time it's here it will be enabled anyways.
Thanks for the help guys.
Yeah I don't think we have it in the Virginia Beach/ Norfolk area either. I excited to get to the end of the year when the roll out should be over
Sent from my Nexus 6 using Tapatalk
cam30era said:
There is only version of Android 6.0 (MRA58K). It is a unified build for all carriers. But you will loose support for LTE band 12 on T-mobile. There's another thread about that issue in this Q&A section.
Click to expand...
Click to collapse
Well, so just fyi, with the benefit of hindsight one month later --- MRA58K wasn't actually a unified build. I flashed it, based on posts like this (yours certainly wasn't the only one). Now, of course, I learn that the official TMo build of Marshmallow for Nexus 6 is MRA58X. There is some mention of an OTA from K to X, but I think I have heard that before..... Am about to downgrade to last official TMo Lollipop, and take OTA to MRA58X, and be a happy, patient little TMo camper from now on.
wbarnes4393 said:
Well, so just fyi, with the benefit of hindsight one month later --- MRA58K wasn't actually a unified build. I flashed it, based on posts like this (yours certainly wasn't the only one). Now, of course, I learn that the official TMo build of Marshmallow for Nexus 6 is MRA58X. There is some mention of an OTA from K to X, but I think I have heard that before..... Am about to downgrade to last official TMo Lollipop, and take OTA to MRA58X, and be a happy, patient little TMo camper from now on.
Click to expand...
Click to collapse
Google has posted the factory image for MRA58X and MMB29K, just yesterday.
cam30era said:
Google has posted the factory image for MRA58X and MMB29K, just yesterday.
Click to expand...
Click to collapse
I'll be darned - thanks for the heads-up!
wbarnes4393 said:
Well, so just fyi, with the benefit of hindsight one month later --- MRA58K wasn't actually a unified build. I flashed it, based on posts like this (yours certainly wasn't the only one). Now, of course, I learn that the official TMo build of Marshmallow for Nexus 6 is MRA58X. There is some mention of an OTA from K to X, but I think I have heard that before..... Am about to downgrade to last official TMo Lollipop, and take OTA to MRA58X, and be a happy, patient little TMo camper from now on.
Click to expand...
Click to collapse
And, FWIW, it's closer to two months... Unfortunately, neither Google, nor the carriers publish much information about their plans for carrier specific builds. So one has to take everything with a "grain of salt" here. Sorry if this caused you any issues....
wbarnes4393 said:
Well, so just fyi, with the benefit of hindsight one month later --- MRA58K wasn't actually a unified build. I flashed it, based on posts like this (yours certainly wasn't the only one). Now, of course, I learn that the official TMo build of Marshmallow for Nexus 6 is MRA58X. There is some mention of an OTA from K to X, but I think I have heard that before..... Am about to downgrade to last official TMo Lollipop, and take OTA to MRA58X, and be a happy, patient little TMo camper from now on.
Click to expand...
Click to collapse
Did MRA58K cause any T-Mo specific issues for you? I used MRA58K on T-Mo since the day it was released (till yesterday when I flashed MMB29K) - it worked just fine. I had Band 12 coverage, and WiFi Calling, and free in-flight Gogo Texting etc. I did read that T-Mo had announced their build was MRA58X, and I would have flashed that, if the factory images had been available before yesterday - but MRA58K worked just fine. (MMB29K is working fine as well)
jj14 said:
Did MRA58K cause any T-Mo specific issues for you? I used MRA58K on T-Mo since the day it was released (till yesterday when I flashed MMB29K) - it worked just fine. I had Band 12 coverage, and WiFi Calling, and free in-flight Gogo Texting etc. I did read that T-Mo had announced their build was MRA58X, and I would have flashed that, if the factory images had been available before yesterday - but MRA58K worked just fine. (MMB29K is working fine as well)
Click to expand...
Click to collapse
It seemed to work fine. This week, I missed a couple of text messages, and so I have been trying to troubleshoot. I really don't know if it was the culprit, but along the way I discovered that MRA58X is the official, TMo build. I don't really have any specific reason to believe the wrong build was the culprit, but I just decided to rip off the bandaid and flash it. I am one of those on the fringes of being comfortable with flashing images, etc. I have just decided I am sticking with OTA direct from the carrier from now on. I don't like injecting variables into the stability of my experience (I realize I should just get off XDA then!! But then a month goes by and I get a little bored....)
Anyone received OTA for Marshmallow on T-mobile?
If you received, when did you received it?
Negative on my end still waiting prob gonna root soon
Stll waiting but got it on my N5 on 10/8 (AT&T) and on my N9 on 10/14.
Been waiting for this myself. Checked T-Mobile's software update site and is still shows Android 6 as "In Testing" for the N6.
its not in testing, marshmallow has been released for the nexus 6. just go grab the factory image, and apply it yourself, manually.
Yes, their specific build, IS in testing.
Currently available build is stock Google build. "Should" work well enough as a daily driver. But I'm sure T-Mobile will make some tweaks for WiFi calling and band 12
Sent from my Nexus 6 using Tapatalk
carlz28 said:
Yes, their specific build, IS in testing.
Currently available build is stock Google build. "Should" work well enough as a daily driver. But I'm sure T-Mobile will make some tweaks for WiFi calling and band 12
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
the time around, there is a unified build, instead of many builds for different networks. the build is already out, its not in testing..
Guess we'll have to askdes , to confirm that.
Sent from my Nexus 6 using Tapatalk
simms22 said:
the time around, there is a unified build, instead of many builds for different networks. the build is already out, its not in testing..
Click to expand...
Click to collapse
Google has tested it. But T-Mobile is still doing acceptance testing. Click the Nexus 6 link on this interactive page at T-mobile.s site. At this moment, it shows the status to be "T-Mobile Testing," which is described as this: "During this stage, the device will go through T-Mobile certification process testing to make sure you get the best quality software possible."
Flashed manually. WiFi calling works just fine.
boomerbubba said:
Google has tested it. But T-Mobile is still doing acceptance testing. Click the Nexus 6 link on this interactive page at T-mobile.s site. At this moment, it shows the status to be "T-Mobile Testing," which is described as this: "During this stage, the device will go through T-Mobile certification process testing to make sure you get the best quality software possible."
Click to expand...
Click to collapse
well of course tmobile has to approve it before it goes out over its network. but its still officially out, and anyone can flash it manually
simms22 said:
well of course tmobile has to approve it before it goes out over its network. but its still officially out, and anyone can flash it manually
Click to expand...
Click to collapse
Yes. No one will stop you. But "can" does not necessarily equal "should." There are reports in this forum that there might be issues specific to T-Mobile when this build is flashed. Maybe that's why they call it "testing."
boomerbubba said:
Yes. No one will stop you. But "can" does not necessarily equal "should." There are reports in this forum that there might be issues specific to T-Mobile when this build is flashed. Maybe that's why they call it "testing."
Click to expand...
Click to collapse
i use tmobile. i am running marshmallow. i dont have any issues. and i don't read ANY issues here regarding any tmobile specific issues. if theres any specific issues that you are talking about, maybe you would care to enlighten me?
edit..
i just read what you linked, and im in that thread as well. thats an issue that you will see reported every single release. and its usually a very few that report it.
I used factory images. No problems on T-Mobile so far
Sent from my Nexus 6 using XDA Free mobile app
There have been questions about Mm6 on the Nexus6 and T-Mobile band12 support.
The Nexus6 was one of the two or three phones to support band12 on release. Since then, T-Mobile has built out and converted a lot of their towers to band12, and there have been rumors recently that they no longer want the N6 to be able to use band12.
I don't understand those rumors and press reports.
There are also disturbing reports from T-Mobile users who are on Mm6 that their Nexus6 no longer supports band12 without reverting to the last Lollipop radio.
So, I am holding off installing Mm6 OTA on my new Amazon-bought N6, even though it was offered when my Cricket/AIO prepaid SIM was in place as soon as I first booted.
Band12 is important, and will become more important, on T-Mobile.
Sent from my VS985 4G using Tapatalk