Develop Bugs

Baked snack kernel

Can I use baked snacks kernel on a different Rom? I'm looking to improve battery life

I don't see why not. Nand backup and go for it.

EVOme said:
I don't see why not. Nand backup and go for it.
Click to expand...
Click to collapse
Is that what makes it have good battery?
Sent from my PC36100 using XDA App

Rocklee99 said:
Is that what makes it have good battery?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
what? doing the nand backup? that's just in case the kernel doesn't work you can restore to the previous condition your phone was in (so do it before you flash baked's kernel)
I'm not sure if his kernels will work on other roms though, I think I tried once

I've used it on my ROM what ROM are you using that might help.

mistersquirrle said:
what? doing the nand backup? that's just in case the kernel doesn't work you can restore to the previous condition your phone was in (so do it before you flash baked's kernel)
I'm not sure if his kernels will work on other roms though, I think I tried once
Click to expand...
Click to collapse
No I meant is the kernel what gives better battery, BTW I'm using ava froyo Rom v8
Sent from my PC36100 using XDA App

Rocklee99 said:
No I meant is the kernel what gives better battery, BTW I'm using ava froyo Rom v8
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes the kernel can help with battery life. You should be ok with flashing a different kernel and that ROM but as posted do a NAND backup before flashing the kernel.

Does anyone know how good the battery is for baked snacks kernel and does anyone know where I can find his kernel #6 ?
Sent from my PC36100 using XDA App

Rocklee99 said:
Does anyone know how good the battery is for baked snacks kernel and does anyone know where I can find his kernel #6 ?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
#6 has never been available for download. I used BS 1.7 on NA 4.19 and my battery was day and a half if not better with average use...seriously. I was amazed. I tried all the baked kernels and nothing worked like that.
Now I am on BS 1.8 using the same kernel and not getting near the same batt life.

EVOme said:
#6 has never been available for download. I used BS 1.7 on NA 4.19 and my battery was day and a half if not better with average use...seriously. I was amazed. I tried all the baked kernels and nothing worked like that.
Now I am on BS 1.8 using the same kernel and not getting near the same batt life.
Click to expand...
Click to collapse
NA as in netarchy?
Sent from my PC36100 using XDA App

Baked Snack
I have no clue how you guys are doing it, but I have the 1.7 version with kernel 6.
I took it off the charger this morning (after a full charge), it is now almost dead, with very little use.
How do you guys do it? Your not shopping the images are you?

This is a newb question I know, I have searched all over the forums. i have the stock rom and am not interested in any of the roms since most of them seem to not have 4g working or some other things( cant wait until they do!). My question is how do I flash just the kernel? i have never flashed anything before and I just backed up everything with rom manager. thanks!!!

mcskibadee1 said:
This is a newb question I know, I have searched all over the forums. i have the stock rom and am not interested in any of the roms since most of them seem to not have 4g working or some other things( cant wait until they do!). My question is how do I flash just the kernel? i have never flashed anything before and I just backed up everything with rom manager. thanks!!!
Click to expand...
Click to collapse
Wipe cache, wipe dalvic, flash like you would a Rom. Don't forget to nand first.
Sent from my blah blah blah blah
Edit - I'm assuming there's a specific kernel you have that you want to flash, and you didn't mean how to extract the kernel from a full Rom - also just noticed that you said you already backed up with rom manager. You may want to consider backing up manually through recovery or using amonra instead - nobody seems to know what exactly rom manager wipes when you tell it to wipe.

mcskibadee1 said:
This is a newb question I know, I have searched all over the forums. i have the stock rom and am not interested in any of the roms since most of them seem to not have 4g working or some other things( cant wait until they do!). My question is how do I flash just the kernel? i have never flashed anything before and I just backed up everything with rom manager. thanks!!!
Click to expand...
Click to collapse
i think you're misinformed (or haven't searched hard enough) - most, if not all, sense based ROMs have everything working and some (i.e. wireless/usb tether, performance/efficiency tweaks, etc.). it's the cm/aosp roms that don't have everything working (yet).
flashing kernels is similar to flashing roms. there is a plethora of threads on the topic. read some of the stickies and many of your questions will be answered to get you started with flashing roms/kernels.

edit: sorry i never know about this is paid version i tooked from his old xda thread, BTW thanks for let me know about that

quocamole said:
i think you're misinformed (or haven't searched hard enough) - most, if not all, sense based ROMs have everything working and some (i.e. wireless/usb tether, performance/efficiency tweaks, etc.). it's the cm/aosp roms that don't have everything working (yet).
flashing kernels is similar to flashing roms. there is a plethora of threads on the topic. read some of the stickies and many of your questions will be answered to get you started with flashing roms/kernels.
Click to expand...
Click to collapse
I have been on this forum for weeks trying to decipher all the lingo. I have not seen any Evo roms that have the 4g working, If i did I would have just used one of those.Trust me, i have searched all over this forum and others before bothering or asking stupid questions. Maybe I am searching the wrong stuff, I will search for sense based roms, thank you.
Also, I have never flashed anything before. Still trying to figure that one out. Thanks for the info guys!

