Related
hi all, some times, i dont know if its a weird rom issues or dust or even the wind, but some times ill finish what im doing on the phone then the menu or what ever im on will start doing weird **** like im touching it, but im not, is this just my handset or everyone.
say im in a picture and stop doing what im doing the pic might just randomly flick up/down till i exit with end key, same as all other apps things gets randomly selected lol
This happens to my unit also sometimes.
For me, I think that it only happens when connected to the usb cable.
DAMIEN123_666 said:
hi all, some times, i dont know if its a weird rom issues or dust or even the wind, but some times ill finish what im doing on the phone then the menu or what ever im on will start doing weird **** like im touching it, but im not, is this just my handset or everyone.
say im in a picture and stop doing what im doing the pic might just randomly flick up/down till i exit with end key, same as all other apps things gets randomly selected lol
Click to expand...
Click to collapse
Did you change the device name to "skynet"?
lmao.. that sounds strange!
This isn't strange at all. I'm working with many capacitive screens and whenever you have a lot of interferences (static charges, ground), the screen treats them as inputs. The bigger the screen, the more sensitive it becomes.
One solution is to reduce the sensor threshold, but for the Leo, you may not be able to configure the sensor...
TrYde said:
One solution is to reduce the sensor threshold, but for the Leo, you may not be able to configure the sensor...
Click to expand...
Click to collapse
It's gonna be +1,000,000 at least for anyone who comes up with an app to do that!
TrYde said:
This isn't strange at all. I'm working with many capacitive screens and whenever you have a lot of interferences (static charges, ground), the screen treats them as inputs. The bigger the screen, the more sensitive it becomes.
One solution is to reduce the sensor threshold, but for the Leo, you may not be able to configure the sensor...
Click to expand...
Click to collapse
Does the iPhone allow you to do this?
count me in and I can actually make the screen go "crazy"
http://forum.xda-developers.com/showthread.php?t=584867
when can we expect a new rom from htc, maybe it will solve the issues
I think your device is broken, i have had the same problem and i swapt my device for another one and now i don't have the problem anymore.
So if it happens often you should go back to the shop you've bought it.
It's happened once to me (in Opera) in several days of quite intensive use (love this phone ).
Having the same problem with my device. For no apparent reason, it would have a mind of its own and constantly trigger parts near the centre of the screen, it got quite freaky when it kept hitting 2 for me when I was dialling a number.
Will be popping into store to get it changed tomorrow (if they have stock).
same here, screen sensitivity is way too high. Hope a fix comes out for this
Had my phone exchanged today, new one running smoothly!
Hi.
I have a problem with my hd2's screen.
Often i press the wrong buttons when typing and so on, And ive come to the conclusion that its something wrong with the screen.
To test this ive gone to the file explorer and then grab the slider to scroll down and hold my finger perfectly still.
And even tho im 100% still it stills jumps up and down like crazy.
I can imagne that its this that makes me type the letter beside the one im trying to hit.
Anyone else has this problem or did i get a faulty phone?
Regards, Joakim
A few other people have reported "jittery" screens. Have you applied any of the decreased sensitivity hacks? I believe there's 1 on BsB tweaks, which is nice and easy.
hargibi said:
Hi.
I have a problem with my hd2's screen.
Often i press the wrong buttons when typing and so on, And ive come to the conclusion that its something wrong with the screen.
To test this ive gone to the file explorer and then grab the slider to scroll down and hold my finger perfectly still.
And even tho im 100% still it stills jumps up and down like crazy.
I can imagne that its this that makes me type the letter beside the one im trying to hit.
Anyone else has this problem or did i get a faulty phone?
Regards, Joakim
Click to expand...
Click to collapse
Have you tried re-aligning the screen and secondly reduce the sensitivity of the screen using BsB tweaks? this might solve your problems
the screen is very erratic: often when pressing backspace seemingly in the right spot the screen will jitter and incorrectly register different parts of the screen. often during texts the cursor will jump to the beginning of the text for no good reason. i find that this problem is augmented in cold conditions or when my fingers are not 100% dry.
I am no authority on screen technology so can only theorize but i suspect the problem to be linked to the fact that Windows Mobile does not natively support capacitive touchscreens (the driver for our HD2s was developed by HTC ). Other mobile OS such as iPhone OS and Android do not suffer any problems like this. we can also rule out a hardware fault here as i own/ed three different HD2s, all of which suffer from this jittering. The next update to Windows Mobile purportedly includes NATIVE capacitive support, which would - i suspect - have undergone more rigorous sensitivity and usability testing and will therefore lead to a better experience on the whole. i suspect that we won't get a truly excellent experience with Windows Mobile until 7 is released. The Windows Mobile we use now is very ancient under the technobotox, which probably explains the frequent freezes, glitches and slowdowns our HD2s suffer on a daily basis despite the awesome specifications (and perhaps why - up to now, Microsoft have put so little effort into the intentionally generic and rather stale Marketplace).
I applyed the screen sensitivity cab and now it seems much better. ill report back tomorrow when ive used it a bit
help!!!!
i installed bsb tweaks 1.6 and aligned the screen,my hd2 still jitter
Hi, Just wonder if you still have the screen problem (register the wrong place when click) after the upgrade.
No. You should check out the humongous thread on google support forums. Googe have now abandned even giving updates on this serious problem.
http://www.google.com/support/forum...8e&hl=en&fid=04134c63c784258e00047fdfe09ae547
p.s. no fix in ere36b either (as im running that now and still experience this problem at random)
I don't understand this issue, I just don't see it on mine at all, no matter what ROM I install ... there has to be something more to this than a simple fault across all handsets ... either select faulty ones or some other factor. Mine just works 100% as expected at all times.
That said I have had no 3G issues either, no matter what radio version I use. Perhaps I am lucky ?
I think its because people are touching the edge of the screen while pressing with the other causing it to register incorrectly
duncan888 said:
I think its because people are touching the edge of the screen while pressing with the other causing it to register incorrectly
Click to expand...
Click to collapse
That is not it, there are plenty of videos that show the touchsreen misfiring while just laying on the table. Also, the way I hold my phone I am never touching the glass surface other than with the one finger doing the touching.
With regards to some people not seeing it, this issue is very random. I can go for days without noticing it and then out of the blue it would come back, most annoying when it happens while typing something.
There is another somewhat related issue with the sensor on the n1. If you download an app called multi touch paint and try to draw two parallel lines simultaneously from say top left corner down to bottom right you will see that the lines are not straight at all and full of zigzags. Only way that this sensor recognizes multiple lines properly is if you draw perfectly vertical or horizontal lines.
There is also a discussion on developer groups where game developers are pointing out this very problem of multi toch totally being screwed up where it switches axis causing your touch to register in completely the wrong place. From the comments of the android engineer it makes it seem that the sensor hardware is just like that, cheap and low quality.
Link to discussion: http://groups.google.com/group/andr...read/thread/d0aa3eea8fd9a2b8/9a8ea81133866460
duncan888 said:
I think its because people are touching the edge of the screen while pressing with the other causing it to register incorrectly
Click to expand...
Click to collapse
trust me its not.
i have had this twice and has nothing to do with that.
i dont see it as a huge problem but a lot of people are getting this on a daily basis..
vas41 said:
That is not it, there are plenty of videos that show the touchsreen misfiring while just laying on the table. Also, the way I hold my phone I am never touching the glass surface other than with the one finger doing the touching.
With regards to some people not seeing it, this issue is very random. I can go for days without noticing it and then out of the blue it would come back, most anyin when it happens while typing something.
There is another somewhat related issue with the sensor on the n1. If you download an app called multi touch paint and try to draw to lines simultaneously from say top left corner down to bottom right you will see that the lines are not straight at all and full of zigzags. Onlyway that this sensor recognizes multiple lines properly is if you draw perfectly vertical or horizontal lines.
There is also a discussion on developer groups where game developers are pointing out this very problem of multi toch totally being screwed up where it switches axis causing your touch to register in completely the wrong place. Fromn the comments of the android engineer it makes it seem that the sensor hardware is just like that, cheap and low quality.
Link to discussion: http://groups.google.com/group/andr...read/thread/d0aa3eea8fd9a2b8/9a8ea81133866460
Click to expand...
Click to collapse
I know, I have seen all these videos and attempted to re-create many times to test I have never seen this issue once.
Don't get me wrong I can understand it being a mare of you are having it, but I just dont ever see it.
after trolling the Google thread, it seems to me there are several scenarios everyone is lumping into "screen issues" and it's going to be hard to pin it down to one source
Mine happens (touch registers on the wrong part of the screen) when I am using certain apps (Ringdroid, Browser mostly) - a couple of things clears it up ; press the sleep button, kill all tasks if you have an app for it, or change to landscape mode. For other people it's the soft keys and/or much worse. Since mine clears up with a specific action, I tend to think it is software related.
With mine it used randomly to happen but only in the Launcher (never again since 36B). I couldn't point anywhere but if I selected any app with the trackball and opend ist everything worked fine again, also the keyboard on the launcher worked well. For me it seems that it has something to do with the launcher.
Hi folks.....,
Anyhow, I have several questions for y'all about the phone. I was wondering, can anything be done about the pink hue in camera shots? I've noticed that in some pictures, it's not so evident, but in others, it's clear as day. Is there a trick to this? I know that changing phones don't really work as it seems to be something to do with the tech of the camera itself + the housing of the lens or something.
Also, since this is my first time using WM 6.5, is it normal for the Start menu, to segment in terms of scrolling? Like, instead of a smooth drop all the way to the bottom, it goes in "pages" almost, if this makes any sense. Also, is there a trick to using capacitive screens? Whenever I try to use my fingertip to scroll, sometimes it registers, sometimes it half-registers. Is angle an issue here? Do you get better with this over time?
I'm running stock ROM right now, with a yellow-reset button if that matters, with 2.13. Having said that, what are some of the common things I can check for in terms of manufacturer's defects, etc? I want to try avoiding flashing until I've checked for these common issues first to save me the hassle of flashing back again, etc.
Thanks everyone! But boy...the phone is snappy.
PoisonWolf said:
Hi folks.....,
Anyhow, I have several questions for y'all about the phone. I was wondering, can anything be done about the pink hue in camera shots? I've noticed that in some pictures, it's not so evident, but in others, it's clear as day. Is there a trick to this? I know that changing phones don't really work as it seems to be something to do with the tech of the camera itself + the housing of the lens or something.
Also, since this is my first time using WM 6.5, is it normal for the Start menu, to segment in terms of scrolling? Like, instead of a smooth drop all the way to the bottom, it goes in "pages" almost, if this makes any sense. Also, is there a trick to using capacitive screens? Whenever I try to use my fingertip to scroll, sometimes it registers, sometimes it half-registers. Is angle an issue here? Do you get better with this over time?
I'm running stock ROM right now, with a yellow-reset button if that matters, with 2.13. Having said that, what are some of the common things I can check for in terms of manufacturer's defects, etc? I want to try avoiding flashing until I've checked for these common issues first to save me the hassle of flashing back again, etc.
Thanks everyone! But boy...the phone is snappy.
Click to expand...
Click to collapse
I can't answer your question about the pink hue. I haven't noticed it in my pictures, yet.
Yes, the page scrolling in the start menu screen is by design. It's so you don't go way farther down than you wanted to. I think it's retarded.
The touch issues you are describing could be for two different reasons.
1st, I hope you aren't using your fingernail? A capacitive screen requires skin contact.
2nd, the 2.13 ROM has serious touch sensitivity issues. There is a sticky in the "T-Mobile USA HD2 General" forum up top that gives you a .cab to install that fixes the registry for much more responsive touch scrolling.
Since you posted this in that same forum, I'm sure you will see it up there!
Thanks for the reply. I actually tried the cab above by zim or something, and it made my touch scrolling so much worse in SPB Mobile Shell. So I don't know what's going on.
Anyhow, I spoke with a T-Mobile rep, and we went through the usual rigmarole, and he told me since I can't get rid of the pink hue, I should just go back and get an exchange. Anyone think I should do this? Or are all units likely to have this problem? How many HD2 users here do not have this problem for the T-Mobile HD2 version?
A good number of the units have the "pink hue" problem. You can see several videos people have made on YouTube about this.
I have a bit of it as well.
My contention...live with it because it seems as though you have about a 50/50 chance of getting another unit with the same problem.
Camusa said:
A good number of the units have the "pink hue" problem. You can see several videos people have made on YouTube about this.
I have a bit of it as well.
My contention...live with it because it seems as though you have about a 50/50 chance of getting another unit with the same problem.
Click to expand...
Click to collapse
Is it normal to see the pink hue even through the screen though? Like, you start up the camera, even just at looking at the screen, I can see the pinkness in the center already. Is this normal?
That's my worry too. Everything else with the phone works so far. No dead pixels, no manufacturer's defects in the physical case....my worry is that by exchanging, I'm increasing the risk of obtaining one of these other problems.
Edit: Also, I have to mention that the pink hue is without flash.
PoisonWolf said:
Is it normal to see the pink hue even through the screen though? Like, you start up the camera, even just at looking at the screen, I can see the pinkness in the center already. Is this normal?
That's my worry too. Everything else with the phone works so far. No dead pixels, no manufacturer's defects in the physical case....my worry is that by exchanging, I'm increasing the risk of obtaining one of these other problems.
Edit: Also, I have to mention that the pink hue is without flash.
Click to expand...
Click to collapse
Mine...on occasion it does have the pink tint but when I take the picture it is not there. People said to try to take a picture of a blank piece of white paper and see what it looks like. I tried with my phone and it looked white and my friend tried it with his iphone 3gs and it was fine as well. I read somewhere about it being an issue with a number of cameras not only the HD2. That being said a lot of people have including myself have taken really good pictures without a hint of pink?!?!
toreone said:
Mine...on occasion it does have the pink tint but when I take the picture it is not there. People said to try to take a picture of a blank piece of white paper and see what it looks like. I tried with my phone and it looked white and my friend tried it with his iphone 3gs and it was fine as well. I read somewhere about it being an issue with a number of cameras not only the HD2. That being said a lot of people have including myself have taken really good pictures without a hint of pink?!?!
Click to expand...
Click to collapse
Flash, no flash?
Indoors or outdoors?
White balance set to auto?
Brightness settings?
whenever I try to use my fingertip to scroll, sometimes it registers, sometimes it half-registers.
Click to expand...
Click to collapse
don't use your finger tip, use the pad. the conductance of the tip is lower than the pad. my left index finger simply won't work at all!
samsamuel said:
don't use your finger tip, use the pad. the conductance of the tip is lower than the pad. my left index finger simply won't work at all!
Click to expand...
Click to collapse
Yeah, I figured as much now. I realize when I use the pad of my thumb and scroll, it's so orgasmic and makes me jizz in my pants. And to see the scrolling without the icons being rendered as you go is.....just ....how it was supposed to be.
Funny enough though, I can't seem to hit the corners as easily. This is apparently evident when for example, you're in the Phone settings, and you have the two arrow keys on the bottom right. It's almost impossible for me to use my right thumb without hitting 10 times while my left-thumb needs about 2 ~ 3 tries. The screen seems to register the touch at the center of my thumb-pad, so to speak. Is this normal? Or does it just register the area of the thumb that gives off the most "signal", so to speak?
PoisonWolf said:
Thanks for the reply. I actually tried the cab above by zim or something, and it made my touch scrolling so much worse in SPB Mobile Shell. So I don't know what's going on.
Anyhow, I spoke with a T-Mobile rep, and we went through the usual rigmarole, and he told me since I can't get rid of the pink hue, I should just go back and get an exchange. Anyone think I should do this? Or are all units likely to have this problem? How many HD2 users here do not have this problem for the T-Mobile HD2 version?
Click to expand...
Click to collapse
The pink spot was addressed by an HTC-issued patch for the euro Leo, which is still available on the HTC support/updates site for that model. But, the patch states that it's for builds prior to the ones used in the Tmo models, so I don't know that it will make a difference, but you're welcome to try it. I think the same tweak is available in all the HD2 tweaks listed in the sticky on the main page...in the list of all the "touch-x" cabs smaberg posted, there's one there for the "camera fix", I believe that's the same thing.
I haven't noticed the pink spot on my HD2 at all, and I did a test or two with a white paper...but I honestly don't remember what lighting I used. If I were you, I'd just test it several ways (indoors/outdoors/flash/no flash) and compare the results.
sirphunkee said:
The pink spot was addressed by an HTC-issued patch for the euro Leo, which is still available on the HTC support/updates site for that model. But, the patch states that it's for builds prior to the ones used in the Tmo models, so I don't know that it will make a difference, but you're welcome to try it. I think the same tweak is available in all the HD2 tweaks listed in the sticky on the main page...in the list of all the "touch-x" cabs smaberg posted, there's one there for the "camera fix", I believe that's the same thing.
I haven't noticed the pink spot on my HD2 at all, and I did a test or two with a white paper...but I honestly don't remember what lighting I used. If I were you, I'd just test it several ways (indoors/outdoors/flash/no flash) and compare the results.
Click to expand...
Click to collapse
It's much more prevalent in indoor shots without flash. For outdoor shots, it's hard to notice it, but the farther you go away from the picture, the more noticeable the pink blur is. The radius of the pinkness get larger as the darker the ambient surround gets, at least for me.
Im still debating whether it is worth the hassle to argue for a brand new one, knowing that the reps might be reluctant to shell out a brand new HD2 over what they'd probably deem as a "minor" discoloration or something.
i noticed the pink hue on my hd it started after i had the screen replaced and then added copilot i beleive its from where the video driver has an issuse and it maybe to where u hav to get the device replaced dude if u hav a custom rom try task 29 and then add a new different rom so that the rom is fresh on the device now so far on my hd2 i see no pink hue but i hav one of the first genration of tmous-hd2 i ordered it the first day,,, hope info helped
wingtytn said:
i noticed the pink hue on my hd it started after i had the screen replaced and then added copilot i beleive its from where the video driver has an issuse and it maybe to where u hav to get the device replaced dude if u hav a custom rom try task 29 and then add a new different rom so that the rom is fresh on the device now so far on my hd2 i see no pink hue but i hav one of the first genration of tmous-hd2 i ordered it the first day,,, hope info helped
Click to expand...
Click to collapse
Hmm, but I've read online it's more to do with the low-quality of the camera parts and nothing to do with software really. Seems like a hit or miss really. Still fidgeting at this point whether to get it replaced or not since everything else works perfectly.
Anyhow, running SPB Mobile Shell on this monster results in 0 lags/freezes.
PoisonWolf said:
Hmm, but I've read online it's more to do with the low-quality of the camera parts and nothing to do with software really. Seems like a hit or miss really. Still fidgeting at this point whether to get it replaced or not since everything else works perfectly.
Anyhow, running SPB Mobile Shell on this monster results in 0 lags/freezes.
Click to expand...
Click to collapse
Yeah, my understanding is that the root of that issue is hardware based...the fix that was released was just an attempt to improve the way the software tries to compensate for that. But yes the only way to 100% eliminate it is to use higher-quality (and therefore bulkier) hardware components, at least from the references I've read on the topic.
sirphunkee said:
Yeah, my understanding is that the root of that issue is hardware based...the fix that was released was just an attempt to improve the way the software tries to compensate for that. But yes the only way to 100% eliminate it is to use higher-quality (and therefore bulkier) hardware components, at least from the references I've read on the topic.
Click to expand...
Click to collapse
What would you do Phunkee? Live with it or try your luck for a new phone?
Also, does anyone know if enabling Wireless N increases your drain when using Wi-Fi? And if you'll see a speed increase on Wireless G networks? And does enabling Wireless N count as "voiding" the phone's warranty?
PoisonWolf said:
What would you do Phunkee? Live with it or try your luck for a new phone?
Also, does anyone know if enabling Wireless N increases your drain when using Wi-Fi? And if you'll see a speed increase on Wireless G networks? And does enabling Wireless N count as "voiding" the phone's warranty?
Click to expand...
Click to collapse
If it's noticibile enough in your own pictures that it bothers you, I'd only try for a replacement phone if they can guarantee you a new one instead of a refurb (might want to take it into a store). I still can't seem to recreate the issue for sure, at least in any pictures where coloring isn't already kooky overall because of lighting irregularities.
Keep in mind too that it looks like new/replacement units are now being shipped with the 2.13 ROM from the factory, so also decide if that matters to you or not.
EDIT: I don't know about the wifi-N drain or performance improvements...I have it enabled on mine but my work and home networks are still G-only. I'm 99.8% sure though that it does NOT void your warranty to enable that.
1. There is a CAB file for the pink spots, have you tried it on your model?
2. Wireless "N" seemed to drain my power more also. And no it will not void your warranty because after a hard reset it will turn the registry tweak off. Hard Reset brings everyting back to stock except for your call timers. (unless you HPSL'd your phone).
Thanks for the suggestions so far guys. Right now, I've noticed that outdoor shots, it's hardly noticeable on the computer, so I think I'm likely to just stick with this phone. Everything runs great after all.
Anyhow, I wanted to ask, how do you guys use your screens? Do you use the base of your thumb? I can't for the life of me get scrolling to work when I use the tip of my forefinger. Not my nail, just even towards the tip, it's choppy. I test it out on the Notes program and I try to do a flick and I can understand why. Instead of a single vertical line being drawn, it's being split into 3 ~ 4 smaller lines, as though the screen is not able to register the touch continuously. Is this something to do with my personal body charge and how my finger is shaped? I only ask because I've used an iPod Touch before and I was able to scroll just fine with my finger tip. Is there anyway to improve the sensitivity even further?
PoisonWolf said:
Thanks for the suggestions so far guys. Right now, I've noticed that outdoor shots, it's hardly noticeable on the computer, so I think I'm likely to just stick with this phone. Everything runs great after all.
Anyhow, I wanted to ask, how do you guys use your screens? Do you use the base of your thumb? I can't for the life of me get scrolling to work when I use the tip of my forefinger. Not my nail, just even towards the tip, it's choppy. I test it out on the Notes program and I try to do a flick and I can understand why. Instead of a single vertical line being drawn, it's being split into 3 ~ 4 smaller lines, as though the screen is not able to register the touch continuously. Is this something to do with my personal body charge and how my finger is shaped? I only ask because I've used an iPod Touch before and I was able to scroll just fine with my finger tip. Is there anyway to improve the sensitivity even further?
Click to expand...
Click to collapse
There has been some sensitivity issues with 2.13; not saying that's it but a good place to start looking. There are also some registry tweaks for the flicking of your finger (how far it flips up/down). I don't have the exact link, but a quick search will get you in the right place. I personally use the end of my index fingers, thumbs, whatever finger is closest to the key I'm looking for.
PoisonWolf said:
Hi folks.....,
Anyhow, I have several questions for y'all about the phone. I was wondering, can anything be done about the pink hue in camera shots? I've noticed that in some pictures, it's not so evident, but in others, it's clear as day. Is there a trick to this? I know that changing phones don't really work as it seems to be something to do with the tech of the camera itself + the housing of the lens or something.
Also, since this is my first time using WM 6.5, is it normal for the Start menu, to segment in terms of scrolling? Like, instead of a smooth drop all the way to the bottom, it goes in "pages" almost, if this makes any sense. Also, is there a trick to using capacitive screens? Whenever I try to use my fingertip to scroll, sometimes it registers, sometimes it half-registers. Is angle an issue here? Do you get better with this over time?
I'm running stock ROM right now, with a yellow-reset button if that matters, with 2.13. Having said that, what are some of the common things I can check for in terms of manufacturer's defects, etc? I want to try avoiding flashing until I've checked for these common issues first to save me the hassle of flashing back again, etc.
Thanks everyone! But boy...the phone is snappy.
Click to expand...
Click to collapse
by pages I wonder if you are describing lagging. Lagging should not be normal. I suggest you notate how much free ram you have and how your program screen behaves (smooth or laggy)by going to >start menu>settings>system memory. After, run clean ram and repeat the above mentioned steps. You should have more memory and a smoother user interface.
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.