Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Maybe the carrier software on the phones need to be tweaked to be compatible with all towers. I'm not a cell engineer so I don't know how to really phrase that.

The last tech support person I spoke with gave me his email address if I had any further questions. I sent him a long email asking if they had updates or reasons why this is occurring and what type of fix is in the making.
 
Yea happened twice at work for me. Like I said, I'm behind concrete so having it quickly jump to 3G for a few seconds then back to LTE really isn't as bad as it was the other day. Still haven't seen 1x or no service. But yes, it indeed still happens but nowhere near as bad by far.
 
The last tech support person I spoke with gave me his email address if I had any further questions. I sent him a long email asking if they had updates or reasons why this is occurring and what type of fix is in the making.

Hoepfully we get a resolution soon. That is all we can really hope for. I do appreciate all the effort that everyone has contributed to help resolve this issue.
 
When did this thread get moved to the tips/troubleshooting subforum (which almost no one looks at)? Seems like MacRumors is trying to bury this story for whatever reason and they've been dead silent on all of our requests to make this story more public.
 
  • Like
Reactions: spinedoc77
FYI, I have been making progress with Apple Developer Relations through a ticket I filed through our Enterprise account.

I'm turning off my Wi-Fi tomorrow and collecting some logs.

-Al

78C8e_a4NWYyYAgOQheJhHBNZsPh81bHcfX9vV5Upuk6J6MoudQW2jpu8U1_ACss4RpdcTf6HZvcBg4qc6XPYgJyEqDTkZkalPsEHEE88-ldR6KI5gqe6bs6rslskZ5tlh20haXyilMk2TfTf3uvsCn9a60bzRlBpQYxzZheVzNo-Qd0nVFFcQyu7-o9unS6MPA-QmEPilqIKO6Vr0w23MgLaCTBVVI_zub1MpdFxCA7wOrQvSeHJx2JspLP31ySfm2UyMYoXKYJ68OtNJqgMzGQ6fdN238JWzVeqaHqELBqr_gCi-MfufvhT_SO6E1m6yUjT6dJn-huV2O8ayFah-D9McI-S-gYP0SkiU4xd9Osmh8tB6_IDXQFz3P7uv3q8XZfJg8ttYIPzWi8eowKJD7xLiGSNUN7XW9qax78sti5CDh0pSL8q69GEAW6l9De-FoMsZMXUNU_EahQ9SGqjrQbgUf1OdQLhc8uh_crad8Z0CuMMNQm6ZzmXunaIb1gZ8hx1mEg_DS1lFCpICJgC6lRym3ycc2RymAEmBSeY6MxLmSRqk2ieNRh0OuTE3-jLTyAa9k7ex4RoyMbMM6xXFowT1C3LUgz8HxjkjSr-0M=w1096-h336-no

[doublepost=1474943854][/doublepost]For those curious... here's what I just loaded on my phone.
 

Attachments

  • IMG_2440.PNG
    IMG_2440.PNG
    301.4 KB · Views: 289
  • IMG_2441.PNG
    IMG_2441.PNG
    548.4 KB · Views: 252
  • IMG_2442.PNG
    IMG_2442.PNG
    248.2 KB · Views: 257
FYI, I have been making progress with Apple Developer Relations through a ticket I filed through our Enterprise account.

I'm turning off my Wi-Fi tomorrow and collecting some logs.

-Al

