Database Info

[Q]Reflashing s7 from cm7 and app install problems

So I flashed the unofficial cm7 build from the dev forum meaning I now have blue Cwm instead of red that I used with s7. What steps are required to reflash s7? Do ihave to use sgs kernel app to reflash kernel then flash s7?
Also I'm having issues restoring apps with titanium. The "stock" app installation screen doesn't allow me to choose install, only cancel. Does this issue stem from not having done a factory data wipe? The thread I read only mentioned to format the system disk but I don't think it was written from the perspective of having come from s7.
Mad props for any help
Sent from my SGH-I997 using XDA App

Yes you will eventually have to use SGS to flash a kernel. Maybe this is the long way around but when I flashed back from cm7 yesterday I used sgs kernel flasher and followed the instructions for infused gb. When I flashed the kernel it got stuck converting partitions to ext4 (probably because they were already in ext4). But I did a battery pull in the middle and was back in red cwm. After that I flashed infused again without hassle with infusion core b. That being said, as long as you have red cwm, you should theoretically be able to flash whatever rom you want.
So in short : just follow the FULL instructions to flash infused v2. Then flash s7. Hope this helps
Sent from my SGH-I997 using XDA App

Thaanks! Will try this if my reflash of cm7 doesn't fix issues....do you think my app install problems are stemming from a previous install?
Sent from my SGH-I997 using XDA App

Hmmm...well out of habit I always personally makes sure I format everything, wipe the dalvik cache, fix permissions and wipe the cache partition as well. A lot of the devs stress that this is necessary so I wouldn't doubt that your app install problems are from a previous install. Something tells me, and someone please correct me if I'm wrong, that when you are going from a voodoo enabled ROM like infused or s7 to a ROM like cm7 that doesn't use voodoo lagfix, you will have issues with trying to get your apps back because they were using a different (but still similar since they are both EXT4) file system. This is just my guess. If anyone could elaborate more on this please do.
I would highly suggest flashing back to stock if you still experience issues or even ultimate unbrick so that way you can get a clean slate. Maybe try using apps2sd. I own it and can verify that it works well. Many others have also praised it. Good luck!

stratatak7 said:
Hmmm...well out of habit I always personally makes sure I format everything, wipe the dalvik cache, fix permissions and wipe the cache partition as well. A lot of the devs stress that this is necessary so I wouldn't doubt that your app install problems are from a previous install. Something tells me, and someone please correct me if I'm wrong, that when you are going from a voodoo enabled ROM like infused or s7 to a ROM like cm7 that doesn't use voodoo lagfix, you will have issues with trying to get your apps back because they were using a different (but still similar since they are both EXT4) file system. This is just my guess. If anyone could elaborate more on this please do.
I would highly suggest flashing back to stock if you still experience issues or even ultimate unbrick so that way you can get a clean slate. Maybe try using apps2sd. I own it and can verify that it works well. Many others have also praised it. Good luck!
Click to expand...
Click to collapse
i went and did another install of cm7 before i ultimate unbrick back to stock. i figure out the app install problem; unknown sources wasn't checked...very noob. but the promt at the beginning of titanium caught me off guard and i cancelled before i could read it.
i, too, noticed that my app icons were intact on my desktop after the s7 to cm7 flash but most (if not all) those that did not require root would force close upon opening. reinstalling the app worked, but i had to get them from the market at the time as my unknown sources box was unchecked. also, i've noticed that widgets do not reload after reboot.
one more thing, after the second flash of cm7, i noticed that flashing gapps only provided me with the market. others such as email and talk were available for dl thru the market but weren't loaded from the gapps flash. i tried multiple times to no avail.
i'm about to ultimate unbrick and reflash cm7 from stock. one more last thing, i'm fairly comfortable with red cwm but have only encountered blue with cm7...how do i wipe the dalvik cache?
thanks for the help!

albee320 said:
i'm about to ultimate unbrick and reflash cm7 from stock. one more last thing, i'm fairly comfortable with red cwm but have only encountered blue with cm7...how do i wipe the dalvik cache?
thanks for the help!
Click to expand...
Click to collapse
When using TiBu, make sure and restore apps using the "restore all apps with data" option, just did it coming from S7 to MIUI and worked fine.
As far as Gapps go, I downloaded them from the Cm7 wiki and installed them manually from blue CWM just to make sure everything was added and it worked for me.
Dalvik is in advanced just like red CWM, just a different color.

xIC-MACIx said:
When using TiBu, make sure and restore apps using the "restore all apps with data" option, just did it coming from S7 to MIUI and worked fine.
As far as Gapps go, I downloaded them from the Cm7 wiki and installed them manually from blue CWM just to make sure everything was added and it worked for me.
Dalvik is in advanced just like red CWM, just a different color.
Click to expand...
Click to collapse
I've always heard it is a huge no-no to restore all apps with data.

