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
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
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.
It seems that corner touch screen sensitivity issues are prevalent among all nook color users. What I'm wondering is, does nookie Froyo have this issue as well?
Yes, or at least for me.
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
I'm on a rooted stock, but my edge sensitivity issues went away when I loaded one of the overclock kernels. I don't know how the two could be linked, but it is the only explanation I have for the difference. I'm not sure if that's been explored on Nookie, but I thought I would share since that would point to a software issue rather than hardware.
isolated_epidemic said:
I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
That I'm not so sure of. Using "Touch Test" I see all touches, but they seem to get shifted slightly when I press near the edges. Maybe this could get solved in the driver (maybe with some help of calibration tool). I hope to have time to play with this sometime soon.
isolated_epidemic said:
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
How can you be so sure?
If i use google market, sometimes the search button is hard to press,
but using appbrain market it works 100% of the time without problems.
No its not H/W I think, run some tests and corners work fine.
Its certainly something else, I also have better response after loading OC.
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
I've seen the same behaviour as well, some apps the corners take 18,013,108 tries to get to work, other apps I'm all "Whoa, first try and it worked?!".
I put the 950 OC on my autonoot but then I started playing with Froyo on a C10 SD card (very quick) so I don't know if the OC's actually helped with the corners or not. And of course this is the one day I leave it at home since I got it.
Ultimoose said:
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
Click to expand...
Click to collapse
Use Menu>Search instead of trying to touch the top magnifying glass.
Happens to me with Froyo. I seriously doubt its hardware related. Seemed to work fine on the stock B&N.
It is common for digitizers to be less accurate along the edges but the Nook Color seems worse than normal. I've noticed the problem regardless of kernel or rom used.
I'm pretty sure it has something to do with the LCD Density. All buttons/elements are a lot easier to press when I switched to 240-250. It does look ugly though, it'd be a lot prettier when we get a custom rom running.
Sigvard is right. Fixed for me by chaging my LCD Density. I set it to 200, which is a little too large for me, so I may lower it. But since doing that I have had no problems at all.
Guide here: http://forum.xda-developers.com/showthread.php?t=889951&highlight=LCD+Density
Ha! I have the exact problem even with stock rom. I though it was the problem of the particular corner of the unit I got! It is much easier to press the button in landscape view.
I dont believe its the screen. Download AppBrain and tap the search button. it works 100% of the time
It is the screen. Use a drawing program and notice how it is easy to draw a straight line in the middle and not as easy on the sides and corners. Note, you need to drag your finger slowly or else you will see more interpolation.
Raising the LCD density just hides the problem by making the hit zone bigger. Fortunately, I can live with the it.
Device: Nook Color rooted to 1.1
I had my Nook Color in the car today (40 degrees or so), pulled it out to show her what it looked like rooted. While standing in the driveway showing her different things, I found the touch screen was overly sensitive. As I was scrolling through different things (the app list, twitter, facebook), the slightest touch would select/open an item. It normally doesn't do this. It was incredibly frustrating and almost unusable. I pulled it out later and it seems to be behaving like it normally does.
Does temperature affect the NC screen? Where they any touch screen changes in 1.1? Is there a setting to calibrate the touch screen? I can't seem to find one. Any other suggestions?
I tried doing a search on the forum, but the search crashed.
Thanks.
horsemom said:
Is there a setting to calibrate the touch screen? I can't seem to find one.
Click to expand...
Click to collapse
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
I don't know if it's placebo or not, but I feel like this app improved my screen response.
http://forum.xda-developers.com/showthread.php?t=934500
As for the other question, I would expect the screen to be less responsive in cold weather, but I don't have anything to base that on.
Guessing what you experienced was due to condensation on the screen. Doesn't take much and can be 'invisible' to you but the screen is sensitive to 'stuff' on the screen and will become overly sensitive if there is anything on it, like moisture, skin oils, etc .. a screen protector may help but unless it continues that is probably the cause.
tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
What you experience is probably temperature related, but another thing to try is to increase the LCD screen density to around 190, 200, or a little more. For me, I get improved sensitivity, especially near the corners.
My daughter accidentally got a little water on the screen and it was a little erratic. I put it in a ziplock with a handful of rice for about 6 hours and it was like new.
I have owned 3 nook colors, the first one I owned freaked out when I used a damp cloth to wipe the screen. It exhibited some strange behavior and emitted some loud static from the speaker. It would not power down or anything... finally it just went back to normal, so I took it back to B&N and then went and bought one at walmart. I took it back because I thought I wanted the Viewsonic G Tablet. But after trying it I finally bought a Nook Color at Best Buy, bought a screen protector too so that I don't have a repeat of my first NC. The screens on these things are, I believe, rather sensitive and the cold or the moisture may have played a part in your unit's behavior.
migrax
tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
Same here. My screen also seems very inaccurate.
Have you found a fix?
Sent from a NookColor using the xda app
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
tenderidol said:
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
Click to expand...
Click to collapse
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
It's funny, actually... The cold makes your skin less detectable because of vasoconstriction in your fingers as a physiological response to the cold temperature, but a hint of moisture by means of condensation has the opposite effect.
For me, condensation is rarely a problem, but the decreased capillary blood flow effect is quite noticeable.
Sent from my Nexus S using XDA Premium App
One thing that's been mentioned before (and the B&N salesman told me while buying a screenprotector) is that if the screen has a lot of fingerprints, it'll make the nook act weird.
Try wiping the screen of fingerprints.
don_ernesto said:
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
Click to expand...
Click to collapse
Thanks for the reply. Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
tenderidol said:
Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
Click to expand...
Click to collapse
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
don_ernesto said:
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
Click to expand...
Click to collapse
Thanks again for the reply.
Yes, I'd love to take care of it ASAP, since I'm sick of trying to hit a small button on the screen and going somewhere else instead.
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
tenderidol said:
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
Click to expand...
Click to collapse
go ahead! you won't loose any app or any data (not even your progress in Angry Birds)
Of course, before applying this changes i always make a backup. good to have a way back in case something goes wrong
Good test tool
I ran GoJimi's tool, and since then my screen has been flipping out. Typing anything is a good test...I enter one key like "z", and get 2 - "zm". Utterly maddening.
A good tool to see what's going on is "Mutitouch Test" from JerryW in the market.
When I press with one finger, I see a "phantom" 2nd point jumping around. Very quick way to see 1) how good tracking is and 2) if there's any random inintended multitouch action happening.
Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Yes, i have this problem. And only while device is laying on the table.
Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.
Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan
Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?
ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.
I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.
I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app
Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O
DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.
Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind