The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.
No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.
Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.
You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.
I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.
I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App
regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?
I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.
viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App
If missing with software and settings dont work you may just have a bad phone.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.
I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.
For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA
Anyone having issues with their Thunderbolt shutting off and the only way to turn it back on is to do a battery pull? I'm rooted running Ginger3DTh3ory 6.2, but it did this also when I was running Bamf 3.0. Any thoughts on how to fix this?
No idea, are you oc'd?
Sent from my TBolt using my f***king thumbs...
Let me describe what mine has done a few times and you tell me if that's what you're talking about. Twice, in the last 2 days, it's just locked up with the screen off. It doesn't respond to power or volume buttons. Only way to get it to work again it to pull that battery.
BUT... the weirdest thing happened the last time. It did it while I was in a call. I could answer with my bluetooth, talk, and hang up with my bluetooth, but the phone wouldn't respond to anything I did to it.
Is this what you're talking about?
Sound like SOD = Sleep of Death. It doesn't happen to much but a pain in the rear...switch Ur govenor from interativex to ondamandx see if that fixes it
Sent from my ADR6400L using XDA App
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
adoublearonn said:
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
Click to expand...
Click to collapse
the official build's kernel is a piece of crap that is leading to a whole new batch of reboots.
OP, that is usually an issue where your phone is not getting enough voltage. I would do what the other poster suggested and switch your governor. It will give the phone a little more juice so it doesn't do that.
All phones are different when it comes to that stuff.
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Mines running fine. Maybe try reflashing?
jeck77 said:
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Click to expand...
Click to collapse
you have to open terminal emulator (I think its preinstalled on gingertheory, if not there is a free one in the market).
type su (hit enter), it might drop your keyboard, pressing menu will let you reopen it.
type speedtweak.sh
This will open script fusion, there you can change the governor to ondemandx.
Hi everyone, so the other day I flashed the latest sky ice cream (6. 7z) with the latest faux (skyrocket) kernel. Then I noticed that my phones battery was dieing at an alarming rate. (this is also after a ton of issues came up with my phone). Last night I did a nabdroid restore to when I first rooted the phone so stock kernel and stock rom and everything was working great, although I didn't spend enough time to see if the phone was acting up but in setcpu, I did notice the fact that the phone did enter deep sleep.
I am now running red Sonia and yes I did flash fauxs ultimate kernel and now for the hours that I've had it disconnected, the entire time that I haven't been playing with it, the phone has been running at 300MHz.
I'm not at home currently but is there some way that I could diagnose what's going on in terminal? Or some type of logging I could run to see what's running my phone into the ground??
Any way thanks in advance for reading this, and I hope this issue can be resolved.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA App
It was k9, there is a bug with it that makes it do a constant poll. If anyone is interested on the Google Code site for k9, its issue number is 3678.
~PsyCl0ne
Whenever I have the lock screen disabled and reboot phone I get a systemUI fc every time and also half the time I attempt to boot into recovery through the reboot menu the phone just locks up fresh wipe and cleaned the cache or whatever is this a common issue in 1.7?
Sent from my LG-P999 using Tapatalk
The rebooting issue is common with trinity kernel which is the one used with PB I think. So you can flash a different kernel if you'd like , I suggest faux's as it's on par with trinity in my opinion. Or you can just power off the phone instead of rebooting
I'm not familiar with the lock screen issue though as I like having a lock screen
I might as well use faux then, I don't really tweak anything on my phone and have been using faux v48 or something since I read it would improve my battery life but I've seen no evidence of it but if it's going to fix the freezing issue might as well stick with it. I use executive assistant app since I can instantly read and respond to my emails, missed calls, and texts from its own lock screen
Sent from my LG-P999 using Tapatalk
Have you tried using a different rom, not trying to diss PB here or anything, I personally love it and have used it for a long time, I switched to singh-ui because I needed better battery life, even though I'm not a big fan of miui just because it's kinda iphoneish and I hate iPhones with a passion, anyways battery life is amazing using the stock kernel it comes with and its very smooth as well
If you do choose to try Singh-UI use the stable version
I'm having some issues with my S 4g. After leaving my phone alone, such as charging it over night. I'll wake up with it booted in to recovery, or as soon as I go to use it I'll get a lot of force closures. I've tried different ROMS I've tried wipping every thing that can be wiped and doing clean installs and it still happens.
At first I thought it was from my alarm app, so I stopped using it. That didn't help. Thought it might be deep idle, so I stopped using that, still happens. Does anyone have an idea what could be causing this? It's making my phone quite un-usable. I'm current on CM9 nightlies, this first started when I went to the CM9 RC1.
You need to provide more info.
Kernel, clock speeds, voltages etc.
If all else fails, you can always use ODIN to flash factory images of ICS and root from there.
063_XOBX said:
You need to provide more info.
Kernel, clock speeds, voltages etc.
Click to expand...
Click to collapse
I'm still using the kernel that came with CM9. I hadn't flashed a new one on to it. So those would be the stock clock speeds and voltages.
It's really weird, as long as I'm using my phone it's fine, but if I leave it alone for a while it misbehaves.... kinda like my kid.
Delete..........
I tried going back to completely stock, re-rooted my phone and doing a fresh install of cm9. Didn't help anything. Switched to a different Rom and no issues so far
Sent from my Nexus S 4G using Tapatalk 2