Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Would be nice if my 12 Pro didn't drop signal when going out of range in the parking lot, and then not pick up when I'm back in range in my office.

I don't know if this is a carrier issue, or a phone issue. But almost every day, when my phone loses 5G connectivity, I can't get any signal back until I put the phone in airplane mode and switch it back on.

Would be nice if some sort of software fix could address it. From what I've heard I'm not the only user with this issue.
 
Honestly, I have been reading the beta 1 thread closely and I’m not surprised in the least they updated it. There seemed to be too many somewhat moderate issues that shouldn’t be present this far along into an iOS version. (I’m the first to admit betas have issues but not like this with iOS 14 being so mature) Ie Safari not working, apps not loading, cellular service cutting out, mail not working etc. It’s a bit nuts if you ask me. I actually predicted they wouldn’t release a public beta due to these issues, at least until beta 2. But it’s great to see they have nipped it in the bud this week. Hopefully public beta is to follow soon.
 
  • Wow
Reactions: SqlInjection
Would be nice if my 12 Pro didn't drop signal when going out of range in the parking lot, and then not pick up when I'm back in range in my office.

I don't know if this is a carrier issue, or a phone issue. But almost every day, when my phone loses 5G connectivity, I can't get any signal back until I put the phone in airplane mode and switch it back on.

Would be nice if some sort of software fix could address it. From what I've heard I'm not the only user with this issue.
Does it still occur with the updated beta 1?

I still believe they haven’t ironed out the iPhone 12 wireless connectivity issues that have been present since day 1.
 
Uhhh, yeah, but the letter on beta build goes backwards to A so a J build then going to a K build is a backwards step in stability, so the OP was right!
Exactly. The closer we get to final build, the earlier the letter should be. More than likely the "J" build had something screwed up or changed that shouldn't have been, so they just pushed out an older build they already had, instead of trying to fix it very quickly to push out a new version.
 
If I was petty I would search up those comments claiming that no 5G dual sim was a hardware limitation and we were silly for believing it could be fixed in the modem firmware. But I'm not petty, or am I?

Anyway, it's great news. I don't need it but I know it'll make a lot of people happy!
 
  • Like
Reactions: upandown
Uhhh, yeah, but the letter on beta build goes backwards to A so a J build then going to a K build is a backwards step in stability, so the OP was right!
The letter at the end of the build number stands for the number of revisions (or compiles) for that specific build-number. First build of let’s say „18E5140“ in this case would be 18E5140a. If a major error is found, another compile is done, named 18E5140b, the third compile would be 18E5140c and so on. So a „k“ compile of a build is newer than a „j“ compile.

In later stages of beta versions, the chances are higher, that a first (a) or second (b) compile of a specific build is considered good for release. That‘s why late betas often end with a or b. ;)
 
Uhhh, yeah, but the letter on beta build goes backwards to A so a J build then going to a K build is a backwards step in stability, so the OP was right!
Those letters don't represent Alpha, Beta, etc. They are just numbers in hexadecimal, representing the build number, every new build has a higher number.
 
Those letters don't represent Alpha, Beta, etc. They are just numbers in hexadecimal, representing the build number, every new build has a higher number.
Not hexadecimal, as neither j nor k are present in hex. Hexadecimal is ending with f ;)

And the letter does not represent a build but a compile of one specific build. See my comment above.
 
  • Like
Reactions: GregoriusM
This is a sizable update. Really looking forward to it.

After this, would love to see Apple really focus on bugs for 6 months. The power of Apple is “it just works”--not bajillions of new features. That’s the trap Microsoft, Adobe, et al. fall in.
Aside from HomeKit issues I haven't had any major iOS bugs in a long time
 
  • Like
Reactions: SRLMJ23
Has anyone else noticed that the Ipados 14.5 Public beta is 4.58 GB?? The Ios one was only around 155Mbs. And yes I did update to 14.5 like 3 days ago.
8BABB184-4C45-43CE-88A3-97BC408C19E6.jpeg
 
I've just checked (was running 14.5 beta 1 already - I have the dev profile installed) and now it wants to download what it's calling "14.5 Public Beta". Clicking "learn more..." opens a blank screen. What a mess.

Downloading anyway :)
What is the size of the file. I just checked mine and it told me it was 4.58gb??
 
Those letters don't represent Alpha, Beta, etc. They are just numbers in hexadecimal, representing the build number, every new build has a higher number.
Not quite.
  • The first number is the product version family. Apple could do whatever they want with this, but it'll increase with each major version. Probably only by one, but that's not guaranteed. For instance, Catalina is 19 and Big Sur is 20. No idea if macOS 12 will be 21; it's the logical guess, but it's not guaranteed.
  • The letter represents a minor version. In the past, 10.15.0 might have been A, 10.15.1 might have been B. With Big Sur, it seems they consume a letter for both minor or patch versions. We're up to D now for 11.2, which is the fourth release (11.0, 11.0.1, 11.1 and 11.2). So 11.2.1 or 11.3 will probably be E, whichever comes next. I don't know if Apple tries to reclaim letters if they decide not to release a version. For instance, 11.2.1 might get some traction as a minor release and then just be rolled up to 11.3. If they were both in testing, I could see 11.2.1 using up E so that 11.3 was F.
  • The final number represents a build number within the version. Apple typically does builds at least daily, and they may reset this part of the build number between minor releases.
So 20D64 should be read as 20-D-64, or 20-4-64, and means "Big Sur, release 4, build 64." And you have to guess when the 64 part was last reset. The only thing you can be certain of is that 20 represents Big Sur, 20D 11.2 and 20D63, 20D64 and 20D65 are ordered builds of 11.2 (and they probably won't all go public, or even pass whatever internal testing Apple has).

TL;DR: The first number represents the major version. The letter represents the release within the version in a way you can't reverse engineer. The last number represents the build within that version and release.

Still too long: A one digit change to the build could still be a huge number of changes, or otherwise have a huge impact.
 
Last edited:
My phone just updated to 14.5 (18E5140k), looks like it was minor bug fixes only indeed, but I don’t recall what this previous 14.5 beta code revision was.
Safari seems fixed (as I’m back to this very own forums), and so it seems my cracklings from Bluetooth, but I still cannot connect to CarPlay in my vehicles…
 
L
Has anyone else noticed that the Ipados 14.5 Public beta is 4.58 GB?? The Ios one was only around 155Mbs. And yes I did update to 14.5 like 3 days ago.
I am noticing that Apple Beta Software program site is hard to access currently (very slow to respond) - local to Cupertino. I don't see a PB for iPadOS 14.5 beta yet.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.