Is anyone having problems with the home button? Sometimes when the phone is off for about 5+ minutes and I want to wake it up, I have to press the home button twice or maybe a couple of times.
I've noticed some other people are having this problem also, i'm just wondering if anyone found a fix?
Its been a problem all along. There is currently no fix and no telling when it may get fixed.
Related
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
..
Last night I noticed that pressing the power button on my phone no longer did anything. Thinking that maybe the phone had somehow become frozen, I pulled the battery and put it back in. Much to my surprise, the phone came on all by itself without me having to do anything. It seems that somehow the power button got stuck in the "pushed" position even though I can still push it like normal.
I have managed to work around the issues for now thanks to some features of Cyanogenmod (I can now wake the phone up using the volume keys and lock by tapping a widget in the notification area), but I'm wondering what caused this and if it's something that could be easily fixed.
Has anyone else ever experienced something like this or does anyone know how I could go about fixing the issue?
Oldiesmann said:
Last night I noticed that pressing the power button on my phone no longer did anything. Thinking that maybe the phone had somehow become frozen, I pulled the battery and put it back in. Much to my surprise, the phone came on all by itself without me having to do anything. It seems that somehow the power button got stuck in the "pushed" position even though I can still push it like normal.
I have managed to work around the issues for now thanks to some features of Cyanogenmod (I can now wake the phone up using the volume keys and lock by tapping a widget in the notification area), but I'm wondering what caused this and if it's something that could be easily fixed.
Has anyone else ever experienced something like this or does anyone know how I could go about fixing the issue?
Click to expand...
Click to collapse
Hi, take a look here:
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
and here
http://forum.xda-developers.com/showthread.php?t=1504501&highlight=power+button
Anyway, someone solve this problem opening the nexus s and manually cleaning the power button. Here a guide to open your device if you want to try:
http://www.ifixit.com/Teardown/Nexus+S+Teardown/4365/1
Opening my ns and cleaning it did the trick for me. Worth a try, your warranty is void now anyway
Sent from my Nexus S using xda app-developers app
Thanks for the info. I'll give it a shot when I get a chance.
Over this past week the back light for my Nexus S 4G appears to randomly shut off. Right now it has happened about 5 times and when I need to use it right then, preventing me from just stopping to investigate what may be causing this. The screen still comes on allowing me to quickly unlock using the pattern and then restart by holding down the power button. The one time I was able to investigate a little I was navigating into the settings menu when the screen just went blank. I pressed the power button a few times and could see the hardware buttons below lighting up as if the screen was on but that was it.
I'm currently running Slim Bean (Android 4.2.1) Beta and will be trying another rom but wanted to see if anyone else may have encountered this issue before I bring it up with that thread.
Yeah experienced this too in most 4.2 ROMs that I've tried. Some people say it's a bug with the auto- brightness settings but I don't buy it since I don't really use auto-brightness but still get the error. I'm back to 4.1.2
Glad to hear. I was becoming worried I had some hardware that was failing.
I will turn auto brightness off and see how it goes.
Thank you
So it has happened quite a bit since my last post. Even with auto-brightness turned off. I'm blaming this bug for my alarm not continuing after I snoozed it a few times. (I know they are unrelated but its just really annoying).
It happened again about ten minutes ago and I managed to output a bug report feature on 4.2.1. Not sure if it is of any use to anyone. Message me if you would like it.
My Nexus 5 has been experiencing this issue for months now. It happens in all apps (especially Facebook, WhatsApp and Jeffit). I press the back button and it freezes, meaning I can't press anything other than the home button to exit the app. This will then repeat itself time and time again until I eventually turn the phone on and off. This will solve the issue for a few minutes until it starts again.
I tried factory reset and it was fine for a short while and then began again. I've tried to see what app it could be, but from Google searches it seems like other people have it too and no one has a solution? There didn't seem to be a thread on it on XDA so wanted to see if anyone has managed to fix it?
I haven't got anything custom on my phone and it isn't rooted. It's so frustrating and it's ruining and otherwise flawless experience with the Nexus 5. I'm pretty sure it started after the Kit Kat update.
Just wondering if anyone else's back button occasionally stops working? It's only every now and then, and you can still see it respond to touch but nothing happens and multiple presses do nothing.
Pressing the home button always works, then after that it will start working again. It's happened a couple of times today already.
Not a biggy I guess, but quite annoying.
Anyone else? Any know why this might happen?
Thanks in advance.
A few times, but always in a crashed app so I assume it's the app not responding.
Sent from my SM-G955U using Tapatalk