Develop Bugs

What kernel is everyone using on CM7 RC1?

I was wondering what everyones experience with kernels have been before flashing it. Any suggestions?
Sent from my PC36100 using XDA App

I've been using the one that comes with gginggerbread 6. It's surprisingly smooth considering my phone usually doesn't like bfs kernels

For CM7 RC1 I use the .7 savaged-zen cfs havs kernel
For CM7 RC1 with WiMax [gingerbread 6], have to use the provided .37 kernel

I personally have been using the 0.0.5-0.0.9 Savage.zen kernal BFS HAVS SBC kernal with either CM7 RC1 CM7 RC1 + WiMax

nosympathy said:
I personally have been using the 0.0.5-0.0.9 Savage.zen kernal BFS HAVS SBC kernal with either CM7 RC1 CM7 RC1 + WiMax
Click to expand...
Click to collapse
No issues? Every time I try to use the kernel, my handcent force closes on me. Dx

using the 0.0.9...phones been on for 2 days 1 hour and 49 minutes
using the sprint extended battery, still at 45%

teh roxxorz said:
No issues? Every time I try to use the kernel, my handcent force closes on me. Dx
Click to expand...
Click to collapse
not a single force close. Been using the WiMax GB since it came out and have been using the savage.zen kernal since. I dk, but my phone seems to like BFS over CFS aswell. It will work will CFS but I get better battery life with BFS.
went from 32% battery to 18% in 1 day and 8 hours with this setup. I also have SetCPU set to Salvage.Zen

nosympathy said:
not a single force close. Been using the WiMax GB since it came out and have been using the savage.zen kernal since. I dk, but my phone seems to like BFS over CFS aswell. It will work will CFS but I get better battery life with BFS.
went from 32% battery to 18% in 1 day and 8 hours with this setup. I also have SetCPU set to Salvage.Zen
Click to expand...
Click to collapse
Interesting, I'll probably do a complete wipe eventually and restore stuff.

teh roxxorz said:
Interesting, I'll probably do a complete wipe eventually and restore stuff.
Click to expand...
Click to collapse
yeah when I flash a new rom, i wipe cache, delvik, boot, system, data, .android_secure.
boot the room, reboot to recovery, wipe cache and delvik and anroid secure, then flash the kernal, then boot, then reboot to recovery and wipe cache and delvik, and reboot and have fun.

nosympathy said:
yeah when I flash a new rom, i wipe cache, delvik, boot, system, data, .android_secure.
boot the room, reboot to recovery, wipe cache and delvik and anroid secure, then flash the kernal, then boot, then reboot to recovery and wipe cache and delvik, and reboot and have fun.
Click to expand...
Click to collapse
Yea, I normally do too, so I'll have fun.

I have been using the kernal packaged with CM7 and its been doing great. So well in fact I have been reluctant to try another one.

0.0.9 working great hardware 004
Sent from my PC36100 using XDA App

The toast kernel works great for me, better than the packaged kernel since I had slow 3G with that one, but cell standby is showing up as high percentage on the battery usage and I'm not getting the WiMax control settings.

admang said:
The toast kernel works great for me, better than the packaged kernel since I had slow 3G with that one, but cell standby is showing up as high percentage on the battery usage and I'm not getting the WiMax control settings.
Click to expand...
Click to collapse
I find that a lil' awkward since you're running a sense kernel on an aosp rom...but more power to ya.

I have started using the latest savaged and I am getting amazing battery life.
Sent from my PC36100 using XDA App

Bootloops in CM7 after MIUI

I've been using cm7 pretty much since I got my g2, but recent problems with gps caused me to look for other options.. so within the latest clockwork recovery I wiped data and cache for cm7 and flashed the latest miui rom. When I decided to go back to cm7 I wiped everything like before and flashed the rc2 rom. Even after repeated flashing I can not get the bootloops to stop. Right now I'm running cm6.1.1 with no problems.. but I would really like to find a way to bet back to 7.
Sent from my HTC Vision using XDA App

[Q] Kernel issues.

So I just flashed Decks which has a Cyan kernel. For some reason my phone doesn't seem to like when I try and flash anything that doesn't come with the ROM I flash.
I've tried multiple AOSP ones that support undervolting, no dice; will not even boot.
I clear cache before every attempt, no dice.
Any suggestions?
-Sent from my EVO in full derp mode.-

I'm not a 100% on what you said but if your trying to under volt an aosp kernel you can try sz 2.2.1 or tiamat they are the only 2 I use because I use the sbc versions but like I said I'm not that clear on what your question was.
Sent from my PC36100 using XDA App

