yashsingh1/xdaforums huggingface dataset:
[Vibrant General] dex1701:
I've been having this problem with my Menu button. I don't remember when it started, but it's really annoying. The other three buttons register a press every single time I so much as brush them with a fingertip. The menu button requires me to apply actual pressure or to actually tap it with some force, sometimes several times, to register a button press. I've tested the theories presented in this thread by others...so far it really seems like a hardware issue...at least in my case. Hard reset, putting the phone down, backlights on or off, programs running, etc....nothing makes a difference. My 14 days is up tomorrow...crap.
[Vibrant General] Shane_pcs:
As long as you request the RMA# before your 14 days are up you are good. I have 30 days for them to receive it. And yeah i just called customer care.
[Vibrant General] mrxela:
Is TMO defnitevly saying that it's a hardware issue? This morning my home button is back in action, both with led's on and off.
[Vibrant General] Shane_pcs:
T-Mobile isn't saying anything. It was samsung support that said it was a hardware issue. T-Mobile agreed to replace it when it was still happening after a factory reset. I am including detailed instructions with my RMA on how to recreate the issue to avoid the tech just pushing the button and saying it works and shipping it back. But I am nervous that the one time they test it it will work fine.
[Vibrant General] RadAway:
I have a similar issue, except it's the back button that's acting up. I have to press it very precisely to get it to fire. The other buttons work fine.
[Vibrant General] mrxela:
I wonder if any developers can offer their feedback on this issue? Since capacitive buttons are solid state, this would make it likely a software related problem.

I read many N1 related posts that said that 2.2 improved button sensitivity/usability.

My first two G1 units were defective, but third one lasted since launch day till now without any issues.
[Vibrant General] Keslynn:
Just checking to see if there's any more information on this issue. Anyone been able to determine the hardware vs software question?

My Home key worked perfectly one whole day out of the blue. Now it's back to its old tricks. The severity of the problem no longer seems to be related to battery level. It's almost always more responsive with the backlight on, but that's the only consistent thing at this point.

Also, as an informal poll (for my curiosity): how many of you having unresponsive button issues have kept your phones? How many have exchanged or returned?
[Vibrant General] mrxela:
I spent the last several days trying to troubleshoot the issue. Removed ClearFreak protector, just in case it might have been causing interference. Factory reset, no change.

Restored stock configuration, removed root. No change. I can reproduce the problem pretty consistently by browsing to XDA forums :D and changing phone to horizontal orientation. After loading a few pages and after LED lights shut down, home key stops responding.

I tired this with different battery levels, on thing that was noticeable but in no way conclusive is that when battery temp was below 80F home button was usually responsive and the hotter it got, the less responsive it became.

This could be heat related, as battery/phone heats up copper runs around capacitive button expand and either short or expand far enough to stop working.

I called in TMO CS, they advised that i send the phone in as buyers remorse within 20 days of purchase and they will send out a new set.

TMO also mentioned that there were no known issues with keys not being responsive and said it was probably hardware defect.
[Vibrant General] junkdruggler:
Mine doesn't show the sake problem... Actually mine is over sensitive... I have a hard time long pressing my menu and home... Can't bring up recent apps or the keyboard sometimes... hasn't ben too big a problem, but annoying sometimes..
[Vibrant General] Shane_pcs:
My replacement vibrant arrives tomorrow (8/4) and I will run it through the complete test. If I fail to be able to recreate it then I am going to conclude that its hardware. I am pretty sure the heat affects it though, which would scream hardware.
[Vibrant General] jkang29:
I received a replacement phone several days ago. so far, all buttons work flawlessly. My guess is that it's hardware. My recommendation is just return it and get a new one. I am now very happy with it now.
[Vibrant General] bromat80:
After a few days of owning my phone (bought on launch) my home button became very unresponsive and I tried uninstalling apps, factory reset and a bunch of other stuff and it still didn't work right. For the last week or so it has been working great. I don't know what fixed it but since the factory reset I have rooted, uninstalled the bloatware, used autostarts, started using set cpu and stopped using a live wallpaper and I haven't had a problem since.
[Vibrant General] mrxela:
At first I was thinking that it is software related and it very well might be. Apparently 2.2 improved N1's button sensitivity, maybe 2.2 for Vibrant will fix all this as well.

