1-4 of 4 Answers
Hello there Trackpad, thank you for finding the unobstructed time out of your bustling day to ask us your question about the Samsung Galaxy Book3 Pro 360. That's a good question. If you're worried about your touchpad possibly interfering with your writing/typing, I recommend locking the touchpad. You can do this by: > Pressing and holding the Fn key and pressing the F5 key to lock the touchpad. If you have any other questions for us, please feel free to contact Samsung Support. Thank you for being a steady Samsung customer. - Debra
Sorry, there was a problem. Please try again later.Most times the touchpad is sensitive to palm touch. Even adjusting the mousepad sensitivity it's still sensitive. I also adjusted the registry and it didn't make a difference.
Sorry, there was a problem. Please try again later.No. Absolutely not. It is both too sensitive and not sensitive enough at times. I have it on the highest sensitivity because it often doesn't register clicks even with me pushing the pad so it physically clicks. I was going to take it back before my return deadline but I didn't because in the store I didn't have a problem. However now that I'm back to work, on excel and using the browser I'm constantly clicking the pad without even touching the pad. It's just too big. Unless you hold your hands well above the pad while you type. But if you work on it for very long you inevitably rest your hands on it which is probably what causes it. I don't even have to touch the pad. It seems like the reason it doesn't register clicks is that it senses that you have 2 fingers on the pad, one apparently being either the palm or maybe clothing in proximity to it, plus the click finger. But I even try holding my hand straight up above it and stick one finger straight down and it still won't register a click. Extremely frustrating.
Sorry, there was a problem. Please try again later.Yes I found it to be! I have been typing a lot since I got it and its has not interfered at all, love that about it!
Sorry, there was a problem. Please try again later.