Can anyone out there see if they get the same behavior as me?
I'm in a band 12 area, with a 4 bar LTE signal.
Wifi calling is enabled but CELLULAR PREFERRED, I'm connected to the T-Mobile ASUS router on Verizon FiOS (2.4, 5ghz, doesn't matter).
Long press 1 to get into your voicemail. What you expect to hear:
"You have no new messages in your mailbox..." is chopped off and what I hear is:
"mailbox..."
If I turn off wifi, the issue goes away. If I turn off wifi calling, the issue goes away. If I change the wifi calling setting so that it uses wifi preferred or always (so the call is an actual wifi call), the issue goes away. If I force the phone to use HSPA, the issue goes away.
So even though the call isn't a wifi call, something about wifi calling and wifi, even though the call goes through VoLTE, is causing the start of a call be be chopped off.
At this point I have disabled wifi calling on my phone.
amarryat said:
Can anyone out there see if they get the same behavior as me?
I'm in a band 12 area, with a 4 bar LTE signal.
Wifi calling is enabled but CELLULAR PREFERRED, I'm connected to the T-Mobile ASUS router on Verizon FiOS (2.4, 5ghz, doesn't matter).
Long press 1 to get into your voicemail. What you expect to hear:
"You have no new messages in your mailbox..." is chopped off and what I hear is:
"mailbox..."
If I turn off wifi, the issue goes away. If I turn off wifi calling, the issue goes away. If I change the wifi calling setting so that it uses wifi preferred or always (so the call is an actual wifi call), the issue goes away. If I force the phone to use HSPA, the issue goes away.
So even though the call isn't a wifi call, something about wifi calling and wifi, even though the call goes through VoLTE, is causing the start of a call be be chopped off.
At this point I have disabled wifi calling on my phone.
Click to expand...
Click to collapse
I have the same set up, I'll turn off WiFi and report back, as I've noticed the same issues...
Generic condescending signature line
---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------
Seems better... I'll keep it like this and see...
Generic condescending signature line
My theory on what's happening here is this:
While you're telling the system too use VoLTE and setting cellular preferred, it's starting the call on Wi-Fi calling and handing off to VoLTE.
The reasoning it's simple...when on Wi-Fi, cellular data is deactivated. VoLTE depends on cellular data. When you start a call, it establishes it via Wi-Fi calling, and establishes the cellular data connection. Once that connection it's up, handover occurs, but this causes a few seconds of Audio loss because it has to set that back up.
You can see the delay yourself by turning off Wi-Fi, then turn off mobile data. Turn mobile data back on and you'll see the delay between enabling and being reconnected too the LTE network.
Hope this helps explain the issue. It's a handoff delay caused by having to reconnect mobile data and LTE, and you likely wouldn't notice for normal calls, but VM answers immediately.
Sent from my LG-H901 using Tapatalk
toastido said:
My theory on what's happening here is this:
While you're telling the system too use VoLTE and setting cellular preferred, it's starting the call on Wi-Fi calling and handing off to VoLTE.
Click to expand...
Click to collapse
I understand what you're saying and thanks for the explanation. And I realize that when wifi is on, data is going through wifi and would have to switch to LTE for a call. So this does make sense to some extent. But.... if wifi is on but wifi calling is not, the calls happen quickly and are not chopped off. But the same holds true - the data is going through wifi and would have to switch to LTE. Your reasoning explains it for wifi calls always and wifi calls never.
amarryat said:
I understand what you're saying and thanks for the explanation. And I realize that when wifi is on, data is going through wifi and would have to switch to LTE for a call. So this does make sense to some extent. But.... if wifi is on but wifi calling is not, the calls happen quickly and are not chopped off. But the same holds true - the data is going through wifi and would have to switch to LTE. Your reasoning explains it for wifi calls always and wifi calls never.
Click to expand...
Click to collapse
That's because with wifi calling ON, the call is initially set up through wifi calling, and has to hand over once the mobile data connection is up, LTE is negotiated, and VoLTE is negotiated. If wifi calling is OFF, the call is established via GSM, then (optionally, but not usually) handed over to VoLTE once LTE is up and VoLTE is negotiated.
I've done work in the industry with VoLTE, and my day job involves VoIP, so it's not as simple as one might think. Believe it or not, GSM to VoLTE handoff is much easier than WiFI calling to VoLTE. It still explains it, believe it or not, it's just a matter of which path. It's also harder to hand off from VoLTE to GSM when you roam out of a VoLTE area... which is the primary cause for VoLTE call drops.
toastido said:
Believe it or not, GSM to VoLTE handoff is much easier than WiFI calling to VoLTE.
Click to expand...
Click to collapse
Why haven't they implemented that then? That hurts them in the rootmetrics etc. scores where they'd test phone calls.
For example, band 12. You make a VoLTE call, drive to out of range of LTE and the call drops to HSPA or Edge. It nevers goes back to LTE. So when they're doing their tests, if the call switches away from LTE, then they drive to an area that is band 12, when the HSPA signal gets weak, the call gets dropped even though there's a great band 12 signal.
amarryat said:
Why haven't they implemented that then? That hurts them in the rootmetrics etc. scores where they'd test phone calls.
For example, band 12. You make a VoLTE call, drive to out of range of LTE and the call drops to HSPA or Edge. It nevers goes back to LTE. So when they're doing their tests, if the call switches away from LTE, then they drive to an area that is band 12, when the HSPA signal gets weak, the call gets dropped even though there's a great band 12 signal.
Click to expand...
Click to collapse
That's actually a great question...and unfortunately one I can't answer or even begin to speculate on...
¯\_(ツ)_/¯
Sent from my LG-H901 using Tapatalk
toastido said:
That's actually a great question...and unfortunately one I can't answer or even begin to speculate on...
¯\_(ツ)_/¯
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Back to my original point though - what I'm hearing is that this isn't unique to the V10. I'm wondering why this isn't all over the internet where people are noticing that the start of their phone call is missing when wifi calling is enabled but they've set it to cellular preferred (which is NOT the default BTW).
Upon using wifi, my Redmi will hold 4G for an unknown amount of time, then suddenly either drop to HSPA, or UMTS depending on the region; as to my understanding this is what SIM Standby does where it just turns off data and leaves the voice and sms services online which is perfectly okay with me because in theory it saves power.
Though using T-Mobile, it doesn't play nice. It randomly drops services, then emergency calls only, then grabs service often switching frequencies, and it does this until I shut off Wifi, grabs 4G/LTE again, and I turn on wifi. Is there an option or a build.prop edit I can do to turn off SIM Standby?
I have a CDMA Samsung Note 3. The phone can run on GSM networks just fine. First initial problem I had was I couldn't get any signal strength to do anything. Now I can text and use data, however attempting to place a call immediately ends like within a second. What setting would cause this to happen?
Background:
LeEco LePro3 (LEX727) bought a year ago and in service since that time.
Not rooted. (Nor do I wish to root, if that was even possible.)
Use Nova Launcher for better desktop experience
StraightTalk on AT&T network. Indoors, usually shows LTE with 2 bars.
"Fully patched". LeEco EUI version 5.8.021S. (No LeEco Android updates available since 1/2017 as they pulled out of the USA market.)
Android 6.0.1.
Android security patch level January 1, 2017.
Handset worked fine for many months.
There was no obvious change or trauma to the handset (no drops, skills, weather exposure, etc.)
Lately, there have been data issues when WiFi is disabled.
(Everything still works with a WiFi connection.)
Not all features work with the StraightTalk/AT&T data connection when WiFi is disabled.
StraightTalk/AT&T data function details:
SIM card status
Signal strength -110 dBm 27 asu
Cellular network type LTE
Service status Voice: In service / Data: In service
Cellular network state Connected
Phone works (can make & receive calls).
Simple text messaging works (can send & receive texts)
MMC messaging works (can send & receive MMC texts)
(Ookla) Speedtest App works with good speeds.
Google Chrome browsing does not work "ERR_EMPTY_RESPONSE"
Firefox browsing does not work "Secure Connection Failed The connection to the server was reset while the page was loading."
Gmail does not download messages, sent messages are stuck in Outbox ("Queued")
Google Maps does not work "Can't connect to Maps".
Google Play does not work. When searching for Apps, "No internet connection. Make sure Wi-Fi or cellular data is turned on, then try again."
Troubleshooting steps taken:
Adjust AT&T APN settings used as per StraightTalk Tech Support.
Change out StraightTalk/AT&T SIM card with StraightTalk Tech Support assistance.
Factory/Hard Reset with reinstallation of all accounts & Apps.
Anyone know how to fix my web data issue? (Or know what further tests/observations to make?)
I am experiencing an intermittent problem where Wifi Calling gets disabled on incoming/outgoing phone calls. The button starts out looking enabled, but the second I accept an incoming call or dial outward I notice the Wifi Calling icon gets grayed out. Once the icon gets grayed out, the call experience is equivalent to having Wifi Calling enabled. In other words, it seems to be dropping back to LTE. I have very poor reception in my office so LTE calls drop out very frequently.
How do I go about troubleshooting the underlying cause?
Background information:
* The phone is an unlocked, unrooted Samsung S9+ running Android 8.0.0. The model number is SM-G965W. The build number is R16NW.G965WVLU2ARF7.
* My service provider is Rogers (Canada). They have noticeably worse LTE service than my previous provider (Telus) but it's unclear whether this is the cause of the problem.
* The phone is connected to my home router, running OpenWRT 18.06.1.
* The internet connection is 25Mbps down, 10Mbps up.
Are there any sort of log files I could look into which would indicate why Wifi Calling is getting disabled, or dropping to LTE?
If this forum isn't the right place to ask, where else could I ask?
Thank you,
Gili