However, there are a lot of posts on other forums about this same issue. TMO forums has 5 page thread on the same issue and most of the folks there run stock non rooted.
[Vibrant General] DKYang:
If you guys are still using the factory screen protector, then take it off. I had the same problem on my second Vibrant, until I took it off. It's been a week and everything is still working well.
[Vibrant General] Silrocco:
Funny that I came across this thread today because, yesterday I called TMO's CS in regards to my Vibrant's Menu button not responding to my touch. CS asked me to perform various test, including a Master Reset. No success, so the CS transferred me to Loyalty CS and are replacing the phone under Buyers Remorse.

So, I can conclude that it is a hardware issue from others posting same issue and a great post from one member here on this thread conducting vigorous test on temperature. Great Job!! :)

My new Vibrant should arrives on 8/6. :D
[Vibrant General] mrxela:
Got my replacement phone yesterday. So far all the buttons are responding well. Hopefully after installing Realook responsiveness won't decrease.
[Vibrant General] dex1701:
I've been having this problem with my Menu button as well. Unfortunately, my 14-day remorse period is up. The button seems to work fine when my battery level is above 80% or the phone is plugged into a charger or computer. Below 80% the sensitivity of the button begins to fall off.

Now I'm pissed off. If I get a warranty replacement I'll probably get a refurb unit that has other problems. Really, really not happy right now. :mad:
[Vibrant General] mrxela:
TMO CS told me remorse policy was 20 days from when you received your phone, not from when they sent it. Or try customer loyalty dept.
[Vibrant General] jkang29:
I had my replacement phone for about a week.

Overall, I'm happy with the new phone; however, I noticed that now my back button has a minor issue. It was my home button initially. It's not as bad as before, but still not as responsive as other buttons. But I'm keeping this phone...
[Vibrant General] Woolaroc:
Has there been any update to this issue? I started noticing yesterday that my home button has become less responsive when the led light is on. I bought the phone about 1 week ago.

I'm afraid that returning would just result in another faulty phone and the store is 45 minutes away from me.
[Vibrant General] Blown 89:
My first Vibrant had reception issues, this one has a home screen issue. Some times it works and other times it doesn't unless I place my entire thumb on the button. I'm past the remorse period so I'll see if it goes away with 2.2. If it doesn't I'll take it back and raise hell until they give me a replacement. All of the buttons responded fine on the first phone I had.
[Vibrant General] SugarMouth:
My first Vibrant had great buttons, my replacement phone has a home button that needs several presses at times.
[Vibrant General] johnnyh64:
Moisture in fingers??

I thought I had the problem as well, but it's been quite some time since it happened. I'm wondering if it might have to do with the moisture in your fingertips? This would make sense at moisture is a conductor and it would describe the intermittent aspects of the problem.
[Vibrant General] Woolaroc:
It's funny you mention this, because I have noticed this as well. Just peculiar that it doesn't affect any other button.
[Vibrant General] Goog1e Phone:
my home button is not responsive once the back light of the buttons go off. When the light is on, then I have no problems.

Sent from my SGH-T959
[Vibrant General] MV10:
We have four Vibrants in the house. One has a serious, persistent problem with the Home button, the other three always work just fine. Oddly, the one with the problem has the fewest apps installed.

It isn't mine, and she doesn't seem to mind, though, so I'm not going to make a big deal out of it.

Like the person above noted, when I messed around with it a few days ago it seemed like it was mainly a problem when the button backlighting turned off. She still has the haptic buzz thing turned on, and I can feel the buzz response, sometimes three or four times before it responds -- and not spazzing out pressing it repeatedly, but giving it the usual amount of time in which my own Vibrant would normally respond.

