XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have a strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU 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)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Android exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under XDA rules.
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacturer has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommended, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately, this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
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. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
A lot of times new members come in or even older members; and they get directed to the gerrit code site for most cm10/aokp roms. Now a lot of people dont know how to read them and what all that info means. So ill break it down for everyone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ID: The number used for categorizing, not important
Subject: What was changed
Owner: Who submitted the change
Project: Where in the rom the change is located
Branch: Self explanatory
Updated: When it was merged to the rom
V: Its been verified to be merged
R: It has been reviewd before it was merged
Now the subject has a basic explanation of what was changed. Click on the subject and it brings you to a new screen like this:
As you can see in the top right it tells you exactly what has changed for the user.
Ex: Add lockscreen rotation as an optional rotation setting (2/2)
This will allow the user to select wether or not to use the
rotation settings for the lockscreen. This is dependent
upon the rotation setting being checked.
Thats basically all you need to know, and i hope you have succesfully learned to read your changelogs now
CM10 Gerrit:http://review.cyanogenmod.com/#/q/status:merged+branch:jellybean,n,z
AOKP Gerrit: http://gerrit.sudoservers.com/#/q/status:merged,n,z
AOSP gerrit: https://android-review.googlesource.com/#/q/status:merged,n,z
HELP
krazeecracker said:
A lot of times new members come in or even older members; and they get directed to the gerrit code site for most cm10/aokp roms. Now a lot of people dont know how to read them and what all that info means. So ill break it down for everyone.
ID: The number used for categorizing, not important
Subject: What was changed
Owner: Who submitted the change
Project: Where in the rom the change is located
Branch: Self explanatory
Updated: When it was merged to the rom
V: Its been verified to be merged
R: It has been reviewd before it was merged
Now the subject has a basic explanation of what was changed. Click on the subject and it brings you to a new screen like this:
As you can see in the top right it tells you exactly what has changed for the user.
Ex: Add lockscreen rotation as an optional rotation setting (2/2)
This will allow the user to select wether or not to use the
rotation settings for the lockscreen. This is dependent
upon the rotation setting being checked.
Thats basically all you need to know, and i hope you have succesfully learned to read your changelogs now
CM10 Gerrit:http://review.cyanogenmod.com/#/q/status:merged+branch:jellybean,n,z
AOKP Gerrit: http://gerrit.sudoservers.com/#/q/status:merged,n,z
AOSP gerrit: https://android-review.googlesource.com/#/q/status:merged,n,z
Click to expand...
Click to collapse
Ok but when I download a commit to try on my source built cm rom which download would I choose? I mean I clcik the commit and then go down to download but which line do i use? Do I use checkout , pull , cherrypick? I want to test a commit in my own build that I am building from source can you please help me with this ? I can't find an answer ANYWHERE!
XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Tizen operating system are licensed. The majority of Tizen is licensed under the Apache license, but the Linux Kernel (which is present in every running Tizen ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Tizen exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL complaint is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL complaint under XDA rules.
1. If you are using a stock kernel you MUST have a link leading to where the manufacture has uploaded their source.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL complaint.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
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. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download: http://fitsnugly.euroskank.com/?rom=cm11&device=m8
Cherry pick list
* CyanogenMod's latest merges: http://review.cyanogenmod.org/#/q/status:merged+branch:cm-11.0,n,z
* CyanogenMod's Github: http://github.com/cyanogenmod
This is a kang of CM11 with cherry picks from CyanogenMod’s Gerrit Instance, compiled by a group of volunteers that enjoy learning about building CyanogenMod & Android in general. All credit goes to cyanogen, #teamdouche and the coders who submit to Gerrit. Thank you to @RyanMacG for providing Euroskank hosting.
These builds are bleeding-edge, most comparable to a nightly build, and are not meant for inexperienced users. Things will be broken and crash from time to time, you need to accept that this isn't stable by any means before flashing. Nandroid as often as possible.
How to post useful, informative bug reports:
Sometimes dev's actually check out our threads, or sometimes we have a good relationship with a dev or two. These bleeding-edge builds will have issues, and having good information on what's broken is great feedback before a feature is merged. Here are some good bug reporting tips:
* No bug reports while using custom kernels or add-ons:
CyangenMod's own bug reporting tool does not accept bug reports from people using non-stock kernels for a reason, so why should we? CM can merge changes to their kernel causing custom kernels to break things until they catch up. Therefore, please do not post any bug reports while using a custom kernel or add-on such as Xposed Framework. Post your issues with custom kernels in their own respective threads as they are the ones who need to play catch up. Any bug report posted in this thread should be while running CM's stock framework and kernel, as this prevents unnecessary clutter.
* Gapps are not a CM issue:
CyanogenMod is built to run without the assistance of Google's proprietary apps (gapps). Having issues with your Google account and syncing is a gapps issue, not a CM issue. Please do not post about any gapps related issues, just wipe data and try a different gapps package.
* Posting about the same bug every build:
Beating a dead horse with "bug X still isn't fixed" posts just adds unnecessary clutter and provides no help into actually fixing the issue. Some bugs take days to squash, some take weeks. Please don't report the same bug every time a build is uploaded.
* Logs:
Provide logcats when applicable. Use a service like Pastebin and put a link to the log in the post. Please do not post logs directly to the forum.
If these requests are too demanding, there's good news! CyanogenMod is open source, so please feel free to download the source code, compile your own builds volunteering your time and resources, then start a thread and run it however you see fit. All we simply ask is that people post good, reliable information that can be passed on to a developer that can actually do something with it, making CM a better product for everyone involved.
CM10/11 Lockscreen Shortcut Icon Pack: CM11_Lockscreen_Icons-20140224.apk
(Credit to Danesh & blunden for source/drawables)
CM10/11 Dark Mms Theme: DarkHoloMms-ThemeChooser.apk
(Credit to djdarkknight96)
ROMManager -----
GooManager -----
KitKang RSS Feed
Glad to see you have M8 kangs too!
Speaker phone
by any chance has CM fixed the Speaker Phone issue? I would love to give this a whirl, but enjoy my speaker phone
Nice. I see that there is support for the dot view case... will there be support for the depth camera in a future release?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Love the SKANK!!!!!!!
XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU 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)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Android exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under XDA rules.
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacture has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
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. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is CarbonRom
About Us:
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Feel Free to look, build, and use our code
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on Disclaimer
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support
We spend We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
[URL='https://t.me/CarbonROM']TELEGRAM
Homepage
GitHub
KernelSource
Credits & Thanks:
CarbonROM Team:
Sohamson
LovepreetSinghgill
Sources
Kernel Source
ROM Source
Donations
PayPal
ROM OS Version: 10(Q)
Version Information
Status: Stable
Created 2020-12-3
Last Updated 2020-12-2
this rom have Gapps?
How's it ?
Smoothness ? BB ?
Is it oldcam or new cam ?
Gcams working ?
I used old carbon official till it was dropped.
Was one if the fastest roms ive tried so far.
Luved it
matthias1976 said:
How's it ?
Smoothness ? BB ?
Is it oldcam or new cam ?
Gcams working ?
I used old carbon official till it was dropped.
Was one if the fastest roms ive tried so far.
Luved it
Click to expand...
Click to collapse
It's is smooth and have good bb
It's old cam
Gcam have issue in night light mode but it will be fixed soon
m.ZePia said:
this rom have Gapps?
Click to expand...
Click to collapse
No