Root Netarchy Smartass Kernal with Setcpu?

[Droiddinho]

What else have you done to your phone? Just flashing a kernel/overclocking wouldn't cause you to lose your text messages. Also, force closes can be due to a lot of things. Did it not start until you overclocked? What are your hboot/radio/software versions? What kernel are you using, specifically (version, CFS/BFS, HAVS/noHAVS, SBC/noSBC)?

The forceclosing and erased text messages happened during the time I was flashing the new kernel/overclocking. The flashing process wasnt smooth, as I overclocked to 1190 and my phone kept rebooting itself until I managed to find enough time to uninstall setCPU in between reboots. I flashed about 3 different kernels in this time(the stock kernel that works with collin's battery tweak, and bfs#9). I also made the mistake of trying setCPU with collins battery tweak enabled, which caused my phone to get sluggish until I once again removed setCPU and disabled the battery tweak.
Now I'm using Froyo with Myns warm 2.2 RLS 5, Radio is 2.15.00.11.19, Kernel is 2.6.32.23 natas@64-bit-evil(the file was called netarchy-toastmod-4.2.1-cfs-bfq-havs-more-smartass-universal-signed)

 

[akazabam]

The forceclosing and erased text messages happened during the time I was flashing the new kernel/overclocking. The flashing process wasnt smooth, as I overclocked to 1190 and my phone kept rebooting itself until I managed to find enough time to uninstall setCPU in between reboots. I flashed about 3 different kernels in this time(the stock kernel that works with collin's battery tweak, and bfs#9). I also made the mistake of trying setCPU with collins battery tweak enabled, which caused my phone to get sluggish until I once again removed setCPU and disabled the battery tweak.
Now I'm using Froyo with Myns warm 2.2 RLS 5, Radio is 2.15.00.11.19, Kernel is 2.6.32.23 natas@64-bit-evil(the file was called netarchy-toastmod-4.2.1-cfs-bfq-havs-more-smartass-universal-signed)

1) Yes, it's very important that you uncheck the set at boot option while testing the max limit. Sorry, I should have mentioned that earlier.

2) Yeah, that's a common mistake trying to use the battery tweak and setcpu at the same time. Good job catching it and fixing it. It's always important to read about these things before flashing them. Learning through experience is great too, as long as you learn something .

3) How is that kernel working out for you? Are you still getting force closes/instability? If so, consider using the "less HAVS" version of that kernel, of update to the latest NA kernel (4.3.1), if you still want to use HAVS.

4) Did you ever get your text messages back? I've never heard of switching kernels doing that, but since unexpected things *can* happen, you should always make a nandroid backup before flashing anything - even kernels.

 

[Droiddinho]

1) Yes, it's very important that you uncheck the set at boot option while testing the max limit. Sorry, I should have mentioned that earlier.

2) Yeah, that's a common mistake trying to use the battery tweak and setcpu at the same time. Good job catching it and fixing it. It's always important to read about these things before flashing them. Learning through experience is great too, as long as you learn something .

3) How is that kernel working out for you? Are you still getting force closes/instability? If so, consider using the "less HAVS" version of that kernel, of update to the latest NA kernel (4.3.1), if you still want to use HAVS.

4) Did you ever get your text messages back? I've never heard of switching kernels doing that, but since unexpected things *can* happen, you should always make a nandroid backup before flashing anything - even kernels.

I had to remove setCPU.... and I still got force closes and random reboots so I removed netarchy too. For some reason I kept getting force closes, and performance wise the overclocking really wasnt a big deal to me. I'm back on the stock kernel and using collins tweak... getting good battery life and stable usage now.

 

[akazabam]

I had to remove setCPU.... and I still got force closes and random reboots so I removed netarchy too. For some reason I kept getting force closes, and performance wise the overclocking really wasnt a big deal to me. I'm back on the stock kernel and using collins tweak... getting good battery life and stable usage now.

Interesting. So what did you do to get the FCs to stop? Restore a backup? I can't help but wonder if you did something else to cause that. Did you flash anything else recently? Did you try flashing a different NA kernel?

 

[Droiddinho]

to get the FCs to stop I just flashed the Myns stock kernel and uninstalled setCPU.

In retrospect I think the problem may have been that I didnt disable colin's tweak properly. To disable it I went into terminal emulator and entered in the prompt that I wanted to disable the tweak, but I think the best way is to just totally wipe it off my system. Next time I experiment with setCPU I'll try this and hopefully it will be more stable.

 

[akazabam]

to get the FCs to stop I just flashed the Myns stock kernel and uninstalled setCPU.

In retrospect I think the problem may have been that I didnt disable colin's tweak properly. To disable it I went into terminal emulator and entered in the prompt that I wanted to disable the tweak, but I think the best way is to just totally wipe it off my system. Next time I experiment with setCPU I'll try this and hopefully it will be more stable.

Theoretically, that should be enough, but it's been known to cause all kinds of obnoxious problems like that. It could be anything from a bad kernel flash to a bad combination of kernel choice and other tweaks like that. But yeah, it's better if you can start with more of a clean slate.