Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
13 was a bit abnormal, due to the uncertainty with China. So, the only one you can really use is 11. No software release is ever perfect, and it’s subjective, as pick any release & you’ll find someone that had no issues & some that has all the issues.
Hi. That's a good point re. 13 - yes, I remember now that Trump was threatening a trade war that could've caused a significant problem for that year's iPhone launch. Point conceded :)

11 was terrible though - I remember even in the March the next year, notifications still had clipped text and the UI was janky.

I agree that software is hard and perfection is never possible. This isn't meant as a disparagement to the teams that work in Apple's engineering, either.

Pulling right back, I guess I've got two complaints:

1) I really feel that Apple now needs to make the x.0 launch akin to an agile style MVP - a release which supports that fall's hardware launches plus any significant UX changes.

Then the other stuff can come through the year, when it's properly ready.

2) Is that internet distribution of software has lead to a 'launch with it being mostly OK for most people and we can patch the edge cases and optimise it later' culture.

So regular people who update when their OS tells them to do so are essentially entered into an unofficial mass beta programme. This is not cool.

It's not just a problem with Apple, of course - you see it in AAA games (these are probably the worst culprits). I'd just like to see an end to this.
 
  • Like
Reactions: dk001 and naasrd
Yes, I know thanks. That's not it though.

To paraphrase Jason Snell who was talking about this on the Daring Fireball podcast (I think):

It's concerning that there's a group of - presumably very senior - people in Apple who thought that the Safari changes that we saw in June were pretty good and signed them off for the beta & WWDC.

It's almost the very definition of an unforced error.
This is what’s most worrying; that senior people saw the changes as progressive and okayed them. There was nothing wrong with Safari, so why introduce a backwards step? Someone at the top took their eye off the ball and that’s very concerning for future updates. And while it’s a relief that we’re back to normal, the speed and alacrity of the return speaks volumes as to what must have gone on behind the scenes in recent weeks. The people behind this need to go, it was a huge mistake. Huge.
 
  • Like
Reactions: bluecoast
I haven’t, the only thing that has been replaced is the battery. Could they be clamping down even harder on replacement parts? If so, I might need a guide on how to roll back to iOS 15.0.2
It’s the battery replacement that did it. There’s a video on YouTube of a guy switching batteries from 2 iPhone 13s to see if the same happened, it did.
 
  • Like
Reactions: Pearsey
Software is always changing to keep up with hardware and hardware to software to the extremes today… it’s all so organic now it’s never going to be bug free. I’d almost go as far to say is it will never be bug free, because of the constant flux of change. It’s how you manage that and keep pushing forwards is the key. Which I think Apple does extremely well. Take the M1 chip as example.

Bugs are, and always will be, part of software. we are really getting somewhere today, bugs and all, like the new MBP ?

I’ve used iPhones and MBPs for over a decade and no bug has ever stopped me from designing. So it’s not that bad. Worst bug that actually made me think about leaving Apple was the call dropping on the G1 to G3 iPhones.

❤️?
 
This is what’s most worrying; that senior people saw the changes as progressive and okayed them. There was nothing wrong with Safari, so why introduce a backwards step? Someone at the top took their eye off the ball and that’s very concerning for future updates. And while it’s a relief that we’re back to normal, the speed and alacrity of the return speaks volumes as to what must have gone on behind the scenes in recent weeks. The people behind this need to go, it was a huge mistake. Huge.

In your opinion. Put all the people in a room that feel the same as you and you will probably be dwarfed by the people that don’t. And that’s why those decisions went forward.

My thumb loves the new safari.
 
Assuming you turn off the "Auto macro" mode, does manually toggling to the 3X lens get you the same macro effect when holding the camera close to an object?
 
Poor battery life in first day with 15.1 in my 12 Pro compared to 15.0.2

Hope it improve in a few days
I am seeing the same on my 13PM today with 15.1 down 11% already with only 1h19m SOT and 1h58m screen off. We will see though and I have not changed anything and using the phone less today.
 
  • Like
Reactions: jfim88
This is what’s most worrying; that senior people saw the changes as progressive and okayed them.
seems to me that  higher ups let the bugs go to alert users- strategically!

just to alert users,
let then be aware they are using  products
instead of just surfing the net on safari and proceeding with their products unawarely.
"oh I'm so happy my iPads work fine now, whew!"
"thanks s!

my best answer of why the bugs in 2021 happen.
 
Has anyone noticed this? The audio balance slider now shows a number value 7449D5D5-BD84-4BB6-9ED1-D448DCBBA0AC.png
 
Since updating to 15.1, I've had multiple instances of the Messages app on my iPhone 13 becoming unresponsive. I can open the app, but I cannot select any of my texts/iMessages. The only way to fix it thus far has been to reboot. It doesn't happen every time, though, which is almost more annoying. If it did, I'd bite the bullet and do a wipe and restore. I'd prefer not to need to do that, though.

Anyone else experiencing this?
 
Anyone else with photos and messages app running full 60 mins plus overnight after installing iOS 15.1?
 

Attachments

  • D1E7FBBC-BF23-45AA-AA42-CCCAEF931B45.png
    D1E7FBBC-BF23-45AA-AA42-CCCAEF931B45.png
    832.7 KB · Views: 99
I noticed a bug with the proximity sensor not waking up the screen while on call. It works fine in the subsequence call if you don't sleep/wake the device. Anyone facing this issue?
 
15.1 on SE2020. How is Your battery compare to IOS 14.8.

I know battery life is individuel, but is worse og better for You ?
 
Is the bug in the Safari address bar fixed? I'm using automatic night mode and the problem is that the font's color in the address bar doesn't change, so I'll have to close Safari every day to fix it. Very annoying.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.