[Q] Note 10.1 touchscreen bug or issue whatever it is ? help! - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl

Its been 2 weeks since i bought this tablet. I have a problem since then which is when i use touch screen, while scroolin up and down and stop without drawin my finger, page under my finger vibrates for a few pixels. For example while im using photoshop touch and crop someting to move with my fingers , that cropped piece starts to shake . Does this exist in all devices ? If its not im gonna take the device back to store . Is it a known problem that no one mentions about ? With pen everthing is cool but when I start using my fingers its shaky like 3 4 pixels.

http://forum.xda-developers.com/showthread.php?t=2619898
http://forum.xda-developers.com/showthread.php?t=2491690
http://forum.xda-developers.com/showthread.php?t=2646401
jep it's a very well known issue and pretty much everyone has it. People are pretty sure that it is a software bug that can be fixed in the next update though.
I'm going to wait until the next update hits and hope that it will be fixed, because otherwise the tablet is perfect. Otherwise I'll probably return it as well.

The capacitive touchscreen controller in these tablets attempts to provide touch coordinates that are as accurate as possible. when you place a finger on the screen, you arent touching a single point, but rather a number of points, for which the controller has to determine a center point. For capacitive screens, the calculation of this touch point can vary from one iteration of the calculation to the next as a result of subtle capacitance changes due to humidity, contact pressure, etc. if you load any of a number of test programs that output the touch coordinates, you'll see that they jump around by a few pixels.
What this means is that the driver for the touchscreen doesnt include enough deadband around the touchpoint to eliminate positional jitter. This can be corrected in the driver, but whether a software update will resolve it or not remains to be seen. If the jitter isn't acceptable, I would plan to return the tablet within your applicable return window, rather than count on a software update that may or may not address the problem. Samsung has been slow to respond to these kinds of issues, if they address them at all.
Sent from my SM-P600 using Tapatalk

dpersuhn said:
The capacitive touchscreen controller in these tablets attempts to provide touch coordinates that are as accurate as possible. when you place a finger on the screen, you arent touching a single point, but rather a number of points, for which the controller has to determine a center point. For capacitive screens, the calculation of this touch point can vary from one iteration of the calculation to the next as a result of subtle capacitance changes due to humidity, contact pressure, etc. if you load any of a number of test programs that output the touch coordinates, you'll see that they jump around by a few pixels.
What this means is that the driver for the touchscreen doesnt include enough deadband around the touchpoint to eliminate positional jitter. This can be corrected in the driver, but whether a software update will resolve it or not remains to be seen. If the jitter isn't acceptable, I would plan to return the tablet within your applicable return window, rather than count on a software update that may or may not address the problem. Samsung has been slow to respond to these kinds of issues, if they address them at all.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Very good point. The driver seems to try to be very accurate. One my older tablet (Acer A500) many times when using Chrome it would magnify the area where I touched as it couldn't really tell which link I had pressed. It seems with this tablet that almost never happens, almost as if the driver is trying to be as accurate as the pen. Sorry, my fingers are not that accurate! Maybe its a (incorrect) reaction to the high res of the tablet?
The driver should be averaging the touched area to get the touch point, but it should also give some kind of uncertainty so it doesn't seem unnaturally accurate (pixel width finger).
I should have tested this on the note 12 or the tab pro's at bestbuy last night...

dpersuhn said:
The capacitive touchscreen controller in these tablets attempts to provide touch coordinates that are as accurate as possible. when you place a finger on the screen, you arent touching a single point, but rather a number of points, for which the controller has to determine a center point. For capacitive screens, the calculation of this touch point can vary from one iteration of the calculation to the next as a result of subtle capacitance changes due to humidity, contact pressure, etc. if you load any of a number of test programs that output the touch coordinates, you'll see that they jump around by a few pixels.
What this means is that the driver for the touchscreen doesnt include enough deadband around the touchpoint to eliminate positional jitter. This can be corrected in the driver, but whether a software update will resolve it or not remains to be seen. If the jitter isn't acceptable, I would plan to return the tablet within your applicable return window, rather than count on a software update that may or may not address the problem. Samsung has been slow to respond to these kinds of issues, if they address them at all.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I agree. This is exactly how it looks like. I understand that the touchscreen needs to be as accurate as possible for the pen. But a simple solution or workaround would be to have a "pen mode" for when the pen is out and a finger mode while the pen is docked in the case.
I'm sure there will be a solution for this sooner or later, especially since samsung is releasing more and more devices with wacom digitizers and stylus. And it's more or an annoyance than a deal breaker for me. There aren't any situations where it keeps me from getting my work done or anything. It's just a little annoying sometimes.
And in my experience samsung is actually quite good with fixing things these days.

