Trackpad once in a while needs two touches to work on Monterey

[Abhay Bobby]

Hey, does anyone have an issue where a touch on the trackpad doesn't register the gesture, sometimes you might have to touch the second time to make it work, its not an all time issue but its noticeably present.
Give me a heads up if anyone facing this issue.
Working on a 16 inch MacBook Pro running macOS Monterey with no prior betas installed into the system

Cheers

 

[Beavix]

You’re not alone.

Tap-to-click issues on B9 and 10 (and now Monterey release)

Hi all, First experience with Monterey has been with B9 but B10 has same issue - has anyone had issues with tap-to-click? I have a M1 MBA, and very frequently TTC doesn't register my first click. Normal clicks seem to work fine. Tried turning on and off. Anyone experiencing this?

forums.macrumors.com

 

[Atarikid]

I have the same issue. It is so extremely annoying that I am planning to go back to Big Sur.

There is an Apple bug tracker ticket for this but Apple does not seem to be able to reproduce the issue (at least the three Apple devs who responded to that ticket). Which is odd because it happens on my MBP 16 Intel and MBP M1
This is really cumbersome because if they say it is not reproducible, it will not get fixed any time soon. :-(


Quality control at Apple is letting us down last couple of years. :-/

 

[Lancer]

I'm having the same issue with my M1 iMac, sometimes I'll be using the track pad and it goes to the bottom left or it grabs a window and moves it. Also some times I have to re-click for it to work. Hope we get a point update to fix it. Also have an M1 MacBook Pro, don't use it as much so haven't see the same issues.

 

[Mario Jad]

Same thing happening here with my intel MBP 16". From the first day on Monterey, 1 out of 10 taps doesn't register so iv'e been using the "force click" more often than not. And sometimes the the cursor jump to the right where my wrist is resting, which never happened before. Wrist detection on Big Sur was never a problem for me.

 

[hooptyuber]

Same issue here.

 

[ChairSpud]

Yes have experienced it on both the M1 mini and air trackpads, kind of annoying too.

 

[mreg376]

Same here. 2017 27" iMac, with an older battery-operated Apple trackpad. VERY annoying. Interrupts the work flow. Why is Apple ignoring this?

 

[Johnny Anthony]

Same here Mac 2017 27"

 

[Spanther]

sometimes 2-finger swipe to navigate doesn't work in safari/brave for me.

 

[MadeiraG]

Same happens to me , bought a brand new 14"MBP (now have to press touchpad 2/3 times to get it to recognise. was going to return it but won't bother if it won't fix it. Running Monterey 12.1 beta
I can't recall it doing it on my previous mbp

 

[Squillace]

I've never thought of this as a "well spread" problem, but now I realize it is. Also experiencing the same problem with my M1 MacBook Pro.

 

[BaggieBoy]

Long thread here on the issue: https://forums.macrumors.com/thread...n-b9-and-10-and-now-monterey-release.2317279/

 

[l2uso]

It has to do with the force click functionality: if you configure "Click" in "Firm" level the "Tap to click" is more responsible. If you disable "Force Click" entirely, the "Tap to click" is fully responsible again.

I configured "Click" in light setting and the "Force Click" works almost like the "Tap to click" feature. Some times is a legit tap, sometimes is a click, but now I can avoid those "double clicks" because the tap thing was not working.

FYI "Click" setting is "Medium" by default and I was almost crazy with the double-tap-to-make-it-work behaviour too.

At least in my experience... I just read this somewhere else. Don't remember where. Maybe even in this forum. Sorry for not remember where.

 

[piotrsss]

If you disable "Force Click" entirely, the "Tap to click" is fully responsible again.

Not for me. ??‍♂️ I tried every combination of settings there.

 

[l2uso]

Not for me. ??‍♂️ I tried every combination of settings there.

Maybe a better/different hardware controller? Sorry to read that

My MacBook Air (with no force trackpad) works like a charm.

FYI: I can confirm that Monterey 12.1 beta 4 has not changed anything about this "bug" (?). Same exact behaviour so far.

 

[elvisimprsntr]

I had the same issue and can confirm it is fixed in the latest Monterey 12.1b4 release, at least on the '20 M1 MBP