78C8e_a4NWYyYAgOQheJhHBNZsPh81bHcfX9vV5Upuk6J6MoudQW2jpu8U1_ACss4RpdcTf6HZvcBg4qc6XPYgJyEqDTkZkalPsEHEE88-ldR6KI5gqe6bs6rslskZ5tlh20haXyilMk2TfTf3uvsCn9a60bzRlBpQYxzZheVzNo-Qd0nVFFcQyu7-o9unS6MPA-QmEPilqIKO6Vr0w23MgLaCTBVVI_zub1MpdFxCA7wOrQvSeHJx2JspLP31ySfm2UyMYoXKYJ68OtNJqgMzGQ6fdN238JWzVeqaHqELBqr_gCi-MfufvhT_SO6E1m6yUjT6dJn-huV2O8ayFah-D9McI-S-gYP0SkiU4xd9Osmh8tB6_IDXQFz3P7uv3q8XZfJg8ttYIPzWi8eowKJD7xLiGSNUN7XW9qax78sti5CDh0pSL8q69GEAW6l9De-FoMsZMXUNU_EahQ9SGqjrQbgUf1OdQLhc8uh_crad8Z0CuMMNQm6ZzmXunaIb1gZ8hx1mEg_DS1lFCpICJgC6lRym3ycc2RymAEmBSeY6MxLmSRqk2ieNRh0OuTE3-jLTyAa9k7ex4RoyMbMM6xXFowT1C3LUgz8HxjkjSr-0M=w1096-h336-no

[doublepost=1474943854][/doublepost]For those curious... here's what I just loaded on my phone.

Good work. Thanks again.
 
  • Like
Reactions: dictoresno
In case you're wondering what's in the log...

10:48:10 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
10:50:47 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
12:03:59 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
14:03:51 -0400 DST [clm] disconnect: duration=2898;cause=kNoError;modemErr=25;rat=3
14:40:49 -0400 DST [clm] disconnect: duration=131;cause=kNoError;modemErr=1008;rat=1001
15:25:57 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
18:46:59 -0400 DST [clm] disconnect: duration=339;cause=kNoError;modemErr=1007;rat=1001

It's logging every disconnect, with parameters associated with the disconnect, as well as associated tower data. Tomorrow should be fun. Fingers crossed for my phone to drop... a lot. ;)
 
In case you're wondering what's in the log...

10:48:10 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
10:50:47 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
12:03:59 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
14:03:51 -0400 DST [clm] disconnect: duration=2898;cause=kNoError;modemErr=25;rat=3
14:40:49 -0400 DST [clm] disconnect: duration=131;cause=kNoError;modemErr=1008;rat=1001
15:25:57 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
18:46:59 -0400 DST [clm] disconnect: duration=339;cause=kNoError;modemErr=1007;rat=1001

It's logging every disconnect, with parameters associated with the disconnect, as well as associated tower data. Tomorrow should be fun. Fingers crossed for my phone to drop... a lot. ;)

I would've loved to log this for them. Good deal!
 
When did this thread get moved to the tips/troubleshooting subforum (which almost no one looks at)? Seems like MacRumors is trying to bury this story for whatever reason and they've been dead silent on all of our requests to make this story more public.

It's actually a troubleshooting type of issue so can't blame the mods. Plus, there were like 3-4 threads on this that they may have merged.
 
Just got my replacement restored and updated tho 10.1 beta. There's an improvement that I can now soft reset LTE just by toggling through the LTE settings. This is one of the issues I had with my original 7+.

Now tomorrow, we'll see. I have long drives from client to client so hopefully this device won't have that issue.

Oh by the way, I also did the the HD Voice procedure someone mentioned.
 
In case you're wondering what's in the log...

10:48:10 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
10:50:47 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
12:03:59 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
14:03:51 -0400 DST [clm] disconnect: duration=2898;cause=kNoError;modemErr=25;rat=3
14:40:49 -0400 DST [clm] disconnect: duration=131;cause=kNoError;modemErr=1008;rat=1001
15:25:57 -0400 DST [clm] disconnect: duration=0;cause=kNoError;modemErr=1011;rat=1001
18:46:59 -0400 DST [clm] disconnect: duration=339;cause=kNoError;modemErr=1007;rat=1001

It's logging every disconnect, with parameters associated with the disconnect, as well as associated tower data. Tomorrow should be fun. Fingers crossed for my phone to drop... a lot. ;)