Thanks for replies! I guess its the driver too. Comparing with apple , yes they dont offer to much of feature but i guess they are best at what they offer and this is the only problem with samsung. Amazing features that we come across via samsung but no perfection.
Sent from my GT-I9500 using xda app-developers app

Related

Device Hack Possibilities: Transplant Focus into 7" screen chassis?

I was playing with my GF's Nook the other day and thinking about what a nice size it is for e-Reading. Now, I realize it has a higher screen resolution that WP7 doesn't support, so I wasn't thinking of going that far.
But I did get to thinking: is there a 7", 800x480 capacitive screen on the market that could be made to simply "plug in" via the same type of connector as the focus uses, and just work? In that case it wouldn't be *too* difficult to transplant the rest of the focus' guts into a bigger chassis (maybe adding a bigger battery since the extra space would be there anyway). Anybody thought about this or have some idea what one would look for?
Thanks!
So I'm guessing nobody has any idea or interest in exploring said idea?
The chances of that working are pretty darn slim. I'm not really into the hardwaret thingy, but I'm pretty sure you would need to know what interface to the display is used on both devices. They need to be the same, or you'll need to find a way to convert the signals, which means a lot of work and room for error I guess.
I would say it's possible, if you find a device with the right resolution and display interface/controller.
The display itself should work, since a display is just a display... It only receives data what to display. But dunno if the touchscreen would work out of the box, maybe different systems use different protocols in sending/receiving/processing data from the touch panel... But then again, I don't have my diploma yet
The displays must have the same controller. Or using the controller from the Focus - but don't forget, that it is AMOLED, so it might work totally different.
I don't think it is possible without too much effort. You should get some x86 tablet and run WP7 emulator on it . Or make an app for the W7 that looks like WP7.
Basically you would need to have two drivers, or make the other side compatible with existing drivers.
The screen and the touch panel.
I don't know what type of touch panel you have, but WP7 uses capacitive screens, this is a big requirement because you won't work around it easily.
The way the positioning data is transfered matters allot, because this can kill the accuracy at the least.
Next, the screen needs to know how to display the data received from your device, I assume the connector won't fit out of the box so thats the first challenge. Then you need to make sure it's receiving the correct data over the correct lines. It is not the same as plugging in a D-SUB/DVI cable.
So, if you have knowledge of some hardware modifications (electro) then you will stand a chance, otherwise you'll probably end up wasting two devices.
If you can spare both, I would say go for it. Otherwise I would think twice if I were you.
Yeah, I'm way too lazy (well, too busy with school) for all that . I was just randomly thinking about it the other day, how nice it'd be to have WP7 on a decent sized screen for an ereader, given that the Kindle app works great on the device. I guess I was hoping that there might exist, essentially, an "embiggened" version of the exact same screen, with the same connector, to simply be driven off the Focus' existing controller and hardware. Capacitive, obviously--WP7 on Resistive would lick all kinds of donkey balls, I'm sure.

[Q] Touch Sensitivity/Response Problems?

