hi friends
yesterday night unfortunately my son fell over my touch pros touch screen when i checked at night the phone was working perfectly and today morning the screen is showing 1 big rectangle mark with small dots on the screens surface and the screen is not responding phone is working but screen not responding
will i have to change the screen ?
please help
The same thing just happened to me!??! Exactly!? If anyone has any tip, please let us know. It's a rectangle slightly smaller than the screen and it's a blurry colorful appearance with a grid of faint dots. It appears as though layers in the touch screen have separated. I didn't do anything to my phone to prompt this - no abuse whatsoever.
Hey guys and gals,
I have nexus 5 that is just about a year and a half old. Every now and then, when I wake up the phone from sleep, the touch screen becomes unresponsive and I see white horizontal lines running across the top. I have tried restarting the phone, resetting the phone to factory. The problem still persists. The only way I get the lines to stop from showing up and get the touch screen responsive again is pushing down on the screen hard at random location.
I have attached a video of the problem I'm getting. https://youtu.be/CzgZ1bcN1Lk
I'm suspecting its a screen issue and I need to replace the LCD panel, Digitizer, etc
Any help would be greatly appreciated.
Thanks!
You need to replace the digitizer (if I'm not wrong), I've encountered this issue before on my older phone.
I charged my Nexus 5 using a cheap charger for some hours and upon unlocking the phone I found that there was a black spot at the bottom right of the screen and it was spreading. Now it's just a white spot (pictures attached) but parts of the screen are not responding to touch. For example I can't type the word "o" or edit a contact. Anyone know any solution to this? Will I have to change the whole screen?
Hi, I'm having some issues with my opo. So, a few weeks ago, my phone suddenly had ghost touch and unresponsive screen. I fix that by flashing boeffla(is my spelling right? ) kernel and adding some lines in build.prop to fix dithering, and both fix come from this forum. Well, it does fix the ghost touch problem.
But, the lower bottom part of the screen is still not working, including the capacitive key. When I dug this forum, I found that 1 of the possible fix is to insulate/isolate the digitizer with the chassis. Sadly, I don't have the tools(namely hair dryer to separate the screen with body) and have no money to buy it. My questions are :
1. Could I disassemble the screen without hairdryer? And if I could, is it risky? I don't have the money to buy replacement screen either if I mess up the process
2. As a workaround, I try to modify screen size, dpi, and overscan through terminal emulator. To a certain extent it works. But, as the dead zone is the bottom part of the screen, is there any command or way to resize the screen so that the resized screen is from topmost until the part where the screen still work? (resized said screen result is placed in the middle of the screen, so I can only resize it to a small size, it's a bit impractical)
3. If I overscan the bottom part of the screen until past the unresponsive area, some part of some apps are "drowned"(for the lack of better term) meaning that some buttons are not visible (example: opera browser). Any solution about this?
I'm sorry if my questions are noob's questions(and a lengthy one at that, too). Please help me and thank you so much for your help
mr5321 said:
Hi, I'm having some issues with my opo. So, a few weeks ago, my phone suddenly had ghost touch and unresponsive screen. I fix that by flashing boeffla(is my spelling right? ) kernel and adding some lines in build.prop to fix dithering, and both fix come from this forum. Well, it does fix the ghost touch problem.
But, the lower bottom part of the screen is still not working, including the capacitive key. When I dug this forum, I found that 1 of the possible fix is to insulate/isolate the digitizer with the chassis. Sadly, I don't have the tools(namely hair dryer to separate the screen with body) and have no money to buy it. My questions are :
1. Could I disassemble the screen without hairdryer? And if I could, is it risky? I don't have the money to buy replacement screen either if I mess up the process
2. As a workaround, I try to modify screen size, dpi, and overscan through terminal emulator. To a certain extent it works. But, as the dead zone is the bottom part of the screen, is there any command or way to resize the screen so that the resized screen is from topmost until the part where the screen still work? (resized said screen result is placed in the middle of the screen, so I can only resize it to a small size, it's a bit impractical)
3. If I overscan the bottom part of the screen until past the unresponsive area, some part of some apps are "drowned"(for the lack of better term) meaning that some buttons are not visible (example: opera browser). Any solution about this?
I'm sorry if my questions are noob's questions(and a lengthy one at that, too). Please help me and thank you so much for your help
Click to expand...
Click to collapse
AFAIK,there's no permanent fix except changing your display which doesn't cost much.
No,only hairdryer won't work,you need a professional heat system to get the digitizer out of the lcd.
I guess the only possible solution I can see is changing your display for the sake of your own good.
It costs only 28 USD.
Hello,
I see many times at my pixel 7 pro that the left side of the screen (at the edges) is not working in gestures or even in tapping in the keyboard or buttons at the whatsapp, is it some settings that I need to change?
Thank you
I also have this issue once in a while. If I turn off the screen & turn on, issue will dissappear but it comes back randomly.. Not sur eif it's because of the case I'm using or software / hardware issue..
I have daome glass plus caseology so who knows?
I've got your same problem, i read pm reddit others people with the same problem
I've got a tpu screen protector
So it's hardware problem?