mcskibadee1 said:
I have been on this forum for weeks trying to decipher all the lingo. I have not seen any Evo roms that have the 4g working, If i did I would have just used one of those.Trust me, i have searched all over this forum and others before bothering or asking stupid questions. Maybe I am searching the wrong stuff, I will search for sense based roms, thank you.
Also, I have never flashed anything before. Still trying to figure that one out. Thanks for the info guys!
Click to expand...
Click to collapse
here you go:
http://forum.xda-developers.com/forumdisplay.php?f=653
all roms are there. aosp roms are usually the roms where everything is not working.
general steps to flashing (but always read the post from the developer for any special instructions):
1. download file to sd card
2a. get into recovery (either via quickboot app or via powering down then holding volume down button while powering up)
2b. navigating in recovery - volume keys to change selection, power button to select
3. nand backup
4. wipe data, cache and dalvik (only wipe cache and dalvik if you're flashing a kernel)
5. flash the rom/kernel you downloaded
6. reboot
7. drink beer
if something goes wrong, get back into recovery and restore your nand backup.
hope this gets you started.... but read, read, read.
good luck.
sorry OP - back on topic. did you wipe cache and dalvik before flashing the kernel? what's your up time and awake time (found in settings>about phone>battery). do you have any monitoring apps installed (i.e. system panel, android system info? you may have rogue app.

juancaperez2000 said:
here is the baked snak kernel 6 if you want it
Click to expand...
Click to collapse
No offense but this is why Hero quit providing stuff at xda...Thanks though

juancaperez2000 said:
here is the baked snak kernel 6 if you want it
Click to expand...
Click to collapse
good on you removing the link

Thank you quocamole, that helps.

[Q] Accidentally over-undervolted and had bootloop. Not can't flash new kernels.

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...

change cpu speed

any working tool for a Gnex on stock rooted 4.0.4 rom to change cpu speed?
like setcpu of cpu-speed nofrill etc?
thanks

thegios said:
any working tool for a Gnex on stock rooted 4.0.4 rom to change cpu speed?
like setcpu of cpu-speed nofrill etc?
thanks
Click to expand...
Click to collapse
I believe you need a kernel installed that will support overclocking.

WesMantooth said:
I believe you need a kernel installed that will support overclocking.
Click to expand...
Click to collapse
that's what i feared :-(
thanks

thegios said:
that's what i feared :-(
thanks
Click to expand...
Click to collapse
fear not!!!
make a backup in CWM recovery.
download and flash a kernal (i really like Frankos M2 kernal)
and enjoy. shouldn't mess anything up, but if it does, just restore your backup....no biggie.
no need to wipe data or anything like that (cache and dalvik cache can be wiped though)

Exactly. It's so easy to get back to stock conditions (and/or your previous setup, with a nandroid), there's really no reason not to try out a different kernel, particularly when the added features (like CPU speed control) have real life implications for improved performance.

turdbogls said:
fear not!!!
make a backup in CWM recovery.
download and flash a kernal (i really like Frankos M2 kernal)
and enjoy. shouldn't mess anything up, but if it does, just restore your backup....no biggie.
no need to wipe data or anything like that (cache and dalvik cache can be wiped though)
Click to expand...
Click to collapse
I have to be THAT guy but, it's kernel*
Sent from my Galaxy Nexus using xda premium

Updated 15/8/12 CM9 for One Bugs List & Solutions GSM+CDMA

Right guys THIS thread is for reporting bugs\issues and for solutions, PLEASE USE THIS THREAD and keep the DEV THREAD CLEAR. We need that thread clear for Deving uses. i will update this with every new release\hot\bugfix. if your unsure on how to create a logcat please refer to this thread
Please post logcats and please post your error like this:
Version of rom your running
DETAILED ERROR HERE (not just wifi doesnt work, explain on how it didnt work so we can reproduce)
Any mods your running and kernel version
issues with CDMA will have (CDMA) Next to them likewise for GSM
Known BUGS
Some graphic Glitch (GSM+CDMA)

**RESERVED**

Reserved

paarthdesai said:
reserved
lols
dont just say thanks hit thanks if i helped
a true lfc supporter
and a former symbian lover
sent from my awesome HTC One V using xda premium
Click to expand...
Click to collapse
shub and paarth why you both reserved?!?!
Sent from my ONE V using xda premium

Lloir said:
shub and paarth why you both reserved?!?!
Sent from my ONE V using xda premium
Click to expand...
Click to collapse
I will test and report my views there...I dunno about paarth
Sent from my HTC One V using XDA

Passa91 said:
Equivalent of a post just saying "first"... why don't you just post your thoughts when you've actually tested it. I mean, really...
On topic - it isn't clear from the dev thread, is hold press multitasking for menu key working?
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
No....i fixed it..
Long press home is multitasking and multitask button us now menu...
Sent from my HTC One V using XDA

Okay so I downloaded Lloir's version of cm9 alpha build.
Currently running adi_pat's titanium kernel build 4.
So I extracted the zip and flashed the boot image thru fastboot.
Then wiped the dalvik, cache, system and data,.
Didn't boot at all.
When I went with the original titanium boot image it got to the boot animation and got stuck there.
I guess this is cm9's way of being stuck at the HTC dev screen.
All other ROMs have worked perfectly on my device. Don't know what is going wrong this time..

tranceph0rmer said:
Okay so I downloaded Lloir's version of cm9 alpha build.
Currently running adi_pat's titanium kernel build 4.
So I extracted the zip and flashed the boot image thru fastboot.
Then wiped the dalvik, cache, system and data,.
Didn't boot at all.
When I went with the original titanium boot image it got to the boot animation and got stuck there.
I guess this is cm9's way of being stuck at the HTC dev screen.
All other ROMs have worked perfectly on my device. Don't know what is going wrong this time..
Click to expand...
Click to collapse
REFLASH titanium 4 make sure it's the 1ghz one and DO NOT flash the boot.img in the rom...DO NOT FLASH BOOT.IMG in the rom.....also i would like to remind that it does take awhile on 1st boot to load....also a how to logcat
http://forum.xda-developers.com/showthread.php?t=1726238

im off to bed for a few hours i worked last night, so i'll answer anything you put up when i wake up

Cool.

Btw will the android apps for the log cats be of any help here?

tranceph0rmer said:
Btw will the android apps for the log cats be of any help here?
Click to expand...
Click to collapse
none whatsoever, you need to adb logcat and save a text file

Yep thought so...... Any way to install adb without installing the whole sdk?
Like fastboot can be installed on its own?

Bug list updated

Hi
Just FYI: I guess for most this is not new
There is a difference where kernel modules are between
stock kernel and Titanium and KISS
Stock kernel will have its modules in /system/lib/modules
Titanium based kernels have them in the ramdisk of the
boot.img in /lib/modules. So the modules will come with the kernel
Titanium or KISS kernel is NOT abel to load modules
from /system/lib/modules
You can try by doing e.g
insmod /system/lib/modules/fm_drv.ko
And you will get the error
insmod: can't insert '/system/lib/modules/fm_drv.ko': invalid module format
So when you use Titanium or KISS make sure /lib/modules contains
the modules from the boot.img. Else e.g. WIFI will not work since the
module cannot be loaded
Regards
max

maxwen said:
Hi
Just FYI: I guess for most this is not new
There is a difference where kernel modules are between
stock kernel and Titanium and KISS
Stock kernel will have its modules in /system/lib/modules
Titanium based kernels have them in the ramdisk of the
boot.img in /lib/modules. So the modules will come with the kernel
Titanium or KISS kernel is NOT abel to load modules
from /system/lib/modules
You can try by doing e.g
insmod /system/lib/modules/fm_drv.ko
And you will get the error
insmod: can't insert '/system/lib/modules/fm_drv.ko': invalid module format
So when you use Titanium or KISS make sure /lib/modules contains
the modules from the boot.img. Else e.g. WIFI will not work since the
module cannot be loaded
Regards
max
Click to expand...
Click to collapse
that would explain a few things....... i honestly forgot all about this.....thanks dude! i keep forgetting the simple crap :silly:

Lloir said:
that would explain a few things....... i honestly forgot all about this.....thanks dude! i keep forgetting the simple crap :silly:
Click to expand...
Click to collapse
Your welcome
Actually I havnt found the exact reason why there is this "invalid format" error
Since the file has the correct format
bcmdhd.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
You can of course als replace the stock modules in /system/lib/modules with
the ones from /lib/modules if you use Titanium kernel
Regards
max
EDIT: Ok I know the reason - was just stupid
10 years of linux knowledge - should have known better
fm_drv: version magic '3.0.16-g42caf24 preempt mod_unload ARMv7 ' should be '3.0.16Titanium-KISS-svn322 preempt mod_unload ARMv7'
The reason is that Titanium or KISS use a different version "magic" which is compiled into the kernel modules

I've got some graphical glitches in settings menu, app drawer, etc., I wiped everything and formatted /system. Used TitaniumKernel and built-in kernel from zip.
Did anyone experienced that?
P.S. an insmod of /lib/modules/bcmdhd.ko worked for me, but wifi didn't work as far as I could have seen with these glitches...

TechnoLover said:
I've got some graphical glitches in settings menu, I wiped everything and formatted /system. Used TitaniumKernel and built-in kernel from zip.
Did anyone experienced that?
P.S. an insmod of /lib/modules/bcmdhd.ko worked for me, but wifi didn't work as fas as I could have seen with these glitches...
Click to expand...
Click to collapse
yes it's a problem the glitches....btw i've just pushed a new git that needs testing PM me if it needs to be reverted
btw DONT EVER EVER USE the built-in kernel....im pretty sure that's what caused my device to die...only use Titanium dude
Also try using the EGL folder from the CM9 in the DEV Thread and let me know if that removes the glitches

Lloir said:
yes it's a problem the glitches....btw i've just pushed a new git that needs testing PM me if it needs to be reverted
btw DONT EVER EVER USE the built-in kernel....im pretty sure that's what caused my device to die...only use Titanium dude
Click to expand...
Click to collapse
I haven't flashed the built-in kernel, I just booted it via "fastboot boot" - normally there should happen nothing if I use it that way. I think it's a prebuilt kernel with just another ramdisk, so there shouldn't be any issues... but as long as we don't know what's the reason I flash as less as possible maybe the built-in kernel hasn't started and rebooted so fast that it booted with titaniumkernel. I don't know.

[Q] Need help with undervolting

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.