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.
Related
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.
model: SGS international GT-I9000
due to corrently hot topic ICS on air everywhere
so im going go give it a try
at the first whn im on 1.12.30miui rom with glitch kernel, i upgrade to OneCosmic 2.11 with glitch kernel too, i realize that my phone is hot, after that i use all the check what happen with my cpu keep running on max speed for few hours for DRM, Media storage and download manager...
after 1day of using on 2.11 i feel like not hitting my target of lagfree, so im changing bk to miui 1.12.30 and after boot up, i get the same thing happen again, my cpu keep running on max speed for same, seem like it keep running on scanning media storage.
i just want to know why it keep running like thay, can anyone give me a answer? or is it because of gallery＋?
SGS GT-I9000 OneCosmic latest build!
onecosmic is still in beta is not final ics so there's bug, because the cpu heat is forced because of such applications that are open gallery
c0c05 said:
onecosmic is still in beta is not final ics so there's bug, because the cpu heat is forced because of such applications that are open gallery
Click to expand...
Click to collapse
i dont think so...
when i change back to miui 2.1.13 im also having the same problem...
SGS GT-I9000 OneCosmic latest build!
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
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
henriqueberthem said:
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
Click to expand...
Click to collapse
Did you overclocked it? If you did - that is the reason.
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
henriqueberthem said:
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
Click to expand...
Click to collapse
Try using CoCore 8.2. And revert settings that you have changed to default and see what happens.
Deepsleep should be 3 or 4, on 5 it gives same result that you are getting. Freez and reboot on some time.
My deepsleep is "3".
henriqueberthem said:
My deepsleep is "3".
Click to expand...
Click to collapse
Then do first thing I told you before that. Without any customization, and with 8.2 version.
Ok, I'm going to flash to 8.2 cocore and keep the default configuration for testing
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
henriqueberthem said:
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
Click to expand...
Click to collapse
Try that newest.
8.2 was pretty good. No matter if it is old.
I tried the newest (Cocore E-v10) and still suffering from random freezes, causing the responses to touch are noticeably slower.
At this time I will flashing to version 9.6
Hello friend.
I tested the newest version of the kernel (refresh-r08 @ 14-Jul) and a few days ago that had no reboot.
But before I used the app tweek (cocore manager v2.1 or Kui) and believe they left is that my system unstable, because after that they uninstalled and I started to tweek the command promt using the Busybox my system has become lighter and reliable.
So it leads me to believe the problem was in the app customization.
Hey,
I've already made 2 other threads like this but since I keep finding out why this is happening and nothing worked so far, here I am with another thread
Basically, when I switch to any other kernel, it makes my screen flicker, which is very, very annoying...
I tried almost every kernel for my SP, including the DooMLoRd kernel for the stock firmware.
For cm11 I tried the FXP kernel and the stock one included in the official build. Both ROMs gave me screen flickering.
Things I tried:
-Forcing GPU rendering and disabling HW overlays at the same time.
-Trying a few scripts which claimed to have fixed the problem.
-Turning off Wi-Fi battery saving.
-Turning off auto brightness.
-Adding a few lines on the build.prop file before flashing the ROM.
And many more...
I know this is not caused by the ROM because:
-The stock kernel doesn't give me flickering on the stock ROM, but the DooMLoRd kernel does, and when I switch back to the stock one, it works just fine.
-All the things that fixed the problem for others on CM11 didn't work for me.
I don't understand...I didn't face this problem on my old Xperia Tipo.
Any ideas?
Thanks in advance
why 3 threads for the same problem????
thread closed