• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root kernel flashing question

cloud3648

Newbie
i have a evo 4g with the cm7 it has the 2.6.37.4 kernel. when i try to flash an alternate kernel say for instance netarchy-toastmod, or CM6-Snap kernels.

my phone will just be stuck on htc evo 4g logo and stay forever. then i will restore a backup then it will be fixed.

why cant i flash any kernals. ive wiped the devik/cache partitions and still doesnt work.
 
i have a evo 4g with the cm7 it has the 2.6.37.4 kernel. when i try to flash an alternate kernel say for instance netarchy-toastmod, or CM6-Snap kernels.

my phone will just be stuck on htc evo 4g logo and stay forever. then i will restore a backup then it will be fixed.

why cant i flash any kernals. ive wiped the devik/cache partitions and still doesnt work.

Netarchy are Sense kernels for the most part and will not work with CM7 as it is AOSP. CM6 kernels may not either as they are for 2.2 based roms as far as I know. Tiamat and Savaged-Zen roms are 2 that work well with CM7. You can find them on XDA. I am running Tiamat 3.3.8-SBC with no issues so far.
 
+1 on tiamat. i'm using 3.3.7 sbc kernel. i did not know that there was a 3.3.8 version. is there a difference? my current kernel is awesome! i just did 35 hours on one charge! i may have to try 3.3.8 and see if i can get better than that.
 
+1 on tiamat. i'm using 3.3.7 sbc kernel. i did not know that there was a 3.3.8 version. is there a difference? my current kernel is awesome! i just did 35 hours on one charge! i may have to try 3.3.8 and see if i can get better than that.

The only reason I saw it was because it came up in Kernel Manager as a new version. I am not sure that there is much of a difference. Only started running it last night so only one full charge so far on it.
 
+1 on tiamat. i'm using 3.3.7 sbc kernel. i did not know that there was a 3.3.8 version. is there a difference? my current kernel is awesome! i just did 35 hours on one charge! i may have to try 3.3.8 and see if i can get better than that.

I read the changelog and while i cant remember exactly what changed i know it was worth me updating because i did lol.
 
just the stock cm7 kernel just drained the hell out of my battery on on demand. so i just flashed to tiamat also how can i see how do i see the options for havs such as undervolting?
 
just the stock cm7 kernel just drained the hell out of my battery on on demand. so i just flashed to tiamat also how can i see how do i see the options for havs such as undervolting?

Not sure what you are asking here. Tiamat kernel has a set level of havs. You can view the levels of voltage per frequency if you look in

/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs

You can also cat "the above" in terminal emulator to get the list

You can modify these voltages but most people dont. Be careful here. Also im not entirely sure if you can just edit that text directly (ALWAYS BACK UP BEFORE EDITING /SYSTEM FILES). Viper boy has set up flashable zips that can lower the voltages of your kernel. Basically his zip pushes a "flag" file to system/etc/init.d and tells it to subtract 25, 50, 75, or what have you from the voltages located in /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs

In most cases people dont mess with these but i suppose using this knowledge you could make your kernel undervolt more, or less technically by changing the "flag" file to +...

There is also a flashable zip floating around to remove sbc on the sz kernel...i havent looked at this zip at all so i dont know exactly what its doing...i'll look into it later.
 
Not sure what you are asking here. Tiamat kernel has a set level of havs. You can view the levels of voltage per frequency if you look in

/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs

You can also cat "the above" in terminal emulator to get the list

You can modify these voltages but most people dont. Be careful here. Also im not entirely sure if you can just edit that text directly (ALWAYS BACK UP BEFORE EDITING /SYSTEM FILES). Viper boy has set up flashable zips that can lower the voltages of your kernel. Basically his zip pushes a "flag" file to system/etc/init.d and tells it to subtract 25, 50, 75, or what have you from the voltages located in /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs

In most cases people dont mess with these but i suppose using this knowledge you could make your kernel undervolt more, or less technically by changing the "flag" file to +...

There is also a flashable zip floating around to remove sbc on the sz kernel...i havent looked at this zip at all so i dont know exactly what its doing...i'll look into it later.
would you have anymore info on were to get this zips at? thanks im interested in testing different voltages on havs
 
smartass govenor seems to still drain the battery. what is teh best govenor for normal use?

