{
"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"
}
Developer Decorum and Conduct
Android is open source and Google releases the code under the Apache License. This open source code and permissive licensing allows the software to be freely modified and distributed by device manufacturers, wireless carriers and enthusiast developers.
Click to expand...
Click to collapse
Full version here
Read Apache Licence here
2.) What is Open-Source?
open source refers to a program in which the source code is available to the general public for use and/or modification from its original design. Open source code is typically created as a collaborative effort in which programmers improve upon the code and share the changes within the community.
Click to expand...
Click to collapse
Read Open-Sourcing here
3.) Too many big words, what does this mean exactly?
Everytime you develop for the android-software you are bound by the GPL, Apache license and the XDA forum rules
Click to expand...
Click to collapse
See full GPL Licence here
4.) What must I do before publishing my work?
Review your work and see if it violates any of the following:
XDA Forum Rules #12
Using the Work of others
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.
Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by the dev or freely share it. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie allowing certain people to use it and not others). Should the dev decide to start sharing the work with others, the work automatically becomes fair game for all to use.
In regards to permissions, same rules remain for this but if permission was already given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under severe circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Ask permission before using other's work, no matter how small it is (a .png file or a xml code), please secure all nessesarry permits from the original author before publishing
Click to expand...
Click to collapse
Tips:-
Create your own license, disclaimer and warranty notice
Protect your work by creating your own license and publishing them together with your work, remember this is your work and you have all the right to secure it at will and on your behalf, just make sure you clearly specify your license, disclaimer and warranty.
Click to expand...
Click to collapse
Open-GPL Licence Sec. 5-6
Publishing your sources, and providing notice of modification
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
After securing the permits if in case your project is a derivative or is based upon another project, you must publish and indicate it in a conspicuous and clear place within your post or work together with it's sources,
if in case of a original work, you must indicate the sources in a conspicuous and clear place within your post or work
Click to expand...
Click to collapse
XDA Forum Rules #6
Do not post warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community
Don't Include Paid Apps versions on your work, Remember not all app developers do it for a hobby, sometimes they rely on app purchases for feed their kids, pay their bills and get their life ahead,
Click to expand...
Click to collapse
XDA Forum Rules #13
Advertising and Income Generation
Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money
Don't post your link to redirect a pay-per-click (e.g adfly, etc) website
Click to expand...
Click to collapse
Link to the XDA Forum Rules
Click to expand...
Click to collapse
5.) The original author declined my permission to use his work or he is not responding, What shall i do?
If in case the author has declined to provide permissions to secure usage of his work. then you are unable to publish it in XDA, you are however free to use it for your own device without sharing the source.
If in case author was unable to respond, PM the moderator to settle this issue and wait for a "GO" signal to publish your work.
Click to expand...
Click to collapse
6.) A person accused me of stealing his work, What should I do to defend myself?
PM the accusor to disscuss with him the matter at hand, however if you are unable to negotiate a concensus with the accusor, then PM a moderator to settle your disputesDON'T FIGHT WITHIN THE DEVELOPMENT THREAD,and wait for the moderators to finish their investigation and undergo a conclusion on the matter
Click to expand...
Click to collapse
7.) Does #4 apply to porting roms, apps, from another device?
YES.
Click to expand...
Click to collapse
special thanks to deathnotice01 for this useful thread
Click to expand...
Click to collapse
Related
This is relating to the announcement of DevDB: http://www.xda-developers.com/announcements/introducing-the-xda-devdb/
Please use this thread to report bugs, request features, and offer feedback. :highfive:
==============================================================
The main DevDB Access url is here: http://forum.xda-developers.com/devdb/
This is @bitpushr here, I'm hijacking @svetius's thread to put a bit more information and a quick FAQ on the DevDB for people.
The overall goal of DevDB is to give structure to the development projects on XDA. Most obviously this is for ROMs, but also kernels and other tools and projects that you wonderful people come up with. I've been getting a lot of PMs about DevDB so I thought I'd compile them into a little FAQ:
1. How Do I Add Projects to DevDB?
You can visit the main DevDB url, and if you have access to add a project or import an existing thread, you will see the following links:
Adding a project will allow you to enter a new project from scratch and automatically create a thread for you.
Importing an existing thread will allow you to "enhance" the thread by adding it to the DevDB database and let you add more detailed information about your project.
2. Why should I add my project to DevDB?
For developers, it adds crucial metadata to your project that will allows us to show your project in more locations on the site. Threads that are "DevDB-ized" show up in the device page ROM listings, for example. We also add some cool features like a new large-file download system, reviews, a bug reporter/feature requester, and more.
For end-users, it allows us to present the ROMs and other projects on the site in a friendlier format. Rather than scouring forums and threads for new ROMs, we want to give them a place to see these projects and the unique features each one has.
We have some other cool ideas 'in the pipeline' so we thoroughly encourage devs to add their projects to DevDB.
3. Who can add projects?
Right now Recognized Developers and some other beta users are able to add projects to the system. If you wish to be added to the best-tester list, please pm @bitpushr.
Eventually we'll open this up to all "Senior Members" after we get all of the bugs out.
This is really cool.
Thanks a lot. :good:
That's why this is my favorite forum.
Some characters aren't showing correctly in FF 22.0. They show up fine under Chromium. I'm using Linux.
The characters are located:
Just before the device's name;
Near each of the table's columns' titles;
The stars also seem hidden (didn't check if those were ASCII characters or images, tho);
There's a weird "fi" showing in the search bar. It's in black when using the normal theme, so it may be less visible than on my dark theme.
{
"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"
}
Also, the bottom bar ("Total Results: X") has white text on a white background using the default theme (on both browsers).
Awesome idea!
GermainZ said:
Some characters aren't showing correctly in FF 22.0. They show up fine under Chromium. I'm using Linux.
The characters are located:
Just before the device's name;
Near each of the table's columns' titles;
The stars also seem hidden (didn't check if those were ASCII characters or images, tho);
There's a weird "fi" showing in the search bar. It's in black when using the normal theme, so it may be less visible than on my dark theme.
Also, the bottom bar ("Total Results: X") has white text on a white background using the default theme (on both browsers).
Click to expand...
Click to collapse
that's a weird binary character. It's actually a hexadecimal representation of a character which is not present in the font you are using.
I have a few issues to address. What about tools which can be used for all devices? The CASUAL project just started a new IDE called CASCADE. It will eventually allow for users to create their own CASUALs easily via guided use of the CASUAL language. Also, there's plenty of CASUAL scripts which will work on all, many, some or one device. Is it possible to link these tools cross-forum?
This is frigging awesome.
Feature requests:
1) Can/will this be enabled for [APP] threads, too? Has anyone SEEN the Nova Launcher thread lately?! But, not just for clutter--the feature request, Q&A, etc. will be very useful, too.
2) Can a FAQ tab be added? Not essential, but may keep 1st post of ROM threads from overflowing with paragraphs and paragraphs of text. Also, related to idea 6, below.
3) In bug reports, can we enter our hardware somewhere so we don't have to re-type it every time? Also, can multiple devices be selected, a la Google Play website app installing?
4) In bug reports, can we have a separate, but REQUIRED TO FILL OUT, text box for steps to reproduce?
5) Can bug reports be edited? Many times we think we know the issue, but then another user discovers the actual regression, and then instead of two bug reports, one can be made?
6) The biggest one is the last, hehe. Can we somehow have user-editable FAQs for threads? I seriously think XDA needs to implement Wiki's IN THREADS. People check threads (nobody, IMO, sees or even knows that XDA has a Wiki) and there are a handful of users who are nearly as knowledgeable as the developer who post. Maybe only OP-approved people can edit. But, seriously, you guys can make XDA legitimately 100x better if you implemented Wiki-style FAQs for these special threads.
Many people know the answer, but don't want to retype it 500 times. Now, let them put their answer in a very EASY TO FIND place in the FAQ. You seriously harness the power of this extremely knowledgeable community. If you don't, then you leave smart people upset at multiple people posting the same question.
Question:
1) Are
My two cents
Hopefully this isn't looked on as the ultimate sin or put me on any list hahaha BUT I have a question for any admin/moderator that's directly involved in this project....
How is this helping the developer?
I see a lot of things that users would love and want because they see this site more of a ROM shop then a development site but I don't see how this helps the developers, the ones doing the actual development.
I mean, judging from threads like the NOVA thread which ikjadoon pointed out above....users don't read or even search before posting which in turn causes developers to take more time away from the development process to answer questions that have been asked and answered about 100000 times if not more.
They also ignore warnings in OPs unless they're in BIG RED letters. They post in the wrong sections time after time even though there are stickies and is written in the XDA rules. The list goes on and on and on, how users repeatedly prove that they can't read 2-3 paragraphs if not less of information that will help them and/or follow simple instructions.
I'm not on any high horse here but if you ask anybody that's willing to be truthful if this is true or not, they will answer HELL YES.
With that said, by encouraging users to be even more lazy and giving them tabs is not only making it more difficult for the developer(s) by having him or her fill out these tabs BUT is not in my opinion going to fix the clutter/searching before posting issue.
This will also (in my opinion) send a wave of users harassing developers if they chose NOT to take part in the whole tabs project.
I don't have all the answers nor do I expect any of the admins/moderators that are directly involved in this project to have them BUT I believe this would be a step in the wrong direction if organizing the forums is the ultimate goal here.
ONCE again, this is my opinion. At the end of the day, is your site and you will do as you want. I'm just a member throwing my two cents in...don't shoot! :good:
svetius said:
This is relating to the announcement of DevDB: http://www.xda-developers.com/announcements/introducing-the-xda-devdb/
Please use this thread to report bugs, request features, and offer feedback. :highfive:
Click to expand...
Click to collapse
How about a field in the DevDB that indicates if the ROM passes Google's CTS (Compatibility Test Suite)? Some people may not want to install something that deviates too far from what Google intended Android to be like (or if something fundamental got broken), if you know what I mean.
Just my humble $0.02
ref: http://source.android.com/faqs.html#compatibility-test-suite
Sent from my Nexus 7 using Tapatalk 4 Beta
@Mazda
Some of your points are EXACTLY the reason I think each of these threads needs a user-editable (aka wiki-style) FAQ.
The developer, here, does NOT need to create and edit the FAQ themselves. Many knowledgeable users can do that and the developer is free to simply curate it.
If the FAQ is readily available in a tab, I think you will see a significant decrease in thread noise.
ikjadoon said:
@Mazda
Some of your points are EXACTLY the reason I think each of these threads needs a user-editable (aka wiki-style) FAQ.
The developer, here, does NOT need to create and edit the FAQ themselves. Many knowledgeable users can do that and the developer is free to simply curate it.
If the FAQ is readily available in a tab, I think you will see a significant decrease in thread noise.
Click to expand...
Click to collapse
I believe they tried that with the WIKI's and it didn't turn out that well....
Some wikis did well and some were ghost towns.........the clutter remained none the less
OH and I would like to say that I'm not here to piss on the idea of this project or just say "none of this will work", I'm simply stating my opinion based on what I've seen as a member since I've joined.
I would LOVE to see XDA live up to it's potential and maybe remove some of the clutter and trolls BUT I just see it going a different direction at this moment in time...
Exactly! They were ghost towns because nobody knew about them and, if you did, why take the time and energy to edit something that like 10 people would see?
Thus, place them as a tab on the OP like the others are now.
Same...XDA has ridiculous potential!
This is a great idea and one I've wanted to see in XDA or any other forum for a long time. Since I own a Note 2 N7100, I contributed my part by using Google docs and forms to provide much of the same information in the DevDB for the Note 2. I would say now much of my work is obsoleted, but I agree it is a good thing for XDA.
However for improved granularity, instead of just 1 ranking rating, can DevDB also include 1 other rating for Screen On Time as an indicator for battery life?
My sig links to the thread where I made the index, you can see what I've done.
Good feedback, guys. Keep it coming :highfive:
Well, more of the same, haha:
Threads are great for a few users having a semi-cohesive discussion. With many users, many important issues are somewhere within hundreds of pages.
A user-editable FAQ would fix that. I'd like to also stress the importance of having the FAQ as a tab and NOT a link, as otherwise we'd have fewer users editing and fewer users reading.
It doesn't have to use the exact wiki format. But, maybe, a community-editable post that is otherwise normal.
Some threads that could've used it:
http://forum.xda-developers.com/showthread.php?t=1727052
Galaxy SIII Annoyances Megathread
http://forum.xda-developers.com/showthread.php?t=1984126
The AT&T Jelly Bean Release Thread (4.1.1 released; Kies and OTA)
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
Mention @ tags don't work with DevDB.. Rest it ok needs improvement though
Not the s3? wow.
AdamOutler said:
that's a weird binary character. It's actually a hexadecimal representation of a character which is not present in the font you are using.
I have a few issues to address. What about tools which can be used for all devices? The CASUAL project just started a new IDE called CASCADE. It will eventually allow for users to create their own CASUALs easily via guided use of the CASUAL language. Also, there's plenty of CASUAL scripts which will work on all, many, some or one device. Is it possible to link these tools cross-forum?
Click to expand...
Click to collapse
Actually we are considering this as some tools are multi or pan-device. Working on a way to show this correctly across multiple devices without getting confusing. Honestly we wanted to make sure that this system works in the first place, find out where we need to expand it, and then do it. @AdamOutler don't know if you noticed but one of the download options (if you have edit capabilities on a download file) is to set it as a CASUAL file. You can also set a specific board for the download. Our API will allow you to ask XDA to "send me all CASUAL package files for 'mako'" and then allow you to download those directly. More TBA.
Mazda said:
Hopefully this isn't looked on as the ultimate sin or put me on any list hahaha BUT I have a question for any admin/moderator that's directly involved in this project....
How is this helping the developer?
I see a lot of things that users would love and want because they see this site more of a ROM shop then a development site but I don't see how this helps the developers, the ones doing the actual development.
I mean, judging from threads like the NOVA thread which ikjadoon pointed out above....users don't read or even search before posting which in turn causes developers to take more time away from the development process to answer questions that have been asked and answered about 100000 times if not more.
They also ignore warnings in OPs unless they're in BIG RED letters. They post in the wrong sections time after time even though there are stickies and is written in the XDA rules. The list goes on and on and on, how users repeatedly prove that they can't read 2-3 paragraphs if not less of information that will help them and/or follow simple instructions.
I'm not on any high horse here but if you ask anybody that's willing to be truthful if this is true or not, they will answer HELL YES.
With that said, by encouraging users to be even more lazy and giving them tabs is not only making it more difficult for the developer(s) by having him or her fill out these tabs BUT is not in my opinion going to fix the clutter/searching before posting issue.
This will also (in my opinion) send a wave of users harassing developers if they chose NOT to take part in the whole tabs project.
I don't have all the answers nor do I expect any of the admins/moderators that are directly involved in this project to have them BUT I believe this would be a step in the wrong direction if organizing the forums is the ultimate goal here.
ONCE again, this is my opinion. At the end of the day, is your site and you will do as you want. I'm just a member throwing my two cents in...don't shoot! :good:
Click to expand...
Click to collapse
Hey @Mazda, this is ddrager from Twitter.
Well these are all good points. We did a lot of thinking about what XDA does, what we stand for, and what we provide for developers. For a developer, we are oftentimes not only for discussion but also a platform both for distribution and for feedback on ROMs and other applications for mobile devices. In this regard, DevDB is a platform for users to find the right ROMs and applications for their devices, which hopefully keeps them off of the threads with questions about downloads and whatnot. Sure, we can complain all we want that n00bs don't read, don't search etc... but complaining about it doesn't fix the issue. We wanted to present a way that is easier to follow for those looking for new ROMs and how to modify their devices. A sort of 'device central' where you can get all the information on your device for everyone from those new to Android to those who are veterans at flashing ROMs.
For developers, not much has changed. You still have the development forums, and this is totally optional. DevDB adds some features like built-in reviews, bug reports, a torrent tracker/download system etc. This is mainly for those devs who wish to have additional promotion of their projects, and to make it easier for end-users to find and interact with those projects.
Regarding the issue of users not reading, this isn't a problem unique to XDA. You can point people to search as much as you want but there are 10 people behind them asking the same questions. We've all been guilty of this to some extent at one time . What we can do as a site is make the important information as easy to see and find as possible to help reduce the amount of extraneous questions sent to developers, that have already been answered.
XDA is a site full of information overload, and the best thing we can do is make that information categorized and easy to read.
ikjadoon said:
@Mazda
Some of your points are EXACTLY the reason I think each of these threads needs a user-editable (aka wiki-style) FAQ.
The developer, here, does NOT need to create and edit the FAQ themselves. Many knowledgeable users can do that and the developer is free to simply curate it.
If the FAQ is readily available in a tab, I think you will see a significant decrease in thread noise.
Click to expand...
Click to collapse
This has been brought up a few times. I think what it comes down to is that we currently have a wiki, and nobody really uses it for something like that (that I know of). You can create a page on there and link it to the thread as it is right now.
Great feedback all, keep em coming! :highfive:
awesome feature. when can we expect it to be available on other forums
not asking for an eta although
Just wanted to say this is AWESOME!
I browsed around a bit in the "db-test-areas" and I really like it! The benefits are clearly visible:
Better overview
makes it easy finding stuff for your device
no need to browse pages and pages of devices sections when you are searching for something specific
I'd love to find it in the whole forums!! Keep it on!
In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not clearly understood by some users, and others leave room for interpretation. With this Q&A, we give you some additional guidelines regarding how the forum for this device is moderated.
Spoiler: Index
Post #1
Who are the moderators for this forum?
How do I contact the moderator team?
Where do I post my thread/issue/question?
Where can I post things that are not allowed in a Device Forum?
What do I do when I do not understand a moderator's decision?
Post #2
XDA-Developers and the GPL
Post #3
ROMs, Kernel, Recoveries, & Other Development Forum
Post #4
Thread Naming
Post #5
WhatsApp/Telegram Groups and Channels - Going Forward
Who are the moderators for this forum?
The Team Leaders (Senior Moderators) for ASUS, HTC, Nokia, Nothing, nubia, OnePlus, OPPO, Realme, Sony, Xiaomi and ZTE devices are Az Biker, coal686, engloa and Stephen.
The Moderators for the sections listed above are alecxs, Funk Wizard, roirraW "edor" ehT, and Sib64.
How do I contact the moderator team?
While you are free to contact any of us via PM, for moderating purposes, it is much more advisable to use the report system. You can find the report button in the lower left corner of every post or conversation message. If you do that, your request reaches all moderators, thereby multiplying the chance of a fast reaction to your request. If you PM a moderator, he/she does not know whether you have contacted others also and therefore it is possible that your request is handled by different moderators, possibly overruling one another. Or, the moderator you messaged might not even be online for some time (for example, due to real life issues, etc.). Our ticket system avoids that. Therefore, please always use the report system.
Where do I post my thread/issue/question?
This is a very important decision and decides not only whether you achieve the goal you intend with your thread/post, but also whether it might be regarded as off-topic/not allowed and therefore be removed. So here is a list to help you decide where to put your thread (or maybe to not post it at all):
Questions & Answers Sub-Forum
What goes here:
All device related questions (questions pertaining to a ROM/kernel/theme/mod, etc. should be asked in the ROM/kernel/theme/mod's specific thread, if it exists)
Guides, News, & Discussion Sub-Forum
What goes here:
Guides, collections, tutorials, repositories, indexes
General information about the device
Tips and tricks
General discussion about technical aspects of the device
What does not go here (by far an uncomplete list, just some examples for topics that are not acceptable):
Everything prohibited by the Forum Rules.
Trolling, arguing, etc.
"What was your last phone/will be your next phone" (Off-topic for a device forum, you can post this in the Off-topic Forum)
"Hello", "Goodbye", "Merry Christmas/Easter/Hannukkah/whatever" (Obviously off-topic, just imagine if every user posts this!)
"I'll never buy XYZ brand/phone again", "Why Sony/Xiaomi/whoever sucks" and all other "hate" threads (Tell that to those guys, not us)
"Help!", "How do I...", "Why..." and all other questions (They belong in the Q&A sub-forum)
ROMs, Kernels, Recoveries, & Other Development Sub-Forum
What goes here:
Publications and releases of your own development (ROMs, kernels, recoveries, etc.; for exact rules for creating such threads, please refer to Post #2 and Post #3 below)
What does not go here:
Any questions, guides, tutorials, general information/discussion, etc.
Themes, Apps, and Mods Sub-Forum
What goes here:
All discussions related to device specific theming or applications (self-made or shared)
Announcements and discussions regarding modifications made to device specific theme or application
Accessories Sub-Forum
What goes here:
All discussions related to accessories relevant to the device
NOTE: Not allowed in any section (including signatures):
Everything prohibited by the Forum Rules.
Specified or implied off-topic threads.
Discussion of/linking to work of developers that are banned from XDA. If they are banned, so is their work.
Political/religious statements of any kind.
Where can I post things that are not allowed in a Device Forum?
You might want to have a look in the General Discussion Forum for forums like:
General
Off-topic
Android Development and Hacking
What do I do when I do not understand a moderator's decision?
Please feel free to contact the moderator via PM to request clarification. They are approachable people, not robots. If that does not satisfy you, you can contact one of the Team Leaders (Senior Moderators). Do not, however, discuss any moderating issues in any of the forums. This will always be regarded off-topic (which it actually is).
Now let's all have fun on this forum and help each other to make XDA a place where users can gather useful information instead of sipping through knee deep piles of unorganized rubbish.
Regards,
Your Moderating Team for ASUS, HTC, Nokia, Nothing, nubia, OnePlus, OPPO, Realme, Sony, Xiaomi and ZTE devices
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 anyone and everyone. 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 kernel. 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. LineageOS, AOSP, etc.) 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 are either with GitHub, or GitLab. 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 ROM or 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 manufacturer 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 wrote a portal article in 2013 explaining a certain situation that has come across our desks. You'll find more examples here. We can only advise you to reach out to these manufacturers with a kind request to comply with GPL v2.
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"
}
ROMs, Kernel, Recoveries, & Other Development Forum
This forum is exclusively reserved for ROMS, Kernels, Recoveries etc. provided they are your own development.
Try to keep the development threads clean. No off-topic posting and no question should be posted in this forum.
Use the report button in the lower left corner of an offending post to let us mods know we need to take action. Don't take matters into your own hands.
Sources need to be posted for all kernels. They're also needed for all ROMs where license demands it. Please refer to Post #2 above for more on this.
You need to use tags in the thread title, like [ROM], [KERNEL], etc. throughout XDA. Please refer to Post #4 below for more on this.
Any disputes between developers should be handled by PM; always try to solve the issue amicably first via PM. No public posting in a development thread regarding these matters.
ROM issues should be discussed within their respective threads.
Thread titles should always coincide with ROMS already available for download. Notification of an upcoming ROM through thread title/placeholder thread is not allowed. A changelog for the yet unreleased ROM can be included in the OP or in another post clearly marked as expected changelog.
All threads posted in this forum that are NOT about one's own development may be closed or deleted. Posters that will choose to disregard these guidelines will be infracted.
THREAD NAMING
The purpose of this thread is to explain how you can name threads in forums thereby making their content easier to read and understand.
Following are the recommended tags:
Click to expand...
Click to collapse
[INDEX] - Index for a specific device (more information here)
[DEV] - Development for projects
[ROM] - Custom ROMs
[KERNEL] - Custom kernels
[MOD] - Hacks and modifications for the device
[FIX] - Fixes for known issues and bugs
[GUIDE] - Guides
[TOOL] - Tools
[RECOVERY] - Custom recoveries
[RADIO] - Radios for the device
The title of the thread should also include the following in a chronological order:
Click to expand...
Click to collapse
[Tag] - From the above list
[Date] - Date of latest version
[Name] - Of the project
[Android Version] - Of the project
[CDMA/GSM] - If the project is only for a specific band
Example:
Click to expand...
Click to collapse
[ROM][18 JUL]LineageOS[12.1][GSM]
More guidelines:
Click to expand...
Click to collapse
If you are unsure of where your new thread should be posted, then please refer to the first post in this thread.
When possible, please include screenshots for your ROM/mod/theme/app as it's expected by our members.
Placeholder threads are not permitted in the development forum and will be removed.
Password must be provided for all password protected files.
Please respect these simple rules, and if you don’t, your thread will be closed or deleted.
Click to expand...
Click to collapse
WhatsApp/Telegram Groups and Channels - Going Forward
Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA.
What does that mean?
We will allow links to messages on Telegram and/or other platforms anywhere, as long as they provide content for a discussion, question, or is pertinent news. This is exactly like the guidelines for YouTube links.
What about download links?
Download links from hosts, platforms or other sources are allowed as long as they do not require registration. Some Telegram links require registration for downloads, so they will not be allowed. Please check them before posting.
What is NOT changing?
Only one link to a Telegram support group is allowed in the first post of a development thread on the condition that main support is still provided on XDA. This means you can mention Telegram group: https://t.me/abc in the first post as long as you're providing thorough support in your XDA thread.
What is NOT allowed?
Posts like For support, join my Telegram group: https://t.me/abc. This means you're not willing to provide support to users on XDA.
Drop-and-run posts/threads are still not allowed under the self-promotion rule. So posts/threads like "Come to my channel for xyz" or "Watch my video and like my channel" are still not allowed. Such links will be removed and the member will be contacted regarding XDA Forum Rule #5 for self-promotion (under bullet point #6):
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
We thank all members for their cooperation in this matter, and wish you a pleasant stay on XDA.
Regards,
Your XDA Moderating Team
Moderator Edit:
Not here, ever:
You need to read the Forum Rules again:
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community..
@Aby lad if you're not the developer of the app you should not copy paste the text from playstore and provide the app through Google drive.
Better to provide the play store link and give proper information about the source.
Hello fellers,
just tested must have feature adaway on my one plus NORD
requirements:
1. Latest magisk
2. root access
steps:
- magisk manager settings
- turn on systemless hosts
- install adaway
- click red button install custom hosts.
restart phone and u re set to go!
adaway apk.
Why not referring to the official threats?
https://labs.xda-developers.com/store/app/org.adaway
https://forum.xda-developers.com/showthread.php?t=2190753
Or use Magisk module Energized Protection
https://www.google.com/amp/s/forum....module-energized-protection-one-t3806865/amp/
Tracker31 said:
...
Click to expand...
Click to collapse
THREAD CLOSED and attachment removed, which by the way wasn't the latest release.
Do not share software without permission of the original developer and without credits to him!
XDA Forum Rules (excerpt):
...
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 to a Moderator. We are here to help!
...
Click to expand...
Click to collapse
Recognized Developer Code of ConductAs an XDA Developers member with special standing as part of our developer program, we obviously have some expectations of your conduct. We try to be friendly here, and while we understand that not everyone is going to get along, we would ask that you try to avoid getting into big arguments in threads. If you have an issue with another forum member, take it up with them politely in a private message. It’s the mature way to deal with things.
As a titled member on XDA, you are a representative of XDA’s ethos – “by developers, for developers.” As such your activity offsite in other public venues should be in the same vein. Any negative, derogatory, abusive talk or actions may be taken into account as to your status as a titled member. This would include any behavior which violates our site rules. This does not change your responsibility to be subject to the requirements for acceptance into the Recognized Developer program, both in their current and future states.
While all users should follow the site rules, we would ask that you take a quick look at them again, as they are occasionally updated. If you have any questions, please don’t hesitate to get in touch with any moderator.
In addition to the rules, we would highlight the importance of acknowledging the work of others. It’s not nice to see your work get ripped off—whether it’s a ROM, part of a ROM, an app, a theme, images, guide text, etc. If you’re familiar with the regulations in academic institutions, you should know the score. Just seek permission and acknowledge those whose work you use, and generally be reasonable about things.
We would also ask that if you have a dispute, you first try to resolve it in a reasonable and private way, such as through private message. It is in no one’s interest to see your dirty laundry aired in public, and it looks much better for you to avoid conflicts on the site.
Senior Recognized Developers of XDA, in additional to the above, are expected to be active on XDA regularly. While we all go away for vacation, exams, and other everyday life events; we would ask that if a Senior Recognized Developer intends to take a significant break from development, he or she stand down temporarily. You’re more than welcome back if and when you return, and we’d love to have you back, if a space becomes available. The reason for requesting this level of activity is because as a Senior Recognized Developer, you will be able to vote on the appointment of other Senior Recognized Developers in the future. If many Senior Developers disappeared, it would be troublesome gathering a sensible turnout. In addition, from time to time we will invite discussions on matters pertaining to the site, and it’s only fair that we try to ensure that the people most familiar with development and XDA have a chance at helping out.
Recognized Developer Minimum RequirementsTo be able to provide some transparency on how the reviews for RD are rated we’ve set up these minimum requirements. Please understand that the RD program is not just a reward for people that try hard on XDA, it is more than that. Accordingly, not just any project meets the standard of development. We will use these minimum requirements with enough room to budge if the circumstances require this, but please use a somewhat critical view of your projects, and only apply if you have at least met these requirements.
Make sure you uphold the RD code of conduct and the regular XDA rules. Should you have infractions on your account, contact the Developer Committee if you want to know if you are eligible to apply. As a general rule of thumb, wait one month per infraction point before applying, and can’t accept members with more than 10 points to their account. Of course, exceptions may be made but contact us if you have a question about this.
All Projects
Members must be actively involved in the community
Team accounts can’t receive the RD title. It’s a program that rewards developers for their individual work and team accounts don’t fit that idea.
A minimum of two full-fledged, markedly different projects are needed to apply for RD, only very special projects are considered otherwise
Any project needs to have at least three months of active development before it will be taken into account for the application
No history of bans and/or serious infractions
Changelogs must be readily available inside the thread, with updated information for each version
Feature lists and changelogs need to be free of blurry expressions like “tweaked ext4 performance” and other meaningless terms. Instead, it should be explained what was done in detail and why it was done
ROM
They started from an official manufacturer or source base (stock ROM or AOSP-like source).
Threads show a clear overview of changes made, in a way that DC can clearly see what has been developed by the user
The ROM isn’t the product of an online kitchen or otherwise derivative development (i.e. themed stock ROM)
ROMs need to identify what kernel they are using
If 100% stock then they must state that
If custom they must provide a link to the kernel on XDA (if available) or a link to the kernel source. To accomplish this there are two options:
Option 1: They provide links to suggested kernels but do not include them in the ROM
Option 2: They include the kernel but must provide a full, buildable source with all GPLv2 requirements met
Apps
Very simple applications may be excluded (very basic UI or functioning)
A free version of the application is available on XDA (no trials)
The developers are either active on XDA or really helpful in their support thread
Kernels
Sources must be posted and downloadable with build comments, toolchain used, and must compile
Sources must be released via forking + commits rather than “lump releases”
Link to the source must include which branch is in use
Guidelines:
In order to make sure the DC is able to find the information we need to make sure your threads hold all the information necessary. Here’s a list of things we like to see.
Threads should include:
Clear introduction
An overview of what the project does (i.e. its purpose) and what is included
2-8 screenshots that are posted alongside each other
A clear changelog in a
Code:
or tag, that shows the non-trivial updates to the project
Installation instructions and links to download and github (or like services) for source code, as applicable
Credits with links to the projects that have been built upon, or have been included, in this project
Provide a checksum if you can (md5, sha1 etc.)
The DC set up a template thread that highlights the important parts of a project. Try to follow this template to have an organized and clean thread. You can find the template thread here.