I used to have the Cappy and hung out in the Cappy subforum. Well i am about to sell it and i went back over there after a 3-4 month leave there and i forgot how infested that subforum is with db's. I have been in about 5 diff subforums in the 4 years i have been here and this one or the others cant touch the d-baggery of the ones that loom in there. Thanks Thunderbolt for saving me.
Now to give this thread a purpose.....
I have BAMF GingerREMIX Beta 6 installed and noticed it wakes on volume. So i booted into recovery and ran the mod i have to disable that. upon reboot, it freezes on boot up. After 2 battery pulls and 2 more failed boot ups, i realized my rom was hosed. I used that one on the Froyo roms and apparently it wont work on GB roms, but i didnt think about that before i did it. So does anybody have a mod to disable wake on volume for GB roms??
Its in the BAMF 2.0 thread. Way down near the bottom with all the other mods.
Edit: My bad I just realized you are on the remix I don't know if the one from regular BAMF 2.0 thread will work or not.
Sent from my HTC Thunderbolt
The one on the BAMF 2.0 thread will work. I have it running on the Remix beta 5 as we speak.
easier method, open root explorer
System > Usr > Keylayout > Mecha-keypad.kl Mount as R/W Open in text editor
you will see
Key 115 VOLUME_UP WAKE
Key 114 VOLUME_DOWN WAKE
just delete the wake part, save and reboot. Note that I didnt even need a reboot for it to take effect.
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.
First ofall i am new to the forum and new to the gtab and rooting, roms. I am running cwm and vegan tab 5. 1.1....i have only had it, used it for 5 days but it seems that the home function has quit working...both the hard and soft key. Back key and info key works fine- any ideas?
I had all my capacitive buttons stop once. I had to let the battery drain to get it back because the hard reset button is inside the chassis.
Sent from my VEGAn-TAB-v1.0.0b5.1.1 using Tapatalk
wickedhog said:
First ofall i am new to the forum and new to the gtab and rooting, roms. I am running cwm and vegan tab 5. 1.1....i have only had it, used it for 5 days but it seems that the home function has quit working...both the hard and soft key. Back key and info key works fine- any ideas?
Click to expand...
Click to collapse
Sounds like what I ran into. I just reloaded my rom and fixed the issue.
Sent from my G-Tablet running Vega-Nb5.1
So I know this is the wrong place to post this, but I "cannot post to the dev forum" due to low post count...nice...
anyway...
Installed CM7 RC1 for 1.2 BL (actual package: "update-cm-7.1.0-RC0-smb_a1002-KANG-signed -clemsyn-bl1.2.zip") along with google apps (package: gapps-gb-20110613-signed.zip) and was running fine for a few days. A little while ago my gtab when to standby (just as it had many many times over the last few days), and when I pushed the power/standby button nothing came back...okay, I thought...no biggie... hold the power button down for a few secs to power down, push the power button again to power back up...gtab boots back up to home screen, but all my widgets fail to load and instead show soemthing like 'problem loading widget'...okay, I say, reboot once more...and here's the rub...after that reboot, now stuck at three birds - cannot even boot into recovery (I have CWM installed). (but I -can- boot to APX)
So...other than re-flash wiping everything out...is there anything else I can do?
Oh...and fyi... the only change made between the previous standby and this last standby was that I moved a few apps from 'phone' to 'sdcard' (Netflix, and two others that I cannot remember).
But I am wondering if the lock up occured more from having to hard power down during standby or if it was due to moving my three apps to sdcard....
You don't happen to use another Launcher ? I had this issue before but no more after sticking to stock launcher.
Actaully yeah, I was using Launcher Pro - but had been since minute one of installing the ROM...as well as the ripple lock...
Sounds like CM7 RC1 doesn't like Launcher Pro...
So...anything that I can do other than re-flash? not a huge loss...just time...
nm - i just re-flashed and will try with the included launcher for a few days.
So...interestingly enough...I re-flashed with tnt 1.2 pre-installed with cwm, re-intalled CM7 RC1, re-installed gapps, only wiped the cache part, removed all broken widgets, and re-added widgets, and now it is all back...i let it standby a couple times and it comes back no prob...so it would seem that the issue might be related to the hard power off (long power button push) (coupled with something else going on in the background maybe)...fun, fun...lol
Co to tablet settings and make it so the gtab wakes from sleep with the volume buttons. Also, the problem loading Widgets thing just happens sometimes. Especially if you have 2 launchers installed on your tab.
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
Hey,
I've been flashing roms to my Nexus S (Rogers) since I got it last May. All 2.3 stuff (Usually NSCollab) until the last month or so, when I started playing with ICS. This seems to be an issue only with the ICS roms I've flashed - thought admittedly, I've only tryad Cyanogen and Nexus MV (Cyanogen-based)
It seems my search key gets "stuck" from time to time. Sometimes, it acts as though I'm long-pressing it... other time like I'm tapping it repeatedly. When this happens, the touch-screen still reacts normally (I can pull down the drawer, type messages in and so on) - but I can't tap back or home or the menu key. Usually (though not always), putting it to sleep for 10 seconds or so will fix this.
Anyone have any ideas what's wrong? Maybe something to try troubleshooting that I haven't thought of?
Thanks
..