Database Info

Kernel's?

Can someone explain to me how kernel's work and if I flash one will I be able to get rid of it? Say flash a stock one? Someone please explain.

Make a nandroid before flashing the kernel

Darrien13 said:
Can someone explain to me how kernel's work and if I flash one will I be able to get rid of it? Say flash a stock one? Someone please explain.
Click to expand...
Click to collapse
The kernel provides the subsystem on which the OS itself operates. It is the interface to the physical hardware, handling access to physical devices as well as memory management. An optimized kernel can make a significant difference over a "vanilla" configuration.
Make a nandroid before you flash any kernels to go back easily. Otherwise you could reflash the full 2.3.3 rom.

thank you guys

If you're using CM7 and want to flash a kernel over it. You can just reflash CM7 without wiping anything and it would override your kernel with stock. CM7 includes stock kernel in it.

Yarr when I upgraded from 2.3.2 to CM7 RC1, my netarchy 1.2.5 resetted back to stock as I lost my Overclock. I just wasn't sure it was a stock kernel or a modified one specifically for CM7 that happened to not have an OC.

Aria807 said:
Yarr when I upgraded from 2.3.2 to CM7 RC1, my netarchy 1.2.5 resetted back to stock as I lost my Overclock. I just wasn't sure it was a stock kernel or a modified one specifically for CM7 that happened to not have an OC.
Click to expand...
Click to collapse
its stock. if you use SetCPU and check the info, its labeled as google.com
or about phone it says #google

[Q] Experiences with Kernel Manager or Kernel Manager Lite?

I've been flashing kernels through Clockwork, but I decided to download Kernel Manager Lite and I'm considering trying it. Has anyone had any experiences with it, good or bad? I'd appreciate any feedback before giving it a go. Thanks

it's works flawless for me, i use the free one.

The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App

That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
icesteve said:
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse

I was using kernel manager pro when I attempted, not the one included in the rom. I figured it had to be kernel manager because CWM flashed it perfectly.
Sent from my ADR6400L using XDA Premium App

Thanks for the responses. I'll probably give it a try. I guess I can always reflash through Clockwork if anything goes wrong. Or worse case, I can flash a backup if anything gets seriously out of whack.

bunklung said:
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
Click to expand...
Click to collapse
I had the same problem .. I never considered that it may have been kernel manager .. thanks for that
Sent from my ADR6400L using XDA App

For me the issue is this ...
No backup made prior to flashing ... I'm sticking w/ RM for kernel flashing

Based on my experience with BAMF rom and leanKernel, it appears that any customization scripts and/or files that the kernel developer intended for you DO NOT get flashed with Kernel Manager (I have Pro version). The people with broken wifi using KM but working wifi with RM proves the point. My experience was that 4G hotspot didn't work when flashing leanKernel from KM, but works fine with an RM flash. This is actually a common problem across several devices I've used. Many kernel devs modify the wifi driver and/or other things in a manner that they end up only working with their specific ROM. The do this by including the modified files in their zip package along with a script telling the phone what to put where. The issue becomes if you switch to a kernel that's relying on a stock wifi driver, and doesn't put it back on its own, then you've got a busted wifi. The only way around that is to manually push/restore a copy of a wifi driver known to work with the kernel you're using. I kind of regret paying for the pro version after finding this out; hopefully the KM folks can figure it out. The kernel itself is just the boot.img file; the add-ons files that go into the /system partition or where-ever. If you're interested in knowing what a particular kernel is pushing on your phone, just open the zip file and drill down through the folders to find what files are in /system tree. This is also a way to find files you need to go back to stock drivers, just find a stock rom that's flashable in RM and drill down to the files in /system/lib and push them back to the phone via adb or root explorer.

i bought the pro version and i wish i hadn't. i downloaded/flash one of protekks kernels through there and it sent my phone into a bootloop and by the time i'd flashed a nandroid backup the 15 minutes had gone by -_______-

why?
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.

turbosrrgood said:
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
Click to expand...
Click to collapse
It will notify you of kernel updates, and you can filter kernels based on what you want
Sent from my ADR6400L using XDA Premium App

Voodoo Lagfix and others after GB Update?

Okay ... So I am about to update to the latest pushed version. Am rolling back to EE4 now and have the update.zip on my card. What about CWM? Does my current version I've been using with my Gummy Charged 2.1 work with it? I have the Imosyn (sp) kernel on my card that I will apply after the update to 2.3.6 for root, as I understand it.
Are there any Gummy's or anything that are going to work after the 'official' update?

You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.

shrike1978 said:
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
Click to expand...
Click to collapse
Thank you sir! Phone is updating now. I will apply the imoseyon kernel after it's done. Lagfix is the main thing anyhow, I can nuke the bloatness with my Titanium.

now I'm confused .... I no longer have CWM recovery. How am I to apply the imoseyon kernel via stock recovery? Can I just rename it as update.zip?

