The iOS 10.x.x Beta Speculation Thread

[zorinlynx]

This "new iPad" is actually a good release and I'm going to go for it.

I don't use my iPad much, simply because it's somewhat slow and needs more RAM. This upgrade will solve that issue for me for not much money. I don't need all the "Pro" features as I'm a very casual iPad user.

 

[dan9700]

I pray ios 10.3 beta 8 today cos beta 7 is so slow and laggy compared to beta 6

 

[Mlrollin91]

This "new iPad" is actually a good release and I'm going to go for it.

I don't use my iPad much, simply because it's somewhat slow and needs more RAM. This upgrade will solve that issue for me for not much money. I don't need all the "Pro" features as I'm a very casual iPad user.

This probably is only slightly faster than the Air 2 and has the same amount of RAM as the Air 2. Air 2 had a tri-core processor, this has dual.

Single core, A9 is better, multi-core, A8x is better.

http://wccftech.com/apple-a9xipad-pro-benchmarks/

I would personally try to get a NIB Air 2 while they are still available, but I guess it all depends on what your use is.

 

[nortonandreev]

New wallpaper possibly coming to iOS 10.3 on iPhone 7 Special Edition.

I hope it will be available for 7/7 Plus users as well.

 

[dreadlord]

Only the RED iPhone 7 orders starts on March, 24th. iPhone 7 does not need a new iOS version since the only change is color. It can be shipped with iOS 10.2.1. However, new iPad orders will begin in April. Since it has a new board (even the CPU is not new), it will need new drivers that should be included in iOS. New iPad will be shipped with iOS 10.3, and it seems like to me iOS 10.3 will not be released next week, too. iOS 10.3 beta 8 should say hi this week.

 

[BlueDr]

Try this people,change your wallpaper with the bubbles wallpaper,after that you will see that all the animations work great and fast

 

[uandme72]

Thanks to @dreadlord

Explanation of iOS build numbers

14 = Major version. Here it says it is an iOS 10 build. '13' means iOS 9 so on so forth.
E = Minor version. First major version starts with 'A' which is x.0 launch release. iOS 10 (14A403). It is not necessary to be a 10.x point release to increment this it may be 10.x.x release. Usually Apple increment this when kernel version changes.
5 = It means that this build is not prepared for public release. Builds have this in build number will not release as stable build.
269 = Actual build number. It means that it is the 269th build of iOS 10.3. There may be a lot of code changes. Generally Apple has a new build everyday. And Apple tests these builds 1 week before releasing it. So, 14E269a went to Apple test team last week to test if there is a major bug. If there is see the next:
a = Revision letter. If Apple test team find bugs, they sends a report to engineering team. Engineering team tries to fix some of them and increments the revision letter. It looks like test team hasn't found any bugs to be fixed before releasing it. So, Apple released to us.

So what can we understand from today's beta?

The build number has '5' before the actual build number. Hence, this is not the build we will see when Apple releases iOS 10.3 stable. I personally expect one more beta, but it may have '5' before the actual build number. Last beta of the iOS 9.3 release is iOS 9.3 beta 7 and its build number is 13E5234a, public release iOS 9.3 build number is 13E234. It means that Apple hasn't prepared beta 7 build as final release but it looked promising, so they released it as it was.

See?

iOS 9.3 beta 7 = 13E5234a
iOS 9.3 final = 13E234

We do not know if final release is same as beta 7. Actual build numbers are same but revision letter may be 'b' instead of 'a'. But very minor thing changes in revisions.

Can revision letter say how good build is?

Well... I think, yes. Take a look at iOS 10.3 betas:

iOS 10.0 beta 1: 14A5261v

Do you see 'v'? Yes, Apple has a, b, c, ... v revision builds before releasing the first beta of iOS 10 to fix some minor bugs before introducing shiny iOS 10 to us.

iOS 10.3 beta 1: 14E5230e
iOS 10.3 beta 2: 14E5239e
iOS 10.3 beta 3: 14E5249d
iOS 10.3 beta 4: 14E5260b
iOS 10.3 beta 5: 14E5269a

It can be clearly seen Apple test team found less and less bugs and reported to engineering team. As result revision letter comes close to 'a' (finally we see 'a') as final release approaches.

One last note, revisions generally happen in 1 or 2 day(s). It is pointless to spend much time in one build, because they have a new one already. I mentioned that Apple sends builds to test team 1 week before. So, when test team sent the report of 14E5269a, engineering team probably was working on 14E5272a. Moreover, iOS 10.3 is not the only branch they are working on. They are working on iOS 10.3, iOS 10.4, iOS 10.4.1 and iOS 11 at the same time. So, it is very complicated actually.

What's next?

I expect one more build as:

iOS 10.3 beta 6: 14E5275a
iOS 10.3 final : 14E275/14E276

How do I know these?

I am a software engineer Most companies use build systems like Apple does, and the logic is same. For example,

Latest Google Chrome release: 56.0.2924.87

56 = Major
0 = Internal version. It has no purpose.
2924 = Minor
87 = Revision


I hope I've explained the build number thing as clear as I could.
[doublepost=1490026537][/doublepost]

Look at all 10.2.1 betas. None had a 5 or a small letter. Meaning they were all potentially final releases.

A small question- if multiple teams are working in parallel on 10.3, 10.4, 10.4.1 etc, then how is it ensured that the bug resolved in 10.3 is not repeated in 10.4, or 10.4.1.
I mean how do the teams synchronise the code between different versions.

 

[Mlrollin91]

