13" Retina Macbook Pro slight trackpad lag

it seem its fixed with latest developer build 14C94b.... testing it for 1 hour and there is no delay, finally!

I confirm that in Yosemite 10.10.2 (currently beta 14C94b) this bug disappeared. No delay!

How can I install that update? Is it possible for an end user or do I need to wait for final release? I am really ****** of that mouse wireless adapter constantly plugged in. Thanks for great news!

You can get information about beta by https://appleseed.apple.com/sp/betaprogram/redemption or https://appleseed.apple.com/sp/betaprogram/.

Nice job! It works perfectly on my MBP13 Retina

Yes, it is gone.... Installed 10.10.2 and no lag.

10.10.2 ... still the same problem... 😕😟

I don´t understand....!!

10.10.2 and no lag. Finally! 🙂 It's been 9 months wait.

I think it's not Yosemite itself. It's rather Boot ROM version. Now I have MBP111.0138.B14. Before 10.10.2 update it was B11.

I too have upgraded to 10.10.2 and found that the problem disappeared for a few days, but then came back with a vengeance! It's immensely frustrating. So much so that, if it is across the board and unfixable, I will take advantage of the 14-day return policy and consider a different model. Apart from this, my MBPr is great. So sad.

I got here trying to find a solution for the same problem, for my MacBook Air, but I fixed it myself and immediately with some inspiration--I cleaned the trackpad. Years of snacking and surfing took a toll, making it hard for the pad to detect movement. Works perfectly now.

I have a mid-2012 15" Retina Macbook Pro that has had this issue since new, on both the built-in trackpad & keyboard and also on bluetooth magic trackpad & keyboards, regardless of using an external Cinema Display or two at the time.

Hardware Specs:

• 2.7 GHz Intel Core i7
• 16 GB 1600 MHz DDR3
• Intel HD Graphics 4000 1536 MB

Current Pertinent Software:

• Boot ROM Version: MBP101.00EE.B09
• SMC Version (system): 2.3f36
• El Capitan - 10.11 Beta (15A216g)

A few of the (drastic) things that have not fixed anything for me:

• New display (originally had image retention & ghosting)
• New logic board (originally had issues with battery showing 30% but prematurely sleeping)
• Secure erased the hard disk & reinstalled fresh copy of Yosemite

Other things I're tried or stared at for way too long:

• Console logs do not reveal anything obvious
• Activity monitor results are irrelevant, meaning nothing is obviously hogging resources at any time
• Variations of external displays, plugged in or battery powered, bluetooth or built-in
• PRAM reset
• SMC reset

Here's the thing about this that bothers me the most: after a new display, new logic board, & secure erasing the hard drive, when booting via Internet Recovery the issue still exists before the operating system is even installed on the drive. That has to rule out operating system configuration, regardless of what version of OS X (which I've gone through 4.)

My wife and I both have 2014 11" Macbook Airs and I use a 6 core Mac Pro at the office, and none of those machines have ever exhibited this issue, so I find myself using them more often than my rMBP as a result.

I have never been able to duplicate this issue on any Retina Macbook Pro I've toyed with at any retail store, and I've made it a point to visit Apple retail stores across the country while traveling to compare.

This issue feels and seems totally hopeless for these machines. Even after spending way too much time educating myself, I've concluded that "It just works" doesn't indicate how well, just that it does in some capacity. The issue goes away completely randomly, and always comes back.

My best guesses are that it's:

• A component on the logic board that only a certain percentage of machines have, and we've been lucky enough to win the same defective ones
• An SSD problem with reading/writing something to logs & swap
• A serial or bus problem with quickly translating user input to screen output

If there's anyone out there at Apple that's reading this, this issue is very real and very frustrating. My machine, for example, cost $4k USD when it was new, which is way too much money for something that can't calculate user input as quickly as my 15 year old Sony Vaio machine still can.

After getting my Macbook Pro back and still having mouse-lag issues, I returned to the Apple store and had a nice Genius run more diagnostic tests. This time the battery failed, which meant replacing the entire bottom-end, including the keyboard and trackpad assembly.

Consider that in 2 weeks, my 2012 rMBP has both a new top half and a new bottom half, with a new operating system image, and still exhibits this issue.

I refused to take my laptop back, but they also refused to keep it, so my next steps are escalating to Apple Customer Relations tomorrow.

While I was at the Apple store, I went from machine to machine to test them for this issue, and every single one of them exhibited the exact same trackpad lag except for 11" and 13" Airs and Mac Pros. I suspect the Mac Mini won't have this issue, but they didn't have any on display to test. I also suspect this issue only occurs on devices with some specific hardware support for retina and graphics switching, excluding the Mac Pro which won't have the power saving features of laptops. That said, disabling graphics switching in settings doesn't alleviate the issue (for me) whether plugged into power or not.

If my assumptions are correct, there's basically nothing we can do but avoid retina devices (including the brand new Macbook, Macbook Pros, and 5k iMac) until processing power and GPU power can keep up.

If my assumptions are incorrect, that means the disk images at my local Apple store just happen to have the same low-level software bug that all of our machines seem to have, in which case it's Apple engineering's problem to solve for all of us.

As much as I also hate to say we're all using it wrong, something else worth trying is using the flat part of your pointer finger instead of the tip. I almost always use the tip, which I suppose has less surface area and might cause tracking issues, almost as if it's trying to prevent an accidental tap but than sees movement and catches up. This doesn't explain the keyboard lag, but maybe this is just happening to us because we know how to duplicate it and now we can't stop.

I had my wife and a few of her coworkers test my theory, and none of them were able to duplicate the issue on my machine until I constrained the circumstances and told them how I'm able to do it every single time. I dunno... It's such a bizarre issue that shouldn't even be possible, that I still think this is a bug even if it's edge-case and obscure.