Related
Hello am a real android noob. i have read a few threads on here but i still need a little help.
am on stock htc rom but want to improve battery life without moving away from stock too much if at all.
my question is would i be better using set cpu on its own or with a custom rom?
thanks
you can use set cpu but you would need to root but the only thing set cpu can do is change the cpu speed lowering the cpu speed would save battery but could cause lag.
Custom ROM are removed of bloatware and have better battery life i have noticed this myself.
Aamir.Badat said:
you can use set cpu but you would need to root but the only thing set cpu can do is change the cpu speed lowering the cpu speed would save battery but could cause lag.
Custom ROM are removed of bloatware and have better battery life i have noticed this myself.
Click to expand...
Click to collapse
Using an undervolted kernel at stock speed should improve battery life but again requires root
But how do you install a custom rom, or for example buzz 1.06 kernel?
Sent from my Desire HD using XDA App
You have to root then istall Clockwork Mod Recovery
Download the ROM must be .zip file place it at the root of you sd
Then boot into recovery choose the option which says install zip from SD and then find the zip and install
same goes for the kernel e.g instead of ROM zip you place the Kernel zip in root of sd
ghostofcain said:
Using an undervolted kernel at stock speed should improve battery life but again requires root
Click to expand...
Click to collapse
Yes i know but you need to root and S-OFF to flash anything i think.
Aamir.Badat said:
Yes i know but you need to root and S-OFF to flash anything i think.
Click to expand...
Click to collapse
Yes you do, but you require root to use setcpu also
Ok guys thanks, I think I use set CPU and see how it goes.
And wait for a gingerbread Rom to come out.
Sent from my Desire HD using XDA App
I wanted to install freedom kernal on synergy rls1 but don't know how to go about it or which kernal would work best, any help is appreciated. Last time I tried to install, I ended up completely wiping everything from my phone accidently
Freedom kernel worked very will for me on synergy when I was using it. Just search for it here on xda, download (i downloaded the aggressive universal which is undervolted -175mv.) The synergy nightly kernel did not work for me, caused wifi to error when turning on. Anyway download, reboot into recovery> wipe cache and dalvik(but not data)>flash zip from sd> download folder (where all your downloads go) and just flash it. Reboot and enjoy. Surprisingly, synergy gets pretty good battery life with this undervolted kernel since not only is this a sense rom obviously, it is a sense 2.1+ 3.0. Good luck
Sent from my PC36100 using xda premium
Just don't wipe data/ factory reset
Sent from my PC36100 using xda premium
Download either the universal freedom, more freedom, or aggressive freedom, put on root of SD card, boot into recovery, wipe cache & dalvik cache, flash kernel.
Personally, i like aggressive freedom
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
Evocm7 said:
Freedom kernel worked very will for me on synergy when I was using it. Just search for it here on xda, download (i downloaded the aggressive universal which is undervolted -175mv.) The synergy nightly kernel did not work for me, caused wifi to error when turning on. Anyway download, reboot into recovery> wipe cache and dalvik(but not data)>flash zip from sd> download folder (where all your downloads go) and just flash it. Reboot and enjoy. Surprisingly, synergy gets pretty good battery life with this undervolted kernel since not only is this a sense rom obviously, it is a sense 2.1+ 3.0. Good luck
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
didnt read your post & basically repeated your post. sorry. lol
Can and should I use setcpu in conjunction with the kernal. If so what are the recommended settings
Sent from my PC36100 using XDA App
ghettovirtuoso said:
Can and should I use setcpu in conjunction with the kernal. If so what are the recommended settings
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes and depends on what u want out of ur phone. I would Google setcpu and read up on it though. If you've never over or under clocked its best to educate before.
http://www.setcpu.com/
Sent from my PC36100 using XDA App
Download the kernel (I use Aggressive, depends on how low voltage the phone can handle). Put on the root of your SD card. Boot into recovery. Wiipe cache and dalvik twice. Navigate to "Mounts" and mount data. Navigate to "Flash Zips" and find the kernel. Select with power button. Reboot.
Download SetCPU or No Frills CPU (If you haven't purchased SetCPU then dowload No Frills, it is free and has a simple interface).
Do not use profiles. I suggest Interactive X. My min-max CPU is 245 - 820. Interactive X drops the CPU down to 245 mHZ when screen is off and manages the CPU well when the screen is on
tropicalbrit said:
Download the kernel (I use Aggressive, depends on how low voltage the phone can handle). Put on the root of your SD card. Boot into recovery. Wiipe cache and dalvik twice. Navigate to "Mounts" and mount data. Navigate to "Flash Zips" and find the kernel. Select with power button. Reboot.
Download SetCPU or No Frills CPU (If you haven't purchased SetCPU then dowload No Frills, it is free and has a simple interface).
Do not use profiles. I suggest Interactive X. My min-max CPU is 245 - 820. Interactive X drops the CPU down to 245 mHZ when screen is off and manages the CPU well when the screen is on
Click to expand...
Click to collapse
You don't have to mount data on Synergy...thats only for the sense 3.5 roms
I used no frills cpu control. Its free in the market and worked well for me. Too bad it wasnt there when I bought setcpu. At least it was only $1. Aggressive freedom is the way to go
Sent from my PC36100 using xda premium
steve97ta said:
You don't have to mount data on Synergy...thats only for the sense 3.5 roms
Click to expand...
Click to collapse
Heard that some people had to do it for Xplod, at least in its earlier stages. I do it every time now I flash a kernel, just to prevent any possible issues
Sent from my PC36100 using xda premium
Can and should I use setcpu in conjunction with the kernal. If so what are the recommended settings
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm sorry if this offends you (ghettovirtuoso), but seriously? If you listened to the video at all when you registered, you would know how to look for these answers on your own. Especially "Should I use an overclock app", "if i'm trying to overclock"? What? First, if you didn't already know this, you shouldn't be doing this! You should do A LOT MORE research before you even ask a single question! Second, be careful not to brick your phone! That's the rough it sounds like your going! It is really unfortunate how many people just want things handed to them without putting anything in themselves! DO YOUR OWN RESEARCH FIRST, A LOT OF RESEARCH! YOU CAN FIND THE ANSWER TO 99.9999% of your questions here already! also if you don't find your answer, use different search terms, or learn correct definitions for word you are using.
Finally lets get to some real development!
I'm running AOKP and for awhile, things were working great. Then I think I must have gotten a little over-zealous with undervolting because I would boot all the way up and as soon as widgets started loading, the phone would freeze and crash.
I tried a handful of things to fix this and ended up just reflashing the AOKP ROM over the top of everything. Cool. Got everything back to normal, EXCEPT:
I now have the stock AOKP kernel (whatever that is) and no longer have the option to adjust voltage settings. When trying to flash a new kernel (I've tried franco, leankernel, and matr1x), I get the boot loop again.
I've tried uninstalling SetCPU, using the SetCPU safe mode toggle, as well as flashing the leankernel tweaks, but still no dice.
Any ideas on how to flash a new kernel? I don't mind trying different things and have a good NANDroid backup to revert back to if necessary.
had the same problem and did what you did plus additional wipe cache and installed kernel before UV was possible which is 12(still have a backup if you want ) after that I've applied 13.1(latest at that time) and everything was fine
Sent from my Galaxy Nexus using xda premium
Read up on fastboot. It will allow you to either flash a kernel+ramdisk (boot.img) or only the kernel (zImage). It also allows you to fastboot both, as in you dont need to flash the kernel to test it.
If that doesnt work, revert back to stock then reflash AOPK, then your custom kernel of choice.
MattSkeet said:
had the same problem and did what you did plus additional wipe cache and installed kernel before UV was possible which is 12(still have a backup if you want ) after that I've applied 13.1(latest at that time) and everything was fine
Click to expand...
Click to collapse
Just to make sure I'm understanding this (I've only had an Android phone for a few days now), you wiped your cache, flashed an older version of a kernel, then flashed the latest version and it worked?
Which kernel was it? And yes, I would definitely be interested in the backup if you have it.
syndac said:
Just to make sure I'm understanding this (I've only had an Android phone for a few days now), you wiped your cache, flashed an older version of a kernel, then flashed the latest version and it worked?
Which kernel was it? And yes, I would definitely be interested in the backup if you have it.
Click to expand...
Click to collapse
It appears he's talking about the franco kernel. You can find old versions here: http://world-of-nexus.com/download-section/category/4-franco-kernel
You're looking for franco.kernel-nightly12-120112.zip. So, wipe cache and dalvik then flash nightly12, then wipe cache and dalvik again and flash whatever kernel you want.
jdk82 said:
It appears he's talking about the franco kernel. You can find old versions here: http://world-of-nexus.com/download-section/category/4-franco-kernel
You're looking for franco.kernel-nightly12-120112.zip. So, wipe cache and dalvik then flash nightly12, then wipe cache and dalvik again and flash whatever kernel you want.
Click to expand...
Click to collapse
It worked just fine with the old Franco kernel, but as soon as I flashed one with UV, it went back to the same problem.
I'm assuming you have undervolting running at boot right? If so, disable that and set the voltage back to stock
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Read up on fastboot. It will allow you to either flash a kernel+ramdisk (boot.img) or only the kernel (zImage). It also allows you to fastboot both, as in you dont need to flash the kernel to test it.
If that doesnt work, revert back to stock then reflash AOPK, then your custom kernel of choice.
Click to expand...
Click to collapse
I'm probably doing it wrong, but I used:
PHP:
fastboot flash:raw boot kernel.zip boot.img
and it gave me the error: "writing 'boot' ... FAILED <remote:Write Fail>
Any ideas?
nbeebe24 said:
I'm assuming you have undervolting running at boot right?m
Click to expand...
Click to collapse
Unfortunately, yes. I can't boot into SetCPU to disable the "Set at Boot" option. I can only boot into the OS at all if I use an old kernel that doesn't have UV enabled and also no options for it anywhere.
I used both the SetCPU safemode zip as well as placing the SetCPU_safemode file in the appropriate places and still no dice. I think this may be because I used the ROM settings to play with UV and not SetCPU.
syndac said:
I'm probably doing it wrong, but I used:
PHP:
fastboot flash:raw boot kernel.zip boot.img
and it gave me the error: "writing 'boot' ... FAILED <remote:Write Fail>
Any ideas?
Click to expand...
Click to collapse
Lol. Thats what you get for not listening to my advice: read up on fastboot.
But my guess is that you should adb shell when in recovery, browse to /system/etc/init.d/ and delete relevant script (which setcpu might have placed there), which loads uv values at boot.
syndac said:
Unfortunately, yes. I can't boot into SetCPU to disable the "Set at Boot" option. I can only boot into the OS at all if I use an old kernel that doesn't have UV enabled and also no options for it anywhere.
I used both the SetCPU safemode zip as well as placing the SetCPU_safemode file in the appropriate places and still no dice. I think this may be because I used the ROM settings to play with UV and not SetCPU.
Click to expand...
Click to collapse
Because now setcpu applies your recorded settings on top of the rom uv settings. Why use two ways of acomplishing the same thing at the same time i'll never know.
syndac said:
Unfortunately, yes. I can't boot into SetCPU to disable the "Set at Boot" option. I can only boot into the OS at all if I use an old kernel that doesn't have UV enabled and also no options for it anywhere.
I used both the SetCPU safemode zip as well as placing the SetCPU_safemode file in the appropriate places and still no dice. I think this may be because I used the ROM settings to play with UV and not SetCPU.
Click to expand...
Click to collapse
Try wiping the data from the app(s) you're using to under volt. Go to Settings, Apps, All and navigate to SetCpu, press it and choose Clear Data. Do the same for the other app. After that's done, install the kernel with UV and see if that works
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Lol. Thats what you get for not listening to my advice: read up on fastboot.
But my guess is that you should adb shell when in recovery, browse to /system/etc/init.d/ and delete relevant script (which setcpu might have placed there), which loads uv values at boot.
Click to expand...
Click to collapse
I looked for information on fastboot, though 5-6 google pages, and couldn't really find how to do it. Then I searched for help with that error and still nothing.
Forgive me for being a bit of a noob, but I did try to browse that /init.d/ directory. I could get as far as /system/etc/ but when I tried init.d, it said that it couldn't cd into that directory. I'm not very familiar with the shell commands, but I used ls inside /etc/ and only say fstab and mstab. Am I doing something wrong?
nbeebe24 said:
Try wiping the data from the app(s) you're using to under volt. Go to Settings, Apps, All and navigate to SetCpu, press it and choose Clear Data. Do the same for the other app. After that's done, install the kernel with UV and see if that works
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Unfortunately, that was one of the first things that I tried and it didn't work either.
nbeebe24 said:
Try wiping the data from the app(s) you're using to under volt. Go to Settings, Apps, All and navigate to SetCpu, press it and choose Clear Data. Do the same for the other app. After that's done, install the kernel with UV and see if that works
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Maybe try clearing the data for the "ROM Control" app, as well as setCPU, since that's what you used to uv (if I'm reading your posts correctly...)? I've never done that so I don't know if it will mess anything up or not... Other than that, I would try a full stock recovery as it seems some setting somewhere isn't getting cleared.
jdk82 said:
Other than that, I would try a full stock recovery as it seems some setting somewhere isn't getting cleared.
Click to expand...
Click to collapse
I should mention that as I'm trying solutions that don't work, I can do an Advanced Restore from CWM and only restore the /boot partition and everything works fine. The problem seems to be isolated there.
Is it possible to do this and still have all of my apps and settings be in place?
I have a working NANDroid backup, but not with UV options. I have a good Titanium Backup as well, if that means anything.
syndac said:
Forgive me for being a bit of a noob, but I did try to browse that /init.d/ directory. I could get as far as /system/etc/ but when I tried init.d, it said that it couldn't cd into that directory. I'm not very familiar with the shell commands, but I used ls inside /etc/ and only say fstab and mstab. Am I doing something wrong?
Click to expand...
Click to collapse
Is the kernel rooted? That is not normal AFAIK, you should see much more in the /etc dir. Also, what kernel/rom are you trying when you get the boot loop? I know you mentioned AOKP and franco, just double checking.
---------- Post added at 02:57 PM ---------- Previous post was at 02:39 PM ----------
syndac said:
I should mention that as I'm trying solutions that don't work, I can do an Advanced Restore from CWM and only restore the /boot partition and everything works fine. The problem seems to be isolated there.
Click to expand...
Click to collapse
After you do that and then (re)flash a kernel with uv support you go into boot loop again, right?
syndac said:
Is it possible to do this and still have all of my apps and settings be in place?
I have a working NANDroid backup, but not with UV options. I have a good Titanium Backup as well, if that means anything.
Click to expand...
Click to collapse
AFAIK with Titanium Backup, yes.
jdk82 said:
Is the kernel rooted? That is not normal AFAIK, you should see much more in the /etc dir. Also, what kernel/rom are you trying when you get the boot loop? I know you mentioned AOKP and franco, just double checking.[
Click to expand...
Click to collapse
Correct. AOKP M3
After you do that and then (re)flash a kernel with uv support you go into boot loop again, right?
Click to expand...
Click to collapse
Also correct. However, I should clarify that if I DON't reflash the kernel, and ONLY do the /boot restore (which restores the stock AOKP kernel), my phone works great.
syndac said:
Also correct. However, I should clarify that if I DON't reflash the kernel, and ONLY do the /boot restore (which restores the stock AOKP kernel), my phone works great.
Click to expand...
Click to collapse
Just to clarify, which program did you use to uv, setcpu or the ROM Control menu?
If you've wiped data from all the programs you've used to under volt your only other option is most likely to start all over and perform a data, cache and dalvik cache wipe and reinstall. In the future, if you are experimenting with UV NEVER select set on boot unless you're sure the voltages are 100 percent stable. You say you have a good nandroid so restore that and reinstall the kernel (unless you had the bad UV values set).
Sent from my Galaxy Nexus using xda premium
nbeebe24 said:
If you've wiped data from all the programs you've used to under volt your only other option is most likely to start all over and perform a data, cache and dalvik cache wipe and reinstall. In the future, if you are experimenting with UV NEVER select set on boot unless you're sure the voltages are 100 percent stable. You say you have a good nandroid so restore that and reinstall the kernel (unless you had the bad UV values set).
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If I've read what the OP said correctly, he has the bad UV values set in the backup somewhere. If he does a restore and then flashes a UV capable kernel he gets stuck at boot (right OP?).
jdk82 said:
If I've read what the OP said correctly, he has the bad UV values set in the backup somewhere. If he does a restore and then flashes a UV capable kernel he gets stuck at boot (right OP?).
Click to expand...
Click to collapse
Correct.
jdk82 said:
Just to clarify, which program did you use to uv, setcpu or the ROM Control menu?
Click to expand...
Click to collapse
I think I used the ROM control menu, but it might have been SetCPU. I know that I looked at both menus at different times.
----
What I'm thinking of doing is making a NANDroid backup now, going completely back to factory, but Advanced Restoring all of my NANDroid partitions EXCEPT for /boot, since that seems to be the one that is causing me problems. Could this work? I guess if it doesn't, I still have that NANDroid backup...
i'm planning on installing GLaDOS kernel today, and i'm currently running codename android.
if anything goes wrong, or i want to switch to another, how do i go back to the stock kernel.
Also, does a CWMR backup backup the custom kernel as well?
yes, the CWMR backups everything, including the kernel, so that would be your best bet
oh okay. so i could do a backup before i flash the kernel, and then if anything goes wrong, just restore that backup. correct?
neok44 said:
oh okay. so i could do a backup before i flash the kernel, and then if anything goes wrong, just restore that backup. correct?
Click to expand...
Click to collapse
Correct or to go even farther you can just restore that kernel only. In that advanced section on the restore menu, restore boot.img
jerrycycle said:
Correct or to go even farther you can just restore that kernel only. In that advanced section on the restore menu, restore boot.img
Click to expand...
Click to collapse
very awesome. thanks!
Great posts guys!
Question, is it best to reset the kernel every time change you change it? I've had some issues with kernels and this may be the problem.
I feel like in theory there's bits and pieces of things in there that I need to clean. Haha. What's the best way to do that?
Thanks in advance.
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Great posts guys!
Question, is it best to reset the kernel every time change you change it? I've had some issues with kernels and this may be the problem.
I feel like in theory there's bits and pieces of things in there that I need to clean. Haha. What's the best way to do that?
Thanks in advance.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I would check /system/etc/init.d; If there are any scripts from previous kernel there, delete them through adb or prefered method.
Also, in that folder, you may find other scripts, for example voltage settings @boot from 3rd party apps like setcpu, you should also remove those (if you use them at all)
You're asking about when changing custom kernels, right? When I switch kernels, I don't reflash stock kernel first. I just flash one custom kernel on top overwriting the installed one.
Oh ok thanks man.
I've only ever set min and max cpu stuff. Never any voltage settings. So I van probably go over with no worries yeah?
So you know what the build number is for stock kernel on 4.0.3?
Thanks again man.
Sent from my Galaxy Nexus using XDA App
This is stock kernel img you can flash it using CWMR
FOR 4.0.3
http://goo-inside.me/kernels/faux123/ICS-4.0.3-Reset-Kernel (1).zip
isn350 said:
This is stock kernel img you can flash it using CWMR
FOR 4.0.3
http://goo-inside.me/kernels/faux123/ICS-4.0.3-Reset-Kernel (1).zip
Click to expand...
Click to collapse
Thanks heaps dude.
Ive used this already and it "seemed" to do the job. But I just dont know if its pure.
Do you guys know the exact build numbers for it? I wish there was a legit google download thats "from the horses mouth" as it were...haha.
Thanks again.
Helmet321 said:
Oh ok thanks man.
I've only ever set min and max cpu stuff. Never any voltage settings. So I van probably go over with no worries yeah?
So you know what the build number is for stock kernel on 4.0.3?
Thanks again man.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
sorry, setting min/max cpu freq at boot time also places a script in /system/etc/init.d/, so I'd look out for those as well, forgot to specify those, as they may also cause conflicts with your current rom/next kernel. as always, you can open those scripts in a text editor and see what they're doing or will do on boot.
not sure on the release version/numbers though..my guess is that the easiest way is to repo sync 4.0.3 tag from aosp, that will have stock kernel version planned for that release.
Can someone post a CWM flashable file of the 4.0.2 kernel please.
Hello, I was wondering if someone could help me undervolt my Samsung Galaxy S3 4G LTE running on Cyanogenmod 10.1.
You need to install a kernel that allows for undervolting, such as KT747.
CamFlawless said:
You need to install a kernel that allows for undervolting, such as KT747.
Click to expand...
Click to collapse
Do you know if Cyanogenmod will allow you to undervolt in the future? Is there some way I can undervolt WITHOUT uninstalling Cyanogenmod?
I have no idea of CM's plans, but you can UV with any ROM as it is dependent on your kernel.
Install the kt747 kernel and after you do that you'll have an app in your app drawer called ktweaker. Go into that and under volt away.
Sent from my SGH-I747 using xda app-developers app
derberts said:
Install the kt747 kernel and after you do that you'll have an app in your app drawer called ktweaker. Go into that and under volt away.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Can you please give me the link to that?
http://forum.xda-developers.com/showthread.php?t=1756776
Be sure to download the one that corresponds to your ROM.
CamFlawless said:
http://forum.xda-developers.com/showthread.php?t=1756776
Be sure to download the one that corresponds to your ROM.
Click to expand...
Click to collapse
Thank you!
CamFlawless said:
http://forum.xda-developers.com/showthread.php?t=1756776
Be sure to download the one that corresponds to your ROM.
Click to expand...
Click to collapse
This will work with my Cyanogenmod 10.1, right? What exactly is a kernel?
TimeAndroid said:
This will work with my Cyanogenmod 10.1, right? What exactly is a kernel?
Click to expand...
Click to collapse
If you are sure to DL the 4.2.1 JB version, yes it should work. I say should as I don't use CM and can't be certain you won't run into issues.
As for the explanation of a kernel, I think you should do some reading up before flashing them without proper knowledge. This link is worth reading and bookmarking for later use.
http://forum.xda-developers.com/showthread.php?t=1369817
Read,read,read if you're still not sure read some more the kind folks here at XDA have vast amounts of knowledge and I can guarantee you that you'll find Answers to most if not all of you're answers.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
CamFlawless said:
If you are sure to DL the 4.2.1 JB version, yes it should work. I say should as I don't use CM and can't be certain you won't run into issues.
As for the explanation of a kernel, I think you should do some reading up before flashing them without proper knowledge. This link is worth reading and bookmarking for later use.
http://forum.xda-developers.com/showthread.php?t=1369817
Click to expand...
Click to collapse
Could you please help me with these steps?
1. Clear cache
2. Clear dalvik
3. Fix Permissions
I think I know how to clear the cache with clockwork recovery but I do not know how to do the other steps.
TimeAndroid said:
Could you please help me with these steps?
1. Clear cache
2. Clear dalvik
3. Fix Permissions
I think I know how to clear the cache with clockwork recovery but I do not know how to do the other steps.
Click to expand...
Click to collapse
I haven't used CWM in months, but I believe both options are located under "advanced" on the main menu.
TimeAndroid said:
Could you please help me with these steps?
1. Clear cache
2. Clear dalvik
3. Fix Permissions
I think I know how to clear the cache with clockwork recovery but I do not know how to do the other steps.
Click to expand...
Click to collapse
Friendly advise:
As it has been mentioned before, you should really read more on what you're about to do here. UV can make your phone unstable and if you don't know what you're doing at the first place and/or how to recover from a unstable state, you'll have a paperweight in your hands.
Please use the search button, read and learn more on what you want to do.
After installing the kernel, do I need to update the kernel when I update cm 10.1? And how do I "fix permissions"?
TimeAndroid said:
After installing the kernel, do I need to update the kernel when I update cm 10.1? And how do I "fix permissions"?
Click to expand...
Click to collapse
Fix permissions by going into advanced in clockworkrecovery, should be the last option. Don't know about your other question but you can check what kernel your running by going into settings--->about.
TimeAndroid said:
After installing the kernel, do I need to update the kernel when I update cm 10.1? And how do I "fix permissions"?
Click to expand...
Click to collapse
Every time you reinstall or update your ROM you need to reinstall your kernel of choice. This is because the ROM will have its own kernel that overwrites the one you install.
To fix permissions, you need to boot into recovery. From there it depends on your recovery software. In TWRP, you select "Advanced" and then "Fix Permissions", swipe to confirm and reboot. I forget where it is in CWM but poke around a little bit and you should be able to locate it.