Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's getting really bad for me. My fiancee has to keep texting me to tell me she called me twice, when I got no indication that I had been called. Just reset network settings, hoping it helps.

This kind of thing is why Apple warns developers not to use pre-release software on their daily use devices.
 
i have had this problem...verizon iphone 5. after messing around i found a fix (well it worked this time, hopefully not just a temp. fix.)....i called my phone from the office....it rang on the office headset but my iphone never did a thing. i turned do not disturb on, then back off. tried calling my phone again, and the call went through to my iphone. hope this helps
 
This kind of thing is why Apple warns developers not to use pre-release software on their daily use devices.
While generally a good idea overall, there's the opposite side of it, especially when it comes to somewhat limited and sporadic issues of this type--issues like this one might not really be noticed, and/or noticed early enough, and/or will enough reproducible information to actually address them sooner rather than later if everyone simply used non daily use devices, which often aren't used to receive or make calls.
 
This is a beta 3 issue for the A1428 build. It is a known issue and is crippling. Thanks to the hacker the slowed beta 4 release my mom still think i'm ignored her :p
 
i have had this problem...verizon iphone 5. after messing around i found a fix (well it worked this time, hopefully not just a temp. fix.)....i called my phone from the office....it rang on the office headset but my iphone never did a thing. i turned do not disturb on, then back off. tried calling my phone again, and the call went through to my iphone. hope this helps
Unforunately, as discussed in fair bit of detail in another thread about this issue at https://forums.macrumors.com/threads/1608119/, it doesn't seem like things of this nature truly fix the issue (beyond some sort of temporary effect, which might even be simply coincidental too, given the sporadic nature of the issue for most who experience it).
 
While generally a good idea overall, there's the opposite side of it, especially when it comes to somewhat limited and sporadic issues of this type--issues like this one might not really be noticed, and/or noticed early enough, and/or will enough reproducible information to actually address them sooner rather than later if everyone simply used non daily use devices, which often aren't used to receive or make calls.

While yes that is true, this particular case is likely that the carrier software hasn't been updated or at least released for ideal iOS 7 compatibility. Which should not be a major issue since folks should not be using iOS 7 as their daily use software anyway.
 
While yes that is true, this particular case is likely that the carrier software hasn't been updated or at least released for ideal iOS 7 compatibility. Which should not be a major issue since folks should not be using iOS 7 as their daily use software anyway.
Carrier part of the software gets updated with iOS beta releases as well, and is definitely used by Apple and carriers for testing too. What's likely is that there's some sort of a bug there.
 
I haven't been able to receive incoming calls with this release... using the Rogers network in Toronto- sometimes appears like a duplicate call with them both on hold, and then other times i see a green bar at the top that says to tap to go back to the call.. but it never works.. I mostly text so not a huge issue... outgoing calls work just fine.
 
Unforunately, as discussed in fair bit of detail in another thread about this issue at https://forums.macrumors.com/threads/1608119/, it doesn't seem like things of this nature truly fix the issue (beyond some sort of temporary effect, which might even be simply coincidental too, given the sporadic nature of the issue for most who experience it).

it is indeed a temporary fix. i'm not quite sure if it's every time i restart my phone....switching to and from my work wifi, LTE driving home, then getting back on wifi...or even my phone just being asleep a while. But i do know it fixes the problem at least temporarily for me. Hopefully it'll be addressed in the next release.
 
VZW iPhone 5

I've been having the same problem. I am completely missing calls, not just the ringer. People tell me later that they've tried to call me and it goes right to voicemail.
 
I've been having the same problem. I am completely missing calls, not just the ringer. People tell me later that they've tried to call me and it goes right to voicemail.

Yeah seems more and more people are having this issue. For me, I don't hear anything but those that try to call me get the normal ringing for a bit before it goes to voicemail, so on their end all seems normal. I don't have any indication whatsoever that someone called me unless they leave a voicemail.

Now, once and a while a call will come through, but I'd say about 80% I am not receiving calls at all.
 
happens to me w/ a Verizon beta 3 iphone 5. seems to work better if i do a genuine hard reset at the beginning of the day. it doesn't go straight to voicemail, i'm told that it actually rings too all the way to voicemail and I receive no notification whatsoever.
 
Same issue here. Calls are hit and miss (I get about half and the rest go to VM. Sprint in CT.
 
Have things improved in beta 4 for those experiencing these kinds of issues?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.