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?
Related
When I wake the polaris up, it seems that the left button (the one in the wheel) is permanently pressed until I press another button. I have to do this in order to unlock the device, as the button is pressed I only get the message "Press cancel and then unlock".
This happens every time I wake up the device and sometimes when I am using it in other situations. It is almost unusable in this state.
I suppose it is a hardware problem. Any ideas for a way to fix it? I wouldn't like to send it to service, but I am fearing this is the only chance I have now. Any help would be appreciated. I have already switched it off, and also removed the battery for a while, but I have the same problem when I turn it on again.
This has happened to me for the first time yesterday. The device has not fallen to the ground any time since I have it (since February). I only carry it in my pocket.
Thanks for your help.
ah, I forgot to tell you. When the button stops being pressed (because I have pulsed another one) it doesn't work anymore. If a press it, no effect, the cursor doesn't move to the left...
I have read in another forum that someone who had a similar problem with the wheel managed to solve it by doing a hard reset and by restoring a backup done before the problem. He stated that using the option "erasing memory" didn't work and that he had to do the hard reset by doing "gps button + ie button + soft reset".
Here is the funny thing. I cannot do that kind of hardreset. Why? Because as the left button seems always pressed the confirmation screen in which you must press the send button to perform the hard reset, never appears. I guess it is due to the cruise which detects that the combination of buttons is no good or because the confirmation screen is shown but as the left button is pressed, you do not have enough time to press the send button (I don't even see the screen).
Is there anyway to perform the hard reset in another way? Thanks for your help...
Well, my cruise works fine now. What have I done? Nothing. Maybe it was a hardware problem in the contact of the button (some dirt or whatever) and now it is working. I don't know, although it wouldn't surprise me if it were software (I had a similar problem with the vibrator in a Mio A701, two days broken, got to work after that and never again failed). I just used the bluetooth and received a couple of calls.
Now I can hardreset. As the button is no longer permanently pressed, the combination of buttons works. Although I haven't pressed "send" to actually do it, since it seems fine.
More here if it fails again, but as I told you I read similar problems in the wheel in another forum...
I've had this problem since the first day I got my phone, but it seemed to go away...now it's back with a vengeance. I'm assuming it's a hardware issue...
I have haptic turned on and sound off for button presses. The issue persists regardless of settings. Basically, the phone will randomly receive HOME button presses, while I'm not pressing the button. Insanely bothersome. Has anyone else experienced this behavior?
I did root and flash to the most recent COG, which, fwiw, made google voice act insanely wonky (was showing Google's number as outgoing CallerID, NOT my google voice number), so I had to go back. Interestingly, my RomManager backup WOULD NOT WORK and the phone was freezing on the white ATT World Phone screen. I did manage to fix it with ODIN, but entering download mode was not as easy as described, my button combination wasn't what any other post said it should be.
So this new ROM isn't exactly the same as the original stock rom, and I'm thinking of rerooting and trying something other than Cog, but obviously if I need to return this phone I should do that first. Interestingly, it didn't do the behavior described even ONE TIME when Cog was onboard.
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.
Edit: the problem seems to have resolved itself by unknown means.
So, I installed TWRP on my new TF300 yesterday after unlocking the bootloader. It seems to work...for the most part.
Curiously, I am having an issue in that most of the buttons on the right side of the screen (and ONLY the right side) will not work.
For example, I can tap Install, and it will work. I can tap Backup, and it will work. but anything to the right of those will not work, such as Restore, or Wipe, or Reboot. In addition, the Home and Back buttons in the upper left do not work, but the other one beside them (I think it's a log button?) does work.
This is causing a considerable issue for me because somewhere along the line my CM9 install got messed up and is bootlooping, and I can't wipe the device. I've tried installing CWM but am having altogether different troubles there (<waiting on device>......)
This is a strange issue and I can't seem to find anyone else having any similar problems. For the record, there are no issues with the touchscreen when in the OS.
Hey guys,
strange and frustrating problem. I was using my phone pretty extensively today (although nothing crazy), mostly thanks to Pokemon Go. Tonight after using my phone normally, I went to press the power button to turn the screen off and nothing happened. I was able to reboot (by changing one of the long-press actions to bring up the power menu via GravityBox) and then was unable to power on the phone. It seems like my hardware power button has suddenly become unresponsive. This leaves me unable to power on/off the phone, including booting into the bootloader. Also, I seem to be unable to wake my phone up by double tapping the screen or swiping up.
The phone otherwise functions fine. If I get a notification, the screen wakes up and I can use the phone. Otherwise, the only way I've been able to get into the phone is by connecting it to a computer and issuing ADB commands. The IR blaster functions fine which makes me think it's not the hardware button?
Has this happened to anyone else before? Can the power button just break like that without any water / physical damage? The fact that I also can't wake the screen makes me think it's a software issue. One other thing I suspect is that my phone abruptly died yesterday (battery died despite software thinking it still had juice left). In the past, with the modified kernel / rom, this has resulted in some nasty issues, including 4G not working and the Android system process basically exploding. I thought I lucked out when I powered it on after that, but maybe it just took a day for this issue to manifest itself.
I'm going to make a NANDROID backup and try flashing a few different things to see if I can fix it. I'll post my progress here.
Current build:
- Verizon M8, S-OFF
- TWRP
- Android GPE 6.0 (MRA58K.H13)
Edit: I haven't been able to find a fix. I'm a bit afraid to try a full RUU since I can't use the hardware keys to reboot into the bootloader should something go wrong. It may just be that my PWR hardware button is f'd which really sucks. I'm not sure I'm up to cracking open the phone to fix it. In the meantime I downloaded an app called Gravity Screen On/Off which uses the phone's proximity sensor to wake the screen up and it seems to work ok for now.