Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Don't want to jinx myself, but today I had the best cellular coverage I have had since I switched to Verizon when the 5s came out. I installed Beta 3 yesterday. Today was my first day of using 10.1 away from home since I got my iPhone 7 last Monday. Never went below 1 bar of LTE today.

When leaving for home, Waze started immediately, and so did scrolling to my last place in my Beats 1 On Demand episode. Even on my 6s, it would take awhile for Waze to open and for Beats 1 On Demand to work properly despite my car being parked outside. The Dodgers game streaming audio from MLB At Bat did buffer a few times, but at the location I was at, it actually buffered less than normal for MLB At Bat. The speed test was better than Friday. Still though, 1.82Mbps Down/0.40Mbps Up on 2 bars of LTE not great. But I have never had great coverage in that old building with few windows.

Still too early to tell though. I'll be at other locations that have had these issues the rest of this week.
 
I updated to beta 3 as it was available, and have seen nothing better in regards to dropping service. I have 4 iPhone 7s and my wife's may be the worst, since her Maps app is completely useless, it hovers all over the map. Since she gets easily car sick and frustrated, it's amusing to me, it's the only thing that has put a smile on my face since all of this started.
 
If disabling VoLTE and leaving it on LTE Data (the temporary fix) only isn't correcting the problem for you, then your phone may actually be defective. The vast majority of phones experiencing this problem has to do with the tower handoff/switching behavior when VoLTE is turned on.

I would swap the phone if I were you as it sounds like the modem itself is having difficulty establishing connections.

I got a new phone and it fixed the issue. I also do not seem to be getting the VoLTE issue, but I haven't left my house yet so will post back again tomorrow.
 
  • Like
Reactions: JeffNT326
Mine was losing service all over the place again today...this is getting old quick. I thought it was improving but it's not. I can't even make fun of Samsung exploding phones at this point o_O
 
  • Like
Reactions: determined09
Lol pay it no mind. He says he didn't leave the house yet so he hasn't even seen the issue. It's been proven replacement or new devices don't solve the issue.

Good point.
[doublepost=1476279683][/doublepost]So I drove to work using the ATT sim and didn't have issues with cellular. Only issue I still have is Bluetooth and my car. But I believe there is a thread already on this.
 
Lol pay it no mind. He says he didn't leave the house yet so he hasn't even seen the issue. It's been proven replacement or new devices don't solve the issue.

I'd like to clarify that there appears to be two issues with regard to the "No signal" problem.

The first issue is what this entire thread is about: the iPhone 7 is dropping to no signal in areas known to have strong LTE signals as the phone is moving between towers. It then has difficulty re-establishing connections in an expedient way resulting in the "No Signal" indicator. The temporary fix to this problem is to turn off VoLTE. Apple and Verizon have said (at some point on some level) that they are aware of this problem and are working on a fix which iOS 10.1 B3 with Carrier v. 26.0 appears to address for the vast majority of users.

kokonutz explained that he or she (sorry unsure of pronoun) tried disabling VoLTE (leaving LTE data only) and installed iOS 10.1 B3. This did not solve the problem as the "No Signal" indicator was present even without moving.

This leads to the second issue which people searching for answers naturally find this thread to read about: some iPhone 7s have faulty modems/a-gps components or connections to the antenna structure that are causing them to lose signal. This issue extends beyond designated Verizon/Sprint phones as evidenced by similar experiences with T-Mobile and AT&T designated phones. For these individuals, swapping the phone has solved their issues.

This is the situation kokonutz falls under. If he begins to move between towers and experiences "No Signal" but is able to reacquire it with the replacement phone, then his replacement phone, with a properly functioning modem, is now operating under the first issue to which a software fix should potentially fix.

On another note, I've noticed the first issue is experienced by many in the NYC/Tri-state area (where I live). This leads me to think that there's an issue with tower network parameters or somehow the iPhone 7 is identifying itself in a way that is conflicting with network VoLTE handoff protocol. Either way, it seems a fix is on the way, and I've heard it could come out this week.
 
I hope that is true...Source?

I can't remember exactly which of these threads I read it in, but since I'm at work right, I'm not able to look for it now. I can search harder once I get home.

