Database Develop

[ALL MUST READ] XDA-Developers and the GPL

GNU General Public License, version 2​
Kernel Developers
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL​
Thank you for your attention.
wildstang83
Forum Moderator

[ALL MUST READ] XDA-Developers and the GPL

GNU General Public License, version 2​
Kernel Developers
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL​
Thank you for your attention.
wildstang83
Forum Moderator

[ALL MUST READ] XDA-Developers and the GPL

GNU General Public License, version 2​
Kernel Developers
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL​
Thank you for your attention.
wildstang83
Forum Moderator

source code is available

it is already published by zte:
https://opensource.ztedevices.com/

Activate

kernel for realme3pro lineage os based rom

This is initial build of kernel where it provides lasted upstream of caf kernel source 4.9.x
It also start importing the latest source kernel source files from realmeQ ( thanks for giving us realmeme )
It also provides feature see in telegram group for more info
Feature:
Compile with clang-10
Lastest Caf upstream 4.9.218
Added Camera driver from realmeQ
This is not supported for realmeui and Rui based rom users
Many more coming
Bugs:
Didn't find any
If u do report with log
Telegram Group : https://t.me/realme3pros
Contact me : @SauravDharwadkar
GitHub: https://github.com/SauravDharwadkar/android_kernel_realme_sdm710/
Download link : https://bit.ly/39zrww8
Md5sum(security) : 1a7d4e7b39afde835b675d31cf6e52f7

Well done
Great keep it under