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.
How many 2018 MacBook Pros are problem free?
- Thread starter sk8r1230
- Start date
- Sort by reaction score
I chose yes, though to be honest, I have only had the laptop now for about 8 hours. I can confirm that during the last eight hours of setup and app install, I have not had any of the listed problems. Here's hoping it stays that way...
2018 MBP 15" 2.2/16/256/555X
2018 MBP 15" 2.2/16/256/555X
How lmao? It’s either a yes or no. If it’s a no I’d like to see the issue since there are multiple listed on this site.
Mine is not perfect. Not sure if backlight bleed or just IPS glow. Unnoticeable in a bright room but very noticeable in pitch black.
Yours doesn't look like a 2018 MacBook Pro since Apple hasn't updated the non-touchbar model.
It is a 2017 but the screen is the same across the board 2016,2017,2018. The manufacturing date of my MBP is June 6th, 2018 so its a fairly recent one.
I understand and sure you can contribute as you wish but that sort of throws off the discussion as we are focused on 2018 MacBook Pros and technically yours is a 2017 model as we are trying to drill into the issues that the 2018 models have. Yours I would say might be a somewhat universal issue.
Anyways, with that said, I think it's best for you to take your MBP back to Apple to have this checked. I personally have yet to experience such an issue but it isn't unheard of. Give the replacement a try and see if it still has the same issue.
Brand new 2018 13" MBP... keyboard stuck key after 2 days of use (I'm a neat freak and I keep my machine as spotless as possible - no eating while using machine etc.). I had to send it to Apple for a fix. The tech told me that the new mesh under keys (there to reduce sound) will probably cause more stuck key issues than the previous version because it's easier for stuff to get stuck.
It boggles my mind why they changed the KB to begin with... there was nothing wrong with previous MBP KB.
It boggles my mind why they changed the KB to begin with... there was nothing wrong with previous MBP KB.
You mean in comparison with mbp 2015 and earlier? One reason is to make it thinner. Another is it actually feels more pleasant to type on, at least to me. It's somewhat like mechanical keyboard, and you also don't see the backlight through the edges. It's cool.
Whether these changes are worth the decrease in reliability is another matter. Probably not.
38% of the new MacBooks have some sort of a problem, wow!
For people who are saying this poll has a selection bias - yes and no. Macrumors may not represent an average Apple user community, but there's no reason to assume people come here purely because they have problems. Even assuming that a lot of users have not reported any issues, it is still an alarmingly high failure rate.
I didn't vote, but I had a MBP 2018 15'' test-drive for a couple of weeks, and keyboard developed a pressure issue when some keys had like 1/2 of the normal travel and I could hardly feel pressing them.
For people who are saying this poll has a selection bias - yes and no. Macrumors may not represent an average Apple user community, but there's no reason to assume people come here purely because they have problems. Even assuming that a lot of users have not reported any issues, it is still an alarmingly high failure rate.
I didn't vote, but I had a MBP 2018 15'' test-drive for a couple of weeks, and keyboard developed a pressure issue when some keys had like 1/2 of the normal travel and I could hardly feel pressing them.
Jesus tap-dancing Christ, not this type of thread again.
I have never met one single satisfied user use their problem-free MBP to open a thread on MacRumors and say "My Mac is totally fine and has no issues". There simply isn't a thread to develop from that aside from maybe "good for you!".
Those 3 or 4 users with coil panic or kernel whine, though, they're all the rage. And suddenly they're the majority of users.
I have never met one single satisfied user use their problem-free MBP to open a thread on MacRumors and say "My Mac is totally fine and has no issues". There simply isn't a thread to develop from that aside from maybe "good for you!".
Those 3 or 4 users with coil panic or kernel whine, though, they're all the rage. And suddenly they're the majority of users.
You don't, it just happens.
It's called a kernel panic because you're then panicked your $5000 laptop is broken.
I think and agree that people need tp stop posting stuff like this.
Also, we had a person chip in who actually has a 2017 MacBook Pro NOT a 2018 model. Anyways, I think that the biggest issue here as well is that we obviously have a bunch of overly anal/OC people. Check out the posts regarding how the delete key sounds louder than the other keys etc. How their Macbook Pros run really "hot" etc. Makes me giggle to be honest.
I think that any post of any relevant nature can be published here. In fact, I think, if your aren’t a fan of these threads then scroll passed.
This thread also has someone chip in to vote “no problems,” even though they have only had it for 8 hours. Which equally biases the poll. Folks who are having kernel panics and keyboard issues, likely had their machines longer than 8 hours before the first problem occurred.
But such is the nature of these kinds of threads/polls.
Update:
So, I took the NEW 2018 MBP into a certified support center. They cleaned the KB, took the key apart, etc. It still sticks. They tried to order a new KB (because you can't just replace a single key on these machines), Apple said it will take 1 month to get the parts. The support center tried to send it to Apple to have them fix it (which would be 5-7 days)... now here's where it gets crazy...
The process for sending the unit back requires the use of an online ticket system. When the support center fills out the form, it sends back an error saying that my BRAND NEW MBP cannot be accepted by Apple for repair as of now. In order to get a full replacement Apple needs to go through their process to try and fix it first... but I can't send it back to Apple as their process is broken (going on 2 weeks now). So, I can't return it and it will take a month to get the parts.
I called Apple support and it got escalated and the guy I talked to said Apple would never replace it and I'd probably have to pay to get it fixed (even though I did nothing wrong and went through the appropriate channels to get it fixed). He also said that the support center I'm using is crazy and they can certainly send it back to Apple to get fixed. I watch the guy at the support center go through the process 2 times in front of me and I saw the error... it flat out says Apple will not accept the new MBP with touchbars back for repair as of now. He tried calling Apple too, same response. The customer facing side of Apple support WILL NOT talk to the stores or certified support centers - so I can't get them both on the phone to see they are contradicting themselves.
I am sooooooooo fricken disappointed. I've been an Apple user for 15 years and I've never had any problems. Now the one time I have a problem no one can help. I'm now computer-less (which means I can't work) for 1.5 months unless I want to use a portable machine in clamshell mode tethered to a usb-c hub. It's not the end of the world or anything, but Apple has lost a ton of respect from me now.
Mine is almost perfect, no KP's, no crackling, no whine, no blemishes. But, I was seeing a lot of battery drain while on sleep, so checking the wake reasons I found various EC.LidOpen (User), EC.RTC (Alarm), and XHC1 even though I have most definitely not opened the lid, and I have everything turned off (power nap, notifications, wake for network access, Siri, and bluetooth).
Funny thing, when I do open the lid, the wake reason is not LidOpen but corespeechd <private>, and then AppleDeviceManagementHIDEventService:
rocessWakeReason Wake reason: Host (0x01).
I have a case open with Apple Support, they have some logs and supposedly will get back to me on Tuesday... We'll see.
I do have to say that once I disabled Bluetooth, the battery drain went from ~15% to ~5% in a ~7 hour sleep period; still think 5% isn't normal, nor seeing all those wake reasons...
I also did an SMC and NVRAM reset.
2.6/16GB/560X/512GB
Funny thing, when I do open the lid, the wake reason is not LidOpen but corespeechd <private>, and then AppleDeviceManagementHIDEventService:
rocessWakeReason Wake reason: Host (0x01).I have a case open with Apple Support, they have some logs and supposedly will get back to me on Tuesday... We'll see.
I do have to say that once I disabled Bluetooth, the battery drain went from ~15% to ~5% in a ~7 hour sleep period; still think 5% isn't normal, nor seeing all those wake reasons...
I also did an SMC and NVRAM reset.
2.6/16GB/560X/512GB
Mine is almost perfect, no KP's, no crackling, no whine, no blemishes. But, I was seeing a lot of battery drain while on sleep, so checking the wake reasons I found various EC.LidOpen (User), EC.RTC (Alarm), and XHC1 even though I have most definitely not opened the lid, and I have everything turned off (power nap, notifications, wake for network access, Siri, and bluetooth).
Funny thing, when I do open the lid, the wake reason is not LidOpen but corespeechd <private>, and then AppleDeviceManagementHIDEventService:
I have a case open with Apple Support, they have some logs and supposedly will get back to me on Tuesday... We'll see.
I do have to say that once I disabled Bluetooth, the battery drain went from ~15% to ~5% in a ~7 hour sleep period; still think 5% isn't normal, nor seeing all those wake reasons...
I also did an SMC and NVRAM reset.
2.6/16GB/560X/512GB
Hey, did you figure the issue out?
I also have same problem.