Post #930 in this thread is confirmation that Apple and Verizon have identified the problem.

Feel free to peruse these forums (I'm pretty sure it's in one of these):

https://discussions.apple.com/thread/7668994?start=180&tstart=0
https://community.verizonwireless.com/thread/918575
https://forums.macrumors.com/threads/uk-iphone-7-plus-wont-connect-to-4g.1997617/

I do want to affirm your point that if the phone is suffering from issue 1 in my previous post, obtaining a replacement will not fix the problem.
 
I can't remember exactly which of these threads I read it in, but since I'm at work right, I'm not able to look for it now. I can search harder once I get home.

Post #930 in this thread is confirmation that Apple and Verizon have identified the problem.

Feel free to peruse these forums (I'm pretty sure it's in one of these):

https://discussions.apple.com/thread/7668994?start=180&tstart=0
https://community.verizonwireless.com/thread/918575
https://forums.macrumors.com/threads/uk-iphone-7-plus-wont-connect-to-4g.1997617/

I do want to affirm your point that if the phone is suffering from issue 1 in my previous post, obtaining a replacement will not fix the problem.


I am pretty sure a new iOS release will come this thursday which will address this issue among other things.

I received a phone call from Apples Executive relations office after emailing tim cook and he said he would follow up with me on Thursday after some input from engineering, seems to me the new iOS is dropping that day and he wants to call me to have me install it and go from there.
 
  • Like
Reactions: JeffNT326
I'd like to clarify that there appears to be two issues with regard to the "No signal" problem.

The first issue is what this entire thread is about: the iPhone 7 is dropping to no signal in areas known to have strong LTE signals as the phone is moving between towers. It then has difficulty re-establishing connections in an expedient way resulting in the "No Signal" indicator. The temporary fix to this problem is to turn off VoLTE. Apple and Verizon have said (at some point on some level) that they are aware of this problem and are working on a fix which iOS 10.1 B3 with Carrier v. 26.0 appears to address for the vast majority of users.

kokonutz explained that he or she (sorry unsure of pronoun) tried disabling VoLTE (leaving LTE data only) and installed iOS 10.1 B3. This did not solve the problem as the "No Signal" indicator was present even without moving.

This leads to the second issue which people searching for answers naturally find this thread to read about: some iPhone 7s have faulty modems/a-gps components or connections to the antenna structure that are causing them to lose signal. This issue extends beyond designated Verizon/Sprint phones as evidenced by similar experiences with T-Mobile and AT&T designated phones. For these individuals, swapping the phone has solved their issues.

This is the situation kokonutz falls under. If he begins to move between towers and experiences "No Signal" but is able to reacquire it with the replacement phone, then his replacement phone, with a properly functioning modem, is now operating under the first issue to which a software fix should potentially fix.

On another note, I've noticed the first issue is experienced by many in the NYC/Tri-state area (where I live). This leads me to think that there's an issue with tower network parameters or somehow the iPhone 7 is identifying itself in a way that is conflicting with network VoLTE handoff protocol. Either way, it seems a fix is on the way, and I've heard it could come out this week.

That's correct. Turns out my problem was different from the main one here, and I did come across this thread while searching for a solution for that issue. I replaced the phone and the issue was resolved.

New phone as in replacement?

The issue I was having was referred to in a previous post, and is explained by JeffNT326 above.

Also, I have been testing my replacement phone for the VoLTE issue and have not seen it yet, but like I said I have only had the phone for basically one morning. On this phone I am on iOS 10.0.2, carrier v25.1 and not iOS 10.1 B3. I have drops to 1-2 bars in areas I usually had these drops, never No Service like my previous issue.

Do you guys notice this mostly during traveling? I drive about 15 miles or so to work and did not see anything.
 
  • Like
Reactions: JeffNT326
What baffles me the most is why APPLE did not see these issues prior to release. They test these phones (prototypes) extensively, especially in the US, on all the carriers, and they act like it was an unknown issue. They also beta tested ios 10 on these phones too.
 
  • Like
Reactions: oneteam
I'd like to clarify that there appears to be two issues with regard to the "No signal" problem.

