Related
Im sure a fair number of you will have experienced the same thing where you press a key once and you get like 3 of that letter and sometimes for me the Fn key doesnt work too well either
i've tried like swirling the keys around to move dust etc but it didnt help
maybe i should just send it back? becuase its really annoying
I also have this problem sometimes. Thought it might be a software problem or so, but maybe you are right and particles are collecting there.
Did someone try that on X1?
Well, if there was such a solution I wouldn't have to send my X1 to the service centre. And just delaying it as much as possible, but given that my warranty ends next week, I'd probably have to go down soon. And anyway, it's not just repeats that I'm facing. Sometimes it's the other way round, as in the keyboard not responding unless I press the key down real hard.
Mopral said:
Did someone try that on X1?
Click to expand...
Click to collapse
just tried, and seems to work! thanks
settings-personal-buttons-up/down control
delay before first repeat set to long
repeat rate 3 from fast
works good!
I'd say it works about 80-90%. It does save the X1 from the trash piles, so kudos to the friendly guy who dug up the solution, and no kudos to SE and/or MS who can't think of fine-tuning the keyboard settings before they ship a product that was $800-900 unlocked at launch.
Caveat and an inappropriate rant: I remember doing so much research, and everyone across so many different forums said a hardware keyboard is the way to go if you do a lot of texting. Not true. I find that hardware keyboards require a lot of efforts to press compared to a virtual keyboard, even worse if it's not spaciously laid out, and even worse if, unlike the X1, the positioning of the keys relative to each other is off.
Truth is I type even faster on an iPhone/ipod touch than an X1, without feeling like an RSI is coming on, and it's not because of predictive text entry. It's because my thumbs can use a lot less force on the keys. I believe most people still press way too hard on a touch screen trying to be control freaks.
So the keyboard may be 80-90% improved, but I've got my budget ready for an iPhone. And no more listening, no more being open to suggestions!
beingthere said:
Caveat and an inappropriate rant: I remember doing so much research, and everyone across so many different forums said a hardware keyboard is the way to go if you do a lot of texting. Not true. I find that hardware keyboards require a lot of efforts to press compared to a virtual keyboard, even worse if it's not spaciously laid out, and even worse if, unlike the X1, the positioning of the keys relative to each other is off.
Click to expand...
Click to collapse
Well, I don't want to live without h/w keyboard anymore. And I did a fast typing challenge against an iPhone and won. The guy who wrote on that iPhone was a real freak, had an iPhone since it came out and types really fast...but I love the h/w keyboard on the xperia. If it would not have this double-letter error I would love it even more...Now I'm going to fix it with the solution mentioned above. Thanks!
I just want to add one thing...
The reason I say the fix is 80-90%, is because I think CPU speed and/or power settings might contribute somewhat to the keyboard issue. Once last week, I had the phone plugged into AC, and the keyboard suddenly became free of issues, and responded properly to my typical typing efforts.
Using nueCPL-ClockSpeed v1.3 in an unscientific test, the keyboard produces more mistakes on a lower speed (384MHz), but its Max Performance setting didn't exactly reproduce the AC power remedy.
This is not a very stringent observation at all, but since I am stuck with the X1 for a while, I'll keep on trying I'm betting that the next iPhone will be a significant update, so I have to hold off the purchase for now... and kiss NRGZ28's toes for his rom's.
Sapa13 said:
just tried, and seems to work! thanks
settings-personal-buttons-up/down control
delay before first repeat set to long
repeat rate 3 from fast
works good!
Click to expand...
Click to collapse
for two days, since i set this way, not even one double or missed letter!
i've done everything you've all said but it doesnt work does that mean it is a physical problem?
comeradealexi said:
i've done everything you've all said but it doesnt work does that mean it is a physical problem?
Click to expand...
Click to collapse
really dont know, since i set that way no problem at all.. maybe dirt came under your keyboard
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
I've never had a problem with mine.
I saw a review saying that they got in the way when typing w/ the onscreen keyboard, but I haven't even had that, and I'd like to think that I have pretty normal-sized fingers.
Some people have problems, others don't i personally haven't. I wouldn't consider it to be something important enough to sway me from a sale though.
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
Click to expand...
Click to collapse
Definitely! That's one of the biggest reasons why I want an N1. It has a good root and dev community and gets android updates first.
I just thought it'd be annoying to have to use a phone with crappy capacitive buttons, but I'm glad to hear that the problem has been fixed.
The only other thing I'm worried about is the dualtouch but it's most definitely going to get fixed in the next update.
Thanks to everyone for their input. I'll definitely be picking up an N1 soon
I have rooted and custom roms etc and I still hate the capacitive buttons with a passion. They are not nearly enough to topple the overall awesome that is the N1 but man I hate those things.
I only hate those buttons, when Nex is in my car mount!
adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Click to expand...
Click to collapse
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I also haven't noticed any change in the sensitivity with different ROMs or kernels. For me though, sometimes if I hit right on top of the button it won't register. I am used to just tapping it a little above and it works everytime.
As others have said, this is definitely not a deal breaker for me or shouldn't be for any person IMO. This phone's pros far outweigh the cons.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
Click to expand...
Click to collapse
When someone is doing that you should just say that it has Finger print authentication technology
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
xboomer55 said:
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
Click to expand...
Click to collapse
Did you just buy your N1 from Google brand new?
Those buttons are a pain in the bum, but you get used to them, the bigger problem is if the phone gets too cold it starts mis-registering the touchscreen necessitating a reboot or a bunch of mucking around to fix it. This is the biggest annoyance with the phone for me, hopefully they fix the screen calibration in 2.2!
Almost swapped mine for a Desire, thinking less of doing so now, unless anyone can offer a good reason
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
SilentMobius said:
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
Click to expand...
Click to collapse
Just realized that!!
It does not get the upward movement
It gets: right, left & down
So this means, one could set different options for different directions...
hacker01 said:
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
Click to expand...
Click to collapse
I have noticed no issues when holding the phone in my hands but the responsiveness is not that great if the phone is flat on a desk or a similar surface. I wonder what if anything the accelerometer may play a factor.
PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I dunna man, my 3-year-old daughter figured it out within a minute of getting my phone. I set her up in a game and she decided she wanted something else, so she messed with the capacitive buttons until she got out of the game. Once she had it once or twice (~5-10 seconds for her to figure out each time) it was pretty much instant after that. If a 3-yo can figure it out, I'm pretty sure it's not THAT difficult. Annoying, sure....but not difficult.
hacker01 said:
Did you just buy your N1 from Google brand new?
Click to expand...
Click to collapse
Yes. Direct from Google.
Wow there's definitely a good mix of answers. I thought that the newer batches of N1's fixed the capacitive button problem, but apparently not.
I guess there's not a definite answer. It seems the only conclusion you can make is that some N1's may still have the problem, some may not. Some can be fixed with custom roms and unlocking the bootloader and some cannot. Your results may very.
EDIT: After rereading some of the previous posts (more carefully. excuse my sleep deprived state lol), the capacitive button issue might actually be more of a feature than an issue. I've read similar posts about the capacitive buttons having that sort of "motion detection" thing to prevent accident presses. Hopefully for anyone still having the problem, you can reread some of the posts on this page and give their methods a try
I haven't had a problem with mine but I haven't had the problems most people say they have with the phone so I would recommend this phone to anyone that wants an android phone
-------------------------------------
Sent from my Nexus One
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus?
Thanks,
Brandon
It would be easier to have them numbered
1. Trackball - never heard of it.
2. Power button - never had anything on mine, but there's a good reason to believe there was a faulty batch out there - some had to exchange theirs.
3. Touchscreen - The issue is that it starts "missing" the presses, registering way below. Pressing the power button twice (entering and exiting standby) "cures" it. A real issue, happens very rarely.
4. 3G - opinions are split on it, reported only by vocal minority and only in areas barely covered by 3G, and only long time ago. Personally, never saw anything that could be considered as "issue". Actually, rather good reception and good data rates over bad connections.
5. WiFi - again, depends on what "issue" is. It's not completely flawless, for example, fails connecting to encrypted network w/ Cisco 521G. Haven't had any problems on mine, though.
6. Proximity sensor - never heard of it.
7. Volume - never heard of it.
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Jack_R1 said:
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Click to expand...
Click to collapse
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
No to all.
Atleast I didn't notice
Any reason not to just keep the Desire? The n1 is great but the Desire is nearly identically and slightly better in some ways.
brandon1108 said:
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes- Never had this problem......
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)- Um, not for me.... But I have heard this happening to people.
3. the touchscreen randomly stops working - NEVER ever has this happened
4. 3G connectivity issue - I only use wifi since it's everywhere. More efficiant and faster!
5. Wifi problems - None for me.
6. Proximity sensor sensitivity issue - Nope
7. earpiece: insufficient volume - Nope, I find it too loud sometimes. But, I do have sensative hearing.
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus? No reasons honestly. They are both pretty similar except for support and design as well as a few other diffs. The only thing I like about the desire is it's hardware keys and chin
Thanks,
Brandon
Click to expand...
Click to collapse
brandon1108 said:
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
Ugh, I do have issues with the capacitive buttons. Like I said above, I envy hardware keys. It's not that they don't work, they just arent calibrated. You need to touch way above where they are for them to register. If you press the button where its placed exactly they don't work.
NOTE: I should let you know about all the cool things the Menu button does (second button with the lines) I just found out about the Menu button on my Nexus Lol!
I would do that trade and not have any issues at all. The nexus is The most active device right now and will be thru this year at least. Those problems you listed are not a big deal, the power button only fails for some people. Use track ball wake and you have nothing to worry about. Everything else is not really a problem.
brandon1108 said:
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
They're all screwed equally All the capacitive buttons register too high, so you have to press higher to hit them. At least they're consistent.
not a single mention of white notification burn-in. seems common.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
3. the touchscreen randomly stops working
7. earpiece: insufficient volume
Thanks,
Brandon
Click to expand...
Click to collapse
yup.
1. get stuck on going "down". kind of annoying but a spazz around with it fixes it.
2 yup, cant get it to unlock sometimes.
3, sort of. wouldnt mind it louder and of better quality. More depth.
mtl171 said:
not a single mention of white notification burn-in. seems common.
Click to expand...
Click to collapse
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Brandon,
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes No
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired) Yes & Yes gettting repaired by HTC as we speak.
3. the touchscreen randomly stops working No - used to occasionally before Froyo but not anymore
4. 3G connectivity issue No
5. Wifi problems No
6. Proximity sensor sensitivity issue No
7. earpiece: insufficient volume No
8. how are the capacative buttons? Fine, If you swipe them downwards in the opposite direction but the same manner as you would, to select the notification bar. If you tap them with the pad of your finger instead of the point it also a non issue. OTOH tapping with the point of your finger you just need to tap slightly below.
PurpleSmurfLlama
I disagree and do not think the majority of power button failures are due to poor maintenance. Is your poor maintenance theory just a hunch perhaps? I keep my phone nice and clean, no obvious crap beneath the button. In another thread someone who had a failing power button dismantled his phone an reported the power button presses a switch that is connected via a ribbon cable to a circuit board. No amount of cleaning these fixed it for him. Furthermore people who have had their "power buttons" repaired have reported that all these these items appear to have been replaced when they get their repaired phone back from HTC. Same phone comes back with new IMEI because the circuit board has been changed as part of the fix. To me this suggests that on the faulty units the issue goes deeper than just the button and a users maintenance of it. I am just hoping that the FIX is permanent.
I've had my Nexus One for a few months now and I can't say I've had any of those problems, well my WiFi sometimes just disconnects, but I think that's just to do with the distance between my room and the router. As for button and trackball problems there's been none, even after a horrifying ordeal where a friend spilt beer on my N1 then instantly after in the panic I dropped it in the sand :/
The swap in my opinion can only be based purely on aesthetics, IMO the N1 is nicer, not being biased, the Desire is beautiful, I just think the N1 is more sleek. Hope this helps even a little.
Sent from my Nexus One using XDA App
brandon1108 said:
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Click to expand...
Click to collapse
Yes exactly, just use black color and you'll be fine. That white is such a horrible color anyway.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
Click to expand...
Click to collapse
How about a poll?
1. no
2. switch is "soft" on the replacement I just received (was fine on original phone and 1st replacement)
3. no
4. YES! RECEPTION IS A BIG PROBLEM! AS IS 3G CONNECTIVITY (3 bars and websites won't load WTF?)!
5. no
6. no
7. yes
maybe add:
8. PINK screen - YES. Just keep asking HTC for replacements, screw them for their poor quality control.
9. camera color tint (blue for me) - YES. Ok for me ... but I made go another replacement binge if I find anything at fault with this phone.
10. I also experience bad call quality - got fixed by the replacement.
1. Trackball - NO problems here.
2. Power button - NO problems here.
3. Touchscreen Unresponsive - Roughly once or twice a month. I put it to standby and back, and it's fixed. I've noticed that only certain ROMs do this. I never had the problem on FRF50 or FRF83, but I have once in a while on FRF91.
4. 3G Connectivity - NO issues.
5. Wifi - NO issues.
6. Proximity sensor - NO issues.
7. Earpiece volume - NO issue, but I have always had one of Pershoot's kernels installed, which includes an "audio fix."
I would have no hesitation recommending a nexus. Though, if you're a gamer, I'd say get a Galaxy S phone because of the better GPU.
#3 is the only one that consistently pisses me off.. all the other ones are software and can and are fixed with different roms.
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
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.