Related
I have a D2G that I'm using an AT&T SIM in for GSM use only. The phone stays in GSM mode all the time.
I'm having an interesting issue with the way the phone detects that it has completed a call.
On a normal CDMA phone (my DX) after you dial a number and hit send, the "call timer" starts counting up as soon as the phone has connected to the network and the call starts ringing. If you want (though there would be little reason to do so) you can bring the dialpad back up and start sending DTMF tones even while the other end is still ringing (hasn't answered yet).
On the D2G in GSM mode (don't know about CDMA mode because I've not used this phone in CDMA mode) when you dial a call, the call timer doesn't start counting up until the phone senses that the other end has actually answered (receives a connect signal). While the line is ringing (before anybody answers) you can bring up the dialpad, but pressing keys does not send any tones. Once the called party answers, pressing keys then sends tones.
The problem comes when trying to dial into a conference bridge where you have to enter the bridgeline passcode, or while trying to use a calling card. Both these systems appear to not send the "connected" signal when they first answer. They wait until you get connected to the desired conference call, or until you've entered all the calling card information and are rung through to your ultimate target before sending the connected signal.
Since the D2G in GSM mode is actually waiting for this "connected" signal before starting the call timer, and since it won't allow you to send DTMF tones until the call timer starts, it is basically impossible to use a conference bridge or calling card.
I have tried numerous add-on dialers, but all hand off to the OEM phone/dialer app after initial dialing. I've tried add-on DTMF generators, but of course they just generate the tones locally (speaker) and not onto the ongoing call. I've been all through build.prop, etc. looking for a setting that would tell it not to wait for a connect signal to enable the "connected" behavior and not found anything.
Putting pauses or waits in the dial string doesn't work either because the phone doesn't even start "pausing" or "waiting" until it senses that it has connected (which doesn't happen before the other end gives up waiting for me to enter the code).
That's the really irritating part. When the conference bridge or calling card system gives up waiting and connects me to the thing that tells me my time to enter the codes has expired and it is going to hang up on me, then it sends the "connected" signal and I can enter all the tones I want on top of the "please call back when you can figure out how to use a phone" message.
I've had someone running a newer firmware test to see if they have this same behavior and they do. If anyone wants to see if they have the issue, they could call the Sprint calling card access number (800-366-2255) and you should find you can't enter any tones once it has answered. Again, this is on a D2G in GSM mode. I'd expect in CDMA mode it would work fine.
Possible avenues of resolution:
Make the phone treat the call as connected immediately instead of waiting for the other end to answer
Have an external app that can send DTMF tones on an active call (Google says that is a common desire that is generally not possible)
Somehow make the built-in dialer allow number presses to generate tones even if it doesn't think the other end has answered yet
Thanks in advance for any suggestions.
Are you trying to say you use the phone on AT&T in USA?
Try switching phone to GSM/UMTS in settings instead of 'global' I remember having some issues with ring back tone while in global mode using GSM network which went away once I switched to GSM/UMTS only.
Sent from my DROID2 GLOBAL
leobg said:
Are you trying to say you use the phone on AT&T in USA?
Click to expand...
Click to collapse
Yep. Other than the undesirable behavior of the call progress timer, it works perfect. Although the data works great, I keep data disabled because on AT&T prepaid data costs like 1 cent per kilobyte. That doesn't seem like much until you think about 1024 kilobytes in a megabyte which means you're paying $10.24 per megabyte which is insane. Fortunately I can bring up 3G Mobile Hotspot on my DX (which has unlimited data) and tether my D2G through my DX and have full Internet. It sounds retarded, but the only time I use this setup is when I need my DX to do mobile VPN for work, and then use my D2G for voice calls. AT&T prepaid is only like $1.99 a day for unlimited voice and text, and you only pay on the days you use it (which is almost never for me).
leobg said:
Try switching phone to GSM/UMTS in settings instead of 'global' I remember having some issues with ring back tone while in global mode using GSM network which went away once I switched to GSM/UMTS only.
Click to expand...
Click to collapse
Thanks for the suggestion. Actually I was already in GSM/UMTS mode but tried switching it to "Global" mode. Unfortunately the behavior was the same.
Somehow I imagine if I trot down to the Verizon store to ask them about it they won't really be super inclined to help. I have considered trotting down to the AT&T store where I bought the prepaid SIM and seeing what they think. But I don't imagine it would be good for much other than the amusement of their confusion.
Droid 2 Global is configured so it doesn't get service with any GSM/UMTS provider located on the teritory of the United States of America. How is yours working on AT&T is really a huge surprise to me and many other members of this and other online forums.
This so called "band lock" (google for Droid 2 global band lock) can reportedly be circumvented, but there is no publicly available method to do it. Unless you got yours 'band unlocked', it is not supposed to get any service from neither AT&T nor T-Mobile. Or maybe you bought it from someone who was working on this 'band lock'
Could you share more info with us?
leobg said:
Droid 2 Global is configured so it doesn't get service with any GSM/UMTS provider located on the teritory of the United States of America. How is yours working on AT&T is really a huge surprise to me and many other members of this and other online forums.
This so called "band lock" (google for Droid 2 global band lock) can reportedly be circumvented, but there is no publicly available method to do it. Unless you got yours 'band unlocked', it is not supposed to get any service from neither AT&T nor T-Mobile. Or maybe you bought it from someone who was working on this 'band lock'
Could you share more info with us?
Click to expand...
Click to collapse
The phone has been unlocked with the TBH/DBU unlock. It is running 2.4.29 firmware and has to stay on 2.4.29 for the unlock to be preserved. The unwanted call progress behavior (the purpose of my original post) has been tested and confirmed on another phone running 2.4.330 so it's not a 2.4.29 issue. I'd bet that all of the Blur dialers probably do the same thing (disable tones after Send and until the call progress timer starts running). Just in CDMA mode the call progress timer starts running as soon as the call starts ringing and in GSM it waits for an actual connect signal. The D2G is truly like two complete phones in one, so seeing this type of disparity in behavior between the two different modes (I assume when in CDMA mode it would work just like all other CDMA models and not have the issue) isn't really surprising at all. I would expect that anybody who is using the GSM mode of their D2G would have this issue when dialing into a conference bridge or calling card provider where the "connect" signal is not given until after all of the secondary dialing has been completed. It would seem however that this issue would have come up before since I can't be the only person that works for a huge company and spends most of his day dialed into conference bridges for meetings (and might just want to dial into those meetings from his spiffy GSM phone).
I've been though the AOSP source for the phone/dialer before (when troubleshooting something else), so when I get a chance, I'll go through again and find the section where it enables and disables the tone sending. I'd guess it would be trivial to remove the part that disables tones during the period between Send and call-progress-timer-start, compile it, and just replace the dialer on the phone. I've been through all the build.prop and everything else hoping a setting would jump out at me, but no luck.
About the TBH/DBU unlock -- after the unlock there's nothing special about sticking an AT&T, TMobile, etc. SIM in there, but I only have first hand experience with the AT&T. I just went into the local AT&T store and told them I wanted to buy a prepaid SIM. They asked what kind of phone and I think I told them I had a Samsung Captivate (not that it really matters). The SIM was basically free and I put $25 on it. Stuck it in the phone, changed to GSM/UMTS mode, phone blurred while it was changing modes, and now has AT&T banner on the lock screen. Pretty much a non-event.
I didn't get a chance to go down to the AT&T store yet, but I plan to. If nothing else I'd like to test calling into the same Sprint calling card number from another GSM phone -- especially an Android phone if they have a working model there -- and see if it too has a problem.
Sorry for rambling. I hope I addressed your questions.
My friend MotoCache1 is the "other" member of TBH, just an FYI!
We haven't discussed the status of the band unlock on XDA out of respect for the rules here regarding paid services.
Well, that explains the things
Btw- mine is on Rogers Canada, i can use comma to add pause to dial extensions conference bridges without issues.
However, when I try my Telus Canada sim in, when I dial number, dialer says hang up, 00:00, then connects the outgoing call, sort of like a call back service, but without ringing back - hang up, then the very next second call connects and phone issues ring back tone. But this "hangup" on the middle prevents me from dialing extensions or conference bridges bu using pause in the number dialed. Everything else is fine (data, messaging/etc). So it is kind of crippled on Telus. Wonder if it is the same thing you get on AT&T.
Sent from my DROID2 GLOBAL
Hmmm. Interesting. Forgive the ignorance, when using Rogers is that CDMA? Or are you using GSM for both carriers?
I tried the same scheme, using commas in the dial string, but unfortunately the phone doesn't ever get to the part after the commas because it waits for connect before continuing the dial string. I don't get the hang up behavior you describe though. I'm a complete newb to GSM, so what I'm about to suggest may be stupid, but I wonder if the carriers have any sort of call handling parameters that are stored on the SIM?
I happened to be in a VZW store to get an extended battery for my DX and asked them if they had a demonstrator D2G in GSM mode so I "could test a bug I read about on the Internet". Moments after the question left my mouth I realized I was stupid for asking it, and he confirmed that by saying "no, we can't use the phones in GSM mode because GSM on that phone doesn't work in the US". Oops, duh.
He asked what the bug was and I told him. He said that he hadn't heard of that, but it sounded like something that would be fixed in a software release. He looked to see if any such releases were listed for the D2G, but found none. Surprisingly (to me anyway) there is a recent release listed for the D1 to fix an "unwanted recipients" problem (for messages), and some other thing (I don't recall).
I'm at Bike Week right now (sitting in the bath tub typing this on my DX -- yay Swype) but will give the AT&T store a shot when I get back. I'll also borrow a buddy's Tmobile SIM and see if it behaves any differently. He has an actual Tmobile branded android phone, (a Samsung, but I don't remember which one right off) so I can do the conference bridge test on his phone too.
Both Rogers and Telus now sport GSM/UMTS (Telus only UMTS) networks. Gone are the days when Rogers had CDMA network, almost 10 years now. Telus still has CDMA alive, but they are phasing that out. My CDMA radio is sleeping, until I get to the States next time I guess (my D2G is active on a pay-go plan) I will be doing some travelling in May/Jun across Europe, so I will try with european sims too.
Sent from my DROID2 GLOBAL
leobg said:
Both Rogers and Telus now sport GSM/UMTS (Telus only UMTS) networks. Gone are the days when Rogers had CDMA network, almost 10 years now. Telus still has CDMA alive, but they are phasing that out. My CDMA radio is sleeping, until I get to the States next time I guess (my D2G is active on a pay-go plan) I will be doing some travelling in May/Jun across Europe, so I will try with european sims
Click to expand...
Click to collapse
Thanks for the details. Interesting that you see two completely different behaviors just by changing the SIM. That leaves the question of whether the difference is due to the way each network is handling the call progress, or if it is some sort of information on the SIM itself that makes the difference.
I looked into SIM editors to see what sorts of things the various editors claimed to be able to read/edit on the SIM. I haven't seen anything along the lines of call processing characteristic parameters, etc., so I'm leaning toward the difference being in the signaling received from the network. I'll be able to get a better idea of what's going on when I get back home and can experiment with a Tmobile SIM, and/or put my AT&T SIM in another phone and see what it does.
OK, back from Bike Week (last week actually) and grabbed a T-Mobile SIM. Really odd results. The very first call I dialed on the T-Mobile SIM, the call timer started immediately, and I could send DTMF tones immediately. Every call since then has exhibited the same behavior I was seeing with the AT&T SIM -- the call timer doesn't start until a formal connect happens (which the calling card and conference bridge sites don't send upon initial connect -- thereby preventing sending the tones to access the service).
I spent just a little time going through the source code of: [platform/packages/apps/Phone.git]/src/com/android/phone/CallTime.java and found the spot where the call gets switched to "active":
Code:
/**
* Sets the call timer to "active call" mode, where the timer will
* periodically update the UI to show how long the specified call
* has been active.
*
* After calling this you should also call reset() and
* periodicUpdateTimer() to get the timer started.
*/
/* package */ void setActiveCallMode(Call call) {
if (DBG) log("setActiveCallMode(" + call + ")...");
mCall = call;
// How frequently should we update the UI?
mInterval = 1000; // once per second
}
I started looking around to see "who" all calls that and right off I only see CallCard.java calling it. I was expecting to see it called somewhere in PhoneApp.java (after observing a connect or something), but it's not called there.
There's lots of hunting yet to do, but I wanted to post progress in case anybody out there cares.
In some hunting I happened to stumble on a pretty detailed page outlining the exact same problem on an iPhone. It's understandable that this type of problem might exist and persist on a closed source device like an iPhone. Fortunately, something like this should be very solvable on an open source device.
I haven't had my buddy with a T-Mobile issued Android phone (Samsung Vibrant) test this yet. That's on the "to do" list.
More updates as I have them.
So what I've figured out on this is that you pretty much just can't use conference bridges or calling cards on a GSM phone. I've used my Tmobile and AT&T SIMs in a bunch of phones now:
1. Droid 2 Global
2. Droid Pro Global
3. Motorola Napoleon
They all do the same thing. Heck, the Napoleon isn't even Android - it's Windows Mobile. I also tried with my friend's Samsung Vibrant (which he has on Tmobile) and it does the same thing -- call timer never starts running and if the call timer isn't running you can't generate tones to put in your access code for the conference bridge, etc. Apparently the AT&T iPhones do the same thing, so again, this is a GSM thing.
Which begs the question again -- doesn't anybody with a GSM phone need to call into conference calls? I was under the impression that most big companies used conference bridges for most of their meetings.
Anyway, when I get some time I'll get back to taking a stab at hacking on the dialer -- just no free cycles to tackle it right now.
It must be something with that conference bridge you are trying it on. I know many phone switches do not connect the call while you are in the IVR/menu trees - it is usually done in order to avoid inaccurate call metrics on the receiving end. We are running a contact centre in our company and I know how important this is (and we do it to - we don't connect the call until operator answers the call). Billing is not supposed to start until call is connected on the receiving end. Apparently GSM operators like T-Mobile and AT&T care about call connect parametter and Verizon is simply ignoring it, I guess.
Hello. I have a problem with my phone, which i did not faced before on other Windows Mobile devices (this is my firs 6.5 one).
Samsung Customer support, lighlty saying, did not helped me redirecting me to my carrier, which i do know is not faulty.
So, when phone have established 3G data connection (neverthless is it internet or mms) i cannot send text messages. Phone acts like there is no range or number was invalid.
When i switch band from WCDMA to GSM, full duplex works like charm. In my opinion i've paid (it's second hand device, but who cares) for fully featured phone and switching band does not solve my problem (in my place only WCDMA works, on GSM band voice calls are choppy and signal still gets lost).
I would me more that gratefull is someone can help me with this strange problem. Phone is used in Polish network Play Mobile (260 04), is sim unlocked (don't know was is locked at all earlier).
What i've done: i've changed sim card to other provider (T-Mobile), did hard reset, upgraded to latest ROM (upgrade_tool_for_sph-i350_ver.1.4.1.0), and lurked in registry searching 3g-, data-, duplex- related keys and values.
Someone faced similiar problem in this device or system?
edit. After checking some settings on SGH-i600 i've found that there's setting to change SMS sending method. It's called 'Send SMS Option' in Connections,and it has 'Network seletion' (not selection ;p) with options 'PS preferred' and 'CS preferred'. In my opinion it's Nokia's coresponding option 'sms over GPRS', which makes on Nokia device to send messages faster.
Anyways, changing this option to PS changes value in HKLM/Comm/Cellular/SMS/Router/ServiceOption from 4 to 8. Changing this value on target device (i350) does make smses not to send at all, regardless if data connection is on or off.
Hello all,
I flashed my girlfriend's Sprint S5 with Lineage OS recently without a hitch, all services working perfectly. We ended up traveling, so she went to Sprint to set up a temporary international roaming plan. Everything was completely as expected abroad. When we got back, her phone would not send SMS messages.
We tried the usual airplane mode and such, and to no avail. Assuming something was wrong with the network configuration from travelling, we reset network settings. Didn't work. I then decided to just do a full wipe and re-flash of Lineage OS. Still doesn't work. I then resorted to going back to the stock TouchWiz ROM from Sprint. At that point, under the stock ROM, SMS were sending. Out of curiosity, we flashed back Lineage OS, and SMS will again not send. We noticed that if the SIM card is removed, SMS will send, but the phone would not be able to access 4G LTE. We also confirmed with Sprint that there are no restrictions on the account.
What could be causing this to occur only on custom Roms? Do we need to do a PRL update? If so, how does that work on stock Android?
Thanks in advance!
S5 sprint No outbound sms
I've had this problem for weeks....So far the only solution is using Google voice app....
I'm using LOS 7.1.1 20170207 kltespr nightly, LTE SMS can only receive, sending doesn't work. Only 3G SMS works.
Things I noticed:
Settings -> About Phone -> Status -> IMEI Information. When on 3G, all information is displayed here, when on LTE, only IMEI and IMEI SV is displayed, there's no PRL/MIN/MEID/ICCID anywhere, not even disabled or greyed out, just hidden completely.
ICCID also shows DUMMY_NV_ICC_SERIAL instead of the actual ICCID.
Same experience for me, I've been trying to find a workaround for over a month with no success. Alternative text messaging apps seem to work, but I don't trust 3rd parties with my SMS.
Unable to send SMS
Mike.
Which third party SMS app are you getting to work? Besides Google voice I have had no luck with any third party app?
I'm having the same issue. I'm on Resurrection ROM which is based on Lineage. Since update I can't send SMS at all other than via Google Voice. I can receive SMS and I can send/receive MMS.
I did find that if I change to 3g only for my network settings, I can send SMS. But then of course I don't get LTE data speeds for everything else. So the issue for me at least is tied specifically to LTE. Wondering if there is an APN or other setting I can change that would fix this but so far no luck finding anything.
Bug reported since 01/28
https://jira.lineageos.org/browse/BUGBASH-37
I've run into the same problem or similar. If I set my preferred network type to GLOBAL then I can send and receive SMS/MMS messages but I'm forced to either Roaming LTE or 3G. It's often stuck in 3G after a drive for any distance. If I force it to LTE, then SMS/MMS stops working and I can't place or receive calls either but the network will show up as LTE and Sprint.
To get there from Settings Home -> More (under Wireless and Networks) -> Cellular networks -> Preferred network type -> Choose Global.
Sometimes I can force it back to LTE but roaming if I switch temporarily to LTE then once it connects switch back to Global. Occasionally I have to put it in airplane mode to get the radios to reset and connect but some combo of switching network type and ending up in global and switching into and back from airplane will do the trick.
YMMV of course.
one way I fix it temporarily is to:
cell networks - carrier settings, let it crash
go in again and let it find your carrier
once connected, make a phone call at least to get it ringing
I can then make sms mms.
it's a rediculous work around but it works for me every time
SMS Sending Problem with Lineage 14.1 (31.07.2017)
Heyy
I'm not able to send sms from SIM 1 but can send sms from SIM 2 in Lenovo A6020a46 (2GB) on Lineage 14.1 (31.07.2017).
The same SIM is working good in another roms and Calling + Internet are working properly.
After dialing *#*#4636#*#* in Phone Information - SMSC Refresh then it appeared "Phone no.", 456 and I pressed Update.
But there was no process for saving or updating. Then I reentered in Phone Information but SMSC Shows blank.
What to do??? anybody help in this matter will be immensely appreciated.
Dilpreet Sidhu
I made this file using Odin with the steps from here. I flashed the file, set the connection to LTE aand it worked. https://forum.xda-developers.com/showpost.php?p=71582847&postcount=5908
To fix this issue with having LTE signal and sending SMS at the same time you have to open EnginneringMode app (or *#*#3646663#*#*) and check 'Sms over Sgs support' in Misc Feature Config tab.
Doesn't work because nothing comes up entering the code. Any idea?
2ISAB said:
Doesn't work because nothing comes up entering the code. Any idea?
Click to expand...
Click to collapse
If that code doesn't work for you, try to find an app called Engineering Mode MTK. Unfortunately I cannot attach any screenshots yet (I got less than 10 posts).
fix
there is an option in network settings (enhanced 4G LTE mode for comunications etc) i disabled that option and messaging works fine now. before unchecking this option i could only send sms only with phone on 3g mode, now it works fine. i think this option is for hd voice calls via 4g lte.
I see this is an old problem and I´m having the same problem. I can receive SMS, but I can´t send.
But to add to that, I couldn´t connect at all with my previous carrier and changed carrier after which I can use data, call and send SMS. I still can´t receive SMS.
My apologies if this is covered someplace; a search of the T-Mo S7 forums turned up nothing.
I am traveling internationally and that means the phone is always "roaming." I'm on T-Mobile's unlimited international plan and so the roaming is included. Nevertheless I get constant warnings about data roaming, by way of a popup. The popup offers a choice to go to roaming settings. If you turn roaming off, of course, nothing works, and then you still get a constant popup asking if you want to turn roaming back on.
I am not alone; the hue and cry has been raised about this over on T-Mobile's forums, here:
https://support.t-mobile.com/thread/141619
T-Mobile's response is that this is a Samsung issue and to take it up with them.
My phone is rooted stock and I have SQLite editor. Surely there must be someplace I can access the settings for this to turn these popups off altogether, but I have not found it. Or perhaps a service menu accessed by dialer code?
Any hints greatly appreciated.
Config details:
model SM-G930T
Android version 7.0
Security patch level January 2018
Build Number NRD90M.G930TUVS4BRA1
SE enforcing, SEPF_SECMOBILE_7.0_0004
slwelsh said:
My apologies if this is covered someplace; a search of the T-Mo S7 forums turned up nothing.
I am traveling internationally and that means the phone is always "roaming." I'm on T-Mobile's unlimited international plan and so the roaming is included. Nevertheless I get constant warnings about data roaming, by way of a popup. The popup offers a choice to go to roaming settings. If you turn roaming off, of course, nothing works, and then you still get a constant popup asking if you want to turn roaming back on.
I am not alone; the hue and cry has been raised about this over on T-Mobile's forums, here:
https://support.t-mobile.com/thread/141619
T-Mobile's response is that this is a Samsung issue and to take it up with them.
My phone is rooted stock and I have SQLite editor. Surely there must be someplace I can access the settings for this to turn these popups off altogether, but I have not found it. Or perhaps a service menu accessed by dialer code?
Any hints greatly appreciated.
Config details:
model SM-G930T
Android version 7.0
Security patch level January 2018
Build Number NRD90M.G930TUVS4BRA1
SE enforcing, SEPF_SECMOBILE_7.0_0004
Click to expand...
Click to collapse
My wife just called me from the UK with the exact same problem. She's using a brand new T-mobile S9+ running the latest update to oreo.
Reading the T-mobile thread I did see a couple of suggestions that had limited results. One was to disable the Samsung+ app or turn off all the apps inside of Samsung+. The other was to disable automatic network selection and to put it into manual mode. Problem with the second option is you have to reselect a different network if you are moving around...like most people do.
I'm going to call her tomorrow and see if any of these work. I'll report back.
Nothing worked. Fortunately, she brought her old iPhone along and started using it again. Sorry
While I'm on a call, I can't send or receive texts. I have the GM1917. I have AT&T in SIM1 & Tmo in SIM2. Once I disconnect from the call, it ends up sending the text whether it be an SMS or MMS.
Another thing I've noticed is when I got the phone, I had the option/ability to turn on VoWiFi and VoLTE for the Tmo SIM. But after the last two updates, I don't have those options anymore.
Anyone with insight as to why I'm having these 2 issues? Another weird thing is VoLTE is available for my AT&T SIM, but I thought AT&T didn't allow VoLTE unless it was a phone from them.
Build: OOS 9.5.6.GM21AA
Model: GM1917
A little more about my setup:
I was having issues with receiving MMS group texts while using the default Tmo APN settings, so I created a new APN using the settings from the tmo website.
The issues were it would take 5-10 minutes to receive a group text, and often times they came in the incorrect order.
I saw there were updates for the 7 Pro available, but my phone wasn't receiving the updates. So I used the OOS Updater app to download the update and install it manually.
Any help would be greatly appreciated!
Well, here's an update:
When I change the data sim from AT&T to Tmo, the options to enable VoLTE and VoWiFI show back up when I select SIM2. At this point when I look at SIM1 the VoLTE option is not showing anymore.
So it seems as though when I change the Data SIM, only that SIMs "Enhanced Communications" option is viewable. Is this working as intended?
surface13 said:
While I'm on a call, I can't send or receive texts. I have the GM1917. I have AT&T in SIM1 & Tmo in SIM2. Once I disconnect from the call, it ends up sending the text whether it be an SMS or MMS.
Another thing I've noticed is when I got the phone, I had the option/ability to turn on VoWiFi and VoLTE for the Tmo SIM. But after the last two updates, I don't have those options anymore.
Anyone with insight as to why I'm having these 2 issues? Another weird thing is VoLTE is available for my AT&T SIM, but I thought AT&T didn't allow VoLTE unless it was a phone from them.
Build: OOS 9.5.6.GM21AA
Model: GM1917
A little more about my setup:
I was having issues with receiving MMS group texts while using the default Tmo APN settings, so I created a new APN using the settings from the tmo website.
The issues were it would take 5-10 minutes to receive a group text, and often times they came in the incorrect order.
I saw there were updates for the 7 Pro available, but my phone wasn't receiving the updates. So I used the OOS Updater app to download the update and install it manually.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Go to Settings
Wi-Fi & Internet
SIM & network
click your SIM under SIM Settings( mine is SIM 1 (T-Mobile))
Enhanced Communications