Related
Quick question i am using a custom rom and I have to flash a kernel to get my wifi working. Is their a way to flash it into the rom so i don't have to flash it every time i do a wipe. Sort of out box tweak
We can't flash kernels by recovery so you shouldn't have to worry about having to reflash the same kernel over again.
Sent from my HTC Amaze 4G using xda premium
Binary100100 said:
We can't flash kernels by recovery so you shouldn't have to worry about having to reflash the same kernel over again.
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I thought so, every time i use the super wipe function and i install the rom i have to reflash the kernel to get my wifi working.
nofroyo said:
I thought so, every time i use the super wipe function and i install the rom i have to reflash the kernel to get my wifi working.
Click to expand...
Click to collapse
That's because the kernel modules are different than the rom modules.
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
nofroyo said:
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
Click to expand...
Click to collapse
You only have a few to chose from.
You have the stock and you have Faux123 kernel.
You may need to use the computer to flash the Faux123 kernel since the Flash Image GUI app doesn't always properly flash the modules.
Using command prompt or terminal right?
One last question if I flash using terminal will that allow me to switch roms and not have to keep on reflashing the kernel everytime ?
Thanks for all your help it's much appreciated
nofroyo said:
Using command prompt or terminal right?
One last question if I flash using terminal will that allow me to switch roms and not have to keep on reflashing the kernel everytime ?
Thanks for all your help it's much appreciated
Click to expand...
Click to collapse
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
I am going to try it right now.
Binary100100 said:
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
Click to expand...
Click to collapse
nofroyo said:
I am going to try it right now.
Click to expand...
Click to collapse
Okay just let me know how well it works for you.
You're a tester.
Binary100100 said:
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
Click to expand...
Click to collapse
it works perfectly, just plugged in and it did all the work. i rebooted and wifi is working as usual. good job.
hopefully i wont have to reflash the kernel every time i need to wipe haha
nofroyo said:
it works perfectly, just plugged in and it did all the work. i rebooted and wifi is working as usual. good job
Click to expand...
Click to collapse
Thanks for the update. I don't think that I can set it up any easier.
Binary100100 said:
Thanks for the update. I don't think that I can set it up any easier.
Click to expand...
Click to collapse
No worries if you need to test anything else i am willing to test
Binary100100 said:
You only have a few to chose from.
You have the stock and you have Faux123 kernel.
You may need to use the computer to flash the Faux123 kernel since the Flash Image GUI app doesn't always properly flash the modules.
Click to expand...
Click to collapse
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
nofroyo said:
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
Click to expand...
Click to collapse
I've been answering this exact question on the EVO 3D boards since HTC released their unlock method back in August. The best answer I've been able to formulate, and feel free to critique or post additional questions is as follows:
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4330.ko (bcm4329.ko is for EVO 3D) . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
In summary, there is no WiFi module which will work across all kernels as the WiFi module is compiled at the same time the kernel is compiled and are required to be used together as a pair.
Hope that helps clarify!
joeykrim said:
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
Click to expand...
Click to collapse
I noticed the issue while applying the Faux123 kernel with the Energy ROM
It's likely because it's not set up to be flashed by recovery but by a computer script.
The directory of the kernel flashing script directory goes like this
Amaze-EKF-008b13-sense
-Kernel-Here
---boot.img
-Modules
---system
-----etc
--------init.post_boot.sh
--------st_drv.ko
--------thermald.conf
--------ti_hci_drv.ko
-----lib
--------modules
-----------kineto_gan.ko
-----------tiap_drv.ko
-----------tiwlan_drv.ko
joeykrim said:
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
I've been answering this exact question on the EVO 3D boards since HTC released their unlock method back in August. The best answer I've been able to formulate, and feel free to critique or post additional questions is as follows:
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
In summary, there is no WiFi module which will work across all kernels as the WiFi module is compiled at the same time the kernel is compiled and are required to be used together as a pair.
Hope that helps clarify!
Click to expand...
Click to collapse
Once again thanks for this information it clearly answers my questions I had. The app you made solved my initial inquiry and works perfectly. Thanks for all you help and support :=)
Binary100100 said:
I noticed the issue while applying the Faux123 kernel with the Energy ROM
It's likely because it's not set up to be flashed by recovery but by a computer script.
The directory of the kernel flashing script directory goes like this
Amaze-EKF-008b13-sense
-Kernel-Here
---boot.img
-Modules
---system
-----etc
--------init.post_boot.sh
--------st_drv.ko
--------thermald.conf
--------ti_hci_drv.ko
-----lib
--------modules
-----------kineto_gan.ko
-----------tiap_drv.ko
-----------tiwlan_drv.ko
Click to expand...
Click to collapse
Yea, definitely not designed to be flashed by the recovery. They're using unique scripts which could easily be modified to follow the same standards as required by a recovery .zip. In fact, it is very easy to package up one .zip file which will do both, be flashable in recovery but also contain all the files and scripts to be flashable from a desktop via adb/fastboot.
Appreciate the link and info. Made it very easy to narrow down the issue!
Will definitely keep this in mind. Good to see/know there are some unique kernel .zip files be distributed which don't follow the "standards".
nofroyo said:
Once again thanks for this information it clearly answers my questions I had. The app you made solved my initial inquiry and works perfectly. Thanks for all you help and support :=)
Click to expand...
Click to collapse
Glad the information helped and appreciate the feedback!
Hey there!
So I've read a bit lately on rooting my S2 and what not (as I decided to give it a go), and after flashing CWM Touch to my S2 I loved it and found it so much easier to install ZIP's and what not. However, on boot it disappeared, then to find that it was only a temporary Flash and when I rebooted the phone, it simply reverted back to the normal CWM.
Now before asking me to use Google or search for a thread, by god I did that. And after looking for almost 2 hours, I found nothing that gave me a definite answer whether it was possible or not. And so this is why I'm creating a thread.
So is it possible to flash CWM touch on my S2 permanently (like other phones have), or do I have to stick with the volume/power button edition.
Thanks everyone! And thanks in advance.
The recovery, it's part of the kernel so which ever version of ClockworkMod the kernel shipped with that will always be there. If you really want touch recovery, you can flash Siyah Kernel and you'll be rooted and have its touch recovery.
Sent from my GT-I9100 using Tapatalk 2
nicholas1520 said:
The recovery, it's part of the kernel so which ever version of ClockworkMod the kernel shipped with that will always be there. If you really want touch recovery, you can flash Siyah Kernel and you'll be rooted and have its touch recovery.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hmm I hoped that wasn't the case.
But isn't there a way to use ODIN3 to flash the kernel with a custom recovery, such as the CWM touch?
Sorry if that sounds stupid, I just am new to all this.
Not sure if you are allowed to bump this or not, but I just did.
Really want to know if it is possible to flash CWM touch on the kernal guys!
xxshabsxx said:
Not sure if you are allowed to bump this or not, but I just did.
Really want to know if it is possible to flash CWM touch on the kernal guys!
Click to expand...
Click to collapse
Why don't you just keep a touch cwm.zip file in your download folder and flash that after you flash a new rom?
Sent from my GT-I9100 using xda premium
kilometers4 said:
Why don't you just keep a touch cwm.zip file in your download folder and flash that after you flash a new rom?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
And I do have the CWM touch zip in my internalSD but there isn't and point flashing it if everytime I reboot the phone and it goes back to the stock kernel.
I just want to know if there is a method possible to flash CWM touch into the kernel, and make it permanent, or at least fine a .tar version of it so I can flash it using odin
Once again I'll bump this.
Does no one have a solution at all?
xxshabsxx said:
Once again I'll bump this.
Does no one have a solution at all?
Click to expand...
Click to collapse
Edited. Sorry, I re-read the thread. As already stated, you'll need to flash a kernel that has the version of recovery you want. If you want a different version of recovery with a specific kernel, you'll need to start making your own kernels.
ctomgee said:
Edited. Sorry, I re-read the thread. As already stated, you'll need to flash a kernel that has the version of recovery you want. If you want a different version of recovery with a specific kernel, you'll need to start making your own kernels.
Click to expand...
Click to collapse
Well I cannot find a .tar version of CWM touch so I guess I won't be able to flash the kernel.
xxshabsxx said:
Well I cannot find a .tar version of CWM touch so I guess I won't be able to flash the kernel.
Click to expand...
Click to collapse
It's in the kernel. Check out RedPill. It has touch recovery.
ctomgee said:
It's in the kernel. Check out RedPill. It has touch recovery.
Click to expand...
Click to collapse
Hmm I saw RedPill but wasn't a fan of it, I really do like CWM
Does anyone know if there is a kernel that has CWM touch in it? For CM10 preferably.
xxshabsxx said:
Hmm I saw RedPill but wasn't a fan of it, I really do like CWM
Does anyone know if there is a kernel that has CWM touch in it? For CM10 preferably.
Click to expand...
Click to collapse
Why don't you just look at the kernels in the development section, specifically for one with touch recovery? You could have found all the available options and tried them out by now.
Or are you just being lazy?
ctomgee said:
Why don't you just look at the kernels in the development section, specifically for one with touch recovery? You could have found all the available options and tried them out by now.
Or are you just being lazy?
Click to expand...
Click to collapse
No I'm not lazy, sorry if I came across that way. I am usually one to simply find something on my own, but for this I simply cannot.
I've looked and cannot find what I asked for in the OP, and am still looking and found nothing. So I simply asked a question to make sure that there isn't a possibility that it can be done.
Anyway it doesn't seem possible at the moment, so I guess I'll wait.
Every tutorial I have read states that to make a custom rom for my phone, I need to download a rom for my phone first. Huh?
My phone is the kyocera rise from sprint.
As far as I know there are no roms publicly available for my phone. I have attempted to make a nandroid backup to see if that would produce a base rom to work with but I can't install a custom bootloader cause clockworkmod doesn't support my phone.
I have successfully rooted however.
My goal is to rewrite the AOSP rom to make a whole new OS for my phone based on android.
So in short here are my 2 questions:
How do I make a custom rom with no rom publicly available for my phone?
How do I install a custom bootloader for my phone if cwm doesn't support my phone?
I am not new to programming, I have 8 years of experience.
I know java, ruby, c# and c++ so if the solution requires programming that's fine with me.
Sent from my C5155 using Tapatalk
liquidmetalix said:
Every tutorial I have read states that to make a custom rom for my phone, I need to download a rom for my phone first. Huh?
My phone is the kyocera rise from sprint.
As far as I know there are no roms publicly available for my phone. I have attempted to make a nandroid backup to see if that would produce a base rom to work with but I can't install a custom bootloader cause clockworkmod doesn't support my phone.
I have successfully rooted however.
My goal is to rewrite the AOSP rom to make a whole new OS for my phone based on android.
So in short here are my 2 questions:
How do I make a custom rom with no rom publicly available for my phone?
How do I install a custom bootloader for my phone if cwm doesn't support my phone?
I am not new to programming, I have 8 years of experience.
I know java, ruby, c# and c++ so if the solution requires programming that's fine with me.
Sent from my C5155 using Tapatalk
Click to expand...
Click to collapse
Before you start making a custom ROM your going to want to port CWM to your device that way you can make backups that you can restore if the custom ROM you make doesn't function. To port CWM check out this great guide. After you have successfully ported CWM and tested it you can move on to custom ROM. From here you have two options. Now that you have CWM on your phone you can make a nandroid backup and create a custom ROM from that. The other option is to create a device and vendor tree for your phone and then build AOSP from source using the device and vendor tree. If you need any more help or have any questions let me know .
Thank you for the prompt reply.
That link was very informative.
If I build the AOSP rom and flash it, will I lose the ability to use my hardware keyboard? If so, is there a way to regain it?
I would assume there must be a way to copy the drivers from my nandroid backup but not sure where they are stored.
Sent from my C5155 using Tapatalk
liquidmetalix said:
Thank you for the prompt reply.
That link was very informative.
If I build the AOSP rom and flash it, will I lose the ability to use my hardware keyboard? If so, is there a way to regain it?
I would assume there must be a way to copy the drivers from my nandroid backup but not sure where they are stored.
Sent from my C5155 using Tapatalk
Click to expand...
Click to collapse
When you build an aosp rom from source some parts may be broken like h/w keyboard for example! There are various mentods to fix those! Seeing as you've programming experience it wouldn't be too hard
Check out the chef central!
Sent from my Tab2 using Tapatalk 2
Went about 6 pages deep in chef central and didn't see anything referencing or relating to hardware keyboard issues. I did however see some very interesting posts on kernel editing. Unfortunally kyocera has not made the kernel sources available for my device.
Sent from my C5155 using Tapatalk
liquidmetalix said:
Went about 6 pages deep in chef central and didn't see anything referencing or relating to hardware keyboard issues. I did however see some very interesting posts on kernel editing. Unfortunally kyocera has not made the kernel sources available for my device.
Sent from my C5155 using Tapatalk
Click to expand...
Click to collapse
You can try extracting the drivers for the hardware keyboard which can be found in the kernel. To do this take the boot.img file and split it, from here you will get a ramdisk from the ramdisk you can extract the kernel. From there you should be able to access the kernel and then extract the hardware keyboard drivers.
Sent from my SCH-I535 using xda premium
liquidmetalix said:
Unfortunally kyocera has not made the kernel sources available for my device.
Click to expand...
Click to collapse
The kernel sources have been released since. Here you go: Kyocera Developer
I had this phone for about 2 days before I jumped on a better deal (thanks, Black Friday!). Good luck with developing for this. I know there are a lot of people looking to get at least a custom recovery for it.
This additional information may be helpful as well. Since there is no recovery to flash things (like kernel, mods, etc.) you might want to consider Flash Gordon. It allows you to "flash any flashable zip (except for Roms) without having a recovery installed". If you were to do that, you could then install Onandroid, which allows you to "make a nandroid backup without switching off the phone". With that backup, you could get the necessary files to then create your own ROM. The problem would then be flashing the ROM but if you have the kernel source (see previous post), time, and a lot of will power, you could port CWM or TWRP. Hope this helps someone!
I have been trying to flash NX-Kernel_v1.1.0 to my phone which is running Rootbox-JB-i9300-v3.9.1.
I have noticed that the file I am trying to flash is not a .tar, which is what I am use to, but a .zip.
When i use TWRP to attempt to flash it boots into download mode and does nothing.
I have also tried using odin and mobile odin but i think because its a .zip odin cannot even see it.
The thread is linked below. I have searched it and people seem to be saying that it is possible to flash with a recovery and odin/mobile odin, all of these i have tried.
Can someone please tell me what i am doing wrong!?!?
http://forum.xda-developers.com/showthread.php?t=2192893
just flash it from recovery like a rom
is the rom based on CM10.1?
Tried
Glebun said:
just flash it from recovery like a rom
is the rom based on CM10.1?
Click to expand...
Click to collapse
I have tried flashing from tw recovery it does not boot into system from there.
The rom is a AOKP base.
guspop said:
I have tried flashing from tw recovery it does not boot into system from there.
The rom is a AOKP base.
Click to expand...
Click to collapse
Why would a kernel made for galaxy note or note 2 work on a galaxy s3?
There are sure to be differences which will make it not boot.
Sent from my GT-I9300 using xda premium
oops, didn't see that. Of course it won't boot, you're lucky if you didn't kill it
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
ficti0n851 said:
Why would a kernel made for galaxy note or note 2 work on a galaxy s3?
There are sure to be differences which will make it not boot.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
b-eock said:
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
Click to expand...
Click to collapse
Wow thank you I cannot believe I didn't realise it was for the note.
b-eock said:
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
Click to expand...
Click to collapse
Hate to tell you it can. I bricked an S3 by accidently flashing an S2 kernel to it which bricked the device to the point that a jig would not even revive it.
That makes no sense if you think of the booting process... I mean crazy things happen. But a kernel should never fully brick a device...
guspop said:
I have been trying to flash NX-Kernel_v1.1.0 to my phone which is running Rootbox-JB-i9300-v3.9.1.
I have noticed that the file I am trying to flash is not a .tar, which is what I am use to, but a .zip.
When i use TWRP to attempt to flash it boots into download mode and does nothing.
I have also tried using odin and mobile odin but i think because its a .zip odin cannot even see it.
The thread is linked below. I have searched it and people seem to be saying that it is possible to flash with a recovery and odin/mobile odin, all of these i have tried.
Can someone please tell me what i am doing wrong!?!?
http://forum.xda-developers.com/showthread.php?t=2192893
Click to expand...
Click to collapse
Flash it w CWM. Should work
Sent from my SPH-L710 using xda app-developers app
b-eock said:
That makes no sense if you think of the booting process... I mean crazy things happen. But a kernel should never fully brick a device...
Click to expand...
Click to collapse
It does if the kernel is not for the proper chip set. Like a kernel for a qualcom chip flashed on an eyxnos chip.
jorv976 said:
Flash it w CWM. Should work
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
the issue has already been found. The kernel is for a different device.
It should only result in a soft brick... Bootloaders are the first to come (primary then secondary. Secondary passing the booting process off to the kernel. Recovery is in the kernel while DL mode is in the boot loaders.) Oh well. I make sure I don't do stuff like that. I'm really OCD and paranoid about stuff being just right.
b-eock said:
It should only result in a soft brick... Bootloaders are the first to come (primary then secondary. Secondary passing the booting process off to the kernel. Recovery is in the kernel while DL mode is in the boot loaders.) Oh well. I make sure I don't do stuff like that. I'm really OCD and paranoid about stuff being just right.
Click to expand...
Click to collapse
\Yeah thats what I thought as well. I was just rushing far more then I normally do and downloaded the same rom for both the S2 for my brother and my S3 and flashed the wrong one to mine. Boy was I not happy. Spent 3 days with some of the most talented developers here and we all agreed that jtag was the only hope.
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes