The problem:
About once or twice a day my SGS reboots randomly.
When did it start occuring:
A few weeks ago, at first i thought it was Deep Idle related so I didn't think much of it.
Conditions:
CM10 nightly + Semaphore kernel, 110 LiveOC and slightly lowered voltages.
So of course you say this is instability due too the OC and UV(and Deep Idle before that), so I went back to stock CM kernel.
Problem still remained.
I have read a random post about reboots in the CM10 nightly thread but I figured I'd try here first.
I've been using on my old phone xbean for some weeks now and no reboots. I think it is a nigtly bug, not related to kernel.
Try flashing another cm10 based rom.
Cheers,
Don't forget to say thanks if this post helped you.
MobileFirmware.com addict and Nexus 4 user
Your using a nightly build.
This could cause the problem.
My SGS random reboots, too (usually 1 times per day). CM 10 Nightly + Stock Kernel. No other modifications!
The nightly builds are not stable, thus the name. Every bug related should be posted in the nightly thread.
Don't forget to say thanks if this post helped you.
MobileFirmware.com addict and Nexus 4 user
Related
Hi all,
I am still running stock 2.3.6 but I am thinking about unlocking my phone to run CM. Anyway, I have been browsing through the dev CM7 thread and found that there are a lot of random reboots, lockups and other problems in the 7.1 stable release. I am thinking that installing the an older nightly perhaps would give me a better experience. Which nightly would you recommend?
Thanks.
I think its not good to stay on
a single nightly because there are few tweaks with every new nighty which makes it better from last one.
Anyway I recommend you to try cm7.1 rc1 before trying nightlies
For some time.
Sent from my Nexus One using xda premium
On my N1 Cm 7.1 is stable to but playing videos in flash full screen causes so many lock ups, i hope cyanogen would release a minor update for it
dookie23 said:
Hi all,
I am still running stock 2.3.6 but I am thinking about unlocking my phone to run CM. Anyway, I have been browsing through the dev CM7 thread and found that there are a lot of random reboots, lockups and other problems in the 7.1 stable release. I am thinking that installing the an older nightly perhaps would give me a better experience. Which nightly would you recommend?
Thanks.
Click to expand...
Click to collapse
I'm one latest nightly, build 227. Very good and stable for me.
Just make sure you do a clean wipe including system partition
when coming from a different ROM.
Thanks guys! Do you know of a bug tracking page that lists all the bugs that CM7.1 currently has?
Thanks.
Not a bug tracker, but I find this page very useful and visit it daily to see if I want to upgrade to the latest nightly or not: http://cm-nightlies.appspot.com/?device=passion
Looks like the latest nightly is marked as 7.1.0.1... #227 as baseballfanz said. Maybe that will fix the problems you mentioned... however, I will note that I've been running 7.1 stable since the day it was released (nightlies before that) and have had zero problems at all. No lockups, no reboots, no problems at all no matter what I do with it...
7.1.0.1 is a maintenance release for a few devices. The N1 was not included in this list. And most of the reboots and instability issues with the stable release are resolved when people perform full wipes of the phone. It has been rock solid for me.
Thanks guys... I have installed CM71 Nightly 231 last night. It was going smooth at the beginning but I got stuck on flashing Amon_Ra recovery. For some reason my phone wasn't taking the CM themed version but the original version installed fine.
First problem after flashing the ROM and gapps was Market wasn't downloading apps for some reason. I think it was because the phone was reinstalling all the apps at the same time and it just couldn't handle the load. I had to install the apps one after another and that got through it.
The phone rebooted itself when I played a video for the first time, but it's been working rock solid so far. Now I'll have to figure out how to use S2E!
Thanks!
I just flashed nighly 20 ont my p970 and everything seems to be all right. Then i restarted, went back to CWM and flashed v08 nova script. Since that (about 25 mins) my phone is stuck at the LG Logo... Hope any1 has got a solution for me
maybe you should pop out the battery and try again
it happens in v06-v07 as well
if you stuck again,it definitely a bootloop
try the unbrick method
I already got nightly 20 back on my phone and also tried the updated version of the kernel... also tried to update with davlic and battery wipe and without, what else could it be?
Strange, especially as it seems to work for others with this combonation as well...
Same here. Nova v8 stuck in lg logo. I tried remove battery but didn't work. I boot it into recovery and flash CM 20 and nova 7 again.
Enviado desde mi LG-P970 usando Tapatalk
Wow, it's very strange for me if what did happen to you was true, 'cause I'm using CM7-Nightly#20 and Nova v08 Kernel well.
These are steps I've just done:
- Download the kernel then copy it to sdcard.
- Do the davik-wipe. You can find it in the advance of the Recovery menu.
- Flash the CM followed by the Kernel.
- Turn off instead of reboot the system.
Done. I waited for a few mins, then booted my phone. Everything are going fine still now. That is a battery friendly when cost only 2% after 4h.
I also got it to work soon after i posted this, but i had to sleep then and i was busy until now... But the problem was that there were/are different versions of the kernel and 1 of them doesnt seem to work with #19 and #20 nightly, as i tired both, but the nova v08-test1 worked like a charm and is battery saving as hell and i like it VEERY much! even though i am a bit confused that in cpu spy there are only values for 800, 1000 and deep sleep mode. but many others already reported this, so it either is a program bug or really a bug in the governor. Maybe I'll try another one tomorrow and report if this bug still exists But as long as battery drain is ok, i will keep lionheart, as it seems pretty fast to me.
One more thing i noticed is, that even though u set the CPU speed to a lower lvl like 600 it still seems to be set to 1000 according to cpu spy... Anyone else who also experianced this?
Nice work anyway guys and a big thanks
yes , agree, this combination kills your battery deadly
Not for me, installion went all fine. Did not reboot, but shut down instead, waited a half of a minute, then started. And performance is great, and battery got thru my day with 1+ hours of gaming and 3g+mobile network on all the time. (Left with 27% after 10h since unplugged the charger, that's fine for me)
N00BY0815 said:
I already got nightly 20 back on my phone and also tried the updated version of the kernel... also tried to update with davlic and battery wipe and without, what else could it be?
Strange, especially as it seems to work for others with this combonation as well...
Click to expand...
Click to collapse
I used CM7 #19 (as #20 has some bugs when someone calls you) and the latest Nova v08 and it worked for me. You just have to take out the battery after the first boot (if stuck on LG logo) and you should be ok.
P.S.
Another dev (aprold) is now working on Nova and he added some updates/changes on it. You might as well check on his latest post.
http://forum.xda-developers.com/showthread.php?t=1276645
I use cm7#20 and last nova08. My OB works fine. Very smooth. I'm pleased with this kernel. I think CPU spy has bugs. Lionheart os ok.
Sent from my LG-P970 using XDA App
Hi to all.
I`ve just flashed nova kernel v09. It's great.
Here I send you results of nova kernel v09 in CM7#20
Lionheart now true correctly working
Quadrant score.
I`ve forgotten
I didn't run nova script yet
Benchmark results without nova sctript.
Many Thanks to Aprold and knzo.
I still can't write on Development forum.
Hi,
Anyone else having problem with hot reboots? Had texas, bcm and aopk on my phone but never had a solid running system.
Right now I've got aokp which only gives me one reboot right after start.
What is your experience?
I have been running BCM for days now, without any issues. Check your partition formats, start with clean flash and see what happens.
Formated the old sd card via gparted. For the new one I used 4ext recovery...
And I always make a full wipe before I flash a new rom.
happyass**** said:
Hi,
Anyone else having problem with hot reboots? Had texas, bcm and aopk on my phone but never had a solid running system.
Right now I've got aokp which only gives me one reboot right after start.
What is your experience?
Click to expand...
Click to collapse
Which version of AOKP are you using? May 30? It seems that the dev has confirmed the software and hardware problems. He recommends to use 1 or 2 version back. I am using May 27 version and didn't have hot reboot issues often. It rebooted sometimes.
I got the same issue with setcpu v2.4 running with these ICS rom's. I upgraded setcpu then things are OK now.
Sent from my Nexus One using XDA
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
taodan said:
Which version of AOKP are you using? May 30? It seems that the dev has confirmed the software and hardware problems. He recommends to use 1 or 2 version back. I am using May 27 version and didn't have hot reboot issues often. It rebooted sometimes.
Click to expand...
Click to collapse
I also use the May 27th version.
In the meantime I tried every other ICS Rom once more (texas, BCM and Miui V4). Also flashed those roms with the kernel aopk uses.
So far aokp is the best one.
Hopefully aokp will be continued soon.
@phhuang
Good idea. Gonna try setcpu.
What are your settings?
I had the same reboot problems you have with BCM older than 12/06/09.
Since then, no particular problem, except the governor falling back to userspace after each reboot, hence quite laggy.
Hi guys,
I'm on CM10.1 stable and I'd like to switch to a custom Kernel for better performace (mainly smoothness and battery life).
I'd like to know which are your favourites and why (3 reasons). Could be a good help to other novices also.
Thanky you!!!
Giuseppe
beppemila said:
Hi guys,
I'm on CM10.1 stable and I'd like to switch to a custom Kernel for better performace (mainly smoothness and battery life).
I'd like to know which are your favourites and why (3 reasons). Could be a good help to other novices also.
Thanky you!!!
Giuseppe
Click to expand...
Click to collapse
I recently updated to CM 10.1 Stable from 10.0 Stable.
While I was on CM 10.0 I used Semaphore Kernel and had 1) excellent luck and 2) support. Just go to Semaphore's thread and see 3) the praise and 4) respect stratosk (the developer) has earned! Semaphore would be my first non-stock Kernel choice without hesitation.
You asked for 3 reasons and got 4 reasons.
Enjoy!
As I recall, Semaphore supports only Samsung GT-I9000 and Nexus 4.
my fav would be stock
but i ll use semaphore sometimes even in GB, cyancore (if i feel to make my fone a psp ) fishear for testing cm10 ROM, n mackay for twrp (making my friend jealous of touch recovery)
but mostly semaphore
Sent from my GT-I9000 using xda premium
Try semaphore, been using it for a year (and updating of course) and never had a problem with it.
I have used Semaphore for 3 years and i will use it until my phone breaks. :silly:
The last times the best for me is mackay
Latrop is also a really stable kernel
Sent from my GT-P7510 using Tapatalk HD
Random reboots
After about four days of CM 10.1.1 stable I must say that it's very smooth and has good battery (about same as cm 10.0 stable with semaphore 2.6.5 or (even better) Slim Bean 4.2.1 stable in my case). Battery time with CM 10.0 stable and it's own Cyanocore kernel was terrible.
However 1) I have had about two random hard reboots a day while phone was in sleep mode. After full wipe, wipe cache and dalvik it still occurs.
And 2) soft reboots when connecting to PC via USB or updates of apps on internal sd storage. This problem also occured while using Slim Bean 4.2.1 stable. (This problem was never with CM 10.0 stable) It kept coming back after several complete factory wipe and wipes of cache and dalvik.
Can that soft reboot problem be a general Android 4.2x problem with apps moved to SD?
After clean flash and/or full wipe, wipe cache and dalvik I use Titanium to restore to restore all my apps and appdata (only non system relaterd resores). Can the problem be related to Titanium app-restores?
Directly after a random hard reboot I copied as read in some topic last_kmsg and logcat. But what to look for in those files (with a lot of text) after opening them with wordpad?
Why is semaphore kernel so popular ...what are its advantages to stock-kernel, for example in CM ???
freakymod2120 said:
Why is semaphore kernel so popular ...what are its advantages to stock-kernel, for example in CM ???
Click to expand...
Click to collapse
Semaphore is the stock CM kernel on steroids. It lets you use the standard processor governors and voltages and so on but allows other things such as touchwake, a bit better vibration control, deep idle and many other features- I can't remember most of them off the top of my head
Sent from my GT-P7510 using Tapatalk HD
why dont u see n read mr stratosk thread for his kernel n read thru all his satisfy customers n also ask them urself, u will get more than what u wanna know about da kernel mate.
Sent from my GT-I9000 using xda premium
Okay you are right ...but i only want to get some impressions from here ...
compacity said:
why dont u see n read mr stratosk thread for his kernel n read thru all his satisfy customers n also ask them urself, u will get more than what u wanna know about da kernel mate.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No more random reboots
After reflashing CM 10.1.2 (and off course factory reset, clear cache and clear dalvik) I now don't have random reboots anymore.
The difference with last time when I was having random reboots: this time I did not restore apps with data using Titanium Backup. I reïnstalled all the apps via Play Store. Meanwhile I read also in the thread of this rom that Titanium restores causes random reboots and soft reboots off updating/removing apps located on internal sd storage.
Although my i9000 now have been working flawless about the last 5 days, not being able to restore apps and data with Titanium is a real let down. Changing rom and installing apps and setting them up is a real annoying time consuming job. I will now be thinking twice before changing and testing other custo firmware. Hopefully Titanium comes with a solution.
---------- Post added at 03:04 PM ---------- Previous post was at 02:42 PM ----------
The CM 10.1.2 stable rom is working very well now. The original CM-kernel seems much better than the one that came with CM 10.0 stable concerning smoothness, batterytime and stability. CM 10.0 (different flashes and factory resets) had much lag but also bootloops out of the blue sometimes. That led to trying Semaphore-kernel which in my case performed very much better and more stable than the CM 10.0 kernel itself.
That's why I'm very curious how latest Semaphore-kernels perform with CM 10.1.x stable. Has anyone tried that yet?
But the best performing rom I've ever had on my i9000 came after that and was Slim Bean 4.2.1 stable (which includes Semaphore as standard kernel). When the stable version comes of Android 4.2.2 there is a 90 percent change I will reflash Slim Bean. Slim Bean was like CM on steroids and also better batterytime in my case.
Hopefully there is then a solution for the current Titanium errors. Otherwise again reinstalling all apps and setting them up. Or try MyBackup Root in stead of Titanium.
I have already put money a side for the new Nexus 7 and my i9000 is still a great phone which does not need replacement. With the earlier mentioned Slim Bean rom my i9000 even performed better than my brothers laggy Galaxy S3 with stock rom. But everybody knows how terrible for performance Thouchwiz is.
I'm facing a problem of SOD while calling in mi3. I've tried resurerction, omni,AICP, xenonHD etc with lots of kernels(GOD,stuxnet,xelerate and other custom kernels) but no success. I'm fed up with this bug. But i'm not facing this problem in stock miui. I've tried every method to get rid of this sh#t but i'm not getting anywhere. Please help!!!!
try Ivan's lollipop rom.. it is the most stable rom
Sangeet007 said:
I'm facing a problem of SOD while calling in mi3. I've tried resurerction, omni,AICP, xenonHD etc with lots of kernels(GOD,stuxnet,xelerate and other custom kernels) but no success. I'm fed up with this bug. But i'm not facing this problem in stock miui. I've tried every method to get rid of this sh#t but i'm not getting anywhere. Please help!!!!
Click to expand...
Click to collapse
No SOD in blisspop either
No SOD on CM12.1 or DU either.
I got 2 SOD on DU while on call both the times. I am running latest DU with God's R4 kernel. Latest rom dirty flashed. Anyone with any inputs on what is causing that?
Kernel changes:
CPU Governer - elementalx (Also got occasional SOD with yankactive on call)
Freq - 300 - 1728MHz
CPU Voltage - Global offset -20
GPU - Max - 389Mhz
GPU Governer - simple_ondemand
IO Scheduler - fiops
Me too... I have AICP installed faced it on 14th build so switched back to 1st but now SOD after kernel, i have also noticed that while doing GPU setting in kernal auditor my phone is going in SOD. I have tried all the kernels same issue. my GPU frequency is getting locked at 200 mHz no matter whichever kernel or GPU governer. SOD is not very frequent though faced 2-3 in last 2 days
santy neo said:
Me too... I have AICP installed faced it on 14th build so switched back to 1st but now SOD after kernel, i have also noticed that while doing GPU setting in kernal auditor my phone is going in SOD. I have tried all the kernels same issue. my GPU frequency is getting locked at 200 mHz no matter whichever kernel or GPU governer. SOD is not very frequent though faced 2-3 in last 2 days
Click to expand...
Click to collapse
I used AICP quite a lot in the past with my cancro (I used AICP for 1 year solid on my Nexus4), but late September cancro's nightlies began to have random issues such as SOD, so I gradually stopped using the ROM, since one nightly would be OK, the next one not...
I've also tried to keep off CM ROMs - I've been using TeamEOS' ROM for a while now, it's AOSP... I can also recommend the latest Dirty Unicorns, also AOSP.
At this stage in the proceedings, definitely no need to stick with a ROM with SOD... use Titanium Backup to restore all your user apps and data, and you can be switching between ROMs and fully operational in 30 minutes
@Sangeet007 - everything can't be bad... choose a ROM/build carefully, install it with the Gapps people are OK with on that ROM's thread, and do NOT install any of your user apps for 24 hours. Just see how it behaves, making calls and browsing etc. I'd be really surprised if you experience problems with ROMs such as TeamEOS, BrokenOS, Dirty Unicorns.
I would also stay away from builds generated automatically, even though it sounds odd, an unofficial build is often more stable.