This is a short summary of some important general points for posting new ROM's.
It should be considered as an optional "add-on" to the general thread:
"Galaxy S I9000 Android Development **STICKY THREAD** Read here first!"
The number of man hours spent working and developing new custom ROMs are astronomical! So why then, is it that so few new ROMs are successful? Basically because of lack of information and poor public visibility/involvement of the developers themselves. It's just like in any other successful business, you have to make your product or service stand out from the rest. Either by making an amazing product or by being a great inspiration for others to follow. Here I will try to explain and list some fundamental ideas, in order to make your ROM better and more popular.
When a would be ROM flasher is looking around for a new ROM, he searches the web and the XDA-forums for threads, usually beginning with the text "[ROM]". Next he/she look at the FIRST page where the developer (and his/her team) is presenting the various features of their new design. What is presented there will often be a decision maker for whether or not someone wants to try it out.
There are a few things that consistently differs between "good" ROMs and "bad/poor" ROM's. These things are often and naturally related to the amount of information available around the ROM in question. Someone who have put down enough mind, sweat and hart into the production (cooking) of a ROM, would also like to share his/her effort in the best possible way, not minding writing a detailed and useful description about their product. The items found below are part of some of these things that do MAKE A DIFFERENCE.
- Primary Purpose:
Essentially a description why you want to provide this ROM and why you think it is needed. What are the main features and driving forces for providing this ROM?
- Ultimate Gaming Experience
- Super stability
- Super Compatibility
- Great Battery Duration
- Minimalistic User Interface (UI)
- Simple to use functionality
- Latest and coolest never seen before interface behavior
- Fully loaded with ultimate editions of absolutely everything
- Mobile Penetration Testing Platform
- or perhaps just for educational or experimental purposes etc...
- Up-to-date Maintenance:
That means an active developer (or group of) who are readily available to answer questions from users of all levels, new or advanced! Often that they should be inhumanly available at all times of the day & night!
- Up-to-date Firmware Release:
That means the the source of your ROM is preferably based on the latest, but publicly available code/firmware. Not on some hidden leaks or old hacked code. When I say "hidden leaks" here, I mean the kind where the origin of the code (compiled or not) cannot be verified or downloaded. (BMW doesn't make car/sales advertisements using 2 year old engines from unknown/secret sources!)
- Detailed CHANGE-LOG:
People want to know that what they flash on their phones, is as close as possible to what they would like to see and use. Also from a paranoia perspective most of us would like to know that it doesn't contain 3rd party or other strange applications that we will never use, or which will give us trouble when we want to add/update applications, at a later time. A description of the various applications is also very useful. Most people would wonder what the "DarkBotSendHelper.apk" is doing on a phone.
A change-log would ideally consist of a list with:
- Title: Change Date and the custom ROM Version the changes apply to
- Full application name
- Full application version
- Short application description
- Link to application source-code, if available
- Link to application on "Android Market"
- Reference to what hacks has been made, if any
- Reason for why the hack is needed
- Unresolved BUG-LOG:
A brief log of bugs and unresolved issues that affects the current release. It is hard to explain without cussing how annoying it is to flash a new ROM, just to find out that some WiFi issue has not yet been resolved, which was posted on page 456/1200! If people post bugs/issues, that cannot be immediately resolved, please add those issues to the BUG-LOG, on the front page.
- Screen Shots! Updated Screen Shots!
The importance of good screen shots can never be enough emphasized! Many ROMs are updated continuously and if the screen-shots doesn't match what the user installs, he's gonna go WTF!, and will start to peppering your support threads with questions about how to install this and that, and how to get the same themes you are using in those screenshots, or from another different ROM altogether! You wouldn't be able to sell a new BMW with a picture of an old Volvo, would you? So why do you think a ROM would be any different? Also include a brief caption about the essential feature(s) shown, for each picture.
- Detailed Installation Instructions
This hardly need more explanation apart for making sure you also say something about:
- WIPE/No-WIPE
- Bootloader Requirements
- Recommended Procedure
- Detailed Device Compatibility List
Yes, the same gross model name/number of a particular device, may very well have some minor variations that can render the device completely incompatible with software from it's apparent twin-brother. Or even certain Firmwares may not be compatible to slight manufacturing variation. See for example the "Samsung Galaxy S" with their sub-models GT-I9000(B/M/T), and to complicate things further, even within the same model there may be slight differences, like in the PCB of the USB-port of the SGS2 GT-I9100.
- Detailed Language Compatibility
What do people use their phones for? Communication! Sure, some use them as a game pad, but after all it is primarily a browsing and communication device. So if you can't use your primary languages with your device, it is useless! Although some network operators are only beginning to understand that most of the connected world is at least bi-lingual and often much more. Thus it is of essence that your phone's keyboard, screen-reader and web-browser can read, display and understand most characters and alphabets around. (I.e. I still fail to understand why it is virtually impossible to find a phone with Russian, English, Spanish and Norwegian keyboard layouts/character sets or at least let me select these my self!) In addition it is very confusing for a first-time ROM flasher to understand the need for all the various PDA/PHONE and CSC region settings, which are often modified and re-packaged for a well cooked ROM, and thus no longer adhere to the original regional code.
So when you cook your ROM, please provide as much information as possible regarding how the user can adapt their phone to his/her own languages. This information includes at least:
- What languages are available for basic operation (the operating system)
- What languages are available for the keyboard mappings
- What keyboard applications can use these languages (Swype, Samsung Keyboard etc.)
- Simple instructions how to include, use and set the phone languages
- List of Technical Terms and Definitions that describe the ROM
The world of mobile device development is packed by technical jargon and abbreviated terms. Many times they are also abbreviated and used in the wrong context, although some the community know what it means. Simplify your vocabulary and clearly define your terms and stay with community standard ones!
- General Presentation
Like any other business presentation, please skip the HUGE fonts in a zillion colors. Most of us are neither blind nor illiterate, but you may risk to come across as being both, with those type of fonts. Remember "KISS"? - Keep It Simple Stupid.
- SPELL CHECK!!
It's embarrassing and very annoying to read descriptions of how great, professional and how well maintained a particular ROM is, when the text is riddled with misspellings, wrong words and childish grammatical errors. Although most of us are very understanding that we are living in a multicultural and multilingual society, sometimes all I think about is, how a person who doesn't know how to spell check, could ever be able to cook a mobile phone ROM. Most text editors feature at least some basic spell checking, bloody hell, USE IT!
- CREDITS
Most of the Android development community is completely driven by voluntary and open source work. Make sure to include the correct credits to those persons who have contributed to the various info/hacks/software that you include in your ROM. Use a separate list for the credits, that include the name (handle) and how/what he/she did to contribute.
2 Good Examples:
http://forum.xda-developers.com/showthread.php?t=1350763
http://forum.xda-developers.com/showthread.php?t=1155776
Final Words:
It is very likely I have missed something here, or that you (as a developer or moderator) disagree on something I have written here, if so, please provide your constructive comments how I can improve this list and post.
In Great Expectations and Hope for Many New Amazing ROMs!
- E:V:A -
PS. This was posted in the "Developer Section" as it applies only to new ROM development threads, and I wouldn't consider this neither as "Q/A" nor "General". But if OP/MOD know of a better suited place, please just move it there...
Also I am not aware of a similar post to this one, even after searching XDA quite a lot. So if it already exists, it is not easy to find and should be reposted or stickied!
<Reserved>
@E:V:A
The only thing that I missed so far is a thread like yours.
Agree on all requirements of released software.
Sometimes I wonder how some "devs" priorities are stacked regarding quality control vs. early delivery on pay-per-download sites.
Not sure what is best place for this thread. Counting # of posts in General asking Q already answered in stickies, it's kind of accepted to skip reading what's there. :-\
Perhaps keep it alive as hottest thread here?
Tapatalked - There's a Thanks button somewhere
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Rahulrulez said:
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Click to expand...
Click to collapse
YES! Not giving credit where due is horrible, basically just forgetting all the hard work another individual has put in to the "feature" of your ROM. Also, this should probably be in general.
Related
First of all: don't worry. Everything you are used to is still here. Your username still exists, all the messages are still here, and we're all still here.
There are a few changes though:
You can set a country flag, as well as which device(s) you have and a home GSM-provider. These will be displayed in icon form with your messages. It's completely uncomplicated and much more fun if everyone participates. So please use the 'Profile' button in the menu above to set these things for you. They help others help you by knowing what device you have and what provider you are using.
Topics now have an extra property, which defines whether they are relevant for the original XDA, for the XDA II or for both. A small icon shows with each message. You can set this property when you start a new topic.
The separate XDAII board is gone. All messages there have been moved to the forum where they are most appropriate (see below). The fact that the messages were originally posted in XDAII now shows with an icon.
We now allow attachments, both in forum postings and in Private Messages, sized up to 50MB (!).
The boards have new names, and are slightly re-organized:
[list:42f131921e]
General
Current events, news, etc.
Using it
messages formerly in 'PocketPC' go here.
Not too technical, about use and peculiarities.
Unlocking it
formerly called 'Unlocking'
Networking it
formerly called 'GPRS/WAP settings'
Stocking up for it
formerly called 'Accessories'
Upgrading and modifying it
formerly 'ROM updates'
Hacking it
formerly 'Programmers corner' and 'Other techie stuff'
Anything but it
formerly called 'Off-topic'
[/list:u:42f131921e]
We currently use the plain-vanilla 'subSilver' phpBB style. Expect further changes to the way things look over the next few days. Please let me know by clicking 'PM' under this message if anything that used to work for you all of a sudden isn't working anymore.
Hope you like it...
New look
Sexy!
Wow ! well done ! :wink: certainly a lot of work ...thanks
Sure does and it looks good too! 8)
But found the following to be missing:
no USA T-Mobile listed under GSM Provider
no AT&T radio stacks listed under Radio Version.
Qman said:
no USA T-Mobile listed under GSM Provider
Click to expand...
Click to collapse
Whoops. Fixed.
no AT&T radio stacks listed under Radio Version.
Click to expand...
Click to collapse
We're still confused about all these Radio Stack Upgrade numbers. And if we are confused, imagine what that means for the poor folks out there. But I will include some more numbers tomorrow...
A couple of suggestions:
In the ROM Version setting of the profile, there should be a "kitchen" option for 4.00.16, since this is on at least one kitchen (perhaps "kitchen" ought to be a check box?)
I don't know that I would have chosen to have a merged 'update it' forum for XDAI and XDAII. Most readers are interested in info for one device and dont care about the other.
pdhenry said:
A couple of suggestions:
In the ROM Version setting of the profile, there should be a "kitchen" option for 4.00.16, since this is on at least one kitchen (perhaps "kitchen" ought to be a check box?)
Click to expand...
Click to collapse
Done. I might make it a checkbox later on.
I don't know that I would have chosen to have a merged 'update it' forum for XDAI and XDAII. Most readers are interested in info for one device and dont care about the other.
Click to expand...
Click to collapse
I was planning to create a one-click filter option for 'viewforum.php'.
Why damn, this blob-thing is ... growing.
As you may have seen the forum now has it's own hostname: forum.xda-developers.com. All existing links (/forum and /phpBB) will redirect to the correct thread or post on the new hostname (using a rewrite rule and sending HTTP 'Moved Permanently').
The uncompressed database for the forum is now 40 MB, the entire site is sending and receiving a few GigaBytes per day, to and from over 2500 unique IP-numbers each day.
Congradulation!
Hello
Well done and great work, keep it up.
thanks with best regards.
Othman
looks alrite but i miss the yellowy colour scheme now looks like every other forum on the web lol :roll:
how strange ...
the DB is only 40Mb ... this fits on 10% of my stamp size SD card ...
and yet, with just 2500 db-access (and how many posts? probably 100kb)
we get Giga bytes of traffic....
Just think how wasteful we're with current technology....
This goes double for a Pocket PC with two wireless communications,
100's of Mb of data, 400Mhz cpu ... and all that it does is displaying
who is calling your phone
Hmmm ....
[this is not a flame of the site or the PPC.... just a note on the status of the information/software age of the 21st century in general]
Looks
gazzaman2k said:
looks alrite but i miss the yellowy colour scheme now looks like every other forum on the web lol :roll:
Click to expand...
Click to collapse
No worries: this is temporary. There will be some proper design-work done on the entire site.
This is a good opportunity to say "Thank you" to Mario Giambanco, whose ideas and kind offer to work on the site prompted me to do some cleanup first, which resulted in the changes you see. Between him, myself, and hopefully some other volunteers we can now start to do a major overhaul concerning the looks and stale content of the main site.
The new 'main site' is going to be database-generated (from the phpBB database), and will have at least 'News' and 'FAQ' pages, pointing to topics on the forum. This will mean the 'main site' will be much more of an up-to-date tribute to the collective work of all of you on the forum, instead of a somewhat stale collection of some cool stuff we did way back. Creating layout in the way we did it before is just too much work.
Welcome to our new face
It looks very nice :lol:
But maybe we need added section: download & upgrade hardware ???
:wink:
very nice
Simply An excellent job
I preferred the old one. bah humbug
Thank You!
Thanks! For all the hard work it is much appreciated :wink:
Keep burning the midnight oil, it can only get better! ( like the XDA II )
Kind Regards, StayLucky Jim.
Hacking it ?
I written quite a few custom applications for the XDA and your site has some interesting infomation that has helped me.
I have replied a couple of times too with some code snipits.
All was very professional.
Now the Programmers Corner is under Hacking it, so I must of now become a Hacker. An interesting term, that I will have to add to my CV and see if it effects my future software appointments.
At last! Your decision to migrate to 2.0.6 is very welcome
If you interested - I can suggest two mobile adaptations for phpbb:
- read only version optimized for using as Mobile Favorites/Avantgo channels
and
- fully functional version for using from mobile devices.
These versions were developed and tested for one of the mostly visited (264,100 messages currently) PDA-related site in Russia http://www.handy.ru/board Unfortunately, all of the site is on Russian, but you may look though the following links just to smell it:
Mobile Favorites/AvantGo version:
Setup channels (Controls translation: forum name; timeframe; pictures (all/smiles only/none); link conversion mode; signatures on/off)
Ready-to-synchronize channel link (two days plus vacations, smiles only, links converted to text, without signatures).
Online mobile version: (banners should be visible from desktop PC only)
Forum index
Forum page
Topic discussion
All security is the same as in desktop phpbb version. Almost all functionality is implemented except site administration, advanced moderation panel (topic joining/splitting/mass deletes) and profile changing/private messaging.
These forum versions not include support for skins or language resources (sorry, but I develop them as fast as I can). So translation to English and slight adaptation to your mods (if any) needed. But I'm ready for this job.
The only main forum changes needed are:
- adding 4 lines to template variables array initialization;
- modifying 4 template files to add links to mobile versions;
Re: Hacking it ?
vangelderp said:
Now the Programmers Corner is under Hacking it, so I must of now become a Hacker. An interesting term, that I will have to add to my CV and see if it effects my future software appointments.
Click to expand...
Click to collapse
It seemed like a logical term to combine 'Programmers corner' and the little used 'Other techie stuff'. We think of the term 'hacker' as meaning a benign and very advanced programmer or techie, and not in any negative media-sensationalist terms. (Even though some of us do smile when we take the SIMlock off.)
Ofcourse if you think the rest of the world would see this differently, you're welcome to say 'Programmers corner' in future job applications.
I sincerely hope this linguistic issue will not keep you from continuing to benefit and contribute in the future.
First I would like to thank the whole forum (with few exceptions that I'd like to not mention here) for the past 2,5 years, which have been very educating for me regarding Windows Mobile as a system. During that whole time I have searched for the perfect simple-to-use, lightweight app for storing and retrieving a grocery list, yet unfortunately I have had to come to the conclusion that it does not exist to this date. There are some existing apps but these are either not simple to use or do not accomplish the simple task at all, or they are too heavy (requiring additionally the .NET framework to be installed for example, etc.).
The idea for the simple software is that one has a changeable groups and items of groceries, from which they can select the already saved ones needed at that shopping day (e.g. during a discussion with girlfriend), and later when in shop they can just check the ones they have already put into basket. I would like to see the person who will argue that it does not easily beat archaic mode of storing information, a.k.a. paper and pen.
I have found an app which, with some relatively small amount of effort can be rewritten to accomplish that task, this software is iContact AE. As far as I understand, there is judicially no problem using the source code from iContact AE as long as following the license restrictions (correct me please if I am wrong). Why AE? Just a selection based on the fact that AE has the most appealing interface and most settings. Of course, this could be a point of discussion, but so far it seems like the best choice.
CAB - http://icontactae.codeplex.com/releases/view/28951
Source - http://icontactae.codeplex.com/SourceControl/list/changesets
I created a possible, chronological tasklist in order to get from iContact AE to the shopping app, whatever it will be called (name suggestions also welcome in due time). Also, I already have a pretty clear vision about
Discuss the usability and feasibility of the selected software / it's source code and it's alternatives (as far as I remember there was the original iContact and some other derivate version).
[*]Create, discuss and review static prototypes of the interface (basically screenshots of each view).
[*]List the requirements to be implemented (or removed).
[*]Code in / remove code according the list from previous task.
[*]Create skin and graphics.
[*]Clean up rest of code, remove unnecessary parts of it (to make it more light).
[*]Test and review changes.
I can either take lead, perform or participate actively in the tasks that are listed green. I only need a competent C++ coder who can help and thinks this is a great idea.
The changes needed to the existing source code do not seem to be much at first glance, but of course as I cannot code in C++, I could be wrong. I just looked at the parts of code where to change the tabs and queries to storage files.
So there, got it off my chest. Any C++ gurus missing a simple, convenient grocery app?
OK, I will put this in another way. I will personally contribute $50 (via PayPal or if EU country, via transfer) to the coder - provided that the end result is according to the requirements, which we will agree forehand. If anyone wants to join in with contribution, You are more than welcome.
aiiro said:
OK, I will put this in another way. I will personally contribute $50 (via PayPal or if EU country, via transfer) to the coder - provided that the end result is according to the requirements, which we will agree forehand. If anyone wants to join in with contribution, You are more than welcome.
Click to expand...
Click to collapse
If I had money I to would offer some.
It's no wunder WinMo is falling behind no one wants to create apps even when offered a straight cash deal.
Amen to that. I was actually reading this and took a good hour of researching to see just how hard it might be and how time-consuming it might be. I would have loved to take this on...but alas, It would split me way too much. I am already working on my FFP_LS Pro 2.5 Improvements (Major Major improvements...I am practically re-writing the app), I am starting work on a game I plan to release (Its a rather popular game I have yet to find for WIndows Mobile), and I already volunteered to work on the Boggle Clone for WinMo ... so I am already pretty split as it is. heh...if I find free time, and nobody has taken this on, I will probably come back and make this my next project
Sorry though...I do hope some developer comes around to assist!
Thanks for Your support. I thought that I don't need to subscribe to my own threads in order to get a notification if a new post is made, but I was wrong. I certainly didn't get one for Your post. So, sorry for the late reply. I will subscribe to my own thread now
Request 1: Add HTML Tidy to the xda wiki stack
Template:Navbox @ Wikipedia said:
Using this template on other wikis requires HTML Tidy to be turned on. A version that does not require Tidy can be found at Wikipedia:WikiProject Transwiki/Template:Navbox. (That version generally shouldn't be used here on the English Wikipedia.) More detailed information on copying {{Navbox}} to other wikis can be found on the talk page.
Click to expand...
Click to collapse
I've been doing a LOT of work adding stuff to the xda wiki, but I've hit an impasse, some of the most complex templates used on Wikipedia depend on it being 'scripted' with HTML instead of pure wikimarkup.
The main example is Template:Navbox. While this specific template does have a pupre wikimarkup equivilent (if it even is an equivilent, it's not maintained at the level of the normal one). The other templates I wish to use dont have equivilents.
Template:Navbox subgroup is the one (among others) that I wish to add in but cant because it depends on HTML Tidy. The Template itself is already on the xda wiki, but if you attempt to use it it's completely broken.
I cant say it's as simple as "install on server and turn it on" but the fact of the matter is that without it most of the fun/magic stuff on wikipedia cant be brought over to the xda wiki.
Some examples of recent stuff i've made (for reference):
Samsung Galaxy S Series Navbox
Samsung Galaxy S II Series Navbox
New Samsung Portal on Main page
Entirety of Dell devices page
If you look at the several navboxes I've made they have hacks in the code to get around the fact that I'm just a normal level editor.
Request 2: We need MOAR editors!
Also this doubles as a request for more editors on the wiki: XDA is the largest android development based site on the internet, yet here we are weeks after the release of the Galaxy Nexus and Galaxy Note and the pages didnt even exist until I made stubs for them.
As of this past quarter I've generated more edits then possibly nearly every other user combined, but there's only so much I can do at this point by my self. (With my primary style being to organize page layouts and tidying stuff up vs writing new content for devices)
[Edit count itself is a bad metric, but edits that arnt mine only number in the dozens a month]
Sure it's reasonable for minor devices and varients to be stubs, but the Note has sold over a million units and yet not a single person has even bothered to make as much as a scribble on the wiki about the device. That's just an example, but ultimately if this were wikipedia, the amount of pages rated 'good' or higher would only number in the dozens. (There's also the fact that my belief is that it's a bad idea to add anything intensive for a device you dont own, standard fare on one device can super-brick another due to quirks)
It's a rather sad state of affairs that for such a large web site with 22000 active users at any one time that there's not a single good consistant repeat editor besides me.
Edit: changed wording to not be inflammatory
Request 3: Turn on Subpages on the main namespace
Mediawiki:Subpages are by default enabled on the template and user namespaces, but not on the main namespace. I believe it's done this way because of editor policy and not technical reasons.
The xda wiki would HEAVILY benefit from having it enabled since it already currently manually uses them, the previous example of:
Samsung <Series>/<model number>/article has long existed this way but without the automatically generated anchors.
The majority of pages are already ready to accept it, it might simply need to be turned on.
XDA Wiki
TheManii said:
there's not a single good editor besides me.
Click to expand...
Click to collapse
IMHO that is a rather sweeping statement and is likely to put off anyone from editing the Wiki. I would dispute even your claim as a good editor would not make sweeping changes to categories without discussion on the pages involved. Should I just "undo" them?
XDA has a problem with repetitive questions leading to user dissatisfaction with overlong forums and the loss of good developers such as AdamG.
One solution may be to create a FAQ Wiki for any thread over a certain size (for example 1,000 posts) and automatically link to that thread at the top of every page and above the reply box.
Cheers
Tom
It is sweeping, but the fact is there arent many repeat editors, many devices havnt not seen edits in months because a great deal of the changes dones are a one-time batch job with a single theme.
I'm not at all saying that the other editors are bad, though yes that what the impression was (and perhaps I should have worded it better). I'm saying that few wish to stay with it for the long-haul.
There's few editors that consistantly return to add/update/expand artitles for their own devices or other devices. That's my main issue. I actively want to be proven wrong in this regard, I'm inviting other to prove me wrong. I myself am somewhat guilty of this myself, I primarly concentrate on the dell devices, but I've kept them very up to date for the previous year.
One example I have issue with is: Acer A500 -xda wiki the entire page are just forum links. I have no issue at all with the contents of the posts (just as much my opinion on them is irrelevent) but the fact they are just links and not part of the article. The fact it's not on the wiki means that other editors cannot make changes themselves, which rather defeats the point of the wiki, which leads to,
The other issue is, unless the OP is excellent at keeping the thread organizied, you often have to wade though the entire thread to keep up to date. With a thread with +200 posts even if you wanted to it's a huge effort to do that. Even in the most complex of topics, they can be broken down a couple bullet points and approx a paragraph each to elaborate. There's also 'bad' advise that doesnt get edited away on topics ('bad' as in it may simply be the case that it was the right thing at the moment but there was eventually a more 'correct' method discovered later and the original 'bad' one is still reposted for whatever reason)
I could copy the posts onto the wiki verbaitm, but you really should have the poster's permission, what if the poster isnt active? It would be a bad idea to paraphrase advise/guides without context, what if you remove an important small detail. The right way to be to frequent the device and get context, but that triples the amount of work to do so properly.
It's no secret that there's always users that refuse to read topics and simply skip straight to posting repeat questions. Short pages with clear instructions are much easier to recommend then having them read though dozens and dozens of posts (which they skipped as they posted without reading in the first place)
Discussions dont really work on a wiki, esp one without consistant-repeat (or even repeat) editors. There's a fair amount of edits for various devices, but there are obviously more devices then editors. Lets walk though it: I want to make an edit, do I post it on the topic's talk page? Short of doing so on wikipiedia proper on a popular change, you wont recieve much feedback.
Do you make a post on each of their device's forums? XDA has sub-forums for each device, but not really a sub-forum for the family itself (back to the SGS/SGS2, there's the main device's subforum and each varient's subforum but none for the entire family, i think) That means making dozens of posts to talk about each major change.
What if it's an old device such as the winmo devices? The HTC HD2 is the only one left on the active part of the xda forums, because it's obviously not just a winmo device now. You're going to have to wait a very long time as they naturally only get a couple posts a month now.
Just as much, unless a mod/admin states to the contrary, you can always assume Wikipedia:Be Bold is implied to apply. I honestly have no issue if my edits are reverted if they are constructive reverts, as that's how wikis work.
If anyone has a issue with the edits I make, you're welcome to discuss it with me and hopefully we'll find a middle road.
Also I've made a reply on User_talkaveShaw#Page Name & Categories (as a fun note: & is translated to _.26_ in links while / isnt, though mediawiki has no issue with either of them, though you cannot directly use & in page names while you can use /) You should read it if the critisim is directed towards me.
tl;dr prove me wrong, Be Bold, help make the wiki better
Edit: HTC_HD2 - NexusHD2 ICS CM9 FAQ is an excellent example of why things should be on the wiki as articles instead of just merely links to a thread. It's about 3 pages of topic points and contains the majority of the topic points instead of having to read 225 (currently) pages to get the same info. (Also, just as much if I inadvertently remove valid content, revert/add it back! That was not my intention, everyone makes mistakes. The xda wiki is pretty well off in that it has little/no intentional vanadalism, you can always assume an edit is in good faith, I dont recall more then 1-2 legitamitely bad edits in nearly a year)
I've asked someone to look at Request 1.
I'm not sure what can be done about Request 2, if people don't want to maintain it, we can't make then
Thanks!
I dont really expect req 2 to be fullfilled in any real manner. Just pointing it out.
Added request 3: enable subpages on main namespace
TheManii said:
Added request 3: enable subpages on main namespace
Click to expand...
Click to collapse
Our server admin has told me this has been done.
Dave
I can confirm it's on now, all the subcatagorized pages seem to be working great now
TheManii said:
I can confirm it's on now, all the subcatagorized pages seem to be working great now
Click to expand...
Click to collapse
Thanks
Dave
If you’ve spent any amount of time on XDA, you’ve heard of XDA Recognized Developer Cyanogen or the nearly ubiquitous CyanogenMod. In fact, chances are that at you’ve either run CyanogenMod on one of your devices at some point in the past, or you’re running it (or a kanged version) now. In many ways, CyanogenMod represented all that was good about Android Open Source Project (AOSP) and proceeded to go where the carriers and manufacturers were unwilling to take their devices. Along the way, Cyanogen inspired developers everywhere to reach for what was previously lacking in the Android community.
Cyanogen also saw an emerging trend which he wasn’t too happy about – the term “chef” being applied to the Android custom development scene, along with the emergence of the so-called “WinZip ROM.” So he created a thread back in 2010 to speak to this emerging trend and offer up some advice. The overriding theme was that contributing quality was far more important than contributing quantity on XDA.
He had this advice to offer for those looking to make their own Android ROMs:
Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works….. Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that s**t on your resume. There is a *ton* of information out there but any kind of “step-by-step rom cooking guide” is going to be a complete fail- it’s too broad of a subject.
As XDA has grown right along with the meteoric rise of Android, so has a desire of users to create their own ROMs, kernels, themes, and so on. Much of this work classifies as “original development,” but there’s been a growing trend to what many are calling “derivative development.” This category covers most of ROMs based on stock releases from the manufacturers, applying patches and scripts aimed at optimization, theming and/or removing stock applications, and using “kitchens” that run a stock release through a list of scripts and then repackage as a recovery-flashable update.zip. This is what Cyanogen was expressing frustration about—shortcuts being taken to achieve a product that differs only slightly from stock (derived) and pushed out instead of building from source and delving into the core of Android and making something truly original.
XDA-Developers exists first and foremost for developers. It’s at the core of who we are; it’s in our blood; and it’s in the air we breathe. There is a place for derivative works—they provide an entry to the scene which can help to introduce people to the wonders of Android. But let’s not stop there. Don’t be satisfied with just creating yet another derivative of someone else’s work. Instead, follow Cyanogen’s sage advice and learn about Android from the ground up, and create something truly original and innovative.
Here are some locations to help you on the path to learning about Android and contributing to the community as a whole:
Android Developer Guides
Working with Android Source
Downloading the Android Source
Git Tips and Tricks
Building CyanogenMod
Pro GIT Book
source : http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/
original source : http://forum.xda-developers.com/showthread.php?t=667298
Well put and a great reminder for all.
Side note - What is with all the "reserved" posts? This has to stop, its just spam. I will delete all posts on sight and repeat offenders will have their ability to post removed.
Sorry to divert the topic.
andyharney said:
Well put and a great reminder for all.
Side note - What is with all the "reserved" posts? This has to stop, its just spam. I will delete all posts on sight and repeat offenders will have their ability to post removed.
Sorry to divert the topic.
Click to expand...
Click to collapse
moved and cleaned...nice..
i was also curious of the so many reservations
anyway, the message is clear..
Dev = Creator(File Pusher)
Chef = Indirect Piracy? LOL
For the chef thing is my opinion since its just improvising, not really creating
I decided to make this thread to not only act as a little competition for forum users, but also to help out some users who are looking for working configurations that'll help their phone run the way they want. Essentially, the way this works is that you must post in a specific format as follows:
Model (I assume it'd be the T-Mobile one but you never know!):
Recovery:
ROM:
Kernel:
Mods:
Benchmark Scores:
Longest Battery Record:
Camera Application (if going for Best Camera Performance):
Misc:
As many of us know, pics or it didn't happen, so if you make a claim better bring on the evidence! The Misc category is where you can add any apps or launchers or basically anything you feel is a key part to your phone's configuration or helpful in understanding how you achieved your numbers. Please include all version numbers for all necessary categories such as recovery, kernel, etc. I will try to monitor the thread as much as possible and update the post after this with winners! The categories to have titles won in will be: Best Benchmarks, Longest Battery, Best Camera Performance, Most Creative Theme, Most Simple Theme, and WTF (for those people out there for those phone's that simply just do not make sense). So have fun guys! :highfive:
[NOTE] Category winners will be chosen by me until I can figure out a simple voting procedure, if you have a suggestion on how to do that then please PM me as not to flood the thread with unnecessary comments. :good:
RESERVED