any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
jakkix said:
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
Click to expand...
Click to collapse
It has to be an app that`s causing that....
jakkix said:
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
Click to expand...
Click to collapse
Happens to me almost every time I connect it to my cars Bluetooth to listen to Pandora, and i'm on the latest CM 10.1 nightly.
SOD
I also happened yesterday and today, yesterday had cm 10.1 and in the evening I returned to stock 4.2.2 and happened again this morning. any suggestion?
My wife and I are both having this problem with our N4s. It's been happening on and off since about 2 weeks after we got them on January 7. I'm still debating whether or not to try an exchange under warranty. I'm not yet convinced that it would help, but it seems like it's only affecting a handful of us, so maybe it is hardware related?
Hmm hppnd with me too. Yst n today almost at same time. After playing with some apps or games.. Phone was hot..
Sent from my Nexus 4 using xda app-developers app
What rom/kernel if any are you guys on? I recently got the SOD. I am on the PA 3.1 and bundled kernel. Not sure what's causing it. My initial assumption was the themes in cm10. Now I think it's the launcher in question or lockscreen.
I am using Nova Launcher with slide/stock lockscreen. Nothing really has changed that I can tell within the last week. I uninstalled all my themes this morning to see if it was that causing the SOD.
Got the SOD this morning at work. Had to long press the power button a few times to boot it up. This time I uninstalled the Nova Launcher completely and reinstalled. Restored my widgets and seeing what that does later.
Happened twice. Once with unrooted stock, once with cm10.1. So i think this is an hw problem.
my battery screen looks exactly like this after SOD: https://code.google.com/p/android/issues/detail?id=35139
in my case long pressing to power button boots the device. no need to charger or button combo.
Forgot I posted here. I forgot to follow up. It turned out for me, there was a bad browser commit in the PA build in early March. I since reverted to a working nandroid and flashed the most recent rom. For others,I suggest to backup your apps and do a wipe. If that doesn't work, then maybe a factory reset?
i realized my SOD's occur at ~13:30 (1:30pm). Uninstalled a few apps(dash clock, rotation widget) and SOD's stopped. But today installed Onavo compression app than, bam!, SOD again(at 13:30 of course).
kpjimmy said:
Forgot I posted here. I forgot to follow up. It turned out for me, there was a bad browser commit in the PA build in early March. I since reverted to a working nandroid and flashed the most recent rom. For others,I suggest to backup your apps and do a wipe. If that doesn't work, then maybe a factory reset?
Click to expand...
Click to collapse
What do you mean bad browser commit?
Linsanity said:
What do you mean bad browser commit?
Click to expand...
Click to collapse
Basically the stock stuff was crashing the rom and causing the sleep of death. Have been fine ever since I reverted back to a working nandroid and dirty flashed the updated ones.
I am currently using the new version of pacman and it happened to me two nights ago.I reflashed and downloaded sleep of death fix app for charging. But I want to be 100% sure it won't happen again because I depend heavily on my nexus 4 for alarm. How can I be sure?
Sent from my Nexus 4 using xda premium
I just posted in the Android issue tracker this fix for nexus 4 SOD that worked for me :
It looks like there are different types of Nexus 4 freezing behaviour, all being lumped under the description: SOD.
My device (reliably) SODs after extendeded USB charging the very first time it sleeps; never happens while actually charging, just immediately upon disconnection; and it never happens in other circumstances.
However, I believe I now have a fix. If I only charge with a QI wireless charger OR if charging via USB, immediately sync with a QI charger upon disconnection, I never (it's been over a week now vs. every morning before) get a SOD.
Try this if you have the exact same problem I had. QI chargers are now available on eBay for less than £4 shipped.
NOTE: if you have a different sort of SOD issue, this may not work for you.
Related
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
yep
+1
Not very often but very annoying if you use your phone as alarm clock.
I honestly haven't experienced either with my SGS. I can sympathise though as my Milestone used to do both way too often (hence swapping for the SGS).
It hasn't happened to me.. It might be running a software or hardware watchdog to reboot automatically when the system panics. Ensure you are using a stock rom, otherwise, it may even be faulty hardware
Would happen several times a day on my Motorola Milestone so I sent it back and got the SGS. Totally rock solid. Only time it reboots is when I want it to. Maybe you have a rogue app?
you guys have any changes to the CPU speed whatsoever, task killers and all? i once used SetCPU and it sort of sent me into a random spree of reboots and such.
i remember rebooting, scanning 10gb of media, auto-reboot... repeat 4 times. lol.
Well it hasnt happened since yesterday. I will flash to froyo today just in case it was software related
Sent from my GT-I9000 using XDA App
dakine said:
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
Click to expand...
Click to collapse
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
AllGamer said:
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
Click to expand...
Click to collapse
Link would be helpful, because I can't find that topic.
WOW, old thread that got dug up, for me it was just a software issue. I flashed many roms since and haven't had it happen again. I never reset my battery stats but I think clockwork mod recovery has an option to do that so most of the custom roms make that easy.
I also had random reboots and power-offs, on average once every 2 weeks, running on stock-firmware JF3. Problems did not go away when I manually upgraded to JM2. Problems stopped when I upgraded to Froyo...
Anyone noticing random crashes with the g2 cm7? Atleast once a week when I take it out of my pocket it doesn't power on and requires a battery pull to turn it on. (No lights, nothing)
Battery voltage issue?
Different people have been having different issues. What nightly/RC are you on? did you do a full data/cache/dalvik wipe before flashing the ROM? did you try fixing permissions?
Yup, I know there are some issues but it seems strange that the whole phone goes into a stale state which requires a battery pull. I believe its happened once or twice with cm6 as well.
I have done all the wipes and fixes etc. I am right now on nightly #15, I previously was on nightly #7 for a long time so maybe it was just that release. Thanks for your reply.
Haven't had one random reboot. Still using nightly 6. My mytouch4g has not had this problem either.
From my permarooted 1209mhz G2 with CM7 nightly 6
Are you overclocked?
Sent from my %s running Cyanogenmod.
Only to 1Ghz.
Today it died while charging, dead and needed a battery pull. Any ideas?
You're not the only one with this issue (myself included), and the cause is not yet known. And it seems there may be a couple different variations of this issue with the same symptom (of the phone powering off while asleep and needing a battery pull to power back on). May be related to overclock, GPS, screen-off profiles, full moon, or who knows what. See this thread for some various thoughts on the problem.
http://forum.xda-developers.com/showthread.php?t=908095
I personally think its a kernel issue, or that the kernel is at least one of the factors. I flashed pershoot's kernel and the problem seems to be solved, so far (keeping my fingers crossed). Having the GPS on while you turn of the screen also seems to be a common trigger for many who experience this problem.
Hi there,
Thank you so much for your reply! I couldn't seem to find any information on the forum.
I just wrote a post because I had the same thing happen to me. Phone just went dead for ni reason and I had to pull out the battery. But my phone isn't rooted. So it might not be because of CM7.
Tried to call Bell, but the wait time was too long. So will try to call them when I get home.
Sent from my HTC Vision using XDA Premium App
There are at least two other threads about this on XDA and quite a few others on the net.
Google HTC phone freeze random crash reboot battery pull or some combo.
No solutions and it happens on stock phones as well as rooted.
Did you search?
Having the same problem recently on my unlocked Desire Z from Bell, using on the Rogers network. It started yesterday and all of a sudden it turns off, and the only way to turn it on is removing the battery and putting it back in. This never was an issue for months. The only thing I updated from that affects the hardware is the new Google Maps, so I think GPS may be the case. But I really need GPS on my phone...
Yesterday I did an experiment with GPS. For me GPS is the case that makes my phone to freeze. With new Google maps it freezes even faster, more often.
Sent from my HTC Vision using XDA App
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Sounds like you need to Odin.
bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
I got that on EB as well. It's weird because it didn't start as soon as I flashed it. It was maybe about a week later when it started doing that. When it happened to me my phone would vibrate sporadically and then the screen would finally go "black" or turn off. The odd thing is the bottom four buttons would stay lit. I would have to pull the battery. It started happening more and more frequently. I've since flashed to EC and am rooted but that's it. I've been flashing back and forth between different set ups, so I haven't been on this current set up for more than 2 days. I did however have the same problem today at lunch. I had to pull the battery to get it to reset. I was playing a video I recorded on my phone before the screen went black. I don't know if it was media related. I will play some more videos and see if it does it again.
k0nane said:
Sounds like you need to Odin.
Click to expand...
Click to collapse
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
cpcormier3 said:
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
Click to expand...
Click to collapse
Have you tried formatting your SD card yet?
k0nane said:
Have you tried formatting your SD card yet?
Click to expand...
Click to collapse
I haven't with EC, but I did with EB and I still had those problems. Today was the first day that it's happened to me. I've only been on this set up for the last couple of days, because I flashed a couple of things and hoping that I would have better luck with stock. I will try re-formatting when I get home. I tried playing a coulpe of videos (the same ones as before) to see if I could replicate the problem, but haven't been able to yet. Hopefully that was just a situation to where the phone just needed to reboot....
bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
!!! Y E S !!!
It happened to me four times today!
Does anyone know a way to get logs to continuously write to disk? Otherwise I have no idea how to troubleshoot this.
I'm running, midNIGHT EC05 with minimal apps installed. I use SetCPU, and I've just changed the settings. I'm thinking this may have started after trying to use 100MHz and "startass" setting. My profiles are now set to 200Mhz minimum and "ondemand." I'll let you know how that goes.
Having to use my old BlackBerry Bold as an alarm clock now, just in case!
EDIT: I did not format SD with this install but have formatted less than 2 weeks ago.
Happened again after setCPU settings were changed.
That happened to me but what's weird isnit only happened when I was on di18 kept having to pull the battery and once I updated to eb13 it all stopped
Sent from my SPH-D700 using XDA Premium App
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Same here. Like the term sod, btw. Happening when I use flash. I'm on stock ec coming from fresh odin, and formatted sd.
Sent from my SPH-D700 using XDA Premium App
alfiej said:
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Click to expand...
Click to collapse
No Beautiful Widgets here.
I am running Go Launcher, which is new to me. Will likely eliminate that tomorrow. Oh yeah, the only other widget new to me is "Android System Info" (which is great, btw).
I run Pure Grid calendar and Sense Analog Clock widgets, but I've been running those without trouble for months.
Does anyone know how to change logging levels?
The only rom I was able to use without the SOD was myfrankenstein DK28. While on
EB13 it did it contstanly and much hasnt changed while running EC05. I formatted my sd card and only installed minimal apps. I tried not restoring from Titanium or Astro. Fresh install from market and it still happens. I've stopped using SetCPU, that didnt help either. I do have Beautiful widgets running on my home screen, but I aslo had that while running DK28. I have no idea what the problem is. It is a complete pain having to check my phone every couple of mins to make sure that its still on. Over night forget about it, every morning the phone is dead. Can anybody help me please.
I just Odin to EC05 last night.. and installed the new syndicate frozen rom... and my screen just went blank today.. so far it has done it twice in less then 5 minutes....
but I have noticed that if the phone is plugged into the charger that it wont do it.. no matter how long goes past.. thats the only way I know my alarm is gonna go off in the morning.. is to have it plugged in..
do anyone know if its doing it on plain Stock untouched modem and stock rom??
because if not imma flash over to that.. I cant take this crap too much longer..
I have had this so called SOD for almost 3-4 months and as a matter of fact I just ordered a replacement 10 minutes ago. My SOD involves the phone either rebooting or completely going black except for the bottom cap buttons, then vibrating in order once, then 3 times, then once, and so on until a battery pull. This has happened on the charger as well for some roms. I can tell you it does it on a stock rom. I just did a full reset, stock eb13, updated to ec05 OTA, wiped sdcard and everything except contacts. The problem exists, so I am almost 100% that it is a hardware flaw somewhere. I even did the ##786# reset. I'll let you know if a new phone fixes the issue :]
damn.. even on the stock rom huh???
well do anyone know if it might have something to do with rather journaling is on or off??
other wise.. i have not a clue of what could be causing it..
I have EC stock rom, but am rooted. It happens to my phone. It doesn't happen quite that often like you guys, but it happens maybe about once a day. It happened more frequently when I was on EB. It would happen at least 5 or 6 times a day. It's strange cause it never happened right when I flashed EB or EC. I was fine for a couple of days before it happened. Not sure why....?
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
sultan.of.swing said:
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
Click to expand...
Click to collapse
I had about six today. I'm flashing stock and running untouched starting tomorrow. If that doesn't fix it, it's replacement time for me too.
Sad, because a stress test on my phone at 1.4ghz ran fine.
Btw, I still use set cpu, but only in known safe configurations, no OC.
I just received my replacement. Brand new phone, I installed a formatted sdcard and synced contacts... within 10 minutes it seemed to be happening again. The phone was stock di18, then it updated to stock EB05... I have no idea what the problem could be now, since this phone is brand new.
My Nexus 10 is exhibiting sleep of death issues when I leave it overnight. Are there troubleshooting steps to help me determine what the cause of the issue is?
apastuszak said:
My Nexus 10 is exhibiting sleep of death issues when I leave it overnight. Are there troubleshooting steps to help me determine what the cause of the issue is?
Click to expand...
Click to collapse
When you leave it on over night, do you have it charging or not charging? If not charging, what is the battery level before and in the morning?
ROM? Rooted? Mods?
SmokinCharger said:
When you leave it on over night, do you have it charging or not charging? If not charging, what is the battery level before and in the morning?
ROM? Rooted? Mods?
Click to expand...
Click to collapse
Stock 4.3. Rooted with SuperSU 1.65. ClockworkMod Touch installed.
I had Sleep of Death overnight, and I was not plugged in.
Yesterday morning it was dead. I plugged it in via pogo cable and factory charger to charge and by 8:00 PM it was only at 37%. Switched to USB cable and got it to 90% in a couple of hours. Went to bed at Midnight. Charge was 80%. After I rebooted the device this morning after the SOD, it was at 60%.
A little history.
I was on rooted 4.3, but had connectivity issues to my Verizon Wireless JetPack.
So I decided to roll back to 4.2.2. I installed CyanogenMod 10.1.3 RC2 and lo and behold, I could one again use my JetPack for Internet access.
But then I started to have Sleep of Death issues. I used CM for over a week and and had 4 SOD problems.
I then found out about Wifi Fixer in the Play Store. Went back to stock 4.3 and installed Wifi fixer and all my JetPack problems went away.
But now I am getting SOD issues. I have been on 4.3 since Saturday night, and have had 4 SOD incidents.
I did a data, cache, and dalvik wipe in between each ROM install.
I'm contemplating doing a full factory reset and re-rooting, but I really don't want to backup all my data and reinstall it, unless I really have to.
Are you running an app like Crossbreeder? It has been known to cause random reboot issues and sleep of death.
If you started getting SoD on a CM based ROM running 4.2.2, and it continued after switching to stock 4.3, perhaps it is an app you installed at some point recently. or an app that was updated and the new version is causing problems.
EniGmA1987 said:
Are you running an app like Crossbreeder? It has been known to cause random reboot issues and sleep of death.
If you started getting SoD on a CM based ROM running 4.2.2, and it continued after switching to stock 4.3, perhaps it is an app you installed at some point recently. or an app that was updated and the new version is causing problems.
Click to expand...
Click to collapse
I had installed the Cyanogen cLock widget, because I really liked it. So, I thought that might be it. I deleted the widget, but I still had the issue with the SOD.
And now I am not sure why the pogo cable charging is so crappy. It used to be much faster than microUSB.
I am not running Crossbreeder.
apastuszak said:
I had installed the Cyanogen cLock widget, because I really liked it. So, I thought that might be it. I deleted the widget, but I still had the issue with the SOD.
And now I am not sure why the pogo cable charging is so crappy. It used to be much faster than microUSB.
I am not running Crossbreeder.
Click to expand...
Click to collapse
With all the changes back and forth, I recommend, as you suggested, doing a full reset, data wipe, etc. I was flipping between 4.2 and 4.3 AOKP ROMs and was seeing strange issues as well. I believe my problem was related to corrupted files, partition, etc for the /SDCARD or TIBU because I was flashing a lot of mods and playing around with programs. I finally did a full wipe of everything (backing up TIBU to dropbox first especially the apps that were not in Play Store) and did a clean, fresh install including the apps from Play Store - not TIBU. It was a pain of course having to reset it all back up, but it is working much better now.
If you can, backup via OTG so you have it.
OK, did a factory wipe and used Fastboot to push the stock ROM and stock bootloader onto the device. No Sleep of Death issues, battery life has doubled. Haven't tested the pogo cable yet. But overall it's good to be in a stable place.
Now trying to decide if I want to root again. I really didn't do all that much with root. I think I will leave it this way for a while to get a baseline and then tinker.
Whether you root or not it would probably be a good idea to make a Nandroid backup of everything so that if you have an issue again you have a completely stable and known good configuration to come back to.
I have two Nexus 4 phones and both are 100 % stock but have unlocked bootloader. Both at random get the black screen of death and I have to reboot by holding both volume buttons and power. Is this a known bug with stock?
Are you on lollipop? From what I can gather, this is a known issue among some of the lollipop users.
lolcakes203 said:
Are you on lollipop? From what I can gather, this is a known issue among some of the lollipop users.
Click to expand...
Click to collapse
Yes stock 5.0.1 thank you I was afraid it was a hardware issue
Same happened to me twice already
Zehlek said:
Yes stock 5.0.1 thank you I was afraid it was a hardware issue
Click to expand...
Click to collapse
did you got OTA or flashed factory image
If you got it through OTA then do a factory reset..it is even recommended by Google..
Factory reset will NOT wipe your rom back to kitkat.
I flashed factory images
Yeah, Google should be coming out with a fix soon, until then I'm afraid the only options are to roll back to KitKat or live with it. Perhaps try experimenting with a custom kernel designed for AOSP like Franco or matr1x?
My advice is flash a good custom ROM & kernel, then wait for the 5.1 update
There is a list of known bug with 5.0.2, 5.0.1 and 5.0.0 ?
You should flash CM12, no black screen of death here, i had it on Stock Lollipop like you
Mashed_Potatoes said:
You should flash CM12, no black screen of death here, i had it on Stock Lollipop like you
Click to expand...
Click to collapse
Flashing now
https://code.google.com/p/android/issues/detail?id=79942
This is the issue that is raised in the issue tracker. I have this problem, the only way to stop it from dying is to keep a constant wake lock on the device which drains battery. I might have to try a custom ROM over the weekend to see.
---------- Post added at 05:57 PM ---------- Previous post was at 05:57 PM ----------
https://code.google.com/p/android/issues/detail?id=79942
This is the issue that is raised in the issue tracker. I have this problem, the only way to stop it from dying is to keep a constant wake lock on the device which drains battery. I might have to try a custom ROM over the weekend to see.
Same problem on mine. Sleep of death at random, especially when charging the device. Also, rebooting while doing onerous tasks (such as time lapse recording or GPS navigation).
v5.1.1 seems to have reduced the chances for these problems to occur, but I still happen into them. And if you set a wake up alarm on the phone and it goes into sleep of death during the night, it is not pleasant at all.
I've sent the Nexus 4 to LG tech support because of the power button that is not working correctly, and mentioned the other two problems, even if I don't think LG can do anything on issues that seem to be software related.
Thank you, Lord! I though it was just me. The bug can be reproduced if you try to upload a video in Facebook Messenger app. The black screen is 100% guaranteed.
Mavasilisk said:
Thank you, Lord! I though it was just me. The bug can be reproduced if you try to upload a video in Facebook Messenger app. The black screen is 100% guaranteed.
Click to expand...
Click to collapse
I've just done that a hour ago, that didn't happen.
BTW in the meanwhile since my last reply I've sent my Nexus 4 to customer service two times, the second time was because LG Italia didn't fix the button issue, while they replaced mainboard and battery. During that week before sending the smartphone back to CS for the second time, I've never experienced a SOD (updated via OTA from 4.3 to 5.1.1, being under Lollipop for the whole week).
I've had it back two days ago, chart saying battery and mainboard have been replaced again, button has (finally been fixed) and... ta-dan! Another SOD yesterday, after 24 hours of activity (after a while afternoon of OTA updates from 4.3, again.
I'm glad to see that in the meantime the Issue 79942 has been moved to requesting more info first and assigned then. But that Priority-small makes my nose writhe...
I'm wondering if one can fix it by flashing a different kernel. I can't read of people suffering from SOD on, say, CM 12.1, so it's likely that a different ROM won't have this issue, who knows about only switching kernel.
I had stock SOD for a while, keeping a wake lock active stopped it but did eat through battery. Flashing hells-Core kernel (leaving the rest stock) fixed the issue for me, no wake lock needed.
I am currently using hC-b83-L with no issues, and no SOD.
You can pick it up here if you are interested:
https://drive.google.com/folderview...sharing&tid=0B77BTW0zStYCSTRIYWpZQS1nOWs#list
I've had this happen a few times. Also I've had a few reboots while listening to music using Google play music.
I've been using LMY48I for a long time now and just dirty flashed the system.img of LMY48T 2 days ago. Will have to see if this has solved it.
What bugs me alot more is how the Google camera still does not work...
Sent from my Nexus 4 using XDA Free mobile app
It's been a couple of days since I've removed all of the widgets from the desktop and no SOD since then. Will post updates about this and then try to re-insert widget one by one.
Someone else ever tried this yet?