Forcetouch Trackpad and Keyboard freezing on Mid-2015 15" MBP

Question

Level 1

10 points

Forcetouch Trackpad and Keyboard freezing on Mid-2015 15" MBP

I've just purchased the Mid-2015 15" MBP with the 2GB AMD Radeon GPU.

After transferring all my user files from my old Late-2011 17" MBP, the trackpad and keyboard periodically (usually soon after boot, and then randomly afterwards) lock up and become unresponsive, including the loss of haptic feedback. The OS itself continues to run.

The only thing that seems to fix it is plugging in any USB mouse - which makes everything work again immediately - and then unplugging it. Then it will keep working for a while. There doesn't seem to be any single catalyst.

I've reinstalled Yosemite from online recovery, but the problem persists.

Has anyone else encountered this issue or have any potential solutions? Could this be hardware or software? Does copying user files change any of the system files that deal with the trackpad and keyboard? It still happens even when logged into a new user account created after copying my old files over.

Do let me know if there's anything I should try out. Thanks!

MacBook Pro (Retina, 15-inch, Mid 2015), OS X Yosemite (10.10.3)

Posted on Jun 2, 2015 12:56 AM

Reply

Answer 1

Mar 13, 2017 3:46 PM in response to NazalWeazel

I have the same problem. My MBP is retina, 13-inch, early 2015 with MacOS Sierra 10.12.3.

I noticed the keyboard and force touch lock up randomly. I experienced almost every scenarios provided by others in this discussion.

It first started with unresponsive KB/FTOUCH when trying to wake up the MBP from sleep mode. However, restart and shutdown fixed it. As the problem kept happening over and over I tried PRAM and SMC reset; seemed successful at first but the problem came back after a while. Recently, I noticed even restarting and shutting down the computer don't fix the problem sometimes. As the last instance (prior to this post), they got functional all of a sudden while i was working with BT magic mouse and external keyboard.

So, I want to confirm that it's completely random.

I hope it is a software issue, as I don't have access to authorized Apple Store in my country.

Please keep sharing your experiences and workarounds, if there's any.

Regards,

Reply

Answer 2

mikonium

Level 1

5 points

Jun 2, 2015 11:25 AM in response to NazalWeazel

I am having the same issue, but on a brand new May-2015 15" MBP. I find I can resolve the issue by putting the computer to sleep and waking it up (holding the power button for a second), but this isn't a feasible long-term solution. Kind of annoyed that a brand new computer isn't working as well as my old one...

Reply

Answer 3

bcrsr

Level 1

14 points

Jun 2, 2015 12:33 PM in response to NazalWeazel

Same trouble here. It happens immediately on reboot. I have reset PRAM and SMC. Neither helped. I also get some screen flicker. This machine was purchased yesterday. I am considering taking back and just staying with my late 2013 model. For the price of these machines, they should be flawless out of the box.

Reply

Answer 4

NazalWeazel Author

Level 1

10 points

Jun 2, 2015 2:17 PM in response to NazalWeazel

Do both/either of you have android file transfer installed? After extensive forum searching it seemed to be an issue with the early force touch macbooks.

Uninstalling android file transfer (and rebooting) seems to have done the trick, ~12h without errors so far.

If both of you have it and uninstalling fixes it, I will mark this as solved, though it would be nice if someone knew exactly why this was happening...

Reply

Answer 5

NazalWeazel Author

Level 1

10 points

Jun 2, 2015 2:18 PM in response to bcrsr

Also bcrsr, I also get some moderate screen flicker every once in a while, so do let me know if you find a cause/solution : )

Reply

Answer 6

mikonium

Level 1

5 points

Jun 2, 2015 2:57 PM in response to NazalWeazel

I had it, and uninstalled it, and rebooted, but the problem still occurs about every 30 minutes. Is there some extensive way I'm supposed to delete it besides doing something like running it through AppZapper?

Reply

Answer 7

bcrsr

Level 1

14 points

Jun 2, 2015 3:12 PM in response to NazalWeazel

Will do.

Reply

Answer 8

bcrsr

Level 1

14 points

Jun 2, 2015 3:13 PM in response to NazalWeazel

I do not have it installed. I must have another issue.

Reply

Answer 9

NazalWeazel Author

Level 1

10 points

Jun 2, 2015 3:44 PM in response to mikonium

EDIT: Issue has reoccurred, Android File Transfer doesn't seem to be the cause. Back to square one.

mikonium-

