Trackpad extremely choppy after 10.10.3 upgrade, no issues before.

I have the same issue in my Macbook pro (Mid 2010). I replaced the battery pack, Yesterday. It wouldn't fix my issue. I have another appointment, Today; with the Genius bar. Gonna replace my track pad. Let's see if it could fix the issue.

I am having the exact same issue. I have tried 2 separate trackpads and both are experiencing jumpy and erratic behaviour, rendering my 2014 iMac almost unusable.

I am back to my  mouse, and although it is not jumpy or erratic, it's responsiveness is slow even thought I have it set to maximum responsiveness in settings, and will not automatically connect after being turned off.

This seems to be a bluetooth issue in general as all my bluetooth devices are having issues.

Had my trackpad replaced at the Genius Bar, took it home, and the issue is still the same. This definitely means it's not a hardware issue. FYI, my wireless keyboard is working perfectly.

I reported this to  ad they have escalated it to their engineers.

I have tried in safe mode everything works fine with my trackpad.... logged back in normal mode again it choppy..... this is happening after 10.0.3 update... plzz help me.

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.

You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

4. Here's a general summary of what you need to do, if you choose to proceed:

☞ Copy a particular line of text to the Clipboard.

☞ Paste into the window of another application.

☞ Wait for the test to run. It usually takes a few minutes.

☞ Paste the results, which will have been copied automatically, back into a reply on this page.

These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is sometimes, but not always, slow, run the test during a slowdown.

You may have started up in "safe" mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.

6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

7. Load this linked web page (on the website "Pastebin.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.

If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.

8. Launch the built-in Terminal application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter

exec bash

and press return. Then paste the script again.

10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

[Process started]

Part 1 of 8 done at … sec
…
Part 8 of 8 done at … sec

The test results are on the Clipboard.

Please close this window.

[Process completed]

The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.

Wait for the final message "Process completed" to appear. If you don't see it within about ten minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it and go to the next step. You'll have incomplete results, but still something.

12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.

If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.

14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

______________________________________________________________

Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Don't bother calling Applecare unless you want to haul your iMac to the Apple Store. They're sending me another trackpad which is not going to change anything because it's a freaking SOFTWARE ISSUE. My bluetooth keyboard works fine. My old trackpad, my replacement trackpad, and in all likelyhood the second replacement trackpad will all have this issue.

All I want is for them to send me a mouse so I can still use my computer while they get their s*** together. I guess I'll pony up $10 and go buy a crappy wired mouse myself. I should't have to do this with a high-end Apple product.

Your issue will be back, rest assured. It worked for me for 10 minutes before it returned.

Here's an ACTUAL SOLUTION: Download the 10.10.4 beta and these issues will be gone! I found another thread about it, tried it, and have been running 100% for the last 3 hours.

https://appleseed.apple.com/sp/betaprogram/

I'm having exactly the same issue on an iMac 5K with 10.10.3. Just followed idea to install 10.10.4 beta and it makes no difference 😟.

Also have logged a call with Apple Support and they are about to tell me to wipe the system and reinstall 10.10.3. I think I'm going round in circles.

Have the same problem with a late 2013 iMac and 10.10.3 - as well with 10.10.4 public beta (14E11f). As soon as I start using Safari or Mail, the cursor starts jumping when I move the position. I also have this problem in safe-mode (as soon as I start using Safari). I don't have any problems when I start the system and just use Firefox for example. When using the Magic Mouse it also feels a bit choppy and slow (even with fastest settings) but not as unusable as the trackpad. Today I figured out, that when using the administrator account (I typically work with a non-admin user) I don't have these problems. Really strange...

@Linc: Your script is not really transparent, because you did everything to obfuscate it - even for me (as a shell coder) it'd take lots of time to figure out, what the script is really doing... :-(

I finally could solve my issue by disabling and re-enabling Safari iCloud sync. First I logged out from iCloud completely and rebooted the system. Problem was gone. Then I logged in to iCloud again - Problem raised up again. After just disabling, rebooting and re-enabling Safari from the iCloud option menu, the problem didn't came up again. I now keep my fingers crossed, that this is a permanent "fix". 🙂

I had a similar problem and resolved it as follows:

Hold down option key while selecting Bluetooth icon on menu bar.

Select "Create Diagnostic Report on the Desktop" (you may need to enter administrative password to give permission.)

A zip file will appear on desktop - open it.

In the new finder window look for a file that doesn't seem to have anything to do with Bluetooth - in my case there was a record of a Google Drive crash. What could Google Drive have to do with Bluetooth or the trackpad pointer? I have no idea.

In any event, remove or disable the program referred to by the file.

Let me know what happens.

Apple Support had me install a fresh copy of 10.10.3 on a brand new partition on a clean drive. This worked perfectly for five hours, where as the problem on my default OS appears after just a few minutes - so progress indeed.

I bit the bullet and after checking all the backups were in the right place and up to date, I rebooted in to Recovery mode, erased the MacHD partition and performed a clean install of 10.10.3 to it. Software reinstalled, OS updated with the latest 10.10.3 graphics update and manual recovery of files now taking place. So far the problem has not come back ... yet!

Ever hopeful!

And ... it's stopped working again. I'll be calling Apple later, once my utterly unnecessary restore has completed 😟.