I am running CM7 on my EVO and for some reason every now and then the phone decides to reboot on its own. Is it something within CM7? DId the fix it if others were experiencing the same problem? I haven't d/l the newest one as of yet. Thanks in advance.
You can get the random reboots if you didn't flash correctly, or over clocking too high. So I would suggest to:
-Download the latest version
-perform a full wipe [factory/data, cache, dalvik]
-flash latest gapps
And you should be good to go.
It's great
mjs1231 said:
Evo running cm7. My done started rebooting in the last two days. I. think its the new update to 1tap clleaner on the market. Lowered my CPU to 245-800. Still reboots . Wiped dalvik and cache part. Still rebooted. NOTE. Cm7 has been working fine since it was posted online. Its some app fubar
Click to expand...
Click to collapse
What kernel are you running? Some kernels are undervolted quite a bit, and some phone's don't tolerate undervolting well. Reboots can possibly result. I had flashed the 3.3.7 Tiamat kernel the other day, running salvage mod. I was getting major and constant reboots. I used ViperBoy's overvolt script, and I've had no reboots since. My phone simply doesn't like to be undervolted, and getting rid of the the undervolt fixed it. So possibly if your kernel is undervolted a lot, your phone may not agree. So consider flashing viperboy's over volt script. His thread is in the dev section.
Related
So i was using Fresh 3.3 up until last night and decided to try Myns. When i used fresh, i tried a few kernals (king 9, 11) as well as a netarchy one and everytime i tried to check battery stats or something, the phone would just reboot. I figured it was just something with fresh and just went back to the stock kernal and moved on.
So after moving to myn, i decided to try these kernals that everyone is talking about and i figured since myn himself even tested king 11 with his rom, it would be trouble free for me, but the same issues occured...my phone would just randomly restart at times, and i can reproduce the restart by checking battery stats in settings.
So i understand some kernals work differently for different phones, but i just want to make sure im not missing some important step when flashing a kernal.
What i did was wipe everything x3 and flashed new rom yada yada yada, then rebooted to load the rom first time, then turned off and booted back into recovery. I wiped cache partition/dalvik x3 and then flash the kernal. This correct right?
that is the correct way to flash a kernel. have you tried to see if you can duplicate the error witha stock kernel? (ie the one fresh coems with i think myn might too but not 100%) If you get the error with stock it is likely not the kernel itself causing the problem.
also try wiping battery stats and see if it fixes it
hello,
Everything is fine with a stock kernal, never get a random reboot and stuff like that. Its wierd...i tried using many different types of kernals and each and every one of them i can reproduce the random reboot by checking battery stats or even updating profile.
But i will try the battery wipe stats thing to see if it works. but just to be clear, do i wipe stats before or flashing the new kernal? and do i wipe when its fully charged or just whenever?
Thanks.
You should probably wipe battery stats after you flash the kernel and with a full charge. Which kernel scheduler are you using CFS or BFS? I noticed that BFS tends to cause random reboots on my EVO so I've stuck with CFS versions. Used KingKlick #11 CFS with Fresh 3.3.0.1 and everything runs smoothly for the most part, but there are a few reboots when I'm underclocked with setcpu during low battery profiles.
thanks for the info i will do that, and i tried both CFS and BFS versions of kingklick and all give the same result. I will try kings 11 CFS first with the battery stat wipe.
Thanks for the info, will post back if any issues occur.
I would like to know if anyone else has experienced similar issues using any of the MIUI roms?
If you have experienced this how did you remedy the situation?
So here is the story:
I was never keen on using MIUI roms as i am a fan of sense, but lately i have been growing tired of sense and have been looking for greener pastures.
My device is rooted(S-On, pvt-3, 0.93 hboot) and i have been running plenty of custom(sense based) roms with no trouble. Last night i flashed Pays MIUI rom and the phone was rebooting evey few minutes ... so i decided to call it a night and went to bed ... then this morning i went to the MIUI site and downloaded the latest 0.12.24(or something) and the phone was running smoothly the whole day without any hicups ... or reboots ... yes you guessed it ... now its rebooting again!
I dont think its the hardware on my device as i havnt experienced any problems with any other roms, and i perform a full wipe each time i flash.
Any advice would be greatly appretiated, thanx in advance!
Try flashing this kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=472705&d=1293232742
it could be that the HAVS kernel is causing your problems. This is a SVS kernel and should be more stable for some people.
Wipe dalvik cache after you flashed the kernel (same way as flashing rom). Disable verfication before flashing.
Lennyz1988 said:
Try flashing this kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=472705&d=1293232742
it could be that the HAVS kernel is causing your problems. This is a SVS kernel and should be more stable for some people.
Wipe dalvik cache after you flashed the kernel (same way as flashing rom). Disable verfication before flashing.
Click to expand...
Click to collapse
Thank you for the reply ... i also thought it might have something to do with the kernal, will flash after the phone has charged ... will post results!
Hi, I'm fairly new to this sort of thing, that is, rooting my phone and messing with ROMs and Kernels, but I seem to be having an issue.
I have MIUI 1.11.4 installed, with the Tiamat 1.1.5 kernel. My problem is that I have no data. My 1x/3G is gone, and I'm not sure what I did wrong.
If someone could talk me through the steps needed to have the MIUI ROM and Tiamat Kernel and Data working simultaneously, I would be most grateful.
Here is what I have been doing:
1. Boot to recovery.
2. Factory reset/wipe.
3. Install MIUI from .zip.
4. Reboot.
5. Wait 10 minutes or so.
6. Boot to recovery.
7. Clear Cache.
8. Install Tiamat 1.1.5 from .zip.
9. Reboot.
10. Scratch my head, wondering where my data went.
Well that's been a problem that has been around since about the last three updates. If your looking for a good alternative here's a couple
rootzwiki.com/topic/7717-kernel-aeroevan-vivow-kernels-for-aosp/[/url]
rootzwiki.com/topic/7911-kernelvivow-kernel-core-betas/[/url]
I personally use areoevan because the last time I tried the core beta one, setcpu didn't play well with it. But back to your question I don't think anyone has found a fix for the tiamat issue.
Thanks, I'm using the aeroevan now. It seems to be working well enough.
I've been using aeroevan's 0.4 kernel with MIUI 10.21 for some time now and I had no loss of data and battery life is awesome
So far, MIUI 1.11.4 with Aeroevan 0.6 is working fantastically. Any errors I have encountered were self-inflicted.
Sent from my MIUI-ed Incredible 2, using xda premium.
I too encountered this problem with MIUI and Tiamat Kernel. All of a sudden i couldn't get a data connection at all....everything had to be wifi.
How did i solve the problem? since I have Verizon's unlimited data plan, all i did was go to the monitor app and increase the allowed monthly data to 200 GB.
Have had no issues since.
Note: Don't know if this is the EXACT same issue you were having, but that's how i fixed it for me.
Hey guys,
I'm running Calkulins latest and greatest buily along with the rogue ET 1.1.3+ kernel and have had nothing but problems since doing so.
To name a few, the LOS bug has hit my phone. This was never a problem previously when I was stock. I'll notice it's searching for service and doesn't get resolved until a reboot.
Second, I'd say 25% of the time I reboot the phone it gets stuck on the custom boot screen that Calkulins has.
Thirddd, I've noticed huge delays in emails and notifications in general.
I've tried flashing again, any ideas?
What sometimes helps me, instead of rebooting altogether. Enable 4G, let it connect, then turn off 4G.
It happened to me when I get out of a tunnel on the subway. Or is that not really the LoS bug that everyone's been reporting?
I had the same problems. Random reboots, LOS, and freezing. I did a full wipe(data, cache, dalvik). Then I re-flashed the rom, I let the phone do a full reboot. Then I went back in to recovery and wiped just cache and dalvik and flashed Rogue Stock v1.1 kernel and let the phone reboot all the way. Then I updated profile and prl in system updates, and then rebooted phone again. I haven't had any problems with the stock kernel from rogue. I think there is a problem with the 1.1.3 kernel. I have had it on the starburst rom and vipor rom and it does the same thing. I used rogue's stock kernel on starburst too and never had a problem. Also I flashed tiffany's nothin but honey theme for calk's 1.5a rom and looks amazing. I did the theme flash last after everything else. I hope this helps.
Hello. I'm running Cyanogenmod 10.1.0-RC5 on my maguro device, and franco-kernel r378. I've been experiencing random reboots, sometimes as often as 2-3 per hour. The phone doesn't even feel warm when it happens. Sometimes I'm using it, but sometimes it's just sitting there doing nothing and it reboots anyway. I've uploaded the last lines of my last_kmsg here, to see if any of you can help me figure out how to solve this annoying issue.
Thank you very much in advance!
Ivan.
I have the same setup no reboots. Do a clean install. Fix per,missions after installing Franco kernel. I have on demand and bfq. Stock speed' and don't use trickster mod
I did a clean install. I'm running the on-demand governor too, and 'deadline' instead of 'bfq' scheduler. I fixed permissions as well, I didn't change the CPU speeds, and I have no idea what the trickster mod is
I might add that i was having this same random reboot problem even with the CM stock kernel.
Any info from the last_kmsg file uploaded?
Thank you!
Best regards,
Ivan.
Small update: I did a fresh ROM install, again. I'm running the stock CM kernel, with the default parameters for CPU speed, scheduler and governor. The problem remains.
Please see an updated version of last_kmsg here.
Try to reflash stock. If the problem remains I am afraid it can even go worse. I mean reboots can become more frequent.
Did u changed your radio?
Had the same problem when I was on AOKP+Franco combo. Actually it was the radio for me which caused the problem.
Reflash everything, including radio, while returning to stock, it worked for me.
good luck :good: