Any success making Wifi Calls on T-mobile in USA ? (not just enabling option in menu) - Xiaomi Redmi Note 5 / 5 Plus Questions & Answers

Hello,
I have read and found success making options for wifi calling appear in the stock menu when it was absent before, however the phone is nonetheless unable to make wifi calls after enabling. Tried placing phone in airplane and turning wifi on.... or just choosing the "wifi only" option for making calls in the network menu - Resulting message always states to connect to a wireless network to proceed with the call, even though I have an excellent connection and internet works fine.
I have done an exhaustive search for methods to successfully use T-Mobile's wifi calling feature on my phone.
My initial research revealed that the option should work so long as your phone supports wifi calling as well as your carrier.
The wifi calling option was absent (as well as VoLTE) on the stock ROM, so I had high hopes that a custom ROM which included the feature would allow me to utilize the service with T-Mobile (my current GSM carrier).
After a slew of unsuccessful attempts to make calls using wifi vs the mobile network, I finally called T-Mobile's tech support who was actually quite helpful, but essentially stated that wifi calling through T-Mobile requires the carriers own proprietary software to work... in other words, even though T-Mobile likes to promote the ease with which you can BYOD (bring your own device), it would appear that the wifi calling feature is only possible when buying a phone directly from T-Mobile unless a custom rom is built which is at least partially based upon T-Mobile's own proprietary software with regard to wifi calling.
If ANYONE has had any luck at all placing wifi calls on the T-Mobile network domestically in the U.S. using the global/MEG7 version of Redmi 5 Plus, your assistance would be immensely appreciated. I have found that, although my phone does not support multiple LTE bands used by T-Mobile, I am still able to make LTE calls quite frequently in my region using the single supported band.... however, my home is a "dead zone" so to speak and, even though I am smack dab in the middle of an excellent coverage zone, my service inside the house is poor enough that others' attempts to call are unsuccessful, leaving me unaware of the call unless a message is left.
At this point, I am getting ready to throw in the towel so any advice or success stories would be greatly appreciated - or, on the flipside, a validation that wifi calling is just not possible at this time so I don't have to drive myself crazy with a continued search for which a solution does not yet (or may never) exist.
Many thanks for your help!

Related

[Q] i717R + CM9 + Fido = no VOIP!!!

Folks, please give me a hand!
I have the Note from Rogers Canada, upgraded to CM9 release, my provider is Fido, and I'm struggling with getting VoIP work over 3G.
1. Native ICS client. It's OK on WiFi, and on 3G the call is being established in and out, but no sound either direction. I heard 3G calling was blocked in GB client, and there was even a method tweaking the APK to make it work, but obviously something is very different in ICS - that tweak is not applicable - I can't find proper file in this APK.
2. cSipSimple - does not work at all, makes the phone acting weird. Well, last update was in 2011, maybe not compatible with ICS at all.
3. SipDroid - crashes.
4. Dell Voice - crashes.
My provider is freephoneline.ca, and I'm testing VoIP with it without success. I'm a network engineer with rich VoIP experience, and run at home a sophisticated FreePBX setup accessible from Internet. I've tried to register my Note on my home PBX as an extension, and I see same behavior - phones ring, calls establish, but no sound.
I don't understand where's the trouble exactly. Is it the Note, or CM9, or my provider is allowing SIP but blocking RTP? I see that all three Fido's APNs are doing NAT, because the phone shows the registered IP that is different from what I see in whatismyip. Could it be the problem? Problems with NATting RTP usually result in no inbound voice, but outbound should be OK...
I wonder if there's a packet sniffer for Android so I could check the traces, LOL.
Whoever has some success doing SIP calling over Rogers/Fido 3G, please help me out.
Thanks!
Shameless self-bump.
Guys, I wonder if nobody knows, or nobody cares? I know it's most likely wrong forum to ask, please push me in right direction...
esokolov said:
Folks, please give me a hand!
I have the Note from Rogers Canada, upgraded to CM9 release, my provider is Fido, and I'm struggling with getting VoIP work over 3G.
1. Native ICS client. It's OK on WiFi, and on 3G the call is being established in and out, but no sound either direction. I heard 3G calling was blocked in GB client, and there was even a method tweaking the APK to make it work, but obviously something is very different in ICS - that tweak is not applicable - I can't find proper file in this APK.
2. cSipSimple - does not work at all, makes the phone acting weird. Well, last update was in 2011, maybe not compatible with ICS at all.
3. SipDroid - crashes.
4. Dell Voice - crashes.
My provider is freephoneline.ca, and I'm testing VoIP with it without success. I'm a network engineer with rich VoIP experience, and run at home a sophisticated FreePBX setup accessible from Internet. I've tried to register my Note on my home PBX as an extension, and I see same behavior - phones ring, calls establish, but no sound.
I don't understand where's the trouble exactly. Is it the Note, or CM9, or my provider is allowing SIP but blocking RTP? I see that all three Fido's APNs are doing NAT, because the phone shows the registered IP that is different from what I see in whatismyip. Could it be the problem? Problems with NATting RTP usually result in no inbound voice, but outbound should be OK...
I wonder if there's a packet sniffer for Android so I could check the traces, LOL.
Whoever has some success doing SIP calling over Rogers/Fido 3G, please help
Thanks!
Click to expand...
Click to collapse
I had a similar setup on Telus, and everything works alright. And then I tried Rogers 3G, there is only one way audio, I can't hear anything. But the other side can hear me. And also, my phone can't receive incoming either.
It's probably a problem/restriction with Rogers.
thunderzhao said:
I had a similar setup on Telus, and everything works alright. And then I tried Rogers 3G, there is only one way audio, I can't hear anything. But the other side can hear me. And also, my phone can't receive incoming either.
It's probably a problem/restriction with Rogers.
Click to expand...
Click to collapse
Confirmed, with latest CSipSimple nightly build (Jeez, they didn't release since 2011!!!) I was able to make calls, now with one way audio (out), outbound but not incoming calls, and if the remote party hangs, the phone does not detect it.
Those symptoms are familiar - NAT can't properly handle UDP inwards. Both SIP and RTP are affected. Enabling STUN did not help either.
Well, I'm going to buy data only SIM from Bell, stay tuned...
esokolov said:
Confirmed, with latest CSipSimple nightly build (Jeez, they didn't release since 2011!!!) I was able to make calls, now with one way audio (out), outbound but not incoming calls, and if the remote party hangs, the phone does not detect it.
Those symptoms are familiar - NAT can't properly handle UDP inwards. Both SIP and RTP are affected. Enabling STUN did not help either.
Well, I'm going to buy data only SIM from Bell, stay tuned...
Click to expand...
Click to collapse
bell will definitely work, their 3G network is just not as good as rogers'
Linphone can receive incoming, but one way audio too
thunderzhao said:
bell will definitely work, their 3G network is just not as good as rogers'
Linphone can receive incoming, but one way audio too
Click to expand...
Click to collapse
Well, recently I've been at Rock Point (Lake Eerie), and both my personal Note (Fido) and business Blackberry (Rogers) had no signal on 3G and even GSM, while my friend was chattering and browsing on his Bell connected phone... Maybe Bell's 3G coverage is spotty, but so is Rogers. I've seen too many times that Rogers drops to GSM with no apparent reason, and that means no decent data for VoIP.
We'll see. I'm aiming at LTE anyways, and Bell's LTE spot is WAY bigger according to their official coverage maps.
Someone has to be a guinea pig for new technologies. I hate the idea of paying $70 for CityFido + data, while I could pay $25-$35 for Bell's flex plus $0 for FreePhoneLine.
esokolov said:
Well, recently I've been at Rock Point (Lake Eerie), and both my personal Note (Fido) and business Blackberry (Rogers) had no signal on 3G and even GSM, while my friend was chattering and browsing on his Bell connected phone... Maybe Bell's 3G coverage is spotty, but so is Rogers. I've seen too many times that Rogers drops to GSM with no apparent reason, and that means no decent data for VoIP.
We'll see. I'm aiming at LTE anyways, and Bell's LTE spot is WAY bigger according to their official coverage maps.
Someone has to be a guinea pig for new technologies. I hate the idea of paying $70 for CityFido + data, while I could pay $25-$35 for Bell's flex plus $0 for FreePhoneLine.
Click to expand...
Click to collapse
finally got it working on rogers 3g with pbxes.org, and then add freephoneline as a truck, csipsimple works fine
thunderzhao said:
finally got it working on rogers 3g with pbxes.org, and then add freephoneline as a truck, csipsimple works fine
Click to expand...
Click to collapse
Hmmm, I wonder how you did it, can't make it work.
Okay, now I'm on Bell 3G (no LTE yet).
1. Registering with FPL directly gives me outbound calls OK, inbound call get voicemail (on 3G), STUN has no effect. WiFi calling is fine.
2. Registering through PBXes and FPL - outbound calls even to VM gives me "488 / Not acceptable here" on 3G, works OK on WiFi. Incoming calls make my cell ring, but when I pick up the call I'm getting same 488 on 3G. What's wrong here?
Will try it on Fido 3G...
esokolov said:
Hmmm, I wonder how you did it, can't make it work.
Okay, now I'm on Bell 3G (no LTE yet).
1. Registering with FPL directly gives me outbound calls OK, inbound call get voicemail (on 3G), STUN has no effect. WiFi calling is fine.
2. Registering through PBXes and FPL - outbound calls even to VM gives me "488 / Not acceptable here" on 3G, works OK on WiFi. Incoming calls make my cell ring, but when I pick up the call I'm getting same 488 on 3G. What's wrong here?
Will try it on Fido 3G...
Click to expand...
Click to collapse
488 means incompatible codec, pbxes only accept ilbc,
Are you using csipsimple?
thunderzhao said:
488 means incompatible codec, pbxes only accept ilbc,
Are you using csipsimple?
Click to expand...
Click to collapse
Yes, and it was a CSipSimple glitch.
By default it has SILK + PCMU + PCMA. I've left only PCMU and it stopped working on 3G only (WiFi was OK). Resetting CSipSimple to defaults resolved it. Weird...
BTW I doubt that PBXes only accepts ILBC, there's quite a number of codecs mentioned in their online help.
thunderzhao said:
finally got it working on rogers 3g with pbxes.org, and then add freephoneline as a truck, csipsimple works fine
Click to expand...
Click to collapse
I've managed to recreate this eventually. I don't know what's so special about PBXes, but yes it works fine with both Fido and Bell 3G. Thanks for the clue! Looks like I'm going to eliminate my home FreePBX and switch to PBXes.
However, sound is choppy like hell on both, barely usable. And I'm still struggling to get LTE on Bell's SIM, hope it will improve things.
One more question - phonebook in my Android has all the numbers in international format - +1-xxx-xxx-xxxx, +7-xxx-xxx-xxxx etc. When I dial directly from my address book into CSipSiple->PBXes->FPL, FPL rejects the call saying it's not covered by my plan. I believe I need substitute +1 with 1, +7 with 0117 and so on, but how do I do this? PBXes is based on FreePBX, and its rules use + as a special character for adding prefixes I believe...
esokolov said:
Yes, and it was a CSipSimple glitch.
By default it has SILK + PCMU + PCMA. I've left only PCMU and it stopped working on 3G only (WiFi was OK). Resetting CSipSimple to defaults resolved it. Weird...
BTW I doubt that PBXes only accepts ILBC, there's quite a number of codecs mentioned in their online help.
Click to expand...
Click to collapse
you are right, pbxes accept pcmu as well, but i thought it's too heavy for 3g, they allow g729a "PASSTHU" only to paid users.
for the choppiness, sip require packets loss way lower than 1%, i'm still trying to figure out what to do about that
esokolov said:
I've managed to recreate this eventually. I don't know what's so special about PBXes, but yes it works fine with both Fido and Bell 3G. Thanks for the clue! Looks like I'm going to eliminate my home FreePBX and switch to PBXes.
However, sound is choppy like hell on both, barely usable. And I'm still struggling to get LTE on Bell's SIM, hope it will improve things.
One more question - phonebook in my Android has all the numbers in international format - +1-xxx-xxx-xxxx, +7-xxx-xxx-xxxx etc. When I dial directly from my address book into CSipSiple->PBXes->FPL, FPL rejects the call saying it's not covered by my plan. I believe I need substitute +1 with 1, +7 with 0117 and so on, but how do I do this? PBXes is based on FreePBX, and its rules use + as a special character for adding prefixes I believe...
Click to expand...
Click to collapse
for the number formats, since i have all numbers stored on google voice, i went there and deleted all "+" and "-"
in csipsimple, there's an option called filter, i think you can reformat there
a few more tweaks for the choppiness, I disabled echo cancelling since sound from ear piece is not likely to reach microphone.
I also have trouble with the new csipsimple, when i use ilbc, it will freeze after about 30 seconds.
if you directly connect to freephoneline.ca, you need to use PCMU in order to receive phone call over 3G, somehow freephoneline disabled g729a on incoming calls.
so much for today's tweaking. good luck, let me know what you find out
thunderzhao said:
you are right, pbxes accept pcmu as well, but i thought it's too heavy for 3g, they allow g729a "PASSTHU" only to paid users.
for the choppiness, sip require packets loss way lower than 1%, i'm still trying to figure out what to do about that
Click to expand...
Click to collapse
SIP as signalling protocol is doing fine. RTP transport for audio is a problem.
I believe nothing can be done over 3G. I'm trying to make it work over LTE - it's supposed to be much better.
However I figured out that unlocked I717R (Rogers) does not connect to Bell's LTE cloud however it should.
I'm going to flash the Bell's radio and try again. I wonder if there's just Bell's baseband for ICS I can download and burn with Odin. I have only found full stock ICS for Bell, and that's a long and messy update path.
esokolov said:
SIP as signalling protocol is doing fine. RTP transport for audio is a problem.
I believe nothing can be done over 3G. I'm trying to make it work over LTE - it's supposed to be much better.
However I figured out that unlocked I717R (Rogers) does not connect to Bell's LTE cloud however it should.
I'm going to flash the Bell's radio and try again. I wonder if there's just Bell's baseband for ICS I can download and burn with Odin. I have only found full stock ICS for Bell, and that's a long and messy update path.
Click to expand...
Click to collapse
not very experienced with radio band and stuff, but have you tried getril? heard it's a very easy app to do this
Galaxy Note not supported yet.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
thunderzhao said:
good luck, let me know what you find out
Click to expand...
Click to collapse
Ok, another report.
1. After upgrading radio from Rogers to Bell, Bell LTE is pretty solid and stable while I'm in GTA.
2. Generally, VoIP over 3G is crap, both Bell and Fido/Rogers. VoIP over LTE is mostly OK. No surprise.
3. CSipSimple cannot properly handle Bluetooth handover. By some reason, the call always starts on speakerphone, then has to be routed manually either to BT or earpiece.
4. SIP keepalives are draining battery really fast, no matter if it's Wifi, 3G, or LTE.
5. PBXes.org is GROSS... I've stopped and dismissed my home FreePBX.
Fido has just started offering LTE. Tonight will try and upgrade my SIM card. I wonder though if I need to flash my radio back to Rogers to make it work...
General conclusion - VoIP over cell data is not ready yet for general use. However, geeks like me can save a few cents...
A few questions:
1. Is it possible to block voice cellular calls in and out? My Bell SIM card 'for tablets' still allows voice calls, and every time I'm hitting the wrong button I'm making 40 cents pay-per-minute charge. Customer service says it cannot be blocked on their side.
2. Is there any way to route SMS messages to VoIP and vice versa?
3. Is there a number portability between cell networks and VoIP operators (Canada and US, just to see a big picture)?
I believe this discussion is off-topic here. Can someone suggest a proper forum?
if you use csipsimple, you can disable mobile, if you use stock phone app, you can set use internet call only.
fongo supports sms now, i use google voice, with simonics
canadian numbers can port to fongo, US number can port to google voice
esokolov said:
Ok, another report.
1. After upgrading radio from Rogers to Bell, Bell LTE is pretty solid and stable while I'm in GTA.
2. Generally, VoIP over 3G is crap, both Bell and Fido/Rogers. VoIP over LTE is mostly OK. No surprise.
3. CSipSimple cannot properly handle Bluetooth handover. By some reason, the call always starts on speakerphone, then has to be routed manually either to BT or earpiece.
4. SIP keepalives are draining battery really fast, no matter if it's Wifi, 3G, or LTE.
5. PBXes.org is GROSS... I've stopped and dismissed my home FreePBX.
Fido has just started offering LTE. Tonight will try and upgrade my SIM card. I wonder though if I need to flash my radio back to Rogers to make it work...
General conclusion - VoIP over cell data is not ready yet for general use. However, geeks like me can save a few cents...
A few questions:
1. Is it possible to block voice cellular calls in and out? My Bell SIM card 'for tablets' still allows voice calls, and every time I'm hitting the wrong button I'm making 40 cents pay-per-minute charge. Customer service says it cannot be blocked on their side.
2. Is there any way to route SMS messages to VoIP and vice versa?
3. Is there a number portability between cell networks and VoIP operators (Canada and US, just to see a big picture)?
I believe this discussion is off-topic here. Can someone suggest a proper forum?
Click to expand...
Click to collapse
thunderzhao said:
if you use csipsimple, you can disable mobile, if you use stock phone app, you can set use internet call only.
fongo supports sms now, i use google voice, with simonics
canadian numbers can port to fongo, US number can port to google voice
Click to expand...
Click to collapse
Thanks thunderzhao!
At the moment I decided to stop my VoIP over cellular experiments, this is not productive.
First, Fido has just offered unlimited national calling + 2Gb of data + convenience pack, all for $56, and it's a killer.
Second, new mobile version of Skype, however not SIP based, is soooo much simpler to deal with than SIP solutions. It has a super clear voice Skype-to-Skype (and video too), works seamlessly over firewalls and NAT, and has a decent quality over both HSPA and LTE.
Third, VoLTE is on the horizon (so I believe), and it will completely change the landscape of mobile services, plans, and prices.
Switching to waiting mode.
Fongo crashes on cm but works fine for me on cm10 and most touchwiz ICS ROMs.

Anyone using this phone with AT&T in the US?

I love this phone....there, I said it. But it's driving me crazy.
I bought it from a Chinese retailer, who shipped it with X821 firmware, but the box states that it's an X820. I doubt there is any difference in the hardware.
I would have left everything as it was, but I can't seem to make phone calls (don't have a data plan yet...yeah, I know....) with anything other than 2G, and that is about to go extinct. When I set it to WCDMA, it shows a UMTS connection, with no carrier designation, but the tower is the same one I connect to with 2G. The phone does sometimes show an AT&T 3G connection in the status bar, but I can't make calls, even though I have full signal. When I place the same SIM in my old HTC Inspire, the same monitoring app shows "UMTS - AT&T HSDPA+" and works just fine.
I'm at my wits end. I have rooted, installed TeamSpain recovery, replaced the firmware with the X829 and even tinkered with the frequency configurations through DFS Studio (which did a lot of complaining, and I'm still not sure if the changes stuck 100%). I also played with APN settings and tried the SIM in different slots, both alone, and with another SIM. And after all of that, still no progress in getting this phone to use a 3G or 4G connection to make calls. If I don't set it to "GSM only", no phone calls in or out. I'm essentially right under a tower, so signal shouldn't be an issue.
If anyone is using the same provider in the US, and is not having these kinds of issues, I'd really appreciate hearing what firmware you are using, and/or what you did to get things working.
I am using it on x820 with official stock 0.17s firmware, and did a dirty flash to cuoco92's 17s firmware. Everything works including HD voice calls, and full LTE.
xterminater07 said:
I am using it on x820 with official stock 0.17s firmware, and did a dirty flash to cuoco92's 17s firmware. Everything works including HD voice calls, and full LTE.
Click to expand...
Click to collapse
I tried this, as well as the Remix ROM. In fact, I think I've tried just about everything, without success. At one point, I had one of the apps indicating a 4G connection, but the phone diagnostics showed GSM (2G). Even the apps aren't all sure what to make of what's going on with the connections reported by this phone.
Currently on the cuoco92 v35 ROM. When WCDMA is enabled, I see simply a good UMTS connection , sans carrier name, in the "Network Cell Info Lite" app, and no ability to make calls. I also often (but not always) see the "AT&T 3G" sign. 4G or LTE never shows at all, even though the diagnostics show that the phone is communicating with an LTE transmitter, when preferred network is set to "unknown". It won't even let me set things like "LTE only".
Any chance you could set your phone to WCDMA and see what the "Network Cell Info Lite" app shows you? Anyone else with this phone on AT&T?
BTW, I am now using a data plan, which I thought might make a difference. It doesn't. EDGE data only for me . New SIM card is on the way, but my hopes aren't high.
Is it possible for a Chinese seller to have borked the phone so thoroughly with their x821 ROM (it's an x820 marked phone), that it keeps any subsequent radios from flashing properly? I don't know how/why it would work for some and not others.
Starting to really dislike this "phone"......it's more of tablet at this point.
Thanks.
I think APN is not set for AT&T
try this:
"Main steps
To use data services on our network with a non-AT&T device, you may need to program the data settings. The sections below provide the correct settings and steps for programming based on your device type and operating system.
.
Access the Settings menu.
Locate and select Wireless & Networks or More Networks.
Select Mobile Networks.
Select Access Point Names.
Locate and select the option to add a new APN. This is usually accessed by a + symbol on the screen or by tapping the menu button.
Program each field using the settings below.
Save the changes to return to the APNs menu and select the new APN.
Name ATT Phone
APN phone
Proxy Not set
Port Not set
Username Not set
Password Not set
Server Not set
MMSC
MMS proxy
MMS port
MCC 310
MNC 410
Authentication Type None
APN type default
APN protocol IPv4
Bearer Unspecified
Note: If you are unable to program your device following the steps above, refer to your user manual or contact the manufacturer for assistance."
Cadet_C said:
I think APN is not set for AT&T
Click to expand...
Click to collapse
Thanks, but I wish it were so simple. I have tried this, and other APN settings. None work to get this phone to be usable on anything other than 2G.
I just received and activated the replacement SIM. Still no improvement. While typing this, I have Network Cell Info Lite app running, and with the Set Preferred Network Type showing "Unknown" in the phone's diagnostic screen, It will switch randomly between "EDGE AT&T" (which works fine) and "UMTS -" (which is useless). Both have strong signals. For a split second before it switched to "UMTS-", the app showed "GPRS AT&T", but only for a split second before it kicks over to "UMTS-".
I wish someone using this "phone" on AT&T in the US, would run this app to compare notes. It may be that that the phone works fine on a full implementation of LTE (i.e. in locations where AT&T have already deprecated 2G) but not in other areas. Still, that doesn't seem to explain why this phone seems unable to register on the same 3G network, used easily by my other phone, with the very same APN settings and SIM.
You would have to call att and check if they turned our phone on to use lte. If your phone is not "registered" as an LTE capable phone it wouldn't be able to pick it up. This phone has all the bands needed for AT&T because I am using it now. All LTE work straight out the box, and i'm on the latest 19s cn rom
xterminater07 said:
You would have to call att and check if they turned our phone on to use lte. If your phone is not "registered" as an LTE capable phone it wouldn't be able to pick it up. This phone has all the bands needed for AT&T because I am using it now. All LTE work straight out the box, and i'm on the latest 19s cn rom
Click to expand...
Click to collapse
I'm a bit confused. Is this what you did to achieve proper function of this device? I.e. calling AT&T and getting them to do this for you? My conversation with their tech person didn't seem to bear fruit in this regard.
Also, which slot do you have the SIM card in? I've used the stock 17s and now on cuoco92 v35 ROM. There definitely seems to be a difference in how the network settings behave, based on the location of the SIM. At one point, after selecting BAND 6 (when it would let me), the phone showed a constant "AT&T 3G" connection, but it was useless. No calls and no data.

A2017G Oreo Enhanced LTE Services Server Error

I have tried this new feature coming with the stock Oreo ROM and received a message from my mobile carrier initially, welcoming me to WiFi calling. All network settings seemed to be working fine, I was also browsing internet with no problems, all apps were connecting and responding as expected. However the first time I tried dialing one of my contacts I've got a message "Server error. Try again later." on the dialing screen itself. It looked like the call couldn't be connected. This happened to all outgoing calls, I suppose to all incoming also although I couldn't confirm that.
I tried many things like restarting the phone, turning data on and off, going into flight mode and disabling it, in the end I reset all network settings disabling LTE advanced services before doing that and enabling them again after the reset, but I still get that error. If I disable LTE advanced, all calls get connected with no problems.
Does anyone know if this is something with a list of supported devices explicitly enabled by the mobile carrier in their network? I am considering calling my carrier for more information but the fact itself I have got a welcome message means the device has been detected as part of the advanced services network. Perhaps there are some network settings I need to enter? Anyone ever used Axon 7's WiFi calling/advanced LTE features on any network?
Does that maybe include VoLTE which the carrier may not support?
https://www.4g.co.uk/what-is-volte/
Well according to the link provided and what I know, LTE is supported by my operator, but I wonder if it needs to be specifically tailored to a phone model by them and/or the 8.0 update by itself is not providing such functionality or it is limited by default. And I think it may be the first since ZTE products are never on the list of supported phones by any operator. But I couldn't claim it for sure as otherwise ZTE would not have included it at all with the 8.0 ROM and there are so many basic or very old models like LG K8 or Microsoft Lumia 550 that are supported.
Has anyone tried using "LTE advanced" on their 8.0 yet?
Menergy said:
Well according to the link provided and what I know, LTE is supported by my operator, but I wonder if it needs to be specifically tailored to a phone model by them and/or the 8.0 update by itself is not providing such functionality or it is limited by default. And I think it may be the first since ZTE products are never on the list of supported phones by any operator. But I couldn't claim it for sure as otherwise ZTE would not have included it at all with the 8.0 ROM and there are so many basic or very old models like LG K8 or Microsoft Lumia 550 that are supported.
Has anyone tried using "LTE advanced" on their 8.0 yet?
Click to expand...
Click to collapse
LTE Advanced = Volte
If your carrier does not support Volte, keep this option off.
WiFi Calling is something separate and not related.
If your carrier does not support WiFi calling, keep this option off.
You should still get LTE service with both of these options off. I personal find WiFi calling to work poorly, so I leave it off even though my carrier supports it. (TMobile US)
Also, there is a Q and A section for these types of posts. Don't post questions in the Guides and News section please.
Thanks for the input. Both of these options are reported to be supported by my carrier on their website. Also I always had LTE before 8.0 so simply wanted to try the new "HD voice and advanced communication service" as described in the latest firmware.
About posting this thread in the news & discussion section, this only relates to Oreo which was only recently released to the public so it is a completely new feature for the Axon. Most of the other threads are too general and since there will still be many people with 6.1 and 7.0/7.1, I would have hardly got any response whatsoever in there. For now I will keep this new option off and will contact my carrier for the support of the Axon and ZTE in general.

Umidigi F1 and GSIs: Getting them to work with Verizon

Good day all,
I'm encountering an issue: a fairly new phone of mine (Umidigi F1) loses its ability to get data from Verizon Wireless when I install Treble Generic System Images (AOSP-based, typically derived from phhusson's et al work). For clarification, despite being from a small Chinese company, the phone normally fully supports VZW (4G LTE data, calls, and text). While on those GSIs, I get a signal and am able to call people with it, but there is no data from the connection.
The APN settings appear to match the ones that work normally (stock F1 and a Pixel 2), so despite not being able to edit or add a new one, I am led to believe this isn't the culprit. Next, I looked at build.prop; the model, device, and brand info changed from the default states and I believe that VZW may be strict enough not to allow the altered info on their network. Attempting to modify build.prop causes a boot loop, though.
Anybody have any thoughts on what I can do? One of the comments at the top of the build.prop file indicates that it is autogenerated by buildinfo.sh. Should I attempt to modify that instead? Or maybe something else?
Veiran said:
Good day all,
I'm encountering an issue: a fairly new phone of mine (Umidigi F1) loses its ability to get data from Verizon Wireless when I install Treble Generic System Images (AOSP-based, typically derived from phhusson's et al work). For clarification, despite being from a small Chinese company, the phone normally fully supports VZW (4G LTE data, calls, and text). While on those GSIs, I get a signal and am able to call people with it, but there is no data from the connection.
The APN settings appear to match the ones that work normally (stock F1 and a Pixel 2), so despite not being able to edit or add a new one, I am led to believe this isn't the culprit. Next, I looked at build.prop; the model, device, and brand info changed from the default states and I believe that VZW may be strict enough not to allow the altered info on their network. Attempting to modify build.prop causes a boot loop, though.
Anybody have any thoughts on what I can do? One of the comments at the top of the build.prop file indicates that it is autogenerated by buildinfo.sh. Should I attempt to modify that instead? Or maybe something else?
Click to expand...
Click to collapse
many MTK soc devices on pis gsi have this issue with sim based data connection. Some even have issue with sms / text.
I did at one point have data working on one of my mtk phones, only when switched connection typs to 3G. But that was not acceptable because way too slow speeds. A solution may come. but i do not know when.
umidigi-f1-tag
I just got a umidigi f1 and am trying to get it working on Verizon. I have talk ant text(sms and mms) working through sim1. However, like you I can't get data to work.
The odd thing is that I can't seem edit the apn settings. That section is missing from my mobile networks section. I am on a stock rom, not rooted.
The sim I was using is a page plus sim. It gets service though Verizon via Tracphone.
I think my issue is that my apn is not set correctly.
Success!
Go to the phone dialer and dial
*#*#4636#*#*
Go to phone information and change your preferred network type to lte only
The default is lte/umts which probably just good for GSM phones
You should see a lte connect. Hit the ping test to verify if you can ping Google.com
Edited to say, the phone is kind of flaky with regards to the APN setting so ymmv. It was working for me for a while then stopped...
Edited 2: Okay I figured it out. To reveal the Apn menu on Verizon, change the preferred network to LTE only as above, then unselect 4g in the Mobile Network section for the Verizon Sim. Restart the phone. Next time you go to the Verizon section, there should be an Apn setting item. Create the proper Apn for Verizon because the default probably does not work. For me, I needed tracfone.vzwentp.
Here's the phone info screen
Here's the mobile network section for the Verizon Sim. Nonintuituve but had to disable 4g toggle but doesn't have any effect on speed. After a reboot, Apn section shows up
Hellom did you get it to work on Verizon? If so what are the full steps?
Make sure your Verizon sim card is in slot 1. Sadly, it seems like Verizon works best in that slot so not able to use a micro SD card.
On 2 other phones running on Red Pocket Verizon, everything just worked. No need to do anything extra.
Also disable wifi calling.
On my other phone running on tracfone/page plus, I had to do the extra steps in the previous posts above.

Anybody doing VoWiFi on Z5c as "officially" supported by your carrier? ...

My carrier is very particular about which phones they open up the Wi-Fi Calling feature to. Generally, they'll only activate and support the feature on phones that they have directly sold & are running carrier-branded firmware (ugh).
I've managed, however, to get Wi-Fi Calling working on my carrier via my Z5c, which is definitely not a supported model. (Long story.) And it all works great...except that I cannot for the life of me get MMS to function over Wi-Fi. I know what the basic underlying issue is that is preventing this from working (APN type 'mms' is not able to be used as a bearer on the IWLAN RAT), but have not yet found a way to work around it.
This leads me to ask: is there anybody out there (still) using a Z5-family phone that has working Wi-Fi Calling actively supported by your carrier? And if so, can you send and receive MMS when you are only on Wi-Fi (Airplane mode on with Wi-Fi re-enabled) without problems?
I mean, if this isn't a supported configuration/feature on the Z5, period, then I'd like to know that before I waste further weeks banging my head against a wall that's never going to budge... It seems unfathomable to me that any phone with Wi-Fi Calling *wouldn't* support MMS over Wi-Fi, but this is a rather early VoWiFi implementation, so who knows.

Categories

Resources