Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
And 13.3.1 beta 1 has a newer kernel (19.3.0 built on December 8) than 13.3 (19.2.0 built on November 4).

I think it's unusual for Apple to use a newer kernel in a small point release. They might want telemetry on the stability and performance of the newer kernel so they released it before the holidays. Just speculating here.
 
And 13.3.1 beta 1 has a newer kernel (19.3.0 built on December 8) than 13.3 (19.2.0 built on November 4).

I think it's unusual for Apple to use a newer kernel in a small point release. They might want telemetry on the stability and performance of the newer kernel so they released it before the holidays. Just speculating here.
Right! That’s why 13.3.1 is 17Dxx instead of another 17Cxx-build. 😁
 
  • Like
Reactions: I7guy and gank41
Apparently there will be a software update coming soon to address the issues in this stories.
Could see 13.3.1 being released imminently and the current 13.3.1 beta being renamed to 13.3.2.

Nice find! Apple will want to fix this issue quickly. Maybe 13.3.1 will be this week after all.
 
Apparently there will be a software update coming soon to address the issues in this stories.
Could see 13.3.1 being released imminently and the current 13.3.1 beta being renamed to 13.3.2.

In think this is why 13.3.1 was released in beta so they could see if the roll back of carrier update was any different and different kernel... fully expect 13.3.1 to be released tonight in full public release!
 
In think this is why 13.3.1 was released in beta so they could see if the roll back of carrier update was any different and different kernel... fully expect 13.3.1 to be released tonight in full public release!

I miss the days when Apple could push carrier updates without software updates. It would allow them to react more swiftly to these types of issues.
 
I believe they still can. I think going into Settings/General/About triggers any pending update to the carrier settings.

While cool (and if confirmed), I'm not sure that I like that it would do this without the user being made aware, or at least being able to accept or decline.
 
While cool (and if confirmed), I'm not sure that I like that it would do this without the user being made aware, or at least being able to accept or decline.
Well, you ARE able to decline... It's been like that since at least iOS7 or even earlier.

1a.png
 
I really want an update as I use my speakerphone a lot and 13.3.1 beta has messed it up really bad.
Cant even video call on speaker phone because of echo.
 
I really want an update as I use my speakerphone a lot and 13.3.1 beta has messed it up really bad.
Cant even video call on speaker phone because of echo.

same here!!!!
[automerge]1578416521[/automerge]
I’m hoping the next beta fixes a lot of stuff. With sprint, my service was horrible with my 8 plus in NYC. I got the 11 pro max and with 13.3 and sprint carrier settings 40.0. right before Christmas and I had unbelievable service and speed well over a 100mb a sec. Then like a moron, I went back on the beta and since the carrier setting went back to 39.5.1, I’ve had to keep putting my phone in airplane mode, reset network settings, etc to get a constant signal and decent speeds. Very frustrating and I know it’s not my phone.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.