Pretty strange.
[Vibrant General] lelik827:
I've had the home button problem for like two weeks now. Finally removed the bit of screen protector covering the buttons and it's working perfectly so far. I actually have half the buttons covered by it still and no problems. Ill post an update if it stops working again.
[Vibrant General] Gix0r:
I'm having this problem with my Home button as well. Details:

-Galaxy S Vibrant, rooted

-Bestskinsever screen skin.

-Home button ONLY works when the backlight is off. I can tap any of the other buttons repeatedly anytime and haptic feedback confirms the press, but the Home button absolutely will not register until the backlight goes out. This makes me think maybe it's a software issue?

I'm going to try cutting my skin where the buttons are located to see if that helps at all. I don't see why the skin would only affect one button though. Otherwise, I guess I'll exchange it.
[Vibrant General] lolcopter:
is everyone experiencing this problem using a screen protector?

because that seems to be the most common denominator
[Vibrant General] Oniyuri:
That seems to be the case doesn't it? So far, we've been using realook and it's been working perfectly.
[Vibrant General] lolcopter:
To be fair, the op said menu button lol
[Vibrant General] Oniyuri:
Lol, yeah caught that at the last sec. Edited post to fit thread. I'm still not used to using the xda app yet.
[Vibrant General] karmasore:
I was having some major problems with my home button not registering. I cut the bottom off my realook so th buttons are no longer covered. I have not had a problem with any button since. I complained to realook about it and they sent me two new screen protecters.
[Vibrant General] ColbyRyptos:
Screen protector should not ber on the actual buttons..its not part if the screen lol
[Vibrant General] Gix0r:
Actually, the buttons are a part of the Glass front of the phone and every screen protector is made to fit the whole front.

Anyways, as many of you with Google Voice installed have probably noticed, the latest version is EXTREMELY laggy. In my search for the previous version of the app, I came across a post saying uninstalling and reinstalling the current version helps a lot with the lag, so I decided to give it a shot. Since then, my Home button has been MUCH more responsive. I used to have a GV widget on my homescreen as well, but have not re-added it. This may be a coincidence, but for those of you with GV installed, give it a try. This makes me think the issue is software related after all. Google really needs to fix these bugs with Voice ASAP!
[Vibrant General] Samcrow:
Home Button

I've been experiencing issues with the home button responding, it's to the point that it won't even respond at all, the other three buttons work perfectly. I'm using Phantom Skinz for my screen cover, similar to Reallook, anyway i lifted the screen cover off the buttons and sure enough the home screen responds just fine. That sucks cause I now need to replace my screen cover. So as far as my phone is concerned no hardware/software issue... yet.
[Vibrant General] Gix0r:
Update/bump: Uninstalling GV must have been a coincidence as the problem is back. I even downgraded to the previous version of GV. I can consistently replicate the problem with my home button though. It ONLY doesn't register when the backlight is on. When the backlight is off, it works every time. I suppose this could be hardware related, as in the Home button only registers presses when the backlight is off for some reason. This is really frustrating me as I don't really want to have to exchange it. Anyone else have any updates on the issue?
[Vibrant General] natecglenn:
I have had it recently but I say just go ahead and replace it as long as its under warranty cause after 3 replacements tmobile updates you to another phone of equal value so then the mytouch hd will be out or something better. I'm not saying do it for that reason alone but if you can never get a phone that works atleast you have a back up plan without spending cash.

Sent from my Samsung Vibrant
[Vibrant General] Gix0r:
Initiated an exchange today. Luckily Amazon has a 30 day policy. They said I should have the replacement in one business day. Fingers crossed it has no issues.
[Captivate General] cropythy:
Are the touch buttons below the screeen really dull for anyone else? I just noticed how dull mine are compared to a coworker's vibrant.

Posted from Samsung Captivate
[Captivate General] uberamd:
Mine aren't very bright compared to my Nexus, I think its normal. The main issue with me is that they shut off WAY too quickly.
[Captivate General] abezapata:
They are meant to be like that. In my opinion they are a lot better than the Vibrant's because the brighter buttons draw attention away from the screen.
[Nexus One Q&A, Help & Troubleshooting] mr_raider:
Looks like I got one of the last N1's before they became extinct this week.

I must say, it is head and shoulders above the magic in termes of build quality.

A few q:

I miss the hard buttons though, I seem to hit the home soft key all the time when using the trackball. Any solution to that?

Also, it seems the side of my thumb is not "capacitive" enough to swipe the screen. I have to use my index! Is this normal? It seems my magic screen was more responsive.

On a more serious note, mine came with Eclair 2.1 update. I used the shaved battery method to root successfully and I'm now on FRF85b. What is the proper procedure to move up to frf91 without loosing root.
[Nexus One Q&A, Help & Troubleshooting] maRioHD:
android.clients.google.com/packages/passion/signed-passion-ota-43546.cc653ee4.zip

Sorry I can't post the url to the update, you got to copy and paste it. But I suggest you visit the post on how to update your phone to frf91, since you might not know how to manually update already. It is on the 3rd page of topics in this section.
[Nexus One Q&A, Help & Troubleshooting] Enndr:
I'll take "Don't come here just to advsrtise your forums for 500$ Alex.

Please at least add something constructive if you're going to solicit your site.
[Nexus One Q&A, Help & Troubleshooting] mr_raider:
Will this hose my custom recovery?
[Nexus One Q&A, Help & Troubleshooting] nxt:
When you're holding the phone and swiping the screen with your thumb on the screen side opposite your hand, it might be your hand is touching/reacting to the screen, so it's not reading your thumb.

The Nexus One screen is very close to the edge of the phone so your hand probably is manipulating the.screen.

If any is that makes sense to you.

Sent from my Nexus One
[Nexus One Q&A, Help & Troubleshooting] mr_raider:
you sir, are god among living men :D
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
Ok, before someone goes on a tangent about how there are threads about this, let me start by saying i know, i've read over them, and i'm still stuck.

I went through this thread http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=695243 and tried the steps.

I also tried following these steps: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ The update.zip flashed like it was supposed to. After rebooting the phone, still no Go.

It looks as if it's going to work, after typing reboot in connectbot, phone boots back up without it working.

When trying to use fastboot, it gets hung at "waiting for devices". Device manager in Win7 does not show anything for the phone (the phone also does not show up on three other computer, 1 Win7, 1 Xp, and 1 Vista).

I've also followed these steps (except where noted)

Press & hold vol down and power on the phone

Select fastboot by pressing the power button

(Could not do these due to computers not seeing device)

Make sure in device manager the driver is installed(Win 7 x64 downloaded them automatically)

Open command prompt like you would to use ADB and type

fastboot oem boot

It will give you a log, look for the line that says INFOCID is SPCS_001, if it says something different, then use the generator below to create one(or hex edit the one I posted)

Download the mtd0.img attached or use this CID generator made by stevebrush over @ Modaco to create a custom one

Download the flash_image attached

Unzip both zips and copy both files to the SD card

Open a terminal emulator(I used ConnectBot) and type

su

cat /sdcard/flash_image > /data/flash_image

cat /sdcard/mtd0.img > /data/mtd0.img

chmod 755 /data/flash_image

/data/flash_image misc /data/mtd0.img

reboot

I'm downloading a stock rooted rom now to try. During this time, it started with Fresh's previous Rom, after i used the update to go to his current rom. Since then, i've tried EvoNonsense, Damage Control, and another that i've now forgotten.

Downloading Caulkin's 1.47 rooted now and flashing.

I'm sorry if this seems like something i should have found in a search, but i really didn't find anything that looked like it'd work for me. :(
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
And yes, it is plugged into the computer, not the wall.
[EVO 4G Q&A, Help & Troubleshooting] one2sas:
I had this issue a couple of times and what I had to was add to it...." or chmod u+x /data/flash_image"

This is found in a later post of the same thread. I was about ready to pull my hair out. I hope this works for you.

In ConnectBot make sure you pick local, the first time I forgot (total blonde!)

su

cat /sdcard/flash_image > /data/flash_image