The first issue is what this entire thread is about: the iPhone 7 is dropping to no signal in areas known to have strong LTE signals as the phone is moving between towers. It then has difficulty re-establishing connections in an expedient way resulting in the "No Signal" indicator. The temporary fix to this problem is to turn off VoLTE. Apple and Verizon have said (at some point on some level) that they are aware of this problem and are working on a fix which iOS 10.1 B3 with Carrier v. 26.0 appears to address for the vast majority of users.

kokonutz explained that he or she (sorry unsure of pronoun) tried disabling VoLTE (leaving LTE data only) and installed iOS 10.1 B3. This did not solve the problem as the "No Signal" indicator was present even without moving.

This leads to the second issue which people searching for answers naturally find this thread to read about: some iPhone 7s have faulty modems/a-gps components or connections to the antenna structure that are causing them to lose signal. This issue extends beyond designated Verizon/Sprint phones as evidenced by similar experiences with T-Mobile and AT&T designated phones. For these individuals, swapping the phone has solved their issues.

This is the situation kokonutz falls under. If he begins to move between towers and experiences "No Signal" but is able to reacquire it with the replacement phone, then his replacement phone, with a properly functioning modem, is now operating under the first issue to which a software fix should potentially fix.

On another note, I've noticed the first issue is experienced by many in the NYC/Tri-state area (where I live). This leads me to think that there's an issue with tower network parameters or somehow the iPhone 7 is identifying itself in a way that is conflicting with network VoLTE handoff protocol. Either way, it seems a fix is on the way, and I've heard it could come out this week.

Concur with JeffNT326. IOS 10.1 Beta 3 seems to have fixed my reception issues even with LTE Voice and Data turned on. However I live close to the I-95 corridor on Northern Virginia and LTE coverage/reception is usually pretty good. I found an article in howtogeek.com that described how to activate the iPhone's Verizon Field Test Mode that allows you to read your actual signal strength amongst other many other technical parameters. Good for finding dead spots in and around your home, but doesn't fix the basic "no reception" issue this thread is all about.
 
What baffles me the most is why APPLE did not see these issues prior to release. They test these phones (prototypes) extensively, especially in the US, on all the carriers, and they act like it was an unknown issue. They also beta tested ios 10 on these phones too.


That gets me too, its literally the nations largest carrier and the one with the most premium pricing and Apple had a device that could easily be used out in the wild for months since it looked almsot exactly the same, and no one ever was like "hey the signal keeps dropping" especially if their sole job was testing the phone so they wouldnt just not notice it.
 
I am pretty sure a new iOS release will come this thursday which will address this issue among other things.

I received a phone call from Apples Executive relations office after emailing tim cook and he said he would follow up with me on Thursday after some input from engineering, seems to me the new iOS is dropping that day and he wants to call me to have me install it and go from there.
Good to know...keeping my fingers crossed that it does the trick. This is probably the most trouble I've had with an Apple product, and I've had a crap ton of them going all the way back to the Apple II+
 
Lol pay it no mind. He says he didn't leave the house yet so he hasn't even seen the issue. It's been proven replacement or new devices don't solve the issue.
Not true. Solved for me. iPhone 7 jet black replacement on 10/3. My production date was week of 9/23. iOS 10.0.1. Won't update until issue is confirmed fixed on later software.
 
Last edited:
Not true. Solved for me. iPhone 7 jet black replacement on 10/3. My production date was week of 9/23. iOS 10.0.1. Won't update until issue is confirmed fixed on later software.

most of us who've had our phones replaced (myself included) have experienced no difference in service reliability. how/where did Apple inform you of the manufacture date of your phone?
 

thanks. I think the reason we're skeptical new phones can fix the issue is that Apple engineers have told their reps to stop replacing phones until a fix is pushed out. given how poor Apple's quality control has been with the iPhone 7, I suppose it's possible they don't really want to implement a mass hardware replacement until they can be sure that newer devices are actually needed to fix this issue. on top of that, could it be that the phones built more recently had some change made to them that avoids the conflict that would require a software patch in the older devices? theoretically, sure, but I really don't know enough about how Apple builds their phones to know if that makes sense or not.
 
So almost four weeks since launch and no true resolution. Anyone getting worried about this?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.