EricNagel said:
I've always heard it is a huge no-no to restore all apps with data.
Click to expand...
Click to collapse
restoringing all USER apps with data is okay but dont include SYSTEM apps with data

EricNagel said:
I've always heard it is a huge no-no to restore all apps with data.
Click to expand...
Click to collapse
the "system data" is the no no, and "restore missing apps" is the preferred option, but I've always avoided system data and have been fine everytime I restore.

[Q] Home and search button stopped responding?

Hey guys,
I'm running the Octane ROM on my SGS4G, and suddenly both my home and search touch keys stopped functioning. However, they ARE triggering haptic feedback (a vibration in the phone when pressed)
Does anyone know what causes this and what's a common trouble shooting route?
I updated my binary in super user and updated busybox...nothing changed.
Also, I don't know if this is related to the problem but it happened at the same time: text msg notifications are permanently as if the phone is on silent; no sound or vibration. Just a status bar icon.
Thanks in advance to anyone who can help, this phone is my only daily.
Sent from my SGH-T959V using XDA App

Have you rebooted the phone? If so, I'd suggest doing a backup then performing a factory data reset.

Yea I rebooted several times..
could I just wipe the dalvik?
If I only do that, what information is lost on my phone?
Also the update from busy box said it might require I do a package reinstall "without" a factory wipe for the update to take effect... Any suggestions on that?
Sent from my SGH-T959V using XDA App

Stafaa said:
Yea I rebooted several times..
could I just wipe the dalvik?
If I only do that, what information is lost on my phone?
Also the update from busy box said it might require I do a package reinstall "without" a factory wipe for the update to take effect... Any suggestions on that?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
You could always try wiping caches first. No data loss that way. The Davlik cache will rebuild itself over time.
I'm nto sure about BusyBox, though. Maybe someone else has an idea?

What about the cache partition?
I guess my question is, what exactly are you wiping when you wipe the dalvik and when you wipe the cache partition?
and is it a safe practice for when strange problems like this arise?

Just wiping the cache.completely safe and the first thing to try after a reboot.also I would suggest fixing permissions when clearing the cache
Sent from my SGH-T959V using Tapatalk

Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?

Stafaa said:
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Click to expand...
Click to collapse
Fix permissions in the advanced option of cwm
And no factory reset does not wipe sd unless you tell it to when you're doing it from your settings menu
Sent from my SGH-T959V using XDA App

ah, gotcha.
Wish I woulda have tried that before wiping.
Another question: After the wipe, I lost all the fonts that were originally there after I first installed Octaine ROM.
I'm thinking I should just reinstall the package, but I'm afraid I cant remember if I had to disable VOODOO lagfix first and whether or not i still have to change the mounting points before i reinstall the rom..

Stafaa said:
ah, gotcha.
Wish I woulda have tried that before wiping.
Another question: After the wipe, I lost all the fonts that were originally there after I first installed Octaine ROM.
I'm thinking I should just reinstall the package, but I'm afraid I cant remember if I had to disable VOODOO lagfix first and whether or not i still have to change the mounting points before i reinstall the rom..
Click to expand...
Click to collapse
Glad you got it working though sucks you had to wipe everything. To be safe I would disable voodoo though I do not know if it's necessary. Definitely go into CWM and re-check the mounts first before flashing.

Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??

Stafaa said:
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Click to expand...
Click to collapse
I'm running the Octane rom too, and have started having problems with all four buttons, but mainly the outside settings and search ones. Other roms do the same for me now, so I don't think it's the problem. I have fully wiped, reformatted, fixed permissions, you name it.
It dosen't seem to matter what happens, they still resist working properly. So are you saying that doing a wipe/reinstall/permission fix did it for you? I can't tell if it's a physical thing or a software thing, but I'm leaning more toward software.

Stafaa said:
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Click to expand...
Click to collapse
You should probably re download your desired rom, do a full wipe (data, cache, and dalvik) and re flash. this sucks but should work. Did you by chance ever flash a kf series 2.3.3 ROM?
Sent from my SGH-T959V using XDA App

Stafaa said:
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Click to expand...
Click to collapse
After the wipe did you install a new ROM or stay on Octane? Maybe try wiping & install Raver's KJ6 stock via Odin or CWM. Run stock for a few days and see if the problems persist.
Sent from my SGH-T959V using XDA App

[Q] HELP flashing kernel PLEASE