Awesome! Great work man. May the intermittent signal be with you tomorrow. If they need any additional individuals to help log the drops, you should tell them there are people (myself and I'm sure a few others) that are more than willing!
 
got my 7 plus jet black and I actually don't have this issue. I am super surprised. I didn't even expect to not have the issue
 
ok so I noticed something strange that may add a curveball into the mix.

last night on my way home when I reported a very positive trip and good signal, I had noticed when I left work that my reception dots were "stuck" on 2 dots. I toggled airplane mode on and off, then my reception dots were normal and much more realistic and remained "normal" for the rest of the ride home.

tonight I noticed that my whole trip home, they were "stuck" again. most of the trip they refused to deviate from 2-3 dots. they kind of tracked past towers, but only went to 3-4 dots....even next to towers. last night in the same exact spots I had full signal LTE. I didn't hit full reception 5 dots at all during the whole drive (very strange).

now, my trip tonight had zero dropouts, no 3G, 1x and no "No Service" episodes. however I can't help but conclude two things.

  1. the signal dots are either being misrepresented vs actual reception value in dBm or totally misrepresented entirely. The phone is indeed at full reception, however the phones software reports otherwise.
  2. after an episode of 3G/1x/No Service, the phones ability to connect to a tower degrades (sort of how Li-Ion batteries capacity degrades over time) and until rebooting or resetting network settings, the phone will remain in this lower reception mode or a software bug exists causing it.
now I know the signal dots are a reference value and to be taken with a grain of salt, but there is no explanation why last night I had correct, exemplary reception and now tonight while driving the same highway, same towers same time, I had only low to mediocre reception. there has to be something else going on.
 
This isn't just an iPhone issue IMO. I have a work 6S Plus running iOS 9 and a personal Android phone. Both are having issues with calls on Verizon.

On the 6S, I went to cellular settings for cellular data and turned it off. I think I restarted the device. I then turned it back on to voice and data. It seems to be working now.

On my Android, if I turn off cell data, my 4G icon goes away. As soon as turn it back on, 4G signal comes back.

IMO, this is a Verison issue.
 
On my Android, if I turn off cell data, my 4G icon goes away. As soon as turn it back on, 4G signal comes back.

IMO, this is a Verison issue.


this is like saying "I flicked the light switch, the light came on. flicked it again and it turned off".

the issue could be hardware related which would make it likely an Apple issue or it could be the way the software runs the hardware, which would make its both an Apple and Verizon issue. However, Verizon told me they work together on the carrier software to make sure its properly compatible with the hardware. but the ball is in apples court to call it good and push it to our devices.
 
  • Like
Reactions: determined09
this is like saying "I flicked the light switch, the light came on. flicked it again and it turned off".

the issue could be hardware related which would make it likely an Apple issue or it could be the way the software runs the hardware, which would make its both an Apple and Verizon issue. However, Verizon told me they work together on the carrier software to make sure its properly compatible with the hardware. but the ball is in apples court to call it good and push it to our devices.

Agreed, but the fact that a friend of mine with an Android, my Android and my iPhone are all having a similar issue leads me to believe it's on Verizon's side.

My iPhone was previously on data only, after I turned it off, I put it on data and voice and it's been working fine since. I called another friend with an iPhone on Verizon having the same issue and told him what I did. He did the same and it corrected his as well.

I haven't made a call in several hours to know if it's stuck.
 
when did you perform this restore?
An hour or 2 ago... My phone was always stuck on 3G whatever I did wouldnt go on LTE even when I activated for the first time. I called Tech support they advised me to restore the phone.
So i restored the phone and also there was a carrier update and then boom LTE appeared.

I dont think anything is wrong with the phones.
This is an carrier issue or software issue...
And changing sim card I dont think will solve the problem.
 
An hour or 2 ago... My phone was always stuck on 3G whatever I did wouldnt go on LTE even when I activated for the first time. I called Tech support they advised me to restore the phone.
So i restored the phone and also there was a carrier update and then boom LTE appeared.

I dont think anything is wrong with the phones.
This is an carrier issue or software issue...
And changing sim card I dont think will solve the problem.

That's what we have been saying all along.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.