Database Develop

D-pad down button, no longer works

So I spent the last hour or so searching for answers and have yet to find any so I figured ask all of you for some help diagnosing my Tilt. Last week it started to exhibit the following problems, what I need help determining is if the concensis is that I may have gotten the internals damp or if I have a hardware issue.
Symptoms;
1. Down D-pad button no longer functions, down track wheel works fine.
2. Sliding out the keyboard causes the phone to beep 10-20 times before you can actually start to type.
3. Random results when using the touch screen. it works 90% of the time but the other 10% if I try to say open an email by touching "in box" actually opens SMS inbox and starts to scroll through all the existing SMS messages.
I am thinking there could be a problem with the ribbon cable that connects the keyboard to the touch screen, or again, it could be wet.
Idea on a solution or further t-shooting to figure this out?

[Q] It Anyone Else Having Touch Button Problems?

Is anyone else experiencing the occasional mixup when hitting the back button? As not always, but many times regardless of the application thats open, I'll hit the back button and the search will come up and I wondering whether thats a common problem or a sensor in my phone is defective and I need to exchange it for a new one...
Thanks in advance

im having a different problem with the buttons. a lot of times my first touch wont register and i have to press it multiple times for it to be recognized.

I've noticed that my touch buttons aren't as sensitive as the touchscreen, and that I need to use a lot of pressure to get them to activate on the first try.

not alone there.. same issue here. I have a clear screen protector over them though.. though it shouldn't be a problem.. I've had the issue even before the protector so..

I have a problem with the back button too, not the other ones. However, when I press a spot a little to the left of the back button and not exactly over the button, it seems to register the press correctly.

I have found that the buttons just do not like any other finger than the index finger try to use the thumb and it will go to search or do nothing.I also returned my first phone as the buttons were terrible 80 percent of the time they would not work.So there maybe be a flaw in some of the phones as this one works fine even with the phantom skins on.The first phone would not even register a response with the skin on.

The buttons on the Captivate suck.
Buttons, as a construct, are well known.
The functional priority of the button is not a mystery and hasn't been for 100 years.
It has to click or otherwise give the user an indication the button has been pressed far enough to take effect.
It has to be tacticle. You have to have some way of knowing that your finger is on the button before you press it.
You have to have some leverage to put enough force on the button to make it move.
It has to be about the size of a finger tip.
It has to be visible. If you can't see it you can't press it.
It has to be different than other buttons that are millimeters from it.
It has to react the first time you press it, or you will naturally press it again, achieving unwanted results.
In all of the above, the Captivate fails.
The T-Mobile Galaxy has more a lot more real estate below the buttons to allow your fingers to get on to them, and a raised ridge on the rear surface of the phone exactly to give your other fingers something to grip against to increase aim and pressure.
But the Captivate has a nice lot of space at the top OH YEAH!

The only problem I have with the buttons is that I can't see them in a dark room
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm getting something similar. Sometimes when I hit the home button the search button blinks as if I had pressed it, then brings up the search screen. On my first captivate (mfg. date 7/16) sometimes it would happen once out of every hundred presses and sometimes it would happen 3 out of 5, very inconsistent. I traded that one in for one with a later manufacturing date (8/10), and my new one does it too but maybe only 1 out of every 100-200 presses. The fact that the search button blinks makes me think it's some kind of short/hardware issue. The back button has only triggered a search for me once, and that was on my first phone.

So this is a hardware issue or a software issue?
My back button on my phone must be pressed 4-5 times sometimes before it will register. The phone did not have the issue when I got it, and a friend of mine who has the Captivate as well does not have this issue.
It may be my imagination, but the phone seems to register touches better after I run a task killer or after restarting the phone, but tends to have issues when multiple apps are up and running.

I was having a button problem as well but fixed it by upgrading to JH3. h t t p://forum.xda-developers.com/showthread.php?t=767666
Your mileage may vary but it worked for me.