A small question- if multiple teams are working in parallel on 10.3, 10.4, 10.4.1 etc, then how is it ensured that the bug resolved in 10.3 is not repeated in 10.4, or 10.4.1.
I mean how do the teams synchronise the code between different versions.

I don't know for certain but I'm fairly confident they combine the code after the previous is available to the public. Anything that was changed in 10.3 will be updated in 10.4 in addition to the new additions of the code. Don't quote me on this but that's what makes logical sense.

 

[boswald]

Try this people,change your wallpaper with the bubbles wallpaper,after that you will see that all the animations work great and fast

No change here. iPhone 6s.

 

[C DM]

A small question- if multiple teams are working in parallel on 10.3, 10.4, 10.4.1 etc, then how is it ensured that the bug resolved in 10.3 is not repeated in 10.4, or 10.4.1.
I mean how do the teams synchronise the code between different versions.

Fairly standard development practices of version/revision control--branching, merging, etc.

 

[sbailey4]

A small question- if multiple teams are working in parallel on 10.3, 10.4, 10.4.1 etc, then how is it ensured that the bug resolved in 10.3 is not repeated in 10.4, or 10.4.1.
I mean how do the teams synchronise the code between different versions.

From the 50 thousand foot level, software coding is done in what is called Branches. So there is a main branch and sub branches. Code gets merged from the branches back to the main branch as things are changed. There is a logical process involved that ensures things get applied.

 

[uandme72]

Noone impatient?
10 minutes to go.

 

[Mlrollin91]

Noone impatient?
10 minutes to go.

I'm not entirely sure what to expect. But we definitely won't be getting the final today, thats for sure.

 

[dan9700]

Nothing, great stuck on beta 7 laggy

 

[d5aqoëp]

I am not finding Beta 7 that laggy on 7 Plus.

 

[dan9700]

I am not finding Beta 7 that laggy on 7 Plus.

Its wierd my mates one is smoother, mine i done restore from scratch using beta 7 and im getting lag on mail shutting and other apps

 

[uandme72]

Its wierd my mates one is smoother, mine i done restore from scratch using beta 7 and im getting lag on mail shutting and other apps

It seems we will get next week.

 

[dreadlord]

A small question- if multiple teams are working in parallel on 10.3, 10.4, 10.4.1 etc, then how is it ensured that the bug resolved in 10.3 is not repeated in 10.4, or 10.4.1.
I mean how do the teams synchronise the code between different versions.

There are not multiple teams working on different versions. There are teams working on different areas like Graphics, APIs, Frameworks, Design. All teams make changes, then they decide which change will be included in iOS 10.3 or iOS 10.4. If a bug is hard to fix and the changes they make to fix that bug is a lot, when they fix the bug they decide that fix to include in iOS 10.4. So, if there is a problem in the fix they can figure it out until iOS 10.4 release which buys a lot of time to see if it affects something else. It is also applicable for big design changes, big features etc.

They maybe have already implemented Black UI to iOS, but they will not include this in iOS 10 releases. Because it is not simple and it needs A LOT of code changes to happen.

Feature implementations may not be related to problem concerns. Sometimes marketing team says "Yeah, okay this feature is looking good, no bugs. But it will be better to include this in iOS 11 to better promote new iOS release."

 

[GCHASE1995]

Bra 7 has sped up my iphone SE and have given me amazing battery life

 

[uandme72]

Do you people recommend that I step down to 10.2.1 to resolve the problem of missing notifications from Notification Centre. 10.3 is perhaps not coming this week- even beta 8 which could solve this problem.

 

[Mlrollin91]

Do you people recommend that I step down to 10.2.1 to resolve the problem of missing notifications from Notification Centre. 10.3 is perhaps not coming this week- even beta 8 which could solve this problem.

Is this a known issue, or are only you expericing it? Have you tried reset all settings?

 

[LoveToMacRumors]

Do you people recommend that I step down to 10.2.1 to resolve the problem of missing notifications from Notification Centre. 10.3 is perhaps not coming this week- even beta 8 which could solve this problem.

What kind of notification problem? If your problem isn't fixed in beta 7 then the final release will most likely not resolve it neither.

 

[Edelheid]

Do you people recommend that I step down to 10.2.1 to resolve the problem of missing notifications from Notification Centre. 10.3 is perhaps not coming this week- even beta 8 which could solve this problem.

If it helps you (save time) my daily driver running 10.2.1 is experiencing that missing notification you speak of. It only started today oddly enough.

 

[uandme72]

What kind of notification problem? If your problem isn't fixed in beta 7 then the final release will most likely not resolve it neither.

Notifications go missing from the Notification Centre. Notifications for new mails dont appear on the NC. If at all they show, they disappear within seconds.
It starts happening when we clear the notifications once by clicking Clear button at the top right of the Notification Centre.
[doublepost=1490120115][/doublepost]

Notifications go missing from the Notification Centre. Notifications for new mails dont appear on the NC. If at all they show, they disappear within seconds.
It starts happening when we clear the notifications once by clicking Clear button at the top right of the Notification Centre.

I have logged on bug portal, wherein Apple has stated it is duplicate of another bug. So its a known issue.
The notifications also disappear from NC whenever I open the mail app.

 

[LoveToMacRumors]

Notifications go missing from the Notification Centre. Notifications for new mails dont appear on the NC. If at all they show, they disappear within seconds.
It starts happening when we clear the notifications once by clicking Clear button at the top right of the Notification Centre.

Oh yeaaa, I had this before