cat /sdcard/mtd0.img > /data/mtd0.img

chmod 755 /data/flash_image or chmod u+x /data/flash_image

/data/flash_image misc /data/mtd0.img

reboot
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
Ah, i read the "or" as in "type this, or that".

I'll try that. Thanks!
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
I receive "unable to chmod or: No such file or directory".

This is after putting Caulkin's 1.47 rooted stock rom on.

If i leave out everything past "or", it works fine, reboots, but still no usb functionality.
[EVO 4G Q&A, Help & Troubleshooting] one2sas:
Try it again, but unplugged from the computer.
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
Same thing:
[EVO 4G Q&A, Help & Troubleshooting] one2sas:
What is mtdp0?

Worse comes to worse...re-root your phone...since it can see it via usb charging.
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
That was a typo. The next line was the correct line.

Yea, short of charging, the usb port won't do anything else. :(

I'm about to flash a stock rom on to it. After that, I'm at a loss. :(
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
Looks like flashing back to a factory rom didn't do anything for me either.

How can i get the amon recovery off of here so i can bring it to Sprint and have it looked at/serviced?
[EVO 4G Q&A, Help & Troubleshooting] guesswhatimevan:
I had this same issue with my usb connection and no one seemed to be able to fix it. I went back to the stock rom, brought it to a sprint store and they replaced it right away.

Edit:

So how do you root without breaking usb? That's what's holding me off from rooting my new phone now.
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
Bump, still no usb functionality.
[EVO 4G Q&A, Help & Troubleshooting] pseudoremora:
Why did you make two threads about the same issue? I can help you, but answer the question first. One that's going to be justifiable.
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
I don't believe i did.

The other thread was about having the AmonRa recovery replaced by the stock Evo recovery.
[EVO 4G Q&A, Help & Troubleshooting] pseudoremora:
From the other thread:

"I still cannot use any usb functionality other than charging, and i'm running unrooted OTA1.47 now."

So, I'll repeat my question.
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
Let me grab the title of that thread for you since you've obviously missed it in your fit of "let me smack some noobs":

"Need to go from AmonRa to Stock Recovery"

Here's another part of it you might have missed:

"I'm at the point where i'm needing to get the AmonRa recovery off and the factory recovery back in place, but i can't find out how to do it."

And the final part of that thread:

"I see a few posts that say to run the ruu, but that involves running the exe while the phone is connected to a windows workstation through usb. With no USB functionality, i'm kind of at a loss on how to proceed."

So, as you SHOULD be able to tell, that was a thread created to hopefull find out how to return the phone to %100 stock in case i end up having to return to Sprint for repair, not about hacking the phone to fix the USB port.

So, this thread = Fixing USB port

Other thread = Returning phone to %100 stock, including recovery.

Now, if you could please conclude your normal habit of bashing people, it'd be nice to have help instead of someone bickering and complaining.
[EVO 4G Q&A, Help & Troubleshooting] pseudoremora:
I have yet to bash anyone, let alone you... though I really should consider it.

The premise of this thread and the other relate to each other; in that you need USB functionality to 1) Return back to stock and 2) Gain USB functionality altogether so you can gain other options besides just "charging". Obviously you're overall problem is USB connectivity.

Why you decided to go and make a different thread when you could have combined two problems into one and just updated your OP in this thread is beyond me, that's what I'm getting at.
[EVO 4G Q&A, Help & Troubleshooting] magnu5:
I know this is hard to belive, but some people actually base their entire opening and reading of a thread over the title alone.

In addition to that, i'm sorry you can't wrap your head around it, but there ARE two different objectives here.

Also, lets say someone down the road needs to return to stock as described in the second thread, and does a search for it. Do you think they'd click on a thread titled "Lost USB" when that has nothing to do with their issue?

Now, if you can't contribute, i'd rather you do what you think is right, such as reporting the threads to a mod, or just not replying because you have some sense of anger at a forum you don't own or operate being cluttered.

If you can contribute, instead of arguing, i would indeed appreciate it.