[Q] Galaxy Nexus keeps turning OFF - Samsung Galaxy Nexus

I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.

Try it without any off your apps installed. If the problem goes away you know it's an app causing the problem. Then start adding them back in batches until the problem re-occurs. Eventually you'll narrow the issue down to one app.

mark_w said:
I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
This is happening to me too.
At random times, the phone will refuse to wake from sleep.
Nothing but a battery pull will fix it.
I don't have skype installed.

Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1360880&highlight=sleep+of+death

Mine started today. Really hope this does not keep happening or I need to return this right away. Missed a few phone calls today and didnt realize until I looked down any my phone was just simply black. Will not wake up or do anything at all. You have to pull the battery. Right before this happened my data was dropping non stop about every 5 minutes for an hour.
I'm trying to stay calm because I love this phone, but between the data drops and the phone turning off im loosing patience quick.

This is happening to me as well. With TWO different phones. The first one I returned to Verizon and now its happening on the second one.
Phone will power off while doing random tasks. The two I've noticed is browsing on the stock browser and texting on the stock texting app.

I'm having the same problem. It's happened twice in the 3 days I've had the phone. It hasn't happened while I'm using it, both times it was when the screen was already off -- it just wouldn't waku up. Nothing short of pulling the battery, letting it sit, then powering on would work.
Couldn't have come at a worse time either, my daughter is in the hospital and I get updates from the surgeons via phone. So now I have to check every 5 minutes and make sure the phone is still on.
Phone is bone stock, out-of-the-box.
Sent from my Galaxy Nexus using Tapatalk

i just had my first turned off this morning... my friend's SGN happened 5 days ago too. very unreliable....

I had that happen to me as well. Turns out I forgot that I had an app scheduled to do a backup at like 3 AM.
Sent from Galaxy Nexus
CodenameDroid 1.2 cdma & Franco 14.4

My sgn turned off every night now. Anyone got any ideas why? I turned my verizon backup already.

reboot durring skype call
mark_w said:
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
it does it when i have skype running too. also i have other other audio apps open. (power amp, tunein, pandora) It's happened twice to me and each time it has been during a skype call while the other apps were running. (in widget form)

shock sensitive in the area right below the camera?
My device just "randomly" switches off (sometimes several times a day). After a long search for a reproducible cause, it seems safe to say that at least some devices seem to be extremely shock sensitive in the area right below the camera (on the back of the device). Even minuscule shocks to this area switch these devices off. Youtube-user 'jardinepatten' demonstrates this problem nicely in a video called "Galaxy Nexus Turning Off".

Related

screen not responding to touch inputs? (not sleep of death)

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.

[Q] Anyone experiencing lock ups?

Had my SGN for a few days now and over the last two I have come to find the phone won't respond after pushing the wake button. Some times the the notification light will be flashing, but the screen just won't turn on.
So far I've pulled the battery 4 times since yesterday... I can't find any reports of this, so I'm hoping I just got a defective unit.
I believe you have a rogue app. When I installed wave launcher it would lock the phone up in this fashion. The only way I could get the screen to turn on was to call the phone and while still on the call I had to uninstall the app and all was fine.. try and remember if you recently updated or installed an app and see if that fixes it
Sent from my Galaxy Nexus using xda premium
I got mine Friday, and when coming out of sleep the screen would turn on, but would be unresponsive to touch. If I pulled the battery, it was fine. I setup face detect to see if the phone was still active, and that would unlock it fine, I just couldn't touch the screen. I exchanged the phone yesterday with a new Nexus, and haven't had a problem since.
I believe the bad app was twicca. I installed right around the time the crashes started, and since removing it I haven't had any more crashes.
Saw another thread regarding pretty much the same issue, was SetCPU.
Previously used to see this (other devices) when something was underclocking CPU when phone was asleep, and phone wouldn't wake up)...
Anyway, glad to hear it sounds like you've got it.

Green pixels, freeze and battery drain. Anyone else?

