I'm working on a stock kernel for my Moto X xt1095. I've got the kernel compiled and it boots but the camera and WiFi are not working. I've tried building the modules but this is where I seem to be stuck. Where do the modules go exactly? In the ramdisk? Any help would be appreciated. I've never built a kernel before and I've been reading several guides but I just can't seem to get this part to work.
Related
Hi ... i own the 'memory challenged' zte kis (from virgin mobile)... due to it's limited ram (and lack of pre-made custom roms) i decided to recompile the kernel with swap option set to 'y'., so that the phone can use swap.
after reading a few guides here and elsewhere i managed to get a successfully compiled kernel that worked on my phone. everything works apart from the original roms ar6000.ko/ath6k wifi module.
i'm presuming that i need to recompile ar6000.ko against the new kernel? so how would i go about that? and where can i find the source code for ar6000.k0/ath6k?
thanks
Dicking around my phone, i believe that we have the ability to use kernel modules on our phone, though I am using xXminiWHOOPERxX's kernel, I have downloaded the source from HTC and it seems that CONFIG_MODULES, CONFIG_MODULE_UNLOAD, and CONFIG_MODULE_FORCE_UNLOAD are set to "y". Looking around the net, I found a few places that shows how to compile kernel modules along with pulling the list of kernel functions.
Here's what I found:
-[Tutorial] How to compile a kernel module outside the kernel
-kallsyms on Android
Figured that this might be useful for those who want to make kernel modules for the Desire 601.
Hi guys, I'm doing a Cyanogenmod 12.1 porting for my device that is unsupported. I can build everything and I get a flashable zip but I'm using a prebuilt stock kernel image extracted from the stock lollipop rom. After flashing, the phone does not boot and It's impossible even to access to logcat, so I think it's a kernel related issue. My question is:
- I have the stock kernel source (v.3.10) given by the vendor
- I have the cyanogenmod kernel source (v.2.69)
Do I have to build the stock kernel or I can build the cyanogenmod one by merging the drivers modules and others stuff?
And if I flash a wrong kernel image can my device become unusable?
I read that is not fair importing built kernel modules from other kernel version, but if I merge the kernel trees, is it the same?
Sorry in advance if my question is a noob question
Well I don't know much about porting roms or kernels though. But with what I've heard flashing the wrong kernels can permanently render your phone useless..
Sent from my Tecno F7 a ...?
I recently tried compiling a kernel for Redmi Note 4g(dior) with dt2w feature. After compiling i succesfully got that option in kernal auditor but it is not working at all ie. whenever my device screen off nothing happens when i tap. I tried compiling kernal from various sources but still same result. Please someone help me about what i am missing.
vishalxox said:
I recently tried compiling a kernel for Redmi Note 4g(dior) with dt2w feature. After compiling i succesfully got that option in kernal auditor but it is not working at all ie. whenever my device screen off nothing happens when i tap. I tried compiling kernal from various sources but still same result. Please someone help me about what i am missing.
Click to expand...
Click to collapse
does your phone stock rom support dt2w ?
Im new to kernel compilation. I was trying to build a kernel without any modification from Sony z2 kernel source (23.5.A.1.291) to see if it works so that i can proceed modifying it to include wireless packet injection.
Most of the functions seems working except for wifi and usb otg.
Been trying various toolchains from doomlord repo. Can i have some help here? Is there any guide which i missed searching the last 4days?
Moderators.?
Is there anyone who could post this in the right section so that some devs could see this? Or can i private message anyone? I can't believe getting no help from xda.
Got it working. I wonder why Sony guides or default configs contain nothing related to this issue.