When i turn on my Nexus One from a cold boot, the touch controls goes crazy. i cant even type on the keyboard because the device registers other keys and not the one Im actually touching but when i press the power button to put the device to sleep then immediately turn it back on again the problem is gone. Does anybody know if this is a software or hardware problem and is there a solution or should i just get a replacement phone?
Device: Nexus One
Carrier: ATT
Country / Language: English
OS / Browser / build number (if applicable): Android 2.1
I'm dropping in to let you know that we are still investigating the problems some of you are having with the touchscreen. Getting to the root of a problem like this can be very difficult because there are a variety of things that could be the potential cause.
Some of you may have seen the touchscreen behaving strangely because of the way you are holding the phone. Please make sure you aren't touching the screen in two places when gripping the phone. If you are trying to register a touch and another part of your hand (or your sleeve even) is also touching the screen it won't work!
If this turns out to be a software issue, we will attempt a fix via an OTA update. For now, completely turn off your Nexus One and then power it up. This typically stops any strange touchscreen behavior.
Lastly, a small percentage of you probably have hardware issues. This is likely the case if entire areas of your screen have become permanently unresponsive. In this case, view the warranty details in our Help Center and contact HTC for support.
Thanks for your continued patience as we work to sort this out, it is hugely appreciated!
I'm having similar issues with my capacitive screen. After about 30 minutes to an hour of use, taps start not registering or registering taps below where I actually tap. Examples:
Tapping in the middle of the screen and feeling haptic feedback from the soft keys
Tapping towards the top of the screen and registering taps at the bottom of the screen (easy to see on the Nexus live wallpaper)
Tapping an icon and winding up at the wall of icon menu screen because the tap was registered at the bottom instead of where the icon was tapped.
Like you, I have no idea if this is a hardware or software issue. I have great confidence in HTC but this clearly does not seem normal what I have going on. I have a 1G iPod Touch and never experienced a single issue of this type with that capacitive screen. As far as I am aware there is no screen calibration needed on the capacitive screens that was needed on the resistive-type touchscreens.
Device: Nexus One
Carrier: ATT Country / Language: English OS / Browser / build number (if applicable): Android 2.1
This is exactly the issue that Im having. Im glad that Im not alone but not so much that we are actually experiencing this problem. I have already emailed HTC regarding this. I'll post there response once i get it.
I hope anybody who has the same problem would leave a post here so we could get an idea how are affected by this.
I have the same issues at time and as the OP said a turn off of the screen and turn back on fixes it. My motocliq used to do this and they released a software update that addressed it somewhat. It's software related and I'm sure they will release a patch.
Thank you S.Puma, i was hoping that this was a software issue. I did not want to get a replacement, the last time i did this with my iPhone i got an even worse one the than the one i had.
Ya like I said, when the motocliq came out, the touchscreen was out of whack all the time, an update resolved most of the issues but there will still some problems (over-sensitive when scrolling, etc.) I hope that when this is fixed, they also release a calibration tool.
I'm having a similar issue. At first it was limited to the lowest part of the screen (about a finger's width above the soft keys) so I thought it was a software issue related to the larger screen size, but just now I couldn't turn the phone off because taps on "Power off" were registered as taps on "Airplane mode" or on the soft keys.
Not exactly sure how the touchscreen works but sometimes I don't even touch it and the app opens. I just get my finger close and it goes. Other times I have to tap near the top edge of an icon to get it to recognize the tap. Is there a way to adjust touch sensitivity?
These all sound like similar issues. The one reason I believe it is software is the fact that it does not do this 100% of the time. If I power down and back off things operate as you would expect for a while. Once it starts getting off track though, it is maddening. If it was strictly a hardware problem I have to believe that it would be going on all the time. I am going to call HTC next week to discuss. I don't want to return this but I need some answers within the 14 day return window. Hopefully someone is aware of this and working on a fix already. It is clearly not just my unit. If there are others, please post more replies here.
I have the exact same problem. I'm finding it all a bit glitchy at the moment. Kinda disappointed. Guess I'm just too used to my iPod touch's easy of use and rare glitching.
After about 20/30 mins of messin about, I couldn't type anything on the internet because it kept thinking I was touching the voice input key or a few keys below. Putting it in landscape mode seemed to kind of sort it out, but it's not really acceptable. The amount of problems people are having on here is ridiculous and hopefully they will get sorted soon.
Same here, was on a confrence call this morning and tried to houth the mute softkey, the phone kept registering a DTMF tone and showing I had clicked the #5 on the keypad.
Capacitive screens can get weird if your skin gets too dry. When my Nexus One gets weird I apply some GoldBond Ultimate hand sanitizer/moisturizer and it immediately works better.
No offense but if it were just a dry skin issue it wouldn't be fine for 30 minutes and then get out of whack. Now I see another thread or two on the same topic. Its a widespread issue apparently.
I started one of the other threads.....someone else with the same issue noticed if you don't touch the metal strip on the back or the contacts on the bottom of the phone this can help the issue...REALLY hoping this is just a software issue but i'm not so sure. What I do know is that its SO annoying that I don't know about the rest of you but I've had to revert back to my old handset until someone tells us what's going on.
Has anyone yet managed to get hold of Google or HTC to find out more? I have contact Google but no reply yet, and I tried to contact the HTC support number (in the UK) but just get an answerphone!
Having issues with the touchscreen also, sometimes not touching the metal ring of the camera helps but it is not reliable. I am starting to think this may be related to the proximity sensors on the phone, it seems to work better if I hold it without having any part of my hand over the sensors. (sensors are located near the power button on the face of the phone)
I too have found that using the power button to sleep the screen then turn it back on "fixes" the problem for awhile; sometimes it'll go for a long time working correctly, others it'll happen quite frequently. I see the mis-clicks and offball scrolling stutters when flicking in Market, Browser and on the homescreens a lot... right now I've tried disabling haptic feedback to see if that helps alleviate the issue. No definitive results yet.
I'm having issues with the touchscreen too. When I try touch the "type to compose" box, nothing happens. Sometimes when I touch "go" or "next" when typing text into web page text fields, either nothing happens, or it will take me to a random page in my browser history.
Same issue here... It gets to the point where answering calls becomes a chore. Hopefully it is software related and we get some sort of a patch soon or this baby is going right back where it came from. Don't want to do that though..
I'm also seeing a similar issue. I feel like the phone is busy doing something else and not handling the screen input events or holding on to the previous input
@sleepyg -- I feel the same, I've been experimenting with killing tasks to try and find if it's one app/process or another, but nothing so far is seeming to help.
I have the same kind of problem. it only seems to happen after I surf the web for a while and then all of a sudden it thinks i'm pressing about a half inch below where i'm actually pressing the only thing that works accurately when it happens is the track ball. It gets so bad that you can't even turn the phone off because you can't tap on the power off button (have to use the track ball to press it). Some times it corrects its self if i kill all the tasks, but only some times works...I hope they correct this or at least acknowledge that it's an issue and they're looking into it or else many phones will be returned
As I already posted in this thread, I am having the same problem.
But guys just FYI, you can quickly resolve the problem by turning off the screen for a second (using the button at the top) and turning it back on.
As someone else posted there was a similar issue with the CLIQ that was fixed (for the most part via a software update). Hopefully, the issue is acknowledged soon and a fix is underway.
The first day I had the phone, the screen was working perfectly. Now that I am on day 2, this bug has become a problem. Sometimes when I tap in the middle of the screen (no where near the buttons at the bottom) I'll get haptic feedback and a menu will pop up. It seems to be happening with increasing frequency. It is beginning to interfere with my ability to control the phone. When the glitch happens, no matter where I press, it thinks that I am either holding down the home button, or the menu button, preventing me from accessing anything else on the screen. I can fix it temporarily by changing the orientation of the screen, but it is pretty annoying.
I am having touchscreen and keyboard sensitivity/accuracy issues. Soft reset has helped, but issue returns shortly thereafter. Hopefully a software patch will resolve this issue.
If the proximity sensors were in fact the issue it would make typing in landscape entirely impossible. It definately sounds software based as per the update on the CLIQ (but there were a lot of software issues with that phone).
We can't rule out the possibility of hardware however. Like a mic that is slowly going out. Capacitive touchscreens pick up the natural flow of electricity from your body, which is how the screen picks up your finger placement. Thus the unnecessary need for a screen calibration (in perfect cirumstances).
If it is in fact a software based issue the best thing that can be done is a master reset. Past that reloading the stock 2.1 software. This can be found on code.google.com. If you don't know what you're doing and break your phone it's your own responsibility though. The thing to remember is that this doesn't occur on a lot of N!'s, so reseting/reloading the software may remedy the issue.
The last thing to keep in mind are simply a few basics. The use of docks, bio-gloves etc inhibit the propper flow of natural electricity and is known to cause issues with non recognition or incorrect recognition (widely reported as an issue with the Sapphire build). This may apply to a few of the above posts, but I don't believe this is the widespread culprit here.
My mistake, I mixed up the two locations, many of the older system releases can be found there, but it doesn't appear to have much fo 2.1 as of yet. You can however refer to this post on xda-developers for a few locations to obtain the files. There are a few ways to flash these files. Refer to the HTC developer site for instructions on each method.
The touch screen is virtually useless for the navigation keys at the bottom. I have to hit them 3+ sometimes. I'm quite used to touch screens because I have an ipod touch. It seems to work better when I use my thumb instead of a finger. I hope this is a software issue and they push a patch out this week otherwise I am returning the phone. Also, pulling the notifications down from the top doesn't work all the time. I would say the biggest problem is the navigation keys though which I think we all agree is pretty important.
I have the same issue. It happens many times over the day that the touch point is recognized at a totally different position or even as a on of the bottom soft key buttons. Very annoying!
I have the same problem. I'm surprised you guys are noticing it too. After using the phone for about 30 minutes the keys stop responding and the icons can't be executed. I check the processes running, and there isn't anything other than the standard boot stuff. This is going to be a problem if I have to use this phone in an emergency.
I have been experiencing the same issue with the touch screen where the touch screen appears to be off and key presses are not directed at the target key. I've turned off the phone, powered it back on and everything appears to be working okay after.
Device: Nexus One Service Provider: Tmobile
Service Area/Country: Fort Worth, TX U.S.A.
OS / Browser / build number: Android 2.1
Data Plan: T-Mobile Android Unlimited Web + 400 Messages
I have a potential explanation. We're having a bit of a cold snap here in DC (low 20s F), and as I was walking out side, I noticed that my touch screen was nearly unusable Everywhere I touched either the home button menu would pop up, or a window would pop up asking for voice input (two of the functions of the bottom, permanent keys). I would rotate the keyboard to horizontal and back to vertical, which would fix it for about 5 seconds before the error returned. Once I got back inside and the phone (and me) had a chance to warm up a bit, everything was back to normal. Anyone willing to do an experiment and see if they get this error more frequently when the phone is cold?
I'm having same issues with 70F. It doesn't seem like it's a temperature issue. It's gotta be the issue with the screen driver. It get's so bad that it crashes apps from time to time. I was swiping through the screen about 100px above the "touch buttons". from the logs you can see that it registered as HOME event, and then "search" event (it tried to bring up the keyboard). GOOGLE, HELP US OUT!!!
01-10 22:35:25.388 W/webview (18233): Miss a drag as we are waiting for WebCore's response for touch down. 01-10 22:35:26.708 I/WindowManager( 67): Ignoring HOME; event canceled. 01-10 22:35:26.878 W/webview (18233): Miss a drag as we are waiting for WebCore's response for touch down. 01-10 22:35:29.538 W/KeyCharacterMap(18233): No keyboard for id 65540 01-10 22:35:29.538 W/KeyCharacterMap(18233): Using default keymap: /system/usr/keychars/qwerty.kcm.bin 01-10 22:35:30.138 I/FieldContext( 5394): Bundle = Bundle[{imeOptions=0, hint=, label=, fieldName=, fieldId=-1, packageName=com.rhythmnewmedia.discovery, inputType=0}] 01-10 22:35:30.188 I/FieldContext( 5394): Bundle = Bundle[{imeOptions=0, hint=, label=, fieldName=, fieldId=-1, packageName=com.rhythmnewmedia.discovery, inputType=0}] 01-10 22:35:30.208 D/AndroidRuntime(18233): Shutting down VM 01-10 22:35:30.208 W/dalvikvm(18233): threadid=3: thread exiting with uncaught exception (group=0x4001b178) 01-10 22:35:30.208 E/AndroidRuntime(18233): Uncaught handler: thread main exiting due to uncaught exception 01-10 22:35:30.218 E/AndroidRuntime(18233): java.lang.IllegalArgumentException: parameter must be a descendant of this view 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.view.ViewGroup.offsetRectBetweenParentAndChild(ViewGroup.java:2518) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.view.ViewGroup.offsetDescendantRectToMyCoords(ViewGroup.java:2455) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.view.ViewRoot.scrollToRectOrFocus(ViewRoot.java:1449) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.view.ViewRoot.draw(ViewRoot.java:1191) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.view.ViewRoot.performTraversals(ViewRoot.java:1114) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.view.ViewRoot.handleMessage(ViewRoot.java:1633) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.os.Handler.dispatchMessage(Handler.java:99) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.os.Looper.loop(Looper.java:123) 01-10 22:35:30.218 E/AndroidRuntime(18233): at android.app.ActivityThread.main(ActivityThread.java:4363) 01-10 22:35:30.218 E/AndroidRuntime(18233): at java.lang.reflect.Method.invokeNative(Native Method) 01-10 22:35:30.218 E/AndroidRuntime(18233): at java.lang.reflect.Method.invoke(Method.java:521) 01-10 22:35:30.218 E/AndroidRuntime(18233): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860) 01-10 22:35:30.218 E/AndroidRuntime(18233): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618) 01-10 22:35:30.218 E/AndroidRuntime(18233): at dalvik.system.NativeStart.main(Native Method) 01-10 22:35:30.218 I/Process ( 67): Sending signal. PID: 18233 SIG: 3
Feed
Touch Screen Problem - Hardware of Software Issue?
