Hello
I have an old Nexus 4 E960 which I used to love but unfortunately the digitizer started malfunctioning and the lower half of the touchscreen started detecting phantom touches. I kept the phone aside for 2 years but considering that all other faculties are working perfectly, it seems such a shame to just let it go to waste. Do you have any idea on how to put it to any use whatsoever? Maybe as an IP cam, maybe control it wirelessly while completely disabling touchscreen input?
I ve tried to set the boundaries of the screen to right above where the phantom touches occur but unfortunately the touches are still detected, although they dont affect anything right now. Without this fix the moment the screen is turned on it would start clicking this and that. But even though the phantom touches are not causing any effect anymore, they still trip the maximum finger limit (at least I think thats whats happening) and I'm unable to just use the phone from the top half alone as I had hoped.
Any suggestion is welcome. Right now I can't even unlock the lockscreen. Nexus 4 doesnt even support OTG so I cant disable touch completely and use a mouse to control it which would have been amazing. But I would really like to use it somehow. I mean its such a beautiful phone!
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
http://forum.xda-developers.com/nexus-4/help
Kind regards
Trafalgar Square
XDA Assist
Related
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.
There are lots of videos showing this problem: after you have touched the screen sometimes the screen registers finger presses even after you've removed them.
It's very hard to see what is going on if you don't turn on "show touches" in settings, so I suspect many reports about touch screens being unresponsive, or acting strangely is really the same problem.
It occurs both in stock ROMs and aosp, but subjectively more often in stock roms. It's not about moisture remaining, I've wiped the screen completely clean and dry and the phantom touches are there before, during and after cleaning.
Is there a software solution to this or is it hardware? Any thoughts of how this problem could be approached? I'm having trouble even reproducing it reliably.
yet another video of the odd problem: https://www.dropbox.com/s/mglol5qon6vy67g/2013-08-11 20.15.01.mp4
I replaced my Asus TF300 because of a similar issue. Asus fixed it once under warranty (replaced the entire LCD and digitizer, I think) but the issue came right back within a few months after RMA. By then the warranty had expired. In my case, the ghost touches were prevalent in a specific part of the screen; couldn't tell from your video whether the false touches were in the same general area every time or not.
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior. Just to be sure, though, I did flash a stock ROM prior to sending back to Asus and verified the issue existed there, labeled the area with tape so they could not miss it, and described in details the steps to reproduce.
Good luck.
Sent from my GT-N8013 using xda app-developers app
bsaman said:
I
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
This is my experience also, the aosp revolt rom, seems to suffer much less so than the stock roms.
It does seem to be the same area but it might be just because it's the side that is used most often for scrolling due to me being right handed.
The difference between how the roms behave is what make me suspect it's a software issue.
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
PremiumMediocre said:
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
Click to expand...
Click to collapse
No, my note has been rock solid, but I haven't enabled show touches so I can't say for sure.
Sent from my Vivid 4G using xda app-developers app
I'm thinking it might be possible to alter the idc file that specifies the behaviour of the touchscreen (https://source.android.com/devices/tech/input/input-device-configuration-files.html). But it's all a bit over my head.
I'm not alone at least:
http://www.youtube.com/watch?v=ii7m2696T3Y
A simpler cause?
I'm not alone at least:
(YouTube Video URL that I'm not allowed to post, yet)
Click to expand...
Click to collapse
The guy in the video did a great job with research. Did you catch the part where he found nearly imperceptible damage to the screen that was a possible cause? The ghosting always seems to occur in the same places because that's where the screen has been "crushed". Now "crushed" is a bad word because the screen probably hasn't been compressed beyond an acceptable level but there might be some correlation between where the users normally places his/her hand when using the pen and where the phantom touches occur. Maybe when writing, some users are baring-down harder than they realize and prolonged pressure in the same arc-shaped area created by the side of a hand, causes some changes in the capacitive properties in that area which cause a "latch" condition -- where the digitizer gets stuck and won't unstick until power is removed.
I've noticed in the videos that I've seen that the presenter get the problem to appear when using the side of their hand in a rolling fashion -- probably the same motion that they use when they just start to write. I also believe that devices that have this problem "get better" or less sensitive when not used for a while. This would follow the idea that the screen is compressed and given some time, the compression relaxes.
If the problem is limited to a certain area of the screen, I find it hard to believe that the problem could possibly have anything to do with ROM or firmware. The matrix of the digitizer in X-Y coordinates is addressed such that if there were a problem like this, the error would occur and repeat in either a straight vertical or horizontal direction instead of finite points spanning many rows and columns.
I guess one way of ruling this idea out would be to find someone who has never used the pen to write yet still has the problem.
I haven't ruled out that it is hardware related, but I have noted a significant improvement leaving stock ROMs for aosp. Maybe that's just a coincidence, I can't know for sure. I have noted something else that might help diagnose this problem.
If the period of turning on the screen, using the tablet then turning off the screen constitutes one session, there are two types of sessions. Sessions which suffer from this problem, which will be apparent in a relative short period of time. But there are also sessions where everything works as it should, regardless of how long the session is. So you will notice this problem within 10 min or not at all.
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
drakester09 said:
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
Click to expand...
Click to collapse
It is different than ghost-touches.
I noticed there is a topic on xda about this problem already: Click
I hope this can be fixed with a software update.
joeyzbg said:
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Click to expand...
Click to collapse
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
DuckMcQUack said:
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
Click to expand...
Click to collapse
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
joeyzbg said:
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
Click to expand...
Click to collapse
It really may be...just get used to New display settings and you will be out of problem too then!
Inviato dal mio One utilizzando Tapatalk
I have the exact same issue with my OnePlus after 3 weeks of use. At first it was the swype issue where the phone wasn't picking up swypes properly on the middle left side of my screen. I use a pattern unlock so it's annoying when the dots don't connect.
The next thing was not picking up my touches properly so when ever I use SwiftKey and they recommend words, I could never properly select it because the touchscreen wasn't registering properly.
I did a factory reset and it solved the problem at first but it's now back after 2 days. It's not as bad as before but still persistent. There are tons of people on Redit, Cyanogen and the OnePlus forums that are reporting the same problem.
The good news is it seems like a software and not hardware issue, hopefully the permanent fix can come soon.
Possible solution to the supposed OnePlus One touch sensitivity problem
Settings→Developer Options→ Scroll About Half Way and UNcheck "block gesture touch events"
Also try and see if unchecking "Adaptive backlight" in Settings→Display & lights→ Adaptive backlight, helps.
Of course none of these are permanent solutions. And this problem is real. But maybe the "solutions" above help.
ive not had these issues just yet. but i do get annoyed by gesture control
This still needs to be addressed. It's almost as bad as an old capacitive touch screen!
I got my phone maybe a month after it was released. After exactly 4 months the touchscreen input died and lost all sensitivity. Typing became impossible. After going back and fourth with support for 2 months they finally sent me another one. The new one was excellent for EXACTLY FOUR MONTHS!! Almost to the DAY! My damn touch is broken again and I can't type. I'm furious! I'm also 1wk outside warranty.
With the first phone I tried every hack, crack, rom, reformat, anything I could find. Nothing would restore the touch. I assume it's a hardware issue. I've been looking around for a solution but haven't found anything. If there is anything, I would appreciate some direction.
Sorry for everyone that ever wasted their money on OnePlus, I won't be getting any more products from them...
Can't edit title, forgive for lack of detail.
Phone: Samsung Galaxy S6
Android 6.0.1 - 2 updates since issue bagan
I had the issue where I could not revert to a standard swipe unlock after using a pin, and was told a solution was to clear credentials/certificates.
This solved my problem, but created another. As it stands, about 75% of unlocks it plays one/both of two sounds, which granted do sound like some sort of unlock sound, however not standard to the way the phone shipped. It also happens at random, sometimes as a response to a touch, or just whenever it feels like it. It is one of or both of the same two sounds presented with at unlock. They are ridiculous and am preventing me from using the phone whilst not on silent. The phone has a mind of its own.
NFC is turned off.
I am not tech illiterate and thought I could fix it, however it has beaten me. Any help would be appreciated.
BigDrewy1 said:
Can't edit title, forgive for lack of detail.
Phone: Samsung Galaxy S6
Android 6.0.1 - 2 updates since issue bagan
I had the issue where I could not revert to a standard swipe unlock after using a pin, and was told a solution was to clear credentials/certificates.
This solved my problem, but created another. As it stands, about 75% of unlocks it plays one/both of two sounds, which granted do sound like some sort of unlock sound, however not standard to the way the phone shipped. It also happens at random, sometimes as a response to a touch, or just whenever it feels like it. It is one of or both of the same two sounds presented with at unlock. They are ridiculous and am preventing me from using the phone whilst not on silent. The phone has a mind of its own.
NFC is turned off.
I am not tech illiterate and thought I could fix it, however it has beaten me. Any help would be appreciated.
Click to expand...
Click to collapse
Greetings and welcome to assist. It looks like you already found the correct place to ask your question here
http://forum.xda-developers.com/showthread.php?p=69454465#post69454465
so I'll close this one up
Good luck
Sawdoctor
Phone: Samsung Galaxy S6
Android 6.0.1 - 2 updates since issue bagan
I had the issue where I could not revert to a standard swipe unlock after using a pin, and was told a solution was to clear credentials/certificates.
This solved my problem, but created another. As it stands, about 75% of unlocks it plays one/both of two sounds, which granted do sound like some sort of unlock sound, however not standard to the way the phone shipped. It also happens at random, sometimes as a response to a touch, or just whenever it feels like it. It is one of or both of the same two sounds presented with at unlock. They are ridiculous and am preventing me from using the phone whilst not on silent. The phone has a mind of its own.
NFC is turned off.
I am not tech illiterate and thought I could fix it, however it has beaten me. Any help would be appreciated.
Well ,
Could you post ur question on s6 forum
http://forum.xda-developers.com/galaxy-s6/help
& register on the forum ok
Good luck ,,