So, I'm kind of curious about the sod issue that the current aries kernel port has. i know it means sleep of death but does that mean that sometimes it won't come back on from the lock screen and you have to do a battery pop? How long does it have to run before that happens or is it random as hell? I'm just curious as to is it impossible to use a rom with that kernel because of the issue.
Sent from my SGH-T959V using xda app-developers app
And that's why there is no ROM with that kernel for use, other than the one release Brian did. No one is saying to use it for any sort of daily use whatsoever.
goddi2010 said:
So, I'm kind of curious about the sod issue that the current aries kernel port has. i know it means sleep of death but does that mean that sometimes it won't come back on from the lock screen and you have to do a battery pop? How long does it have to run before that happens or is it random as hell? I'm just curious as to is it impossible to use a rom with that kernel because of the issue.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Yes. SOD you need to pull battery or possibly long press power button. And it happens when the phone sleeps.
Do you you if it's every 1st attempt to push the sleep button or does it happen after a period of time when it's sleeping?
Sent from my SGH-T959V using xda app-developers app
goddi2010 said:
Do you you if it's every 1st attempt to push the sleep button or does it happen after a period of time when it's sleeping?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
It's kind of an interesting issue. It might be a SoD (sleep of death), it could be they cypress keyboard driver which controls the volume, power, and capacitive keys, it could be a regulator issue, it could be an issue with the pmic or battery drivers.
So many possibilities.
It happens everytime you push the power button on the phone to turn off the screen. My life is seriously complicated right now and every spare minute I have is spent on figuring out this issue, continuing to maintain the cm9 herring build, porting sk4g (sgh-t839) to teamacid's cm7, and looking into work on the at&t galaxy note (sgh-i717).
m4xm4n and jeffsf are also helping out on the sgs4g aries SoD issue, but it's a very complicated issue. We'll sort it out soon!
Thanks bro no rush I was just trying to get a better understanding of the sod problem and you answered it 100 percent.
Sent from my SGH-T959V using xda app-developers app
Related
Anyone else have an issue hanging up after a call? Sometimes it takes up to 30 seconds to end my calls it has happened on multiple roms. I'm on Wind mobile btw... Wondering if there is a fix or if that's just life with the g2x.
Pin it to Win it.
I've only had issues like that on stock 2.2 Froyo. Never had the issue since.
If you have a setcpu profile set for in-call, it happens. Try going into accesibility and enable power button end call to see if it helps hanging up.
Sent from my PG41200 using xda premium
wyldkard said:
If you have a setcpu profile set for in-call, it happens. Try going into accesibility and enable power button end call to see if it helps hanging up.
Sent from my PG41200 using xda premium
Click to expand...
Click to collapse
Ooooo good idea
Pin it to Win it.
More info needed. Rom? Kernel? It is helpful if everyone that has some quirky thing happen posts more details. No offense intended towards the op.
This has happened to me on a few different ROMs and turned out it was a memory issue. I deleted all of my music and woks like a dream again
+1 on the power to end call... love that feature
I have the same issue in CM 7.2 with trinity and faux. Doesn't bother me though.
EDIT: Actually, i just flashed the latest nightly and the bug is gone now.
Sent from my LG-P999 using xda premium
jcbofkc said:
More info needed. Rom? Kernel? It is helpful if everyone that has some quirky thing happen posts more details. No offense intended towards the op.
Click to expand...
Click to collapse
Happened on all the roms i was running and the power button to end call fix totally worked for me
Running HFP 1.8 w/Faux 048 on Wind Mobile in Calgary, Ab.
Yesterday I watched about an hours worth of Netflix, set the tab down and then approximately 6 hours later picked it up and it was turned off. Attempted to turn it on, no dice. So I plugged it up to charge but can not charge or power it up even with the cable plugged in.
Its 3 months old and obviously I can send it to Samsung for repairs but I would hate to do that if you guys have an idea how to fix it.
Anyone got any ideas?
Sent from my Galaxy Nexus using xda premium
Problem solved. Held the power button down for 15 seconds as suggested after a google search and it came back to life.
Strange how something so simple is the answer.
Sent from my Galaxy Nexus using xda premium
It's called a SoD, or Sleep of Death. It usually happens when using some sort of Deep Idle/processor idle kernel feature. If you're using stock ROM, it's probably just a kernel glitch and was most likely a random occurrence. If you're using a custom ROM/kernel, then turn off didle/deep idle!
MultipleMonomials said:
It's called a SoD, or Sleep of Death. It usually happens when using some sort of Deep Idle/processor idle kernel feature. If you're using stock ROM, it's probably just a kernel glitch and was most likely a random occurrence. If you're using a custom ROM/kernel, then turn off didle/deep idle!
Click to expand...
Click to collapse
Stock rom. I haven't gotten around to flashing one yet as most of the time i am too busy flashing my phones. Thank you for the info though. Hopefully it doesn't happen again anytime soon.
Sent from my MB865 using xda premium
So my Blaze is having some catastrophic problems. It started out the other day by turning off and then vibrating like crazy in my pocket in the same way it would of you were holding the power key down, and it wouldn't stop. I pulled the battery, replaced it and it immediately started vibrating and wouldn't stop as if the power button were stuck in.
Long story short I took my phone apart and removed the plastic button and can get it to boot and stay on for a while. It still craps out sometimes, but I've had it on for a couple hours now with out the plastic part of the power button. I can still hit the button with a pen, BUT here lies my problem...
If I so much as look at the power button funny, it decides that it wants to get stuck down and won't go back up. The actual moving part doesn't get stuck, I think it's electrical.
So if anyone has any clever ideas on how to fix this, I won't have the money for a new phone for a couple weeks and it will make my life very happy to be able to make this one usable
It works sort of if I never have to press the power key, and I remember using a ROM that had the volume locker wake option, but for the life of me I can't remember which one it is. So if someone could help me out there too, that'd be great
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Cm10 has volume rocker wake in display settings.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Oh gosh thank you so much.. I couldn't remember where to find it lol
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
That's what happened to me! Can you please list what you flashed before the problem or your ROM and kernel at that time?
Sent from my GT-N7100 using xda premium
Jserrano56 said:
That's what happened to me! Can you please list what you flashed before the problem or your ROM and kernel at that time?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Gosh I'm kinda flash crazy, I believe I was on the most recent version of Paranoid Android with whatever version of LZ Kernel comes with it. I originally thought it may be a ROM / Kernel issue so I flashed CM10, and it was still broken.
I don't actually think my problem is a software (ROM or kernel) problem. If it's stuck resetting and I pull and replace the battery, it starts to boot without me touching the button. That means the problem is occurring before any of the software even loads.
I'm pretty certain it's a problem with the button. If I so much as touch it, it acts like it's stuck depressed. I think it may also be heat related, so maybe the ROM or kernel may have caused some overhearing that damages the hardware, but I don't know. It was definitely super hot when it first started.
Hope that helps you!
And if any devs or anyone has any idea about this.. That'd be great
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Morganmachine91 said:
Gosh I'm kinda flash crazy, I believe I was on the most recent version of Paranoid Android with whatever version of LZ Kernel comes with it. I originally thought it may be a ROM / Kernel issue so I flashed CM10, and it was still broken.
I don't actually think my problem is a software (ROM or kernel) problem. If it's stuck resetting and I pull and replace the battery, it starts to boot without me touching the button. That means the problem is occurring before any of the software even loads.
I'm pretty certain it's a problem with the button. If I so much as touch it, it acts like it's stuck depressed. I think it may also be heat related, so maybe the ROM or kernel may have caused some overhearing that damages the hardware, but I don't know. It was definitely super hot when it first started.
Hope that helps you!
And if any devs or anyone has any idea about this.. That'd be great
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Here no stop reboots and over heating and it too would button before I pressed any buttons
Sent from my GT-N7100 using xda premium
Hey guys I have been having a pretty serious issue the last couple of days. Was running a CM 10 teamchopsticks nightly from a few weeks ago, which worked perfectly up until three days ago. Then it started crashing randomly, the screen would go black and it would vibrate every few seconds, a battery pull would fix it. I updated the phone to the latest nightly, and now I can't run the phone for 5 minutes without the same type of crash. When I battery pulled and tried to turn on the phone, it would immediately crash about 4/5 of the time. This bug is rendering my phone unusable. Not sure whether this is a Rom issue or something else, thanks in advance.
Not sure what kernel I am running.
Hearing it may be a hardware issue, anyone agree?
Could be, try to odin stock jb or ics. If you still have the problem then it's probably hardware. Unfortunately the rocket is getting old. I'm having some old age problems with mine too. Mostly stuck power button.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I am hearing broken power button, how do I fix?
nsilverman15 said:
I am hearing broken power button, how do I fix?
Click to expand...
Click to collapse
I don't Think you have it. Take your battery out and then put it back in. If it boots at that point then that's a sign that you probably do. Or if you try to try to power off you phone but it reboots then that's another sign
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Getting the first thing you said
nsilverman15 said:
Getting the first thing you said
Click to expand...
Click to collapse
Could be a stick power button then, that's almost a sure sign. Mine is intermittent. Some times it's ok, others not not.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hello all,
Semi-noob here, I've rooted and flashed my phone to the Stable version of Cynogenmod, on Android 4.1.2. I haven't added the Lightning Kernel, only because of a pretty annoying issue: the phone randomly shuts down for no apparent reason. I ran a search and didn't see much about this issue so here goes: doesn't matter what's going on with the phone, it will suddenly (and very randomly) freeze for a moment, then go black, the Samsung logo will appear, it'll vibrate, then kaput.
To turn it back on, I have to do one of 2 things:
-hold the Power button for a LONG time;
-remove battery, reinsert, hold Power button normally.
So what gives? Did I flash something wrong? Should I reflash the ROM? Any assistance would be greatly appreciated,
Cheers!
I'd think it's the screen of death.
But when I look at this more, I think of what the oc, governor and scheduler are.
Sent from my SGH-T769 using Tapatalk
The stable version is not very stable. Look for the latest nightly, its much better.
For the latest cm 10 10.1 and 10.2 go here http://www.goo.im/devs/cm/t769/nightly
Look closely at the dates to get the right one.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Somcom3X said:
I'd think it's the screen of death.
But when I look at this more, I think of what the oc, governor and scheduler are.
Sent from my SGH-T769 using Tapatalk
Click to expand...
Click to collapse
In retrospect, I should have thought of that, thanks! I changed it to Performance from Interactive after reading this last week and since then no shutdowns at all. Hopefully this is the end of that annoying bug. Merci! :good:
Whoops, no sooner had I written that than my phone shutdown again. WTF? Anything in particular I should do to stop this?
Try the latest cm 10 nightly? That is what I'm running on 2 phones with no shutdowns like your describing.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
tommyboy8125 said:
Try the latest cm 10 nightly? That is what I'm running on 2 phones with no shutdowns like your describing.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I might flash it when I get back to the US, I am on a long-term business trip and last thing I need is to brick the phone while in France!
I've had similar issues with CM10 "stable". I knew the rom was at fault. I haven't tried the nightlies, but that would have been my next guesses too. I've been looking for a daily driver, and despite some hiccups with MIUI, I've been pretty happy with it.