The following are reasonable formats that are suggested when posting a new ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel they must provide a link to the kernel on XDA (if available) or a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available).
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external websites home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
Related
Here is what is likely to be posted here and whats not
The following are most likely “Original Development”:
Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
Your own “unofficial” stock build of your favourite 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
ALSO ALWAYS REMEMBER THE GPL LICENCE:
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)
Click to expand...
Click to collapse
To put it short,
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL 2.0 since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what best for you)
- A github link
- packing your kernel and uploading
- a diff .patch files
- Credits to people in case of an already custom kernel
- Sources must be posted in first post of development.
Rule No.2 - If you are about to post a new Rom, you don't have to post source since they are covered by Apache, BUT you must be in compliance with XDA rule and with good sense. Remember that publishing sources is a very polite manner.
New Roms thread must contain:
- Exactly say which base rom do you used : Stock, custom from another developer, CyanogenMod.
- Permission to use said ROM as your base by the original developer(s).
- Credits given to original developer(s) in your first post: (eg: Credits and thanks for this Rom goes to XXXXX)
- Credits given, if possible, to the people from whom you grabbed scripts, themes and apps.
- Your ROM MUST BE free of paid apps, NO WAREZ ALLOWED.
- Your first post must contain as much info as you can provide, "this is my ROM" and a link is not tolerated (screens, installation procedure, CM version, kernel version etc.)
- Thread Title : " [ROM]xxxxxxxxxxx[date of release][kernel version/kernel required]
Rule No.3 - AdFly, or other ad-revenue related redirecting links, are NOT allowed. Thread will be closed and links be deleted.
Click to expand...
Click to collapse
-----------
Referenced from:
Samsung Galaxy Ace Section
☞[WARNING: READ ME 1st] If YOU DID NOT CREATE "it" THEN IT DOESN'T BELONG IN HERE
NOTICE: If You did not create the ROM, KERNEL, FIX, MOD, APP, HACK, GUIDE, or if it's not a SOURCE CODE then it should go to Nexus 4 General as it doesn't belong in Development.
If your thread can be phrased as a question, it DEFINITELY doesn't belong in Development either, post in in the Nexus Q & A sectionhttp://forum.xda-developers.com/forumdisplay.php?f=1909. If you post it in Development it will be moved/closed and you may get an infraction or a ban.
There is only 1 exception, stock ROMs are allowed, as long as the link does not require a registration to download the ROM.
You may start planning a [DEV] topic in the General or Q & A section and then have it moved to the Android Development section once the actual Development has started.
☞ Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source
☞ Themes are graphical/visual changes made to a ROM which make's the ROM visually different from the original work, i.e. different battery icons, a blue-color scheme, etc. They may be packaged up together with a full ROM and deployed the same way. Simply running a script (not made by you) to deodex and then packaging other people's work/MOD's into one place does not constitute original development.
Follow the FORUM RULES and the XDA MANTRA and we'll all get along and enjoy this community!
Thank you for your cooperation & thanks to jerdog for writing this wonderful explanation.
Below is a format that is a guideline to be used as an example of how a rom thread should look. It doesn't have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
Name of rom, team, etc
Introduction
Changelog in code or list tags
What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code or list tags
What works/what doesn't work in code or php tags
Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
Screenshots (2-10 different screenshots of different aspects of rom)
Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
Do's and Don'ts of the rom
Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
Finally the dl link
Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes you weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Not to toot my own horn but here is a link to one of my own rom threads as an example. Link
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesn't look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either. If posted then the thread will be removed
Thread title format
Just to add to Papa Smurf151's post, when posting something, please use this format for the title:
[What it is][last updated][Version+stable/test/beta/wip/etc]Name of rom/kernel/etc
For example:
[ROM] [15nov12] [4.3.1BETA] TheBestestKangedROMEver
The following are reasonable formats that are suggested when posting a new ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel they must provide a link to the kernel on XDA (if available) or a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available).
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external websites home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
Just downloaded the latest version as needed to update my license key also, but the new key I just generated is not working in the new version, it is asking for a ELM key, I have a KLM like I've always used, which isn't working, adhell gives error 201 when I try to use it. Anyone know what's going on? Do I need a new type of key? I see no options on SEAP to make anything other than the key I have..
See for link to edu key
https://gitlab.com/fusionjack/adhell3/blob/master/README.md
And more info, last two pages
https://forum.xda-developers.com/galaxy-note-9/help/adhell-3-1-assistance-t3873831/page23
Thanks I figured it out already, never got notification of your reply which would have been helpful haha. But I'm sorted now anyway. Thanks again though ?
Please keep in mind that AdHell3 is NOT supported on XDA. For official and up-to-date information about the AdHell3 project, please visit:
Main repo: https://gitlab.com/fusionjack/adhell3
Scripts for compiling: https://gitlab.com/fusionjack/adhell3-scripts
Get your EDU ELM key from: https://seap.samsung.com/license-keys/generate/edu
Official Support Discord Channel: https://discord.gg/hfreZum
Dependable(?) precompiled APKs: https://www.mediafire.com/folder/sb37c6gmhqgbn
Mike B. said:
Please keep in mind that AdHell3 is NOT supported on XDA. For official and up-to-date information about the AdHell3 project, please visit:
Main repo: https://gitlab.com/fusionjack/adhell3
Scripts for compiling: https://gitlab.com/fusionjack/adhell3-scripts
Get your EDU ELM key from: https://seap.samsung.com/license-keys/generate/edu
Official Support Discord Channel: https://discord.gg/hfreZum
Dependable(?) precompiled APKs: https://www.mediafire.com/folder/sb37c6gmhqgbn
Click to expand...
Click to collapse
Why is it not supported?
Not supported as in official and up-to-date information about the AdHell3 project is on the links listed
Snowby123 said:
Why is it not supported?
Click to expand...
Click to collapse
Because XDA doesn't provide a convenient way to host and support ongoing source code projects, and there are only 3 of us and only 24 hours per day!
Various XDA threads erroneously deal with AdHell3 as if it were a simple "download and install" app when it's actually a GitLab project which must be compiled by a Samsung Developer. It is not (and cannot legally) be distributed as a precompiled APK, and any such APK that you may find is the sole responsibility of its uploader (and hosting site), in violation of Samsung's policies. Improper distribution of earlier AdHell, AdHell2, and SABS led to those apps getting discontinued at Samsung's request. Furthermore, those APKs must be "patched" to be usable, possibly in violation of XDA's policies.
The AdHell3 project is alive and well, and fully supported in the venues mentioned in my previous post, including READMEs, FAQ, etc. See you there...
UPDATE:
Samsung is not currently issuing any keys suitable for use with AdHell3. Please see our official support areas or at least check out THIS post