[Mandatory] Rules for Original Development - LG G Watch R

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"
}

Related

Introduction

Hello, XDA.
I joined the forum after hearing that is was "basically the hub of anything to do with Android." I also joined because I'm in the beginning stages of developing Android applications (learning Java), and I eventually wish to release a free, open source application to contribute to the community -- to the world. I won't be specific as I really can't at the moment; I'll be a little more specific when I finish the Java tutorials by Oracle. I don't intend to reinvent the wheel, I just expect to make it better. =p
My goal on this site is to integrate, learn, and enjoy myself at the same time.
Albeit insignificant, I am familiar with a coding language called "gotos" or so I've heard it called that. More specifically, the Mugen engine that focuses on developing fighting game characters and stages through a compilation of graphical and audio components. The coding is mostly based off of physics and trigonometry (two subjects at which I excel) and a bunch of other cultural expectations.
Away from the digression: The ancient syntax of the Mugen engine, believe or not, has helped me a great deal in understanding the object orientated language known as java.
In java, I'm not ready to code any applications or anything yet, but I understand the basic functions so far. I'm just finishing up the Interfaces and Inheritance portion of the aforementioned tutorials. I know it will take years for me to become a wiz at this java stuff. I mean, I've been doing Mugen for 4 years and I'm still learning new stuff (and the coding language is as easy as it is inferior).
I own a Galaxy S2 phone, am running gingerbread (I think that's what it's called, this uncertain is exactly why I'm a n00b). Whatever that information is worth. Maybe I should put that in my signature.
Anyway, I hope to integrate well. I am not new to forums, so I don't expect to step on anyone's toes or anything. The video before I registered was very, very entertaining, but nothing in it surprised me.
Cheers, Mr. Holmes.
Welcome. I'm new too.
Welcome to the forum mate, and good luck with your app development.
Sent from my GT-P1000 using Tapatalk
Hi Holmes,
Welcome....im new too here..all the best to u holmes..
{
"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"
}

[Clarification] Development ~ Original Development

~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)

[Mandatory] Rules for Original Development

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 favorite 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 re-badges 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 “add-on 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"
}

Material lolipop theme for hk theme manager/xtheme engine

hello guys i am today presenting my first ported theme for xtheme engine & hk theme manager this theme is made for hdpi devices
Personally tested in micromax unite 2
This theme has a bug of calculator so i added lolipop calculator in this zip
View attachment 3192954
View attachment 3192955
{
"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"
}
[Moderator Edit: Download links removed]
Forum Rule 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, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who 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 that developer. 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). If the developer decides to start sharing the work with others, the work automatically becomes available for all to use, albeit with the relevant credit displayed.
When permission has already been 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 extreme 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.
Click to expand...
Click to collapse
Thread closed.

Fuchsia OS project

Fuchsia is a capability-based operating system currently being developed by Google. It first became known to the public when the project appeared on GitHub in August 2016 without any official announcement. In contrast to prior Google-developed operating systems such as Chrome OS and Android, which are based on Linux kernels, Fuchsia is based on a new microkernel called "Zircon".
Upon inspection, media outlets noted that the code post on GitHub suggested Fuchsia's capability to run on universal devices, from embedded systems to smartphones, tablets and personal computers. In May 2017, Fuchsia was updated with a user interface, along with a developer writing that the project was not a "dumping ground of a dead thing", prompting media speculation about Google's intentions with the operating system, including the possibility of it replacing Android.
It is distributed as free and open-source software under a mix of software licenses, including BSD 3 clause, MIT, and Apache 2.0.
{
"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"
}
It's been quite some time since we've heard anything about Google's Fuchsia OS project. The search giant is keeping the lid on the whole endeavor. Still, the odd public official mention here and there and the activity on the Fuchsia repository do signify that the project is alive and work on it is ongoing behind the scenes.
In a new development, a path was spotted on said repository, adding support for the Kirin 970 chipset and detailing test for booting the Zircon kernel on the Honor Play, based on said chipset.
Looking at the patch and its meta data a bit closer shows that the owner (as in the project management meaning of the therm) is one Murali S R with a huawei.com email. This is a clear indication of some sort of cooperation between Google and Huawei on this matter, as opposed to Google simply testing things internally on its own.
Source:
https://www.gsmarena.com/googles_fuchsia_os_project_adds_support_for_kirin_970-news-34388.php
https://www.xda-developers.com/huawei-testing-fuchsia-os-kirin-970-honor-play/
https://www.digitalinformationworld.com/2018/11/huawei-tests-google-fuchsia-on-honor-play.html
I've been following Fuchsia Project for quite some time now. This is a welcome development from Huawei and Google.

Categories

Resources