Related
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
I'm new to the forums here and I just installed CM7 on my phone the other day. Ive been trying to overclock my phone but every time after I install it, the phone is so unresponsive that I have to reload CM7 again because its unusable. The bottom home and menu buttons don't work either. Does anyone else know why this is happening or the solution?
Overclocking is built into cm7. You don't need any other app
Sent from my SAMSUNG-SGH-I777
How are you trying to overclock it? What are you setting it to? What type of governor are you setting? Mine locks up when I use SmartassV2.
http://forum.xda-developers.com/showthread.php?t=1103414
i personally use the tiamat kernel and setcpu to overclock on cm7, since the stock cm7 kernel only goes to 1.5, but still even without overclock cm7 is never unresponsive or "unusable".
I've had mine oc to 1.2ghz and min is all the way down on ondemand setting. Im using absolution right now and I'm not seeing the greatest of battery life like i did with cm7 and talonace's kernel. but I just turned off all animations on the phone today so I'll update you tomorrow
I actually underclock with CM7 and it's still snappy and responsive. Slows down a bit when syncing, but otherwise it is solid even when clocked under stock.
First off if this is the wrong place i apologize. I have searched for the better part of the day on a couple issues and haven't found any solutions to my last problem. I have a htc inspire running CM7 stable. The other day i started to flash different kernels to try them out. I started off using Lordmod V8.1 BFS. I liked everything about it but i was experiencing my data connection and wifi would stop working through out the day and i have to reset my phone and it would work. Then it would happen a little later on. Next I installed TalonACE 7x30 v1.1.1 BFS and have had only a couple internet drops and wifi but mostly the same problems. Sometimes the bars would be gray other times it would still be green but with no connection. I also flashed a new radio. (a recommend one from xda) 12.54.60.25P_26.09.04.11_M2.
So my question is, is it the kernels, CM7, or the new radio I flashed. Also if anyone knows a link to my question please inform me or any methods to fix this issue. Thanks
This actually has been an ongoing battle to pinpoint in lordmods thread. The consensus is leaning towards it being a rom issue. Based on my testing I tend to agree. For now the only "fix" is to use cfs kernels
I am experiencing this as well.
HTC Inspire 4G
BBMod Rom v1.6.0b
TalonACE v1.1.2 BFS (BRAZILIANWAX)
No UV
I'm using Absolution which is cm7 based and had similar problems along with battery issues, so I changed to talonace miui 1.09, all mi issues are gone. Also I use stock radio
Sent from my Inspire 4G using xda premium
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...
Hey guys, I bought myself a Nexus S one month ago and I've flashed about 15 different ICS ROMs. Is it just me or are there almost no stable ICS ROMs? All of them had random reboot issues apart from AOKP and CM9. I had no reboots on AOKP but the clock got stuck every 2nd day, so my phone wouldn't wake me in the morning which is even worse. CM9 I liked a lot, but I couldn't phone in the hands free mode (don't know the propper name of it in english) because the mic wasn't loud enough. Currently I'm on ras cream sandwich and it reboots while i'm listening to music which is really frustrating. Oh and before i forget, I always flashed matr1x kernel and used smartass governor, no OC.
Is there any stable ICS ROM apart from CM9 and AOKP? Or can i fix the other bugs?
Thanks in advance!
Your problem is the kernel, not the rom. My phone also reboots while listening to music in the undervolted matrix kernel. Stay with rascream and flash the _thalamus kernel and see how stable it is. That kernel is really stockish and stable. If you don't want to flash you could try to raise your voltages to stock values in nstools. Some phones like undervolting, some not. ;-)
Verstuurd van mijn Nexus S met Tapatalk
hm I didn't know matrix kernel was undervolted, I thought that's only the case with trinity TEUV kernel by default well I'll try another kernel for the time being and see how that goes.
Yeah. Some of our phones can't handle the voltages mathkids kernel supplies outta the box unfortunately. Either adjust them back to the stock ones or search for another kernel. I prefer either thalamus or Simple Kernel. I just recently flashed the latest version of the former and its great. You can try Air kernel if you want a few more governors and whatnot.
Sent by pocket technology.
Like.. that's what STOCK is all about.
The people that made the phone are the most interested in making a stable ROM, no compromises.
Most stable and fast rom
Try APEX ROM 1.1.2 (latest release), that's what i'm using until aokp milestone 6 comes out. there is no lag, no reboots (just if u OC too much),...
Slim rom with no tweaks is smooth. Try it and u will not regret it.
Good luck
Vs Nexus S 4G
MIUI roms are very stable these days.
Sent from my Nexus S using Tapatalk 2
Well it differs from phone to phone. My phone is good with Matrix kernel. Might be one of the best custom kernels to run for my phone if not the best. Matrix isn't a compromise for my phone.
Sent from my Nexus S 4G
For several days I'm with Slim ICS and Matr1x and I have no problems with random restarts. No OC and no tweaks!
Try CyberGR ROM
I have installed CyberGR ROM and I have not suffered any reboot. I followed one by one all the steps of the development part and I'm quite happy with it.
Good luck.
Well, if you really want stable, get Stock 4.0.4. I'm on 1100+ hours on uptime without a single reboot... The only thing I've done to the stock 4.0.4 is getting root.
I would also like to know. from my own experience, stock 4.0.4 is best, but can CM9 very be made that stable? I'm running it now with ink kernel and no tweaks and it seems slightly laggy :/ should I flash brainmasters tweak pack?
Sent from my Nexus S using xda premium
Bugless Beast hasn't given me any issues. I've rebooted to flash other kernels but the only two kernels that have given consistent performance are Simple(stock with bln) and thalamus. Once I get my new battery, I may see how long I can go without rebooting. But if you want rock solid, go with stock ROM. Hell, my cousin has an EVO 4G and has almost 1200 hours up time. Lol.
Sent by pocket technology.
AOSP+ definitely belongs to this category. Stock with a few useful modifications.
You should try AOKP again
I know you've already used AOKP but you should try/flash it again. I'm sure that the clocking was freezing because of some flashing issue.
Go to this link and download the milestone-5 version (m5) of AOKP. Also, you should use this rom with matr1x v19.5 cfs.
Milestone means that it's stable, so you shouldn't have problems with it. I use this rom and matr1x 19.5 on my daily device and haven't had any problems nor reboots. Great performance and great battery life too. Besides that, the rom is highly customizable.
Apart from stock, Have you tried BuglessBeast? Very stable. No need to flash any custom kernels.
if ur using ra scream use one of the trinity kernels. its super stable, super smooth, and long battery life
im using this black ice rom, in love with it .. shud try
alexfiorani said:
I know you've already used AOKP but you should try/flash it again. I'm sure that the clocking was freezing because of some flashing issue.
Go to this link and download the milestone-5 version (m5) of AOKP. Also, you should use this rom with matr1x v19.5 cfs.
Milestone means that it's stable, so you shouldn't have problems with it. I use this rom and matr1x 19.5 on my daily device and haven't had any problems nor reboots. Great performance and great battery life too. Besides that, the rom is highly customizable.
Click to expand...
Click to collapse
I searched the internet and apparently I'm not the only one with that problem. I tried AOKP twice (i think build 32 or something and m5), always with matr1x kernel. Could this also be a kernel Issue?
I don't know that much about Android, but what I found out in the past days is that my Nexus S can't handle UV. I also get very high Android OS battery usage sometimes but I don't know why. High meaning Android OS once used more battery than display even though i had 2h screen on time. I suspect it's got something to do with titanium backup not restoring apps correctly, but that's just a stab in the dark.
Currently I'm on Apex v1.1.2 with stock kernel. No random reboots so far. I didn't restore apps via titanium backup (which was a pain in the ass). So far Android OS seems to use way less battery than before. But yesterday I had something like SOD when received a call while using TuneIn, so I had to pull the battery and call back. Not what I call stable.
I know that's a lot of text and probably also a bit OT sometimes but I hope some of you will read it , I'm not really a flashoholic and I'm getting sick and tired of switching roms, but I need my phone to be reliable. I'm really tempted to just switch back to stock ROM with stock kernel at the moment...
the things I'd really like to have is bln, notification toggles and stability.