hi all
in this Topic i am making android 4.0.4
Part of the ROM files tigrouzen
DOWNLOADS
ROM
MOD EDIT: Link removed.
kernel
nand
MOD EDIT: Link removed.
sd
soon ...
patches
wifi &bt wave 2
MOD EDIT: Link removed.
gapps for this rom
http://www.mediafire.com/download/zfe72bjtnsjt787/google_for_nimaics.zip
features
. ROM: 66mg
. stable
. very smooth and fast
. Excellent battery
. odexed rom
. add file & code for Optimization
. zipaling
. Base rom: slim
. change or deleted app
. Enhanced sound quality
. Space, RAM: 160mg
. other ...
Installation
Bada 2.0 is required
copy rom.zip &kernel (zImage) to memory
flashed boot & fota
for s8500
MOD EDIT: Link removed.
for s8530
MOD EDIT: Link removed.
Reboot the phone holding Power and home
CWM Recovery starts, pick:
go to
install zip/choose zip from from storage/sdcard/rom name.zip/yes
after installed reboot and startup android
THANKS TO
thanks for files & kernel [tigrouzen]
volk204
Rebellos
blue59
alberto96
and other Badadroid devs
reserved
Kernel sources?
volk204 said:
Kernel sources?
Click to expand...
Click to collapse
kernel for tigrouzen (iczenrom)
i just make rom
nima.yavari said:
kernel for tigrouzen (iczenrom)
i just make rom
Click to expand...
Click to collapse
no kernel sources - no ROM here
volk204 said:
no kernel sources - no ROM here
Click to expand...
Click to collapse
why?
So what do I do?
nima.yavari said:
why?
So what do I do?
Click to expand...
Click to collapse
Kernel development is covered under the GNU GPL v2 license. This means that all necessary information should be available to every person interesting in compiling a kernel, including the source, information about the toolchain, etc.
Violating the GPL license means that kernel is technically illegal, and therefore can't be shared. As far as XDA is concerned, it's considered warez, and as such, discussions of this ROM/kernel aren't allowed
from: http://forum.xda-developers.com/showpost.php?p=46855920&postcount=780
volk204 said:
Kernel development is covered under the GNU GPL v2 license. This means that all necessary information should be available to every person interesting in compiling a kernel, including the source, information about the toolchain, etc.
Violating the GPL license means that kernel is technically illegal, and therefore can't be shared. As far as XDA is concerned, it's considered warez, and as such, discussions of this ROM/kernel aren't allowed
from: http://forum.xda-developers.com/showpost.php?p=46855920&postcount=780
Click to expand...
Click to collapse
ok
i can't put just rom?
no kernel to this topic
You are still don't know, Why Tigrouzen isn't here
thnks
cfernr said:
how to perform nand install?
Click to expand...
Click to collapse
read post 1 Installation
nima.yavari said:
read post 1 Installation
Click to expand...
Click to collapse
why not nand 4.4.3?
cfernr said:
why not nand 4.4.3?
Click to expand...
Click to collapse
kernel tigrouzen erorr fc com.phone
need new kernel for 4.4.3
Awesome work bro!
Keep up the good work and make even more ROMs.
is GPS working on this rom?
cfernr said:
is GPS working on this rom?
Click to expand...
Click to collapse
yes
nima.yavari said:
yes
Click to expand...
Click to collapse
i cant have gps working? any app or something to fix it?
imho this is the best rom ever for the wave
The GPLv2 requires you to share the source code if you've modified anything in the kernel. This is not optional, you are obliged to do so. Non GPL compliant works simply do not belong on XDA (please report any you encounter).
OP, you may PM me once you're ready to upload the full, working sources.
You can review the forum rules here and read more about the GPL here and here. Thread closed.
Related
Credits to: Raven for his FM code, cyanogen, wesgarner
Here is my kernel - 2.6.35-rcx AOSP sourced
Inside the zip you will find the zImage you need to fastboot flash as well as all the modules you would need, including the needed bcm4329.ko for wifi.
Whats in Store:
- HAVS
- FM radio support
- Undervolted
- OC capable
Here is Kernel #2 - 2.6.35-rc5 no FM support but Bluetooth takes its place.
What's in Store:
- Fresh source code from aosp as of 8/9/10
- Bluetooth
- HAVS as of #2
- Updated wifi module
- Many other things
Enjoy!
http://kingxklick.com
possible changelog
What exactly does it feature?
(sorry, I'm new to your kernels...I only use Wildmonks.....well except right now I'm using the 720p mod which of course is its own kernel)
uoY_redruM said:
What exactly does it feature?
(sorry, I'm new to your kernels...I only use Wildmonks.....well except right now I'm using the 720p mod which of course is its own kernel)
Click to expand...
Click to collapse
simple, fast, cfs, 1.2ghz capable (this version may not be 1.2 capable) and a bunch of other stuff!
kingklick said:
simple, fast, cfs, 1.2ghz capable (this version may not be 1.2 capable) and a bunch of other stuff!
Click to expand...
Click to collapse
Wooo! Sounds like something I'd like.
Have you integrated the 720p yet?
kingklick said:
simple, fast, cfs, 1.2ghz capable (this version may not be 1.2 capable) and a bunch of other stuff!
Click to expand...
Click to collapse
is it undervolted? does it have FM radio support or 720p, and which ROMs is it compatible with?
compatible with any ROM
- FM support
- Undervolted
updated op guys
Nice but no 720p support?
I assume if FM is enabled Bluetooth is broken?
bewA said:
I assume if FM is enabled Bluetooth is broken?
Click to expand...
Click to collapse
have not tested bluetooth on a vanilla rom, let me know
Nice! When is HAVS kernel coming out? (or when can I test it?)
kingklick said:
have not tested bluetooth on a vanilla rom, let me know
Click to expand...
Click to collapse
how come it aborted installation when i was flashing it? using Devil D: rom
hi king.
this is what i would like to see:
source code or references to where source(s) is/are from?
what was modified?
what differentiates this from the other kernel posts in this section?
thanks.
-pershoot
I heard that this includes a keylogger that is sent back to you. Please tell me this isn't true and provide proof that you don't do this. thank you
pershoot said:
hi king.
this is what i would like to see:
source code or references to where source(s) is/are from?
what was modified?
what differentiates this from the other kernel posts in this section?
thanks.
-pershoot
Click to expand...
Click to collapse
http://github.com/kingklick
nopenope said:
I heard that this includes a keylogger that is sent back to you. Please tell me this isn't true and provide proof that you don't do this. thank you
Click to expand...
Click to collapse
...........................
are you serious?
Sorry but you adding a keylogger to take not only I but others information for your own gain for phones and such is no joke.
nopenope said:
Sorry but you adding a keylogger to take not only I but others information for your own gain for phones and such is no joke.
Click to expand...
Click to collapse
hmn... he doesnt have to proove anything..if u have doubts dont use it..bottom line.
rotastrain said:
hmn... he doesnt have to proove anything..if u have doubts dont use it..bottom line.
Click to expand...
Click to collapse
this has nothing to do with me wanting to or not wanting to use "his" work which I'll never do has to do with legally is if indeed he is putting that in "his work" and if he is what legal issues can arise from doing so from the users that stupidly use "his work"
I am not responsible if i brick your phone
this is flashable stock kernel for 6.2.A.1.100 only
DOWNLOAD : MOD EDIT FOR NON-GPLv2 COMPLIANCE
MD5check: 2EC8BB7901EFB81322861321FFAA6BAF
INSTRUCTIONS
1.Copy flashable zip to you mobile
2.Flash zip using CWM recovery.
3.clear cache and dalvik cache
enjoy
Report if any error..!!
do you need to wipe ur data
Sent from my LT22i using Tapatalk 4 Beta
No
Sent from my LT22i using xda app-developers app
tupanceski said:
do you need to wipe ur data
Sent from my LT22i using Tapatalk 4 Beta
Click to expand...
Click to collapse
its not necesary but if something bugging you then you can
This thread is closed until the OP @garvitdelhi complies with the GPL.
How to comply.....
a.cid said:
Dear kernel and ROM developers.
According to GPL v2 license, under which kernels are released, kernels must be released with source code provided.
To be fully compliant, the thread must contain in the OP:
@ kernel devs
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released
Example.
@ ROM devs
If ROM uses custom boot.img, the source must be uploaded by you.
If it uses kernel by someone else, the kernel thread (and source link provided in main thread) must be linked in the OP.
If the ROM contains stock kernel, it must be mentioned. Source isn't required.
If you can not do any of the above, release your rom without a boot.img in the flashable zip.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal
Violation of GPL is in fact a breaking of the law, so I don't have to explain what could be a final of this.
More information can be found in the news written by pulser_g2.
Thank you for your attention.
Moderator Team
Click to expand...
Click to collapse
Please PM me with the Kernel source code link, so it can be reviewed.
Once the link is approved the thread will be re-opened
Project Unity
** For Google Nexus 5 **
Development Release Notes...
Thread CLOSED. Builds are all broken, no updates EVER. No chance of being fixed.
A. you HAVE TO link your source, legally and according to xda rules.
B. this is not an original rom, and does not go into the n5 original development section. this is cm, not your own personal development.
C. you dont even thank the people who develop the rom, very disrespectful.
D. and there is a legal reason why gapps arent included in custom roms, lkegally you are not allowed to include them if you are distributing your rom. which is what you are doing. for personal use, its allowed, but when you are sharing your rom with the gapps, that is against the law since you do not have a license.
simms22 said:
A. you HAVE TO link your source, legally and according to xda rules.
B. this is not an original rom, and does not go into the n5 original development section. this is cm, not your own personal development.
C. you dont even thank the people who develop the rom, very disrespectful.
D. and there is a legal reason why gapps arent included in custom roms, lkegally you are not allowed to include them if you are distributing your rom. which is what you are doing. for personal use, its allowed, but when you are sharing your rom with the gapps, that is against the law since you do not have a license.
Click to expand...
Click to collapse
ok well i did not know that and i do credit in the rom bu whatever. I will fix the issue.
And the aroma i have spent a ton of time on so thats my part of it. but it's fine. I can take gapps out. no problem...
LiquidSmokeX64 said:
ok well i did not know that and i do credit in the rom bu whatever. I will fix the issue.
And the aroma i have spent a ton of time on so thats my part of it. but it's fine. I can take gapps out. no problem...
Click to expand...
Click to collapse
a cm based rom doesnt belong in original dev, its cm, no matter what you did to it. you using a different developed rom is still not your work, it belongs in n5 android development. and credit needs to go in the op as well, not just in the rom. in the rom itself, credit isnt even needed.
LiquidSmokeX64 said:
(Current Release) : On hold while I correct legal issues...
Click to expand...
Click to collapse
That's interesting.
Yeah this thread will be closed and links will be removed. Sorry dude. You have to exclude gapps for a starter.
Good luck. Cheers ?
Gapps aren't included for the same reason with CM because Google told them to take it out. And unless code optimizations come from you it is essentially a kanging of someone else's work...which is fine when you give credit. But make sure you respect everyone, and the GPL. If the kernel is custom (not the one included with CM), make sure to include a link in OP to kernel on git with your sources and commits.
I have removed Gapps ok. My bad. I got it figured out, switched toolchains, and some other cleanup. Now this is totally legit I think
I will have the new ROM uploaded sometime tomorrow with a separated Aroma Gapps. If I can still at least do that.
LiquidSmokeX64 said:
I will have the new ROM uploaded sometime tomorrow with a separated Aroma Gapps. If I can still at least do that.
Click to expand...
Click to collapse
So...how the things are going on here???
i was informed by an xda mod gapps can be included
There is nothing wrong with including gapps..it is only the official CM team that got a C&D from Google...it is not enforced by XDA anyway.
Click to expand...
Click to collapse
Anyone know anything about Linaro? I could sure use some help to get it to do kernel optimizations and stuff. Just have had no luck in my attempts.
Dr.Pagan said:
So...how the things are going on here???
Click to expand...
Click to collapse
Up and running now lol
Screenshots please
Bigby2727 said:
Screenshots please
Click to expand...
Click to collapse
why? its CM/AOSP look
Downloading now.....
Not see AROMA installer ROM here as much as Sammy Android Phone. :silly:
( Samsung AROMA installer ROMs are much larger size 1.2 GB - 2 GB )
--------------------------------------------------------------------------------------------
Stuck at "Google" Logo after 1st reboot AROMA finished .....
or I am doing something wrong .
ps000000 said:
Downloading now.....
Not see AROMA installer ROM here as much as Sammy Android Phone. :silly:
( Samsung AROMA installer ROMs are much larger size 1.2 GB - 2 GB )
--------------------------------------------------------------------------------------------
Stuck at "Google" Logo after 1st reboot AROMA finished .....
or I am doing something wrong .
Click to expand...
Click to collapse
I'm Not sure... First Reboot? Did you flash gapps? Dirty or Clean? I need more details to attempt to fix the issue. I'd like a recovery log, and the Aroma log as well, That way I have everything I need to get this corrected ASAP
ps000000 said:
Downloading now.....
Not see AROMA installer ROM here as much as Sammy Android Phone. :silly:
( Samsung AROMA installer ROMs are much larger size 1.2 GB - 2 GB )
--------------------------------------------------------------------------------------------
Stuck at "Google" Logo after 1st reboot AROMA finished .....
or I am doing something wrong .
Click to expand...
Click to collapse
It seems i had horrible luck uploading that day. I've had to reupload everything for every other ROM so I will jus re upload this one too
I do clean install with AROMA without gapps ...
Stuck at Google logo with unlocked key at the bottom. :silly:
I'm not sure, I might be missing something. I think I need to find the vendor files or something
Hi,
Just saw a commit at CM..cant seem to post a link, which adds Wiimote support natively in cm, but needs a kernel compiled with CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
URL review . cyanogenmod . org / # / c / 63293 /
Strictly speaking the above commit is for cm11, but i assume it would also work for cm12..
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the kernel thread itself I'm asking here:
Could anyone help please?
muximus said:
Hi,
Just saw a commit at CM..cant seem to post a link, which adds Wiimote support natively in cm, but needs a kernel compiled with CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
URL review . cyanogenmod . org / # / c / 63293 /
Strictly speaking the above commit is for cm11, but i assume it would also work for cm12..
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the kernel thread itself I'm asking here:
Could anyone help please?
Click to expand...
Click to collapse
Will add it.
muximus said:
Hi,
Just saw a commit at CM..cant seem to post a link, which adds Wiimote support natively in cm, but needs a kernel compiled with CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
URL review . cyanogenmod . org / # / c / 63293 /
Strictly speaking the above commit is for cm11, but i assume it would also work for cm12..
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the kernel thread itself I'm asking here:
Could anyone help please?
Click to expand...
Click to collapse
i will upload it for you as soon as i get a compiled kernel with recovery working. but right now kernel boots but recovery wont start and i dont understand why.
so may take 2 weeks...
also made a feature request for you here:
http://forum.xda-developers.com/devdb/project/?id=6484#featureRequests
Deutschland uber allez!
MusterMaxMueller said:
i will upload it for you as soon as i get a compiled kernel with recovery working. but right now kernel boots but recovery wont start and i dont understand why.
so may take 2 weeks...
also made a feature request for you here:
http://forum.xda-developers.com/devdb/project/?id=6484#featureRequests
Click to expand...
Click to collapse
Pl. help me with this Q:
It seems cm12 has not merged this commit yet.. but I could still flash a newer kernel meant for cm12 on a cm11 rom...... right? Thats the way it works on linux...
muximus said:
Pl. help me with this Q:
It seems cm12 has not merged this commit yet.. but I could still flash a newer kernel meant for cm12 on a cm11 rom...... right? Thats the way it works on linux...
Click to expand...
Click to collapse
im no kernel dev but i dont think it will work that way on android. mainly because of firmware blobs and selinux but im not sure.
wiimote support wont work
http://forum.xda-developers.com/showpost.php?p=58820839&postcount=203
MusterMaxMueller said:
im no kernel dev but i dont think it will work that way on android. mainly because of firmware blobs and selinux but im not sure.
wiimote support wont work
http://forum.xda-developers.com/showpost.php?p=58820839&postcount=203
Click to expand...
Click to collapse
I made the request to Mathias, who merged the patch in the cm11 branch.. Keeping fingers crossed that it gets merged soon!
Now patch uploaded for cm12 branch as well!
See the url here: http://review.cyanogenmod.org/#/c/89843/
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.