Related
Kernel for stock roms
Features
Overclock
UV
15 Governers
smartassV2
interactive
InterectivX
conservative
ondemand
userspace
powersave
performance
braziliawax
scary
lazy
savageszen
lagfree
minmax
Lionheart
I/O Schedulers
noop
deadline
cfq
vr
sio
XZ compression
Good battery life
very smooth and some other changes
More feachers will add soon
Download
http://www.mediafire.com/?1w6uwvk158t1a6u
For oc and changing governer and for changing I/O schedulers use noFrill app attached at end of post
BUGS
bootanimation not showing (was working with stocklight so I thought its fixed)
Credits
ketut.kumajaya
madman
an0nym0us_
skynet28
dragonn
LibiSC
and some other awesome people
SOURCES
https://github.com/nims11xda/cooper_stock_kernel
Changelog 15-8-2012
15 Governers
Added more I/O schedulers
XZ compression
reduced size of zimage
some other changes I not remember
Changelog 12/8/2012
Fix bootanimation ( work with stock light rom)
additional ram 1-2mb (now 280mb total ram because in past it was around 278mb , not too big jump but its good than nothing
tune dirty background ratio and vm dirty ratio
fix some kernel memory leak
few changes for uv
and some minor changes for future
Changelog 11/8/2012
added more frequency range
better battery drive ( thanks to dragonn and LibiSC)
uv module
thanks nims! Btw it's Features
Nims finally makes his own kernel! NICE!
Awesome!
Nimms got a kernal
Gotta try it
Anyone tried it? I am using CF-Root-S5830-v3.7-b84 on The Myth 2, any difference?
EDIT: TESTING!
EDIT 2: No bootanimation, so far stable and fast on Myth 2.
BLN?
Sent from my GT-S5830 using xda premium
No boot animation in xperiatized v12
sorry 4 my bad english
I think you've missed something.
eagleeyetom said:
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL2 since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what best for you)
- A github link
- packing your kernel and uploading
- a diff .patch files
- Credits to people in case of an already custom kernel
- Sources must be posted in first post of development.
pulser_g2 said:
The GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2).
Many of the amazing developers at XDA create custom kernels, which feature many improvements and changes over the “stock” kernels released by OEMs, including performance and stability tweaks. This is exactly what the GPL is designed to protect, by ensuring that anyone can get access to the original source code used to build the kernel. Given a suitably configured computer, it should be possible for anyone to reproduce a released kernel using the provided source code.
Recently it has come to our attention that a number of users have been neglecting to follow XDA’s GPL regulations, which amount to posting the sources for any kernel you build from source to share with others.
As a result, we would like to clarify our position on the GPL, and users’ obligations to this effect. By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL, and should highlight this in your thread with a link. (Plenty of respected and trusted sites will host the code for you free of charge, such as GitHub and BitBucket.)
By posting open sourced work on XDA, you are also ensuring that your available sources are up-to-date with the work you have released. This means that if you update your kernel to add a new feature, for example, your sources should be updated to include this change. If they are not, this means you are not complying with the GPL.
There is no provision in the GPL to withhold access to sources based on time or other conditions, so please don’t attempt this, as it will only earn yourself a formal GPL request. If you do not provide the correct, accurate, and up-to-date sources (and keep them up-to-date), you will be non-compliant with the GPL.
In order to be fully GPL compliant, your sources must:
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)
The GPL is a legally enforceable license agreement, and while it offers users freedoms to copy and redistribute code, that permission is conditional upon all changes which are released being made publicly available. If you require further advice on this matter, we suggest you review the license itself or consult a lawyer.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xarcom said:
No boot animation in xperiatized v12
sorry 4 my bad english
Click to expand...
Click to collapse
yes I not noticed that
will fix that
CallMeLewis said:
I think you've missed something.
Click to expand...
Click to collapse
may be
But you also missed
there is written choose what best for you
give credit to people incase of already custom kernel
and I did same and when I add some thing new that I not pached from others github will give sources as now not any that stuff that you like to fork from mine
but will add new stuff soon so will give as patch because i can not upload whole source tree and even samsung already uploaded that
Update
Kernel updated
nims11 said:
Kernel updated
Click to expand...
Click to collapse
hi nims
with previous kernels there was a problem with touch with overclocking !!!!!
has it been resolved ??????
drprateekluthra said:
hi nims
with previous kernels there was a problem with touch with overclocking !!!!!
has it been resolved ??????
Click to expand...
Click to collapse
yes but test and give feedback about it
Can u add inid.d support ?
Nice work BTW !
Cryss said:
Can u add inid.d support ?
Nice work BTW !
Click to expand...
Click to collapse
I assumed init.d was supported as I'm running 2.3.6 KTM and still have a2sd after flashing this kernel. Not sure how it would be working without init.d.
Is it have any lag or bug?
And is it better than batteryextend?
Thanks
Can you make one for cm7
Sent from THE Ace
Update
Kernel updated
fixed few things and added few stuff
for chagelog see 2nd post
may be new update will be next week end as will busy with my study and college
TechNoJerky said:
Can you make one for cm7
Sent from THE Ace
Click to expand...
Click to collapse
I already compiled but want to add more stuff so may be in week or so it will available
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.
@ 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.
Kick-ass kernel
Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
Branch used to compile (can be a direct link to git)
Name of the defconfig used in build
A short instruction about how to build it (not necessary, but useful)
Click to expand...
Click to collapse
@ ROM devs
if ROM uses custom boot.img, the source must be provided. If it uses kernel by someone else, the kernel thread must be linked in the OP
if the ROM contains stock kernel, source must be linked (official site can be used)
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.
Tom
XDA Senior Moderator
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.
Kick-ass kernel
Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
Branch used to compile (can be a direct link to git)
Name of the defconfig used in build
A short instruction about how to build it (not necessary, but useful)
Click to expand...
Click to collapse
@ 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 - Samsung International
This dev sub-forum is scheduled for GPL cleanup on 8th July, I.e. 7 days from the date of sticky.
I believe that is enough time for everyone to comply with this.
Threads which aren't GPL compliant will be closed down with their download links removed.
Do we need to post the whole code of the kernel?
◄Rahul4Ace► said:
Do we need to post the whole code of the kernel?
Click to expand...
Click to collapse
The whole code which is required to compile a complete, up-to-date kernel in similar build environments.
So, yeah. Whole code, not just modified chunks.
a.cid said:
The whole code which is required to compile a complete, up-to-date kernel in similar build environments.
So, yeah. Whole code, not just modified chunks.
Click to expand...
Click to collapse
Thank You For The Info, Hope The XDAians follow this.
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.
Kick-ass kernel
Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
Branch used to compile (can be a direct link to git)
Name of the defconfig used in build
A short instruction about how to build it (not necessary, but useful)
Click to expand...
Click to collapse
@ 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.
Tom
XDA Senior Moderator
With recent site wide concerns about GPL Compliance, or lack thereof, I've copied this here to help remind everyone about the importance of posting the matching source code for your kernels.
I'll leave this open for awhile in case anyone has questions about it.
thanks for a update
will help the developers as well as end-users
***Moderator Edit: Thread closed due to GPL Policy violation***
ROM features:
- debloated
- pre-rooted
- with nice wallpaper
Warning: this ROM is still in test process, if there is any bugs please report
Download ROM:
(Pan Baidu) ***Link removed by moderator***
Credits: ROM PLAYGROUND
@(EVIL RYU) Please read the GPL Policy linked in my signature. You are required to post the source your kernel was built from to be GPL compliant. Please correct this immediately.
Also, if you ported this from someone else's work, you MUST give them credit, per Rule 12 of the XDA Forum Rules.
Otherwise, if this is not your own work, you must give credit to the original developer.
If these corrections are not made within 5 days, this thread will be closed and download links will be removed.
V0latyle said:
@(EVIL RYU) Please read the GPL Policy linked in my signature. You are required to post the source your kernel was built from to be GPL compliant. Please correct this immediately.
Also, if you ported this from someone else's work, you MUST give them credit, per Rule 12 of the XDA Forum Rules.
Otherwise, if this is not your own work, you must give credit to the original developer.
If these corrections are not made within 5 days, this thread will be closed and download links will be removed.
Click to expand...
Click to collapse
hello, I have fixed the problems as you mentioned..
(EVIL RYU) said:
hello, I have fixed the problems as you mentioned..
Click to expand...
Click to collapse
Your kernel source link is not correct. Are you using the stock kernel? If this is just a modified stock ROM, you can find the stock kernel source here
Is this an Android 9 rom as you menthioned in the title? Gald to see that on Snapdragon S7e. Thanks for your work.
(EVIL RYU) said:
hello, I have fixed the problems as you mentioned..
Click to expand...
Click to collapse
As you still have not posted the correct kernel source, I have closed this thread and removed the download links.
Please be aware that your kernel source link must point to the source code for the OEM kernel if you're using the stock one, OR if you are using a custom kernel, either the source used to build that kernel or its repository. You cannot use the ROM download link as your source.
When you are ready to correct this issue, please use the Report button on your post to contact us.