Database Develop

[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] Capacitive Buttons and Digitizer Issue

VZW SCH-i800
Recieved unit with only ability to turn off from screen when power button depressed. Screen and capacitive buttons otherwise non-responsive.
Flashing various ODIN Roms gives me the following:
1. No response on digitizer or capacitive buttons as received.
2. Response throughout digitizer except left 1/2" and bottom 3/4 inch and no capacitive buttons. As Tab is rotated, it seems that screen calibration is not correct.
3. In Recovery, capacitive buttons do not work. (Thank goodness for CWM!)
Has anyone seen this before? Any solutions I can try?
I have unbrickable mod hardware mod that I performed after a bad bootloader flash, so I can try about anything.
So far ICS and stock DJ11 allow most use of digitizer with anything else pretty much gives me no screen control.
Nothing solves capacitive button issue.
TIA!!

I had the same problem 2 weeks ago, but it recovered by itself 24 hours later, however this morning problem again, think I'll need to change the digitizer, some China supplier is selling between USD2 to USD40 only, can't even believe it's true or not. Majority USD10.
http://search8.taobao.com/search?q=...all&ssid=s5-e&pid=mm_14507416_2297358_8935934
use this keyword to search, ”P1000 觸膜“

[FIXED]: Phone Laying Flat, HOME/BACK are Non-Responsive

So you've played with changing button sensitivity, heard about perhaps removing the screen protector, but still don't get it?
I think I might.
Try this, let me know if you guys can confirm, then perhaps we need to send info to HTC?
Unlock your screen
Place your phone on a level surface so its curved back can rock back and forth.
Enter the app drawer, so pressing HOME will actually do something.
As gently as you can, steady the phone with one hand, and touch HOME (It should work)
Now, re-enter the app drawer and press quickly on your phone's HOME key. This will cause it to quickly rock back and forth a bit and shake.
Press the home key all you want, it shouldn't work... especially the more you bang on it.
Wait 10 seconds.
Steady your phone again, press HOME gently. It should work.
The theory? Something is programmed in the phone that if it detects rapid shaking, like maybe in a pocket or being handed back and forth during watching a video... to turn off the buttons to prevent undesired actions. BUT, the curved back of the phone naturally lets this motion occur so it's triggering when it shouldn't.
If you're particularly twitchy, maybe that can cause it from time to time while even in hand too?
SOLUTION:
Run calibration tool a few times until the symptom goes away. Try alternating between pressing more firmly or more softly to make a difference. Take care to center your fingers on the letters.
If you experience bad button behavior while phone is on a flat surface, re-calibrate:
SETTINGS->Language and Keyboard->HTC Sense Input->Advanced->Run Calibration Tool

I couldn't replicate this problem. The home button works as intended while being rocked. I also haven't found to have any button response issues that some encountered.

Long813 said:
I couldn't replicate this problem. The home button works as intended while being rocked. I also haven't found to have any button response issues that some encountered.
Click to expand...
Click to collapse
LOL

compact_bijou said:
LOL
Click to expand...
Click to collapse
Heh, come on man... the phone has BOOM Sound, it was meant to be rocked, no?! :laugh:
Serious note though... yeah always have thought the buttons worked fine too and thought other people were crazy...
I lay it flat though casually press them, they go away and don't come back.

Also couldn't replicate it. Basically the home/back buttons work when they want to, which apparenlty is about 95% of the time. The other 5% is just purified annoyingness.
Allegedly HTC has fixed the button problem in 1.29.XXX.12 which so far has only rolled out to unbranded phones in Europe and Asia. However if you have the international phone you can install the newest Android Revolution ROM which is based on the .12 software. Everyone who has .12 seems to agree that the button sensitivity issue is gone.

Re-ran calibration tool pressing normally and it seems to have fixed it.
No amount of shaking or rapid pressing causes the phone to miss a button press.
This is with US Version of phone w/ screen protector.
If you experience bad button behavior while phone is on a flat surface, re-calibrate:
SETTINGS->Language and Keyboard->HTC Sense Input->Advanced->Run Calibration Tool

[Q] Back button backlight not working?

I have a brand new Lumia 920, and I note that the backlight of the "back" button rarelly turns on....home and search backlight works fine, but the back button only turns on once or twice a day.
Is this normal? how to fix it?
Sorry for my english.

All the backlights should come on together. Sounds like you may have gotten a faulty model; warranty replacement should be no trouble. These things happen, especially when the problem is intermittent and may have slipped through testing.

[Q] Digitizer quirkiness after repair

Question for the hardware people!
I'm not by any means a hardware expert, but I like to dabble and learn as I go. I've disassembled my G2 several times (screen+digitizer replaced, flex cable replaced, etc.) and I feel fairly comfortable with what I'm looking at. I recently attempted to transfer everything over to a new bezel, only to get 90% of the way done and find out they had sent me a D800 chassis rather than VS980. That's another story. When I put everything back into my original chassis, though, I now have a goofy issue with my digitizer. When waking the phone with the power button, I have to be touching the screen, or else the digitizer is either erratic or nonfunctional. In other words, if I just push the power button, the digitizer will not accept touches. If the screen times out and I immediately push the power button (before the phone locks), the digitizer will either not accept touches, or will start registering random phantom touches. If the phone wakes up due to a system event (phone call, notification, etc) the digitizer will not accept inputs. To remedy these problems I have to explicitly hit the power button to lock the phone, then hold my thumb down on the screen while I hit the power button to wake the phone again, at which point the digitizer functions properly.
So the question is, what might cause this? My first inclination is that it's some kind of grounding issue, but I'm not sure what I would be double-checking if I were to open the phone again. Does anyone have any DIY ideas or suggestions?
Thanks!!

Edit: Sorry wrong post, ignore my answer.