I would have suggested smart ass...what are the other options with tiamat?

may not be that you need a diff kernel, may be that you need to turn off 3g when your not using it or decrease sync frequency or any number of 100 other things...

Check your battery info in spare parts...anything too high? anything holding a wake lock? may narrow down an issue for you...
 
the google services are really high in the network usage tab


Of course, not so worried about network usage but probably indicates you have google apps synching frequently...

Its hard to pinpoint google services because it covers so much but if its not holding a wake lock for a ton of time its likely not the issue
 
Of course, not so worried about network usage but probably indicates you have google apps synching frequently...

Its hard to pinpoint google services because it covers so much but if its not holding a wake lock for a ton of time its likely not the issue

i turned off autosync what exacly is a wake lock
 
i turned off autosync what exacly is a wake lock


Some apps will hold wake locks in general its ok but a partial wake is an issue because that means even though you have the screen off the cpu and the phone are actually still running

Its not horrible as long as its not excessive
 
Just a couple of quick clarifications on some things:

1) Everyone (including me) always recommends that if you use smartass, don't use profiles, as that is what smartass will do automatically, and the two will fight each other. That's *sort of* true. What will happen if you use profiles, is you will change the max/min under certain conditions, and smartass will not set the frequency where it should under those conditions. Likely, you won't notice many issues unless you start using battery level type profiles. In any case, if you ever feel the need to use profiles with smartass, just make sure your profiles use a different governor. I don't know why you would want to do that (with a couple of exceptions), but it is possible. One quick note - if you use the Savaged Zen kernel with the Savaged Zen governor (which is based on smartass), it sometimes doesn't wake the phone up right away when you press the power button. You can get around this by creating a screen-off profile that makes the max/min very low (as usual), but uses a different governor such as conservative. This is really the only time you'd ever do this.

2) Back to the whole vdd_levels_havs thing, the flashable zip to lower the voltages is an init script, not a flag file :). An init script is a script that will run at boot. Text files in /sys will affect the behavior of devices. For example, this is where your min/max frequency, governor, etc. are stored. On each boot, they are set to default. The HAVS levels will be reset on each boot unless you tell it to be lower. That init script will modify the vdd_levels_havs at each boot to tell it to do that. A flag file is just an empty file that tells an app, script, etc. to behave in a certain way due to the presence of that file.
 
Just a couple of quick clarifications on some things:

1) Everyone (including me) always recommends that if you use smartass, don't use profiles, as that is what smartass will do automatically, and the two will fight each other. That's *sort of* true. What will happen if you use profiles, is you will change the max/min under certain conditions, and smartass will not set the frequency where it should under those conditions. Likely, you won't notice many issues unless you start using battery level type profiles. In any case, if you ever feel the need to use profiles with smartass, just make sure your profiles use a different governor. I don't know why you would want to do that (with a couple of exceptions), but it is possible. One quick note - if you use the Savaged Zen kernel with the Savaged Zen governor (which is based on smartass), it sometimes doesn't wake the phone up right away when you press the power button. You can get around this by creating a screen-off profile that makes the max/min very low (as usual), but uses a different governor such as conservative. This is really the only time you'd ever do this.

2) Back to the whole vdd_levels_havs thing, the flashable zip to lower the voltages is an init script, not a flag file :). An init script is a script that will run at boot. Text files in /sys will affect the behavior of devices. For example, this is where your min/max frequency, governor, etc. are stored. On each boot, they are set to default. The HAVS levels will be reset on each boot unless you tell it to be lower. That init script will modify the vdd_levels_havs at each boot to tell it to do that. A flag file is just an empty file that tells an app, script, etc. to behave in a certain way due to the presence of that file.


Ok thanks for clarifying that its an init script. I used flag in parenthesis because I knew that wasn't the name but I didn't know off hand and it didn't have an extension so flag got me through lol :)
 
Ok thanks for clarifying that its an init script. I used flag in parenthesis because I knew that wasn't the name but I didn't know off hand and it didn't have an extension so flag got me through lol :)

Haha, it's all good. Your description was correct.
 
I do my best akaza...the term was wrong and I knew it but I hope the explanations are good...sorry for improper terminology guys...I'm still learning too :) as long as you don't call bs on me then I'm ok lol
 
Back
Top Bottom