Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Installed public beta; it is synced with dev beta. Today’s beta is a “b” release; last week was a “d”; “a” and onwards are gen release quality. Don’t forget to hard restart your iPhone 2x in 2 hours; I turned off the glass effect. Turned on reduce motion. Put it on low battery to stop indexing, plug it in at night/when not using the iPhone, and turn off low battery to finish indexing.
 
Installed public beta; it is synced with dev beta. Today’s beta is a “b” release; last week was a “d”; “a” and onwards are gen release quality. Don’t forget to hard restart your iPhone 2x in 2 hours; I turned off the glass effect. Turned on reduce motion. Put it on low battery to stop indexing, plug it in at night/when not using the iPhone, and turn off low battery to finish indexing.
What on earth are you talking about?

You don’t need to restart your phone unless you’re experiencing issues like stuttering or overheating. And why would you go out of your way to obstruct indexing?
iOS is smart enough to do the heavy lifting only when connected to power. Any task that’s performed while unplugged would not have any noticeable impact on battery life.

You’re incorrect on the “a” releases being general releases as well. There were instances where we jumped from “c” builds straight to RC. So release of an “a” build is not a requirement. And they don’t necessarily countdown either. Next week could be a “c” or “d” build.

I’m not sure where you’re getting all your information from but pretty much everything you said doesn’t have any actual basis to it.
 
What on earth are you talking about?

You don’t need to restart your phone unless you’re experiencing issues like stuttering or overheating. And why would you go out of your way to obstruct indexing?
iOS is smart enough to do the heavy lifting only when connected to power. Any task that’s performed while unplugged would not have any noticeable impact on battery life.

You’re incorrect on the “a” releases being general releases as well. There were instances where we jumped from “c” builds straight to RC. So release of an “a” build is not a requirement. And they don’t necessarily countdown either. Next week could be a “c” or “d” build.

I’m not sure where you’re getting all your information from but pretty much everything you said doesn’t have any actual basis to it.

Fine, I”ll play along.
Go look at the .0 betas from the last 3 years, not point releases. iOS 17 went d, c, a, a, then RC. iOS 18 went f, b, a, a, then RC. iOS 26 went c, a, a, a, then RC. iOS 27 is d last week and b this week. Does it have to hit a before RC? No, but it has every year since 17, and once it’s on a the RC has been 1 to 3 weeks out. The c to RC jumps you’re thinking of are 16.2 / 17.2 type point releases with 3 or 4 betas. Only time a letter went up late in a .0 cycle was the beta 6 respin last year, 23A5318c to f, same beta.


On indexing, Apple’s own support page says battery and heat take a temporary hit after a big update while it indexes for search. the Optimizing Search and Siri banner in Settings, it says longer charging help indexing go faster, so it’s running when you’re not charging, just slower. Low Power Mode throttles it, which is the whole reason every “indexing stuck” post says turn LPM off and plug in. I just do it in reverse. LPM on during the day, off overnight on the charger.


Restarts, open the beta 6 release notes. Known issue 179470940, blurry status bar, Apple’s workaround is literally “Restart your iPhone.” Beta 1 notes had the same workaround for home screen edits not saving. Basically restart after install and again a couple hours later once the downloads are done. 60 seconds or less.

Go to bed.
 
Last edited:
Fine, I”ll play along.
Go look at the .0 betas from the last 3 years, not point releases. iOS 17 went d, c, a, a, then RC. iOS 18 went f, b, a, a, then RC. iOS 26 went c, a, a, a, then RC. iOS 27 is d last week and b this week. Does it have to hit a before RC? No, but it has every year since 17, and once it’s on a the RC has been 1 to 3 weeks out. The c to RC jumps you’re thinking of are 16.2 / 17.2 type point releases with 3 or 4 betas. Only time a letter went up late in a .0 cycle was the beta 6 respin last year, 23A5318c to f, same beta.


On indexing, Apple’s own support page says battery and heat take a temporary hit after a big update while it indexes for search. the Optimizing Search and Siri banner in Settings, it says longer charging help indexing go faster, so it’s running when you’re not charging, just slower. Low Power Mode throttles it, which is the whole reason every “indexing stuck” post says turn LPM off and plug in. I just do it in reverse. LPM on during the day, off overnight on the charger.


Restarts, open the beta 6 release notes. Known issue 179470940, blurry status bar, Apple’s workaround is literally “Restart your iPhone.” Beta 1 notes had the same workaround for home screen edits not saving. Basically restart after install and again a couple hours later once the downloads are done. 60 seconds or less.

Go to bed.
iOS 9.0 went from "c" to RC which wasn't a point update. iOS 12.0 went from a->b->a in betas 10, 11, and 12 before RC which was quite late in the cycle. So no, it wasn't just in iOS 26.


