My nexus s at times tends to be unresponsive at the center part of the screen. This problem has actually plague me from since I was in stock 2.3.1 and followed on up to now. From my searches, I know I'm not the only one that has this problem and some speculate that having a screen protector contributes to this problem.
My best bet is that this would be more of a software problem than a hardware side as a quick lock/unlock always fixes this issue. Below is a request by someone in cyanogenmod and I find that his response seems to have some good basis. I was hoping with a better background in developing this stuff could help. Also what to know who else out there is experiencing the same problem.
Recently I've got a Nexus S, and I fount its touchscreen sometimes unresponsive, especially right after unlock. The center of the screen cannot sense tapping, but the edge and corner area works well. The four soft keys always works great, but I think they are controlled by a different cypress chip. I've tried to connect adb and "cat /dev/input/event0" and the result confirms my observation. Searching a Chinese android-lover forum, I found several guys are experiencing similar problem. (Some are running stock, others, including me runs CM-7rc). The problem can be strangely solved by locking and unlocking the phone quickly, and when the touchscreen is working correctly, it's actually very sensitive and responsive.
Suspecting a driver issue, I looked into the source of touchscreen controller (AMTEL MXT224) driver (/driver/input/mxt224.c) by Samsung and compared it to drivers of the same chip by Motorola and HTC. I notice that HTC and Moto's drivers send calibrate signals to the touchscreen controller in there resume method, but samsung's does not. I doubt whether it's the cause of issue. Modifying driver and compiling android kernel are beyond my knowledge, so I'm calling for help.
I know not all nexus s are suffering this, so I'm read to test and provide feedback. Any help would be greatly appreciated!
HTC driver (http://pastebin.com/7BZvp50x, http://pastebin.com/wxMV9ifY)
Moto driver (http://pastebin.com/5jnT8jvv, http://pastebin.com/yNH3nUa5)
Click to expand...
Click to collapse
Related
I have a completely stock Nexus S. Whenever I answer or place a phone call the screen goes black and never comes back on. I have to remove the battery and reboot the phone. Anyone have any ideas as to the cause of this?
I think it may have something to do with the proximity sensor not being sensitive enough.
Thanks
Sorry for the thread necromancy but it's either that or creating another redundant thread for the same issue. I'm suffering from the same problem as the op (nonrooted Nexus S everything stock) and so are the people who have responded to the informal bug report in the Google mobile help forums you'll get as the first hit if you google "Nexus S back screen after call" (sorry, first post so no links).
I've been unable to remedy it despite quite a bit of research and it's getting quite frustrating, especially since the problem is still present after the update to ICS.
I've gathered this has been an issue with a multitude of handsets and that the problem is on the kernel level and seems to be the result of the proximity sensor being miscalibrated.
Now I don't know how the calibration data is handled on the Nexus S so if anyone is sitting on info related to this I'd love to hear it. Also if there is any way to recalibrate the proximity sensor via ADB or some MMI code that would be great.
Otherwise, has anyone suffered from this problem and managed to solve it by changing kernels? If so which kernel did you use?
Cheers.
evening all
Does anyone else find themselves sometimes having to tap multiple times to get something to work? (e.g. one example - clicking into a text box to bring up the keyboard)
I'm running 4.0.3 but to be honest it was the same with 2.3.6. It's certainly not terrible / unusable and I'm wondering if it is merely "lag" or an intermittent hardware fault.
Screen test applications seem to work fine by the way, possibly pointing towards "lag"?
By the way, If I tap VERY quickly too those taps are often NOT recognised, but I tested that scenario too with a friends' HTC desire and his was the same, sometimes recognised and sometimes not.
I previously had an i9023 by the way, on which I never noticed an issue. Do the 2 models have different controllers I wonder!
B
I find its finger oils that cause that. A quick wipe or turning screen off and on quick restores functionality.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
I'm having similar issues.. either lag or the answer mentioned above. It could also be a software glitch. However I doubt it's a hardware problem since for that, the screen would be dead in a certain area 24 7 which is not your problem.
Bought a nearly new galaxy tab2 from the internet, but the touchscreen seems not to be working.
Any idea what that can be. Could it be something with a ROM, or does it need to go to Samsung.
OOge said:
Bought a nearly new galaxy tab2 from the internet, but the touchscreen seems not to be working.
Any idea what that can be. Could it be something with a ROM, or does it need to go to Samsung.
Click to expand...
Click to collapse
It could be failed hardware, a bad cable, or perhaps a problem with the touchscreen controller chip.
If you can capture the boot messages using 'dmesg' over ADB, there may be info there that could help determine which.
If it's under warranty, return it to the seller for a refund or replacement, else just keep searching for a solution :\
OOge said:
Bought a nearly new galaxy tab2 from the internet, but the touchscreen seems not to be working.
Any idea what that can be. Could it be something with a ROM, or does it need to go to Samsung.
Click to expand...
Click to collapse
When you say the touchscreen "seems" to not be working, what exactly do you mean?
Does it not work AT ALL, or is it just not very responsive to your touch, i.e. scrolling is slow and choppy and/or pinch to zoom is flaky?
Because I have noticed certain apps do not work well on my 10.1 when it comes to the touchscreen, when the tablet is under heavy load. Are you experiencing this more with certain apps, like Chrome and/or Samsung Keyboard? If that's what is happening, I can help.
I use a custom firmware, so not possible to return to samsung.
As it is stuck on the install screen, I can't enable debug for ADB.
Or is it auto enabled on a custom rom.
What has the highest chance of failing. Logic board or digitizer (as the cable is not sold seperatly)
I have a Tab 2 P5110, I bought it as faulty as the touchscreen is not working. Otherwise it's alive and responding to the buttons.
After reading several topics it looks like it is a bug that can only be fixed by physically replacing the digitizer panel.
Of course I'd prefer a software solution but so far what I've found wouldn't work on this model due to HW difference.
Can someone confirm that?
Thanks.
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Elvecio said:
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Click to expand...
Click to collapse
Not yet they aren't. It appears to have affected the functionality of double tap to wake for some people.
Doesn't seem like they're updating us on the investigation either. If they've fixed it using software, at the very least they should tell affected users why all the previous updates didn't work for them.
I've been on the nightly road since mid August, in my experience touch issue improved a lot after the touch firmware update in October, however there are still very rare cases where finicky / unresponsive touch happens, you don't want that when you ask someone for her contact in a bar on Halloween and she can't input the letter 'n'.
After that I think I experienced touch issue twice, I foolishly thought this was fixed sometime ago, however it came back big time the day before yesterday, and I was on the latest nightly... So in short, touch issue is not gone
touch issue
even im having touch issues with double tap and typing.
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
anuradha1208 said:
even im having touch issues with double tap and typing.
Click to expand...
Click to collapse
William Haven said:
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
I'm thinking about downgrading... I'm currently running CM12 nightlies and the touchscreen is annoying me
vantt1 said:
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
Click to expand...
Click to collapse
Everywhere
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
st11 said:
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
Click to expand...
Click to collapse
There are at least two different touchscreen issues as far as we know:
One is where the touchscreen is semi-terrible all the time regardless of temperature
The other is where the touchscreen becomes unresponsive with the increase in temperature, and subsides if the phone is restarted or cools down
Is there a way of finding out which firmware is being used for colorOS?
I can't take this anymore, I am considering flashing either 44s or color OS
Hi all,
Just replaced the screen on an Lg G4 and I'm having some odd and somewhat inconsistent behaviour.
The phone is only picking up some some screen inputs, but once the touch screen is active it will detect all input until the touch "session?" is expired. This is best demonstrated in a video I recorded. https://youtu.be/wVREoSQUPtU
So it seems the digitiser is intact but refuses to recognise certain parts of the screen until the touch "session" is active.
Wondering if anyone can explain this behaviour and pinpoint if it's hardware or software related.
uhuglue said:
Hi all,
Just replaced the screen on an Lg G4 and I'm having some odd and somewhat inconsistent behaviour.
The phone is only picking up some some screen inputs, but once the touch screen is active it will detect all input until the touch "session?" is expired. This is best demonstrated in a video I recorded. https://youtu.be/wVREoSQUPtU
So it seems the digitiser is intact but refuses to recognise certain parts of the screen until the touch "session" is active.
Wondering if anyone can explain this behaviour and pinpoint if it's hardware or software related.
Click to expand...
Click to collapse
Update:
It seems the touch screen issues go away when the usb charger is attached. The device has been fully discharged as per the sellers instructions but despite these two fixes when the phone is running on battery the strange touch issues persist.
Still unsure what can explain this behaviour, but it seems more hardware related now that we can get it working with the charger attached.
Any advice?
Bump
Bump
Bump
bump? Surely someone must know!