I bought my Nexus 7 2013 32gb model from Amazon and got delivered early before official local availability. I have noticed some touch problems in various apps (Pocket, Youtube, Chrome). I turned on developer settings and then turned on "show touches". When have problems it's like the touches are never registered. It's weird because its not consistent. I am considering sending it back for a replacement, but I have a friend who picked one up locally and has similar issues. I am wondering if this is a bug in 4.3 or something like that.
Any thoughts? Anyone else have this problem? RMA or keep it?
Flashing a different kernel could fix your problem as that is what bridges hardware and software.
Username invalid said:
Flashing a different kernel could fix your problem as that is what bridges hardware and software.
Click to expand...
Click to collapse
Looking to remain stock at the moment. I figure if its a kernel/software problem google will release a fix fairly soon. If it's a hardware problem unique to a small number of devices like mine then I would like to RMA it.
Liquidretro said:
Looking to remain stock at the moment. I figure if its a kernel/software problem google will release a fix fairly soon. If it's a hardware problem unique to a small number of devices like mine then I would like to RMA it.
Click to expand...
Click to collapse
Yesterday mine was fine and today when I was typing in landscape I was having the biggest problem getting the letter b to go through I actually would have to hold it for a brief second.... Then I restarted... And now bbbbbbbbbbbbbbbbbb.... Yup everyone goes through I have a feeling its a software bug but I'm staying unroofed till I know for sure ...
Sent 4rm my Nexus 7 2013... It feels and looks so sexy...
I'm having the same issues in chrome. I do tons of browsing and it seems about every 20 minutes I have to close out and restart the browser session. Anybody recommend another browser in the mean time?
zim2704 said:
I'm having the same issues in chrome. I do tons of browsing and it seems about every 20 minutes I have to close out and restart the browser session. Anybody recommend another browser in the mean time?
Click to expand...
Click to collapse
dolphin does the same sometimes. i like NEXT browser
the screen seems to be too insensitive imo.
i tried on my old nexus 7 and nexus 4 to keep swyping between "n" and "d" in the stock keyboard, they register all the gestures without dropping in between. However in the new nexus 7, it often drops my gesturing if i don't press on the screen hard enough.
Kind of makes me wonder if it's the calice I have on my thumb from using lighter too much
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
I've noticed touch issues on my otherwise flawless screen (no dust, dead pixels, or multitouch issues other than this specific scenario) due to what I assume are grounding issues. I did some testing:
If I lay the tab flat on a table, and touch it with 1 finger, touches are only registered maybe half the time.
If I touch it with 2 fingers, no issues at all.
If I'm holding the tablet in one hand and touching it with 1 finger, no issues.
If I merely touch the case (not even the screen) with one finger while the tablet is flat on a table, and touch the screen with 1 finger, no issues.
Anyone else notice this?
My keyboard inputs letters that I don't physically touch at times when I'm writing a sentence so there definitely appears to be an issue with some units at least. I've never had this same problem on any other touchscreen device.
SubMatrix said:
I've noticed touch issues on my otherwise flawless screen (no dust, dead pixels, or multitouch issues other than this specific scenario) due to what I assume are grounding issues. I did some testing:
If I lay the tab flat on a table, and touch it with 1 finger, touches are only registered maybe half the time.
If I touch it with 2 fingers, no issues at all.
If I'm holding the tablet in one hand and touching it with 1 finger, no issues.
If I merely touch the case (not even the screen) with one finger while the tablet is flat on a table, and touch the screen with 1 finger, no issues.
Anyone else notice this?
Click to expand...
Click to collapse
Yup, same exact situation here. I hope this is a software issue that can be fixed
Sent from my Nexus 4
Mine doesn't register touches sometimes... contemplating on exchanging.
Sent from my SPH-L720 using xda premium
dcaplinger76 said:
Mine doesn't register touches sometimes... contemplating on exchanging.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Exchanging mine tomorrow.
Kills me, I had a 16gb with no issues at all, then earlier this week, exchanged for a 32gb and this one has touch issues! I also noticed right away that this 32 was noticeably more laggy due to a few milliseconds delay when I tap in one of the "bad" areas, which tends to be the top half of my screen.

[Q] Dead spot on screen

