My capacitive back button is going crazy!!! I figured it was just the rom or a program running in the background. So I rebooted into recovery and it happened then too!!! Definitely a hardware issue. I didn't drop the phone and I wiped the screen clean. So I'm not sure what the problem is. Is there any way I can disable the back button completely and remap it to the Search button? I never use the Search button, so this would work for me. Please help!
I have had this happen to me, it would randomly act up. After two weeks or so, it just stopped happening.
I have seen reports on forums that some people have tightened the screws on the back of the phone and had luck with that fixing the problem.
Sorry I can't be more helpful.
Yeah happened to me too when I first rooted it, found out it wasn't the root that did it but an application that I put on there that was not compatible with the phone.
I had the same problem too -- I posted this a few days ago on another thread dealing with this problem. I'm not sure why it's happening but it many people think it's a software incompatibility issue. I did five hard resets and the problem went away. Most people who tried the hard resets only did it once, and the problem persists. It'll even persist in recovery. I think you need to do enough hard resets until the problem disappears. Mine now is glitch-free -- good luck.
http://forum.xda-developers.com/showthread.php?t=952535&highlight=back+button+issue&page=2
Nexus S
Rooted Stock 2.3.1
T-mobile unlocked
Try installing the stock 2.3.4 just for trial. The new update fixed all my issues with the back button
Sent from my Nexus S using XDA App
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
SphericalPuma said:
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
Click to expand...
Click to collapse
Your new nexus s are using latest version or not?
I have this issue sometimes too. Mine doesn't go crazy though, it just becomes unresponsive and dark. I have to wait a couple of seconds and then it comes back. Kinda of like the phone freezing while the damn button come back.
Running Nexus S4G 2.3.4
Related
Hey guys, im on my pc, and im literally watching my phone press the return button really quickly, constantly for a few seconds at a time. I know theres a topic about the back button but im not sure if its the same issue, im running Cm7 with Honity, and I dunno what to do, ill be using my phone and suddenly it will spaz out and continuously hit back until were on home, then just keep pressing it!
I am running stock, unrooted 2.3.2. I also occasionally have this issue. I have not really been able to reliably reproduce this issue. Sometimes it happens middle of the day, sometimes towards the end of the night after the phone has been in use all day. Other times I can go days without having an issue. I had chalked it up to a quirk of my phone, but it is nice to see other people having the issue too.
Hopefully it is a firmware/software error and not something physically wrong with the phone. I would have to have to send it in for repairs.
i tightened the 6 screws on the back of the phone and i stopped having that issue. try and see if it will work for you
Yeh your not alone.
I have done a factory reset and not experienced the issue as of yet, its been 2 days, however if it should happen again i will try tightening the screws a bit.
Back button issue
There are a few longer threads in this forum about the back button issue on the Nexus S -- for some people the back button doesn't work at all, and for others it turns on all by itself. There were a few replies from a Google employee (ryguy) who said it would be fixed in an upcoming OTA update, etc. but some reported having problems AFTER getting 2.3.2 when the problem didn't exist before. There are also other reports of tightening the screws on the back of the phone, which haven't tried but seemed to improve things for people whose back button WASN'T working at all.
For my phone around 2-3 weeks after buying it I had the back button come on all by itself. I fixed it by doing hard resets, as suggested on an earlier thread that deals with this issue (it's like 10 pages long but has the complete story of everyone's experience and fixes with this issue). Anyway, the point is for me after the first hard reset the problem persisted, so I did it a few more times (like maybe 5 times) and now it's gone.
There are some people who tried a hard reset (factory settings restore) and the problem still persists but I think that you have to do as many hard resets as possible (like, over and over and over) until the problem disappears. I'm rooted so I did a Nandroid backup first, then did 5 hard resets through Clockwork Recovery (select the "Wipe User Data" option), and after five hard resets I just flashed by backup and I was back to where I was, minus the back button issue. You don't have to be rooted, of course, to do this, but if you are, doing that ROM Manager backup allows you to quickly reinstall everything to the exact way it was after you're done with the five or 10 hard resets or whatever.
If you're unrooted you can power off the phone, then turn it on while holding the Up Volume button. This boots you into Bootloader mode and you can navigate around to do a factory reset. Or, if you are rooted and have ROM manager, you can use ClockworkMod Recovery like I did (see other threads on how to use these programs).
Anyway, hope this helps - TC
Samsung Nexus S with root access
Stock Android 2.3.1
Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.
Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app
Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app
I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.
I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.
MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.
My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app
Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.
Hey guys,
In the last two weeks i've noticed that my Knock On feature stopped working completely. It will Knock Off but it will not knock on. Also, my pull down notification menu will have issues. i will start to pull down and it will "catch" and then stop. It appears to pull down still as long as I stop at the spot it is having problem.
I am running Scott's Clean ROM with no other Mods. Uninstalled all apps since the problem, still nothing. Also, I have tried wiping cache and davlik cache. Still nothing.
Any one else having this issues or a solution? Thanks!
BUMP
ThKA said:
Hey guys,
In the last two weeks i've noticed that my Knock On feature stopped working completely. It will Knock Off but it will not knock on. Also, my pull down notification menu will have issues. i will start to pull down and it will "catch" and then stop. It appears to pull down still as long as I stop at the spot it is having problem.
I am running Scott's Clean ROM with no other Mods. Uninstalled all apps since the problem, still nothing. Also, I have tried wiping cache and davlik cache. Still nothing.
Any one else having this issues or a solution? Thanks!
Click to expand...
Click to collapse
Yeah I have that problem, I had to send my phone to LG for repair.I'm due to get it back this week.
Sounds like a hardware problem to me.
I received my phone back on Saturday, on the return docs it just said 'replaced touch screen'. It's working fine but I'm surprised they replaced the screen, I expected it to be a software issue to be honest.
Had the same issue att sent me a new one
Sent from my LG-D800 using XDA Premium 4 mobile app
This just started happening for me too. It's a bar across the screen near the top, which happens to be in line with the power button on back. Considering the knock on stops working, and it being right in line with the power button I feel like it would be software related, but updating to Kit Kat / factory reset did nothing for me. Also I did nothing to my phone to suddenly cause a hardware failure. Hopefully LG is trying to resolve. I am giving it a couple weeks before I try a warranty repair -- a friend of mine had the same issue and it suddenly went away.
I had the same issue for a day then and went away and now its back again.
I don't know if that is hardware or software issue.
Anyone got some info about it? I don't got any warranty so I would like to know more about this issue before paying for screen replacement.
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Powergreb said:
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Click to expand...
Click to collapse
That is strange...I haven't had that kind of behavior on my Nexus 6-works without a problem-never freezes or reboots...now I know the Amazon app would do something to my Nexus 6 I don't know what but when I install it-my phone with reboot randomly or shut down...ever since I uninstalled it-no issues-for months.
Try running safe mode and see if it does it again-that way you will know if it is an app that's causing the issues. This is how it's done: http://www.greenbot.com/article/2923927/how-to-restart-your-android-phone-into-safe-mode.html
You can always try a factory reset as well....have you tried updating to the most recent factory image from Google?
Powergreb said:
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Click to expand...
Click to collapse
I've been experiencing the black screen freeze frequently since getting the phone only a couple days ago. No other lockups however. Also running pure stock.
I too have the same issue. Screen goes blank and lock ups. Also running pure edition...
Same. Interestingly, in my case, it seemed to happen most frequently when using Hangouts.
I have another post that describes random reboot and I believe they are related. Long story short. I believe either the factory reset + software update fixed it, or it's a hardware problem problem. While I wait for the replacement, I only had one random reboot. Of course the new phone is rock solid. It's only been a couple of days. I would have a few by now if I'm still on original phone _ original firmware.
Powergreb said:
I have another post that describes random reboot and I believe they are related. Long story short. I believe either the factory reset + software update fixed it, or it's a hardware problem problem. While I wait for the replacement, I only had one random reboot. Of course the new phone is rock solid. It's only been a couple of days. I would have a few by now if I'm still on original phone _ original firmware.
Click to expand...
Click to collapse
I'm having the same issue. So no random freeze leading to reboot with ur rma device?
Sent from my Nexus 6P using Tapatalk
What I'm trying to say is don't panic and RMA your device. Do a factory reset and make sure you're on the latest firmware. Mine was OK after the first self-reboot during setup after factory reset but has been good while waiting for the RMA to arrive. To answer your question, the new device has been perfect but it's only been 48 hours.
I am facing a similar issue with my Nexus 6P, can anyone please help me with it?
On any rom, whatsoever, I get reboot when I turn the Google Maps Navigation On.
After few minutes, phone just reboots
I havent yet tried stock, any idea how can I find the root cause? I have cleared data for maps, also I have tried to uninstall maps with TiBackup and installed fresh from Play Store
Powergreb said:
I received my 32G model on Nov 28. Firmware MDA89D. Pure stock unmodified in any way. Not even using screen protection or cases. Setup as a new device, not copy from another existing device. I've been getting randon freezes and crashes. When it froze, it did not respond to any touch input or any key input. The only way to get back is to hold down the power button to do a force reboot. It seemed to have settled over the last few days. What I do have on an ongoing basis is crashes. When I use Google map navigation, the phone will work for a few minutes and the screen went black followed by a reboot. It did it on 2 consecutive days already.
Is it just me having this problem therefore a defective unit or is it the OS / Software problem.
Click to expand...
Click to collapse
Yup same stuff going on over here with mine. It locks up and reboots even after clearing cache and rebooting only a few hours earlier. Have done 2 factory resets and am on the latest OTA update. I also noticed that I have to clear the cached data every day, sometimes multiple times a day to keep device running smoothly. This really concerns me with a device that's less than 2 weeks old. I also have only a handful of basic apps( Fb, YouTube, Spotify). Really thinking about returning it. When the phone runs right its great, but all the issues make me nervous. Might be time for a Note 5? I am just getting used to this phone and would hate to leave it though. Interested to see if the first major marshmallow update fixes these problems.
Jcomstock said:
Yup same stuff going on over here with mine. It locks up and reboots even after clearing cache and rebooting only a few hours earlier. Have done 2 factory resets and am on the latest OTA update. I also noticed that I have to clear the cached data every day, sometimes multiple times a day to keep device running smoothly. This really concerns me with a device that's less than 2 weeks old. I also have only a handful of basic apps( Fb, YouTube, Spotify). Really thinking about returning it. When the phone runs right its great, but all the issues make me nervous. Might be time for a Note 5? I am just getting used to this phone and would hate to leave it though. Interested to see if the first major marshmallow update fixes these problems.
Click to expand...
Click to collapse
Mine actually had one random freeze and reboot after factory reset then nothing for 48 hours after that. Of course I rma'd mine and I'm glad I did. Screen is on the colder side with even volume speakers on the second unit. Sending my original one back.
Sent from my Nexus 6P using Tapatalk
I'm just about ready to RMA. I've tried factory resets, cache wipes and just recently updated to the latest stock MDB08M. It was fine for a day or two but now the lockups are increasing.
As others have said, by any other metric this is one of the best phones I've had. This freeze/reboot thing is getting annoying and even if it isn't happening to every user it's happening to enough to be of some concern.
I'm facing app closures, my gmail app keeps crashing, it happened on my graphite nexus 6p, and now same thing on my frosty 6p. Its not just gmail, it's also chrome now. Maybe i should have not restored from my previous device.
what's this?
I came to this thread expecting a lot more of a technical discussion (the site is called xda DEVELOPERS after all).. but instead all i see is "oh my phone is crashing.. i'm gonna RMA this sucks) posts.. moving on to android enthusiasts on stack exchange thank you very much
upgrading to 6.0.1 fixed it!
upgrading to android 6.0.1 fixed it!!
Hi everyone!
So I just had this problem after I woke up yesterday. I googled a lot but only found similiar problems.
Let me tell you what happened chronologically:
After turning the phone on in the morning it started updating apps as if I was doing a firmware update: "updating apps 1 of 135" etc. Note that my nexus was already running on 5.1.1 and had the latest updates installed.
Now it randomly freezes the screen on whatever screen it was before it happens and it won't respond to any touch input. This can also happen when not using the phone, then it will freeze at the lockscreen (the time freezes with it so sometimes i can see at what time it froze). Also, it loses connection with Wi-Fi as i'm using Whatsapp Desktop when i'm on my laptop and it mentions me that my phone is not connected.
The only thing that "fixes" (temporarily) it is a reboot. Now sometimes, on the lockscreen, i can just hold the power button and the pop-up comes in to turn the phone of, which i can somehow just tap on an it responds by turning the phone off. But sometimes (less frequent than the latter mentioned) the pop-up doesn't come in and holding the power button for a few secs will do the trick.
I hope I informed you all enough and my end question is: does any of you know what this is? How i can fix it or what i can do to prevent it or anything as I am hopeless. (my G3 is up for reparation so this is my sisters old phone, i had a nexus 4 myself for 2 years before the G3).
Thanks in advance!!
The best way to test it is by reformat the OS.
I positively think that it will solve the problem.
Since the phone is no longer under warranty, I guess there is no harm to install custom rom on it. They are fast and stable too.
Hope this help. Good luck.
Sent from my Nexus 4
EXACT thing happened to me too. Backup your data and hard reset from recovery. This fixed it for me
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
multimedias said:
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
Click to expand...
Click to collapse
Then it's time to change the screen or phone. Looks like it is a hardware issue.
Nitin
nitin.chobhe said:
Then it's time to change the screen ...
Nitin
Click to expand...
Click to collapse
I agree, your screen needs to be replaced.