The thing is that we don't really know what's behind it. Could be the earpiece, could be the connectors to it, could be the chip that drives various aspects of audio, could be the modem, could be the drivers for any of those things, could be something else in the software. While the general overall design might not have really changed, all kinds of components, connectors, drivers, software, etc. certainly has, and a number of times over the years.We know perfection isn't there but an issue like this on a design that's been the same for 4 years just doesn't seem right. Especially the ear piece. I've replaced and fixed iPhones over the year and the ear piece hasn't changed much, if at all, over the years. Trust me. Being in the packaging business, I'm an engineer, everyone thinks everything should be perfect. I know that it can't. Just weird to see these issues almost being a given with Apple. I'd be curious if we could ever see the numbers of users affected but you know that will never be released
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 Confirms a Fix is Coming for Static Noise Problem Affecting iPhone 8 Earpiece
- Thread starter MacRumors
- Start date
- Sort by reaction score
Agreed. It's happening on 100% of iPhone 8 phones - plus and non-plus. The problem is intermittent however and doesn't happen on every call. Coupled with the fact that a lot of people don't use their phones to make calls very often OR they use Bluetooth, earbuds, etc., not everyone has noticed the issue since you must be using the handset (not on speaker) for the problem to occur.
Ah, not really. Just new chips. You ever open up an iPhone 6, all the way up to an iPhone 7? It's pretty much the same thing in terms of internal components. I understand it could be a connector, but just weird to see Apple having all these issues. We all know it's because they sell millions of phones right away and people freak out but that's to be expected. You're paying a premium for the Apple brand. You expect quality above the competition. That's the real point. And Apple has been getting lazy and slacking.
Apple's acknowledgement is nothing more than a way to stop people from returning their phones by saying it's a "known issue". They've already replaced hundreds of phones for this problem. That's costly. They had to acknowledge the issue to stop the bleeding. Otherwise, they wouldn't have said a thing.
I wish brand new latest model iPhones didn't ship with the crappiest version .0 of the newest beta OS. It makes the new phone seem junky & buggy and degrades the whole new phone warm fuzzy feeling.
The user experience in every case of the previous model iPhone running the last version of the previous OS is superior to the newest released iPhone running the newest .0 release.
Apple clearly can't hit an annual cycle OS update without releasing a whole lot of reoccurring bugs. I'm wishing for the year when they'll concede defeat & release on a bi-annual schedule.
The only way to get a 'new iPhone' that's not riddled like Swiss cheese with OS bugs is to buy it in May when the OS is at it's .3.x stage.
The user experience in every case of the previous model iPhone running the last version of the previous OS is superior to the newest released iPhone running the newest .0 release.
Apple clearly can't hit an annual cycle OS update without releasing a whole lot of reoccurring bugs. I'm wishing for the year when they'll concede defeat & release on a bi-annual schedule.
The only way to get a 'new iPhone' that's not riddled like Swiss cheese with OS bugs is to buy it in May when the OS is at it's .3.x stage.
Well, certainly with 6s and the addition of 3D Touch there were more changes internally than just some chips. But, again, even with just some chips and connectors there can certainly be some issues somewhere at times, even just from manufacturing potentially. But beyond that, we are still talking about drivers and software which undergo even more changes with it all (even if the overall UI that the user uses might not seem that much different). So there's something to factor in from that as well.
In terms of paying premium and expecting more and all that, well, there's something to that, although most flagship devices aren't exactly that much cheaper. Expecting somewhat better quality and all that would be within more or less reasonable expectations, but that doesn't exclude some issues here and there, a variety of which have been here and there before as well. Again, it's not unconceivable at all to say that things might be somewhat more worse now that Apple has that much more of a customer base than ever before and more devices in play and all that, and to wish that things would be better. But as far as perfection goes and just the reality of mass production and supporting more and more devices and customers and all that, reality comes into play in quite a large way too.
Kind of makes the whole public beta seem totally pointless, doesn't it? People have been reporting bugs for months that STILL made it into the final GM release. Ridiculous.
I just think the bigger issue with this is that the iPhone 8 really isn't selling well. So an issue with their iPhone that isn't selling well because of the iPhone X is somewhat uncalled for in my opinion.
He was being facetious.
True enough. I truly appreciate all the early adopters for putting up with the inconvenience of being guinea pigs to get most of the annoying bugs out.
I've never been inconvenienced with the "early adopter" bugs. I think it's how you have the ability not to let the little things get in the way of enjoying that "fresh coat of paint".
Inability to make a voice call without digital clicking noises and pops is not a little thing, in my opinion. To each his own. I make voice calls roughly 2 hours a day and couldn't stand it.
I made 2 separate genius appointments with my 8+ and both times the guys were cool, but completely shrugged off what I was saying because they couldn't hear it (in the noisy Apple store). The 2nd time I made sure he entered detailed notes into his system about why I was returning the phone and that it isn't 'buyer remorse.' Overall a fine experience but I can't stand the prevailing attitude over there that if a 'genius' can't see / hear it there mustn't be a problem.
I no longer have a horse in this race, got my money back. Very curious nonetheless what Apple will do to resolve this and whether it truly is a software issue vs. hardware issue. Good luck guys and girls.
...quote: “The noise issue can be bypassed by using headphones or the speaker phone option on an affected device, suggesting the issue lies in the software rather than the hardware.”
If using a headphone or speaker doesn’t exhibit the problem, why isn’t it a hardware problem? The software is used regardless of the audio path.
-Jeff
If using a headphone or speaker doesn’t exhibit the problem, why isn’t it a hardware problem? The software is used regardless of the audio path.
-Jeff
Apple did me a huge favor. I've always wanted to "New phone, who dis". Now iOS 11 with the new RSNP1.0 feature (Random Static Noice Problem), gives me that ability.
Quick, somebody call me.
Quick, somebody call me.
OK, I guess it depends on what the bug is, but either way the cautious crowd appreciates people like you
.....ground control to Major Tom.....Apple did me a huge favor. I've always wanted to "New phone, who dis". Now iOS 11 with the new RSNP1.0 feature (Random Static Noice Problem), gives me that ability.
Quick, somebody call me.
I see both sides of this argument. I have no idea how this issue got past all the developers and engineers that work on the iPhone. On the other hand, it's not the end of the world and people need to calm down. Posting the ten billionth "LOL IT JUST WORKS" comment isn't going to fix this issue any faster.
LOL. I love this baseless "I hate this company personally, so somehow that must make them incompetent" viewpoint. As though Google is some run-out-of-a-P.O.-Box outfit, and not staffed with a large number of brilliant software engineers. And let's also ignore that Android is based on open source technologies that have been worked on and refined for decades by other people not working in Mountain View. Even richer, I doubt you even have a real reason to not like Google. Have they personally wronged you in some way you can tell us about? No. You're just another lemming who's gotten sucked into the corporate cheer-leading us-vs.-them bandwagon with others, thinking it's something you have to take up just because you happen to use Apple products.
#staticgate! LOL. It seems I always miss the #gates.
iPhone 4 #antennagate - mine worked fine
iPhone 5 #scuffgate - mine lasted fine
iPhone 6 #bendgate - mine never bend
iPhone 6S #nogate - as far as I recall
iPhone 7 #hissgate - mine isn't hissing
iPhone 8 #staticgate - skipping this one
iPhone X #notchgate - looking forward to this one
iPhone 4 #antennagate - mine worked fine
iPhone 5 #scuffgate - mine lasted fine
iPhone 6 #bendgate - mine never bend
iPhone 6S #nogate - as far as I recall
iPhone 7 #hissgate - mine isn't hissing
iPhone 8 #staticgate - skipping this one
iPhone X #notchgate - looking forward to this one
Can you imagine if Tesla sold the Model S with buggy software that caused the car to suddenly decelerate or lose charge when you're driving in the middle of nowhere? "Things get fixed" isn't a good enough excuse for a phone that you're using all day long, especially when it's disrupting the user experience in many fundamental ways.
Shouldn't have to worry about being early adopter on basically 4 gen product.