linsalata28 said:
I'm not a 100% on what you said but if your trying to under volt an aosp kernel you can try sz 2.2.1 or tiamat they are the only 2 I use because I use the sbc versions but like I said I'm not that clear on what your question was.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Wow, re-reading my post I see autocorrect didn't do me any favors.
I've tried both SZ and Tiamat and I can't get either of them to run on my phone. After clearing cache I flash either of them and if I remember right SZ never gets past the white HTC screen before rebooting and Tiamat (if I'm lucky) will start to load my ROM before just locking my phone up.

It's important to clear cache and dalvik cache before flashing a new kernel. I use SZ 2.2.1 with CMod ... works great with interactive x governor. I don't undervolt, simply use 245/998, and haven't had any issues at all. Might give it a try ... good luck.

Try wiping cache & dalvik again after flashing the kernel. You can also try different versions, perhaps the versions of Tiamat & SZ that you used just don't like your phone.
Also, if you have SetCPU set to "set on boot", uncheck that option before flashing a new kernel.
Sent from my Evo + MIUI using Tapatalk!

wmdunn said:
It's important to clear cache and dalvik cache before flashing a new kernel. I use SZ 2.2.1 with CMod ... works great with interactive x governor. I don't undervolt, simply use 245/998, and haven't had any issues at all. Might give it a try ... good luck.
Click to expand...
Click to collapse
I do clear both. I reboot the phone and it either never loads the ROM or starts to load the ROM and locks up.

plainjane said:
Try wiping cache & dalvik again after flashing the kernel. You can also try different versions, perhaps the versions of Tiamat & SZ that you used just don't like your phone.
Also, if you have SetCPU set to "set on boot", uncheck that option before flashing a new kernel.
Sent from my Evo + MIUI using Tapatalk!
Click to expand...
Click to collapse
Tried wiping after kernel install, no dice. And I don't have "set on boot" checked.
Grrr, I don't get why my phone doesn't like flashing kernels. Maybe I'll move to a different recovery and try...

Tried RA - no dice. Now rather than locking up the phone just reboots constantly. That was Tiamat, going to try SZ...

[Q] Broken 4g and Wifi, please help!

I've got an evo 4g, I've been rooted for about a year. i flashed cm7.1 and it was running for about 3 months and last week wifi and 4g just stopped working. i used rsa checker to check my keys and they're still there. i think the problem is my ip address. its unavailable on wifi and 4g. i dont really know where to look. can someone point me in the right direction?

Did you just flash a new kernel?
Try flashing Tiamat... see what happens.

i just flashed savaged zen, but that was after the problem. i reflashed clockwork again, as well as cm7 again. how do i update my ip address? i think thats the prroblem. by telling you i already flashed a kernel, do u think it will help? how?

biggda said:
i just flashed savaged zen, but that was after the problem. i reflashed clockwork again, as well as cm7 again. how do i update my ip address? i think thats the prroblem. by telling you i already flashed a kernel, do u think it will help? how?
Click to expand...
Click to collapse
Just flash Tiamat and see what happens. This is almost definitely kernel related. Make sure you wipe dalvik cache and cache (preferably with Amon RA or TWRP recoveries).

I love you man, I'm talking serious bromance! Can you explain why that worked? Did my old kernel go bad? Thank u so much!
Sent from my PC36100 using XDA App

it broke again, I flashed again. It didn't come back.
Sent from my PC36100 using XDA App

Try a different version of CM7. You can also try an entirely different rom for troubleshooting purposes. Generally 4G & wifi issues stem from the kernel. Are you flashing any mods or running anything that makes system changes, like V6 Supercharger? If you're using V6, undo the kernel tweaks.
Best bet is to flash a different version of CM7, even if you have to downgrade. Do a full wipe - data, cache, dalvik, system, boot, SD-ext, .android_secure - and flash only the rom and gapps. Try 4G & wifi before restoring anything. If they work, you can then restore anything you've backed up with TB, just try to avoid restoring system apps/data. If the problem comes back then it may be something in one of your apps or the data you've restored... though unlikely.
If this doesn't work, do a full wipe again and flash a fully stock rooted rom. Update your radios etc with the combo zip. If that fails, RUU.
There are plenty of options, but I don't think you'll have to go as far as running an RUU. Start from the top and work your way down.
Supersonic Evo 4G | MIUI | Tapatalk

I went to 7.1 rc then I reflashed 7.1 without gtalk . Works fine now. Thanks.
Sent from my PC36100 using XDA App

the only thing I could see that broke it was font installer app or google talk. Its fine now. Ill keep u updated. Thanks
Sent from my PC36100 using XDA App

EVO force closing all apps. Any suggestions?

Im running cm-nightlies 256 coupled with tiamat 3.3.7 no sbc and running the ram script. Not vipermods scripts. Apps keep freezing and forceclosing and some even cause my phone to reboot. Its a completely clean install for the rom. Everything was wiped multiple times. Then had a clean flash with the kernel. Any ideas what might be causing it?
Sent from my PC36100 using xda premium

Alright since you wiped it I would say its because the kernel and scripts. try getting rid of them bro and see if it helps if not flash a different version of cm because the nighties are not always stable

Fix permissions in recovery or ROM Manager.
Sent from the original Swagged Out EVO via Tapatalk 2

Boot to recovery Wipe cache and dalvik 3x each, fix permissions(uid mismatches) under advanced menu, wipe cache and dalvik again, reboot if that doesnt fix it flash the rc of cm7.2 as it's more stable than the nightlys and if u upgrade to 7.2 change your kernel to tiamat 4.1.0 I found it plays better with cm7.2 than 3.3.7 does
Sent from my SPH-D710 using xda premium

Yeah, what they said.

Thanks guys.
Sent from my PC36100 using xda premium

Undo any kernal tweaks from ethier v6 or kak
sent from my EVO EXPRESS 4g