Is there anything definitive on whether the 6.01 MMB29K Shamu factory image has
whatever it was that was T-mobil specific in the long awaited MRA58X?
There is nothing on the factory image page that singles out T-mobil for either image,
but we know from other sources that "X" resolved some T-mobil specific issue.
kmandel said:
but we know from other sources that "X" resolved some T-mobil specific issue.
Click to expand...
Click to collapse
I didn't see any article indicating what T-Mo specific issue was addressed by "X" (if you did, please do share). "K" worked just fine - band 12 and WiFi calling (both of which are T-Mo specific) worked fine on "K".
I'm on 6.0.1 now, and Band 12 and WiFi calling are still working
jj14 said:
I didn't see any article indicating what T-Mo specific issue was addressed by "X" (if you did, please do share). "K" worked just fine - band 12 and WiFi calling (both of which are T-Mo specific) worked fine on "K".
I'm on 6.0.1 now, and Band 12 and WiFi calling are still working
Click to expand...
Click to collapse
+1 I'm on 6.0.1 no problems
Sent from my Nexus 6 using Tapatalk
jj14 said:
I didn't see any article indicating what T-Mo specific issue was addressed by "X" (if you did, please do share). "K" worked just fine - band 12 and WiFi calling (both of which are T-Mo specific) worked fine on "K".
I'm on 6.0.1 now, and Band 12 and WiFi calling are still working
Click to expand...
Click to collapse
There were several articles like
http://www.techtimes.com/articles/1...shmallow-update-approved-rollout-imminent.htm
With statements like:
"However, the rollout got delayed and did not get pushed out as initially planned as the carrier found a major bug. Smith recently explained on Twitter that when T-Mobile put the build through testing, it found the bug. As a result, the carrier had to get a new build which had to be tested out again. ....Smith also revealed that update had the build number MRA58X."
Actually, I have been running MRA58K the original release, which has both band 12
and wifi calling without trouble, so I'm puzzled about what "X" was supposed to fix,
and if 29K has it too.
After the update, I had the option for wifi-calling in my settings but it wasn't working right. After a soft-reset it worked great.
There is a new update coming out this week, hopefully it will fix all of the issues.
Got it too. Haven't used it yet. It'll be nice if it works OK. We'll see.
This has been a frustrating issue. My wife and I both have Nexus 6 phones. She has the 32gb & I have the 64gb version. Hers recently started not receiving MMS messages. Anything with a large picture would simply never show up. Anything with a very small graphic or group text would show up as "Non-text content". Here are the steps we've taken to solve this:
1. TMO started by insisting it was an APN issue. So she edited her APN. Didn't help.
2. We then swapped SIMs. Hmmmm. My phone then behaved like hers while hers could then send/receive MMS.
3. TMO said ok maybe it's the SIM. They sent us a new one. SAME result. Her phone wouldn't receive MMS.
4. Out of frustration, I factory reset her phone and reset the APN info. Didn't help. (Cleaned up her phone of some trash programs though. :laugh
5. TMO engineering says they still can't find anything on their end. Elevate to tech supervisor. She tells us to go a TMO store (right near us) to try a THIRD SIM. OK, we do. SAME RESULT. We tried swapping SIMs around again and the same thing happens. My SIM in her phone, everything works. Her SIM in mine, I can't receive MMS.
6. TMO store guy suggests MAYBE (but unlikely) that there is something her account has that's stored on the SIM when its activated that causes the phone to freak. Also says it's above his pay grade .
So now we are again waiting on TMO to poke around further on their end. My question for all you smart types here is:
Has anyone ever heard of this issue? Is there anything you know of that could be causing it? I think it's a bad provisioning somewhere in the dark recesses of TMO. The ONLY change we made to our plans (which seems just coincidental) is that we moved from the 2 lines Unlimited for $100 plan to the over-55 Unlimited plan. We did this maybe 3 weeks ago. But the features are all the same on both plans.
We are both on the same Android 7.0 final OTA firmware updates from Google. NBD92G
Would there be ANY chance that a sideload firmware update would make any difference? We're getting desperate here. Any & all suggestions welcome.
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Don't use old firmware... I had issues on certain custom ROMs and old firmware where MMS wouldn't work over WiFi. Never as bad as you were getting.
If you wanna stay stock, sideload the latest OTA to go to NGI55D. Anything older than that is vulnerable to Blueborne exploit, which is a HUGE security concern IMO. I can confirm MMS is working correctly (even with WiFi enabled) on bone stock NGI55D as well as custom ROM Dirty Unicorns v11.7.1 which includes September security patch.
ktmom said:
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Click to expand...
Click to collapse
I've had this issue on most LOS roms. i ended up making a custom APN i flash when i try a rom built on LOS.
Yeah, it sure sounds like a problem with account partitioning, or something else with the account that gets associated with the SIM on initial use. What if you try the problem SIM in a phone that is not a Nexus 6? I wonder if you could get a new sim and set it up in a different phone, then transfer it to the problem phone?
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
RealSkier said:
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
Click to expand...
Click to collapse
Glad they figured this out.
Hi
Upgraded to Pie last Friday on EE in the UK on a carrier device so its the EE Firmware.
Prior to the upgrade I have VoLTE on the status bar at the top and since then never shown its face again, anyone else had this?
How did it upgrade via OTA or via Odin and if latter what did you use?
Updated in US and the hack to allow VoLTE (via shortcut master) no longer works. Hopefully a fix (or real update from certain carriers) will arrive soon...
Sounds like Pie isn't fully baked yet.
I'll see myself out.
I'm on EE and have been using Pie for quite a while at this point. VoLTE works fine for me.
Hello All,
I posted this in Samsung Community, but unfortunately none was able to help. I am hoping XDA members could help fix this issue.
I am facing a strange problem with my S21 Ultra Unlocked which was directly bought from Samsung. I had enrolled into OneUI 4.0 beta when I was in the US. I was using Sprint connection then.
I had to travel back to my home country (India) and I am using an Airtel sim card (LTE) here. Now, the strange problem is that LTE (data) works here fine. But, VoLTE is not working. The network changes to 2G for phone calls. I am assuming that the auto-switching bands which was introduced in OneUI 4.0 is causing the problem.
Using Smart Switch PC, I rolled back to One UI 3.1. VoLTE and WiFi calling started to work again. But, soon after I got update notification for One UI 4 beta. To confirm that it is indeed an issue with One UI 4, I installed it again. And as expected, I am not getting VoLTE or WiFI calling again.
Since I changed from Sprint to Airtel, I am not able to withdraw from the Beta program as well. I am getting the error "One UI beta features aren't available because your service provider has changed".
Also, I am not sure what the final One UI 4 will offer. For the first time in my life, I am seeing an Android upgrade causing my phone to not able to connect to VoLTE.
I am also attaching the screenshots of Phone Information. As you can see, in OneUI 3.1, VoLTE and WiFi calling are provisioned. But in OneUI 4, both are not available. I am assuming the issue is because IMS is not registered. But, I am not able to find how this can be fixed.
Thanks in advance for your help.
Thanks,
APS
#volte #samsung #s21ultra #oneui #oneui4 #imsservice #ims #airtel #oneuibeta
A quick update - I updated to final version One UI 4 and the issue is still there. I am still not able to get VoLTE or WiFi calling in India.
I am having similar issue. Were you able to figure out anything?
dp1989 said:
I am having similar issue. Were you able to figure out anything?
Click to expand...
Click to collapse
No. I have started a new thread in Samsung US Community. Let's see if it reaches the right team who needs to fix this issue.
Since the issue was previously in the Beta version, I didn't get much support. Now, I can see more people facing the same issue since OneUI 4 final version is out.
Can you please provide Samsung members thread link here (or subject line which will help me find it).. I will reply with same issue
dp1989 said:
Can you please provide Samsung members thread link here (or subject line which will help me find it).. I will reply with same issue
Click to expand...
Click to collapse
Try this "DON'T BUY S21 Series Phones if you want use it outside US".
aps99 said:
Try this "DON'T BUY S21 Series Phones if you want use it outside US".
Click to expand...
Click to collapse
I searched Samsung members app and didn't find any thread like that. May be if you can post a link.
dp1989 said:
I searched Samsung members app and didn't find any thread like that. May be if you can post a link.
Click to expand...
Click to collapse
It's in the US community. Did you search there?
Yes, I searched in US Community.
dp1989 said:
Yes, I searched in US Community.
Click to expand...
Click to collapse
Not sure if URL can be posted here. Let me try anyways.
Samsung account
us.community.samsung.com
Yes. I've noticed this since the beta started, was hoping it would be fixed by the time stable is released, but looks like it isn't.
VoLTE/VoWiFi worked fine in Qatar with One UI 3.1 (US unlocked model) but is unable to activate on One UI 4.
It's a shame, but they probably won't fix it since it still works alright with US sims. Maybe it will be fixed in One UI 5 accidentally next year the same way it broke now, but don't hold your breath.
I would once again rollback to One UI 3.1 and wait for a stable Android 12 One UI 4.0 however it may never work with that device in your region. I won't be updating until they release a better version, still too many bugs. Your best option is sell it and buy your Service Provider's device, that's a permanent fix.
varcor said:
I would once again rollback to One UI 3.1 and wait for a stable Android 12 One UI 4.0 however it may never work with that device in your region. I won't be updating until they release a better version, still too many bugs. Your best option is sell it and buy your Service Provider's device, that's a permanent fix.
Click to expand...
Click to collapse
I am on stable One UI 4.0 now. Still it doesn't work.
I cannot sell a device that has such an issue now that I am in India. I will probably sell it once I am back in US if Samsung doesn't fix this issue before then.
Go to settings -->general> reset ----> reset network settings
And reboot after
Volte shou´d work again
Hey i was having this same problem, but seems to have disappeared since I installed SM-G998U rom. I didn't install Userdata and seems I didn't get any bloatware plus activation is still on. You can try.
SOGKush420 said:
Go to settings -->general> reset ----> reset network settings
And reboot after
Volte shou´d work again
Click to expand...
Click to collapse
That won't work, and is completely irrelevant to the issue at hand. This only applies to the unlocked US model (U1) - the OneUI 4 update misconfigures VoLTE for international SIMs.
U will work, but the branded firmware shouldn't be required, U1 is currently broken.
lui0703 said:
Hey i was having this same problem, but seems to have disappeared since I installed SM-G998U rom. I didn't install Userdata and seems I didn't get any bloatware plus activation is still on. You can try.
Click to expand...
Click to collapse
Did you lose the data? I already factory reset my phone trying to fix this issue, rolling back etc.
aps99 said:
Did you lose the data? I already factory reset my phone trying to fix this issue, rolling back etc.
Click to expand...
Click to collapse
I did a full backup before. And just restored the data via Smart Switch after.
lui0703 said:
I did a full backup before. And just restored the data via Smart Switch after.
Click to expand...
Click to collapse
Just to confirm. Are you having a US phone which is being used outside US? What is your current carrier?
SOGKush420 said:
Go to settings -->general> reset ----> reset network settings
And reboot after
Volte shou´d work again
Click to expand...
Click to collapse
Will you please elaborate the whole procedure how did you installed this rom roll back to one UI 3.1 safely..
I have USA unlocked variant of S21 ultra and i am on stable One UI 4.0. Facing the issues.
..VOLTE AND WIFI CALLING FEATURE NOT WORKING ..
YOUR HELP WOULD BE HIGHLY APPRECIATED