Related
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.
Does upgrading the HBOOT help with the wonky touchscreen heat-related miscalibration issues that every Nexus owner knows about?
I raised this question on a different thread:
http://forum.xda-developers.com/showthread.php?t=903975&page=9
but wanted to throw this question out to a larger audience.
This week I finally got tired of having intermittent but definitive touchscreen miscalibrations, usually associated with charging and/or heavy usage. HTC shipped a swap for me to use.
The new one works pretty well, except the camera takes pinkish tinged images, so it unfortunately will be going back. However, I noticed that the HBOOT is the newer 0.35.0017 (though the date displayed by the bootloader screen is Jun 14, 2010).
So I upgraded the HBOOT on my original N1, and have been trying hard to reproduce the touchscreen craziness. So far I've been unable to do it.
It's difficult for me to make it happen on demand. I "stress tested" it essentially by doing the things that normally bring it on, GPS with charger, and graphics intensive games. But I'm getting really tired of beating angry birds again and again =P
So, if you're still experiencing touchscreen wonkiness that is fixed by turning on and off the screen, which HBOOT do you have?
There are of course many other potential mitigating factors I've thought about. Custom ROMS. Kernels. Touchscreen protector. Radio version.
Just for completeness, there are different part numbers on the two:
Original N1 part # 99hke002-00 F
Replacement N1 part # 99hke002-01
Who knows what the significance of that is.
No it doesn't.
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
You know, as strange as it sounds, since I upgraded to the 0.35 HBOOT about a month ago, I have had zero issue with the digitizer. Call it coincidence, but that is what's happening so far.
We will call it coincidence for now =)
A happy coincidence.
waylo said:
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
Click to expand...
Click to collapse
Not very often, in fact think it hadn't done it over the past week. I've been using the crap out of it customizing CM7 over this weekend and no hiccups.
our touch screen is always a hardware problem..
That's not the question. The question is if you're still having a lot of problems with your touch screen, which hboot do you have?
I was actually kinda wondering the same thing. I finally got around to putting on CM7 (build 39) on Friday (coming from CM 6.1). I right away had the impression that the screen was more responsive (the notification drop-down bar tipped me off) and I have not had a single episode of wonkiness with the screen since. CM 6.1 was a little weird for me and I had screen issues (especially the drop-down).
Oh well, even if it isn't the HBOOT, something has changed for the better for now
Another thing I learned recently is that on the native google navigation app, there seems to be a touchscreen dead zone directly vertical in the center of the screen (in landscape mode at least). It basically corresponds to the current street you're on if your navigation is active and your path is straight ahead.
So if you touch there and try to shift the screen around, you might mistakenly think the whole screen is awry. I think this is by design.
I'm not sure why it's there but it reliably is unresponsive to drags. So I'm not using that center area to gauge if my screens gone wonky.
Now if you hit the menu button, the buttons centrally do respond to taps.
Just had my first case of misregistering digitizer in a while. But instead of the whole bottom 1/3 of the screen going stupid it was just the bottom right corner, around the enter button/backspace if you have a portrait keyboard.
Oh well, it still works better than stock eclair!
So just as an update, the HBOOT definitely does not rid the digitizer issues plaguing everyone. It seems actually that my kernel had more of say in when/how often the issue surfaces.
I found that on Enom's Froyo ROM, problems arose more often with stock Enom than Pershoot or Wildmonks. However, each kernel has its own benefits.
I recently got a replacement phone from esurance for a broken Droid x2. They sent me a droid 4, which I had no objections against given the great specs comparatively.
I read reviews on the screen being low quality, viewing wise, and this is not the issue I have with the phone. Coming from a dx2, the quality is not that different.
My problem is that there appears to be a lag between when i touch the screen and when it starts reading the input. A simple test to show what I am talking about is as follows;
Download multi touch paint or another paint app. If I swipe my finger across the screen as fast as i can, I can get 2/3 of the way across the screen before it draws anything.
This half second delay makes typing on the screen nearly impossible...It only picks up about half of the letters I press when typing normally like I would on a Dx2. To be clear, its not inputing the wrong letters because i am not used to the phone.. Its not inputting anything on about half of my keypresses.
I am on the latest official (nonleaked) version of android. Unrooted.
Should I RMA it again? Is there a fix, and has anyone else experienced it?
Thanks for any help!
over 150 views and no reply yet? I dont mean to rush things along, I just wanna make sure i did everything right.. Im in the right section?
If nothing else, could someone else tell me whether they have similar results?
Is typing horrible for everyone on the onscreen keyboard?
I don't use the on screen keyboard much but the few times I have I have not noticed any lag. Sounds like a hardware issue to me.
I'd do a factory reset (yeah yeah, I know). If that doesn't fix it, you can either RMA it again or try to install a 3rd party rom and see if that helps things.
What you are describing is definitely not normal.
Factory reset actually cleared up my issues =) thanks!
I've started to have touch screen issues the past few days.
Any idea what may cause it?
Sometimes, when I touch the screen, say in settings, I touch one item, but a different item is selected somewhere randomly on the screen.
Happens in TWRP as well. If I select options to wipe, it will select others, and then it doesn't swipe over to execute the action.
No ideas? What would make touches appear where I don't touch, even on TWRP?
I tried the keyboard calibration on HTC's keyboard.
Any ideas? Screen protector?
It comes and goes.
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
mcwups1 said:
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
Click to expand...
Click to collapse
I opened another thread about a similar issue I'm having after Lollipop. My gesture launch randomly stops working and I have to reboot. No other issues for me though. I have an anti-glare screen protector on mine, but had no issues before the update. I've thought about a factory reset to see if that would cure what ails.
I'm on tmo but have the same exact issues. This is what i've found so far...
I turned on the developer options and turned on show pointer. This will show you where the touches are landing.
If you scroll down slowly, you can see most of the touches are in line (up and down) and not random on the screen.
I've removed all programs that have screen overlays (screen filter, twilight etc)
I've removed the cases thinking they might be causing the issue, but removing them only slightly improved the issue I thought...
Sometimes its hard to reproduce the effect, its not consistent. So this leads me to believe that it could be a process that's running in the background that calls attention at the moment you're touching the screen, and then refocuses the screen to your point of contact. And in between it thinks you're moving your finger when you really aren't.
In any event, I can't find the exact cause of this. But, it definitely started after the update to lollipop. I had none of these issues before. I even got the phone exchanged because I believed the digitizer went bad or something. But this issue exists on my original phone, its replacement, and now on my wife's current phone and that phones replacement (across 4 phones).
I'm currently working on my wife's replacement (4 or 5 non-oem programs installed) and continue to have the problem. But it is not consistent as I can't readily reproduce it.
What i've done to try and learn more is when I see the screen pointer light up in random places, I keep pressure on the screen so I can observe where the screen is registering contact. It almost looks as if it's trying to pull down the shade. Whether it be because of the dual points of contact and it thinks we're swiping down, or because of another program that is stealing focus for whatever reason.
If anyone else has insights into this, please let us know as this is more than frustrating! I keep calling people in hanouts with a lot of people and they aren't happy about it lol.
Also for reference, we're using ADW ex launcher instead of Stock HTC Sense. But even when I remove ADW (uninstall) and run sense, it continues to happen. So it's not that.
Just retired my 2 XL and got a like-new 4 XL. Loving it so far, except one nagging issue.
Randomly the top 30-50% of the display stops registering taps (touch). It's easy to fix by turning the display off then back on, but I'm concerned it may be a hardware issue.
Interestingly, when this happens and something that is full screen and scrollable such as a contact list or app drawer is in the foreground, I can drag from below the "no touch area" to the top of the screen, but I can't start a drag at the top. So, it can sense touch in the troubled half, it just won't register taps.
I have done tons of searches. I see lots of people saying Android 12 had touch issues out of the gate, but was supposedly fixed. I disabled the block_untrusted_touches. I have checked any app that has draw over other apps permissions. I have tried with high touch sensitivity on and off. I have paid attention to running apps when it happens. I installed a LogCat reader looking for touch related issues when the problem occurs. I tried safe mode, but due to the intermittent nature of the problem, and the fact that safe mode disables most functionality, it really wasn't a good long term test.
I have yet to pinpoint this.
Sometimes it doesn't happen for a day, other times it's multiple times per day. So trial and error takes time because just when you think you licked the problem, it rears it's ugly head again.
I'm running LineageOS 19.1 at the moment (which I had also run on my 2XL with no issues). It is rooted. No apps force closing or crashing.
Has anyone else seen this on the 4XL?
Definitely interesting, never heard of that. I had some touch issues, specially if the display gets wet where it register touch, but poorly to the point I need to restart the device and dry out the screen. Though in my case the creen is completely cracked, so I suspect that's the cause as it didn't happened before.
Though I had a similar to yours but with the battery.
The problem was that the phone would randomly shut down, and that would happen more often when it was on my pocket.
This made the phone very un stable as sometimes I would have the phone completely off and didn't even know about it.
So I decided to open it and have a look at it. It turn out that the problem was the flex cable that connected the battery with the logic board, it was just slightly tore on one side, but just a tiny I couldn't nearly see it, I had to use another phone to zoom in.
As it was torn, depending on the way the phone was changed the force the gravity made over the cable, causing that sometimes it not enough energy got the phone, causing it to shut down.
Once I replaced it, it never happened again, not a single time.
Maybe you have a similar problem, though as you are rooted and using a custom ROM, that may be the reason, my case was extremely rare.
anyway, good luck