Database Info

[Q] HELP! Capacitive side buttons stopped working!

Hey guys,
Oh i dunno whays happened. Everything worked fine yesterday then i went to sleep. Next day the side buttons stopped working. The touch screen still works but the side capacitive buttons stopped.
It doesnt even work when i boot into clockwork mod
I have so far tried:
Reboot did nothing
Put calibration.ini file in root directory
Put calibration.ini in sdcard2
Put calibration in sdcard root
Reboot
Didnt fix it.
I got it ebay as i live in australia so warranty may be difficult.
I am using button saviour to get by for now but until i can get the side buttons to work i can no longer navigate clockwork mod because the home button is the select button.
I'm usibg vegantab b5.1 at the moment.
Any help would be really appreciated!
BAM

If you haven't, you might want to try this: http://forum.xda-developers.com/showthread.php?t=934500

Just tried it but still no joy. Looks like the side buttons are on a different touch interface to the rest of the screen. I guess it could be worse. Vegantab is a nice rom to be stuck on.
I wonder if there is a way to make clockwork mod work with a usb keyboard?

Woohoo! It's working again! Just in time for honeycomb too
I searched and searched for similar issues and finally read about either draining the battery or opening up to find the hidden reset button.
I opted to drain the battery.
Now I'm still not going to rubber stamp that draining the battery fixed it but when I did finally plug it in and fire it up I found the buttons worked again.
Another theory I have is that viewsonic might have some poor soldering. The reason I suggest that is because in Australia we've had some stinkin hot days here at 42degrees Celsius with high humidity. So it wouldn't surprise me for a dry solder to become temperamental under these conditions.
Anyways happy ending for now. Well hopefully it'll keep running until a reliable honeycomb rom turns up for gtab hey

I have encountered a similar problem. The side buttons stopped working after a few days of use. They do work sometimes randomly. Is there a reliable solution to this problem?
I tried calibration.ini, and the buttons worked once. They have stopped working again.

Home and Search Keys don't do anything on VegaN-5b1?

Ok, possibly a stupid question but search didn't yield results that helped me. A friend noticed that my search and home keys don't do anything on my G-Tablet running VegaN-5b1.
The keys work fine if I boot into Clockwork so I figure it's a mapping issue or a known ROM issue.
Any ideas to help me out?

It is not an ROM issue.
Are you sure the button works on CWM and not after it boots to the Vegan ROM, just want to make sure. Since people here said it stopped working Period.
there are couple of things you can try.
1. Drain the battery completely and then charge. I am not making this up, one user had success with this method.
2. Check if you have installed button remapper or any util like that. ( i have installed button remapper to disable my back button)
3. Try a different ROM.

CWM works just fine. As far as a button remapper goes, I don't believe I have one - at least not one I can identify.
I guess I can try another ROM - which sort of defeats your first line of "It is not a ROM issue".

Cleared the user data and caches with CWM, did a full restore and everything started working again. Must have been some bad data someplace.

I am having this issue too. The buttons work in CWM, but not in Vegan.

[Q] Problem with front buttons after permroot/clockworkmod/CM7

Hi all, got my MyTouch 4G a couple weeks ago and immediately started researching how to root it and install a non-Sense ROM. Finally got up the nerve a few days ago. This is my first post, so I can't post links. I followed the "TMobile myTouch 4G: Full Update Guide" on the CyanogenMod Wiki.
To be clear, I did the following:
- permroot via "gfree -f"
- Flash ClockworkMod Recovery (3.0.0.5)
- Flash CM7 Nightly build 34 + gapps via Recovery
After doing so and using it for a bit, I noticed that the "back" or "<--" button on the front wasn't responding to button presses at times. Sometimes it would be fine, then sometimes it would take a "long press" on the button to get it to work, then finally it would stop working altogether, only to randomly start working again later.
I thought maybe this was a problem with the nightly build, so last night I wiped all data and flashed CM7 build 38. It only got worse after that. Now, the back button NEVER works, and the MENU button is now acting buggy in the same exact way the back button was before. I also noticed the "Genius" button doesn't work either, but I don't know if it was working in build 34 because I don't use it.
I tried booting into recovery and cleaning caches/wipe and reset/clean davlik/etc and nothing worked.
I went into the "Key Test" and got NO RESPONSE when pressing the menu, back or genius buttons All the other buttons on the phone still work as expected. It's amazing how many apps depend on a functional back button. I am stuck in configuration menus in a couple of apps because I can't back out of it!
So to the point... what are my options? How can I get these buttons back?
Thanks in advance.

texastoast said:
Hi all, got my MyTouch 4G a couple weeks ago and immediately started researching how to root it and install a non-Sense ROM. Finally got up the nerve a few days ago. This is my first post, so I can't post links. I followed the "TMobile myTouch 4G: Full Update Guide" on the CyanogenMod Wiki.
To be clear, I did the following:
- permroot via "gfree -f"
- Flash ClockworkMod Recovery (3.0.0.5)
- Flash CM7 Nightly build 34 + gapps via Recovery
After doing so and using it for a bit, I noticed that the "back" or "<--" button on the front wasn't responding to button presses at times. Sometimes it would be fine, then sometimes it would take a "long press" on the button to get it to work, then finally it would stop working altogether, only to randomly start working again later.
I thought maybe this was a problem with the nightly build, so last night I wiped all data and flashed CM7 build 38. It only got worse after that. Now, the back button NEVER works, and the MENU button is now acting buggy in the same exact way the back button was before. I also noticed the "Genius" button doesn't work either, but I don't know if it was working in build 34 because I don't use it.
I tried booting into recovery and cleaning caches/wipe and reset/clean davlik/etc and nothing worked.
I went into the "Key Test" and got NO RESPONSE when pressing the menu, back or genius buttons All the other buttons on the phone still work as expected. It's amazing how many apps depend on a functional back button. I am stuck in configuration menus in a couple of apps because I can't back out of it!
So to the point... what are my options? How can I get these buttons back?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried a different keyboard?

To be clear, I'm talking about the PHYSICAL buttons on the front of the phone.

