This was happening before the update just an fyi, its also crashing on the iPad.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases iOS 16.1.2 With Carrier Improvements and Crash Detection Optimizations
- Thread starter MacRumors
- Start date
- Sort by reaction score
OMG! Yes... my caller is using AT&T and I told the CSR that. Thank you for the tip and I will try that!
EDIT: YES... the number is indeed showing up in the Verizon Call Filter app as spam.
Last edited:
Hopefully the one with AT&T where my iPhone 13 PM either doesn't ring at all (and shows as a missed call) or rings for a millisecond (and shows a missed call).
Or maybe the one were I (just now) get a voicemail notification for a VM left YESTERDAY or 3 HRS AGO or some other really delayed time? My Apple Watch will show a VM and I look at my iPhone and NOPE -- no notification.
God forbid my calls actually come to my phone with some sort of reliability and my VM notifications are timely?
T mobile: Mine is 52.0.1, before update.
16.1.2 "Preparing Update...", still. About 10+ minutes. Progress bar seems stalled.
16.1.2 "Preparing Update...", still. About 10+ minutes. Progress bar seems stalled.
Well, as it used to be iOS for iPad and iPhone (and iPod Touch IIRC), I know many people that call the iPad-OS still iOS. You know: "I just updated my iPad to iOS 16!"
And as all other OS types are referring to which device-type they're for, I do feel that iPhoneOS does make it (even) clearer.
But whatever.. not a big deal IMHO.
I checked and mine was 52.0.1 before and after for T-Mobile. Others on my device haven't changed either.
This happened to me Sunday night. I couldn't understand why it was being reported as spam even though he is a saved contact. I hit allow in the call filter app after I realized what was happening.
52.0 for me on Verizon
AT&T is also 52.0 (I’m on a dual-sim setup).
Yes. My ipad app was crashing a half an hour ago but seems stable now.
Edit. Getting more crashes
Last edited:
Mine's been doing that for the last few hours ... and I was on 16.1.1.
It's unrelated to the 16.1.2 update
I wonder what was changed that's causing this problem? Verizon issue or AT&T issue? Most of the people I talk to have Verizon so I didn't even notice it until Sunday night.
I wonder why, after speaking several hours with 4 different level II tech reps, why none of them thought to look at the Verizon Call Filter app? They blamed me for blocking the number, their script kept them focused on my iPhone settings, but not once did they suggest to check the VERIZON Call Filter, or even ask if I was using their call filtering service. And after giving them the incoming number, they don't have the resources to check that number against their call filters? Nor the resources to see that my account is using their official call filtering service? Surely since the app has the power to prevent the call from ringing and dump it straight to VM, somewhere in their system it knows the call was rejected by the Verizon app, right??
Verizon's customer service is lacking lately...I'm hoping they get this issue resolved quickly, but I'm not holding my breath lol.
For the Call Filter app, you should enable the notifications if you have them disabled; it will notify you whenever a call is blocked as spam. I also had the same happen on Saturday evening, when I got a notification from CF app that a call from my neighbor (on AT&T) was blocked as spam. That's what led me to go in and allow it and mark it as "not spam", then I saw others reporting the same on Reddit. Not sure what changed, but something was changed on Thanksgiving of all days that brought this about...
So it seems based off this thread, ATT is still on 52.0.
Can anyone on iPhone 13 let me know if modem firmware was updated from 2.12.02?
Otherwise I'll prolly stay put on 16.1.1
Thanks!
Can anyone on iPhone 13 let me know if modem firmware was updated from 2.12.02?
Otherwise I'll prolly stay put on 16.1.1
Thanks!
I'm on a 13 Pro with iOS 16.1.2 and modem firmware is still 2.12.02
I just had a coworker that has AT&T try to call me and it wasn't blocked. Maybe they fixed the issue? Spam level is set to all risk levels on the VZW call filter app.
All CSRs from level 1 and 2 were off-shore. Friendly but really lacking in knowledge and expediency. They used to have excellent tech support based in the states.
That is another good tip. I am using the free version of Verizon Call Filter so I changed the filter level to "high risk only" and whitelisted (also report as not spam) the numbers that are showing up as my contacts. What's odd is the app obviously knows these are my contacts since they show up in the Call Filter app with the names from my Contact book.
I doubt it. Mine started on Thanksgiving and has been hit & miss. Sometimes I thought it was resolved too. Some calls from a particular number came through while others from same number were blocked. Maybe 50/50.