Root Best Kernel for teppics rooted stock froyo rom

[dinaro]

Just wondering which kernel - in terms of performance and battery life would be the best to use with teppics rooted stock froyo rom.

I'm currently using this kernel with the sd card read fix and gpu+ fix but I'm wondering if theres something thats better in terms of performance and battery life.

Desire Kernel for Teppic74's ROM - xda-developers

I've heard many good things about richards v5 kernel but I don't want to OC or do anything crazy. I just need the sd card read fix... maybe the gpu+ fix and no OCing as I do want to keep my battery life as is.

 

[SUroot]

You only overclock with a higher Mhz kernel if you set the max Mhz higher in Set CPU, otherwise it stays as standard.

As a Defrost fan, I would recommend Richards kernel. His kernels are undervolted so even if you did overclock, it would still use less battery than stock at 998Mhz.

With Set CPU though not only can you overclock, but you can set min and max to loweset with a screen off profile so if the screen is off, the MHZ is always 245

 

[turbohobbit]

Maybe I'm using flawed logic here, but isn't there as much risk - if not more - in flashing a kernel as flashing a radio?

 

[SUroot]

It's not risky if you're careful (don't remove power source). If you do, you can just reflash the kernel.

Radio is different as it is in a secure nvram location where if it corrupts, you may not be able to reflash it.

As long as you have enough battery power, the back cover firmly on and don't drop the phone, you shouldn't have anything to worry about

Scaredy cat

 

[turbohobbit]

LOL @ Scaredy cat

I'll have a think about all of this: more to play with!

 

[SUroot]

Yeah. Flashing anything is 99.9% recoverable. It's just radio thats not. You just need to be careful. If you're careful then its fine. It's only of something stupid happens.

 

[dinaro]

thanks dan few more noobie questions on kernels.

1.) I can flash any kernel I want with my existing rom or do I need certain roms to install richards kernel?
2.) Will it mess up my existing partition?
3.) If something goes wrong or I don't like it... I can always reflash with my previous kernel without issues right?
4.) He has quite a few versions in his thread which one do you think I should flash based on my needs?

 

[SUroot]

I don't use a sense Rom, so can't really advise on what's best to use or if any are compatible with stock roms. With a custom kernel though, is recommend going for a custom Rom anyway to get the best out of it.

You can replace with any compatible kernel, bit since your existing kernel is not flashable, only a nandroid restore would get an old kernel back, so always backup before flashing anything.

No it won't mess up any partitions

 

[dinaro]

I'm not sure which one I should flash out of these, and to be honest I really don't understand the difference between the mV's

Froyo Kernel V5e_HAVS@925mV min

Froyo Kernel V5e_HAVS@875mV min

Froyo Kernel V5e 1190Mhz max

Froyo Kernel V5e 1113Mhz max

 

[SUroot]

mV is millivolts. It's the minimum voltage the CPU will use. I find when the phone is idle, 875 is too low. My phone reboots randomly. Every desire is different though. Many are fine with that mV.. I use a 925 myself.

At the other end of the scale, I find 1190mhZ too fast a clock speed and I also get random reboots so I have to clock it to 1152 and its fine.

1190 IS quite high so I assume that is an SVS kernel. Also given the file name I assume the 1113 is also SvS.

The lower voltage two (these will all be undervolted but the top two are more extremely undervolted) are HAVS.


Stock kernels are SVS. Static voltage scaling. There is a table. On one. Side is clock speed. On the other is voltage. X mhZ = Y mV. Static values

Havs is experimental. Hybrid adaptive voltage scaling. Like svs, there us a table. It is not static. It also takes CPU temp into account and can ultimately give a lower mV than svs.

I use Havs usually. Svs tends to be a bit quicker but Havs definitely better for battery for me.


All desires act differently so it is trial and error what is best for you.




Hope this helps

 

[dinaro]

thanks again, great explanation, I understand it a bit better now. to your point it'll be different for all users but I think i'm going to test these 2

Froyo Kernel V5e_HAVS@925mV min

Froyo Kernel V5e 1113Mhz max

 

[SUroot]

Cool.... nandroid backup first though....

 

[dinaro]

definitely,

 

[dinaro]

damn, got stuck in bootloop, wonder why it works for some ppl running this rom and why it doesn't for others

 

[Hadron]

damn, got stuck in bootloop, wonder why it works for some ppl running this rom and why it doesn't for others

Have you added any other mods?

I use this ROM, added teppic's powersaving mods, then moved to the-fallen's kernel (the thread you linked), and then to Richard's V5e (1113 SVS), all with no problems. But I did manage to bootloop it when I tried altering the screenstate scaling script that had come with teppic's powersaving modpack (not replaced or overwritten by the subsequent updates). Now I must stress that it was my fiddling, rather than teppic's script, which was the problem, but it did show that an incompatible init.d script can cause this, which is why I ask whether you've added other mods.

 

[SUroot]

If like Hadron says, you have flashed mods, you could reflash the rom and immediately flash the kernel and see?

 

[dinaro]

I have flashed the mods that he provided in the thread indicated in my signature then flashed the fallens kernel. Actually in the same order that you did but I didn't mess with anything else. Would this cause the issue? Also not sure what implications there are if any - if I had to reflash the rom then do the kernel, would I have to do a factory wipe?

 

[SUroot]

Also not sure what implications there are if any - if I had to reflash the rom then do the kernel, would I have to do a factory wipe?

No, wipe is data.

Put it this way. Anything to do with the ROM (Mods, Themes, Add-ons, Kernels) are on /system.

User apps (that you install) their cache, your settings etc are all on /data

Whenever you flash a rom, /system is completely over written. Sometimes if its a different rom, your /data is incompatible.

If you are flashing the same rom, /data wont be incompatible so no wipe needed. As the rom over writes /system all your add ons etc are over written too. So its a clean slate from a rom perspective, but not from a data perspective.

 

[dinaro]

Sorry for so many questions... still learning quite a bit So should I just re-flash the rom then do the kernel right away? The only thing I'm worried about is if something messes up my A2SD+ mod, the other mods I don't care as much cuz I can reflash again.

I guess the main thing I'm getting at is... I don't want to mess up my partition or my AS2D+ mod since my apps are there.

Since my AS2D+ is a mod that would be in my /system that means my apps are in /data so would that mean my partition and apps are still there if my A2SD+ mod is wiped?

 

[SUroot]

Partition remains. Reflash all 3 then

 

[dinaro]

OK! thanks again for your help DF. I'll try this now...

 

[Hadron]

Unfortunately I'm not using A2SD+, so can't speak for compatibility there. I can't see how reflashing the ROM could hurt your partition, and I believe that a nandroid will anyway back up the data in the ext3 partition as well (when I do one it always reports that it can't find the partition to back up).

But if it was me I'd be inclined to try flashing ROM and A2SD+, then kernel - if that works, then you're good to go. If that won't work then I guess that kernel isn't for you

 

[Hadron]

Ah, and Dan replied while I was busy typing

 

[dinaro]

thanks hadron, I just flashed exactly in that order and i booted up fine! running his kernel now

time for some benchmarking!

 

[SUroot]

Ah, and Dan replied while I was busy typing

What can I say? I'm a minimalist