Hello xda! , i have just bought i nexus 7 (2013) last wednesday and today i have noticed that there is a certain area of the screen where if i swipe my finger from another location it terminates the touch and starts another one, i enabled developer options and turned on the pointer location to see what was happening and it shows the line when im close to the "spot" but when i strike through it it starts another line after that "spot" but if i tap its okay i discovered this while playing draw something and when i go through that location it just start a new brush line or whatever and its a little annoying, the thing is that i bought it at RadioShack but didn't add the warranty but still have the 31 day warranty.
Hope you understand what im saying
1. Is this a reason to replace my tablet?
2. Will they replace it or what?
1. Yes
2. No reason why not, you're within a week.
(if you used a CC you've got even more leverage)
Now that you know what to look for you can test before you even leave with it. :thumbup:
Yeah I Think i'll keep it for a few days (15 or 20) if google launches a patch i'll keep it if not i'll try to replace if the same issue is present on the replacement i'll ask my money back
Sent from my Nexus 7
I don't think that a dead spot that's repeatable is software, but, what the heck. They're pushing out an update right now that's supposed to fix the touch issue, so you'll know soon enough...
Hello Guys, i just updated my tablet to JSS15Q and the multitouch issue has been corrected but my problem with the vertical dead spot i mentioned is still there today i'll back up everything that i can and tomorrow will take it to RadioShack for replacement. Thanks
Sent from my Nexus 7
danvee said:
I don't think that a dead spot that's repeatable is software, but, what the heck. They're pushing out an update right now that's supposed to fix the touch issue, so you'll know soon enough...
Click to expand...
Click to collapse
It usually isn't a true dead spot in the sense that there is no voltage drop or current going through that area. It is usually that for that area they need to use a different threshold to trigger detection. I saw in the firmware changes they can fine tune even edge responses, so I assume they can have some sort of matrix where the thresholds are specified for different parts of the screen. The problem might arise that if they make some area more sensitive, displays that are already more sensitive in that area might start having undesirable behavior.
I have seen areas where the screen won't register taps but will register swipes. I've also seen areas that won't register taps or swipes, but when you hold the unit it starts to register them, so clearly the wiring is there for the input to be registered, but the thresholds to determine noise vs input may need to be tuned.
It does seem there is a lot of variance on these touchscreens which appears to be making it hard for them to come up with one firmware that fixes everything.
They may need to add some user tunable functionality to account for the different variances.
Is that even possible?
Interesting, but it's not a constant in my case.
The upper ⅓ in portrait becomes decreasingly sensitive toward the top, but only periodically. Maybe 2-3X/day.
Can't reproduce it at will, or by introducing any series of events (at least consciously).
It just happens.....
The occasional freezing happens, maybe once/day, and again, not reproduce able at will.
One plus is that any spontaneous rebooting has been while it's 'sleeping', hasn't done it during use.

[Q] Touchscreen and sound problems.

Hello.
I'm using my nexus for a couple of months now (device is assembled in november 2013), and there are two issues that really bother.
First of all, response of touchscreen is not always correct: it sometimes misses some touches (press the letter on a keyboard, for example - and nothing happens until 3-4-5th touch) or handles single touch like multitouch (scrolling through the page in browser with one finger suddenly acts like two-finger gesture). It usually happens on the top half of the display and while tablet lies on flat surface, but not always: I have noticed same behavior in hands. There are no exact circumstances that show that bug always and for sure, but it appears once a day or two. Today, though, it didn't respond to touches at top half at all, and when I ran a multitouch test, I saw this: http://youtu.be/XwEDCwUZ8h8
The other thing is upper loudspeaker. While it is on, a weird high-frequency sound is present. I can not describe it exactly, but I have recorded an example: https://dl.dropboxusercontent.com/u/71375852/%D0%B7%D0%B2%D1%83%D0%BA1.mov In fact, it is louder: I can hear it from a distance of 10-15 centimetre, and it is even louder if device is charging. But verdict of service-centre said, that this is a software issue, manufacturer is awared and will fix in oncoming ROMs.
So the questions are:
1) How common are these problems? Are there any fixes yet? Are the any people who had a replacement or moneyback because of the issues?
2) Are there any official feedback from Asus or services that recognise these issues as hardware fault which requires a repair or replacement?
As I said, my service-centre did not confirmed the sound issue as hardware issue and they also did not notice the touchscreen bug. But the device still had a 20 days repair: the battery was replaced because of unstable work. According to our laws, I need 10 more days of repairs to get a replacement of the device or have the money back. But there should be exactly a repair of a fault which is covered by warranty: it won't work if after 10 days service will just return the device, saying it had worked properly. So any information about these issues would be really appreciated.
Thanks for any responce.

