I've been experiencing a strange phenomenon in relation to the touchscreen on my new Nexus 7. It is essentially impossible to capture in video and difficult to accurately describe, so I apologize for any frustration in comprehending my description.
If I open the Play Store (for example) and gently flick to produce a slow automated scroll, the store page will scroll completely smoothly (aside from the usual few dropped frames as images load). However, if I place my finger on the screen and manually scroll through the page by the same amount at the same speed, it visibly stutters. The stutter produced is not absolutely horrible and some people may not even directly notice it, but it is just enough to make manual input feel sticky. On webpages filled with text where stutter will exacerbate even minor ghosting, it is particularly annoying.
The issue is present globally within the OS, although there are certain games which implement further input smoothing and seem to get rid of it. I was somewhat apprehensive about posting this thread, as it an issue which may be too subtle for many people to directly replicate (assuming I do not simply have a defective device, that is) without an exact understanding of what they are looking for and some may think I'm being "too picky".
To further clarify, I am aware that many people have had multi-touch and phantom input issues on this device, but those are not what I am referring to. I have experienced no multi-touch nor phantom input issues whatsoever.
Has anybody else encountered this issue or should I simply organize a replacement? If it is a software issue, I am perfectly willing to wait for Google to rectify it in a future update.
troy2062 said:
I've been experiencing a strange phenomenon in relation to the touchscreen on my new Nexus 7. It is essentially impossible to capture in video and difficult to accurately describe, so I apologize for any frustration in comprehending my description.
If I open the Play Store (for example) and gently flick to produce a slow automated scroll, the store page will scroll completely smoothly (aside from the usual few dropped frames as images load). However, if I place my finger on the screen and manually scroll through the page by the same amount at the same speed, it visibly stutters. The stutter produced is not absolutely horrible and some people may not even directly notice it, but it is just enough to make manual input feel sticky. On webpages filled with text where stutter will exacerbate even minor ghosting, it is particularly annoying.
The issue is present globally within the OS, although there are certain games which implement further input smoothing and seem to get rid of it. I was somewhat apprehensive about posting this thread, as it an issue which may be too subtle for many people to directly replicate (assuming I do not simply have a defective device, that is) without an exact understanding of what they are looking for and some may think I'm being "too picky".
To further clarify, I am aware that many people have had multi-touch and phantom input issues on this device, but those are not what I am referring to. I have experienced no multi-touch nor phantom input issues whatsoever.
Has anybody else encountered this issue or should I simply organize a replacement? If it is a software issue, I am perfectly willing to wait for Google to rectify it in a future update.
Click to expand...
Click to collapse
got the exact same issue with the two i ordered. Sometimes unlicking is a pain or drag and drop an icon to a screen. I"m waiting to get an update. If the next one is the same. i send them back
I thought this was solved in the last update.
Sent from my Nexus 7 using Tapatalk 4
Yup, This is the exact issue I am so frustrated with. I am really hoping this is a fixable issue..
It's a known issue.
I had the same, and fixed by applying this :
http://forum.xda-developers.com/showthread.php?t=2428133
Hopefully it will be fixed in the next release.
But until then, you can use the above solution.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I had this same issue on two nexus 7 devices (one purchased, the other a replacement unit) but eventually returned both over single touch issues. The stutter was apparent especially in chrome when you pinch to zoom. Feedly was another app that would stutter as you scroll down an article. I assumed this was more of an app specific issue but I guess it may be just another touch related issue with the device.
Sent from my BN NookHD+ using Tapatalk 4
AFAIK, this issue is due to the capacitive touch screen not having a very fine resolution input. It is especially noticeable on cheap tablets. The touch screen has input lines running say on a 1x1cm grid. As you draw your finger across, the line whichever is closest to your finger will register. So it will jump from one line sensing the finger to the next one, and this is then input to the software scrolling and produces a stuttering in the scrolling. You can easily try is by slowly drawing the finger up and down and watching the reaction of the page that is scrolling underneath.
To alleviate this, the screen driver can hand over from one line to the next in a smooth gradual manner but of course there will always be a scrolling rate where the effect is worse. The slower you scroll the clearer you can see it.
If lines are close to each other or you have fat fingers, this effect becomes less noticeable.
[edit] having said that, there are always apps which scroll poorly regardless of the quality of the screen.
^I thought that was the issue at first, but now im thinking its a software issue. The slower I move my finger, the less stuttery the animation. It is only when i move my finger at a medium or fast speed that it begins to stutter like this.
juried said:
AFAIK, this issue is due to the capacitive touch screen not having a very fine resolution input. It is especially noticeable on cheap tablets. The touch screen has input lines running say on a 1x1cm grid. As you draw your finger across, the line whichever is closest to your finger will register. So it will jump from one line sensing the finger to the next one, and this is then input to the software scrolling and produces a stuttering in the scrolling. You can easily try is by slowly drawing the finger up and down and watching the reaction of the page that is scrolling underneath.
To alleviate this, the screen driver can hand over from one line to the next in a smooth gradual manner but of course there will always be a scrolling rate where the effect is worse. The slower you scroll the clearer you can see it.
If lines are close to each other or you have fat fingers, this effect becomes less noticeable.
[edit] having said that, there are always apps which scroll poorly regardless of the quality of the screen.
Click to expand...
Click to collapse
This would be a perfectly plausible explanation, however the amount of stutter doesn't really seem to vary at all, regardless of the speed at which I drag.
juried said:
AFAIK, this issue is due to the capacitive touch screen not having a very fine resolution input. It is especially noticeable on cheap tablets. The touch screen has input lines running say on a 1x1cm grid. As you draw your finger across, the line whichever is closest to your finger will register. So it will jump from one line sensing the finger to the next one, and this is then input to the software scrolling and produces a stuttering in the scrolling.
Click to expand...
Click to collapse
Huh? Try an app like 'Yet Another MultiTouch Test' that displays touch coordinates. The touchscreen certainly has single-pixel accuracy/resolution (a pixel is 0.08mm wide).
tni.andro said:
Huh? Try an app like 'Yet Another MultiTouch Test' that displays touch coordinates. The touchscreen certainly has single-pixel accuracy/resolution (a pixel is 0.08mm wide).
Click to expand...
Click to collapse
It has high resolution (different to accuracy btw) due to the driver software working out where the touch is by using all the pick-up dots that show a capacitive response. But in the Nexus you can actually see the capacitive pick-up dots if you hold it in the sun and get the reflection just right, and they are 5mm apart.
Sent from my Nexus 7 using xda app-developers app
I also have the same stuttering issue, mostly in Chrome browser, when scrolling through some websites. Sometimes the tablet will respond to a scrolling glide but sometimes it will not, this is very annoying, another issue that I have is the random "touch - stuck" problem, where a single touch will register at one spot for 1-2 seconds, and you have to touch that spot again in order to un-stuck it, my Nexus 7 FHD has no problem at all when doing the YAMMT app test, there seems to be a lot of bugs in this tablet, I think Asus just sucks in general, my Samsung Nexus 10 has no problem whatsoever...
Sent from my Nexus 7 using Tapatalk 4
juried said:
It has high resolution (different to accuracy btw)
Click to expand...
Click to collapse
What point are you trying to make? The resolution is slightly higher than the display resolution and whatever internal accuracy the touch screen controller has, it is sufficient for that.
due to the driver software working out where the touch is by using all the pick-up dots that show a capacitive response.
Click to expand...
Click to collapse
The Elan touch screen controller has it's own microcontroller that is running some proprietary firmware blob that does all the magic. That firmware reports the position. The OS driver is very dumb and just passes that on.
juried said:
The touch screen has input lines running say on a 1x1cm grid. As you draw your finger across, the line whichever is closest to your finger will register. So it will jump from one line sensing the finger to the next one, and this is then input to the software scrolling and produces a stuttering in the scrolling.
Click to expand...
Click to collapse
But in the Nexus you can actually see the capacitive pick-up dots if you hold it in the sun and get the reflection just right, and they are 5mm apart.
Click to expand...
Click to collapse
That's simply not how things work. The controller measures capacitance at adjacent grid points and determines an interpolated position based on the capacitance measurements. There is no jumping from line to line, the position is smoothly determined using the interpolation.
There are touch screens that only have 2 pairs of grid lines (one pair for X coordinates, one pair for Y coordinates) and rely exclusively on interpolation to determine the position (but they can't support multi-touch).
Related
Hi
Anyone else having problems with the touchscreen taking maybe 5 presses for you to be able to select for example a menu option? This is really starting to bug me now. So much so I'm thinking of sending it back to t-mobile and cancelling the contract.
Any help/suggestions would be appreciated.
Cheers
Andy
Try an Calibration in the settings menu.
There isn't a screen calibration setting on this handset. I wasn't aware we had to do this on these capacitive screens.
My X10 doesn't work like that at all. How hard do you press? Does it work in one press if you press harder?
Press harder on as capacitive display?
You'll have to place your second hand on the metal frame and it'll work perfect.
Dry hands are also not good.
boo6 said:
Press harder on as capacitive display?
You'll have to place your second hand on the metal frame and it'll work perfect.
Dry hands are also not good.
Click to expand...
Click to collapse
Yeah. If you press harder a larger area of your finger touches the display. I.E. more for the digitizer to sense.
boo6 said:
Dry hands are also not good.
Click to expand...
Click to collapse
I'm definitely noticing this. I'm not exactly the type of guy to regularly moisturize my hands. I work in construction, and this capacitive screen absolutely sucks for me. I've been using resistive screens beautifully up to this point. I find I often have to lick my thumb regularly to get the screen to work properly. I have a ton of trouble unlocking the phone, since the screen thinks I've lifted my thumb halfway through the pattern. Using swype is a nightmare for this reason as well.
There are resistive multitouch screens on laptops and desktops now. I hope we see a swing back to resistive screens on smartphones.
I'm experiencing this problem aswell an i'm pretty much sure this is all software related, you can actually see the interface reacting to the press but it seems like the device never executes the action forcing you to press multiple times, annoying as hell yes! I sincerely hope SE fixes this in the next update.
Has anyone had any problems with accuracy? In some apps the touch registers like 5mm below where I actually touch.
I think the stock screen protector hinders the touch sensitivity quite a bit. Try getting a thinner screen protector. There is a thread talking about how sensitivity and accuracy improved when they took theirs off.
needmoregigs said:
I think the stock screen protector hinders the touch sensitivity quite a bit. Try getting a thinner screen protector. There is a thread talking about how sensitivity and accuracy improved when they took theirs off.
Click to expand...
Click to collapse
Thanks for the tip but I already have an uberthin protector. That brand has worked very well on all other capacitive displays I've had. I'm suspecting a software bug rather than a hardware issue.
needmoregigs said:
I think the stock screen protector hinders the touch sensitivity quite a bit. Try getting a thinner screen protector. There is a thread talking about how sensitivity and accuracy improved when they took theirs off.
Click to expand...
Click to collapse
I jammed my X10 in a sports armband for Ipod touch, it has a very thick plastic window and it did not affect the sensetivity a bit so i dont think the thin stock protector will do any difference. Just my opinion
ddewbofh said:
Has anyone had any problems with accuracy? In some apps the touch registers like 5mm below where I actually touch.
Click to expand...
Click to collapse
I've noticed that on the dialer application.
Sometimes, while I am on Recent Calls section, I press the green telephone next to a contact and it calls the one right below it!
Haven't ever noticed any sort of oddness like that... and I have a thick screen protector on top of the stock one.
Occasionally I'll type a letter wrong, but that seems to have improved with the update from two weeks ago.
Hey guys, so I tested the evo 4g, which is supposed to have the same Atmel maxtouch multitouch sensor and find that it has significant input lag (tested with multitouch visualizer) basically the dot which signifies where the input coordinates are lags about 1/2 second to 1 second behind the movements of my fingers, I was wondering if anyone with an incredible could test it on theirs and so maybe shed some light onto whether it was a software issue or a hardware issue with the maxtouch. thanks!
Dorick said:
Hey guys, so I tested the evo 4g, which is supposed to have the same Atmel maxtouch multitouch sensor and find that it has significant input lag (tested with multitouch visualizer) basically the dot which signifies where the input coordinates are lags about 1/2 second to 1 second behind the movements of my fingers, I was wondering if anyone with an incredible could test it on theirs and so maybe shed some light onto whether it was a software issue or a hardware issue with the maxtouch. thanks!
Click to expand...
Click to collapse
Individual Touch, Single Finger: Very responsive. No lag (estimate <20ms). Can successfully tap many times/second with no drop-outs.
Individual Touch, Alternating Fingers: Comfortably responsive. No lag as long as presses are distinct, as if with a single finger. If there is a slight overlap in the alternating touches, often only one point will be detected. You can see this by rapidly tapping back and forth between two fingers on the screen -- an occasional touch is missed (you have to be very fast) -- likely because the duration of the overlap does not seem long enough for a multi-touch detection (see below).
Multiple Touch: If fingers are in motion (swiping, pinching, etc.) when contact is made with the screen, then both points will be detected very quickly (estimate <150ms) and subsequently tracked very well as they continue to move. There is, for the most part, no detectable lag for me in tracking the locations of two fingers moving about. If you really go nuts moving them about the screen, then the multi-touch detection will occasionally 'stutter' for a split-second here and there, but nothing like the 1/2s to 1s you describe. If fingers are stationary when the screen is touched, not in motion, then it seems to take much longer for the multi-touch to be detected (estimate >500ms), and even then perhaps it is detecting a slight movement in one of the points. Is a tiny bit of motion perhaps required for the multi-touch detection to even work? I don't know enough about the technology to answer that one.
Overall: Excellent real-world responsiveness (apart from a separate, and conditional, grounding issue some of us have experienced). The only situation I could see someone having trouble with is if they are a lighting fast typist with the on-screen keyboard. If you type fast enough to overlap some of your key presses, than you will probably notice some missed letters here and there, and a few scattered reports seem to bear this out. I am not that fast, and I find the sensor on the Incredible to be a huge improvement over any other smart phone I have ever used.
Hope that helped. Cheers!
Thanks alot for your detailed analysis! Seems like its a software issue on the evo then I suppose.
in froyo update i think they will fix that
both of them does not have the max touch technology (you cannot use nither fingre nails nor stylus ) and it has the same matrix pattern in all htc devices screen ,so what
hoss_n2 said:
both of them does not have the max touch technology (you cannot use nither fingre nails nor stylus ) and it has the same matrix pattern in all htc devices screen ,so what
Click to expand...
Click to collapse
I realize that Atmel makes the claim that the MaxTouch sensor family works with fingernails, gloves, or a plain stylus, and that we clearly cannot use those things on the Incredible, but rest assured, we have a MaxTouch sensor all the same.
See attached cropped picture of a partially disassembled Incredible, look towards the bottom-center for a chip marked Atmel MXT224. Specifications for the MXT224 are a little different from the overall MaxTouch family description, and they do *not* include mention of support for fingernails, gloves, or plain stylus, while it does specifically reference a 'conductive' stylus.
askwhy said:
I realize that Atmel makes the claim that the MaxTouch sensor family works with fingernails, gloves, or a plain stylus, and that we clearly cannot use those things on the Incredible, but rest assured, we have a MaxTouch sensor all the same.
See attached cropped picture of a partially disassembled Incredible, look towards the bottom-center for a chip marked Atmel MXT224. Specifications for the MXT224 are a little different from the overall MaxTouch family description, and they do *not* include mention of support for fingernails, gloves, or plain stylus, while it does specifically reference a 'conductive' stylus.
Click to expand...
Click to collapse
it is written it only supports two fingres not more
wow this is really confusing, great find on the chip number, so on the specifications it mentions one touch or two touch support.
BUT it is listed under unlimited touch on this page
http://www.atmel.com/dyn/products/devices_v2.asp?family_id=701
what gives?
I've noticed a very slight amount of ghosting on my n7, but most of the existing discussion relates the white-backed google I/O devices (and it's not as bad as some of those examples).
It's most noticeable when switching between landscape and portrait modes. For example...
- Browse threads on xda in landscape for several minutes: Strong contrast between white website and the black back/homescreen/taskswitcher bar.
- Press homescreen button (switches back to portrait).
- I can now see a faint impression of the bar running up the side of the screen, It fades after a minute or two. This is on the default wallpaper.
It's the sort of thing you may miss if you didn't know it was there.
It's not drastic, but my concern is whether it's likely to get worse. At the moment it's less annoying than say a stuck pixel (I'd kick myself if I went for a replacement and found not only did it have ghosting but pixel defects as well, especially given the annoying 'it's not a fault' stance that manufacturer's take on that issue).
I have the screen lift as well of course, but then it seems that's unavoidable?
androidfish said:
I've noticed a very slight amount of ghosting on my n7, but most of the existing discussion relates the white-backed google I/O devices (and it's not as bad as some of those examples).
It's most noticeable when switching between landscape and portrait modes. For example...
- Browse threads on xda in landscape for several minutes: Strong contrast between white website and the black back/homescreen/taskswitcher bar.
- Press homescreen button (switches back to portrait).
- I can now see a faint impression of the bar running up the side of the screen, It fades after a minute or two. This is on the default wallpaper.
It's the sort of thing you may miss if you didn't know it was there.
It's not drastic, but my concern is whether it's likely to get worse. At the moment it's less annoying than say a stuck pixel (I'd kick myself if I went for a replacement and found not only did it have ghosting but pixel defects as well, especially given the annoying 'it's not a fault' stance that manufacturer's take on that issue).
I have the screen lift as well of course, but then it seems that's unavoidable?
Click to expand...
Click to collapse
I'm returning mine because of it. Sounds similar to what you are noticing, but is bad enough that if I spent long enough in the Gmail app I can actually read some of the messages in the imprint left on the homescreen. I noticed it as soon as I first turned on the device and googled for the issue - not because I read about the issue and went looking.
I get the impression it's only some of the I/O devices and a few early retail ones that have this issue. It's far more annoying to me than the screen lift issue and there are hundreds of posts on here about screen lifting. I think if the ghosting was as prevelant there would be a lot more posts on the topic.
00se7en said:
I'm returning mine because of it. Sounds similar to what you are noticing, but is bad enough that if I spent long enough in the Gmail app I can actually read some of the messages in the imprint left on the homescreen. I noticed it as soon as I first turned on the device and googled for the issue - not because I read about the issue and went looking.
I get the impression it's only some of the I/O devices and a few early retail ones that have this issue. It's far more annoying to me than the screen lift issue and there are hundreds of posts on here about screen lifting. I think if the ghosting was as prevelant there would be a lot more posts on the topic.
Click to expand...
Click to collapse
I read about potential ghosting before the device was available, but had forgotten about it by the time mine arrived.
The first time I noticed it was after browsing the bbc news website, there was a faint impression of the site banner running across the middle of my homescreen. Initially I thought it might be uneven backlighting. Then I remembered the ghosting on the I/O devices.
So I wasn't specifically looking for it, but it might have taken me longer to figure it out what is was if I hadn't known.
I haven't noticed it on mine at all.
Sent from my Nexus 7 using XDA Premium HD app
I don't see it, and I just watched about 30 min of a video with a constant tv network logo in the corner.
Well, I went into my local store this afternoon to have a look at the n7 on display.
The screen was suffering from the usual separation (no surprises there), but I couldn't replicate the ghosting issue. Guess I'll be looking at getting a replacement for mine then...
Sad, really love the tablet, shame there are so many teething issues.
Mine is a Pre-Ordered 8gb model and I certainly have extensive image retention. For example, if I leave the default homescreen (with the transformer movie cover on it) up on the screen for anything more than 10 seconds, it will be retained when I scroll left to the blank screen. It remains for something like 3 minutes. Obviously I am RMAing the device and all I can hope is that the replacement doesn't have this issue at least to this extreme level. Is anyone else having this level of retention?
I have an Acer Iconia W700P (Windows 8 Professional) tablet. Although it has only a capacitive touchscreen, not an active digitizer, it came with a nice stylus that is extremely accurate for tasks such as ticking small checkboxes and dragging over text to select it.
The problem I'm having is trying to write or draw in, e.g., Windows Journal or Paint: small features tend to be smoothed out and not registered. E.g., if I attempt to write a number of consecutive lowercase e's ("eeeeeee") at a normal handwriting size, what appears on the screen is a slightly wiggly line; the loops are all gone. I know from dragging over text and such that it's not a question of accurately registering the position of the stylus; it's just that small movements of the stylus are being suppressed or ignored.
A couple of questions: Is this a common issue with Windows 8 touchscreens, or is it specific to Acer? In either case, is there some sort of registry tweak or other setting I can make to get the tablet to register small stylus movements?
Even if no one has a suggestion for fixing the problem, I'd still be interested in knowing if people with other Windows 8 computers with capacitive touchscreens have the same issue. It would be nice to know if this is Acer-specific so I can file a bug report with them, in case it's not a general Windows problem. Thx.
I haven't heard of the issue and don't own a touchscreen windows 8 device myself but my first thought is update speed.
How quickly are you writing the text, it might be that you are writing at a higher speed than the touch position is being updated which I think would be a driver issue.
Capacitive touch displays have a lower tracking resolution than those with active digitizers, hence the rationale for why the latter exists. It's not a bug or a problem. It's a hardware limitation, and there is no software tweak.
For future questions, please search before asking. This will save you time.
http://activeink.typepad.com/active_inks_blog/2011/09/n-trig-vs-wacom-the-digitizer-wars.html
e.mote said:
Capacitive touch displays have a lower tracking resolution than those with active digitizers, hence the rationale for why the latter exists. It's not a bug or a problem. It's a hardware limitation, and there is no software tweak.
For future questions, please search before asking. This will save you time.
http://activeink.typepad.com/active_inks_blog/2011/09/n-trig-vs-wacom-the-digitizer-wars.html
Click to expand...
Click to collapse
Thanks for the reply, but I'm afraid it didn't address my issue.
I am aware that the resolution of a capacitive touchscreen is less that that of an active digitizer; however, as I thought I had made clear in my original post, the accuracy of my stylus on this touchscreen is not a problem.
The issue is tracking motion. This is not a hardware issue, as far as I can tell. I have an Android phone with a capacitive screen (a Nexus 4), and I can reliably write and draw with small features accurately captured. There are videos on the website of the manufacturer of my stylus showing it being used with an iPad (which also has a capacitive touchscreen) to draw and write quite accurately, as well. However, the touchscreen driver (I assume) on my Windows 8 Acer Iconia W700 only accurately tracks the motion of the stylus when the movements are large (greater than 1 cm, approximately). Smaller motions are either squashed to a very small size or are suppressed altogether.
I did a bit more experimentation, and I can be a bit more specific in terms of what the problem is now. If I draw a line, say in Windows Journal, the starting position is accurate to perhaps 0.5 mm -- certainly within the limits of my manual dexterity, at least. The end of the line, however, is always 2-3 mm short of the position of the stylus when I lift it off the screen or change direction. The effect of that is if you're trying to draw a loop that's perhaps 5 mm tall is that the loop just isn't registered at all.
So again, the question is whether this is an Acer quirk or whether it's a Windows 8 issue.
>the accuracy of my stylus on this touchscreen is not a problem...The issue is tracking motion.
Please read better, I did say tracking resolution, not resolution. Inking--where tracking res comes into play--has been problematic on most every capacitive tablet on this site. The iPad is better than many, but it's not for serious inking, either. It works for only relatively large movements.
http://google.com/search?q=ipad+inking
Again, searching readily provides the answer. The issue is your preconception that it's somehow the manufacturer's or OS' fault, and despite answers to the contrary--from the variety of sites you've already asked this question--you cling to your belief.
The capacitive stylus' accuracy means nothing. It's a "dumb" stick with an electrically conductive tip. Tracking accuracy is dependent on the device's sensors, and different devices would likely have different tracking resolution. Smartphones have higher-density display resolution, and should have correspondingly better sensor resolution to match. But it's generally accepted that capacitive displays are not suitable for inking (writing) or drawing. It's in the very link I provided. People who need inking/drawing tablets inevitably use active digitizers.
>the question is whether this is an Acer quirk or whether it's a Windows 8 issue.
It's not a Win8 issue, because Surface Pro (which has a Wacom digitizer) works fine for inking.
http://google.com/search?q=surface+pro+inking
If you want to call the W700's sensor limitation a "quirk," then it's your right. But I don't think you'll get far with your quixotic quest to get better tracking resolution for your tablet. It was never advertised for inking.
e.mote said:
>the accuracy of my stylus on this touchscreen is not a problem...The issue is tracking motion.
Please read better, I did say tracking resolution, not resolution.
Click to expand...
Click to collapse
My apologies for overlooking the word "tracking" in your reply. However, it still seems odd to me that the tablet is able to determine very accurately where I touch the stylus to the screen but not the position of the stylus after I have moved it some distance. And it has nothing to do with the speed with which I've moved the stylus, either.
e.mote said:
Inking--where tracking res comes into play--has been problematic on most every capacitive tablet on this site. The iPad is better than many, but it's not for serious inking, either. It works for only relatively large movements.
http://google.com/search?q=ipad+inking
Again, searching readily provides the answer. The issue is your preconception that it's somehow the manufacturer's or OS' fault, and despite answers to the contrary--from the variety of sites you've already asked this question--you cling to your belief.
Click to expand...
Click to collapse
Actually, this is the first site where I've asked this that I've gotten any response at all, except for answers.microsoft.com, where the Microsoft tech suggested that it was an Acer issue, not that it was an inherent limitation of the technology.
e.mote said:
The capacitive stylus' accuracy means nothing. It's a "dumb" stick with an electrically conductive tip. Tracking accuracy is dependent on the device's sensors, and different devices would likely have different tracking resolution. Smartphones have higher-density display resolution, and should have correspondingly better sensor resolution to match. But it's generally accepted that capacitive displays are not suitable for inking (writing) or drawing. It's in the very link I provided. People who need inking/drawing tablets inevitably use active digitizers.
Click to expand...
Click to collapse
Again, I'm fully aware of the difference between a capacitive touchscreen and an active digitizer. I've owned devices of both kinds.
e.mote said:
>the question is whether this is an Acer quirk or whether it's a Windows 8 issue.
It's not a Win8 issue, because Surface Pro (which has a Wacom digitizer) works fine for inking.
http://google.com/search?q=surface+pro+inking
Click to expand...
Click to collapse
Which is irrelevant to the question at hand, for the very reason you mentioned: the Surface has a Wacom digitizer and a driver for that kind of device. The Acer W700 has a capacitive touchscreen and a corresponding driver. The fact that Windows does well with a Wacom device says nothing about whether the driver for a capacitive touchscreen device is deficient.
e.mote said:
If you want to call the W700's sensor limitation a "quirk," then it's your right. But I don't think you'll get far with your quixotic quest to get better tracking resolution for your tablet. It was never advertised for inking.
Click to expand...
Click to collapse
Well, neither was iPad, but as the video I linked to in my earlier message showed, it does a very acceptable job of tracking the movement of the stylus I have. If it's a hardware limitation of the Acer sensor versus the iPad sensor, I can live with that; I didn't buy the Acer for pen use, and I would have bought a different device if that were what I needed. It could occasionally come in handy, though, hence my question as to whether the issue is specific to Acer or whether all Windows 8 capacitive touchscreen devices are as inferior to the iPad's capabilities as mine.
Anyone else notice if you scroll up and down on any screen, it causes the top and bottom of the screen to warp and get bigger and smaller?
I really notice it when scrolling through cells, try scrolling up and down without lifting your finger really fast on any screen with cells and you'll notice the warping.
Idk if this is a feature or a bug or I'm having a vivid LSD flashback...but I didn't see this happening on the new moto x or the HTC one m8 so I was jw!
I've showed this to a couple different people now and they can see it too. It's kind of disorienting, anyone know a way to turn this off?
I haven't bought my own Droid Turbo but I also noticed this while playing with the phone at Verizon today.
Have you performed the software update?
I'm thinking it might be how the screen refreshes. I'm noticing this as well
can someone post a video ??
Can't reproduce this, please record it
I notice this issue too. Looks like the screen stretches and collaoses at different areas as you scroll vertically. If there is no fix for it i might return my phone makes me almost motion sick
SoulfulSquirrel said:
I notice this issue too. Looks like the screen stretches and collaoses at different areas as you scroll vertically. If there is no fix for it i might return my phone makes me almost motion sick
Click to expand...
Click to collapse
Try setting animation to "off" in all 3 places in Developer tab, I think it helps with image warp.
itanas said:
Try setting animation to "off" in all 3 places in Developer tab, I think it helps with image warp.
Click to expand...
Click to collapse
Turned off all animations and the effect is less obvious but still visible. Bummer.
Turn the phone in landscape
In landscape the phone is unusable because of this issue. I can't believe that they let these out in the wild like this.
Yeah, it's really starting to bother me too. I'm a little OCD though.
So I'm guessing the Nexus 6 will also have this issue as well being they are using the same screen technology (supposedly). Kinda sucks.
So have we figured out if this is an issue with all models or just some models?
I wonder if it's a hardware or software issue. Does it happen in all apps or just some?
theEastonator said:
So have we figured out if this is an issue with all models or just some models?
I wonder if it's a hardware or software issue. Does it happen in all apps or just some?
Click to expand...
Click to collapse
Seems like a hardware issue. Possibly the way the screen refreshes.
I really hope I'm wrong though. It's the only thing making me want to return it.
*Edit* I'm wondering if it may happen because the dpi is so high. Maybe with root we could play around with some display settings to see.
So I guess a lot of people just aren't noticing it? Because when I Google around this thread is the only discussion I find.
(I don't own the phone...I was planning on buying it but observed this issue with the display model and decided to wait).
EDIT: You can see the issue briefly here, as he scrolls around in Chrome:
http://youtu.be/DI3TpYFvbg0?t=5m41s
I was hoping it was just a Chrome rendering issue but it seems that's not the case.
theEastonator said:
So I guess a lot of people just aren't noticing it? Because when I Google around this thread is the only discussion I find.
Click to expand...
Click to collapse
That's what I'm thinking as well. It only happens if you scroll at the right speed, not too fast not too slow. I think a lot of people just don't notice it or don't really think about it or care when it happens
I still can't see it, on mine or in the youtube vid.
I noticed this on mine but I figured it was an animation built in to Android when scrolling (like the word bunch/bounce when hitting the end of a page) but that I just hadn't really noticed it before on other phones because the animation wasn't as smooth, screen wasn't as sharp and screen wasn't as big. I don't notice any weird trailing or stretching when watching videos or playing games so not sure that it would be an issue with the display.
pfroo40 said:
I noticed this on mine but I figured it was an animation built in to Android when scrolling (like the word bunch/bounce when hitting the end of a page) but that I just hadn't really noticed it before on other phones because the animation wasn't as smooth, screen wasn't as sharp and screen wasn't as big. I don't notice any weird trailing or stretching when watching videos or playing games so not sure that it would be an issue with the display.
Click to expand...
Click to collapse
That's the main reason I started this thread haha. I googled around and couldn't find any evidence of this being a new animation. They could definitely play it off as a bouncy animation if that wasn't what they were going for. Looks like it might be a bug though...
Yeah, I don't see the warping in the video or on either of the 2 Turbos in my house. The only thing I can see in the video is the weird lines going diagonally across the screen which is pretty much unavoidable when trying to record video of a screen. The only thing I see on my own phones is that it gets a bit blurry if you scroll too fast.
Sent from my XT1254 using XDA Free mobile app
I'm really hoping it's a software fix. After using the phone a couple of days I'm getting killer battery life. I called Motorola and they told me to call back and speak to tear 2 tech support. Maybe they will confirm a software fix can set things straight. I'll let you guys know if I find out anything helpful.