Is there a way to make this available (the kernel module) w/o installing a custom firmware?
gsmd said:
Is there a way to make this available (the kernel module) w/o installing a custom firmware?
Click to expand...
Click to collapse
just recompile the kernel from android source
Thanks.
Do you know any tutorials to get started?
Hi!
I've compiled a kernel (with enabled netfilter-support) which is suitable for the OFFICIAL ADP 1.6 firmware published by HTC.
It's based on the original kernel-config (plus netfilter/iptables)!
Available here:
http://code.google.com/p/android-wifi-tether/wiki/ADP16KernelUpdate
Don't install this kernel on any CUSTOM rom!
.
Would you care to list the steps you've taken to compile this kernel?
Guys I have made a custom rom based on CM7.nAa 14 kernel is compatible with CM7.But I want my custom rom also to support it.http://forum.xda-developers.com/images/smilies/crying.gifI have downloaded the .ftf kernel file and I have also extracted it.What changes do I have to do in my rom to make my rom work with the kernel?
Please give a detailed answer.
@OP
Well kudos to you for finding the right section. And what CM7 ROM exactly have you based your ROM on?
It already started working.But thanks for you trying to help.
What I want to know is that there is no networking in my rom.
Please help me fix it.I am talking about a custom rom developed by me based on cm 7.1.
What CM7.1 ROM have you based this on? I'm asking whether you have based your work on any existing ROM or not and the name of that ROM. If that ROM supports nAa-14 kernel, then your ROM will support nAa-14 kernel too.
My rom is supporting the nAa 14 kernel,I have tested it I have a bug in the network. It has no network at the moment. Do you know a fix for this bug ? I am running a rom that is developed by me and I am now testing it.
I haven't released the from here yet.
Sent from my X8 using xda app-developers app
Network bug? I don't even know if logcats can be used to debug. Can you try re-flashing the kernel and the ROM?
Basically you not need to change anything in the kernel. You need change the userspace drivers in the rom to match with the kernel level drivers. Both active x8 gb kernel (nAa and alfs) use similar drivers, except the proximity sensor (nAa use a modded one, alfs use the stock driver), you can use both with the correct libsensorservice and hw libs. And not 100% sure, but nAa use the older kgsl driver (1.1) alfs use newer (1.2), need to change the driver in the rom (libgsl.so).
To solve the network errors, you need to check the RIL related binaries and settings. Better if you give more detailed infos your base rom, the "cm7.1 rom" is not enough. CM7 but the origins? CM7 exists on thousands of phones. Better if you use x8 rom, or rom from a phone what use same hardware (msm7x27 like lg p500, galaxy mini, htc legend, etc...)
Sent from my E15i using xda app-developers app
What more should I add to"cm 7.1"? Please make it clear. Its downloaded from the cyanogen mod download center. It is used as my base rom. I modded it with certain tweaks and replaced many apps and also added many other mods
Sent from my X8 using xda app-developers app
You could have said that it was downloaded directly from cyanogenmod.com for a start. It's pretty confusing when you say just CM7.1 because there are hundreds of CM7.1 ROMs lying around the Development forum, some for stock kernel, some for nAa-gb and others for alfs-gb.
Let me give you a tip if you're just adding tweaks and other mods, and not modifying it on a large scale. Instead of releasing a ROM, why not release a flashable-zip that will make required changes to the existing ROM that users are on. It will be unique and if you want, I can help you with it.
Summary: Why waste time releasing a ROM (~80MB) when you can release a flashable-zip (~10-15MB)?
Cheers.
sgt. meow
I just asked what is your base rom because we not have official cyanogenmod support. If you use only the cm repo to build a complete rom, it will be really hard, due the missing device specific parts. So, the question again (I hope it is clear): you use only the cm repo as base OR use unofficial cm repo from nAa (with working device specific settings/codes) OR use prebuild cm7.1 rom from x8 OR use prebuild cm7.1 rom from other phone. All options is a cm7.1 rom, but all need different works.
From the best to the worst:
1. Use the minicm repo from nAa (nothing to do to get fully working rom)
2. Use prebuilt x8 rom as base (basically not need to do anything)
3. Use the official cm repo (need lot of work because missing a lot of thing)
4. Use any non x8 prebuilt rom (basically the hardest way, need large amount of work with hw related things)
Sent from my E15i using xda app-developers app
@pilu1978
We used to have official CM support till CM7.2 (I guess). It's stated in the CM Shakira page. And you can build CM7 from source as EET has explained in his tutorial. But in any case his best option (if he's going to compile from source) is to use MiniCM7 repo. It's the most updated one.
Plus it will support nAa-14 without any modifications.
The OP wrote this is cm7.1, not 7.2 As I know the official cm7 support is not complete, but my knowledge is NOT unlimited And we not have cm kernel.
Sent from my E15i using xda app-developers app
pilu1978 said:
I just asked what is your base rom because we not have official cyanogenmod support. If you use only the cm repo to build a complete rom, it will be really hard, due the missing device specific parts. So, the question again (I hope it is clear): you use only the cm repo as base OR use unofficial cm repo from nAa (with working device specific settings/codes) OR use prebuild cm7.1 rom from x8 OR use prebuild cm7.1 rom from other phone. All options is a cm7.1 rom, but all need different works.
From the best to the worst:
1. Use the minicm repo from nAa (nothing to do to get fully working rom)
2. Use prebuilt x8 rom as base (basically not need to do anything)
3. Use the official cm repo (need lot of work because missing a lot of thing)
4. Use any non x8 prebuilt rom (basically the hardest way, need large amount of work with hw related things)
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
I am using a prebuild x8 rom and modding it
And what is the original rom, what you use as base rom? If it is a stock kernel based rom, you need to change the drivers (sensors, gsl, egl, etc) to work with nAa kernels, if it is a minicm based rom, nothing need to do it will work with nAa kernel.
Sent from my E15i using xda app-developers app
I think he got over that problem by now. LOL.
No man its not working.
See I will explain my question once more. I am using this rom as my base rom: http://download.cyanogenmod.org/?type=stable&device=shakira
I want to make this rom compatible with custom kernels like nAa 14 and alfs etc so what should I do exactly?
If I have to change my drivers then please explain to me how to change my driver to these kernels and also tell me where to find the driver files in the rom and also tell me the download link for the drivers please.
I will be very grateful!
THANKS in advance. Please someone help me.
Hi all
I have been trying to find out what the latest version of clockwerkmod is and I would just like someone who knows to inform me if the version given out by rom manager which is 6.0.4.3 is the latest and greatest just so i can make sure it has selinux support as i'm quite new to hacking android.
I have been using the thread on the original development section however could some also inform me as to what "cm only" and "tw only" means as i cant find that on the thread
Thanks
CM only : kernel will only work on cm roms.
TW only : will work only of stock based custom rom.
I think the latest for note as per the cm kernel is 6.0.4.5.
nokiamodeln91 said:
CM only : kernel will only work on cm roms.
TW only : will work only of stock based custom rom.
I think the latest for note as per the cm kernel is 6.0.4.5.
Click to expand...
Click to collapse
Ah, so TW would stand for touchwiz then, ok
Also I've found an update but its not sticking when i flash it. Everytime i reboot, it reverts to an old version...
You cannot flash recovery using rom manager. You will need to change the kernel.
Hi,
I wanted to install CM12.1 in the 1st place but when I tried to install Tangerine Kernel, I got stuck up and the screen went blank with nothing. So I went on with Williams Kernel + CM11 stable version just to be sure that I don't brick my phone permanently.
I have been browsing through the forum, trying to know which Kernel to be used for CM12.1 ? Helium has versions like L and M which confuses me !
It would be really helpful if you guys clarify my queries,
Can anyone please let me know what Kernel and its version to be used with CM12.1 which is stable for daily use ?
Also can I go with huashan's latest nightly build for CM12.1 dated 2016-04-02?
Also I have another doubt in the installation sequence. After installing a new Kernel.zip from SD card through recovery, should I go ahead and install the ROM.zip at the same time or should I reboot my phone after installing the new Kernel and enter recovery again to install the ROM ?
Please help me understand.
I have unlocked bootloader + Williams Kernel + CM11 stable version currently on my phone.
Thanks in advance.
If you are using a new nightly of cm12.1 don't use tangerine kernel because is outdated. Use helium or the stock one. For helium: M means marshmallow, that's android 6.0.1. You have to use helium L. The l stands for lollipop, Android 5.1.1.
And, if you flash the kernel and then flash the rom zip you will overwrite the kernel, so at the end you won't install anything.
The installation is in the thread but afaik you have to flash first the rom zip and then the kernel.
Sent from my A0001 using Tapatalk
How old Kernel supports new ROM ?
darjwx said:
If you are using a new nightly of cm12.1 don't use tangerine kernel because is outdated. Use helium or the stock one. For helium: M means marshmallow, that's android 6.0.1. You have to use helium L. The l stands for lollipop, Android 5.1.1.
And, if you flash the kernel and then flash the rom zip you will overwrite the kernel, so at the end you won't install anything.
The installation is in the thread but afaik you have to flash first the rom zip and then the kernel.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks @darjwx for the reply . You have mentioned that we need to flash rom.zip followed by the kernel.zip that is needed for the ROM. But how does the old kernel (Williams Kernel in my case) support the new ROM (cm12.1 in my case) ?
As per my understanding, we need a proper Kernel to run the ROM. Is it not like that ? Also ROM and Kernel shares different memory right ?
The rom zip comes with a kernel, so flashing the rom zip will install the new kernel.
Yep you can say that. But it's better to say that they are using different partitions.
Sent from my A0001 using Tapatalk
darjwx said:
The rom zip comes with a kernel, so flashing the rom zip will install the new kernel.
Yep you can say that. But it's better to say that they are using different partitions.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks bro. I'll try it.
use doomkernel
Download and use doomkernel which is compatible with your device model if its avaible for your device from xda
Want to know what kernels to be flashed over what ROMs?
(I'm new to kernals but know how to flash roms )
hashtag_harsh said:
Want to know what kernels to be flashed over what ROMs?
(I'm new to kernals but know how to flash roms )
Click to expand...
Click to collapse
Hello... Check development and original development forum for kernel threads. You can flash most of them I guess over any ROM unless specified by the OP.
Some also provide different kernels for different Android versions.
Ex: 6.x, 7.x, 7.1.x
Read the first posts of these threads or use the search function and simply download the proper version for your ROM/Android version.
Some offer some extra features, but overall you can tweak most of them as you want with a kernel manager app: kernel adiutor, Ex kernel manager, etc...
Good luck...