Links from different source codes. leeco - LeEco Le Pro3 Guides, News, & Discussion

Hello everyone.
Not being developer and wishing one day a ROM CM.
The site LeEco.re to reference the source codes of different smartphones leeco.
For those who want to develop.
here is the link.
http://www.letv.re/topic/1903-source-code/

Related

[Q] Best way to advertise custom forks of a kernel

I am developing some enhancements against another Linux Kernel that is already on the forums. The Kernel itself doesn't seem to have a dedicated thread as it's normally distributed as part of a specific ROM. I believe most of my enhancements would be useful to other users of this ROM, but I am having difficulty getting in touch with the developer. I'm not interested in maintaining a complete fork with my own branding and name, but if I publish anything without the developers consent I would like to make it somewhat obvious that it's not the official kernel by the developer. I'm not sure the best way to advertise it though. I could create a new thread for the kernel in the same forum as the ROM and mention in the title it's a fork of the Ursa Minor kernel, or I could just post my update.zip for the kernel in the Andromeda3 thread which is the ROM it goes with. Should I first post a question on their thread about their wishes?
Since I tend to use North Winds as my organization, I've been prefixing nw1 onto version strings where appropriate, but keeping the branding as Ursa Minor in general since it's still 95% the same.
I'm not 100% sure of what your asking? You want to branch off a current developers kernel with your own modifications?
have you tried PMing the dev to ask if they're ok with it?
Basically, I'm curious what the best way to be respectful and publish my enhanced version of his kernel. I have sent the developer several PMs, but the last response I got was on the 13th when I was having trouble building his kernel. Three days later I published my first enhancement in source code form on github.com and sent another PM to the dev. Now I've added several more enhancements and I'd like to publish it, but I haven't seen any response from the dev since my help request on the 13th.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well it appears that since kernels are covered under the GPL, you are free to publish your work as long as you credit the original developer in your post. So feel free to post a new thread with your work
Hope that helps

Is there any for Developer interested in making CopperheadOS port for the Oneplus 3?

This thread is for discussions related to the topic.
CopperheadOS is an Android OS with focus on security. You can find more Info about CopperheadOS on their website.
https://copperhead.co/android/
I hope there are some developers or people who are interested in this.
I'm not a developer but I do support this! I'd be willing to learn about building from source and seeing if it were possible though. Gotta start somewhere ! 😉
Sent from my Pixel using Tapatalk

no devs

hi,
what's up?! no new developing for our E5?
Lots of people develop for out phone, hence the LineageOS and different resurrection remixes posted here.

I am a Chinese Developer about MIUI9

Hell foreign friends,
I am the original author of Nubia Z17's MIUI9.
I found someone stealing my ROM ,MIUI9.I was very angry.
Please stop your infringement!!!
曦颜XY said:
Hell foreign friends,
I am the original author of Nubia Z17's MIUI9.
I found someone stealing my ROM ,MIUI9.I was very angry.
Please stop your infringement!!!
Click to expand...
Click to collapse
I'm not quite sure stealing is the right word for it. He has ported it for international use. Furthermore he has quoted your work in his initial post. Maybe you two could figure something out and work together, since everybody likes your miui 9 port so much. It would be a shame to have miui 9 not ready for international use.
曦颜XY said:
Hell foreign friends,
I am the original author of Nubia Z17's MIUI9.
I found someone stealing my ROM ,MIUI9.I was very angry.
Please stop your infringement!!!
Click to expand...
Click to collapse
You need to read the Forum Rules. XDA is about sharing open source projects...
Rule 12:
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!
Thread closed and moved.

Development ***CLOSED*** [RECOVERY] PitchBlack Recovery A52s 5G

**Moderator Edit**
Projects that fail to provide proper credit where due will be removed.
See the Forum Rules:
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Developer Relations Team (DRT) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team or a Moderator (see here). We are here to help!
Click to expand...
Click to collapse
Good job, please add proper credits in OP (you're clearly using mine/@Ryzen5950XT TWRP/OFOX device tree as base) and a link to your device tree source code.
BlackMesa123 said:
Good job, please add proper credits in OP (you're clearly using mine/@Ryzen5950XT TWRP/OFOX device tree as base) and a link to your device tree source code.
Click to expand...
Click to collapse
Sry I'm tryna fix da flashlight n gonna upload it 2 da tree later wit my own branch. Gonna give creds but for now plz hlp me out. Thx!
Hello @ArixCute
Please be aware that if you used anyone else's code to build this project, you must provide all due credit per the Forum Rules:
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Developer Relations Team (DRT) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
Click to expand...
Click to collapse
If we establish that you have kanged someone else's work without giving credit, we may at our discretion remove your projects from XDA.
@ArixCute
As you have failed to provide proper credit to @BlackMesa123 for the source, this thread has been closed, and the download links have been removed.
See PM.

Categories

Resources