A70 Touchscreen sometimes misses quick touches

Hi All!
I just got a new a70 5 days ago, it's performing very well, but i did notice one thing. Sometimes my quick touches when i just very quickly and barely touch the screen, the touch is not registered. I activated the factory diagnostic mode (*#0*#) and tested and got some interesting results. If i touch the screen quickly enough, the touch is not registered at all, even though i apply a substantial force. I can do this like 3-4 times out of 10 if i really try. I also tried it on my galaxy S5, and although I could reproduce the same issue, it was much harder to get it to miss a touch than on my brand new a70. I did try it with and without a screen protector and it didn't make any difference. I'm actually surprised, I didn't think I can touch the screen too quickly so that the sensor (or software?) fails to register it. My question is: is this an expected behaviour, or something that should be looked into? It doesn't really affect everyday use, but ever since i discovered this I'm now always having this weir feeling anytime i'm about to touch the screen that "is this touch going to miss?". So my questions are the following:
1. Is this behaviour normal?
2. Why does my S5 seems to be more "reliable" and is harder to get to miss a touch.
3. Is there a 'minimum touch duration' for these capacitive screens?
4. Anybody else who has A70 experienced this, could try it out?
(it was not very easy to reproduce at first. i started noticing it when i wanted to open messenger chats, that some of my touches missed. for the issue to be easily reproduced one would have to try and tap as quickly as possible, so that your finger touches the screen for the shortest time possible)
crazylachesis said:
Hi All!
I just got a new a70 5 days ago, it's performing very well, but i did notice one thing. Sometimes my quick touches when i just very quickly and barely touch the screen, the touch is not registered. I activated the factory diagnostic mode (*#0*#) and tested and got some interesting results. If i touch the screen quickly enough, the touch is not registered at all, even though i apply a substantial force. I can do this like 3-4 times out of 10 if i really try. I also tried it on my galaxy S5, and although I could reproduce the same issue, it was much harder to get it to miss a touch than on my brand new a70. I did try it with and without a screen protector and it didn't make any difference. I'm actually surprised, I didn't think I can touch the screen too quickly so that the sensor (or software?) fails to register it. My question is: is this an expected behaviour, or something that should be looked into? It doesn't really affect everyday use, but ever since i discovered this I'm now always having this weir feeling anytime i'm about to touch the screen that "is this touch going to miss?". So my questions are the following:
1. Is this behaviour normal?
2. Why does my S5 seems to be more "reliable" and is harder to get to miss a touch.
3. Is there a 'minimum touch duration' for these capacitive screens?
4. Anybody else who has A70 experienced this, could try it out?
(it was not very easy to reproduce at first. i started noticing it when i wanted to open messenger chats, that some of my touches missed. for the issue to be easily reproduced one would have to try and tap as quickly as possible, so that your finger touches the screen for the shortest time possible)
Click to expand...
Click to collapse
Yeah the touch on this device is horrible. Don't listen to fanboys, this device has a couple of issues other than the touch screen having an awful response time.
Check:
+
The SD675 isn't well optimized for most games, so it lags in most of them, while on the A50's weaker processor, the Exynos 9610, games work just fine. Most of the time, they work better on the A50 than on the A70.
And there's another issue with dark colors being turned off instead of dimmed, because the screen doesn't know the difference between "dark" and "totally black". I'm gonna demonstrate this later by comparing the A70 and A50 side by side.
The A70 has a stronger CPU than the A50. The A50 has a stronger GPU than the A70. The A70 has better battery life.
That said, yeah touch problems. I notice it all the time when browsing. Trying to tap on small links are not registered most of the time. I have to zoom in.
I believe it to be a hardware issue that is not fixable in software.

Categories

Resources