Well, with no other ideas, I reflashed the stock mt4g ROM, unrooted and took it back to TMo. They swapped me out with a new one (good ffc, good screen).
Unfortunately, this new one is resistant to rooting. Using the same CyanogenMod Wiki article referenced above, "rage" seems to work (I get the # in terminal), but "gfree -f" gives an input error when trying to do the part7 backup and "sync" gives an I/O error and freezes the device. The part7 backup files created on the SD card are all zero bytes (plural because I've tried multiple times).
I found other posts about the input error and I/O error for other devices, but no resolution.
I also tried visionary, but it didn't work. I temprooted and again it seemed to work (# in terminal). When I tried to permroot it said it needed to be temprooted in order to work, implying that it was not, in fact, temp rooted. One time, after doing a factory reset and immediately loading visionary, it seemed to actually work. I was able to temproot and proceed to the permroot which also seemed to succeed, but then the phone rebooted and the result was no root ($ in terminal).
Any ideas? Links to more recent permroot instructions? Anything?

Simply because I don't like leaving open-ended threads, I thought I'd wrap this one up. I ended up returning the second MT4G to TMo and getting a third one shipped. For some reason they sent 2. First thing I did was try rooting both. 1 rooted, the other one did not. OK, so I checked the FFC's, both slightly off-center, but flat against the glass. Checked the screens, and the rooted one had panel_type 2 and black was obviously blacker at an angle than the other one, so it looks like I got a winner. Successfully flashed CM7 and everything still works.

On the G2, HTC updated something (radio I think) to patch the exploit used by gfree. If they're doing that now for the Glacier as well, then it may still be possible to use gfree if you downgrade using a pre-update firmware image from the forums. But, since it seems you have one that you're satisfied with, maybe there's no sense in bothering with it. (Then again, since you have a spare to play with, you might decide to have some fun and try it.)

Actually, I don't have a spare. I sent both unrootable phones back. Last thing I need is to be charged for that second phone they accidentally sent.
I don't know what the problem actually was, but I can see from these boards that I'm not the only one. It fails at the part where it's trying to set the eMMC r/w and it can't do the part7.* backup.

There's a good chance gFree may have been failing on the second phone because your phone was connected to your computer via USB. It's normally not that big of a deal, but MT4Gs are set to automount the sd card upon connection. Gfree freaks out about this and fails.
Glad you got everything figured out, even if it took you 4 phones.

[UGG!] Back button is driving me insane!

My back button is freaking out. It randomly presses and it sucks. I can't do much of anything on my phone because of it. Started happening last night and has lasted all through the day doing the same thing. Open an app and use it for a few seconds then it hammers the back button. (Or long presses it.) Doesn't matter which app, and sometimes no app, just the main screen.
Why is this happening? It had been working great. When I was on 2.3.2 it happened a couple of times and then quit. Now it won't stop. I've cleaned the screen several times. Wash my hands like crazy. Reboot, pulled battery...

happened to me after i restored apps with mybackup. i don't know if it was a specific app or something to do with mybackup. couldnt be bothered finding which app it was, so just factory reset to fix it.

this thread might be related
http://forum.xda-developers.com/showthread.php?t=952535

I've seen that thread and tried to tighten screws but none were loose. I hoped to not reset...

The model working at The best buy store here has this issue bad. The back button simple doesn't work unless pressed extremely hard, enough to almost break the phone. The other 3 buttons work just fine though.

My back button is also less sensitive than the other buttons.
I can even use the phone with gloves, only the back button doesn't work.

I found one thread that said to turn off animation. I did but it didn't stop. It did seem to slow it down. Now it seems to have stopped for today.

i had this issue with my home button. it's a hardware issue not caused by any apps you've downloaded. you're going to have to call samsung and have them fix yours unfortunately. they won't send out a new one they require you to send yours in for repair and for them to ship it back out to you =/

my 1st ns had problem with back button with my second ns back button works great

[Q] Back button keeps blinking(and vibrating)

So my Nexus S 4g been mighty stable, til this morning. i check my bank account on my phone then all the sudden, the back button starts blinking like crazy, and everything goes back if i open anything, and the vibrate feedback can be felt like rapid fire. So I hold the button so I can actually power off the phone into recovery.
Its still blinking, so I hold it down so it sends only one signal, so i can change my kernel back from Netarchy 1.3.7 to 1.3.6 where it still does it. Repeat to Mathkids. I also wiped the cache partition, and dalvik cache for this one. havent tried stock yet.
Anyone ever have this problem. Its still doing it. Thinking about going to stock and returning phone.
And if I do return it, do I have to unroot, and relock the bootloader?

tried stock kernel, did a few backups, formatted everything agian, turned back to stock and it hasnt stopped.
did notice tho if my hand or thumb got close to the back button, but didnt touch it, it would stop blinking. maybe it needs a heat sensative calibration? it wont stop flickering no matter what

It seems to be related to this issue: www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Im having exactly the same problem, but with the searh button. In the Google thread a Google employee has replied, and according to him they're working on a fix (software related). This was posted a couple of weeks ago, i bet the fix is issued in 2.3.5, set to rls in the upcoming days.
For me the search button flickering seems to be related to how long the screen has been on, i.e. how warm it is. I can use it perfectly for 20-30min, but then its unusable for the next five. I discovered the relationship between screen on time and the flickering like a day ago and it may be incorrect. The Google employee says it is a software issue, but i dont hold my hopes high.

I was having this problem with the search button.
I goofed up something on the phone and ended up reflashing it back to stock like 5-6 times in the course of a night.
Ever since then, I havent had the issue pop up even once.
I also have read that it has to do with the NFC contacts on the battery cover. Someone was able to supposedly fix this by preventing the contacts from touching their corresponding contacts on the phone.