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] Replaced Nexus One screen, now the screen won't turn on

Ok, so I broke the screen on my Nexus One. These things happens. I ordered a replacement screen, and thanks to numerous online guides, I (thought I had) replaced the screen.
Now, I guess that some other parts of the phone might have become damaged, but I doubt it. The phone seems to work. The touch buttons light up. The unlock gesture gives a slight vibrate. So does the volume rocker when I (seems to) reach the top/bottom of the scale.
But the screen itself doesn't show any response. No backlight (should I be able to see that). Nothing. What could I possibly be missing, I've gone over everything three times, but can't see nothing wrong. I've checked all the connectors everywhere. Somehow I get the feeling I'm missing something obvious....

Are you sure you bought an amoled screen replacement and not the slcd screen? That would cause such an issue.

Or maybe he needs an SLCD screen and not amoled..

I was going to ask if your wifi and bluetooth still work but i suppose you cant really test that yet...
I replaced my digitizer last week and now the phone works fine apart from the Wifi, Bluetooth and the charging pins for the dock at the bottom. LAME!

Maybe two Months ago I replace the full Housing on my phone is no easy task but not too difficult either. Check if you didn't ripped any of the flex cables and if the cables are connected properly. I have a long history of replacing housings and my best advice is to do again make sure you have time.

Exactly the same issue. Did you find a solutions?
I too had a broken screen. So, I ordered one from ebay and replaced it.
Now, it screen does not turn on though the icons at the bottom of screen switch-on.
I can here the sound when volume rocker is pressed.
Also, I believe that the touch is also working as I can hear the unlock sound when I swipe my finger across the screen.
Did you find a solution to the problem? Did I make some mistake or the screen is faulty?
jonragnarsson said:
Ok, so I broke the screen on my Nexus One. These things happens. I ordered a replacement screen, and thanks to numerous online guides, I (thought I had) replaced the screen.
Now, I guess that some other parts of the phone might have become damaged, but I doubt it. The phone seems to work. The touch buttons light up. The unlock gesture gives a slight vibrate. So does the volume rocker when I (seems to) reach the top/bottom of the scale.
But the screen itself doesn't show any response. No backlight (should I be able to see that). Nothing. What could I possibly be missing, I've gone over everything three times, but can't see nothing wrong. I've checked all the connectors everywhere. Somehow I get the feeling I'm missing something obvious....
Click to expand...
Click to collapse

Just months after the Nexus One was released, Google announced that the AMOLED Company "Brightstar" fell short of displays and was unable to produce more displays for HTC, so they decided to move to Sony to make the displays, To determine whether a phone has the AMOLED or SLCD display, The internal sticker on the back side of the screen assembly can be examined; part number 60H00443-03P indicates SLCD and part number 60H00287-00P indicates AMOLED, and as i mentioned, the AMOLED screens are gone so finding a replacement for that model would be merely impossible. I was looking around and thought that i may of found a fix to this, see, the HBOOTs on the devices are both the same except the top code of the screen that determines the screen type, if you were to flash the SLCD HBOOT, you might be able to retrieve a working screen, well its probably worth the gamble anyway since you probably are not going to find a replacement in a while.
EDIT: And after moments of posting, i found a AMOLED screen seller that will ship to Europe! http://www.ebay.co.uk/itm/LCD-Scree...K_Replacement_Parts_Tools&hash=item4d06825672

Dude, I dropped my n1 and shattered the screen almost 2 years ago. Bought a replacement screen and tried to replace out on my own. Needless to say, it didn't go so well, my n1 was is a paperweight. Good luck man! I miss my working n1...
Sent from my Galaxy Nexus using xda premium

Cracked screen - need digitizer?

I have a Galaxy Captivate from a friend who has dropped it and shattered the screen. The bottom 4 touch buttons light up when the phone is powered on, he claims that there was a very faint image on the screen but so far it hasn't displayed anything for me.
Is it likely that a touchscreen + digitizer can fix this, or is it likely that something else is wrong with the phone? The touch buttons lead me to believe that I may be able to replace the screen + digitizer and have it work again =/
Opinions?

Verizon LG G2 Screen Issues... NOT the turn on then off issue

I have recently purchased this phone via swappa and haven't had any issues prior to this and that has been three weeks (other than a light leak).
The issue that is happening is the LCD will not turn on. When the phone is unlocked via knock on or power button you can move your finger over where the lock circle would be and feel the vibrations showing that it does register the touch. Then usually I would just hold the power button till it rebooted and this would sometimes fix the problem, on a side note the boot LG logo and boot animation do not show up during this time simply the lock screen would randomly appear.
That is problem, now on to what I tried to fix it. I have put on an entirely different rom and the problem persists, I have also flashed a different kernel on the stock rom with no avail. I at first thought it could be due to a faulty proximity sensor, but the last time the screen was on I checked it with sensor box. One way I have been able to reproduce the problem is after locking it putting it in my pocket and waiting around five minutes, this then will make it so the LCD does not turn on ( Which makes it seem like it has something to do with deep sleep). Also something I just found since I was actually able to find the power off button, the screen also won't turn on when the phone is off and plugged into the charger (this makes it seem like hardware issue). It seems like as long as I keep the phone from going to deep sleep the LCD will turn back on.
Some of this makes it seem like a software issue other things make it seem like a hardware issue. I just was wondering if anyone had any ideas or if I need to buy a new screen, if the mobo is bad, or if I could fix this with software. Any and all ideas are welcome.
Thank you all in advance.

[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.