Q: Magic Trackpad 2 - intermittent loss of connection

Same annoying issue here with Magic Trackpad 2 on a late-2015 iMac (3,3 Ghz i5/M395/16GB/512SSD), running OS X 10.11.1. This is definitely ruining my user experience with the new iMac.

Especially after scrolling with 2 fingers the trackpad often becomes intermittently unresponsive for one or more seconds, not sensing finger movements or tap-to-click operations (I have not yet seen it missing out on hard clicks). Also here the problem disappears as soon as the trackpad is connected with the charging cable.

Bluetooth interference or a defect in the iMacs Bluetooth assembly can be considered ruled out: the problem occurs in different (also completely non-wireless/non-USB) settings and the trackpad exhibits the same behaviour when being connected to a late-2011 Macbook Air and a late-2013 Macbook Pro (both running 10.11.1).

Other usual troubleshooting procedures such as PRAM/SMC reset or such as advised in this thread did not help to improve the situation.

It seems the problem is more pronounced when applying only little pressure with the fingers, as if the capacitance changes under these circumstances were not properly translated into Bluetooth signals. The fact that the trackpad is working flawlessly when wired might suggest that the issue is related to the trackpads Bluetooth assembly/driver, possibly also to a minor voltage drop affecting the trackpads Bluetooth capabilities.

Right now I can imagine 3 possible causes:

• A general problem with El Capitans Bluetooth support (as I could not test the trackpad on other OS X versions)
• A defective trackpad (https://discussions.apple.com/thread/7306296, here a similar problem was solved by replacing the trackpad)
• A design flaw with Magic Trackpad 2

Anyone having suggestions?

(Typing this I notice that the return key on my 5 days old Magic Keyboard 2 starts making a squeaking noise, resembling a small bird. I must admit I am not overly impressed by the quality of my new input devices…)

You have a 14 day, no quibble, return option for either a refund or an exchange.   Use it; I would.

seventy one wrote:

 

You have a 14 day, no quibble, return option for either a refund or an exchange.   Use it; I would.

I know, but this is actually my 2nd replacement iMac. The first two I got had issues with the fan (a ticking noise). As the current machine does not have any noise issues I am not too inclined to send it back. Apple Care told me to send the device in for repair, but given the nature of the problem I am not convinced this would help (besides, I would not to be able to use the iMac for at least another week, not an option either after all the hassle).

You don't have to send the machine back to resolve the problem with the keyboard; just the keyboard.   I believe that the 14 days counts from the date the exchange was made.    Talk to them; you should not feel on 'the back foot'.   If the complaint is genuine Apple will respond fairly; that I believe from previous experience.

@seventy one: thanks for your advice! I have now ordered replacements for both trackpad and keyboard. However, I have seen a Macrumors user with the same problem report that replacing the trackpad did not help, and that his trackpad also did not have any issues under Boot Camp/Windows. So it might be possible that the problem is related to the operating system or some kind of general design flaw. We'll see.

This may sound a touch negative but if there is something wrong with the system, one or two replacements should quickly concentrate minds.    Every replacement hits the bottom line and there is nothing so guaranteed to ensure management attention than ... pressure on the bottom line.

So, my hope is that you already resolved this, but if not here's what I did and it fixed it for me.

In the bluetooth drop down on the top menu bar, I saw there was a random MAC address for a device. No name, no info about it(like if it was a KB or TP or headphones). Once I deleted this from the BT prefs, the trackpad worked perfectly. Not sure what that extra one was from or when it was added to the system, but thats what I found to be the fix.

Hope this helps...