★ ★ ★ [Announcement] Read 1st! Android Development Section Rules ★ ★ ★ NEW SECTION!!!
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
- 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
Hello fellow XDA users
I have an honor to announce that since 26.07.2012 Development Forum has been divided into two parts.
Android Development
Original Android Development
Android Development Section Rules
svetius said:
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
Your own “unofficial” stock build of your favorite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
Click to expand...
Click to collapse
To avoid future questions about XDA app/Tapatalk and missing section.
Do the following:
1. Unsubscribe your favorite forum.
2. Exit the app.
3. Clear the app cache.
4. Open app and subscribe forum once more
Enjoy!
Greeting Developers :angel:,
I am new to this ROM building/porting process.
I want to install Vanilla Android on my note-4, so after questioning Google number of times, I came across official Android development guide on official Android website: https://source.android.com/source/downloading.html
I have downloaded the Android source locally and was following various Guides and tutorials from XDA-University & forums only for the development process. http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
I discovered that for downloading/configuring the build for a specific device(trltexx), we need to create a localmanifest file that contains device tree, vendor and kernel configuration links for repo syncing.
Now, I want your expertise to guide me forward from this point. Questions being:
1. Can I use CM or other projects (eg. AICP etc.) device configurations for this AOSP project.
2. Can I use these configurations for cross-version android build, say if I want to compile version 6.x, can 5.x configs can be used. (Manufacturer will take several months to release version update)
or Create new configurations using some guide/tutorial/book or something.
In XDA, I know I'm at the write place posting my questions and asking for expertised help.:good:
Thanks!!
Hi,
I am opening this thread to start a discussion about LineageOS and the recently announced Project Mainline to put together a Q&A list (I will summarize the interesting questions and answers in this first post).
1. In general: will Project Mainline still work when you switch from your manufacturers stock ROM to LineageOS..? Or may there some restrictions for non-official ROMs through the Play Store?
2. Will LineageOS be able to support Project Mainline for devices that support Project Mainline in their stock ROM?
3. Will LineageOS be able to support Project Mainline for older devices? Or do old Linux kernels prevent this? Are kernel refreshs for old devices even technically feasible or is it far too much effort and too buggy in most cases?
4. These are the 14 components Project Mainline is able to update via the Play Store:
• Security: Media Codecs, Media Framework Components, DNS Resolver, Conscrypt
• Privacy: Documents UI, Permission Controller, ExtServices
• Consistency: Timezone data, ANGLE (developers opt-in), Module Metadata, Networking components, Captive Portal Login, Network Permission Configuration
I assume this doesn't cover all "components" in Android, or does it? What parts are left out and why - does anybody know?
Cheers,
carsten
OpenSource Code Distribution
Does this help anyone with custom rom development / bootloaders / rooting?
I feel like this device still has a fairly large userbase, and would benefit from some new life.
Hello,
For those interested in the original kernel source code for the SM-T813 :
As I am learning how to make ports for Android, I am trying to train on the original sources of the Linux kernel for the SM-T813.
After several weeks of research, I couldn't find the origin of the different kernel repositories.
Also on https://opensource.samsung.com, it was impossible to find the sources. So I contact them at the end of January to have an access to this sources...
... And they are now available !
You can download them on https://opensource.samsung.com (search SM-T813 at mobile phone on release center) or on my repository at https://github.com/Akipe/android_kernel_samsung_gts210vewifi_original_samsung
It is based on the T813XXS2BTK3 firmware with Android 7 Nougat.
I will see to ask for sources of similar tablets.
Will this help with porting new Adnoid version to these tablets?
Pawel_ said:
Will this help with porting new Adnoid version to these tablets?
Click to expand...
Click to collapse
I don't think so,
Kernel sources for this tablet already exist, and are ported to newer versions.
It is more useful for those who want start from scratch, and want to inspect the unmodified source code.
But my goal would be to successfully create from scratch for the SM-T813 LineageOS 14.1 (Android 7); and then try to move to the latest versions.
Since I am a beginner, I still have a lot to learn, and I don't have much time, so we will see