Please perform the below mentioned steps to resolve the issue:
To Reset S Pen - Insert the S Pen into the slot. Then, open the S Pen remote setting screen and tap More → Reset S Pen.
For further assistance, register your concern in Samsung Members Application (Open Samsung Members Application > Get help > Send Feedback > Error report/Ask questions).
the S-pen in my laptop is the skinny toothpick kind of pen. no battery, no reset. it worked ok for a while but now it is completely useless. i tried everything - new tip, not inserted fully, etc. nothing works. I got this Notebook P90 to be able to use the pen on the screen for graphics. now it only serves half purpose. Samsung should come up with a solution and replace pens if that is what is required.
do not leave people frustrated and annoyed. you can do better than this Samsung.
So i have been having same issue with s pen on s7 tab. And did a lot of reading about it with people having very mixed success in resolving it.
One thing was clear, its the pressure sensor that is mucking up when the nib is inserted. It just recognizes that screen is being touched too early. And its really annoying. Without this pen function the tablet is just another trash gadget that i have no interest in, as my work involves a lot of marking up and writting on PDFs.
Anyway. I managed to overcome this issue for time being by the looks of it. Some people had luck by not pushing the nib all the way. But this is just a matter of time until it goes in far enough to start doing the same thing...
So, what i did is:
1. Remove the nib.
2. Get a sharp knife. Utility or precision knife works best.
3. Start cutting tiny fractions of the end of the nib stem that goes into pen and keep checking if the issue goes away, by reinserting and writing after cut.
By small fractions, i mean really small, because if you cut too much, nib will not go deep enough to contact sensor and be wasted, so you will need to start over on a new one.
This way you dont need to worry about pressing nib too far in to activate this annoying bug.
Try it and see if this solution is consistently working on more cases than just mine. Hope it does!
