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....)
Related
I downloaded the version back in late Spring or early summer (might be 52.0) and remember that I couldn't find Wi-fi calling in it despite it being mentioned somewhere in the change logs. Is the latest version (81.0) supporting it now?
Cloudrift said:
I downloaded the version back in late Spring or early summer (might be 52.0) and remember that I couldn't find Wi-fi calling in it despite it being mentioned somewhere in the change logs. Is the latest version (81.0) supporting it now?
Click to expand...
Click to collapse
Read Post #3 FAQ #5. If it doesn't specifically state so in the OP then it probably is not supported. However, you might check out this Add-On from the T-Mobile HTC One Forum.
Cloudrift said:
I downloaded the version back in late Spring or early summer (might be 52.0) and remember that I couldn't find Wi-fi calling in it despite it being mentioned somewhere in the change logs. Is the latest version (81.0) supporting it now?
Click to expand...
Click to collapse
In short, NO, the last version to support T-Mobile WiFi calling (and coincidentally also Sprint phones) is ARHD 31.6
Interesting. Is there a reason why the feature was removed?
Cloudrift said:
Interesting. Is there a reason why the feature was removed?
Click to expand...
Click to collapse
i honestly don't know, technically it was never "removed", it was just not added in later releases... at first due to lack of OTA updates, but later on, maybe the person doing the t-mo stuff was no longer supporting it
since mike is nowhere close to T-Mo US, he pretty much has very little chance to test it, and if he was getting support for T-Mo then maybe that person moved on.
is the 4.4.3 T-Mo OTA update out? if it's not, i'm pretty sure it won't be implemented in 8x.x series until the official 4.4.3 T-Mo OTA is out.
Thanks for the information. Didn't know about all of this.
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
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
I searched and didn't see it mentioned but the latest Update for TMobile OP7 Pro is available. Sorry if wrong place to post or a dupe.
Update 9.5.10 just landed on my phone. Screen shown in my most recent post
Awesome! Thanks man I've been waiting for this update.
Sent from my GM1915 using Tapatalk
Updated & definitely see huge improvements on the Camera (the Camera was already great IMO). OnePlus has seriously shown amazing support for this device sofar.
Sent from my GM1915 using Tapatalk
Can anyone make a patch boot image for this update please
Camera updates
DxTcmix said:
Updated & definitely see huge improvements on the Camera (the Camera was already great IMO). OnePlus has seriously shown amazing support for this device sofar.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
What improvements do you see? Someone mentioned that the 48mp Pro mode photo quality was reduced in another forum. I'm still in 9.5.5 so I would need to update to 9.5.6 then this one. Just want to make sure that it's worth the update.
So this was how long after the official release? I think the updates are definitely coming quicker on my pro than they did on my 6T with T-Mobile.
I had actually returned my first OP 7 pro, but am going to give another try now that the new update is out a lot faster than TMO originally told me. The phone is very comfortable and smooth, but camera was the only thing that was a downer. So here's to a second try [emoji16]
Sent from my SM-N960U using Tapatalk
retrofred said:
I had actually returned my first OP 7 pro, but am going to give another try now that the new update is out a lot faster than TMO originally told me. The phone is very comfortable and smooth, but camera was the only thing that was a downer. So here's to a second try [emoji16]
Click to expand...
Click to collapse
I was surprised how fast the update came out considering most carriers can take their sweet time vs unlocked OnePlus international version. I was considering making mine the international version but thought I would see how quick TMo would release it. Good luck to you and hope it meets expectations. Keep in mind the teams working on the gcam are working their magic. If the stock camera isn't up to your standards you may try testing their gcam apk and xml. Users are reporting better pics.
https://forum.xda-developers.com/oneplus-7-pro/help/gcam-mod-7-pro-t3930459/page18 found links here
I heard that the T-Mobile version of 9.5.7 is better than the international version is that true
Exathi said:
I heard that the T-Mobile version of 9.5.7 is better than the international version is that true
Click to expand...
Click to collapse
How so? I am curious. for the most part the international version has been working for me with very few if any complaints, though do wonder if the T-Mobile firmware's radio firmware is slightly better for cellular connectivity.
Edited for clarification and spelling.
stmims1124 said:
How so? I am curious. for the most part the international version has been working for me with very few if any complaints, though do wonder if the T-Mobile firmware's radio firmware is slightly better for cellular connectivity.
Edited for clarification and spelling.
Click to expand...
Click to collapse
They have Google feed
Exathi said:
They have Google feed
Click to expand...
Click to collapse
Update did not bring Google feed to this device. It was already there on the T-mobile version.
room511 said:
Update did not bring Google feed to this device. It was already there on the T-mobile version.
Click to expand...
Click to collapse
True but I heard the volte and vowifi works better with the T-Mobile updates
How do I update to 9.5.7 while rooted?
Agree on the speed at which TMobile turned this update around.. I really appreciate the effort.
As for camera performance. I am far from a professional. It does seem to take a better photo in auto mode to jpeg. I downloaded the update on the plane as I was leaving for vacation. Glad to have the improvements with me.
No ghost taps yet and double tap has not missed a tap yet, only two days in though might be too early to tell...
Nightscape
The Nightscape on the INT and TMO are NOT the same. INT is MUCH MUCH better. TMO version is like the 9.5.5 version i dont know why this isnt the same but it isnt. I tested them back to back last night and the difference is HUGE. Yes I did the cache wipe and had thought it fixed it but nope. I haven't really tested the other camera functions. Everything else seems fine. The INT version does get weird with wifi calling and switching over so yah the Radio firmware issue does seem to be a thing.
9.5.8 just rolled out for th global version can't wait until TMobile gets it
And here you go...
Only update listed was the security patch.
Yeah, I was almost going to switch ROMs back to the T-Mo version since they rolled out 9.5.8 pretty fast, but looking at the release notes from T-Mo which only shows security updates, I think I'll stick with the International version as the 9.5.8 release included a camera and phone audio update.
CharlyDigital said:
And here you go...
Only update listed was the security patch.
Click to expand...
Click to collapse
T-Mobile is really stepping up their game I'm so happy we have the OnePlus 7404 North America OnePlus is a very good company and they are so customizable
Ok 2 questions around the AT&T Pixel 4 December update
1. Has anyone received the OTA yet?
2. Since the factory image for December is up on Google and labeled specific to AT&T, does this mean Google baked it entirely and AT&T will not touch it? Did AT&T send any carrier specific mods for Google to bake in the monthly patch? I know some carriers like to add their own pieces to updates but I was wondering why Google has an image labeled AT&T?
splink7007 said:
Ok 2 questions around the AT&T Pixel 4 December update
1. Has anyone received the OTA yet?
2. Since the factory image for December is up on Google and labeled specific to AT&T, does this mean Google baked it entirely and AT&T will not touch it? Did AT&T send any carrier specific mods for Google to bake in the monthly patch? I know some carriers like to add their own pieces to updates but I was wondering why Google has an image labeled AT&T?
Click to expand...
Click to collapse
1. I haven't received it. Side loading it now.
2. It's a mistake on the downloads page. The one labeled AT&T only is meant for every other carrier except T-Mobile & Fi (version *.11), and Japan & Taiwan (version *.016.A1).
https://support.google.com/pixelphone/thread/21769134?hl=en/
EVR_PR said:
1. I haven't received it. Side loading it now.
2. It's a mistake on the downloads page. The one labeled AT&T only is meant for every other carrier except T-Mobile & Fi (version *.11), and Japan & Taiwan (version *.016.A1).
https://support.google.com/pixelphone/thread/21769134?hl=en/
Click to expand...
Click to collapse
How does one side load? And does it factory reset the device?
splink7007 said:
How does one side load? And does it factory reset the device?
Click to expand...
Click to collapse
I'm assuming your phone is completely stock and its bootloader is locked?
If that's the case just sideload the OTA image for your phone using the stock recovery. Follow the instructions here:
https://developers.google.com/android/ota?hl=en
This process will not reset your device. It's just a manual way of updating your phone instead of waiting for Google to send it to you.
Curious as to who releases the update? Carriers or Google direct?
splink7007 said:
Curious as to who releases the update? Carriers or Google direct?
Click to expand...
Click to collapse
Images are developed and provided by Google monthly. Did you look at the URL? See the very straight forward instructions there. Those monthly images are also referred to as "rescue OTA's". Applying OTA images is really an essential skill for those with locked bootloaders. First step is to "install" the latest adb/fastboot binaries. This is essentially extracting a zip file into a folder, and reading the instructions right there on the same web page. I challenge you! You can do it. This is a walk in the park for you who presumably was partially dis-assembling HTC phones and jumping solder points to get S-On and root. If you need some pointers just PM me. I'm working a lot of hours but can help you at night.
v12xke said:
Images are developed and provided by Google monthly. Did you look at the URL? See the very straight forward instructions there. Those monthly images are also referred to as "rescue OTA's". Applying OTA images is really an essential skill for those with locked bootloaders. First step is to "install" the latest adb/fastboot binaries. This is essentially extracting a zip file into a folder, and reading the instructions right there on the same web page. I challenge you! You can do it. This is a walk in the park for you who presumably was partially dis-assembling HTC phones and jumping solder points to get S-On and root. If you need some pointers just PM me. I'm working a lot of hours but can help you at night.
Click to expand...
Click to collapse
Lol indeed and almost 15 years ago! Oh I am sure I can bro but not sure I want to after reading some of the issues with flashing the ota and uncertainty of which img to use. This post I was actually wondering who pushes the actual ota, Google or the carriers? If i had an unlocked bootloader I may actually root but asides kernal and minor mods, I'm not sure root is beneficial for me now. Used to oc the processor and push the devices but there's plenty under the hood nowadays lol.
I feel like I'm back on my Samsung! Updates that don't deliver. Asides from vanilla Android, another was prompt patches/updates coming from the horse itself is why I switched to the pixel. Total disappointment
Mine is updating right now, just got the update tonight. I'll follow up after it installs
splink7007 said:
I feel like I'm back on my Samsung! Updates that don't deliver. Asides from vanilla Android, another was prompt patches/updates coming from the horse itself is why I switched to the pixel. Total disappointment
Click to expand...
Click to collapse
Its always going to be slower coming from a carrier than it is from google.... So I really wouldn't expect updates any sooner than mid month of the release. Honestly, this is the fastest AT&T has EVER updated a device. I just got mine tonight (had to manually check for a system update)
rodcpierce said:
Its always going to be slower coming from a carrier than it is from google.... So I really wouldn't expect updates any sooner than mid month of the release. Honestly, this is the fastest AT&T has EVER updated a device. I just got mine tonight (had to manually check for a system update)
Click to expand...
Click to collapse
I actually got November update they day of release last month.
rodcpierce said:
Its always going to be slower coming from a carrier than it is from google.... So I really wouldn't expect updates any sooner than mid month of the release. Honestly, this is the fastest AT&T has EVER updated a device. I just got mine tonight (had to manually check for a system update)
Click to expand...
Click to collapse
I am on T-Mobile and bought an unlocked Pixel 4XL. They are dropping the ball with these updates. This is 2 months in a row for me. I don't mind them holding off if they fear it is going to break the devices but I shouldn't have to sideload an OTA every month when there are other devices, a few being Samsung devices, with the December security patch.