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.
- Status
Yeah I can't do Zollotech. He's always showing up and does some of the most comprehensive coverage but like you said, a looooooot of repeating stuff. ".... so no issues there...." x 20.
I think my current favorite is JT from Painfully Honest Tech. Dude pulls no punches.
I got my 13 Pro Max and I'm debating on if I should install the new beta or stay on the stable builds for a while. Anyone else having the same issue? 🤣 I have been experiencing annoying bug when unlocking the phone, like it lights up in two stages (I've seen someone else reporting the same thing), and I really hope it's fixed in 15.1, but I will be disappointed if I installed the beta and it's not fixed.
from what I’ve seen on here buddy with the 13 pro and max, B3 was an over heating mess. I’d like to think B4/RC today would be fixed in that respect. Probably wait till someone jumps straight in with no fear and go from there feed back.
I have B3 on my 13 Pro and it's damn near flawless. The issue you're seeing with the home screen lighting up in phases sounds like an auto-brightness bug; I'm also not seeing that on 15.1.
I installed the beta directly from 15.0.2 and no overheating at all. From what I have read the heating up results from going from b2 to b3.
It's been happening only when the "Tap to wake" setting is disabled. But I really hope it's fixed in the 15.1. Like it's not a big deal, but you see it every time you unlock your phone and you know it's not the expected behaviour, so it annoys me.
I don’t use raise to wake. I only use tap to wake so I’m sorry I wouldn’t be able to test that.
Frankly, I miss how fast the UI felt in the initial betas of iOS 15 and especially the beta 5 where Safari was near perfect (for me). It happens every year. The software works fast for a while, then the later betas screw it right back.
I deleted beta profile. Beta 3 runs smoothly on my 12 mini, so waiting for official release. B2 was my worst experience with Beta software ever.
The next beta could be even more better…
Could be! Could also be a step or 12 backwards. The nice thing about this community is there's plenty of folks who are okay with playing guinea pig (such as myself) and you can read all the feedback before making a decision. I'm with @NovemberWhisky, beta 3 feels to me like it should be the RC.
yeah, people need to get over the letter thing. The "D" means it took 4 tries to get the build to pass QC. But (unless I am misunderstanding the process), it DID pass QC on that 4th try. So, I think we will get a RC this week for release in conjunction with the event next week. Not for any good reason other than they seem to try to time it that way.
how I see it, is it’s just a good gauge of where we are though no? let’s you judge what could be next as we close in. like at this stage, some feel an “A” build will come in first, before the “RC”. And others feel it’s ready for an “RC” build regardless of the jump from “D”.
So I’m really interested in this, as plain and boring as it might be. Saying that, do we not think then that a beta needs to hit an “A” build to get final QC sign off at Apple, would that not be a goal in their stages before public official release do we think?
I’ll only ever ask once 😉
I don't track this, but a good answer to your final question would be whether every last beta of an iOS release was an "A" build.
I don't believe that is a metric they require, no. I think it's likely that in a situation like we have now, the next build compiled could be the one we're on with the logging/beta code removed. It could also be a completely new build that was acceptable on first compile and never had the beta junk to begin.