May be my imagination, but it seemed to be more isolated to back button on JH3 than JF6 on my machine. My perception is that if I take an additional half-second pause before pushing back button it registers more often. Do not believe it is hardware though. I believe that your home page(button), settings (button), and search(button) all reference something that resides in permanent memory(ROM) whereas the back(button) is trying to recall something that is in temporary memory (RAM) and possibly similar to lag issues may be related to Samsungs somewhat proprietary file allocation system. I am by no means computer literate enough to ponder concept any deeper than just mentioned.

I was having a problem with pushing the home button and the search would come up. I took it to a AT&T store and because I was still in the first 30 days they swapped it out for me.

i'm having a completely different issue with my touch buttons. my back button will register multiple button presses even when i'm nowhere near it. it's quite frustrating to be in the middle of an app and all of a sudden the back button goes off 3 or 4 times and gets you back to the home screen. i've tried searching the forums for some resolution or to see if someone else has had this, but not yet.
Edit: I must not have searched thoroughly enough, found another thread on this issue. http://forum.xda-developers.com/showthread.php?t=858873&highlight=back+button+issue&page=2

[Q] Screen sensitivity

I am not sure whether it is my mind playing trick with me or not, but I feel like my phone is less sensitive after I did the hard reset (power+volume down). Sometimes I need to press 2-3 times because the first light tap was not detected.
So is there anyway to increase the sensitivity?

I have the same problem, but no idea that is the hardware or only software problem.....

Fresh owner of this Optimus 2X in France, in our community, frandroid.com, we encounter the same problem , I think this is a software issue.

Did someone already contact LG??

Maybe they should include this into the bug list thread.
May I know were you guys having this problem since it is out of the box? or after reset?

I have the same problem started from day 1 till now

I have the same issue and already thought I'd be the only one having this problem.
I would not say it's a problem with sensitivity, but it feels like the touchscreen goes into some kind of sleepmode where then you need to press a second time, to wake it up.
Continuous touching is no problem. (like when typing rapidly on the keyboard)
This video is not from me, but it shows the problem.
Have a look at 13:28 and 13:37. The reviewer tries to hit the "Ackermann" entry, but the touchscreen does not recognize the touch. At 13:37 the guy has to press another time to get the entry selected.
http://www.youtube.com/watch?v=VRid-Yhu7Gg&feature=player_embedded

Yes! The touchscreen is definitely less sensitive than my old HTC Hero, and gets quite frustrating sometimes when a scroll misses the first part of the movement or a click is missed.
Sent from my LG-P990 using XDA App

just in case, are you guys using 20110218 baseband too?

The same problem here. If I unlock the screen and then tap on any on screen apps, I need to touch again for it to open. Only the first time though, after that it function ok. I think this is a bug and needs to be fixed... I have my pc for double-click.

Yep, count me in. Same problem here. Sometimes screen taps aren't registered. Will do some research later on, but I think it's a software problem. (maybe you have to tap 2x as fast )

Hi,
same problem here!

Potentially a driver issue. A Nexus S user had a similar issue in this thread: http://forum.cyanogenmod.com/topic/18431-tuning-driver-to-deal-with-unresponsive-touchscreen/
He managed to tweak the driver and it works fine now. Need to know C++ (I think?) to understand though.

9mmBullet said:
Potentially a driver issue. A Nexus S user had a similar issue in this thread: http://forum.cyanogenmod.com/topic/18431-tuning-driver-to-deal-with-unresponsive-touchscreen/
He managed to tweak the driver and it works fine now. Need to know C++ (I think?) to understand though.
Click to expand...
Click to collapse
I see, then probably they will fix it on the next update/gingerbread?

Same issue here.

Correct me if I'm wrong, but the problem seems to be that the screen has zero tolerance when it comes to tapping and swiping together. If you tap and slide your finger a bit directly after the tap, the tap is ignored. In other words your tap has to be a steady tap when you click on a button or an app. Right on the spot and with no swiping or sliding afterwards. I can't reproduce this on any of my other devices.
Ergo, it seems that the natural tapping I'm used to isn't working on the x2. It seems like I have to adjust my tap. I think that this could in principle be solved with a setting somewhere, because clearly the x2 is capable of registering this in for example a web page.
The great thing of this is that you can safely tap and swipe in the app drawer to scroll up and down or left and right. The downside is that a tap with a little swipe isn't registered at all. I would say that LG has choosen here for a wrong setting.

