Related
[REF Idea]*Chef input required please* ROM Spec & content - easy choice & comparison.
Hi all HD2 XDA'ers
As we know, the "Which ROM is best" question can be so subjective that no single thread or poll can accurately help you make a decision. Also they get closed and locked pretty quick by the mods.
The users and flashers need some method of selecting ROMs, or at least prioritizing which we try first, based on their individual requirements.
In addition, and perhaps more importantly, the ROM chefs have no standardised way to illustrate or describe exactly what their ROM is like to prospective users. The many posts and threads do not enable any form of comparison.
Here's an idea for anyone willing to take up the challenge:
Unfortunately I can't dedicate the time and effort required, however I know it would be infinitely useful to many users and cooks alike. (Maybe even the mods would find it a useful way of stopping the constant questions, threads and polls of which rom!)
Create a table detailing all the specific (or generic) characteristics of each ROM. Then all chefs, new or experienced, can add their ROMs to the table.
Table would begin with high level details (for a quick overview); then possibly expand to include subtleties and very specific details.
First we would need to create a benchmark using the latest STOCK ROM. This is what the specs of cooked ROMs will be measured against. It should also define all stock apps, etc. for accurate comparisons and to assist the cooks in completing the table for their own ROMs.
For example:
ROM Chef's username
ROM Name/Version
Fully Loaded / Minimalist
Which custom apps included [free text list/csv]
Stock apps cut from Rom [free text list/csv]
What Task Manager used (if any)?
Ringtones stripped? [Y/N]
Media/Wallpapers included
Tweaks included [free text list/csv - or single row for each expected tweak]
Theme changed [description]
Manila version
Cookie/MaxManilla included? [Y/N]
WM Version [6.5 ; 6.5.3 ; 6.5.5]
SYS/XIP build
Free memory after flash (MB)
...and on... (the above is just off the top of my head - it would certainly need more thought, massive expansion and sub-divisions.)
Perhaps start as a thread, work it to a useable format, gathering feedback, comments, suggestions and requests, then move to the Wiki. I recon, if the format and fields are all dimensioned extensively and well enough, the resulting table/wiki would be adopted across all devices.
I would sinserely love to do this myself and regret just pushing the idea out there. I really hope that someone who's heart is really in it, will be willing to take this up to the benefit of all HD2 owners who wish to stick out WM6.5x despite the temptations of other devices, OS's and ports.
All the best,
Hirshy
Information Systems Security Senior Specialist - Networks
T-Mobile (UK) Ltd.
Sounds like a good idea to me.
basically like distrowatch for linux systems? with the package/AKU/radio/Memory/custom apps on the y key, ROM name on the X key. And a blank space in the table where the package is removed?
Just a note - how would someone like you use the data since you work for T-mobile?
chris_ah1 said:
Just a note - how would someone like you use the data since you work for T-mobile?
Click to expand...
Click to collapse
+1 id like to know that too
chris_ah1 said:
Just a note - how would someone like you use the data since you work for T-mobile?
Click to expand...
Click to collapse
quasi_mojo said:
+1 id like to know that too
Click to expand...
Click to collapse
Hmmm, what would you guys like me to do with it?...
I have contacts in the Handset teams for testing and procurement. As my particular job role is impacted by the 'quality?' of their firmware, I regularly feedback required changes and user input. Though to be honest, they're unlikely to care much about any roms other than their own customised garbage!
Have you seen the state of T-Mobile's stock ROMs? At least on Android they get OTA updates quite quickly and in-line with the HTC development branch.
However on WinMo it's the regular old story that they release a device and forget about the bugs and updates.
I work in their Network Security team and am becoming more involved in Terminal Security (devices and whether anything compromises the Network or User Data in terms of confidentiality, integrity and availability). I test all new T-Mobile products, services and network features on their respective platforms.
For example on WinMo, there are the new WnW4 Widgets which run from the Opera run-time environment.
So I guess in that respect, as a favour to the community I would be willing to add my own professional input into whether there are any Security or TMO functionality concerns (from the user's perspective) with the ROMs...
My input here isn't for any professional purposes, I am just a member of the community that has worked at T-Mobile for 11 years and has ties to various contacts.
If there are any concerns for my intentions here (which I hope not) I have personally spoken to Dutty Throy about a year and a half ago to provide him with a contract deal so he could hopefully continue his great work at much less expense. I'm certain he would vouch for me...
Regards,
Hirshy
P.S. (If you read this Throy, it seems that you have since moved to Voda, so maybe T-Mob wasn't cutting it even with the deal - I suppose half-price sh!t is still sh!t !)
Yep, cant believe this hasn't been done yet, would totally reduce wasted threads
Big problem is the rate at which roms get updated.
But i see your point that it would be useful.
It's a helluva lot of work though given the number of roms.
Just off the top of my head I can think of 20roms.
And in the past chefs have been slow to submit their roms to a couple of the rom databases that already exist for swift comparison. I do think that this is better than one of those sites. You would have to get a team together and assign five to ten roms each to watch and update a spreadsheet because it's not going to work relying on the chef's input.
but it really might be useful - e.g. Topix 1.5.8 was based on 21898, but now Topix 1.5.9 is based on 21897 and without the weather function. The build might not be so relevant, but missing weather certainly is!!!
Then you also have the question as to whether to include the htcpedia-only roms in the list.
chris_ah1 said:
Big problem is the rate at which roms get updated.
But i see your point that it would be useful.
It's a helluva lot of work though given the number of roms.
Just off the top of my head I can think of 20roms.
And in the past chefs have been slow to submit their roms to a couple of the rom databases that already exist for swift comparison. I do think that this is better than one of those sites. You would have to get a team together and assign five to ten roms each to watch and update a spreadsheet because it's not going to work relying on the chef's input.
but it really might be useful - e.g. Topix 1.5.8 was based on 21898, but now Topix 1.5.9 is based on 21897 and without the weather function. The build might not be so relevant, but missing weather certainly is!!!
Then you also have the question as to whether to include the htcpedia-only roms in the list.
Click to expand...
Click to collapse
Well, I for one would gladly help with reporting from the roms i test, and it could be nice if a team where assembled to do so, because this whole forum is one big mess, where its impossible to get a little overview with all the threads and all those roms..
One thread to collect information about roms, builds, radios and so on - Would tidy up a lot! And, it would have to be a team of people who are able to stay objective, so that its not a contest of which rom is best..
If this is going to happen - pm me
acdbox said:
Yep, cant believe this hasn't been done yet, would totally reduce wasted threads
Click to expand...
Click to collapse
no it wouldnt, people would still jump the gun and start new pointless threads
Possible way to get started
This could be accomplished using a simple spreadsheet format.
One "Mod" would be in control of the master sheet that would be posted for download.
Team members would be responsible for one or more ROM's as they choose to participate. Submitted to the Mod.
They would get the official blank spreadsheet with labels from the Mod with directions for data consistency.
Only the Mod could add/change the format upon request of the team when new apps or features arise.
Data would be kept as simple as possible in the cells. X=includes, blank=not includes, version number, etc.
Each ROM version would have a column of it's own. Versions could be limited to "last three" or whatever.
Column would have date of posting to show how current the data was.
Most of the work would be front loaded to bring us up to date.
Cut and paste would make this fairly easy for the team and the Mod.
Comparison would then be as easy as reading a chart.
The end user could delete columns and compare ROM's he is interested in.
Start of Col. A labels (add your ideas and let's see if we can come up with a consensus.)
ROM Chef
ROM Name
Version
Build
Language
Radio Required (this could be RadA, RadB, Rad C to Rad F, all picked from a list at the bottom of the sheet)
Theme
Manila version
Cookie
MaxManilla
WM Version
Free memory after flash (MB)
App name 1
App name 2
App name 3
To app infinitum
Well its an awesome IDEA, I am ready to support by all means..!!!
I have already have a site dedicated to filtering roms located at www.xdaroms.com. I am open to ideas to make rom filtering even better.
Great idea!! This is a big hold up for a lot of users: they don't have time to try 20 ROMS, test them and figure out which they want... This is also a hold up for me, I can try some ROMS, like 3 or 4 but I want to know which ROMS I would have to start with... I am not going to take a "risk" flashing HSPL and not having time to install ROMS on it and so....
bowpay said:
I have already have a site dedicated to filtering roms located at www.xdaroms.com. I am open to ideas to make rom filtering even better.
Click to expand...
Click to collapse
+1 that was what I was going to say there is no need for this idea when there is already a comprehensive site that does it.
re xdaroms: at least for the hd2 there are quite a few chefs and roms missing. plus a distrowatch approach where you can see them all lined up is more handy with only one entry for the latest ROM visible.
This means there is room for a seperate glance-database.
chris_ah1 said:
re xdaroms: at least for the hd2 there are quite a few chefs and roms missing. plus a distrowatch approach where you can see them all lined up is more handy with only one entry for the latest ROM visible.
This means there is room for a seperate glance-database.
Click to expand...
Click to collapse
Part of the problem that any website or utility we have is the fact that cooks don't update forum(XDA) or rom(xdaroms) posts correctly. Some like to overwrite old posts or roms and update the build version which causes problems for viewing a history of build versions. I do encourage all the cooks to create new rom posts for each new build. I am also going to allow cooks to import an old rom as a starting point which should make the rom posting a little less tedious.
One solution for showing a build history is to do a group by on the list showing all roms for a paticular version however it will only work if cooks update accordingly.
I don't think this issue can be easily resolved untill I get more cooks on board on xdaroms.com and we can start to formalize a rom posting technique.
Again I am open to ideas and hopefully we can come up with a really nice easy to use way to publish roms.
bowpay said:
Part of the problem that any website or utility we have is the fact that cooks don't update forum(XDA) or rom(xdaroms) posts correctly. Some like to overwrite old posts or roms and update the build version which causes problems for viewing a history of build versions. I do encourage all the cooks to create new rom posts for each new build.
Click to expand...
Click to collapse
Hi bowpay, nice site - sorry I hadn't seen it before.
I think one of the greatest obstacles is exactly that - it is another site. Between XDA-Dev and HTCpedia, users and cooks have enough posts to contend with...
What you state above (quoted) could be mitigated by using a tabular structure instead of posts. New ROM versions would simply be appended to the table, with the old record remaining as a both a history and comparison. The old record would also be the perfect starting point for the cook to update the table (copy the column, paste as new column, update changed details). "Simples!"
I think cooks would find that easier to represent their new roms using this tabular format than constantly changing posts. The single proviso is that is must be complete and total representation of all variables that the ROM might have.
Please can any Chefs reading this, share their opinions/support and post whether they would adopt such a method for keeping users informed of their ROMs and new versions.
In any event, two things could happen:
The cooks utilize a common table for listing ROMs and versions. This would be analogous to a vendor providing a spec-sheet for their product.
Or (if not the cooks) users would create the records and constantly update the fields as they play with the ROM, use it and find the specs. This is comparable to independent reviewers detailing the specs of a product after the vendor has supplied it to them.
Either way would work and be greatly beneficial.
One field per record could even have a hyperlink for download and link to thread for images and discussion.
No objections to XdaRoms assisting the endeavour as it seems to be their speciality - it's all in the title! However for mass exposure and adoption it really needs to be on the cooks first-stop website. I think that is here...?
All the best,
Hirshy
ahirshfield said:
Hi bowpay, nice site - sorry I hadn't seen it before.
I think one of the greatest obstacles is exactly that - it is another site. Between XDA-Dev and HTCpedia, users and cooks have enough posts to contend with...
What you state above (quoted) could be mitigated by using a tabular structure instead of posts. New ROM versions would simply be appended to the table, with the old record remaining as a both a history and comparison. The old record would also be the perfect starting point for the cook to update the table (copy the column, paste as new column, update changed details). "Simples!"
I think cooks would find that easier to represent their new roms using this tabular format than constantly changing posts. The single proviso is that is must be complete and total representation of all variables that the ROM might have.
Please can any Chefs reading this, share their opinions/support and post whether they would adopt such a method for keeping users informed of their ROMs and new versions.
In any event, two things could happen:
The cooks utilize a common table for listing ROMs and versions. This would be analogous to a vendor providing a spec-sheet for their product.
[*]Or (if not the cooks) users would create the records and constantly update the fields as they play with the ROM, use it and find the specs. This is comparable to independent reviewers detailing the specs of a product after the vendor has supplied it to them.
Either way would work and be greatly beneficial.
One field per record could even have a hyperlink for download and link to thread for images and discussion.
No objections to XdaRoms assisting the endeavour as it seems to be their speciality - it's all in the title! However for mass exposure and adoption it really needs to be on the cooks first-stop website. I think that is here...?
All the best,
Hirshy
Click to expand...
Click to collapse
I hear ya I think that its going to be difficult for XDA to adopt this format due to not having things in place and being geared as a forum. I set out to help the XDA community and each day XDARoms is growing. We are going to make it easier to create forum posts by creating a BBCode Generator and our overall goal is to get cooks to post roms first at XDARoms then click the forum post generator link on a paticular rom. The post generator will generate BBCode or HTML for XDA or Pedia or any forum for that matter (Copy and paste).
Our niche is Roms so cooks will naturally want to post roms on the site because we geared the site towards cooks and it will simplify the rom posting for all websites. It may take time but I am dedicated to making rom posting as easy as possible. After all I am not just the president I am also a member (Hair club for men). lol
I really like where this post is going so any other chefs like to chime in and give us your 2cents? Much appreciated.
--Edit--
What you state above (quoted) could be mitigated by using a tabular structure instead of posts. New ROM versions would simply be appended to the table, with the old record remaining as a both a history and comparison. The old record would also be the perfect starting point for the cook to update the table (copy the column, paste as new column, update changed details). "Simples!"
Click to expand...
Click to collapse
When I get a little more time I will take a look at the rom posting process and use some of your suggestions. The database schema is all setup to do exactly that it will just take a little time to make the UI behave.
Well...I think it can be automated... is there a command line tool to extract all such information from a nbh file ? Can someone point me to anything similar ?
My idea : After a upload, automation extracts all such information and automatically appends to the spreadsheet/online sheet...so less work for the webmaster and the chef
ahirshfield said:
In addition, and perhaps more importantly, the ROM chefs have no standardised way to illustrate or describe exactly what their ROM is like to prospective users. The many posts and threads do not enable any form of comparison.
Click to expand...
Click to collapse
Why not use the wiki for that?
chris_ah1 said:
but it really might be useful - e.g. The build might not be so relevant, but missing weather certainly is!!!
Click to expand...
Click to collapse
Don't know how you came to that conclusion but you are certainly wrong. Don't spread wrong information mate.
I thought that this section was unique crap for Galaxy S2. Looks like we will have same **** soon.
anonymous572 said:
I thought that this section was unique crap for Galaxy S2. Looks like we will have same **** soon.
Click to expand...
Click to collapse
huh?
im yet to see what this section is for too
panyan said:
im yet to see what this section is for too
Click to expand...
Click to collapse
Yea ive seen it on other sections before, But I dont fully understand it
What the hell is 'original development' ??
What is the current development ? Un original ?
whats with the need to add un-necessary sub sections ? It just fuels confusion
Maybe "original" means "real". So there will be a chance to distinguish between cloning/adding/tweaking from development
Do we need / want it ?? I think we should open up a poll and pass the results on to the mod(s)
We had a similar thing in the HTC One S forums, Where they added a subsection for Tmobile Versions, It was totally un-needed as there were no differences between the 2 devices. We made a poll and the section got removed.
Sometimes these things do more bad than good, As if the flashing procedure isnt difficult enough already, What with the brickbug and all that.
If you think its a good idea to remove it, Ill open a poll before the section gets full with stuff.
Why not wait a little bit and see what it should be used for?
One Mod will explain sooner or later...
lets just hope its something useful
Is it so hard to understand? All stuff about original roms goes in there.
What do you mean Original ROMs ? Things like Stock TW ROMs ? Or does that include Custom ROMs too ?
Only in the SGS2 threads the 'original' section is full of custom ROMs and kernels too.
I mean this device is almost 12months old, We've survived without it.
Im just old fashioned Change freaks me out
Confusing?
Hate It?
Simply Don't Open It
anonymous572 said:
I thought that this section was unique crap for Galaxy S2. Looks like we will have same **** soon.
Click to expand...
Click to collapse
wish you could enlighten us on how it was a unique crap and a **** for s2 then?
original = stock = cooked roms
the other thread will be for "really" developed roms i.e, aokp/aosp/cm9 variants
So if some one builds a ROM based on Cynogen Mod from scratch..will it be in original section or since its from CM it will be in Development
btw this was the rule posted there
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)
i get the idea to separate the genuine development from the WinZip one, but it may not be that easy in practice to distinguish those lying somewhere in between
See Here
XDA, the moderators and the powers that be.... have been wrestling with trying to differentiate the Difference between the Code-writing Development and the Quasi-developers that use rom cooking tools.
To that end we will be going through the development threads in the next couple of weeks and moving the appropriate threads that meet the original code requirement to be placed in this new forum.
Please bear in mind that this is a "Work in Progress" and will take a bit of time to hone and perfect what goes where.
Also, please understand that this does not mean that some developers are on some special pedestal. That is not the case.
I will use an analogy to explain:
A music composer writes an original piece of music. The music composition may be awesome... but his performance of it, may not.
Such often is the case in developers..... often someone comes up with a awesome idea or new code application, but it often ends up being perfected by the use of others putting their creative spin on it.
That is the beauty of The Android Platform and ....XDA provides a fertile field for all to share ideas and collectively improve our experience
I hope this clarifys the potential questions
Thanks from the Moderators
Click to expand...
Click to collapse
At the end of the day everything is built from something else but what they are getting at is ROMs that are just other roms with maybe a new theme and tweaks taken from else where would just be in the normal development.
But if you came up with something new and different (not just a rehash of other peoples work) then it should go in original development
Now its starting to make sense, well ive always reverted to one particular rom (cleanote) so i guess i wont be affected.
maybe its for the best, there are a lot of similar roms out there so it might make life easier.
Im still adapting to the new xda theme, any more change after this and i might self destruct.
Want me to start a poll?
Sent from my GT-N7000 using XDA Premium App
azzledazzle said:
Now its starting to make sense, well ive always reverted to one particular rom (cleanote) so i guess i wont be affected.
maybe its for the best, there are a lot of similar roms out there so it might make life easier.
Im still adapting to the new xda theme, any more change after this and i might self destruct.
Click to expand...
Click to collapse
sahilarora2003 said:
Want me to start a poll?
Sent from my GT-N7000 using XDA Premium App
Click to expand...
Click to collapse
It makes alot of sense, will make it easy to find new and 'bigger' development work against the small tweaked roms which while important are starting to fill up the forum
It was tested in the S2 forums and has been rolling out XDA wide so theres not alot a poll will do, in honour of the hitch hikers guide of the galaxy, the plans have been on show for quite some time, if you can’t be bothered to take an interest in local affairs, that’s your own lookout.
I'm not sure why the decision was made to start dividing up the Android Development Forums into regular and "Original" versions but I personally feel like it's pointless and confusing, especially for people who have been using this site for several years.
At the very least they should be named more appropriately, the word original makes it sound like you're talking about modified stock ROMs etc..., i.e. what was originally on the device.
The entire point of an open source community is that different people can work on different things. I guarantee you that some of the so called "unoriginal" ROMs out there had just as much work and time go into them as anyone else's. So this is basically a just a slap in the face to anyone who is new to this type of development, it certainly would not encourage anyone to continue contributing and learning.
The bottom line is that the only "Original" Android ROMs come from here: http://source.android.com , even Cyanogen MOD is still 90% someone else's code/work. Essentially the whole thing amounts to elitist segregation, aside from Linus Torvald there isn't a person alive today that has any right to thumb their nose at another open source developers efforts simply because they didn't think they were worthy of being recognized.
Cool story bro
Well IMO I think it makes sense that its called original because its all based on aosp which is the original Android
Sent from my SGH-T999 using xda premium
eggydrums said:
Well IMO I think it makes sense that its called original because its all based on aosp which is the original Android
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Actually it has nothing to do with that, there are many modified stock ROMs in the original forums. Unless of course you're referring to those as well in which case EVERYTHING is based on the AOSP. In either case I hope you voted for option two
Darkside Agent said:
Cool story bro
Click to expand...
Click to collapse
Why didn't you vote?
Why would I?
Total waste of a thread...it will accomplish nothing and is just a rant from you
No one else has a problem with this, including people like myself who's work doesn't go in the original section
Plus this has been covered so many timez the Admins are bored hearing about it
Find something else to concentrate on, this is highly irrelevant
I agree with the OP.
Having two forums for the development of Android for one device makes no sense.
At the very least, a sticky at the top of every "original" forum needs to interpret why the forum is different to the standard development forum.
Sent from my GT-I9305 using xda premium
It seems that every time I've come here in the last few months everything is different. I understand wanting to 'spice it up' or 'make it organized'...but XDA was pretty much unchanged for a very long time, and now all these changes are more frustrating than helpful. In the end, I guess it doesn't make that big of a difference.
Let it be said that the first time I read 'original android development'...I thought of apps that were developed 100% by a dev...and NOT based on 'original android'.
I'm going to lock this up and explain the differences of development and original development.
Plain development: those are ROMs that are based off stock based ROMs or ROMs like cm with some apps or minor tweaks tossed in. Nothing that is brand new or has revolutionary features in. Team venom ViperS sense ROM is normal development if that ROM is based on a stock based sense ROM. Now if they brought that rom to a Samsung devices or non HTC phine, then its original.
Original development: any ROM that is compiled from source and has revolutionary features in it. Examples cyanogenmod, AOKP,PAC man, Paranoid Android, BAKED,Slim Bean etc. Those are all examples of original development. If someone downloads or compiles a source based ROM. Then adds their tweaks apps etc,that would be normal development. Basically original development is cutting edge stuff.
Sorry if its been answered already but I'd like to know what is the point of the two different development threads? THANKS
Sent from my Nexus 4 using XDA Premium 4 mobile app
OuncE718 said:
Sorry if its been answered already but I'd like to know what is the point of the two different development threads? THANKS
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
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)
Hope this clear your doubts..
Thank you for explaining in detail. You've definitely helped. I understand now!
Sent from my Nexus 4 using XDA Premium 4 mobile app
OuncE718 said:
Thank you for explaining in detail. You've definitely helped. I understand now!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for asking. It is very annoying to see wrong threads in the frong forum every day, it is a plus of work for moderators.
luiseteyo said:
Thank you for asking. It is very annoying to see wrong threads in the frong forum every day, it is a plus of work for moderators.
Click to expand...
Click to collapse
I definitely notice that (wrong threads in the wrong forum). I'm grateful for the response I've gotten. I thought I would of been flamed for not knowing the difference.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Just throwing this out there, but are CM and TW ROMs intended to be in Android Development and only ASOP be in Original Android Development? It's difficult to determine sometimes whether a ROM is a CM, TW, or ASOP ROM as they're kind of intermixed within the Android Development. I'd think that CM and ASOP ROMs should be posted in the Original Android Development forum?
i do know there's a directory, but thanks to everyone developing for the S4 on Sprint!
Original development is anything based off of google code. AOSP such as CM
Anything based off the sprint TW rom goes in the other folder.
Yes, there are some in places they shouldn't be.
Developers are not always clearly indicating what the base of their rom is.
ASOP. Is The Same As CM. I See Difference. But A Big Difference With TW. Is The Bomb!
Sent from my SPH-L720 using xda app-developers app
I think some of the ASOP/CM roms that are not in original are Kangs from someone else, or a different phone all together.
Just an FYI guys, it's AOSP (not ASOP). Android Open Source Project.
I like to think that ROMs built from source belong in Original Dev. That means CM, AOSP.
Everything else goes in Android Dev. But sometimes it can get a little hazy.
pulser_g2 made some good distinctions regarding what should go where:
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.
*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 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
A good explanation of Android Development vs. Original Android Development can be found here by one of the mods.
http://forum.xda-developers.com/showthread.php?p=41633683
Sent from my SCH-I545 using Tapatalk
my bad, that's my dyslexia kicking in there,
one thing that maybe as a suggestion is that the ROM devs can put in the subject line [AOSP] [TW] [CM], etc with what the base of the ROM is? I know there's not too many sprint ROMs out there, but those that do exist it's still a little difficult to search for each.