Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
Never had one so far. Running stock 4.2.2/Franco kernel nightly_110
-Edit- currently undervolted -75 mV.
just stop messing your phone up with stupid OCing and benchmarks... This issues are installed to protect the hardware from crashing... ( Red light of death... )
My phone just fine. never had this SOD.
Never had an issue on this device. On my old phone, dropping the min CPU speed too low would cause it a LOT.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
You don't have an option for unable to turn on phone without a reset: no blinking led. This is also a scenerio.
Please take a look here! http://forum.xda-developers.com/showthread.php?t=2195278
I've tried almost everything (wipe& re wipe , install stock ) and nothing seem to solve it.... most frustatin thing is when I hit "home" after playing heavly and ...bamm it goes black screen & hav to reboot pressin home&vol+
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Im using it now (customROM&UV) since it doesnt affect my issue.... I tried completly stock for 2 days and keep crashin... or at least on g.earth as I didnt install any app/game to be sure its not an app related issue.
Cant figure out what happens, it can play games w/o any issue, but sometimes when I change orientation it just goes black
PD: I dont hav enough time, but ill do a logcat to see what can possibily make it freeze
My case is not listed in the poll options:
- the phone went into standy, good battery, no calls, no high loads;
- LED was inactive totally.
- then I was unable to turn it on normally (only through reboot).
While in this state, trying to call the phone resulted in "long" tones, i.e., like the network saw the phone. The phone did not ring.
This happens with the latest stock firmware on the 2nd day of my use. Non-reproducible. Phone returned.
Would be delighted to learn if that's a hardware or software issue
Not necessarily SOD but experienced extreme battery drain under these situations
1- Charging via USB and left phone connected after PC shut down.
2- Charging via Wireless Charger left it on the pod.
In 1st ASA pc is shut down
and
In 2nd ASA Phone charged completely , as I suspect the charging process goes backwards ! It someone drain current from your battery to the power source.
AFAIK none of these issue are positive with normal good old AC charging. However you can still use a workaround by using the app called "Safe Charge"
This is my experience
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
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
My nexus 4 was bought about one month after it was released .
I didn't have this issue in the first three months ,but recently ,about in the past one month ,it occurred kind of frequently and randomly.
Here is the issue:
I lock the screen and leave it there without using .When I am ready to use it ,I cannot awaken the screen even after I press the power button several times, both short and long press ,as if my phone was powered off ,even though I know its power is still 50 percent or so. After a series of random press ,I give it a long press ,then it gets rebooting .
I have been searching on the internet and many Nexus 4 users have this issue ,however, nobody can tell exactly what causes this problem .Some say it is caused by snapdragon batteryguru and some say the battery is not firmly installed .
I don't know whether you guys have ever come across this issue ,what is your analysis about it and how you solve this boring problem...
Glad to see that I can find solutions here...
My nexus is running original android 4.2.2 and is not rooted.
sleep of death. long press (10-20 seconds) powers off/reboots the phone. can be caused by phones software, undervolting and apps.
i haven't got any issues like this, have you installed a rom? if you have try another rom, also remove battery guru as suggested
mlndshh said:
i haven't got any issues like this, have you installed a rom? if you have try another rom, also remove battery guru as suggested
Click to expand...
Click to collapse
mine is running original android 4.2.2 and I never installed other roms...
simms22 said:
sleep of death. long press (10-20 seconds) powers off/reboots the phone. can be caused by phones software, undervolting and apps.
Click to expand...
Click to collapse
Thanks
But it seems difficult to find out a proper solution ...
youngwuno1 said:
Thanks
But it seems difficult to find out a proper solution ...
Click to expand...
Click to collapse
if its an app, figure out which one it is.
So, just a little bit of background, I got my Nexus 7 on Christmas 2012. Recently, my Nexus 7 has been "shutting off" (I put it in quotes because it isn't really shutting off: the screen is just refusing to turn on) in the middle of the night. I've also noticed the whole screen freezing when controlling volume in certain conditions. Since I use my tablet for my alarm, having it off is doing me no good. Does anybody have any idea how to fix this? I thought it was a loose battery connector in the internals, but there was nothing loose.
I am running Google's official stock KRT16S with Oxydo kernel v14.
Thanks!
Sent from my Nexus 7 using Tapatalk 4
I suggest you go back to stock Rom with stock kernel and make sure the problem still exist.to solve a problem, first thing you have to do is find the cause of the problem, especially in here you have to find if it's software issue or hardware.So go back to complete stock conditions and check if the problem persist and if yes I would conclude it could be a hardware issue. It's hard to give more help without knowing more specific details like when did it started and if it's in that condition all the time ? Some pictures or screenshots will get you more help
go back to the stock kernel or try not to undervolt your kernel, you are having screen of death issue, device is not getting enough power.
also try a different kernel, not all kernels behave good on all devices.