My personal experience about screen sensivity.. can you confirm if it's the same for your device?
I noticed a strange touch response.. and after some tests, I can say that the touch screen and icons are influenced by the surface where the phone was put!
with the phone in my hands, it's all ok (only sometimes - rare - I need to tap more than once).
If I put the phone over a glass surface (like a glass table) without touching it with both hands, the touch and the icons not respond!! NEVER!
If I put the phone on my scanner the touch screen works ok, but the icons not (or only few and rare taps was detected).!
If I put the phone over my big Onkyo amplifier.. It works like in my hands.. or better!! even without touching with hands.. only with a finger!
Put it back on my glass table.. and all stop working again. If I put a aluminium foil under the phone (between phone and table).. the touch and the icons works again !!
If I put it on the bed.. it don't work.
LG support say that they have tested the phone about this issue after my report.. but no strange response was detected by them. I don't know if they really tested it..
Try it and let me know what you think about!

tested on glass surface, I can press and swipe through pages with a finger without problem.
it is true that my device is not so responsive, but aint reaching that level yet

i read about a similar behaviour on other devices because some devices need a proper grounding for the capacitive screen to work correctly. You can find this problem via google.
Some devices have problem in a car-mounting, for example.
But i think thats not the problem the thread-opener talked about?

Guys I'm looking to get this phone and after reading Engadgets review of the X2 where they mention that the screen is not as sensitive to the touch as other phones I got a bit worried and started googling which lead me here!
Is this true? The screen isn't very sensitive and you have to apply more pressure than other capacitive phones?
I know that the OP is talking about a different issue but I reckon LG will get that sorted out via software update, or at least hope so!
Please do post your experience about the screen sensitivity of the X2 as this is putting me off. I currently have the Motorola Milestone 2 which is very sensitive to the touch even with a screen protector on it.
Cheers

Home button is too sensitive.

Hi all,
It seems my home button is way too sensitive, it sometimes(I say sometimes because it seems to vary) senses a touch from up to 3-5mm away from the screen. This becomes problematic because since it's range is so big, it can pick a normal press as a long-press or even seem to be pressing by itself and it's pretty annoying. Is there a way to lower/calibrate it's sensitivity or even better, to move the "hold" functionality to the back or HTC button?
This wouldn't have bothered me and I haven't even noticed it until I made a very favorable (for me) exchange with some guy and he calls me the next morning to tell me I tricked him because I gave him a faulty phone and the button presses itself, so I had to tell him I'll look at the phone and try to see what the problem is and if I can fix it by tomorrow, so any help would be appreciated!
Also, the guy said in 2 instances he put the phone down and it kept pressing itself.
Edit: apparently the problem might be liquids(water or sweat) on your finger, explains why it would keep activating after your finger was taken away. That moment when you're using a product wrong and blaming it on malfunctions. Can anyone replicate this for me? Wet your finger and press the home button, see if it registers as a long press(i.e. opens google now), I want to be sure it's not limited to my device.

Unresponsive parts of screen?

Is anybody else experiencing unresponsive screen on some parts?
Couple of days ago I started having problems with letter "a". It wouldn't react unless I pressed it all the way at the left side of the key, which I attributed to being close to curve of the screen - if the phone was in my left hand then I pretty much punched it on the right spot every time, so I thought it had to be it. It's an ongoing thing.
But now I was making a video in Quik app, and in one of the screens the play/pause button is right at the place where the letter "a", and I found my self having to press the key like 10 times in a row before it reacted - on a couple of occasions. I doubt it's some sort of memory issue since this thing is a beast and no way a couple of pics in Quik app could make it unresponsive.
I am utterly crushed now, since I love this phone to death. I really hope it's not a defect :crying: