I took apart my tytn, including the screen part.
After reassembling it, I've had random issues related to the keypad and screen.
By keypad, I mean all the keys on the screen part of the phone (D-pad, call/hangup,soft left/right, Internet Explorer & Email).
They will randomly cease working and randomly restart working (usually after turn on/off the screen with the power button)
The screen will also randomly turn white and come back on only if I turn off the screen and then back on.
Im thinking it has to do with a loose connection somewhere in the screen section of the phone, however, Ive taken it apart 2 more times to check everything out and the problem persists.
I wonder if anyone experienced the same thing and found which specific internal is the issue.
i would like to know too cause my buttons just stopped working. so the talk, end, message, Internet explorer, ect. but the left down up right and center button work.
I have the exact same issue.
All the keys (not keybord keys) randomly stops working. I am so used to it now, that I dont even try to answer the phone with the green key button.
The screen fades to white, sometimes (maybe 1-3 times a day).
The screen is white when awakening from "sleep mode", turning on and off the screen fixes that after a while (50% of the time white screen when from sleep mode).
I have found out that putting a finger nail between the keyboard and the screen, on the right hand side, when in closed position, and then putting the screen back on, gives me a 99% chance of funktional display.
The problem also accurs in the "full keyboard position", But putting the finger nail in the same spot helps.
So I think the problem of the connection is in the keyboard part of the phone, since those slide contact always are on the right hand side, and the display contact shift side.
I would lite to know if any body have a permanent solution for this.
(I have now opend my phone yet, and I have tryed the putting thin plastic between the display and the cover, with minimal success)
thanks for your time
alkizmo said:
I took apart my tytn, including the screen part.
After reassembling it, I've had random issues related to the keypad and screen.
By keypad, I mean all the keys on the screen part of the phone (D-pad, call/hangup,soft left/right, Internet Explorer & Email).
They will randomly cease working and randomly restart working (usually after turn on/off the screen with the power button)
The screen will also randomly turn white and come back on only if I turn off the screen and then back on.
Im thinking it has to do with a loose connection somewhere in the screen section of the phone, however, Ive taken it apart 2 more times to check everything out and the problem persists.
I wonder if anyone experienced the same thing and found which specific internal is the issue.
Click to expand...
Click to collapse
These are the exact symptoms of the "SCREEN FADING INTO WHITE" problem. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=303872
The common causes for this are a bad connection to the D-PAD controller PCB (in the technical manual they mention it should be carefully checked and the really small screews with same torque making a 90 degree with the PCB), a bad controller (that was my case, had to order a new one) or not enough pressure on the square black chip on controller (some people seem to have fixed it by putting a plastic sheet in between the chip and the case, to apply constant pressure).
I suggest you try to re-open your phone and reconnect the D-PAD PCB as carefully as you can, double checking the connection and the screws there.
I did fix my problem, by ordering a new PCB and replacing the old (probably bad) one. It started to happen after I dropped my phone and it's the only thing that worked. Now my phone is as good as new.
Hope this helps!
Similar Issues with screen
I have similar issues;
Anything thats on the foreground gets closed by the 'x' button and if I slide it open the start button gets continually pressed!
Seems to be the top right corner of my TS thats at fault
sometimes it's fine....most of the time its not!
Andy.
I have the same! I have a huge dead spot in the middle of my (Tytn) screen, and if you tap there it actually activates the "ok" in the top right corner. The rest of the screen works ok. Whilst drawing in notes any drawing near the center dead spot results in a streak to the top right hand corner...
Bad screen?
Bad rom?
Bad motherboard?
lepic2019 said:
I have the same! I have a huge dead spot in the middle of my (Tytn) screen, and if you tap there it actually activates the "ok" in the top right corner. The rest of the screen works ok. Whilst drawing in notes any drawing near the center dead spot results in a streak to the top right hand corner...
Bad screen?
Bad rom?
Bad motherboard?
Click to expand...
Click to collapse
You can rule out the ROM and M/board in my view for this specific problem. Your issue is very similar (and I think has the same cause) as those who find programs close randomly when in portrait mode and when they open the keyboard the start menu often pops up untapped.
I think this is just a case of a bit of pressure being put on the screen top right corner. Some folks have tried the business card run around under the bezel fix and had some success others have had to return for replacement/repair.
Some have taken the device apart and removed the gasket around the screen under the bezel, but this is not guaranteed to work.
Others have replaced the screen and for this particular problem it is very rarely successful as the screen is not normally damaged.
If you have a warranty use it - all of the above "fixes" are warranty voiding.
Mike
Hi Mike
It's an interesting problem as when performing a click and drag in Notes (drawing mode) the center section of the screen seems to work normally - a square box can select an area right through the middle of the screen - suggesting that the screen (as you say) is OK. So what is causing the a tap in the middle of the screen to register in the top right hand corner, when we now know that the center of the screen can work and respond in the correct manner. The size of the affected area is about the size of a thumb print EXACTLY in the middle. Personally I would like to believe that performing screen alignment 4 - 5 times a day for the past year has worn out the center dot and that is affecting the surrounding area. The trouble is that this fault has been reported on this site a few times now, and everyone says it's caused by something else! What did I do immediately before this happen I hear you ask? I flashed a new radio rom and was fiddling with a piece of card I have wedged down the RHS side of the screen to try and help stabilise the screen alignment. Since this problem arouse, I have removed the gasket - but that hasn't fixed it. I'm going to try and boot up the phone out of the casing to see what "zero" pressure applied to the screen does.
I'll report back...
Lepic.
lepic2019 said:
Hi Mike
It's an interesting problem as when performing a click and drag in Notes (drawing mode) the center section of the screen seems to work normally - a square box can select an area right through the middle of the screen - suggesting that the screen (as you say) is OK. So what is causing the a tap in the middle of the screen to register in the top right hand corner, when we now know that the center of the screen can work and respond in the correct manner. The size of the affected area is about the size of a thumb print EXACTLY in the middle. Personally I would like to believe that performing screen alignment 4 - 5 times a day for the past year has worn out the center dot and that is affecting the surrounding area. The trouble is that this fault has been reported on this site a few times now, and everyone says it's caused by something else! What did I do immediately before this happen I hear you ask? I flashed a new radio rom and was fiddling with a piece of card I have wedged down the RHS side of the screen to try and help stabilise the screen alignment. Since this problem arouse, I have removed the gasket - but that hasn't fixed it. I'm going to try and boot up the phone out of the casing to see what "zero" pressure applied to the screen does.
I'll report back...
Lepic.
Click to expand...
Click to collapse
It will be interesting to see what results you get. You'll need the old rubber band technique to hold the battery in place while you do it!
Mike
Well it's not due to the case squishing the sides of the screen as I just dismantled my hermes, wired it all up in bits on my desk, powered it up and still the screen has a dead spot in the middle and phantom taps in the top right. Temperature is normal room temp, approx 22deg c today.
I'm not sure the exact mechanisms of how these touch screens work out where you are tapping (resistance, voltage), but it looks like there are 3 separate strips running around the screen. 1 goes straight across the bottom, two goes up the LHS and across the top and 3 goes up the RHS. Therefore there is a gap between strips 2 and 3 in the top RH corner. Coincidence? hmmm It seems to me for it to register a tap in the top RH corner, strips 2 and 3 would register low voltages (or high resistance) and bottom wouldn't register at all. Thus suggesting a fault with the PSU that powers the touchscreen. Taps near the edges work because they are near the edges and therefore the resistance is not too great and can be detected, taps in the middle and worse off because they are far from all the detecting edge strips.
Does anyone think that there might a registry tweak for boasting power to the touchscreen?
Hermes Whie Screen Problem
To fix the "white screen" problem, you have to take your unit apart, and reconnect the ribbon cable.
I have a new 8525 and it started happeneing to me, so I took it apart this week, and reseated the ribbon connector.
Fixed the problem.
Has anyone here read and understood all that is said here:
http://msdn2.microsoft.com/en-US/library/aa919680.aspx
Perhaps someone could compare the touch.dll in Black Majik to WM5 - should be the same right?
How come that HKLM/hardware/devicemap/touch doesn't show the touch.dll driver as drivername? Keyboard has it's driver...microsoft says it should say drivername = touch.dll
Do you all have that in your registry?
Hi,
I just want to thank everyone on this site for the plethora of information that is available.
Here is a rather strange issue, that I did not see covered previously...
I purchased a used aria with a cracked digitizer off ebay for pretty cheap. I replaced the digitizer myself and all was good. I used the phone for about a week and dropped it. After that, the digitizer has been acting a bit flaky.
For instance, when it decides that it wants to annoy me, every input seems to register only on the middle of the screen. For instance, if I touch the top of the screen, the screen registers touches as though I was touching the screen in middle of the height. If I touch the bottom, it still registers the touch in the center of the screen.
I found that If I knock the phone against a table, along the edge, the problem goes away for a while. Then it crops up, again, randomly.
Anyone have this issue?
Thanks,
JC
Now I know this problem has been asked before but after some extensive searches I can see there are no clean fixes for this.
My Nexus 4 (Android 5.0.2 LiquidSmooth ROM) has started showing ghost touches at the bottom part of the screen. I know there are a lot of explanations available such as digitizer not working, battery being too old etc. But I'm not interested in these hardware issues/fixes.
I have isolated the area of effect as the bottom ~160 pixel height of the device. I then proceeded to use the ADB shell command
wm overscan 0,0,0,160
which removed that portion from the UI. This fixed the effects these phantom touches have on the apps or UI. But a problem still remains that these ghost touches happen in too many numbers and this leaves other usable areas of the screen insensitive to touch. I am guessing this is due to the multi touch limit being reached in that bottom unused part itself. Multi touch testing apps dont pick up touches on the top part of the screen
So my question is, is it possible to remove a part of the screen from the System itself? Ideally a thick black bar of unused area, leaving me with a shorter yet fully working screen? Or atleast is it possible to turn off touch response in that lower part of the screen so that it doesnt max out the multi touch limit?
My Nexus 4's is same too
I think, that ghost touch will work from Screen Digitizer. My Nexus 4's screen digitizer was non-LG's digitizer, it was fake. I need to change that digitizer
I workaround this issue avoid using undervoling in the kernel, and avoid lower temperatures in phone, yes as you read ... this issue give my crazy when my phone was to hot and I tried to cold my phone using one ice cube in screen and back, the temperature of the phone down but ghost touches appears again, so played some videos to warm the phone again and dissapear again.
Don't ask me about how it works, or relation with screen, digitizer or battery, I don't understand but help me to workaround the issue.
I've had my Nexus 4 for a couple years I believe now, and overall it's been a nice device. I've had occasional issues now and then with software (Camera not available message, random powerdowns) but no hardware issues. A couple weeks ago, part of my display stopped responding. The LCD itself shows everything, there's no bars, no visible cracks in the screen. but the left hand side of the screen, I'd estimate about 1/5 the screen in width, no longer responded to touch. The far far left edge, along the very edge of the display, registered, and on the other side of that 1/5 worked fine. The area that was giving me issues was right about where the 'a' key on the keyboard is in portrait mode -- the only location I could press to get an 'a' registered an 's' as well.
This is all being tested with the developers Show Screen Touches and Show Pointer Information turned on.
Then, the end of this past week, it got worse. The entire left half of the display still shows fine, but almost never responds to touches -- maybe 1 in 100 times it will. Thankfully, I was able to get in one of those times and disable my screen lock. It seems to be able to register as far left as an x value ~418. This means the back button in portrait mode, for example, no longer works. To make me even more confused, it seems to register phantom presses. The device can be lying, powered on on my desk, no touching it, and the display starts showing screen touches -- the most common one I see is right about where the word Google is in portrait on the stock main screen. These will continue indefinitely.
All this to say, I suspect my digitizer has had a mechanical failure. Does that seem a reasonable conclusion to you? I like the four inch form factor of the device, and with most new smartphones getting larger and larger, I'm shying away from changing to another device. I've looked briefly at replacing the digitizer -- it seems you can purchase either the digitizer alone or with the LCD, and that when replacing just the digitizer it's easy to accidentally create problems with the existing LCD. Is that true?
Also, the part about having to use a hair dryer to pull the components apart makes me a little nervous. Screws and cables I can handle, but a hair dryer?
Rainshine said:
I've had my Nexus 4 for a couple years I believe now, and overall it's been a nice device. I've had occasional issues now and then with software (Camera not available message, random powerdowns) but no hardware issues. A couple weeks ago, part of my display stopped responding. The LCD itself shows everything, there's no bars, no visible cracks in the screen. but the left hand side of the screen, I'd estimate about 1/5 the screen in width, no longer responded to touch. The far far left edge, along the very edge of the display, registered, and on the other side of that 1/5 worked fine. The area that was giving me issues was right about where the 'a' key on the keyboard is in portrait mode -- the only location I could press to get an 'a' registered an 's' as well.
This is all being tested with the developers Show Screen Touches and Show Pointer Information turned on.
Then, the end of this past week, it got worse. The entire left half of the display still shows fine, but almost never responds to touches -- maybe 1 in 100 times it will. Thankfully, I was able to get in one of those times and disable my screen lock. It seems to be able to register as far left as an x value ~418. This means the back button in portrait mode, for example, no longer works. To make me even more confused, it seems to register phantom presses. The device can be lying, powered on on my desk, no touching it, and the display starts showing screen touches -- the most common one I see is right about where the word Google is in portrait on the stock main screen. These will continue indefinitely.
All this to say, I suspect my digitizer has had a mechanical failure. Does that seem a reasonable conclusion to you? I like the four inch form factor of the device, and with most new smartphones getting larger and larger, I'm shying away from changing to another device. I've looked briefly at replacing the digitizer -- it seems you can purchase either the digitizer alone or with the LCD, and that when replacing just the digitizer it's easy to accidentally create problems with the existing LCD. Is that true?
Also, the part about having to use a hair dryer to pull the components apart makes me a little nervous. Screws and cables I can handle, but a hair dryer?
Click to expand...
Click to collapse
I would say it's most likely a hardware problem with the digitizer. The lcd/digitizer assembly is glued together so it's very difficult to separate the two without damaging the lcd.
Unless you have the tools to separate them properly, it's alot less headache to get the entire assembly already glued together.
Hello everybody,
I have a accidentally cracked Pixel 4. The Display cracks after it falls from around one meter height. I decided to fix the screen and buy a new one. It seems to be not an original Bit the board of the new and the old screen seems to be exactly the same. I opened the phone and replace the screen without any damage. After the screen was inserted I test it if it woks. Success! Everything works (I not tested the touch Funktion yet) after I build most of the things together I give it another try and I recognized that the touch Funktion does not work. No matter how hard I press or hold the connector down etc. I tried many things also a Hard Reset. I never seen such problem before. And my question is: is this the screen, the phone or a software problem? And how I can fix this issue? I am completely confused because I fixed many phones but something like this is new. Regularly the complete Amoled does not work.
If I go to the left upper corner, there is some movement in the screen and this also stays if I release my finger (video).
Video 1
Video 2