Green tint 😃🤦♂️😂Still not an a build wow what’s taking so long it’s such a minor update lol
Still a while away from a public release.Are you sure guys that these « a », « b », « c »,…. « w » builds are a sign of near public release ?
Franck
I'm referring to the not downloaded tracks. No different than jumping to a time slot in an HD YouTube video as opposed to a 720 or 480 video.They are all downloaded offline so it shouldn’t be buffering
No, not convinced. I believe the letter indicates how many times Apple had to tweak the process on a particular day to get a viable ipsw. So the next day they could run the tweaked process and get an A build. Hence the build letter is meaninglessAre you sure guys that these « a », « b », « c »,…. « w » builds are a sign of near public release ?
Franck
No, not convinced. I believe the letter indicates how many times Apple had to tweak the process on a particular day to get a viable ipsw. So the next day they could run the tweaked process and get an A build. Hence the build letter is meaningless
No chance, since it’s a d build, there’ll definitely be a RC build before final release. ?hmm another beta. I stand by that there won't be an RC, that 14.7 will then just get public release. Maybe next week.
No it isn't exactly. Typically near an end of a version there are less changes to code therefore less commits so they can release several 'a' builds back to back before a final. Folks equate this to "almost ready to release". But Apple could just as easily release 15 betas all 'a' builds during the entire beta cycle before a release.Are you sure guys that these « a », « b », « c »,…. « w » builds are a sign of near public release ?
Franck
Exactly this.No, not convinced. I believe the letter indicates how many times Apple had to tweak the process on a particular day to get a viable ipsw. So the next day they could run the tweaked process and get an A build. Hence the build letter is meaningless
Exactly, Has no bearing on anything other than how many commits a particular build had before releasing it. Look back at iOS 14.5 betas. Betas 4,5,6,7,and 8 were all 'a' builds.Yes. I also think that these build letters are only the number of iterations needed to obtain a « viable ipsw file » to be released to testers, and doesn’t presume how far/near is the next public build.
Franck
No chance? Look at iOS 14.4. Beta 2 was 18D5043d then the very next build was the release version 18D52. There never was an 'a' build for iOS 14.4. There may or may not be an RC actually released to devs 1st but not necessarily since an RC is the release version.No chance, since it’s a d build, there’ll definitely be a RC build before final release. ?
No, not convinced. I believe the letter indicates how many times Apple had to tweak the process on a particular day to get a viable ipsw. So the next day they could run the tweaked process and get an A build. Hence the build letter is meaningless
Yes. I also think that these build letters are only the number of iterations needed to obtain a « viable ipsw file » to be released to testers, and doesn’t presume how far/near is the next public build.
Franck
No chance, since it’s a d build, there’ll definitely be a RC build before final release. ?
I always see “green tint” in comment like it’s a show stopper. I highly doubt 14.7 will fix it… I think the only major change in this version is the fix for Split Tunnel mode of VPN since at 14.6, Split tunnelling is a hit and miss.
Yeah, if I was having a hardware issue, I would have had Apple look into replacing my hardware. Maybe even setting it up again in store, to confirm whether or not the hardware is still having an issue.iOS 14.7 and iOS 15 betas have no fix. It’s hardware issue, but the user is in denial, and being lazy in regards to getting it replaced, which many other owners have done already, as per the threads I’ve read on the Apple community pages.
I think the user is waiting until just before Applecare expires and getting a swap out to a “new” phone.Yeah, if I was having a hardware issue, I would have had Apple look into replacing my hardware. Maybe even setting it up again in store, to confirm whether or not the hardware is still having an issue.
Ahhhh, that's a great idea. Then I'd assume there'd be no need to keep posting about it then, right? Right?? ???I think the user is waiting until just before Applecare expires and getting a swap out to a “new” phone.
Wouldn’t AppleCare just swap it for another of the same model?I think the user is waiting until just before Applecare expires and getting a swap out to a “new” phone.
Yes, but there's been times in the past where there was a small number in a batch that were bad or something similar. Getting a phone 3-4 months later, you're pretty much guaranteed to get a different batch....Wouldn’t AppleCare just swap it for another of the same model?
Yes it will be a phone of the same specification. By ‘new’ I meant one with no scratches or dings and with a brand new battery. Interestingly it won’t be the “same model” because Apple use different model numbers for new phones and the swapped out phone equivalents.Wouldn’t AppleCare just swap it for another of the same model?
It Hans't even proven it's a hardware issue, I'll wait a little longer, some people have been getting a new device or installing new software and having green tint show up.iOS 14.7 and iOS 15 betas have no fix. It’s hardware issue, but the user is in denial, and being lazy in regards to getting it replaced, which many other owners have done already, as per the threads I’ve read on the Apple community pages.
If it was software, it would be more common. Instead it’s a handful in comparison to the amount of devices out there.It Hans't even proven it's a hardware issue, I'll wait a little longer, some people have been getting a new device or installing new software and having green tint show up.
In the end we are all guessing if it's hardware or software. ?