Related
Some weird S-pen behavior was brought up in this thread:
http://forum.xda-developers.com/showthread.php?t=1935657&page=3
At first I was not aware (like most of us?) that my pen too suffered from these flaws but I decided to try it and discovered that I too could indeed replicate the "errors" mentioned.
I think it is time we bring some light into this matter so here is how to test if your phones S-pen behaves erratically or not:
- Go to your dialpad
- Enter *#0*#
- Press 'Wacom Test'
- Draw long diagonal lines from upper left to lower right. Also try drawing in the lower right (and left) corners.
- Press and hold the pen-button while pressing and holding pen at screen to take a screen-shot.
- Result is stored in Storage/SDCard0/Pictures/ScreenShots/
My belief is that all phones share this "flaw" and that those saying they don't, simply haven't tested it properly. But this is just my guess and I may be wrong about this.
Anyway, please give it a try and report your results here.
Here is a link to an image showing the problem:
http://wfurl.com/67f4046
My test:
http://i9.photobucket.com/albums/a99/k0nane/SamsungGalaxyNote2/Screenshots_2012-10-20-14-19-32.png
I believe it is a matter of how fast you are doing it.
i believe my Note I abd this Note II both have this problem...we need to cobtact samsung for this
My note 10.1 with fast no problems but with slow out has some imperfections
Sent from my GT-N8000 using xda app-developers app
hoss_n2 said:
My note 10.1 with fast no problems but with slow out has some imperfections
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
Oh there is a whole bunch of waves on the right side of your screen-shot. They are very subtle, but they are there.
They will become more visible if you draw longer lines and at slightly more than 45 degree angle.
I went to a mall today and tried their Note II and just as I expected it had the very same "flaw" when I tested it.
So I believe the people claiming not to have this issue, are either not doing the testing the same way as described, or simply not noticing the flaws.
It is not a big deal for most users of course.
But for people doing a lot of drawing it can be quite bothersome, since these "flaws" will affect all kinds of drawing in a subtle way, not just when drawing diagonal lines.
white-k said:
Oh there is a whole bunch of waves on the right side of your screen-shot. They are very subtle, but they are there.
They will become more visible if you draw longer lines and at slightly more than 45 degree angle.
I went to a mall today and tried their Note II and just as I expected it had the very same "flaw" when I tested it.
So I believe the people claiming not to have this issue, are either not doing the testing the same way as described, or simply not noticing the flaws.
It is not a big deal for most users of course.
But for people doing a lot of drawing it can be quite bothersome, since these "flaws" will affect all kinds of drawing in a subtle way, not just when drawing diagonal lines.
Click to expand...
Click to collapse
I tried today 2 note II and another note 10.1 all have same issue, very strange
Sent from my GT-N8000 using xda app-developers app
It could just be that your hand is not drawing straight. Remember its plastic on glass, not much friction. Try doing this with a ruler and see if its any different.
I've informed Samsung about this, awaiting a reply. :fingers-crossed:
I don't experience this at all :-\
Sent from my GT-N7100 using xda app-developers app
sHaHiN786 said:
I've informed Samsung about this, awaiting a reply. :fingers-crossed:
Click to expand...
Click to collapse
Awesome! Please let us know if they reply. :good:
I think the problem lies in the wacom pen. I noticed a slight displacement of the tip in relation to the pen. The slower it gets the more dramatic the waves.
Sent from my GT-N7105 using xda premium
mix1987 said:
I think the problem lies in the wacom pen. I noticed a slight displacement of the tip in relation to the pen. The slower it gets the more dramatic the waves.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
The tip may seem a bit wonky, but I am now pretty sure the waves comes from some kind of (magnetic or otherwise?) "interference".
As I went to the mall to try out their S-pen, I noticed a HUGE wave-bulge in the middle of the screen! First I thought that some customers had just poked the screen a bit too hard, but then I flipped the device over and discovered an electronic(magnetic?) anti-theft-gadget attached to the exact opposite side of the device, where that big wave-bulge (looking like an onion) appeared when drawing.
I even took photo-proof of this. I'll try to upload them here if I can find the time.
Here are photos from the mall.
One photo shows interference in the shape of an onion.
The other photo shows the security-device on the back causing the bulgy waves.
Maybe this will help someone with more technical knowledge deduce what causes the "normal" smaller waves on all our phones?
Bulgy waves:
http://wfurl.com/e0a662e
Security-device:
http://wfurl.com/ac3d39e
Hmm, Wacom active digitizer pens are affected by magnets so it's not surprising that large bulge thing happened in the store.
Don't know if it's the same thing with the Note2 screens though. My Note1 has a similar issue in the very top left corner (you can't draw straight lines there).
Supposedly even metal parts near the screen can actually affect the writing ability of the Wacom digitizer but the driver is supposed to compensate for that. Perhaps the driver isn't calibrated as well as it should be.
white-k said:
Here are photos from the mall.
One photo shows interference in the shape of an onion.
The other photo shows the security-device on the back causing the bulgy waves.
Maybe this will help someone with more technical knowledge deduce what causes the "normal" smaller waves on all our phones?
Bulgy waves:
http://wfurl.com/e0a662e
Security-device:
http://wfurl.com/ac3d39e
Click to expand...
Click to collapse
Good find, Samsung have yet to reply to me, I've had problems with them in the past making false claims, so I'm giving them till tomorrow the latest, then I'll be contacting them directly, they have the worst customer service I have ever experienced.
sHaHiN786 said:
Good find, Samsung have yet to reply to me, I've had problems with them in the past making false claims, so I'm giving them till tomorrow the latest, then I'll be contacting them directly, they have the worst customer service I have ever experienced.
Click to expand...
Click to collapse
Cool. Someone needs to address this issue to them. You could even refer to this thread, to show them, if you want. Keep us updated buddy! :good:
white-k said:
Cool. Someone needs to address this issue to them. You could even refer to this thread, to show them, if you want. Keep us updated buddy! :good:
Click to expand...
Click to collapse
Due to religious events, I was busy, but I can confirm that the fault is with our S-Pen, I went to Phones4U and tested their device, and used their pen on my phone which did not produce the same lines as my pen does. I will upload photo's later. I will contact Samsung on Monday.
sHaHiN786 said:
Due to religious events, I was busy, but I can confirm that the fault is with our S-Pen, I went to Phones4U and tested their device, and used their pen on my phone which did not produce the same lines as my pen does. I will upload photo's later. I will contact Samsung on Monday.
Click to expand...
Click to collapse
Interesting. I was almost convinced that this was a problem on all Note II's.
Please do upload some photos. Will be interesting to see.
Where is your Galaxy Note 2 made from? Mine from Korea and no problem!
i don't see this problem on my note 2, maybe your hands are shaking?
Multitouch Visible Test
With that app, 1-finger touch is alright, no issues.2 Fingers seems alright too. Adding up to 4 fingers seems to be alright and moving them around the screen.
Sometimes with 5 fingers though, they'll all show on the program, and then immediately vanish. If I keep moving my fingers across the screen, they'll pop in and out, but won't actually stay on screen and follow. But this only happens sometimes. Other times, 5-finger input works fine.
My other camera is dead at the moment and I have to run and get batteries for it tomorrow, so I can't actually upload video of what I mean. I was hoping to get some input from other people about how their multi-touch seems to be with that app. Not entirely sure if this is just a rare defect, widespread, or working as intended maybe (not entirely sure if there's anything saying how much multi-touch this screen is; figured it was 10 though)
Some things to try:
- Use 1 finger, drag it all over the screen
- Keep adding fingers 1 by one after dragging them across the screen (add finger, drag it around, add next finger, etc.)
- Don't touch the screen for about 3 seconds, then just have all 5 fingers come in-contact with the screen, and keep them in one spot (on mine most of the time, the points appear then immediately vanish)
Could it just be the app your using?
Try using this one...
Check out "MultiTouch Tester"
https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
See if it does the same thing.
Sent from my SPH-L710 using xda app-developers app
jjdevega said:
Could it just be the app your using?
Try using this one...
Check out "MultiTouch Tester"
https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
See if it does the same thing.
Click to expand...
Click to collapse
Yea it still does the same thing :/ Here's a video:
It could be as simple as compatibility issues with the app...
Sent from my SPH-L710 using xda app-developers app
Called up Google and it doesn't seem to be widespread (or at least the person didn't say it was), and I could get a replacement under warranty. I don't have the funds to put on hold currently so it'll have to wait if I do decide to do it.
Although I wonder if I really should, I mean I highly doubt I'm going to do anything requiring more then 2 fingers on the screen at any point (nor can I really think of anything), and aside from multitouch, everything else seems great. No dead pixels, back doesn't flex, screen is alright quality-wise.
Would be nice if some other people can try out multitouch though just to see if it really might be widespread or not though. The thing is though, it works fine sometimes, and other times it doesn't. Perhaps software might fix it in time, but I don't know. I thought I heard of the Nexus 7 having a similar issue, but I can't recall...
jjdevega said:
It could be as simple as compatibility issues with the app...
Click to expand...
Click to collapse
It seems to do the same even with the "Show touches" option enabled in Developer options (tried it on an empty homescreen).
Bump
Anyone? It only takes a minute or two at the most to test this... and the apps available to do so are free and light.
Doing the tests you described never caused anything on my tablet. But if I put my hand down on the tablet flat then put my five fingers on I get your issue. Then wait three seconds and try again and everything is fine till I put my palm back on.
Might be a badly configured palm detection algorithme? Op, do you have fat fingers? Sorry if that sounds rude
Chluz said:
Might be a badly configured palm detection algorithme? Op, do you have fat fingers? Sorry if that sounds rude
Click to expand...
Click to collapse
Lol, hmm, na I don't think I have fat fingers
How about fruit ninja, does that work properly? It's true that if show touches doesn't work, it's not a good sign. Unless it's a system firmware bug
1 and 2 fingers seems to work great in Fruit Ninja; 3+ randomly works or doesn't work, and when it does work it seems to cut-out at some point and then just show slashes delayed from where my finger is currently
Any idea if its hardware or software related? I have the same issue with my N10 and don't know if I should get a replacement or not.
Got mine today, same issue. Actually, that too bad since everything works fine, and i only got a minimal light bleed. I hope my replacement won't be worst regarding light bleed :/
Same issue on mine. Considering a replacement now with this and wakeup lag + battery issue (indicator not updating % at all!?)
Don't know if I wasn't lucky or just poor QA.
I'm pretty sure it is a software thing because when the problem occurs and I tab on the multitasking button twice (so it shows the multitasking menu and switches back to the app) the touchscreen acts normal again until I put more than three fingers on screen.
But if its a software problem, shouldn't it happen to on every N10 running the same Android version?
I have the same issue. If I slowly add one touch at a time, it usually works. But if I touch down 3+ fingers at once it gets very confused and bounces between zero and N touches. I have a Galaxy Tab 10.1 (first generation) and multitouch seems to work much better on it than the Nexus10. However, I did notice that the Nexus10 is better at distinguishing 2 very close touches than the GTab. On the Nexus10 I can have my fingers as close as 1/2 inch or so before the touches merge. On the GTab it is more like 3/4".
Hmm, kind of interesting to see that others are also having a similar issue.
I noticed that when I tried a custom ROM (latest Kernel sources + 4.2.1), the multitouch seemed to work, slightly better (the issue still occurs, just maybe not as much). Not too sure if it was placebo or what though.
I called the support and will replace mine with a new one. It might be just a software issue thats solved with an update but I don't want to risk it.
just got my replacement today, same issue (and also worst light bleed ). Third replacement on this way...
Initial releases almost ALWAYS flesh out some build issues that quickly get fixed (even Apples, but not so often), so hopefully the title says it all. Since we already have seen a few issues with the initial builds, such as camera sensor quality, case gaps, dead pixels, etc., maybe this thread will be a good place to keep watch on the progress of the HTC One issues being remedied, as many of us wait for HTC to perfect the One before we make our order. We don't want to get stuck with hardware issues that may be quickly remedied after initial release.
So you early adopters can help the lurking masses who are anxiously waiting for the right time to buy. Once we have a lot of people reporting what is or isn't good, we can then get an idea of when issues are not really issues anymore.
Please list any hardware issues you have noticed (software too, but no so important since software can be fixed after purchase), and/or list any fixes to these issues or opinions on whether these have become non-issues, so that many of us who are waiting can check the problems off our lists. If there are ways of identifying which hardware versions have the problems vs. which ones do not, that would be great info for this thread as well so that we can check a device in the store or quickly return a device before committing to a purchase.
Hardware issues:
-- Camera sensor yielding image issues such as mis-focus and/or color banding in a small percentage of units, partly due to a HUGE number of image sensor being rejected and causing initial release delays.
-- Gaps is the seams of the case materials such that the unibody design doesn't seem so smooth and seamless.
-- Stuck display pixels or observable differences in displays on a small percentage of sold units, possibly due to HTC using more than a single screen manufacturer.
-- Is black anodize hard enough that resistance to scratching and chipping is on par with other brands out there?
-- Signal reception issues
Software/driver issues:
-- GPU tests not scoring as expected, in comparison to similar phones currently coming out.
-- Volume level adjustability more granular in the low volume end.
-- Capacitive buttons not responding when they should.
-- Battery Drain issues
-- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
gruuvin said:
Initial releases almost ALWAYS flesh out some build issues that quickly get fixed (even Apples, but not so often), so hopefully the title says it all. Since we already have seen a few issues with the initial builds, such as camera sensor quality, case gaps, dead pixels, etc., maybe this thread will be a good place to keep watch on the progress of the HTC One issues being remedied, as many of us wait for HTC to perfect the One before we make our order. We don't want to get stuck with hardware issues that may be quickly remedied after initial release.
So you early adopters can help the lurking masses who are anxiously waiting for the right time to buy. Once we have a lot of people reporting what is or isn't good, we can then get an idea of when issues are not really issues anymore.
Please list any hardware issues you have noticed (software too, but no so important since software can be fixed after purchase), and/or list any fixes to these issues or opinions on whether these have become non-issues, so that many of us who are waiting can check the problems off our lists. If there are ways of identifying which hardware versions have the problems vs. which ones do not, that would be great info for this thread as well so that we can check a device in the store or quickly return a device before committing to a purchase.
I'll start it off. So far hardware issues to look out for:
- Camera sensor yielding image issues such as mis-focus and/or color banding in a small percentage of units, partly due to a HUGE number of image sensor being rejected and causing initial release delays.
- Gaps is the seams of the case materials such that the unibody design doesn't seem so smooth and seamless.
- Stuck display pixels or observable differences in displays on a small percentage of sold units, possibly due to HTC using more than a single screen manufacturer.
- Is black anodize hard enough that resistance to scratching and chipping is on par with other brands out there?
And possible software/driver issues with:
- GPU not testing where expected, in comparison to similar phones currently coming out.
- Volume level adjustability more granular in the low volume end.
- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
The sometimes-not responding capacitive buttons which are most likely a software issue.
Also:
-Fix the color temperature of the screen, it's too much on the cooler side
-Fix the audio hissing in some 1080p videos made in a quiet environment
-Sense drains too much battery in stand-by
-Improve 4G/LTE signal reception
-'msm_hsic_host' wake lock keeps the phone awake on stand-by and drains battery
darkgoon3r96 said:
The sometimes-not responding capacitive buttons which are most likely a software issue.
Click to expand...
Click to collapse
I get this aswell...
Also, whether its me or not but sometimes im on the phone and it randomly turns on speaker phone.... Going to wait n see how this one pans out tbh. It might be me touching it with my ear.
Xperia23 said:
I get this aswell...
Also, whether its me or not but sometimes im on the phone and it randomly turns on speaker phone.... Going to wait n see how this one pans out tbh. It might be me touching it with my ear.
Click to expand...
Click to collapse
If it is you touching it with your ear, then that is still a problem, as the proximity sensor should sense that the phone is close to your head and then shutdown the screen and touch sensor input so that touching the screen does nothing.
Maybe u could add links for each of the problems to related threads so users can get more info?
Sent from my Desire HD using xda premium
I just checked out the one at a nearby at&t store. I had such a hard time with the capacitve buttons that I am reconsidering the phone. Not once did I get them to work on my first touch. Extremely disappointed. Hoping it was that one model in that store. Will check out another store. Also looking at xperia zl as an alternative now. So disappointed though as it was pretty awesome looking and extremely light.
Sent from my SPH-L710 using xda app-developers app
gruuvin said:
- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
My biggest issue with the lack of menu button is that I've always used it to quickly pull up the address bar on my browser. If you gently scroll up or down on the browser it will pull it up, but it doesn't always work very well. That is what I would like to see a solution to, first and foremost.
The home and back buttons are not very sensitive and don't always react on my first attempt. Also the battery is draining extremely quick. I'm losing 12% per hour.
Sent from my HTCONE using xda app-developers app
There's a fix for the capacitive buttons. Someone found a sensitivity setting.
Sent from my Nexus 7 using xda app-developers app
Element515 said:
There's a fix for the capacitive buttons. Someone found a sensitivity setting.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Care to share the light on this? A link or instructions?
I don't quite remember where I read it... I've been stalking these forums for a while because I really want the phone... If you play around in your settings, somewhere there's an option to adjust/calibrate the sensitivity. Then, if you just very lightly touch the buttons, it will calibrate to that sensitivity and then fixed!
gruuvin said:
-- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
Does the hardware support this? As there might not be touch sensor on the logo... :/
Pr20 said:
I just checked out the one at a nearby at&t store. I had such a hard time with the capacitve buttons that I am reconsidering the phone. Not once did I get them to work on my first touch. Extremely disappointed. Hoping it was that one model in that store. Will check out another store. Also looking at xperia zl as an alternative now. So disappointed though as it was pretty awesome looking and extremely light.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
So I went and checked it out at another store and there was no problem with sensitivity. It had a weird problem where home would just bring up whatever screen you are on. Must be particular to that phone. Either way the sensitivity of the buttons was totally fine which was the main issue.
Also liked at xperia zl which is a fine phone in its own right but it just does not compare to the one. Although it does have one advantage which is that it is much easier to hack and get aosp and also get klp when it comes out.
Sent from my SPH-L710 using xda app-developers app
Element515 said:
I don't quite remember where I read it... I've been stalking these forums for a while because I really want the phone... If you play around in your settings, somewhere there's an option to adjust/calibrate the sensitivity. Then, if you just very lightly touch the buttons, it will calibrate to that sensitivity and then fixed!
Click to expand...
Click to collapse
I think this is the thread.
Solution to irresponsive back/home key
Case pitted
Got my 64bg on the 19th via mail direct order ATT. Top of aluminum case near power button front side chamfered edge had 2 pitted dents. Put back in box and immediately went to ATT store to return for new order replacement. I also noticed some rough finish in edges of aluminum casing where it meets plastic fill. Not at the level of my Iphone 5 fit and finish. Will see what replacement looks like in the next few days once received.
I'm glad I'm not the only one who feels the need to stab the hell out of the capacitive buttons when it comes time to go "home" or "back."
One of the few things that has agitated me about this phone is the effort required to press the back and home buttons. I actually began wondering if they were pressure-sensitive or something. After all, my Note 2 would often register inadvertent presses of the back and menu capacitive buttons because they were so sensitive. With the Nexus 4, the buttons are responsive, if not hypersensitive.
I have just set my calibration and the home /back buttons are immediately more sensitive.
omar302 said:
I think this is the thread.
Solution to irresponsive back/home key
Click to expand...
Click to collapse
Worked for me, thanks
Sent from my HTCONE using Tapatalk 2
g2525 said:
Does the hardware support this? As there might not be touch sensor on the logo... :/
Click to expand...
Click to collapse
Consensus is: yes, the hardware might support it, while software currently does not.
The sensor array likely completely covers a rectangular area but the coded area does not include the logo area. This might be hackable at the kernel layer.
Hi all, I want to check something with you.
On my N3 the S-pen as well as the little blue circle do not appear in the lower right corner. Its a very small area but nevertheless it does not register.
Note 2 users have had the same issue, see THIS thread.
Can you check on yours so that I can rule out a faulty N3?
Thanks!
Same thing here. Though I can still scribble in that area in sketch pro.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Same thing here... :/
Sent from my SM-N9005 using xda app-developers app
That's a shame really. Doesn't affect it really but it would be nice if there was an option to calibrate the pen.
Sent from my SM-N9005 using Tapatalk
Nikolatravic said:
Same thing here... :/
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Even the *#0 menu, the spen test ignores that area, the same with the note 2.
I guess it's to avoid interference (if you noticed, it's the same corner where the spen slot is.)
Hello !
I got the same issue (if it's one...).
Envoyé depuis mon Snanfoïde n7000
Same here but i dont think this is hardware issue.to double check go to dial and type *#0*# then go to Spen hover.
Hi everyone,
I am having the same issue. I noticed it today when I played a bit with the Microsoft Remote Desktop in the landscape mode. The X button to close a window is at the exact spot. I was I bit annoyed that I couldn't close a window with the s-pen, but I could with a finger. So I checked in the test menu and I saw the problem there.
I was thinking of returning the phone as I also have the multi-touch problems experienced by multiple users of this forum. I will probably contact the Samsung support to check what they have to say about those issues. I really like the phone and those might be minor issues, but they can be quite annoying if you have an expensive phone like Note 3. I will check in the local shops if the phones there also have the issues.
EDIT: I have attached an image of the s-pen test menu. Don't mind the pink tint, as I used a crappy phone camera. You can see that the s-pen isn't detected in the lower right area. In my case, there here is also a small area in the lower left corner.
EDIT 2: I have spoken with Samsung support. They have told me that the inability to use this area with the s-pen is due to a design constraint. I have also asked about the multi-touch problems and they have told me that it is not intended to use more than two fingers.
Greetings and have a nice day.
I'm going to unbury this thread as I've noticed that my Note 3 (bought at 10 March 2014, so probably a recent built) takes considerably more pressure to activate the digitizer on the bottom right, pretty much above the speaker.
This is noticeable for instance on the . key on the Samsung keyboard. Apply the same light pressure as on other keys and nothing happens. Push it harder and it triggers. This becomes quite annoying while typing with the pen, especially for people coming from the N2.
If you like to use your fingers you'll be OK. No difference at all.
A picture is worth a thousands words
I have circled in green the correct lines, in red the stray ones.
Why does it behave this way? It is no even co sistent, that is it does not happen always on the same spot
I get that too, don't know why.
Me too
Verstuurd vanaf mijn GT-I9300 met Tapatalk
I think it is happening because the pen is not communicating with the screen properly. Meaning that when you lift the pin up instead of pulling it straight up you're pulling it slightly at an angle and the pen is still close enough to communicate with the screen.
Sent from my GT-N8013 using XDA Premium HD app
Temetka said:
I think it is happening because the pen is not communicating with the screen properly. Meaning that when you lift the pin up instead of pulling it straight up you're pulling it slightly at an angle and the pen is still close enough to communicate with the screen.
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Exactly, im thinking that too. Or atleast it looks like that when writing. It's annoying but you can live with it - i dont care show much about it when writing, but when drawing it is awful.
enigma_x said:
Exactly, im thinking that too. Or atleast it looks like that when writing. It's annoying but you can live with it - i dont care show much about it when writing, but when drawing it is awful.
Click to expand...
Click to collapse
Might be the damaged SPen nib.My one was kinda wearing out so it justs does crazy stuff.Try replacing it to see if it works
Its not damaged, don't waste your money on a new one. It's Samsung's fault as they didn't fixed all the bugs in the firmware when they developed the product. I have lots of friends that use Note in school and everyone has this problem. That includes n8010 n8000 n8013.. The solution is either try using LectureNotes and apply some of the built in filters or try to teach yourself how to write in a way that there are no nibs. Also, be aware that some parts of the screen are more affected than other parts.
I think i might have insight here..
I recently looked into dev settings on my nexus 4 and set 'show pointer" out of curiosity. It is very interesting how the systems tells you not only the coordinates of the pointer, but the change in x- and y-coordinates, aka the speed of your finger as you glide. It also extrapolates where your finger would end up based on that speed, much like a momentum simulation.
I think whats happening here is that as you lift, you might flick the tip just a millimeter or so but at a high speed and the system extrapolates the line quite unnaturally. I might be wrong here tho, its just a theory.
Edit: looking back at the photo, notice that the lines happen as you lift the pen and not as you set it down..
Sent from my Nexus 4 using xda app-developers app
Happens to me too. I don't think that everyone here doesn't know how to lift a pen when they stop writing.
That doesn't make sense. It's a Samsung issue that I hope they fix in the next update.
thegios said:
A picture is worth a thousands words
I have circled in green the correct lines, in red the stray ones.
Why does it behave this way? It is no even co sistent, that is it does not happen always on the same spot
Click to expand...
Click to collapse
Does your case have a magnet on it? Sometimes magnets mess with Note 10.1 S-Pen.
Hahahalalala said:
Does your case have a magnet on it? Sometimes magnets mess with Note 10.1 S-Pen.
Click to expand...
Click to collapse
I have the original samsung case that yes, have small magnets on the edge and in the middle
thegios said:
I have the original samsung case that yes, have small magnets on the edge and in the middle
Click to expand...
Click to collapse
The original samsung case shouldn't give any problems,. but try taking it out for a while and see how that goes.
If not, call Samsung Support.
So far, I'm not able to replicate the stray line issues here, but my case (some generic flip cover with an elastic band to hold it shut) does not have magnets because I was concerned about the effect on the s-pen behavior so it could be that.
However, in terms of a fix you could try adjusting the sensitivity of your s-pen itself.
CAUTION!! you may damage it by doing so, I'm not responsible etc etc, do at your own risk !! ---
The click button along the side of the s-pen (with the ridges in it) is remove-able and underneath it is a screw you can adjust (in very small increments please) to adjust the sensitivity of the pen. The screw NEAREST the pen tip (there are two screws next to each other) is what you would adjust --- going CLOCKWISE to DECREASE sensitivity, and COUNTER-CLOCKWISE to INCREASE sensitivity.
I adjusted it to be slightly less sensitive as my pen was registering on the screen sometimes without touching it --- it appears that the tail-ended portions of your E's may also be a result of over-sensitivity.
YMMV of course