I didn't do anything more than uninstall it before it fixed (or at least so far...) the issue for me, but perhaps a fresh install of Yosemite may help. This also resolved slow wifi speed for me. Was surprisingly easy to do from online recovery, I thought I'd have to re-import my user files but it started up with them intact and happy.

However, it seems that although Android File Transfer was the cause for me, it isn't the only cause. As bcrsr has stated, he has the issue without having Android File Transfer at all.

bsrsr-

Do you have any other apps that deal with/change the USB protocol in any way? It almost definitely seems to be related to how the laptop is handling USB connections.

Anyone else-

If you know what you're doing and don't mind messing with your new computer, is anyone able to recreate the issue by running Android File Transfer and seeing what's happening behind the scenes? It may not be AFT at all, but getting rid of it is what got things working for me.

Reply

Answer 10

NazalWeazel Author

Level 1

10 points

Jun 2, 2015 3:42 PM in response to NazalWeazel

I take everything back, it's just happened again. Plugging in and unplugging a USB mouse solves it temporarily. AFT was a red herring.

Reply

Answer 11

bcrsr

Level 1

14 points

Jun 2, 2015 3:46 PM in response to NazalWeazel

Has anyone disabled the force touch to see if this is the culprit?

Reply

Answer 12

mikonium

Level 1

5 points

Jun 2, 2015 4:13 PM in response to NazalWeazel

Not sure if this will be at all helpful, but here is what my console spat out right before the computer froze up:

6/2/15 7:06:08.078 PM apsd[72]: MessageTracer: load_domain_prefix_whitelist:120: Missing default whitelist file: /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Resources/Subm itDiagInfo.default.domains

6/2/15 7:06:16.680 PM apsd[72]: MessageTracer: load_domain_prefix_whitelist:120: Missing default whitelist file: /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Resources/Subm itDiagInfo.default.domains

6/2/15 7:06:25.282 PM apsd[72]: MessageTracer: load_domain_prefix_whitelist:120: Missing default whitelist file: /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Resources/Subm itDiagInfo.default.domains

6/2/15 7:06:26.645 PM secd[270]: JmISBQl8BHuD402afWqjASPL+f object 226AD5CF dropping from manifest: not found in datasource

6/2/15 7:06:26.645 PM secd[270]: JmISBQl8BHuD402afWqjASPL+f object 276CE957 dropping from manifest: not found in datasource

6/2/15 7:06:26.645 PM secd[270]: JmISBQl8BHuD402afWqjASPL+f object AF4C67C9 dropping from manifest: not found in datasource

6/2/15 7:06:26.645 PM secd[270]: JmISBQl8BHuD402afWqjASPL+f object ECDB6902 dropping from manifest: not found in datasource

6/2/15 7:06:26.645 PM secd[270]: JmISBQl8BHuD402afWqjASPL+f object F6FC8A3E dropping from manifest: not found in datasource

6/2/15 7:06:33.883 PM apsd[72]: MessageTracer: load_domain_prefix_whitelist:120: Missing default whitelist file: /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Resources/Subm itDiagInfo.default.domains

6/2/15 7:06:44.000 PM kernel[0]: TCON: Status check (1) (EXIT:0x0005028f)

6/2/15 7:06:46.000 PM kernel[0]: TCON: Status check (1) (EXIT:0x0005028f)

6/2/15 7:06:47.000 PM kernel[0]: TCON: Status check (1) (EXIT:0x0005028f)

6/2/15 7:06:48.000 PM kernel[0]: TCON: Status check (1) (EXIT:0x0005028f)

6/2/15 7:06:50.000 PM kernel[0]: TCON: Status check (1) (EXIT:0x0005028f)

6/2/15 7:06:51.000 PM kernel[0]: TCON: Status check (1) (EXIT:0x0005028f)

6/2/15 7:06:51.000 PM kernel[0]: TCON: Ack issue

Reply

Answer 13

NazalWeazel Author

Level 1

10 points

Jun 2, 2015 5:34 PM in response to bcrsr

Giving it (disabling force-touch) a go, been a few hours since and no errors yet. Will report back if anything changes.

Reply

Answer 14

mikonium

Level 1

5 points

Jun 2, 2015 7:09 PM in response to NazalWeazel

Just tried disabling force-touch/haptics and the problem persists.

Reply

Answer 15

NazalWeazel Author

Level 1

10 points

Jun 2, 2015 10:41 PM in response to mikonium

Likewise, problem persists even with force touch disabled. Screen also occasionally flickers. Hardware fault with this model then? Oh dear. How do we inform Apple about this?

Reply