I tried compile kernel for XRN3 Mtk
And terminal displayed this
make: *** No rule to make target '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/codegen.dws', needed by '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/inc/cust_kpd.h'. Stop.
I disabled needed line in defconfig, but it still not compiling
Sorry for my bad English
What can i do with that error?
Skrem339 said:
I tried compile kernel for XRN3 Mtk
And terminal displayed this
make: *** No rule to make target '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/codegen.dws', needed by '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/inc/cust_kpd.h'. Stop.
I disabled needed line in defconfig, but it still not compiling
Sorry for my bad English
What can i do with that error?
Click to expand...
Click to collapse
check if this file already exicst in ur kernel source or not
messi2050 said:
check if this file already exicst in ur kernel source or not
Click to expand...
Click to collapse
I am also facing the same error
can you explain the solution.
kalwardin said:
I am also facing the same error
can you explain the solution.
Click to expand...
Click to collapse
Which device are you compiling for and can you link the kernel source
messi2050 said:
Which device are you compiling for and can you link the kernel source
Click to expand...
Click to collapse
Lenovo Tab 2 A7 10 F
and the kernel source is https://github.com/KalWardinX/kernel_lenovo_tab2a710f
I m trying to port postmarketos but while building kernel i am getting this error:
'No rule to make target /home/pmos/ build/src/kernel_lenovo_tab2a710f-91effce241038f11 4faae5f80e19a94c810185e9/drivers/misc/mediatek/ mach//dct/dct/codegen.dws,
needed by
/home/ pmos/build/srckernel_lenovo_tab2a710f-91effce2410 38f114faae5f80e19a94c810185e9/out/drivers/misc/ mediatek/mach///dct/dct/inc/cust_kpd.h. Stop.
Please Help
I am stuck in this part since 5 days. :crying:
kalwardin said:
Lenovo Tab 2 A7 10 F
and the kernel source is https://github.com/KalWardinX/kernel_lenovo_tab2a710f
I m trying to port postmarketos but while building kernel i am getting this error:
'No rule to make target /home/pmos/ build/src/kernel_lenovo_tab2a710f-91effce241038f11 4faae5f80e19a94c810185e9/drivers/misc/mediatek/ mach//dct/dct/codegen.dws,
needed by
/home/ pmos/build/srckernel_lenovo_tab2a710f-91effce2410 38f114faae5f80e19a94c810185e9/out/drivers/misc/ mediatek/mach///dct/dct/inc/cust_kpd.h. Stop.
Please Help
I am stuck in this part since 5 days. :crying:
Click to expand...
Click to collapse
Well the cpu is mtk with old 3.10 kernel version, i would suggest to use a prebuilt kernel as this problem is probably related to the used toolchain to compile so if you are porting a rom with the same android version of the stock rom this will be the best solution for you, if it's a newer version you will need to upstream the kernel and apply necessary patches for the target new android version and call the correct toolchain.
messi2050 said:
Well the cpu is mtk with old 3.10 kernel version, i would suggest to use a prebuilt kernel as this problem is probably related to the used toolchain to compile so if you are porting a rom with the same android version of the stock rom this will be the best solution for you, if it's a newer version you will need to upstream the kernel and apply necessary patches for the target new android version and call the correct toolchain.
Click to expand...
Click to collapse
Thanks
I will try that
Related
Hello there,while working on OMFGB and CM6,I decided to take ICS CAF sources and build them since andy is working at AOSP,arjen is working at CM9 and now I'm working at CAF. I opened this since I can handle various projects at a time,infact I'm developing for other stuff also.
Current status: Fixing build errors
All d best little genius..
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Good luck bro!
OT: Mind I ask u why u changed ur name?
Sent from my LG-P500 using xda premium
andy572 said:
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Click to expand...
Click to collapse
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
mentalityx said:
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
Click to expand...
Click to collapse
You're right. But now i've already created them,so for the next time.
Bytecode said:
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Click to expand...
Click to collapse
dont know, the hw specs are the same - at least the same cpu/gpu and memory.
maybe only another camera^^
Building now
sooo... any news here?
Bytecode said:
Building now
Click to expand...
Click to collapse
Ha ha little bytecode is going again
Enjoy your build procedure well be waiting
Sent from my LG-P500 using xda premium
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
edit the Android.mk and remove that lib, its proprietary **** only
SWEATTAIMI said:
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
_Arjen_ said:
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
Click to expand...
Click to collapse
I'm getting really,really confused here
Adding vendor and device folder from andy gives me libskia ****,adding all from andy gives me framework ****,I don't know what to do here
Lemme basically explain: What files are needed for building/booting CAF ICS succesfully? Don't post stuff necessary for fixing bugs later
Thank you
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Bytecode said:
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
Click to expand...
Click to collapse
AOSP is not CAF, AOSP is not CM - each framework has its own code, it
has nothing to do with my changes, as you can see in my patches, its nothing
to make it "feel me like a phoenix"
To help you a bit:
some makefile variables cant be used in CAF, CM or AOSP and vice versa,
you have to look in relevant config variables ad what its used for,
than look in the source code if the name has changed or the variable
cant be used (or what ever).
_Arjen_ said:
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Click to expand...
Click to collapse
qcom repos are very needed to compile qcom related changes like audio/media.
the title speaks.
How to port kernel???
Messi10 said:
the title speaks.
How to port kernel???
Click to expand...
Click to collapse
Recipe to port a kernel.
1 test device
1 Vendor kernel source
1 Copy of required patches to be port
1 Linux computer
Way too much time on your hands.
Power on Linux computer and add vendor source. Verify it compiles and then sprinkle in patches compiling as you cook until they have all been applied and your kernel builds. Flash to device and proceed to debug and fix errors until your kernel boots.
Viola.
thewadegeek said:
Recipe to port a kernel.
1 test device
1 Vendor kernel source
1 Copy of required patches to be port
1 Linux computer
Way too much time on your hands.
Power on Linux computer and add vendor source. Verify it compiles and then sprinkle in patches compiling as you cook until they have all been applied and your kernel builds. Flash to device and proceed to debug and fix errors until your kernel boots.
Viola.
Click to expand...
Click to collapse
is there another way without building stuffs?
Messi10 said:
is there another way without building stuffs?
Click to expand...
Click to collapse
Nope you have to compile it for your device, it's just in the nature of the kernel. Read this for more information. http://en.wikipedia.org/wiki/Kernel_(computing)
thewadegeek said:
Nope you have to compile it for your device, it's just in the nature of the kernel. Read this for more information. http://en.wikipedia.org/wiki/Kernel_(computing)
Click to expand...
Click to collapse
okay thanks for your help
Messi10 said:
okay thanks for your help
Click to expand...
Click to collapse
No problem. Thank you for being polite, and trying to learn.
I will shortly be the owner of a Samsung Galaxy Note Edge SM-N915S (Korean Exynos 5433) device and have downloaded the kernel sources and successfully compiled the zImage.
The problem is:
After compile the zImage, I think I will need a Exynos 5433 dtbTool binary to create a master dt.img for boot.img re-pack. (There is a dt.img inside the stock boot.img). I have tried the qualcomm dtbTool but it shows 0 images. Although I'm just a "hack" and don't profess to be a Dev, my build environment is setup correctly as I've built many Exynos and also Qualcomm kernels (with dt.img) in the past.,
One thing I do notice though is that 5433 is not found in SM-N915-SkyHigh-Kernel/arch/arm/boot/dts/Makefile , all Exynos are commented out. Maybe they need to be added in as well so any working dtbTool will make the dt.img ?
In my defconfig (not committed to github), I try also with
Code:
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE=y
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE_NAMES=""
If anyone [ @AndreiLux - @ketut.kumajaya - @xiaolu ] could please share a suitabe Exynos 5433 dtbTool binary or further guidance would be much appreciated.
Why would you even do this. The kernel image is a normal image as has always been AFAIK.
Not a real solution for you but some great information: https://github.com/kumajaya/android_kernel_samsung_universal5422/blob/master/README.md, https://github.com/kumajaya/android...mmit/26a6298340a2ff09fd00fad8ca53c32118a1527a, and https://github.com/kumajaya/mkdtbhbootimg
Upload the original boot.img also a good idea, I'll analysis it in my spare time.
AndreiLux said:
Why would you even do this. The kernel image is a normal image as has always been AFAIK.
Click to expand...
Click to collapse
My SM-T705 5420 kernel doesn't have a dt.img
within the stock boot.img, the SM-N915S does. As i said, Qualcomm Note 3 N9005 was similar having the dt.img and requiring it made after compiling zImage. It needed to be included with boot.img for OC functions etc to work. I was thinking the same thing for the 5433, but doesn't look like it.
ketut.kumajaya said:
Not a real solution for you but some great information: https://github.com/kumajaya/android_kernel_samsung_universal5422/blob/master/README.md, https://github.com/kumajaya/android...mmit/26a6298340a2ff09fd00fad8ca53c32118a1527a, and https://github.com/kumajaya/mkdtbhbootimg
Upload the original boot.img also a good idea, I'll analysis it in my spare time.
Click to expand...
Click to collapse
Thanks, I'll take a read tomorrow and upload the stock boot.img if needed.
I've just managed to compile a basic kernel and re-pack into stock ramdisk + dt.img using the mkbootimg_dtb binary and flashed successfully. Haven't tried yet whether it'll flash without the dt.img though.
Just wonder what's the use of it when nothing is made in kernel source?
Thanks for sparing your time guys, , appreciated.
Cheers.
UITA
deleted .......... just woke up
@AndreiLux
New something was missing............. Thanks for committing it and sharing the rest of your work.
I see some of your commits for the 5433 Makefile and more. Cheers mate !
UpInTheAir said:
@AndreiLux
New something was missing............. Thanks for committing it and sharing the rest of your work.
I see some of your commits for the 5433 Makefile and more. Cheers mate !
Click to expand...
Click to collapse
Did you test it out? I didn't actually use that DTB yet.
AndreiLux said:
Did you test it out? I didn't actually use that DTB yet.
Click to expand...
Click to collapse
Just added as you did, but adjusted for my device: exynos5433-trlte_eur_open_12.dtb. zImage compiled OK and have only briefly tested kernel repack and boot. Haven't had much more time at hand than that afraid. Can't use my source as Sammy needs to update it for newer firmware base (no wifi/data connectivity, baseband or recognise SIM etc)..............
An old dtbtool binary still didn't see it, I assume it's in-built via the Makefile (didn't check terminal log) ? But suppose to re-pack it with the boot.img though.......
UpInTheAir said:
Just added as you did, but adjusted for my device: exynos5433-trlte_eur_open_12.dtb. zImage compiled OK and have only briefly tested kernel repack and boot. Haven't had much more time at hand than that afraid. Can't use my source as Sammy needs to update it for newer firmware base (no wifi/data connectivity, baseband or recognise SIM etc)..............
An old dtbtool binary still didn't see it, I assume it's in-built via the Makefile (didn't check terminal log) ? But suppose to re-pack it with the boot.img though.......
Click to expand...
Click to collapse
https://github.com/kumajaya/mkdtbhbootimg/issues/1
I'll still have to make something to automate the extracting and packing of that process.
AndreiLux said:
https://github.com/kumajaya/mkdtbhbootimg/issues/1
I'll still have to make something to automate the extracting and packing of that process.
Click to expand...
Click to collapse
Fingers and toes crossed here. Far beyond my comprehension, but of course keen to know of more development.
Hey guys can ny 1 tell me what changes do we have to make to compile a kernel for cyanogenmod?? I know that cyanogenmod requires somekernel tweaks in the stock defconfig.. So how do we make a cyanogenmod defconfig??? What changes do we have to make in the
Code:
make menuconfig
Dialogue?
Please reply guys... Im usig a samsung galaxy star pro...
Btw i got my answer! Thanks k2wl bro! He told me to get the config.gz file from /proc partition and extract it..
Code:
adb pull /proc/config.gz
And extract the file... So a .config file will be obtained.. We have to rename it as
Code:
cyanogenmod_(device name)_defconfig
That can be used by us for compiling cm upto jb 10.2... For kitkat, u need to edit it with a linux program (make menuconfig) included in kenel source and enable selinux.. I dont know hw to do that as of now.. so compiling cm10.2 for star pro s7262
regalstreak said:
Btw i got my answer! Thanks k2wl bro! He told me to get the config.gz file from /proc partition and extract it..
Code:
adb pull /proc/config.gz
And extract the file... So a .config file will be obtained.. We have to rename it as
Code:
cyanogenmod_(device name)_defconfig
That can be used by us for compiling cm upto jb 10.2... For kitkat, u need to edit it with a linux program (make menuconfig) included in kenel source and enable selinux.. I dont know hw to do that as of now.. so compiling cm10.2 for star pro s7262
Click to expand...
Click to collapse
thanks for the info man. I would've not known about that.
twilighttony said:
thanks for the info man. I would've not known about that.
Click to expand...
Click to collapse
Lmao that was 3 years old. Now i have my own ROM (http://halogenos.org) haha
regalstreak said:
Lmao that was 3 years old. Now i have my own ROM (http://halogenos.org) haha
Click to expand...
Click to collapse
is it based on LineageOS/cm? if so i would totally build for it for my axon7.
twilighttony said:
is it based on LineageOS/cm? if so i would totally build for it for my axon7.
Click to expand...
Click to collapse
Based on CAF and some parts are from AOSP. Would love to have a dev for axon 7. We have a team member who badly needs a build for it xD
Just telegram me telegram.me/regalstreak We will discuss!
regalstreak said:
Based on CAF and some parts are from AOSP. Would love to have a dev for axon 7. We have a team member who badly needs a build for it xD
Just telegram me telegram.me/regalstreak We will discuss!
Click to expand...
Click to collapse
I had gotten a kinda working build after writing this, but I got shat on by the other team members on telegram so i left. Such elitism. We can discuss still if you want. Sorry, I've been very busy.
Hello,
This is a stock SeLinux permissive kernel and init.d activated for Samsung Galaxy Note Edge (N915F) for Lollipop 5.0.1.
There are inputs that is working also on N915FY.
The kernel was compiled from Samsung source LL_CIS kernel using Google toolcahin v4.8.
If you want to test it, please flash in cwm the attached file and report back. Please make a backup of your actual kernel (boot.img) befor flashing this one.
Special thanks to @Micky387 who advised me to update the source kernel (MH driverI), @Wuby986 for his support and guidance and @daxgirl for his advices.
My kernel source for N915F (N915FOXE1BOC6) is here.
Happy flashing.
PS. Kernel updated. Same functionality but some different info in "About".
Well you got further than I did .. Kept getting some driver file referenced so it would not complied.. Thanks for effort I hope you work it out soon.. Unfortunately I don't have time at the moment ..
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
micky387 said:
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
Click to expand...
Click to collapse
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
starbucks2010 said:
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
Click to expand...
Click to collapse
No need to flash module. The MHI module will be in the kernel so you have boot.img with all inside.
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
Wait one more day..
Or maybe earlier
Finally done.
Make backup of your actual kernel, flash the attached zip from post 1in cwm and please report back.I didn't check the init.d support but it should work.
Good, I'll try.
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Any chance that you would be willing to make this kernel compatible with the Sprint variety? Man.... I need my viper4android bro. Please. Lol
UpInTheAir said:
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Click to expand...
Click to collapse
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Well done mate ..... Yea
---------- Post added at 08:32 AM ---------- Previous post was at 07:36 AM ----------
Boot and works fine , nice one
Can this be used on N915FY as well?
I don't have any reports from N915FY users. You can try and tell us
Don't forget to make a backup first.
starbucks2010 said:
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Click to expand...
Click to collapse
Hey, no problem.
Just to clarify....
If you've made any (even minor) change to "Samsung" source, then you have to upload "your" complete source and link "your" source, not "Samsung" So if you've made the kernel permissive or even use a different toolchain or path, technically you have modified from original and is now "your" source If you use a custom defconfig, don't forget it too
github is well worth the pain I Google for answers all the time (how to do this and that), but still screw things up (sometimes majorly) now and then.
dubart said:
Can this be used on N915FY as well?
Click to expand...
Click to collapse
Using this kernel with a N915FY. Great job btw I can finally use viper audio which I've missed so much. Major props dude!
I'm gonna flash this on sprint variant either that or throw this device out my window
dinaps86 said:
I'm gonna flash this on sprint variant either that or throw this device out my window
Click to expand...
Click to collapse
Lol it booted just no data. Yaaayyy!!!
I see that there are other people who are interested in Selinux permissive kernels.
So, if you want, I can add selinux permissive to any samsung kernel as long as you provide me 2 files: your original kernel (boot.img) from the ROM you want to flash and the Kernel.tar.gz - source kernel from Samsung site. In order to get Kernel.tar.gz file you'll need to download the kernel source file (~ 1Gb) from Samsung site, open the archive and upload ONLY the Kernel.tar.gz (~ 100-150 Mb) and the readme file from the archive to some sharing site. Then, I'll try to compile that kernel for you.
There are also downsides. I cannot stay up to date will all new commits done to the kernel source so I'll compile your kernels only with info that I have at that date. If you fork the github and find kernel source updates, I can add them.
PS. I only set up a working PC with Ubuntu and Google toolchain v4.8. If you find any information that this setup is not suitable for compiling your kernel, then there is no point of providing me the above files.
Best regards.
OP updated with some Antutu screen shots.