★ ★ ★ [Announcement] Read 1st! Original Android Development Section Rules ★ ★ ★
Hello everyone.
This message is directed to all ROM/kernel developers of Ace community.
There are some rules, which you have to follow before starting new thread.
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.
Rule No.2 - If you are about to post a new Rom, you don't have to post source since they are covered by Apache, BUT you must be in compliance with XDA rule and with good sense. Remember that publishing sources is a very polite manner.
New Roms thread must contain:
- Exactly say which base rom do you used : Stock, custom from another developer, CyanogenMod.
- Permission to use said ROM as your base by the original developer(s).
- Credits given to original developer(s) in your first post: (eg: Credits and thanks for this Rom goes to XXXXX)
- Credits given, if possible, to the people from whom you grabbed scripts, themes and apps.
- Your ROM MUST BE free of paid apps, NO WAREZ ALLOWED.
- Your first post must contain as much info as you can provide, "this is my ROM" and a link is not tolerated (screens, installation procedure, CM version, kernel version etc.)
- Thread Title : " [ROM]xxxxxxxxxxx[date of release][kernel version/kernel required]
Rule No.3 - AdFly, or other ad-revenue related redirecting links, are NOT allowed. Thread will be closed and links be deleted.
In case of questions please drop me a PM.
Best regards
Tomek
Forum Moderator
Official XDA GPL statement:
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
Huawei Device Co., Ltd ("Huawei")is pleased to provide you the corresponding open source code of the device. If you want the code, please contact us with an email titled "Open Source Codes Issue" to [email protected]. Please note we may charge you the cost of physically performing source distribution like sending you a CD of the Open Source Codes, if you reqest. And the code download link will be ready soon.
Please include GSI ROM details about how you fixed bugs or patches involved to fix issues along with reasons and results of using GSI rom instead of stock OneUI
Please post successful GSI installs along with bug fixes or patches for the Samsung Galaxy M32 here :
Home
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
It took quite a while to get the source for pstar build RRA31.Q3-19-19's source code released.
The following stuffs are now available. Hope this can be useful in the future.
kernel-msm
kernel-devicetree
kernel-camera-devicetree
kernel-display-devicetree
kernel-msm-4.19-techpack-camera
kernel-msm-4.19-techpack-display
kernel-msm-4.19-techpack-video
vendor-qcom-opensource-audio-kernel
vendor-qcom-opensource-wlan-qcacld-3.0
vendor-qcom-opensource-wlan-fw-api
vendor-qcom-opensource-wlan-qca-wifi-host-cmn
For each repo, look for tag MMI-RRA31.Q3-19-19.
I will add more information - https://dumps.tadiphone.dev/dumps/m...si-user-11-RRA31.Q3-19-50-d4e962-release-keys
Hey everyone,
I've tried to make TWRP for ibiza (XT2137-1) but I failed (maybe miserably) but I tried. I am leaving a device tree as is for ibiza on my github repo. If someone wants to thinker with it and maybe create functional recovery then it's up to you. I got my self working to begin this project for debugging Phh/TD GSI as for now Android 13 PE made by Mr. Ponces won't boot on ibiza, and I wanted to extract ramoops and ksmg but stock wouldn't allow me. So I am leaving this to community, maybe one or more people will turn this to something. The second version of device.mk was auto generated by twrpdtgen script and it was defaulted to omni config, so I tried to convert it to twrp config from caprip. I'll publish shortly kernel sources for ibiza.
GitHub - theh0riz0n/android_device_motorola_ibiza: Minimal device tree for Motorola G50 5G (ibiza)
Minimal device tree for Motorola G50 5G (ibiza). Contribute to theh0riz0n/android_device_motorola_ibiza development by creating an account on GitHub.
github.com
兄弟，等你成功