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.
Related
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.
Hi all, I'm one of the "new to the gtablet world thaks to Woot" crew. First, thanks for what you all do here, it's a great resource.
I've managed to install the TnT Lite v4.3.0 wthout any problems and everything seems to be running well. My question is, when i hit the power button on the side, it shuts the tablet down and to turn it back on i have to hold the power button down and it has to go through the entire boot process.
Maybe thats what it is suppose to do, but being used to my iphone i imaged it would just turn off the screen and hn bring back up the lock screeen whn it was pushed again. Am i wrong or did i do something wrong when installing? Is it a setting change?
I know this question may be dumb, I'm not as tech-ignorant as this post may make it seem.
Thanks again.
A long press on the Power button should power it up. Once it's gone through the full boot cycle, a short press on the Power button should put it into sleep mode. When in sleep mode, another short press should bring it back to wake mode. A long press on Power while the gTab is fully awake should bring up a dialog box that asks what you want to do, go into Airplane Mode, Shutdown, etc. If you choose shutdown, you'll get another dialog box that asks you to confirm with a yes/no.
I am using the Stock Enhancement so maybe it works differently from yours but mine has functioned this way consistently from the time I got it, even before I loaded the Stock Enhancement.
did you try to press the "power" button lightly. when you press it lightly, it should just turn off the screen. If you press the power button and hold it for a sec, you should see a popup choice (shutdown, sleep, air mode, etc). I agree that the power button is a little sensitive to me as well and I have been using mine for 3 months and it is getting a little bit "wear".
So, it is just my solution, and it may or may not work for you. Since you are running tnt lite (not working on Vegan rom). You can download an app from android market called "Tap Tap App" power button (free)
https://market.android.com/details?id=net.maicas.android.wsleep&feature=search_result
and it will place a icon to your screen or notification bar. It basically turns off your screen, and you can press the volume buttons to turn the screen back on. I have been using this solution for a month now, and have no issues so far.
I'm pushing the button very lightly, and it appears to shut the machine down, or makes it unesponsive. Then I have to hold it down for quite a while to get it to do anything, which makes the machine reboot. When i hold down the botton (when the machine is on) I do get the options, and can put it ito sleep mode that way, and then a light touch will turn it back on. But obviously this is not the way it is suppose to run.
Is there a way to reinstall TnT or shoul i try one of the other ROMS?
Actually I think that is a problem with 4.30. If you install clemsyn's kernel it should fix it. Pershoot's may work too but I only tried clemsyn's.
It sounds like a sleep-wake issue. Like wall_fodder said, you can try to install Clemsyn or pershoot kernel. before you do install the kernel or reflash it, make a backup through clockworkmod and use titanium to backup your apps and data.
I am using 4.2.5 and very stable. Yes, you can reflash it with 4.2.x or vegan 5.1 through clockworkmod.
tyy10002 said:
It sounds like a sleep-wake issue. Like wall_fodder said, you can try to install Clemsyn or pershoot kernel. before you do install the kernel or reflash it, make a backup through clockworkmod and use titanium to backup your apps and data.
I am using 4.2.5 and very stable. Yes, you can reflash it with 4.2.x or vegan 5.1 through clockworkmod.
Click to expand...
Click to collapse
thanks, is there a step by step on this someplace?
hey all, thanks again, i restarted it in recovery mode and now everything works fine, nothing new installed or changed. Thanks so much...
I heard mixed results about 4.3.0 and sleep. For me, it works (as well as others). But some have reported issues. I'm not sure why that is -- maybe a data wipe is needed?
fyi, the recover reboot only helped the sleep issue for about two presses of the sleep button. However, I installed the Clemsyn kernel through Clockwork Mod and now it works great (after several tests). I had installed tnt 4.3.0 and 4.3.1 directly without CWM. So installed CWM on top of tnt4.3.1 then installed Clemsyn. Probably not the correct way to do it, but everything is working right now.
Lots of hail marys from this newbie while i was doing it though.
i have spent all evening trying to figure out how to fix this. I have looked high and low, near and far. After four hours of searching, i finally found the post in the Backside thread about manually editing qwerty.kl to change the key 107 setting from "endcall" to "power", but this has accomplished nothing.
why on earth has this issue not been fixed yet? from what i gather by google search, this has been a problem since at least june, probably sooner. is there ever going to be an update for BACKside IHO that fixes this? I was tremendously pleased when i found that i could get my OptV to 2.3 by way of CM7, but i have spent all day tracking down quirks (had to reinstall twice to get prox sensor working)... I never got into Linux because of this crap, but now i have to do it on my phone???
It would probanly be best to unroot and reroot/ or install a clean install of CM7 with a full wipe.
Hit that thank button if I helped!
I have done a full-wipe and reinstall of CM7 (to fix prox sensor). How does one go about un/re-rooting? Does it entail restoring to factory, or can it be donr without having to remove CM7 (again)?
It will take it back to out of the box state. CM7 is a rom, roms require root to install besides stock. After you root, you will need to install it again.
Hit that thank button if I helped!
still no dice, and now the prox sensor is broken again.
EDIT: it seems there was more than one file with a value of "ENDCALL" assigned to key 107. Changed all "ENDCALL" buttons i could find to "POWER" and now it works.
For some reason, though, prox sensor only works when not in bluetooth mode
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
the same thing happened to me once on my ns4g. I had to pull the battery.
try flash recovery img at fastboot and then see if you can get in recovery
greg2826 said:
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
Click to expand...
Click to collapse
As long as it is working OK now then all is good.
Happens every now and again.
Ok this has happened to me a couple of times and from what i have found if i press both up and down volume buttons and power button in random combos after about second or third try it sorts it self out. I have tried to create the error and from what i have seen its if you are a lil heavy handed and either press the volume up and down together to start with or the power with one of the others at the same time it does some weird lock on going back or rebooting or anything really. don't think its isolated to the version of CW as i've had it on older builds
bigmem said:
Ok this has happened to me a couple of times and from what i have found if i press both up and down volume buttons and power button in random combos after about second or third try it sorts it self out. I have tried to create the error and from what i have seen its if you are a lil heavy handed and either press the volume up and down together to start with or the power with one of the others at the same time it does some weird lock on going back or rebooting or anything really. don't think its isolated to the version of CW as i've had it on older builds
Click to expand...
Click to collapse
that happened to me before, i got a mini heart attack, and some what i pressed the both volume button by accident and it worked lol
allenxx said:
that happened to me before, i got a mini heart attack, and some what i pressed the both volume button by accident and it worked lol
Click to expand...
Click to collapse
I swear the amount of random errors i have had in CWM and i always leave the battery pull to last thing, battery pulls have led me to partial bricking and having to learn quick that its not a good thing lol
bigmem said:
I swear the amount of random errors i have had in CWM and i always leave the battery pull to last thing, battery pulls have led me to partial bricking and having to learn quick that its not a good thing lol
Click to expand...
Click to collapse
try twrp recovery
greg2826 said:
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
Click to expand...
Click to collapse
It's caused by scrolling through the menu options 3 times. It's actually a feature. I forget where I read it but apparently back in the day there was a dude with a broken power button who couldn't select things in CWM so Koush put in that feature just for him. I believe one of the other buttons works to select items when that's enabled. To get out of it just keep scrolling up or down through the menu options 3 more times.
You ended up in the stock recovery. Hold power then press volume down OR volume up (cant remember which) and you'll be in stock recovery.
Also, the physical buttons are disabled when you press vol up and vol down at the same time. Do it again to return to normal.
happened to my yesterday again, after six months of problems free.
anyway nothing to be scared about.
thank u for answers, i kinda forgot about that thread... LOL
What's going on guys? So I'm having this problem with my S3 for the second time now. What occurs is the capacitive buttons and the home button randomly stop working/functioning properly as well as vibration ceases to function. I make the distinction because the capacitive buttons continue to work, but mapped functions (such as holding the menu button for google now or holding back button to kill an app) do not work. The home button completely doesn't work.
I've googled this issue and the only thing of relation that I could find was a topic where someone mentioned that the EFS could be missing some files. The first time I thought that there was a chance this could be a hardware failure but it happened so rapidly and randomly that I doubted it (plus doing a keytest in CWR confirms everything working fine). Sure enough, wiping the install and installing the latest nightly fixed it. Now it's back. I could just wipe it and restore my apps again but my backup is encrypted and takes forever to restore so if there's any other fix for this, that'd be peachy.
E: I should mention that I do not have a backup of the EFS.....yeah...
also, what's causing this? Corruption of the internal memory card?