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.
Apple Acknowledges Microphone Issue With Some iPhone 7 and 7 Plus Models on iOS 11.3 and Later [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
That could be considered a deadly weapon in the Apple Store. I'd hate for it to get caught in someone's gigantic drooping earlobe.
Now they could of course properly test iOS updates, I mean Apple must surely be bearing those fruits if designing and controlling all the hardware and software it runs 
But alas no, they would rather slash the budget for beta testing and bug fixing for more profits and then spend that profit on share holders, 100 billion was the latest figure announced yesterday I do believe. They need to tread very carefully after the throttlgate issue as that’s not over yet..
But alas no, they would rather slash the budget for beta testing and bug fixing for more profits and then spend that profit on share holders, 100 billion was the latest figure announced yesterday I do believe. They need to tread very carefully after the throttlgate issue as that’s not over yet..
I think the most common answer I've seen on these threads is that they can't possibly test for everything BUT one wonders if they only test the new release by powering off/powering on?
Now they could of course properly test iOS updates, I mean Apple must surely be bearing those fruits if designing and controlling all the hardware and software it runs
But alas no, they would rather slash the budget for beta testing and bug fixing for more profits and then spend that profit on share holders, 100 billion was the latest figure announced yesterday I do believe. They need to tread very carefully after the throttlgate issue as that’s not over yet..
Well, it's not even about testing for everything in this kind of scenario, but finding devices that might be affected by something when the vast majority of the same type of devices don't seem to be.
OMG it might take 10 guys 30 seconds to test voice quality on each possible device
I’d say that destroying the mic, requiring a physical fix, is quite a big thing to miss during SQA...
Seems like you missed the whole point there--it's not about different models, it's about the issue being apparently sporadic in that it only affects some devices of a particular model while vast majority of them don't experience it. You can have a hundred iPhone 7 devices for example, and none of them would experience the issue, depending on how sporadic and prevalent the issue might be.
OMG It might take 1 guy a single sensible decision to allow downgrading and/or take beta feedback seriously
I think its a possibility testing it’s software is not high up on Apples priorities.. I’ve seen a few posters in here that test betas say how they filed bug reports for bugs that hit the headlines, months before release...
As I said, Apple design and build the hardware and software, they have no excuse.
So deflecting onto something else now. Would downgrading resolve this issue for those that are affected? Did this come up in beta feedback?
[doublepost=1525461231][/doublepost]
There are certainly all kinds of cases that are involved, and that's basically also to say that there are in fact some unforeseen things, just as there are some that could have been avoided or dealt with sooner/better.
Considering their history in bugs, thy could do a LOT more. People don’t excuse Apple bcaus they know how much money they have, it’s customers expect that money to spent on improvements and good quality, not endless bugs..
OK, it might require 2 braincells to get activated simultaneously, but what’s wrong with temporarily downgrading those “isolated”, “minor”, “hard to replicate”, “rare”, “unidentified” issues until they are solved - to restore elementary functionality.
And thus the question that you seemed to have overlooked: would downgrading resolve the issue this is all in relation to?
If Apple might for once introduce such capability (that thousands other IT-companies have) - which should be mandatory by law AFAIK
That rather was an acknowledgement of arrogance (disguised as a question)
Last edited:
I find it interesting how many people don't understand that the addition of diagnostics is likely to cause software to refuse to work with hardware on the edge.
Years ago on the Apple II there was a key combination you could hold on startup to do a longer system diagnostic. If this diagnostic failed, it meant the hardware had a problem. It didn't mean the diagnostic had broken the hardware. Yet I had this argument more than once…
So either not willing or unable to answer the question in the context of the actual topic (and for some unknown strange reason trying to deflect to an ad hominem type of argument based on something that isn't even there). A simple "I don't know" could have been sufficient.
Last edited:
It may require your car to stop working one day for you to understand to whole issue.
It’s up to the maker to get itself in a position to get it fixed - instead of coming with a myriad of complications. Customers shouldn’t know or care how they fix that.
Last edited:
Surprise surprise. More ****** software from Apple. I've been using iPhones since the iPhone 3 and there have NEVER been as many problems with iOS software since Tim's incompetence & Ive's ego ousted Scott Forestall. It's been one issue after another with iOS since 9.
iOS 11. The disaster that keeps on giving. Bet Apple can’t wait to get this sorry episode in the history books. Broken from the start, with updates fixing stuff and breaking other things with impressive consistency.