Hello,
For the last few days now my phone keeps randomly pushing the menu bottom for no reason!? I've tried several roms and I'm having the same issue. I have one of those expensive screen protectors on, but I don't think that is the issue. Sometimes all of the compasitive buttons lock up and I have to lock the screen and then unlock it for them to get back to working?
androidguy1991 said:
Hello,
For the last few days now my phone keeps randomly pushing the menu bottom for no reason!? I've tried several roms and I'm having the same issue. I have one of those expensive screen protectors on, but I don't think that is the issue. Sometimes all of the compasitive buttons lock up and I have to lock the screen and then unlock it for them to get back to working?
Click to expand...
Click to collapse
I have this same issue. I've done some research and it appears to be a hardware glitch that happens when you have low signal. I've seen some reports of people bringing up the issue with Sprint/Samsung and they will replace the phone. I haven't taken the time to try that yet, since it only happens very infrequently for me.
lol awesome, this started happening to me maybe 2-3 weeks ago and i had thought i sat down too hard on my phone and messing up the menu button. originally i thought i was able to replicate the problem just by holding the phone vertically and rocking it back and forth. i'm glad to see others are having this same issue (well not really glad, just relieved its not a hardware issue).
i am experiencing the same issues the OP is.. menu button randomly pressing itself and all buttons being locked up requiring a lock screen then unlock to get things back to working.
andermic said:
I have this same issue. I've done some research and it appears to be a hardware glitch that happens when you have low signal. I've seen some reports of people bringing up the issue with Sprint/Samsung and they will replace the phone. I haven't taken the time to try that yet, since it only happens very infrequently for me.
Click to expand...
Click to collapse
can you point me to the other reports of this issue?
Thanks guys. I just don't have the time to take in my phone in. I normally have about 3 or more bars of service and it was still locking up on me. it's getting really annoying. Maybe I can just call it in? Who knows? They always give me a hard time! If anyone finds a better solution please let me know. Thanks!
Related
My Desire from today has had a faulty back button key.
Since today sometimes you gotta press back a 2 or 3 times before it responds.
Anyone else have this happen?
Mine does this too. Always has since day one, kind of annoying but for what its worth I will just put up with it.
Nekromantik said:
My Desire from today has had a faulty back button key.
Since today sometimes you gotta press back a 2 or 3 times before it responds.
Anyone else have this happen?
Click to expand...
Click to collapse
Yes suffering the same for about 2 days know.
Me too but not from the day i bought it. It started to happen after a month or so
Sent from my HTC Desire using XDA App
Same here! Started after a couple of months and Froyo didn't change anything either. At the moment I can live with it. Just hope it doesn't get worse!
i have faulty MENU button. not from begining, i'd say that since froyo update.
basically it works but sometimes nothing happens when i press it. i noticed that it doesn't work when pressed not in the middle of it.
but not always. sometimes it's okey to press it not in the middle and it works.
ometimes when i press it, and nothing happens, and then i press it again the context menu appears instantly on the screen, like it was there already, and starts to disapear slowly. i'm talking about context menu i get on the main screen, the menu with all apps, scenes, add to home, ... options.
hard to tell if it's hw malfunction or maybe some sort of software bug.
How weird! My back button started playing up today and the menu button about a week ago.
I was looking at these forums to check the backup/hard reset procedure, as I wonder whether it's a software problem rather than a hardware fault.
I got insurance so may get it replaced but I dont wanna end up with a SLCD version
crazybones said:
How weird! My back button started playing up today and the menu button about a week ago.
I was looking at these forums to check the backup/hard reset procedure, as I wonder whether it's a software problem rather than a hardware fault.
Click to expand...
Click to collapse
I dont think its software as it happens on 2 different ROMs I tried.
pelotasplus said:
i have faulty MENU button. not from begining, i'd say that since froyo update.
basically it works but sometimes nothing happens when i press it. i noticed that it doesn't work when pressed not in the middle of it.
but not always. sometimes it's okey to press it not in the middle and it works.
ometimes when i press it, and nothing happens, and then i press it again the context menu appears instantly on the screen, like it was there already, and starts to disapear slowly. i'm talking about context menu i get on the main screen, the menu with all apps, scenes, add to home, ... options.
hard to tell if it's hw malfunction or maybe some sort of software bug.
Click to expand...
Click to collapse
I don't believe that it's froyo related as I'm with T-Mobile (stock) so still on 2.1
Edit - My Menu button behaviour is exactly the same, pointing to a software issue.
I dont think its software as it happens on 2 different ROMs I tried.[/QUOTE said:
I understand what you are saying, but I find it hard to believe that we all suffer the same hardware fault at the same time with the same symptoms! Then again, if we all have one of the first batch of Desires, it is possible.
Click to expand...
Click to collapse
I once had this too.
After I updated to FroYo, it works flawless. But that could only be a coincident.
one person has this issue on stock 2.1 and others on 2.2 so its a varied issue.
My phone was part of the first batch so those with issues should state if it was first batch or not.
Nekromantik said:
one person has this issue on stock 2.1 and others on 2.2 so its a varied issue.
My phone was part of the first batch so those with issues should state if it was first batch or not.
Click to expand...
Click to collapse
Mine was first batch, the fault seems to intermittent.
My back button was playing up yesterday also.
Seems fine today though??
Maybe this is the reason why the producers seem to prefer touch sensitive buttons at the upcoming models. Harder to get faulty buttons from the product line.
Kahunar said:
Maybe this is the reason why the producers seem to prefer touch sensitive buttons at the upcoming models. Harder to get faulty buttons from the product line.
Click to expand...
Click to collapse
there were alot of people who hated the touch buttons on the N1 and prefer the hardware buttons on Desire.
Just done a hard reset - the first since I've had the phone. It appears much better, but I'll only know for sure once I've used it for 24 hours. Have only loaded one application (Linda file manager) in case the issue stems from an app update.
I think I'd prefer touch buttons.
I've got a de-branded Orange Desire running Froyo and I've got the same fault developing with my back button. If it is definitely hardware then these kind of things can only get worse, to the point where it stops working completely.
This started on mine and few days ago. I think its an app, probably an update that is doing it. That's why a factory reset currently it. Any thoughts?
Sent from my HTC Desire using Tapatalk
This has absolutely nothing to do with software and it's a hardware semi-fault.
Boot into recovery and select hardware key test, press the button in question many times, you still see sometimes it misses, sometimes it doubles.
I've started experiencing it with the menu button after two months I bought it, now it happens with home too, and it's getting worse. You really have to press hard to have the long press functionality.
Back button is only sporadically doing it, far more the search button.
I'm planning to ask for a warranty repair, but after having had in my hand an slcd one I'm having second thoughts.
If anyone has it back from repair, it would be nice to know what they have done and if the chassis was replaced.
I have had my Htc Evo rooted for a long time now. This problem recently just started and I'm not sure if it's because my phone is rooted or maybe it's just an electrical or hardware problem. The top right button to lock the phone or to wake it up from sleep doesn't register all the time. I sometimes have to push it several times for it to work. Do you think I should restore my phone? Maybe it's because it's rooted? Something got corrupted? I'm leaning more towards hardware problems..
Any ideas?
Thanks!
steveojp said:
I have had my Htc Evo rooted for a long time now. This problem recently just started and I'm not sure if it's because my phone is rooted or maybe it's just an electrical or hardware problem. The top right button to lock the phone or to wake it up from sleep doesn't register all the time. I sometimes have to push it several times for it to work. Do you think I should restore my phone? Maybe it's because it's rooted? Something got corrupted? I'm leaning more towards hardware problems..
Any ideas?
Thanks!
Click to expand...
Click to collapse
Are you just having trouble waking the phone up with the power button, or is it all functions of the power button are acting weird? Does it put the phone to sleep fine? I've had it happen a few times, where the phone wouldn't wake up by pushing that button. That was attributed to the ROM i was using at the time, and also having the min clock setting at 128.
If your case is different, and the button isn't working properly for all of it's functiopns, and not just waking up the phone, it could be a hardware issue, or the button mechanism could be hanging up or something.
k2buckley said:
Are you just having trouble waking the phone up with the power button, or is it all functions of the power button are acting weird? Does it put the phone to sleep fine? I've had it happen a few times, where the phone wouldn't wake up by pushing that button. That was attributed to the ROM i was using at the time, and also having the min clock setting at 128.
If your case is different, and the button isn't working properly for all of it's functiopns, and not just waking up the phone, it could be a hardware issue, or the button mechanism could be hanging up or something.
Click to expand...
Click to collapse
All the functions of the power button is acting weird..sometimes I have to push the button like 10 times for it to wake up so I can unlock my phone. Sometimes I have to push it 5 times or more to turn it off. It's weird though how this randomly started doing this. I was hoping it was the Rom. I'm running Fresh I've never had any problems with it. That's why I leaned more towards the hardware. Is there any way to go around pushing the power button to wake up the phone? Do you think I should restore my phone to see if it maybe fixes the problem?
Thanks!
steveojp said:
All the functions of the power button is acting weird..sometimes I have to push the button like 10 times for it to wake up so I can unlock my phone. Sometimes I have to push it 5 times or more to turn it off. It's weird though how this randomly started doing this. I was hoping it was the Rom. I'm running Fresh I've never had any problems with it. That's why I leaned more towards the hardware. Is there any way to go around pushing the power button to wake up the phone? Do you think I should restore my phone to see if it maybe fixes the problem?
Thanks!
Click to expand...
Click to collapse
If it was me, I would make a nand backup of your current setup, and then try flashing a different rom, and seeing if the problem persists. If it continues, I'd then unroot and return to stock setup. If it happens on stock setup, I'd then take it to Sprint to have it looked at.
Sent from my PC36100 using XDA App
k2buckley said:
If it was me, I would make a nand backup of your current setup, and then try flashing a different rom, and seeing if the problem persists. If it continues, I'd then unroot and return to stock setup. If it happens on stock setup, I'd then take it to Sprint to have it looked at.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Alright, I'll do that. Thanks
bump for update from OP
Power BUtton Problems with Waking etc.
Not sure if you ever resolved your issue, but I have the EVO 3D, NOT rooted but with the latest updates, and ever since the last OTA update that moved me to software level 2.08.651.2, I have had issues with the phone not waking on an inbound call until I hit the power button and then wait about 8 seconds for the screen to come on. I have Factory Restored it 3 times, which seems to fix the problem temporarily, but it always comes back.
I just did a warranty replacement claim to see if that will finally resolve the issue. I even found a post where someone said the stock batteries are somewhat loose, so I took a business card and taped it to the bottom of the battery, opposite of the charging posts so that the fit would be better, still no luck.
steveojp said:
Alright, I'll do that. Thanks
Click to expand...
Click to collapse
anyone had problem with the screen not responding after waking up?
There's no way to turn off the phone / make it respond unless to unplug the battery and plug it in again. Had this problem on the first GN and my second replacement GN.
Yep, happened to me the other day as well. There was a crash right before which made the phone reboot. Once it came back, the hardware buttons responded fine but the touchscreen was dead until a battery pull.
Hasn't happened since though.
Had this at lunch today also had it a few days ago.
When returning from sleep the touch input seems to be completely unresponsive.
I left mine for a while to see if it recovered, it did, it came up with the crash report for "System Process" The screen was then responding fine.
Weird. This is indeed different to the sleep of death, because the screen comes on.
Although maybe it's related in some way?
This just happened to me, and so I googled to find an answer. It thankfully led me here. It's like you guys described: I just tried unlocking my phone, but the screen was completely unresponsive. Not a single touch would register, even when trying to touch the Power Off option.
I read robaldred's comment, so I decided to try the waiting game. Thankfully, after a few minutes the screen just came on and the device was ready to use. I don't believe I saw a crash report though.
I hope this won't become a serious issue. I'd hate to be stranded at a point when I need to use my phone.
I had this problem too. have you guys used custom notification sounds?
Sent from my Galaxy Nexus using XDA App
I had this exact problem and I found it was due to Juice Defender (I have the Ultimate version as well). It kept happening after I installed and but since removing it over a week ago no problems.
Just had it happen here, had to pull batt. Using BatteryXL but will keep it on and see if it happens again.
I have had my Moto 360 for just over a week. For the second time the touchscreen stopped functioning. First time I resolved by turning it off (very long press hardware button) then left overnight and it was fine in the morning. Turning it off and back on again didn't help. Couldn't factory reset because no touchscreen.
Second time is now.
Does anyone else have this problem? Any clues how to resolve?
Thanks.
Edit: After left off for a while (instant off and on doesn't work) it is fine now. Anyone have any clues or better suggestions how to fix?
spanielhead said:
I have had my Moto 360 for just over a week. For the second time the touchscreen stopped functioning. First time I resolved by turning it off (very long press hardware button) then left overnight and it was fine in the morning. Turning it off and back on again didn't help. Couldn't factory reset because no touchscreen.
Second time is now.
Does anyone else have this problem? Any clues how to resolve?
Thanks.
Edit: After left off for a while (instant off and on doesn't work) it is fine now. Anyone have any clues or better suggestions how to fix?
Click to expand...
Click to collapse
Yes mine has done it two or three times since the last OTA update, nothing I did to the screen had an effect, had to reboot the watch to recover.
teslabe said:
Yes mine has done it two or three times since the last OTA update, nothing I did to the screen had an effect, had to reboot the watch to recover.
Click to expand...
Click to collapse
Mine doesn't recover immediately on a reboot but it is nice to know I'm not alone in the problem. It's better to know that you've only had this problem since the OTA. That means it can be fixed in software. Thanks.
Same here
Lost "touch" today on mine. Had the 360 for about 4 weeks and not seen the problem until now. Wasn't even sure how to turn it off until I saw "very long press" - thanks!
Turning mine back on straight away was fine so it was just a turn it off and back on thing. Frustrating, but I'm glad it's a software bug rather a touch screen fault, that would be a real pain. Hopefully, if it's a bug it will be fixed.
i think.....
I think this happens when the moto 360 is not set on your wrist
Ddoes anyone solve this issue ? My new moto 360 touch screen doesnt work at all. So i can choose any language in initial setup
This problem Occurs when no static energy is given to the case of the moto360. As soo'n as You touch The Iron ring The touch Will work. Release it and it Will stop working. Ik think The touch screen works rather like a conductive layer between the back of the watch and the screen it self in which the skin gives the energy needed to control the screen. When the back of the watch isn't connected to skin the touchscreen completely stops working.
In video you see what happens
https://youtu.be/KpQ-dqWYO6s
Mine did this too, however I broke my screen ordered a replacement and haven't had the issue since. When mine quite working if I triple pressed the power button it lock the screen then pressing the power button it would turn on and work though. Sometimes it wouldn't come right back on like it froze or something.
Sent from my Nexus 6 using Tapatalk
I've been having this problem too, it's more like my weekend watch but last week i noticed that it wasn't responding and i thought it could be a RAM issue. I've done multiple reboots and it doesn't work.
There was only an occasion where i left it overnight till it almost drained completely and it worked again, and then it started freezing again.
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.