I have just recently begun modding my G2x. I can install ROMs without any problems but I've since been interested in flashing a custom kernel. Information is sort of everywhere and what I do manage to find I am worried about it being out-of-date. Anyway, I flashed cm7.1 (the stable release) and it worked fine until it started fc-ing everything google related (something to do with sync?). I decided to try flashing kernels (wiping caches as instructed) and could never get one to work. I've since flashed the latest cm nightly (201 I think) and tried trinity with it. Still nothing. I've since read that I should let the phone sit for 10-20 minutes but after about 20 minutes it is just a black screen and nothing ever happens. It does get really hot however. Anyway I have tried flashing kernels multiple times and nothing has ever worked, same story every time. Any way somebody could tell me what I'm doing wrong? Tell me what's compatible (as maybe sorta stable) with the ROMs I'm using? HAHA and if it's not asking too much...maybe some links too? Sorry, just very new to this and very eager to learn. I just have a bit of trouble figuring out what's supposed to be compatible and where to find it. THANKS!

Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!

fcisco13 said:
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Thanks will give it a shot in the morning. Too much of a headache all day. Back in a useable state and I want to keep it that way for a bit haha. Will post results.

I still haven't tried to flash a new kernel... that is coming in a bit. I do have a question though... I'm interested in getting my phone in the cleanest state possible before doing anything further. I basically want my external sd cleaned up (I want to just reformat it) before flashing a rom again. What files/directories are absolutely essential to keep? As I said, I want to just wipe it clean but I'm not sure I can do that.
Sent from my LG-P999 using XDA App

So just to be thorough I can safely remove the cwm directory as well? Just delete it all put my rom and kernel zips back and I'm good?
Sent from my LG-P999 using XDA App

Make sure you flashed recovery through nvflash
NVIDIA NEVER AGAIN!

Tried to just flash 0.4.7 and it did the same thing as before. Waited 20 minutes before taking out the battery then tried to boot it again. Waited 20 more minutes and all it ever did both times was get hot. Same results as before.
Sent from my LG-P999 using XDA App

OK that's what I was missing. Needed to be running SV. Anyway it's working now just fine. Muuuch appreciated.
Sent from my LG-P999 using XDA App

(Q) One Last Grasp: The Lose Data, Lose APN CM code bug

After reading thread upon thread and flashing rom upon rom, wiping and nullifying the way along. I still have this issue that many of you are aware and just hoping by chance I may have missed the answer and someone can help me.
I am experiencing the bug where if you lose data, whether it be by switching to airplane mode and back, shutting of the phone, not rebooting it, or just a drop in coverage, when it comes back the APN list is cleared and can no longer connect to any data. Calls and texts seem to go through, but surfing and picture messaging don't work until the phone is rebooted, normally or through the button combo.
I've tried wiping everything several times, even uses the nullifier dual wipe twice and it still happens. I've tried all kinds of roms, 2 different MIUI, Eaglesblood, Kang Banger, Weapon, they all do the same thing. The only thing that "works" is restoring my very first stock nandroid. But once I go from that, wipe, and flash another, the problem returns. If it matters, my order of rom flashing was stock then Singh MIUI-GalNet MIUI-Kang Banger-EaglesBlood-Weapon-Singh. All gingerbread roms (I believe).
So if anyone can offer me just the slightest of solutions, it will be so very much appreciated. Thanks in advance.

When you saying "wiping"...what exactly are you wiping?
Sent from my LG-P999 using Tapatalk 2

I've worked pm with him, he's wiping system, cacheS, data, flashes zips then boots and then reboots later and fixes permissions. He still gets data drops and loss of apn's.
Sent from my LG-P999 using xda premium

Yeah mt3g has been a real help, but we're stumped. I wipe the data, wipe the cache, wipe the davlik cache, format the data cache and system, flashed, wait 20 minutes, reboot and fix permissions, reboot and wait again. Even flashed different kernels. All to no avail. And for some odd reason, I use T-Mobile, but I have Simple in my APN list as well and I think that leads to the issue.

I noticed Harsh's latest Kernel fixed the issue for me.
Sent from my LG-P999 using xda premium

Bulletblitz27 said:
I noticed Harsh's latest Kernel fixed the issue for me.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Why are you bringing up a kernel that is for cm9 when the discussion is about cm7?
Sent from my LG-P999 using xda premium

Yeah, that would cause a whole new set of problems huh? lol

[Q] P5110: Random Rebooting (CyanogenMod 10.1 - RC5)

My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!

jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,

jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.

Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.

Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium

Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?

Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.

Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium

Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.

Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.

Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.

jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app

After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.

Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?

All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app

Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1

I am Having the same prob with galaxy tab2 7.0(gt-p3100)