I did not have that problem for a long time, it only recently happened. In the morning the device 'froze' for the first time and did not react to any input without the screen turning on.
I took out the battery to restart and everything seemed fine. But later on it happened while I was using the device, certain pixels moved out of place (like a green pixel distortion) and the device froze. Screen turned off soon after. Taking out the battery was the only option.
Now, this is either battery or some other hardware flaw. After restart the battery had been hit with a 20% drop.
Might the device act up by some charging problems? When I am charging the device, I can feel the electric 'buzz' from the docking connectors (the three golden circles).
Also, when it is not charging, I cannot detect it myself, but if I take a strand of hair, the end of it 'sticks' lightly to the screen (and to the docking connector) if I put it close there. I fear like there's some manufacturing flaw there that broke loose.
The device has not dropped once, nor has had any other physical damage happen to it.
Has anyone else had the same symptoms happen?
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
I found this issue (or one very much like it) at code.google.com here:
http://code.google.com/p/android/issues/detail?id=22748
jss42 said:
Sounds like you've hit the same (or similar) issue to others (including me)
Sleep of Death
http://forum.xda-developers.com/showthread.php?t=1360880
Click to expand...
Click to collapse
Thank you. I thought it was different from Sleep of Death since the initial symptoms were different from weeks ago when I read that thread, but now reading it this seems correct. This thread can be merged or removed, I'll post in the other thread. Thanks again!
I've had that too, couple days ago using Facebook everything just froze. The keyboard went all buggy and green pixels everywhere. The back of the phone started to warm up phone wouldn't respond in any way.
Tried everything I could try, only option was to pull the battery, once that happened phone wouldn't turn back on!
I gave the phone 5 mins to rest before putting battery back in then it turned on.
My heart was pounding I thought my phone had died!
Thankfully it hasn't happened since
Sent from my Galaxy Nexus using xda premium
It's happened to me multiple times. Less since I turned off the EQ in the Music app, but it's still happening.
Once it happened with the device just sitting there with Tapatalk displaying a list of posts. I wasn't even interacting with it.
I think it's a OS or driver problem and will be fixed in an OTA.
happened to me once, although when it happened I was already pretty low on battery, about 20% left, maybe less.
I was in a settings menu for some app, I can't remember which. But I had the keyboard up, and the green pixels hit, froze, unfroze, green pixels again, froze, and then shut off.
it would not turn on via the power button, so I quickly pulled the batt and put it back after 30 secs or so and powered it up. Batt did not drop any lower than it was, and it worked fine. Plugged it in, recharged overnight, and has been fine ever since.
I'm running 4.0.1 and I don't have anything but apps made by Google on the phone at the moment.
never rooted or unlocked bootloader.
Hopefully 4.0.2 or 4.0.3 fixes this
i realize now that there's no support for 720P AC3 .MKV files on the Nexus yet, but every time i tried the phone would lock up and i'd have to do a battery pull. other then that, i notice if i have Google Music running and attempt to do something else(multi-task) the phone will also lock up.. but then it will reboot on it's own. i also get lag regularly switching views/menus or going from portait/landscape. additionally, the browser(regardless of which one i use) will occasionally just freeze & close by itself.. usually if i try to do a secure login on a site. i will also sometimes get FC's(have seen them for launcher pro & android keyboard)

Phone goes to sleep instantly after waking up

This morning, I experienced something strange on my Hercules. The phone display automatically turned off after waking it up within a sec, it happened on and on. Sometimes it would last for 15-20secs then turn back off. Sometimes (very rarely though) it would power up fine and stay that w My timeout setting is 1 min, so it was not because it was timing out. This happened all throughout the morning, then it fixed itself miraculously after 2-3 hours.
I'm running the official CM9 RC2 rom. I don't think it was a software issue as luckily I had nandroid backup from 2 days back which I was able to restore, yet the issue was still there. What do you guys think? My guess is the power button was acting screwy, maybe it was not releasing properly or something.
The answer lies within the depths of your soul. When it is destroyed, only then will you find your path.
Sent from my SAMSUNG-SGH-T989 using xda premium
Mafioso said:
This morning, I experienced something strange on my Hercules. The phone display automatically turned off after waking it up within a sec, it happened on and on. Sometimes it would last for 15-20secs then turn back off. Sometimes (very rarely though) it would power up fine and stay that w My timeout setting is 1 min, so it was not because it was timing out. This happened all throughout the morning, then it fixed itself miraculously after 2-3 hours.
I'm running the official CM9 RC2 rom. I don't think it was a software issue as luckily I had nandroid backup from 2 days back which I was able to restore, yet the issue was still there. What do you guys think? My guess is the power button was acting screwy, maybe it was not releasing properly or something.
Click to expand...
Click to collapse
Something similar happened to me on aokp milestone 6 with the original kernel.. The screen went off and whenever I tried to turn it on it would back off again almost instantly.. Not giving me enough time even to do anything on the screen.. It kept doing it till I did a battery pull... Haven't experienced that since
I joined the darkside while riding a unicorn

Random Reboots?

I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.

Categories

Resources