Related
Right, since this is such a significant impairment (and some users don't seem to experience it), I decided to create a separate thread for it:
If anyone finds out how to properly CALIBRATE the touchscreen on Froyo on Blackstone, please post it here.
So far, the "msmts_calib=0x395.0x3c9.0x79.0x77" results in random keys etc being pressed on the left hand side of the screen.
Thanks
z.
zero0007 said:
Right, since this is such a significant impairment (and some users don't seem to experience it), I decided to create a separate thread for it:
If anyone finds out how to properly CALIBRATE the touchscreen on Froyo on Blackstone, please post it here.
So far, the "msmts_calib=0x395.0x3c9.0x79.0x77" results in random keys etc being pressed on the left hand side of the screen.
Thanks
z.
Click to expand...
Click to collapse
well, there is a bigger problem as the calibration part ...
in froyo it seems to be, that the calibration willb e done automatical and it is not necc. to do anything extra...
but the module/driver for touchscreen is buggy ...
better for testing is the app dotty (can be downloaded from market).
there you'll see, that if you press via finger middle botton, that it jumps on screen touch to left botton - only sometimes ......and with this bug it is almost not possible to use the phone via fingers ...
my boot paramter for calibration is: msmts_calib=0x395.0x3c9.0x79.0x77
but as told above ... the problem is the touchscreen doesn't work correct if using finger ...
if you use the stylus, then it is working, so i think it is a bug, that if the touchscreen driver is getting multiple zones on touching the display, then something strange happen, and then it add an extra point on the left side, which makes using keyboard (SIP) almost impossible.
the only questions would be: does this bug also happenon 2.1 ?
because it it is there working, then we can try to implement the driver from 2.1.
cu camel
Slow down...
Slow down guys...
For 99% of users the calibration works fine, you're in the minority experience tolerance issues.
Touchscreens drift over time, and with heat fluctuations (quite dramatic ones only) etc.
You guys are just unlucky and have devices that have clearly drifted by some amount....
Now, there ARE instructions floating around about how to fix calibration issues, but they aren't on the Blackstone thread, they are elsewhere and I can't recall quite where, but they DO exist.
When it comes to used a finger instead of a stylus, here you just have to live with the differences between a resistive and capacitive touchscreen. Resistive is the one used on Blackstone and most other touchscreens older than 18 months old, whilst never devices tend to have capacitive screens.
What's the difference?
Resistive need physical pressure against the screen, but can be highly accurate in ONE position. You can use these screens with or without a stylus, so can be good for handwriting recognition etc.
Capacitive need NO physical pressure against the screen, but are less accurate.
However they can detect multiple presses at the same time in different parts of the screen.
You can't easy use these screens with a normal stylus and so they aren't ideal for handwriting recognition or fine detail work.
When it comes to using your finger on resistive screen, a lot of accuracy is lost... you're just pressing a large area of the screen and the screen can only deduce ONE point under your finger. This can lead to inaccuracy and wrong buttons being pressed with a UI that has tiny icons and controls.
If your touch calibration is ALSO out, then things get worse still.
Now, before any techies get too techy, there ARE some 'smart' techniques for trying to have multi-touch on resistive displays, but we will no go into that here, and they are generally 'hacks' that don't work in all scenarios.
You guys just need to get your displays recalibrated... that should cure 95% of all your problems, and the remaining 5% are just the stuff we all face... like no multitouch, pinch to zoom etc
It's definitely wrong to give the impressions that XDAndroid releases simply don't work correctly with touch screen. That's very misleading indeed.
i too have issues with touch screen accuracy (both 2.1a and 2.2 v1.0)
80% of the presses are fine, but the other 20% xdandroid would place my finger about 1" to the right, slightly down of when i first contact the screen, and then work out where i've actually pressed a fraction of second later, translating it into a swipe etc.
the touchscreen tool in the debug area proves this fact.
WM is perfect.
weirdly, it seems not to occur at all/noticably less using the stylus. maybe something todo with pressure/contact area?
i do think the OP has a valid issue tbh.
TheBrilliantMistake said:
Slow down guys...
For 99% of users the calibration works fine, you're in the minority experience tolerance issues.
Touchscreens drift over time, and with heat fluctuations (quite dramatic ones only) etc....
Click to expand...
Click to collapse
Thanks for the info.
First, I didn't mean to mislead anyone. I just noticed increased inquiries about this issue and I wasn't aware of the 99% of users having it perfectly working...is this a fact btw?
Besides, I am aware of the different types of displays but obviously, pinch zoom etc are not exactly the main concern, we are just looking to use the phone with our fingers mate!
I agree - I have been using the phone for many months running WM and I had no issue, whatsoever. I am not much of a techie but you are still referring to the software calibration, correct?
Thanks for sharing some valuable info again. I would love to see those instruction on how to do this calibration as without it and along with much of resentment to use stylus, it pretty much makes the phone running Froyo useless )
zero0007 said:
Thanks for the info.
First, I didn't mean to mislead anyone. I just noticed increased inquiries about this issue and I wasn't aware of the 99% of users having it perfectly working...is this a fact btw?
Besides, I am aware of the different types of displays but obviously, pinch zoom etc are not exactly the main concern, we are just looking to use the phone with our fingers mate!
I agree - I have been using the phone for many months running WM and I had no issue, whatsoever. I am not much of a techie but you are still referring to the software calibration, correct?
Thanks for sharing some valuable info again. I would love to see those instruction on how to do this calibration as without it and along with much of resentment to use stylus, it pretty much makes the phone running Froyo useless )
Click to expand...
Click to collapse
But windows mobile typically makes you calibrate your screen when you reflash a ROM, making the calibration specific to your device.
It's also not clear where the calibration info is stored, other than the registry it MAY be stored in E2, or some flash area somewhere. Regardless, it usually forces you to recalibrate (some custom ROMs skip this).
The XDAndroid chaps deemed to 'auto configure' Blackstone calibration for some reason, and this is the most probable reason why folks are having issues.
As for 99%, hummm well, just my releases alone have over 20,000 downloads, and my stuffs one of the lesser used!... yes, some folks have calibration issues, but the majority aren't reporting any... I've maybe seen/heard 20 folks with the issue... that's not too many all in all across all the various releases. AND, some of those guys were also the types of guys saying "this sucks, the battery lasts 2 hours".... as if we didn't all know that ;-)
There was a calibration tool floating around somewhere, plus, those values CAN be edited to suit your device, so there is some home!
Wow, I thought I was one of the only people that had the calibration issue. X_X It's what caused me not to use XDAndroid as much. =(
Anyone have any idea what the calibration tool was? I tried searching calibrate and calibration but no tool was mentioned in the Blackstone droid threads.
PS. I have no idea on how to change the calibration values... =/ When I open up the ts_calibration it shows up as blank. When I open up the startup.txt ("msmts_calib=0x395.0x3c9.0x79.0x77") I do not know exactly what the values affect.
Update:
I tried using the stylus but it currently has the same problem as if I was just using my finger... Does that mean that my touch screen is going out on me? =(
I have a problem too with touch screen calibration.....I guess i'm 1% of users...
im curious as to how maany others have this issue - seems theres a few coming out of the woodwork now
im sure the XDAndroid FAQ or the release thread says the devs are aware of almost all issues so dont bother reporting them (or something to that effect), yet i havent seen anyone mention touchscreen issues upto this thread.
does anyone see a need for a bugtracker for the XDAndroid, or are the forums sufficient? to me, forums seem a bit 'unofficial' with reguard to bugs - maybe an official bug tracker (specific to the android project) would help everyone to see what people are experiencing and numbers involved.
i must say i am only a user, so i dont see or get involved in the development side so maybe this thing already exists in closed circles.
to put it another way, each phone has their own android subforum so it must take the devs alot of time to collate info. bug tracker could be a better way to manage this?
I have the same problem, since 1.6... i touch the screen and is like i touched 1cm outside the screen on the left for 0.001 seconds, so is extremly difficult to type without stylus.
with the stylus is much better but still not good
Ps. i remember the first version of android working on blackstone (1.5 i think) was working good, and the touch screen was fine
veehexx said:
im curious as to how maany others have this issue - seems theres a few coming out of the woodwork now
im sure the XDAndroid FAQ or the release thread says the devs are aware of almost all issues so dont bother reporting them (or something to that effect), yet i havent seen anyone mention touchscreen issues upto this thread.
does anyone see a need for a bugtracker for the XDAndroid, or are the forums sufficient? to me, forums seem a bit 'unofficial' with reguard to bugs - maybe an official bug tracker (specific to the android project) would help everyone to see what people are experiencing and numbers involved.
i must say i am only a user, so i dont see or get involved in the development side so maybe this thing already exists in closed circles.
to put it another way, each phone has their own android subforum so it must take the devs alot of time to collate info. bug tracker could be a better way to manage this?
Click to expand...
Click to collapse
I was actually thinking about the same thing..unsure how to proceed though...
mitikos said:
I have the same problem, since 1.6... i touch the screen and is like i touched 1cm outside the screen on the left for 0.001 seconds, so is extremly difficult to type without stylus.
with the stylus is much better but still not good
Ps. i remember the first version of android working on blackstone (1.5 i think) was working good, and the touch screen was fine
Click to expand...
Click to collapse
I would dig up that version along with calib code in the startup txt file then!
well, i've put the idea forward in the main android subforum here.
it would certainly be useful from a user side perspective to see progress and known issues. fingers crossed
edit: and when did i move to 'Senior member'!!?
I experience similar issues with 2.2, didn't notice it to the same extent in 2.1. When I type on the on screen keyboard, pretty often i get an added button press detected off to the left (about 2 - 3 cm). The problem does occur a lot less when using the stylus instead of the finger.
This is NOT likely to be a calibration problem, as in that case all presses would be off consistently (e.g. always half a centimeter in the wrong direction or something like that).
It looks as if the Touchscreen sends some "incorrect" data that WM filters as too short of a press or whatever and that is affecting some users.
mmm, questionable.
Calibration is as far as I'm concerned done each time, individually with new system (ROM) unless using a saved one from previous attempt install (my Froyo case).
To my understanding of the matter, wrong calibration doesn't necessarily have to mean your display is "shifted" 2cm to the left or so. Simply, it just doesn't work properly i.e. you have the same problem as all other people in this thread.
Maybe reading TheBrilliantMistake's post about different types of screens earlier would help you understand...
after all, we need that calibration tutorial/tip which is allegedly somewhere around here...
StevieBallz said:
I experience similar issues with 2.2, didn't notice it to the same extent in 2.1. When I type on the on screen keyboard, pretty often i get an added button press detected off to the left (about 2 - 3 cm). The problem does occur a lot less when using the stylus instead of the finger.
This is NOT likely to be a calibration problem, as in that case all presses would be off consistently (e.g. always half a centimeter in the wrong direction or something like that).
It looks as if the Touchscreen sends some "incorrect" data that WM filters as too short of a press or whatever and that is affecting some users.
Click to expand...
Click to collapse
I have the same problem, exatly the same.
Cant we set android to ignore the first 0.1seconds of a pression on the screen?
StevieBallz said:
I experience similar issues with 2.2, didn't notice it to the same extent in 2.1. When I type on the on screen keyboard, pretty often i get an added button press detected off to the left (about 2 - 3 cm). The problem does occur a lot less when using the stylus instead of the finger.
This is NOT likely to be a calibration problem, as in that case all presses would be off consistently (e.g. always half a centimeter in the wrong direction or something like that).
It looks as if the Touchscreen sends some "incorrect" data that WM filters as too short of a press or whatever and that is affecting some users.
Click to expand...
Click to collapse
ah - finally
now you got it - this is exact the problem what i want to tell everybody ..., and i'm sure, that this happen, because the touch screen driver doesn't calculate correct the position when a bigger range (like touch from a finger) is touched. This doesn't happen, when stylus is used ...
to remove the first 0,1 sec or something ... don't think, that this would help
...on the other hand ... which module is responsible for touch screen ?
Just for a start the background of calibration (it's on security risks with touchscreen based voting machines but the principle is obviously the same) - http://vote.nist.gov/threats/papers/touchscreencalib.pdf
I believe TheBrilliantMistake in this case thought we'd sometimes hit adjacent buttons. But fact is, it always does trigger to the left and in addition to the correct press being detected, so well there's something else to this one.
Guess it will be ironed out eventually as it's a lot less common in 2.1. But it's annoying to the point of making texting a real pain in 2.2.
StevieBallz said:
Just for a start the background of calibration (it's on security risks with touchscreen based voting machines but the principle is obviously the same) - http://vote.nist.gov/threats/papers/touchscreencalib.pdf
I believe TheBrilliantMistake in this case thought we'd sometimes hit adjacent buttons. But fact is, it always does trigger to the left and in addition to the correct press being detected, so well there's something else to this one.
Guess it will be ironed out eventually as it's a lot less common in 2.1. But it's annoying to the point of making texting a real pain in 2.2.
Click to expand...
Click to collapse
does it means, that under 2.1 there is no such kind of "touchscreen bug with finger" ?, because then we can take a look to the modules - maybe we can compare the difference to 2.1 ...
I didn't experience it there but I have to admit that I didn't use 2.1 for too long. Maybe it's a speed issue with 2.1 being more optimized and polished then 2.2 which leads to it occuring on a less frequent basis.
Due to the known problems with powersafe modes not being supported yet in XDAndroid I'm currently mostly running WM6.5 but I'm looking forward to the advancements with XDAndroid, great project.
Add 2 more devices to the 1%.
I'm experience the same issue. My friend which has a newer Blackstone than me let me put my XDAndroid mSD card into his phone and there goes the same issue.
Tested with some drawing applications, here is what i experienced:
Just like others stated before most of the times when the bug occurs I get a line starting like 2 cm to the left of my finger (and a little lower) and ending under my finger. It's like I've been dragging my finger across the screen for 2 cm. Sometimes it goes as far as the left side of the screen.
Since this is inconsistent I doubt it's a calibration issue. I must assume it's the driver. But I might be wrong.
Anyway I believe a lot more people than 1% are experiencing the issue but they aren't posting about it since they believe it's a known issue.
Hey guys I always knew that multitouch on HD2 isn't pefect at all, but now I noticed a peculiar behavior which I was not aware (tnx to ICS)...
enabling a function in developer settings to show pointers position I discovered that multitouch is working in a wrong way.
When you put the second finger over the screen it is recognized correctly but when you move it close to the same axis of the first one (both vertical and horizontal axis), it automatically get aligned on the same abscissa or ordinate (depends which axis was closer) even if the fingers are not aligned.
This is frustrating when I use some apps that take advantage of multitouch, such as games or emulators, because while I'm pressing a key on the screen and I need to press another one on the opposite side, but not perfectly aligned, I get a wrong recognition and often I press another key or a blank space.
I hope I was clear, but to understand better the problem you should activate that function in developer settings and try yourself.
Please give me a hope to think it is a solvable problem... maybe with a better driver :fingers-crossed:
That's just the screen I'm afraid. I've had the same issue with every ROM I've tried, and there's nothing you can do to solve it. At the very least, it's nice for me to hear some confirmation that I'm not the only one who experiences this.
Nigeldg said:
That's just the screen I'm afraid. I've had the same issue with every ROM I've tried, and there's nothing you can do to solve it. At the very least, it's nice for me to hear some confirmation that I'm not the only one who experiences this.
Click to expand...
Click to collapse
I read around the forum that HD2 has hardware capabilities, so I think we need to get better input driver
The hardware doesn't support more than 2 points, and it does this rather poorly too. It's not so bad when using things like pinch to zoom or using two fingers to turn the map in Google Maps but when gaming it can be a bit of a pain. There's no driver that can increase the number of points the HW can support (if there was one then surely it would already have been implemented in Android) so afaik there's genuinely nothing that can be done about this. If there is, I'm sure someone will correct me soon.
It's a known issue and we can do nothing about it because of not so good touchscreen. Hardware problem, you know. It's present in every OS and in every ROM. For gaming I'd recommend getting a PS3 controller or using OTG cable and some other gamepads, like the X360 one.
Spaqin said:
It's a known issue and we can do nothing about it because of not so good touchscreen. Hardware problem, you know. It's present in every OS and in every ROM. For gaming I'd recommend getting a PS3 controller or using OTG cable and some other gamepads, like the X360 one.
Click to expand...
Click to collapse
Maybe you're right, an external controller is the best choice, but I don't want to bring with me other accessory when I'm outside... for the wrong recognition I think it's just driver fault because the problem is software side. When I use one finger is really precise the issue is when I try to use two fingers, because the driver is written wrong and read a fake position
Maybe this makes things a bit clearer. http://www.tactyl.com/fr/telecharger/39-drivers
Back in the days, there weren't that many "multitouch" apps out there for android.
If you look at the nexus one, it's even worse. http://www.youtube.com/watch?v=5puAvPqXpuc
From reading one of the booklets that came with the HD2 it all comes down to single-touch and a pinch-to-zoom gesture which both work most of the time.
Some people who developed emulators at that time, tried to avoid this "autoalignment" by putting the pads in opposite corners.
While still many people don't know that pressing on the edge of the screen, of the HD2, with at least one finger can cause
a swap in the y-axis once the second input is on the screen. (almost like in the nexus one video)
In very good light you can see this "edge-area", it's about ~4mm thick on each edge.
You can always download MVT and test it yourself. https://play.google.com/store/apps/details?id=com.batterypoweredgames.mtvistest&hl=en
Some time ago tatsumaki made a decent virtual gamepad for fpse which got rid of the alignment by incorporating it in the way he/she arranged the buttons and button mask.
No one is going to fix this by a new driver,
End of story.
Update April 1st 2014: Many owners of a Note 3 these last few months have reported that their updated firmware does not suffer any multitouch issues (anymore). A few people have reported that newer firmware has re-introduced multitouch issues, so I'm still calling it "Mostly fixed". I will update the opening post if this status changes.
Below text is still phrased like the problem is "current" in many Note 3's. Will update that part soon.
------
Hi while checking my new model Nexus 7 for (minor) multitouch problems with the apps "MultiTouch Test" and "MultiTouch Tester" I also tried these on my Note 3. Here I discovered that fingers/touches kept disappearing even with only 3 or 4 fingers on my European Note 3. Just moving the fingers about made 1 or more touches disappear. Since then I discovered the problem is much more severe, and can happen with only 2 fingers on the screen, making it far more likely it will disrupt normal phone usage.
If you're interested if your Note 3 has this problem, for warranty sake or otherwise, you can either follow the written steps below or try to emulate the videos.
3RD UPDATE:
A procedure to check whether you have the multitouch defect: (UPDATED on October 12th)
1. Download and run a multitouch testing app of good reputation (I tried both MultiTouch Test and MultiTouch Tester).
2. Put 2 (or more) fingers on the screen of your Note 3 in a horizontal line in landscape mode. You can also use Portrait mode with 2 fingers (shown in the second video below).
3. Move the fingers slightly about, trying to have both (all) in a straight horizontal line.
4. After only a bit of trying one (or more) detected fingers should disappear (become undetected) or ghost touch detections should appear.
To make it easier to detect these 'glitches' you can either use more fingers (3 should suffice) or try to emulate the videos below. If you don't have the Multitouch problem on your Note 3 then please also fill in the Poll so we get an idea of the scope of this phenomenon. Thanks!
Video showing 3 fingers 'gltching' in landscape mode: (beside a Galaxy Note 1)
Video showing 2 fingers 'glitching' in portrait mode:
Video showing erratic Multitouch behavior with more fingers: (through an "unwilling" participant )
(moving your fingers around a bit you should have the same Multitouch issues with only 3-5 fingers on screen)
Ps: I included a "Have not tested yet" entry in the Poll, fully expecting a user to change his/her choice later on; the xda forum software doesn't allow changing either the Poll or your choice unfortunately.
Mine works ok with 4 fingers. But with 5 or more, it's where the problems start.
What exactly does this mean? Not expecting to use more then 2 fingers at once. It seems pointless to me. No?
It's hard today use 5 finger on the phone
Sent from my SAMSUNG-SM-N900A using xda app-developers app
tWoBrO said:
Mine works ok with 4 fingers. But with 5 or more, it's where the problems start.
What exactly does this mean? Not expecting to use more then 2 fingers at once. It seems pointless to me. No?
Click to expand...
Click to collapse
It seems I would agree, but seeing the commotion on the Nexus 7 forum and the impact on control glitches while playing games I thought I'd raise the question. Better to know and understand then pure ignorance.
Agree, that's why I asked.
Personally I don't remember one single time that I have used 3+ fingers on the screen.
Ettepetje said:
Hi while checking my new model Nexus 7 for (minor) multitouch problems with the apps "MultiTouch Test" and "MultiTouch Tester" I also tried these on my Note 3. Here I discovered that fingers/touches keep disappearing even with only 3 or 4 fingers on my European Note 3. Just moving the fingers about makes 1 or more touches disappear. Can others check as some don't seem to have this problem. Thanks in advance!
Click to expand...
Click to collapse
I had that problem too. I noticed that when I didn't manage to drift in Mario Kart. I had to change my controller layout so it is not symmetrical because the problem seems to appear when your third touch is at the same level as your first one (sorry if that doesn't make any sense, English is not my primary language).
(I have a N9005 btw).
Hayleia said:
I had that problem too. I noticed that when I didn't manage to drift in Mario Kart. I had to change my controller layout so it is not symmetrical because the problem seems to appear when your third touch is at the same level as your first one (sorry if that doesn't make any sense, English is not my primary language).
(I have a N9005 btw).
Click to expand...
Click to collapse
Mine is a N9005 too. There must be many more people with such a defective Note 3 but not yet discovered it.
sounds like a touch screen driver problem. contact samsung about this. if they know it they will fix it at the next firmware release.
Did you use the built-in "show touches" feature in developers options to rule out any app compatibility issues?
mi7chy said:
Did you use the built-in "show touches" feature in developers options to rule out any app compatibility issues?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, with such small round indicators, that feature doesn't help much in discovering suddenly disappearing finger touches.
I have used the latest version of both apps ("MultiTouch Test" and "MultiTouch Tester") mentioned in the openingpost. Sofar it seems that some people have the issue and others haven't, which would indicate that the problem is inside the phone, not the app(s).
A procedure to check whether you have the multitouch defect:
1. Download and run a multitouch testing app of good reputation (I tried both MultiTouch Test and MultiTouch Tester).
2. Put 3 or 4 fingers on the screen of your Note 3 in a horizontal line in landscape mode.
3. Move the fingers about trying to have at least a couple in a straight horizontal line (still in landscape).
4. After a bit of trying one or several detected fingers should disappear (become undetected) or ghost touch detections should appear.
5. In my case I can have 3 fingers on the screen with only 1 or 2 detected.
Today I got assured from somebody working at a local (Dutch) Samsung service center that Samsung won't exchange or repair my phone with the knox warranty flag set. They will just send it back and void the warranty. I'm also sure that many more people have this defect but don't know it yet, so it could become wise (or crucial ) to check for this problem BEFORE rooting your Note 3.
I will make a mention of this situation in some rooting topics so people are warned beforehand and can do a quick check for this phenomena. On my phone it looked like a Nexus 7 type defect which I am sure a lot of (smart phone) gamers will find highly undesirable.
Yup, definitely have this issue myself. Very worrying.
neoKushan said:
Yup, definitely have this issue myself. Very worrying.
Click to expand...
Click to collapse
neoKushan, thanks for your comment. Sofar you are only the third or fourth with this defect I am aware of.
I added a poll so we can collect data on this without everyone needing to reply (not that I want to discourage anyone from replying ).
Yes, my phone does have this problem, when I put more than 4 fingers on the screen horizontally or very closed to each other, it's shown only 2-3 fingers, sometime only 1. I dont use that many finger on my phone but it just bug me to know that I have a defected phone...
I can reproduce it after a lot of moving the fingers around but it's not easily reproducible. I'm not sure if I brought it back to the store they would recognize it as a problem since it mostly works normally. Is that how it is with others, or are you able to easily reproduce it time after time?
When I align three fingers one can disappear after messing with it for awhile. But if one does disappear and I put a fourth finger, ghost fingers appear and it spazzes out. (in any case, i have to mess around quite a bit before anything weird happens)
I haven't rooted yet, should I take to T-MOBILE and show them? Will they just dismiss it, like it's not an issue?
Is it REALLY an issue? I really want to root my phone, but I don't want to have issues later.
It can certainly be an issue (the 3 finger version at least) if you play games on your Note 3 using on-screen controls. Someone earlier here mentioned Mario Kart.
No problems here
I have the SM-N900W8 Canadian
All multitouch test apps work fine for me
All fingers move and detected perfect
10 fingers were detected (5 were mine, 5 were my co workers) =O
wtf?
first test, with 6 fingers looks good. I did some strange movements, everything looks ok.
but you are right, in landscape mode, with 4 fingers on a row,
very strange effects are visible.
2 from 4 focal points are temporarely lost.
tested on a german version gt 9005 stock rom without root, yet.
Hey guys, I just picked up my Tegra Note and I'm enjoying it, but in testing out the potential and limitations of the DirectStylus, I came across a problem and I want to find out if it's just my problem, or if it's reproducible with all Tegra Notes with the latest system updates.
Basically, I'm using the stylus, and stylus only mode is activated. This works pretty well and ignores most/all inputs from anything except the tip of the stylus.
However, I have noticed that if I slide my finger onto the screen from the outer edge/bevel, it will often (nearly 100% of the time) register this as a touch. For an example, if I tap the home button with my finger nothing happens, however if I drag my finger from just below the screen onto the home button, it will press. Likewise I cannot scroll through home screens by normally swiping my finger, but if I swipe from off screen on the left or right, it will register. Bringing down the notification area with a finger swipe, etc, all work as well when naturally this should only be possible with the stylus.
The main problem with this is when writing/drawing with my hand resting on the edge of the device. If my palm is entirely off the screen it is fine. If my palm is entirely on the screen then stylus only works, too. However, if in the process of writing my hand slides from the side onto the screen, suddenly the stylus looses focus and I'm drawing lines with my palm.
I hope I have explained this issue correctly, and I wondered if this was a known problem? If there are any solutions? Have I messed up and set an option somewhere I shouldn't have? Should I get it replaced? Sorry for all the questions! :laugh:
Oh and it's not rooted or anything. Just stock, updated to the latest system version through the system updates.
Thanks, hope you can help!
I get a similar issue at the bottom left of the screen sometimes. It only seems to effect the bottom left but in both orientations so that rules out a hardware issue. Doing a quick lock and unlock seems to fix it for me and it functions fine until next time I turn on stylus mode. Seems hit and miss with no real way to replicate it.
It didn't seem to do it before ota 2.3 so I predict a hotfix for the issue. Its a minor issue, the battery life on 4.4.2 isn't however, 4-5hrs with lite use is pretty rubbish. I suspect that's an issue with the power saving features (I think it's stuck on Max performance all the time).
Would be nice if they fix the SD write issue but Google dictate that I think.
Mine was certainly a lot worse than that - persistent on all four edges of the screen and there is no way to stop it. 60-80% of the time it was manageable, but consistently reproducible, other times it was far worse and could only manage dots and dashes when I tried to write anything while resting my palm on the screen. It also developed a 'blind spot' problem I've noticed reported on a couple of forums - a spot where the stlus simply refused to draw - so I grew more concerned that I had a problem with the actual hardware. So, I took it into the store I bought it from, and they're going to replace it for me.
Hopefully I won't have a problem with the replacement one, because I absolutely love the tablet!
I've had similar problems... just remember, all of the stylus functionality is governed by software; the screen on this is simply a regular capacitive screen that's also capable of detecting the size and shape of what's touching it, and the rest is calculated by software. It's a neat idea, but in practice it hasn't held up as well as Nvidia would've liked us to believe. Now that I've had a Galaxy Note 2 for a couple months, I have to say that the active stylus experience blows the TN7 away, but then again it's a much more expensive technology to implement. I almost always used a pencil with my TN7 while it was my day-to-day work buddy since I found the stylus to be too sticky and hard to write with... I also found several of the issues I was having weren't as bad while using a pencil, so maybe you could give that a try. Also, remember that if the screen is dirty that it will affect the stylus's performance as the screen is so sensitive that even a little moisture could register as a touch on the screen.
I received my replacement tablet today, and it is a lot better than the one I previously had. While the problem is still there, it is far, FAR better than before. Now it seems to be a minor nuisance, rather than a consistently reproducible problem. On top of that it has a much more vibrant screen - less yellow and washed out - and no 'dead zones' when trying to write with the stylus. So while I am certain software has an impact on performance, there must have been something weird going on inside the hardware of my previous device, too.
Considering the price, the fact that others have had similar issues, and how much I like about everything else - I'm very happy with my new TN7 now!
Have same problem .... When i swipe from left or right side of the screen it detects stylus nd do all the things.... Dont knw wat to do amazon is not replacing too the tablet..!
Same problem, I don't usually mind it other when I'm using an app like sketchbook pro, it becomes really annoying.
Sent from my Nexus 5 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2787574
Sent from my Nexus 5 using Tapatalk
Hi all,
I'm happy new owner of OnePlus 6T for 1 day. However I noticed something that makes me frustrating. The touch in this phone works worse than in other phones. I noticed it after updating system to newest version (9.0.6 I think) but I don't know if it is related to software. I downloaded Multi Touch app and if I push on screen very weak and then normally, it won't register touch. Also, clicking very fast on screen the phone sometimes doesn't register any clicks for even more than one second ! I thought maybe I'm exaggerating, but tested Huawei P20 Lite and every single touch gets registered properly. However when the touch is registered normally, moving finger across the screen it never gets lost, which makes me think it may be just software glitch. Please tell me if I can have faulty model, or it's just something with the software. I got no answers on OnePlus forums, so I hope to get at least one here. Thanks.
I can't replicate that at all. All touches respond, and all 10 touch events. Tapping quickly, adding fingers, etc all work as intended.
That's strange. I've tried with FactoryMode handwriting ad it seems everything is just perfect... Maybe the app is bad ? One thing that still doesn't work though, is multi touch. When I press more than 2 fingers simultaneously, it won't register anything. But when I press all 10 fingers one by one, everything is perfect. Is it normal ?
No touch problem here. You might have a faulty digitizer.
Ok, it is definitely software glitch. When I enabled option to show touches in developer options, everything is recognized properly. OnePlus messed up with it, because apps can't detect more than 2 fingers simultaneously.
I found 100 % working fix for this here:
https://forums.oneplus.com/threads/multi-touch-on-the-oneplus-5.556144
The software takes over handling touchscreen events so it can take a screenshot when you swipe three fingers. If you've got that enabled then disable it and try your tests again.
Using Multitouch Tester I was able to register 10 simultaneous touches.
Edit: Yeah, as per the link in the previous post.