Jump to content

Connection Lag When Making Phone Calls


Recommended Posts

For a while now I've noticed that when making phone calls from my S3 it takes anywhere between 10-20 seconds before I start to hear the line ringing.  It doesn't seem to matter if I have a really strong or a really weak signal, the delay is always there.  I've also noticed that if I'm roaming (haven't noticed which carriers or if it really matters) the call starts ringing almost instantly, within just a second or two.

 

Has anyone else noticed this on either an S3 or other phones?  I would suspect a phone issue since it's only on the Sprint network, but I haven't tested any other phones.

 

Link to comment
Share on other sites

For a while now I've noticed that when making phone calls from my S3 it takes anywhere between 10-20 seconds before I start to hear the line ringing.  It doesn't seem to matter if I have a really strong or a really weak signal, the delay is always there.  I've also noticed that if I'm roaming (haven't noticed which carriers or if it really matters) the call starts ringing almost instantly, within just a second or two.

 

Has anyone else noticed this on either an S3 or other phones?  I would suspect a phone issue since it's only on the Sprint network, but I haven't tested any other phones.

 

I'm roaming on Verizon here in South Dakota and every call takes me 20-30 seconds to go through.  None of my roaming is instant like you noted.

 

Robert

Link to comment
Share on other sites

For a while now I've noticed that when making phone calls from my S3 it takes anywhere between 10-20 seconds before I start to hear the line ringing.  It doesn't seem to matter if I have a really strong or a really weak signal, the delay is always there.  I've also noticed that if I'm roaming (haven't noticed which carriers or if it really matters) the call starts ringing almost instantly, within just a second or two.

 

Has anyone else noticed this on either an S3 or other phones?  I would suspect a phone issue since it's only on the Sprint network, but I haven't tested any other phones.

On my S4 I experience it, I just end the call, and keep trying until it actually goes through. It happens on an airave, as well as out in Town. 

Link to comment
Share on other sites

For a while now I've noticed that when making phone calls from my S3 it takes anywhere between 10-20 seconds before I start to hear the line ringing.  It doesn't seem to matter if I have a really strong or a really weak signal, the delay is always there.  I've also noticed that if I'm roaming (haven't noticed which carriers or if it really matters) the call starts ringing almost instantly, within just a second or two.

 

Has anyone else noticed this on either an S3 or other phones?  I would suspect a phone issue since it's only on the Sprint network, but I haven't tested any other phones.

 

 

I have noticed this happing in areas that Sprint has capacity issues. Not sure if that is the reason. Just what I tell myself so I feel better.

Link to comment
Share on other sites

This has happened to me quite a few times, I would just hang up and just call back and it will go right through the second time.  A lot of times when I do reach the person I was trying to call they would tell me that their phone rang but then it hung up even though I never heard anything at all on my end when I had called the first time. 

Link to comment
Share on other sites

Long delays on outgoing calls are likely the network being overloaded, or having an issue. My semi-educated guess is possibly your phone is in the process of being transitioned from one tower/sector to another when you attempt to make the phone call, so it is waiting for that to complete first, possibly getting stuck and waiting for a timeout before it checks again. When you cancel the call and try again, your phone checks again immediately to see if it is in a transition and lets it go through since it isn't.

 

It also could be something somewhere on the network not making a connection properly when navigating through the labyrinth of the digital world to the endpoint you want. Anything inter-carrier will have a more likely chance of this happening since it transitions to a separate system, obviously.

 

In addition, ringing on modern digital telephones is entirely fabricated, there is nothing real about it. There is absolutely nothing on the network or technology side that requires a phone to ring. It is merely added in to let you know something is happening, as a holdover from previous inferior technology that literally used the telephone wires to "ring" the phone by pulsing the power through the line.

Link to comment
Share on other sites

On my S4 I experience it, I just end the call, and keep trying until it actually goes through. It happens on an airave, as well as out in Town. 

 

It normally goes through, just usually takes 10-20 seconds before I hear the ringing start.  (And I understand it's digitally generated and not a real ringing  :) ).  Rarely, it won't go through even after waiting a while and the call will just end without ever connecting.  This is very consistent when I'm on Sprint, never less than 10 seconds.

 

Also, I miss a lot of incoming calls with my S3 and have for a while.  I thought it was just network upgrades going on, and very well could be.  But, there have been several cases when my wife tries calling my S3 a few times and it doesn't ring.  Then will call my kid's iPhone 5 and it will ring.  And a few times tonight while I was on the way to the store she called and my phone never rang.  I was in the car and on a major road with very good coverage.

Link to comment
Share on other sites

It normally goes through, just usually takes 10-20 seconds before I hear the ringing start.  (And I understand it's digitally generated and not a real ringing  :) ).  Rarely, it won't go through even after waiting a while and the call will just end without ever connecting.  This is very consistent when I'm on Sprint, never less than 10 seconds. Also, I miss a lot of incoming calls with my S3 and have for a while.  I thought it was just network upgrades going on, and very well could be.  But, there have been several cases when my wife tries calling my S3 a few times and it doesn't ring.  Then will call my kid's iPhone 5 and it will ring.  And a few times tonight while I was on the way to the store she called and my phone never rang.  I was in the car and on a major road with very good coverage.

yeah if sfter 10 seconds I hang up and try again. I dont have the patience of 20 seconds or more for a phone call haha
Link to comment
Share on other sites

I compared my daughter's iPhone to my S3.  The few comparisons we made her call was connected in 3 seconds or less and mine was consistently 10-15 seconds.  To me it doesn't sound like the tower was overloaded or we both would have seen the same delays.

Link to comment
Share on other sites

On my S4 I experience it, I just end the call, and keep trying until it actually goes through. It happens on an airave, as well as out in Town. 

Yes, I raised the issue about the airave in another forum but it seems that when coming into range of the airave the phone switches from tower to aiave constantly for about 10 minutes then finally stays connected to aiave.  It has only started recently so I think it may be due to NV?  I thought the 2.5 has an 800mhz beacon to resolve that issue.

Edited by matt7701
Link to comment
Share on other sites

I just had this happen today on my S3 - took a while before the call started to go through. Not the first time it's happened either

 

Today I was out in a parking lot in an area that's been getting a lot of upgrades, so hard to tell.

 

Still happening to very consistently.  The iPhone 5 of my daughter never has this issue, roaming or not and neither does my wife's old Samsung Seek.  Very strange.

Link to comment
Share on other sites

I only have slow call connection when my signal is 1-2 bars on my iPhone 5. Overall calls connect alot faster then they did on AT&T when I had them. Back when I had my S3 it was the same, never a slow connection unless it was weak signal. 

Link to comment
Share on other sites

Guest kamiller42

My calls can take a while. I'm using a Nexus 5.

 

Even though the ring is an artificial replica of older technology, it's a great user feedback system. It let's the user know the call has gone through. I like it, but don't like when it take up to 20 seconds to hear it.

Link to comment
Share on other sites

My sister just complained about this with her samsung victory lte. I thought it was a google voice routing delay.

 

Sent from my SPH-P100 using Tapatalk 2

 

 

Hmmm...I do have Google Voice as my voicemail.  My daughter and wife (who don't have the lag) don't have Google Voice.  I thought it was only for voicemail and the call still went through Sprint as any other call would, but maybe I'm wrong there.

 

Another note, it's the same on 1x800.  For a while I had 1x800 on the testing SID and then it went away.  I thought they just turned it off after testing, but apparently I somehow reset my PRL back to the stock Sprint PRL.  After restoring the digiblur PRL I can now connect to 1x800 again.  Still taking a long time to connect.

 

Also, I've noticed that incoming calls sometimes only ring once on my phone and I don't have time to pick them up.  Other times they don't ring at all.  I've tried calling my cell from the home phone and I'll hear the six or so rings but my cell doesn't ring or rings only once and then goes to voicemail.  

Link to comment
Share on other sites

It's Google Voice that's been causing my problems.  I just disabled the Google Voice integration with my Sprint number and now calls go through immediately.  Tried while on 1x800, and roaming to several different numbers.  All calls were initiated right away with no delays.

 

Also, incoming calls started ringing on my phone much faster and I had time to answer before the call went to voicemail.  Tried calling my cell several times and it's much better.

 

So, not sure what I'm going to do at this point.  I like receiving e-mails or texts when I get a voicemail, and being able to get voicemails from the app on my phone or via the web when I can't listen to them on the phone (mainly at home where I don't have a great signal).  However, having all my calls come through to my phone is much more important.

 

Any thoughts?

 

EDIT:  When I disabled GV on the voice website, my phone showed a message saying there was a system update it was setting up services.  Don't know what it did, but it caused something to happen on my phone.

Link to comment
Share on other sites

I had a feeling it was a Google voice issue because every time I leave the G voice or Gmail website open and I get a call, the website always "rings" first before it gets to my phone. So I always know to get my phone ready. About a 5 second delay give or take. Phone calls aren't as big a deal to me. So I don't mind having the delay. And when I am in the subway or no signal at least I know if I have a missed call with Google voice. Especially since some people don't leave voice mail.

 

Sent from my SPH-L710 using Tapatalk

 

 

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • The DAS at LGA Terminal B actually has n41 at 100+20, but if you are deprioritized, good luck on the busy days, as all the bands are congested, even B41 and n41, with data being worse than 128kbps international roaming. It has SA active for n41 as well. The L train tunnel is actually 80+20 for n41, with SA n41 active. Speeds aren't anything compared to Philadelphia's DAS system that has n41 though. The gig+ upgrades are expanding, as eNBs 894588 (Sprint convert site) and 55987 can both pass 1 Gbps now. Clocked nearly 1.3Gbps on eNB 55987 today.
    • Hopefully this goes thru!  https://www.reddit.com/r/tmobile/comments/1211mh7/tmobile_files_another_sta_application_to/
    • Yup 80MHz C-band + 40MHz DoD for a total of 120MHz. They should be pretty well setup post-clearance. — — — — — Famous Verizon site on Atlantic referenced in this reddit post got moved to the top of the building next door. — — — — — Also looks like I mapped a T-Mobile oDAS node eNB 347812 in Brooklyn Heights. Streetview shows it as one of the CC nodes with no antenna on top as of May 2022 but this specific eNB was first mapped this month. I didn't notice that I mapped it until I got home but the range on it is significantly greater than the normal "antenna-less" nodes T-Mobile deploys. I'm wondering if it got upgraded to the new 5G oDAS design but I won't be able to check it out until next weekend.  
    • I didn't know they had access to 80 MHz of c-band that does change some things then once that's online
    • While I've been loath to update my Samsung devices past the May 2022 update to keep the Band Selection tool, I note that it looks like Android 14 is going to add Timing Advance for NR to the API.  (Was looking today as I have another Verizon A42 5G now that I'm going to unlock for T-Mobile, and wanted to figure out if I should let it update or not.)  Since I can technically make band changes from *#73#, on the A42 5Gs, I can probably live without the Band Selection tool if a later Android version adds something useful like TA values. I assume SCP will be updated to support that once it becomes publicly available.  The real question is whether or not the phones will support it.  My S21FE and A42 5G devices do on LTE, but I know the S22 and the A32 5G do not support it even on LTE, providing just zero in that field. - Trip
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...