I've been having this problem for the better part of a year now, but it hasn't been that bad, only a few malfunctions when charging. But now my back button seems to be unresponsive, but only works when kept charging on my desk in rest mode. When charging the phone only malfunctions on the back button side of the screen.Note that i recently flashed lineageOS [7.1.1] on it and the problems have been occurring after flashing. I know that this is probably a screen problem and is going to need a new one, but if this can be fixed without a replaced screen it would be awesome.
Any ideas ?
If you are having troubles over the ROMs and you are using a SM-G360H/HU just replace the digitizer aka touchscreen. There ain't no workaround. So far as I'm aware of.
Related
My nexus 7 currently has an unresponsive touchscreen. Almost none of my touches are working now and yesterday the tablet was working just fine but some of the touches were not working. Now almost all the touches arent working, did the hardware just fail on me?
lovenokia said:
My nexus 7 currently has an unresponsive touchscreen. Almost none of my touches are working now and yesterday the tablet was working just fine but some of the touches were not working. Now almost all the touches arent working, did the hardware just fail on me?
Click to expand...
Click to collapse
Here is what I posted yesterday on another thread, but short answer is that yes it's most probably hardware fault (I don't have picture at work, so can't attach it here).
I purchased my Nexus 7 from Staples during business trip to San Francisco. My device started having touch screen issues after few hours. Factory reset did fix it and I liked the device a lot so I didn't return it as I thought touch screen issue was just a SW glitch. Issue came back at the airport . Unfortunately I didn't have time to return the device at that point. Issue wasn't manifesting itself all the time, but seemed to come up every time I plugged the device in charger. Symptoms were exactly as in this video: http://www.youtube.com/watch?v=uVkvCXDKU2M and the other one in which multitouch is demonstrated. I suspected different applications as a reason to the problem as well as faulty charger. Then I found this thread and became assured that this must be a HW problem.
As I'm living in Finland and don't know when my next business trip to USA will take place I decided to try and fix the problem myself. I took off the back cover and touch screen worked perfectly. Initially I suspected grounding problem but pretty soon came to conclusion that it can not be the case. The problem in my case was the "sponge" pushing (what I assume is) display / touch flex. I have marked that in the attached picture. Even a very light touch to sponge caused touch screen to go crazy. As I don't have the luxury of immediate warranty repair I decided to remove the sponge and my Nexus 7 has been working flawlessly ever since. I can even charge and everything works as expected. When I started charging the device I placed my Nexus 7 on the table. It probably caused slightly increased pressure on back cover and therefore to "sponge". After removing the sponge I can't see any of the touch screen problems I was having. Couldn't be happier as I don't have any of the other problems people have found and device is working as it should, at least for now.
I don't encourage anyone to do what I did, but if you are in the same situation as I was with imported device, you can try to take off back cover and see if the problems are fixed. You should be very careful though not to break the device especially when it's powered on with back cover off. Hope this helps someone.
EDIT: 22.8.2012. Forgot to mention, that turn of WiFi if using device with back cover off. Turning off NFC and GPS won't hurt, although GPS is receiving only. Reason is that antennas are located on back cover.
Hello guys, i hope you can help me with this strange situation
The 17/01/2013 i sent my Nexus 7 to warranty because it had a problem related to the display (left part of the display slightly rised)(and this caused some unwanted touches in the middle of the screen)
The tablet came back yesterday (11/02/2013), they replaced the entire display and it worked well for some hours; in the evening i found a strange issue, sometimes the screen is unresponsive but if i try to shut down and then turn on the display again it works well...
So... my question is: is this a software problem? are there any apps that let me to recalibrate the touchscreen? Should i try go back to stock (for example 4.1.2)?
I really hope you can help me, because i don't want to resent it back to warranty and wait another 20 days~
Hi guys
I bought G2 with broken screen, replaced that with new screen - everything was fine. I did upgraded rom to higher version, after that screen become very difficult to operate. I had to press it very hard to make it work, and obviously no swipe option.
I disconnected all pieces and put together and there was no changes, however I realised that when I push back of the motherboard with force sometimes screen become responsive as normal, it works couple of seconds and become difficult again.
I have tried to localise the exact place when is a problem but it's like a lottery, sometimes it works in left corner, sometimes I have to twist motherboard a little bit.
I have read about motherboard problems on G2, but in this case it stopped to work after rom upgrade and it sometimes works fine so there is a chance to fix it I presume.
Any ideas folks?
Hi,
I own an Oneplus 2 for over a year now, in which I had to replace it's display two times . The first time I ordered a new display+digitizer assembly and replaced it myself, went great and everything worked fine. The second time was a month ago, I ordered the exact same display from the exact same seller on Ebay and did the replacement. I tested the display before assembling the Phone and it worked as it should. But an hour later when the phone was already assembled I discovered that the touch screen was completely unresponsive
After some trial and error I came to this conclusion:
the problem seems to be caused by applying a mild pressure anywhere on the bottom right quarter of the screen
the display does always respond when I hold my finger on it (with or without applying pressure) for about 4 seconds, then it sees my finger and I can swipe around (while still holding it down)
if I try the method above a few times, or let the phone rest on a desk for some time, the problem disappears and the touch screen works fine again.
So far, it looks like a hardware-issue, maybe a faulty screen or I messed something up while replacing it. But it gets weirder:
My OP2 is rooted and at the moment of replacement, it was running Lineage OS 14.1 (nightly, 2017-03-30). And when I wanted to update that to it's newest build, I realized that this whole touch screen problem doesn't exist in the TWRP recovery interface. It worked perfectly fine even when I tried to recreate the problem by applying firm pressures on every spot on the screen. So this made it look more like a software-issue, however the update of Lineage didn't resolve it and even restoring my backup of OxygenOS 3.5.6 didn't help.
I found this XDA-post about having firmware issues for the touchscreen with Android 7, but running their fix did not resolve anything either.
Right now my phone is pretty unusable since having it in my pocket is creating the problem. :crying:
Does anyone have any ideas of what the exact problem could be? Or anyone having similar issues? Why is it that there is no problem at all when booting into recovery (TWRP)?
It looks like loose connections between the display and digitizer.
After all it was a hardware issue. I disambled the phone again and after a lot of trial and error I found that there was something that came in contact with the back of the lcd that must have created a short cicuit or something. I placed a thin sheet of paper on the back of the lcd to prevent this and it all worked again! Still weird though that it didn't happen in TWRP.
Hey, guys.
So in Short my Note 4 fell from my mom into the seawater, I got it out and dried it and it kept freaking out for several days, but then slowly restored all functions normally.
Well, except that the soft keys don not light up or respond to fingers. Only to the S-pen
Is there any fix to it? and is it a hardware issue? I went to the Customer care and without even checking they said they'll change the entire touch screen, which will cost almost 60% of the mobile price
Any help here please?
Could be the charging port board. The keys are integrated in it.
I had the same issue with my back button after i swapped a malfunctioning charging port.
Now I changed it again and although I restored my back button functionality (with minor hiccups), it still doesn't light up, so I turned off the lights on both buttons.
Considering I have the wakelock app on to keep it alive, having replaced the battery twice and having disassembled it several times, I am happy with what I have.
Sometimes I just wish it would die so I have a reason to buy a new phone, but as long it turns on I won't go to another device.
gustic.gx said:
Could be the charging port board. The keys are integrated in it.
I had the same issue with my back button after i swapped a malfunctioning charging port.
Now I changed it again and although I restored my back button functionality (with minor hiccups), it still doesn't light up, so I turned off the lights on both buttons.
Considering I have the wakelock app on to keep it alive, having replaced the battery twice and having disassembled it several times, I am happy with what I have.
Sometimes I just wish it would die so I have a reason to buy a new phone, but as long it turns on I won't go to another device.
Click to expand...
Click to collapse
Problem is, It's 5 months old now and I'm borke to afford a new one that soon.
Plus everything works perfectly except touch on them despite that they work fine with the pen
Guess I'll have to settle with any app to draw soft keys on my touch screens, since I'm not replacing a 4000 pound screen just to fix the keys
I just hoped that someone had run into that issue and fixed it