By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.

trparky said:
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
Click to expand...
Click to collapse
Ahhhh.... it's @ the Sammy screen and she's talking to me! Looks like all is good while it re-writes the allocation tables. Thanx again, appreciate the heck out of the help.

hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?

Chopstix9 said:
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Click to expand...
Click to collapse
You SHOULD have root since the kernel is your root method. Have you tried restarting?
Sent from my SCH-I510 using xda premium

Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?

Chopstix9 said:
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Click to expand...
Click to collapse
Try installing Superuser from the Market? imosyeon kernel should have installed binary and apk, but maybe it missed part of it. If all else fails, flash the superuser zip from CWM.
http://www.toms-world.org/android/download/http/Superuser-3.0.7-efgh-signed.zip

Yes, I had installed SU from the market and didn't have root. I had an SU zip saved on my desktop .... su-2.3.6.3-efgh-signed .... I put that on the sd and installed it and I am rooted !!
Thanx Again

I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.

KarateExplosion6 said:
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
Click to expand...
Click to collapse
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.

Chopstix9 said:
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Click to expand...
Click to collapse
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.

It just doesn't matter ... In all honesty I liked the feel of the Gummy GBE 2.1 better than this stock ginger ... but again, it just doesn't matter to me. Functionality is all I care about, it's only a damn phone !!!

I loaded up the debloated/deodexed/rooted all-in one package danalo posted in development, flashed perfectly and after a wipe in CWM on first boot seems to be running fine except for the poop
sent from my Acer Iconia A500 beast of a tablet via XDA app

KarateExplosion6 said:
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
Click to expand...
Click to collapse
Care to make a thread of what you done? Files used? I want to re-root my Charge, but want to keep the latest ota update and radios. Main question is the "update.zip" file?

iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.

trparky said:
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
Click to expand...
Click to collapse
Yeah, I read last night. Awful news. I hope someone can just get us full Voodoo and EXT4 support. I don't absolutely need OC/UV, but it'd be nice...
In other bad news, imnuts is getting a Galaxy Nexus and only pledging support for the Charge for "a few more months."
Let's hope JT and the gang can get this RIL figured out, so we can at least have Team Douche to continue development with CM 7.2 and CM 9...
Sent from my SCH-I510 using xda premium

Damn. And I thought it couldn't get any worse with iMoseyOn leaving. And now we have imnuts leaving too? It just went from bad to worse in a matter of 48 hours!
Guess I better get used to just using the stock kernel.

Overclocking in ICS?

I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.

stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.

sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.

Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.

Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.

stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?

Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL

Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.

UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.

I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss

WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.

WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.

fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss

WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.

horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.

[Q] I think I need to downgrade my baseband...can someone please confirm?

G2X LG P999
CM7.2 Nightly 2012-12-02
Faux123-054
BB Mar 11 2012
CWM v5.0.2.0
As a result of trolling this site for a while, I have tried a few different ROMs and a couple of different kernels. All is good with this present combo except for an overheating issue while charging that I'm pretty sure is fixed (checked "Stay awake" in Settings/Applications/Development). I tried Hellfire Phoenix v2.3 last and dug it. I came back to CM7 because I recently had the need for bluetooth (headset) in my car and with my PC. I thought the problem was with the ROM, but after having the same bluetooth issue with CM7, I dug around here and found out that the problem is the baseband.
Am I right in that assessment?
If I am right and the only way to get bluetooth working on a custom ROM is to downgrade the baseband, is this what I need to do?: http://forum.xda-developers.com/showthread.php?t=1048274
Do I really need to go back to stock? Can't I just use CWM to flash a baseband that will work?
TIA,
Nasty

Yes, currently Bluetooth headset only works on the stock gingerbread roms with the new baseband.

Additional question
TwitchyEye said:
Yes, currently Bluetooth headset only works on the stock gingerbread roms with the new baseband.
Click to expand...
Click to collapse
Thanks...bummer. I guess I'll have to live without...not going back to stock.
I reloaded Hellfire Phoenix 2.4.2 and put the OC mod version of Mazout360's CM7/9/10 Kernel. I like it the most. But, it's a battery burner...which isn't that big of a deal most of the time. But if I have to do some traveling and need the extra battery life, I may need to flash the stock voltage version.
Question:
Can I flash the kernel without wiping everything out the ROM and having to go through the whole setup from the ROM's startup (reload apps, adjust settings/drawers/ringtones, enter mail accounts etc)?
Or would it be better to get an app like Setcpu and figure out how to downclock and lower voltage when I need the extra battery life.

Just boot into recovery and flash the kernel, don't need to wipe anything.
Assuming you're talking about mazouts non oc one.
Sent from my LG-P999 using xda app-developers app

You would still need to wipe cache and dalvik... can't flash a kernel without that typically.
Sent from my LG-P999 using xda app-developers app