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
Hi my Samsung Infuse sometimes starts vibrating and then it turns off randomly, does someone here is experiencing this problem too?
If it vibrates once, then twice and reboots I think somwthing is force- closing but why it reboots Idk. Mine was doing that at one time (dont remember what rom/kernel I was on @the time) but I flashed 2 stock, then back to bionix & havnt had problem since
Mine does this too. Except when it reboots, my wallpaper changes back to what it recently was before I changed it (even after I deleted the obnoxious picture).
After flashing to Infuse 1.5.2, the wallpaper and shortcut locations were all normal (also lost my texts, not a problem). Later on, it vibrated and rebooted again, and all my old shortcut locations were back, my old wallpaper was back, and all of my texts were back, but I was still on Infused v1.5.2
It's kind of annoying seeing as it happens every other day or so.
might be too much UV
i only had this happen with test kernels on bionix -almost- never with infused
drowningchild said:
might be too much UV
i only had this happen with test kernels on bionix -almost- never with infused
Click to expand...
Click to collapse
im not doing any UV/OC, this problem also existed when i was in stock firmware, i updated now to infuses 1.5.3, lets see if the problem persist, nobody know a possible fix?
Everytime I flash a 2.3.4 Rom (All CM7 Nighty's and MIUI), my phone seems to overheat. I kept it stock kernal at first, then I tried both faux's and morfics UV kernals and that didn't help either. But when I revert back to Froyo, it doesn't heat up at all.
Any experiencing the same?
Yup samething here. I experienced that with the new eagleblood rom and the new gingerbread leaked update. I notice that whenever i get overheating the phone automatically shutdown. Funny enough a tmobile rep persuaded me to buy a new battery by telling me that the one I have right now is faulty and is what cause the random reboots and shutdowns. Do you experience any of those issues with your phone as well?
Sent from my LG-P999 using Tapatalk
No reboots, No blackscreens, it just gets really hot in the back whenever a 2.3.4 rom is running.
Hey guys, getting some weird behavior from my Nexus S 4G (currently running CM7 nightlies with the stock CM stock kernel)...
The screen will go off and I cannot get it to turn back on without doing a battery pull and rebooting. I cannot press the power button and get the screen to turn on, and I cannot hold the power button to reboot the device.
This is an intermittent problem.
I'm currently running CM7 (as mentioned above), but it was also doing this on a stock, rooted, deodexed 2.3.5 rom with the Matr1x 5.5 kernel.
I'm wondering if it is some rogue app that is causing the issue? I'm trying to run a logcat on it and catch if there are any fatal errors, but I've been unable to catch it happening.
This issue has happened at least 6 times over the past 3 days.
I've heard of this happening when people undervolt too low, or use SetCPU profiles with screen off less than 800. Probably not your issue though.
If nothing else works, you might try the V6 SuperCharger script. This has dramatically improved my phone's response times.
Sent from my Google Nexus S using XDA App
berkmanmd said:
Hey guys, getting some weird behavior from my Nexus S 4G (currently running CM7 nightlies with the stock CM stock kernel)...
The screen will go off and I cannot get it to turn back on without doing a battery pull and rebooting. I cannot press the power button and get the screen to turn on, and I cannot hold the power button to reboot the device.
This is an intermittent problem.
I'm currently running CM7 (as mentioned above), but it was also doing this on a stock, rooted, deodexed 2.3.5 rom with the Matr1x 5.5 kernel.
I'm wondering if it is some rogue app that is causing the issue? I'm trying to run a logcat on it and catch if there are any fatal errors, but I've been unable to catch it happening.
This issue has happened at least 6 times over the past 3 days.
Click to expand...
Click to collapse
It almost sounds like a power failure.
If this happened on my phone, I would install stock Rom and stock kernel. I would run that for 3 days. If it happened one more time on stock, I would file a warranty claim. If it did not, I would then troubleshoot further on the software side.
Dude, you nailed it. Thanks!
I was using a single SetCPU profile to underclock to 1000 when the screen turned off in an attempt to save battery.
This got passed along when I switched roms due to TiBU. It was driving me crazy...
Sent from my Nexus S 4G using XDA Premium App
Is anyone else experiencing this? I get it on Viper 2.2.0 using beastmode, elemental and stock kernels. BM and Elemental were both max 1.7, min 192. I have completely wiped everything, including sd and did a fresh install of viper 1.2.0 up to 1.2.4 with elemental kernel with no issues. Bumped up to 2.2.0 and installed elemental. I made a few test calls and it seemed to be ok then a few hours ago my gf called and it was back. Every single call my phone reboots..Anyone have any ideas? I had been using 2.2.0 for over a week then it just started doing the reboot thing yesterday. I'm currently wiping everything and rolling back to either 1.2.4 or king cobra 1.5. It's so frustrating because I was getting the best battery life I've ever seen on my phone with the viper 2.2.0 beastmode 4.3 combo. All helpful thoughts or suggestions are welcome.
I've not run Viper, but I have the same experience with any of the JB roms. Its even worse with custom kernals, so you might try it without. Just an idea.
After trial and error (flashing, setting up my rom a few changes at a time, test calling to see what breaks calling, wiping..rinsing and repeating) til 5 in the morning I think I've finally figured out my problem.
Turns out for me it wasn't a kernel issue at all, or even a rom issue for that matter. I love the aosp lock screen way more than sense so I would un install the HTC lock screen with tibu; that was fine, no reboots. Then in venom tweaks>lock screen I enabled aosp lock screen...still fine. Then lastly I enabled aosp call work around and bam! Reboots every time! I disabled the work around and have not had a single reset and I've probably made around 15 test calls just to be thorough lol.
I've tested while locked, unlocked, on the lock screen, while browsing, watching YouTube, rebooted then tested...I hope I'm not jinxing myself here but by jove I think I've got it. My settings from a clean wipe are viper 2.3.1, stock radio, beast mode 4.4, max 1.7, min 192, no gpu over clock, mp decision on, s2w off, intilidemand governor. So far everything has been humming right along and working like a charm.
I can't believe I overlooked something so simple and immediately pointed the finger at the rom and kernel when it was my own damn fault lol. Sorry to make so much clutter in the thread but hopefully it can help someone having the same issue.