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.
Related
Hard Keys Not Working
So, I searched and searched, but couldn't find anything that addressed my issue, so here goes...
Yesterday out of nowhere, the hard keys on my ATT Fuze just stopped working (Home, back, call, and hang up). Also, when I press my volume rocker it not only causes the volume screen to fluctuate wildly and not really do anything (but make lots of noise), it also makes the battery screen and the camera program open...
I've done a hard reset, a soft reset, and I have reflashed my old ROM (RRE21725 V3) and just flashed a new ROM (RRE21725 V5). Doesn't matter what I do, the hard keys still won't work and every time I reboot, the volume window opens and flashes a lot, the camera program opens, and the battery page pops up.
I'm going crazy and am finding my phone a bit unusable.
This hasn't happened up until late yesterday. I've never dropped my phone or gotten it wet. I just purchased it back in March.
Help, if anyone can.
hello, sound like the phone itself, i sent mine back about 3 weeks ago, same problem. you can try and flash the att rom, new one is posted on htc's web site and see if that works.
lupe
Installed anything recently?
have you tried a reset (soft/hard)?
Put a new screen protector on recently? (might be activating screen elements.)
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
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.
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
LMurphy said:
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
Click to expand...
Click to collapse
Definitely sounds like malware. You have two choices that I see, either root and custom rom or flash back to stock. Since you are stock you'd just be overwriting your existing install. Read this thread and decide your course of action http://forum.xda-developers.com/showthread.php?t=2203309
Hey everyone, I'm a fairly new OPO user myself here as well; I received mine back in early-mid October, and have had it since then.
But oddly enough, for the past two weeks or so, the following issues have surfaced and has become more frequent, and prominent than ever. For all the fellow OPO-users out there, I was wondering if anyone else has come across the same issue(s) that I've been going through... Unfortunately I really haven't had the time to look up any solution methods and whatnot with two young'uns whom are extremely demanding of my presence... All. The. Time.
So I thought that if I compiled my little list here, hopefully some kind soul will reach out to me with answers (or at least, the direction to where I could find those answers) and make my day just -that- much lighter.
Now just to mention the main points : NO, I have NOT rooted my phone, and YES, I DID install the OTA update, and currently my CM version is the 11.0-XNPH38R.
~~~~~~~~~~~~~~~~~~~~~
a) sometimes, my OPO screen will absolutely REFUSE to turn back on, after I've put the phone to sleep. nothing i do can get the screen to turn back on again - unless it decides it finally wants to. (it's got a mind of its own, this thing... and it's just as stubborn as I am. UGH.) i try double-tapping the screen several times (i've turned that feature on) and i try pressing the power/wake button, or holding it down, ... but zilch. this will usually last up to 10~15 minutes. (after 5~10 minutes of trying to bring it back to life, I just give up and let it be.) when the screen DOES end up turning back on, it's either flashing the "power off/reboot/accessibility" menu several times (probably from me trying to mess with the physical power/wake button) then finally respond to my 'backspace' on-screen keys, or the home icon, returning me back to the proper lockscreen it's supposed to show. ANOTHER way it ends up FINALLY responding, is that the phone will vibrate in short sequences of two, maybe three times and then it will initiate the rebooting process. then everything starts working fine again. i don't recall having ever done anything to trigger something like this to happen, either...
b) the keyboard (the stock Android keyboard) randomly will NOT work; by that I mean, when I am in a messaging app, or any other app that requires a person to TYPE WORDS ON, the keyboard DOES show up, (along with the suggestive bar just above it) and when I try to type, all the usual things will occur; the letter I happen to press will pop-up in response to my tap, and in the suggestive word bar above, it will start showing me the possible word combinations possible based on the sequence of the letters I type, but nowhere do I actually SEE on the SCREEN/message bar/etc. any letters or characters popping up. this issue too, will happen out of nowhere and will last about 15~20 minutes as well. usually what fixes the problem (as annoying as it is) is if I shut down/turn on, then reboot the phone a couple of times to get the keyboard to actually start working again. but there MUST be an easier method to fix this (and all my other issues) !
c) the stock camera app; this issue actually started occurring within days - just under a week of actually getting the shipment of the phone to my place. I was testing out the camera functions, the usual, then suddenly, I would get booted out of the app, and a message saying "The Camera cannot be used at this time" will pop-up as a result. (although, what was even STRANGER, was for a while, (for about 2-3 days) I was receiving a totally different message that didn't even make any SENSE: it said something along the lines of "the camera could not be connected to the device at this time" or "the camera has been disconnected from the device"... i don't even know HOW a camera can "disconnect" itself from the phone, but apparently it CAN.) with this issue, there was absolutely NOTHING I could do to start making it work again. it was non-functional for three, four days straight (no word of a lie) then just for the hell of it, I decided to open the camera app again, and boom, it was working. that didn't last long, though... then suddenly after opening the camera, there would be a prolonged black screen on the phone that wouldn't go away, and I couldn't select any options whatsoever... then when the camera finally started "working", i tried taking a picture - i thought that it would work, since nothing was indicative of it NOT working... but alas, such was not the case. when i went into gallery, to browse through the photos I had taken, they were not there at all, and the photos i had thought were taken weren't actually taken at all.
Asides from that, and some occasional (frequent) crashes while using the phone, I'm not feeling too frustrated by it. (I guess I just have an effin'-load of patience.) Still, I would greatly appreciate any thoughts or suggestions about this dilemma of mine, or providing me the key to all of the answers to these stupid bugs.
Thanks for all those who took the time to read my lengthy post. :fingers-crossed:
-- MK.