Database Users

Keypad + screen issues (after reassembling)

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?

[Q] Proximity sensor funkiness?

This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?

I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App

I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.

I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.

ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?

Yeah, ditto that - how do recalibrate the sensor?

Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.

I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#

Ok, mine says No Detection. Is there anyway to set the value?

One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.

If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.

ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?

samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....

Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps

What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?

BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?

another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?

rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned

S4 screen stays off , please help.

Hi,
I'm hoping someone can help me determine if I have a defective phone or no. Basically what happens is that when I receive a call and I bring my phone to my ear the screen turns off (as it should ) but when I move the phone away from my ear the screen stays off and I have to press the power to bring it back on. Mind you this started happening 2-3 weeks ago, before it was fine bring phone to face/ear screen turns off , move it away from face the screen would turn back on.
Now logically it seems the proximity sensor might be having issues but it works fine when i bring it to my ear so maybe that's not it?
This is quite annoying whenever I'm on a call and have to press numbers, end calls, go back to what i was doing I have to continuously press the power button. I googled these issue and a few people are reporting the same thing. but i didn't see any solutions or answers.
Thanks for any help.

Ive had the same thing happen. Go to Settings > My device > Call Settings. Look to see if the option to "turn off screen during call" is enabled/disabled.

I feel like you have a a custom rom, or maybe just rooted with some cpu clocking going on. whats usually going on is your phone is going into a deep sleep where it's energy is to low to even force itself to wake up.. but it's still alive not dead, just unresponsive (I feel like I'm talking about malnourished human beings). don't let your phone get too weak, set your minimum cpu speed a little higher than what it is now, and make sure it gets more complex carbs.
Sent from my Galaxy S4 using xda app-developers app

soraxd said:
I feel like you have a a custom rom, or maybe just rooted with some cpu clocking going on. whats usually going on is your phone is going into a deep sleep where it's energy is to low to even force itself to wake up.. but it's still alive not dead, just unresponsive (I feel like I'm talking about malnourished human beings). don't let your phone get too weak, set your minimum cpu speed a little higher than what it is now, and make sure it gets more complex carbs.
Sent from my Galaxy S4 using xda app-developers app
Click to expand...
Click to collapse
I have not changed anything on the phone, it's stock and simply have accepted the carrier's OTA updates and that's it.
And also I should have mentioned that I did check the call settings, I have the "turn off screen during call " enabled, before posting here I had that option disabled but then the screen would stay on during a call, which is worse cause then the phone gets hot near your face and don't want a bright light next to me.
Also I did a hard reset and factory wipe and nada, still doing the same thing .

same
I have the exact problem with my s4. I will post any findings.

Got It
For me, it was dust inside the phone in front of the sensor.
How to fix
1) Remove back of phone along with the battery and GSM and SD cards.
2) Remove 4 screws around the back of the speaker. Then pry out ward from the battery compartment and pop out the speaker housing.
3) Remove 5 screws from the rest of the back. Use your thumb nail and start at the bottom and work around the phone to pry appart.
4) Remove 1 screw from the camera and sensor housing. Pry the metal cover off by starting at the top and pry upward.
5) Take the camera out by on snapping the bottom snap plug with a flat head tweaker. Then remove front facing camera.
6) Lastly take out the sensor snap plug and tilt the sensor out. Blow air inside the housing .
7) reassemble.

[Q] Proximity Sensor Driving me nuts

Hey
My proximity sensor keeps stuffing up. When I make a call, and put the phone to my ear , it turns off the screen but when I release the phone from my ear, the phone screens remains off and I cannot access the phone untill the other party hangs up
This is a real pain when they do not answer and their voicemail comes on and I need to leave a message. I have to turn off my phone when this happens
I have fixed this but it only remains fixed for about a day
I have cleaned it, blown in the area where the proximity sensor sits with a straw ( did not have air compressor can) worked for about a couple of days then it stuffs up again
Not sure what the hell I can do to fix it now.. Buy a new sensor? I have a screen protector but there is a cut out where the ear goes

Go into settings, accessibility, then tick 'The power key ends calls' It won't turn off the screen.

I had that problem, I took the sensor out and wiped it, seems to be fine now. I saw a video online to help me, not got the link readily at hand though

[Q] Screen goes black when I make a call

My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........
Does anyone out there have any idea whats happening and what the fix may be?
Thanks for any help

Remove your screen protector.

Blacksmith5 said:
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........ Does anyone out there have any idea whats happening and what the fix may be? Thanks for any help
Click to expand...
Click to collapse
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.

Proximity sensor turns off screen when you put it to your ear to avoid your skin touching the "End call" button or something else

kbakalar said:
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Click to expand...
Click to collapse
Thanks for that info I had not thought about that... That may be cause of my problem.... I will have to figure out a solution
Thanks again

Didgeridoohan said:
Remove your screen protector.
Click to expand...
Click to collapse
I am not using a a "screen protector" But thanks for the input

Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...

Didgeridoohan said:
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Click to expand...
Click to collapse
I did as you suggested and the results say 2" uncovered 0 when covered

Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.

Didgeridoohan said:
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Click to expand...
Click to collapse
I'll keep looking for a solution.......... It's a pain especially if if I have to respond to a VM and hit a Number.......
Thanks again

I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.

Man of La Mancha said:
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Click to expand...
Click to collapse
Yes I resetthings so I only have to hit the power button to end a call Thanks for all the help