Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Going back to Apple Store with my Macbook pro 2018

chekie

chekie

macrumors member
Original poster
Sep 11, 2013
93
63
I am one of the unlucky ones with MacBook pro 15 2018 that has crackling speakers. It happens only occasionally. In fact, it only happened three times within the 3 weeks since I had it. And killing the coreaudiod process fixed it every time. Also I experienced a different but related issue: when I play videos on youtube with chrome or safari, the videos just quickly fast forward to the end. It happened only once and killing coreaudiod also fixed it.

I talked to apple support over the phone and was told that I could bring it back to apple store for a replacement. I am wondering if it is worth it. On one hand, most people believe that this is a software issue, eventually system update will fix it. (By the way, I am running High Sierra with latest patches). On the other hand, some people just never experience it and new unit replacements seem to fix for others.

So I want to hear from those who have or had this issue. Did the system patches (2018-002 and 2018-003) fix the issue for you? How many of you have any luck with replacement units? And for those who still have the issue, are you going to wait it out for new patches?

Another reason why I am a little reluctant for replacement is that I heard something about replacements not always being new ones. Sometimes Apple uses refurbished, open-box, or exchanges devices for replacement. I wonder if it is true.

Thank you all and have a happy holiday.
 
If it were me, I would verify that the replacement computer is new... if not, then I would keep the one I have. If so, then I would take the replacement. If the new replacement has the same issue, I would live with it until Apple corrects the problem.

Joe
 
PROFESS0R said:
If it were me, I would verify that the replacement computer is new... if not, then I would keep the one I have. If so, then I would take the replacement. If the new replacement has the same issue, I would live with it until Apple corrects the problem.

Joe
Click to expand...
Thank you Joe. Is there any reliable way to verify if the replacement is new?
 
Let’s see now, eventually it will be fixed. Really.? How do you know it will eventually be fixed or how long until it’s fixed knowing Apple. If it were me, I would just send it back, give me my money and wait until it’s really fixed. I would not trust Apple anytime soon in light of what’s going on with the butterfly keyboard and the T2 chip.
 
  • Like
Reactions: Pangalactic, Plutonius and turbineseaplane
Just to agree with others here, get your money off the table.

The only hope for Apple fixing this crap moving forward is if people are voting with their wallet and hitting them where it hurts.

It’s almost like Apple is playing a game to see how much they can charge and how much the customers will tolerate and… Frankly I’m pretty shocked with what some people on the forum are willing to tolerate.
 
Last edited:
  • Like
Reactions: greenmeanie, Never mind, tsukeyomi and 2 others
As much as I am disappointed in recent MacBooks' quality, I do need a Mac for work as mobile app development machine right now. So getting a refund and waiting for future MacBooks with hopefully improved quality isn't really an option for me... :(
 
chekie said:
As much as I am disappointed in recent MacBooks' quality, I do need a Mac for work as mobile app development machine right now. So getting a refund and waiting for future MacBooks with hopefully improved quality isn't really an option for me... :(
Click to expand...

Any reason you need the very newest ones?

Could you get a new/refurb/pre-owned 2015 model that would suffice and keep as much of your hard earned money in your pocket while we let Apple figure out if they're going to build reliable products again?
 
I doubt it's a software issue since it doesn't appear to be a common occurrence. I'd certainly take the replacement. That said, do upgrade to Mojave.
 
chekie said:
And killing the coreaudiod process fixed it every time.
Click to expand...
What does that tell you? :rolleyes:
We've seen the same thing hundreds of times with faulty kexts on Hackintosh systems until someone supplied a properly working one. This is a software issue, period. It'll be fixed in the future, infact it's been fixed on the iPads as well. This is where Apple's priorities are right now. iOS first, macOS later... just wait until an update.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back