Can now be found in Roll up
~The following are the main determining factors in the differences between Android Development and Android Original Development,as laid out by XDA Developer Admin pulser_g2.~
{
"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"
}
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 "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)
Related
The following are rules for 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)
{
"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"
}
The following are rules for 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)
{
"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"
}
At least for me, one of the main factors when deciding to buy new phone is 3rd party development community. And what place is better to find custom ROMs than XDA-Developers? However, it is hard to determine which devices are more XDActive than other. Only statistics I have found was total number of posts, which does not help much as 3 year old device will probably have more total posts than 3 months old one even though 3 year old device will be more abandoned than new one.
That is why I decided to make little scrapper that went through all recent threads on all development forums and counted all posts made in October 2015. Results are there:
RAW Data
CLICK
Breakdown by manufacturer flagships
Here is little graph that displays all posts made in October 2015 broken down by manufacturer and phone release date (all flagships from specific year and manufacturer are counted together):
{
"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"
}
(I had to collect these manually so graph only includes flagship phones).
As you can see, if you get anything else than Nexus, Samsung or Oneplus, activity on the XDA will be relatively low regardless of the device's age. While 2015 devices are included on the graph, numbers for most of them are irrelevant because they were just released. However we can still make some comparisons, for example between HTC, Samsung, LG. Even though they have been released at about the same time, activity on this year Samsung's devices is already comparable to last year's and it is vastly higher than all other devices..
Original Development breakdown
Second graph is similar to first one, but only counts posts made in Original Development forums of the devices. That shows clear picture of actual development, instead of just buttload of ROMs with changed themes or different baked-in apps.
I don't think there is anything surprising here. Anything except for Nexuses and Oneplus scored really bad here.
I will attempt to re-do those periodically and post the result, I think it will be interesting to see how device activity evolves over time, especially for 2015 Samsung devices that only have supposedly developer-unfriendly Exynos chips.
After an analysis I found that number of all posts is not very indicative of device's activity. For example G4 development forums are barren wasteland, except for one thread that generated a lot of traffic, moving it near the top of the list even though there was no activity really.
That is why I updated RAW data link in first post with two additional metrics:
Number of all threads that were posted to in October 2015. I feel this is much better metric, because it indicates that device is actually active, not just one lone ROM.
Number of posts made by recognized contributors/developers. This metric is suspectible to the "one active thread" metric as original one, but it can be used to distinguish between actual developers posting something instead of people just rambling about.
There are a few issues I see with XDA that need quick attention:
1. Posting a new threadIdeally, the 'Post Thread' button should be available universally, and user must choose the appropriate forum (and sub-forum) before the button gets activated for posting.
Currently, one has to 'search' to find forums and sub-forums, which itself isn't intuitive. This is more like Apple's way of implementing some of their things. This being the world of Android, we should stick with the simpler and intuitive approach.
Alternatively, there should be easy and quick access to the following two pages:
General Discussion
forum.xda-developers.com
Android Development and Hacking
forum.xda-developers.com
2. Sub-Forums by Android version and brandThere is a sub-forum for each device model. I guess this is done so users can find the right files to flash (this being the XDA) for their device. I'm not sure what % of posts on XDA are about flashing stuff.
I would like to think that the number of posts about general topics concerning Android would be far higher than those specific to flashing and modding.
In this regard, it would be nice to have a forum for each version of Android, and then a sub-forum per brand. An issue with a particular version of Android will affect all devices, especially those that are from the same brand. This will make it easy for users to find posts per Android versions and learn about problems that may not have been discussed in the device specific sub-forum.
An example:
When Samsung releases OneUI 6 based on Android 14 later this year, any issues with it would be seen on S23 Ultra, S23 Plus, S23, S22 Ultra, S22 Plus, S22, S21 FE, and a whole lot of devices that get OneUI 6. Same logic applies to all the smartphone brands.
It is far easier to discuss issues related to the OS version in one sub-forum than spread it out over multiple sub-forums, which will also result in many duplicate posts for the same issue. Plus, users watching device specific sub-forums may not be aware of issues on their device if they haven't been discussed in those sub-forums.
3. Filters in Watched section
Just as we have filters in New Posts section, it would be nice to have one in Watched section too.
{
"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"
}
I had already made a suggestion for this here and here.
Hopefully XDA would consider these suggestions after taking inputs from its members.
@TheMystic
It would be nice to post it here, your request might be seen by xda admins
https://forum.xda-developers.com/t/xenforo-2-2-upgrade-post-bugs-issues-and-comments-here.4245677/
khusika said:
@TheMystic
It would be nice to post it here, your request might be seen by xda admins
https://forum.xda-developers.com/t/xenforo-2-2-upgrade-post-bugs-issues-and-comments-here.4245677/
Click to expand...
Click to collapse
Already made a request in a different sub-forum (New Device Forum Request) some time back, and it got lost in the comments section.
I have posted a link to this post in the sub-forum you suggested. Thank you. Hopefully it won't get lost like last time.
{
"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"
}
Disclaimer
* We're not responsible for bricked devices, dead SD card or anything happens with your device
* Flash on your own risk/knowledge.
--------------------------------------------------------------------------------------------------------------------------------------------------------
TEAM XTENDED: @SuperDroidBond | @mady51 | @mukesh22584 | @anishpratheepan | @xawlw | @SonalSingh18 | @Roger.T
***Links Removed by Moderator***
We would like to give thanks to everyone in the Android community, big or small.[/B]
@Mgm2023 you are required to comply with the Rules for Posting In Development and Telegram Policy stickied at the top of this section.
Further, you must comply with 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:
Click to expand...
Click to collapse
This does not appear to be your own project. You must indicate as much, and you must have permission from the developers to share it.
This thread will be locked until you are ready to make the required corrections.