That's just to keep people from worrying about their battery right after an update. It has some impact on the battery, but definitely not enough for you to actually notice.
LPM throttles everything, including dropping the display to 60fps as it’s designed to maximize the battery. The pros don't outweigh the cons when you have decent chunk of battery left even during the indexing phase. It's not necessary at all. LPM also turns off once you hit 80% for the same reason.

At the risk of repeating myself here, only parts of indexing that doesn't significantly affect the battery life are run while unplugged. The resource intensive stuff happens while your iPhone is charging and locked.


You're actually proving my point here. The notes say to restart as a workaround which means after you experience the issue. It doesn't mean restarting would eliminate the issue. Workarounds are temporary measures and not a permanent solution to an issue.
 
OS 27 beta 6 is on the "B" build. Which means 2 more weeks of OS 27 beta.

This also means that Apple will hold their iPhone event on the week of Sept 7th - Sept 11th.

Apple already told employees the iPhone event is the first half of September.
That is any date between Aug 31st and Sept 11th.

Apple's decision to host the iPhone event on September 7th is financially genius. September 7th is Labor Day. Which means no one works. This indicates that Apple will have the highest viewership of their event since no one is working.


I believe Gurman already ruled out that day for the event and preorders because the 7th is Labor Day but that Friday (which would be preorders) is also a holiday in the US. Sept. 11 (25th Anniversary). And if history says anything, they announce the event 2 weeks before it happens. So they would need to announce this week if it's the week before. From his latest info I've read, he said event Wed Sept. 9 with preorders starting the following Monday Sept. 14 due to the Sept. 11th holiday that Friday.
 
What on earth are you talking about?

You don’t need to restart your phone unless you’re experiencing issues like stuttering or overheating. And why would you go out of your way to obstruct indexing?
iOS is smart enough to do the heavy lifting only when connected to power. Any task that’s performed while unplugged would not have any noticeable impact on battery life.

You’re incorrect on the “a” releases being general releases as well. There were instances where we jumped from “c” builds straight to RC. So release of an “a” build is not a requirement. And they don’t necessarily countdown either. Next week could be a “c” or “d” build.

I’m not sure where you’re getting all your information from but pretty much everything you said doesn’t have any actual basis to it.
The only reason that builds in late beta stage is a "low" letter is because they dont have to build that many times to test a new feature. its mainly bug fixes in these releases
 
Installed public beta; it is synced with dev beta. Today’s beta is a “b” release; last week was a “d”; “a” and onwards are gen release quality. Don’t forget to hard restart your iPhone 2x in 2 hours; I turned off the glass effect. Turned on reduce motion. Put it on low battery to stop indexing, plug it in at night/when not using the iPhone, and turn off low battery to finish indexing.

Why?? Just why? And you most certainly do not need to hard restart your phone…that’s nonsense.

And also, this part of the “conversation” is not for the speculation thread.
 
... yes it's normal, we're in the endgame now.
Screen_Shot_2019_06_27_at_3.48.24_PM.png
 
The only reason that builds in late beta stage is a "low" letter is because they dont have to build that many times to test a new feature. its mainly bug fixes in these releases
Build what? And how would fixing the bugs translate to less "builds"?
 
There doesn't really need to be such a hullabaloo with regards to Apple's versioning; a quick check with Google's AI (combining data from multiple sources) suggests the following:

Anatomy of a Build Number

Users on StackExchange agree that Apple build numbers follow a strict coding structure: [1]
  • Major Version (The Train): The starting digits represent the OS "build train" or major version (e.g., 24 for iOS 27, 25 for macOS Tahoe). [1, 2, 3]
  • Minor Version Letter: The capital letter right after the number tracks the minor release train. A usually points to the initial .0 major consumer release, while B, C, or D track subsequent minor point updates (like .1 or .2). [1, 2]
  • Sequential Build Number: The digits in the middle (often starting with a 5 during beta cycles) show how many times the internal code was compiled. Higher numbers mean a more recent compile date. [, 2]
  • Stability Suffix Letter:The final lowercase letter (ranging from a up to z) denotes how close or stable a build is during testing.
    • Letters near the beginning of the alphabet (a, b) are early internal builds.
    • Letters near the end (g, h, i) mean the beta is maturing and getting closer to a Release Candidate (RC) or public launch. [1, 2, 3, 4, 5]

It took me a bit of time, as the relevant reference links are freaking YouTube videos... but it looks like the AI hallucinated an incorrect answer for the stability suffix -- at least, according to one of the linked videos, anyway. From this video:
... as we get closer to a stable release, Apple will be moving that letter at the end closer to the beginning of the alphabet...
 
Last edited:
  • Like
Reactions: Kal Madda
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.