Related
I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?
Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.
It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.
It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).
Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!
Most probably replaced the phone's MB.
Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...
I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.
The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.
Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App
Does upgrading the HBOOT help with the wonky touchscreen heat-related miscalibration issues that every Nexus owner knows about?
I raised this question on a different thread:
http://forum.xda-developers.com/showthread.php?t=903975&page=9
but wanted to throw this question out to a larger audience.
This week I finally got tired of having intermittent but definitive touchscreen miscalibrations, usually associated with charging and/or heavy usage. HTC shipped a swap for me to use.
The new one works pretty well, except the camera takes pinkish tinged images, so it unfortunately will be going back. However, I noticed that the HBOOT is the newer 0.35.0017 (though the date displayed by the bootloader screen is Jun 14, 2010).
So I upgraded the HBOOT on my original N1, and have been trying hard to reproduce the touchscreen craziness. So far I've been unable to do it.
It's difficult for me to make it happen on demand. I "stress tested" it essentially by doing the things that normally bring it on, GPS with charger, and graphics intensive games. But I'm getting really tired of beating angry birds again and again =P
So, if you're still experiencing touchscreen wonkiness that is fixed by turning on and off the screen, which HBOOT do you have?
There are of course many other potential mitigating factors I've thought about. Custom ROMS. Kernels. Touchscreen protector. Radio version.
Just for completeness, there are different part numbers on the two:
Original N1 part # 99hke002-00 F
Replacement N1 part # 99hke002-01
Who knows what the significance of that is.
No it doesn't.
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
You know, as strange as it sounds, since I upgraded to the 0.35 HBOOT about a month ago, I have had zero issue with the digitizer. Call it coincidence, but that is what's happening so far.
We will call it coincidence for now =)
A happy coincidence.
waylo said:
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
Click to expand...
Click to collapse
Not very often, in fact think it hadn't done it over the past week. I've been using the crap out of it customizing CM7 over this weekend and no hiccups.
our touch screen is always a hardware problem..
That's not the question. The question is if you're still having a lot of problems with your touch screen, which hboot do you have?
I was actually kinda wondering the same thing. I finally got around to putting on CM7 (build 39) on Friday (coming from CM 6.1). I right away had the impression that the screen was more responsive (the notification drop-down bar tipped me off) and I have not had a single episode of wonkiness with the screen since. CM 6.1 was a little weird for me and I had screen issues (especially the drop-down).
Oh well, even if it isn't the HBOOT, something has changed for the better for now
Another thing I learned recently is that on the native google navigation app, there seems to be a touchscreen dead zone directly vertical in the center of the screen (in landscape mode at least). It basically corresponds to the current street you're on if your navigation is active and your path is straight ahead.
So if you touch there and try to shift the screen around, you might mistakenly think the whole screen is awry. I think this is by design.
I'm not sure why it's there but it reliably is unresponsive to drags. So I'm not using that center area to gauge if my screens gone wonky.
Now if you hit the menu button, the buttons centrally do respond to taps.
Just had my first case of misregistering digitizer in a while. But instead of the whole bottom 1/3 of the screen going stupid it was just the bottom right corner, around the enter button/backspace if you have a portrait keyboard.
Oh well, it still works better than stock eclair!
So just as an update, the HBOOT definitely does not rid the digitizer issues plaguing everyone. It seems actually that my kernel had more of say in when/how often the issue surfaces.
I found that on Enom's Froyo ROM, problems arose more often with stock Enom than Pershoot or Wildmonks. However, each kernel has its own benefits.
I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."
I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!
Is there an FAQ about this digitizer issue?
JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me
Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733
JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.
Part of my m7 touch screen isnt working .. its kinda crazy cuz the phone never got dropped .. i saw that many people had that problem its between this two parts of screen that doesnt work theres a line that working..sometimes the touch isnt working at all !!
(when people call me sometimes).
its really disappointing cuz i like htc very much !
another problem that im having and saw that many people has it too : screen brightness always go maximum ! auto off for sure but still the brightness making problem tryed to reset the phone didnt help( not hard reset) it sucks to have a bunch of problems in a new phone ..
please please help me !
post.img.org/image/6naksobvx/
delete the dot in postimage ! sorry but this photo will help you understand and i have to share it !
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Val D. said:
Areas of the screen not registering touch input in most cases is a hardware issue with the digitizer. Loose digitizer connector may cause similar issues, but the only way to check is to open the phone. Opening is not easy and there is a high risk to damage the body. If you decide to go this way, my suggestion is to get new front and back panels + screen kit and to transplant the rest into the new housing. It's also a good time to replace a worn battery or a faulty camera module.
Click to expand...
Click to collapse
some times the screen back to full funcanlity
and please help about the other problem with the brightness .. its look like one of the sensors is broken in the phone .. maybe its the problem ?
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Val D. said:
When Auto Brightness is set to Off, the phone is not using the light sensor.
You'll have better chance to get help if you provide some basic information about your phone:
- What OS version? (KK, LP, stock, custom)
- Was the phone factory reset after the last OS update? (highly recommended)
- Do you use any applications that control screen brightness? (like some picture viewers, barcode display apps, etc.)
You may fix the brightness issue (most likely software related), but non working digitizer on parts of the screen is hardware related and no app will fix this.
Click to expand...
Click to collapse
lollipop not root and other .. i deleted everything , did a soft reset not the hard type . no but i download lux to see if its help and it doesnt help either
The only thing left to try on a software side is factory reset the device. Many users report it clears various OTA Lollipop update bugs. The process takes about 10-15min, the OS will go through Android system update process again and the device will be reset to factory default state (don't forget to backup all your data). During the initial setup process don't restore your online account backup, make clean setup. Test the screen and digitizer before installing any 3rd party apps. Make sure your screen protector (if you have one) is not bugging the digitizer. If you have the same issues, then it's definitely hardware related (screen/digitizer assembly or connecting ribbon cables).
****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine
Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
anyone ?
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.