Related
Hi,
Have spent a great deal of time browsing through the site, and trying out some of the ROMs. Which has led me to the following...
The Company I work for has deployed a large number of XDA-II's (Himalaya), and we've encountered a number of reliability problems with them, not to mention users unable to keep the devices charged.
The consequences of these problems are: 1) Lost software installs and 2) Extra support time.
We've also found the O2 active UI to be a right royal pain in the ar5e!
So, having been playing around with ROMs, I have an idea of what is possible. But, to date, I've just not been able to find exactly the ROM I'm looking for. I'm quite happy to sit down and try and figure things out for myself, but it's quite difficult to try and find a good chunk of spare time.
So, here's the point of my message.
If I can identify the components I need to be installed within a "special edition" cooked ROM, would someone be able to help me build it? I'm basically looking for WM2003SE, so that the screen can be flipped into landscape - or a third-party progam to do that, a wireless email client that I will provide, backup software that I will provide, all the usual hardware stuff (BT, camera etc), no O2 UI (Hoorah!), and maybe one or two other packages, and as much storage/memory available as possible, and, of course, the ability to add a splashscreen. That's it - nothing too out of the ordinary. All of the additional software will be licensed.
So, that's my idea. What do you get in return? Well, I'm more than happy to donate to the site, and, come to some arrangement with anyone that is interested in helping - perhaps some hardware/software etc.
This would save me a lot of time, and be quite an interesting project - to see so many devices get a decent upgrade, and one that helps reduce support overheads.
Please PM me if you are interested.
Thanks.
Vince
well you can
select the win2003se rom you want and put the rest in a cooked extended rom that was what i did i put all cabs i needed in extended rom if the device gets hard reset it will install everything there
the config file must have the names of course
you can get some of the setting there too like operator settings
you can allways donate to xda-developes....lol
PS ...i m not part of xda-developers or in any way associated with them just a user who is glad they existed.
Please will someone post ONE rom without removing .rgu files before posting.
I just want to cook my own ROM.
...
Cmon, guys
I was about to create the exact same thread.
Until a few month ago, I used to re-cook the roms I downloaded here to get rid of the unusefull applications and add my customisation.
Now that wm6.1 is out, I wanted to switch to it but I was unable to find a rom with this f*** dsm and rgu that are mandatory for a clean cooking.
Cookers, why the hell are you removing this files ?!?
Is it to save a few kb which is stupid regarding the pain in the ass trying to improve the rom after this suppression ? (Or did I miss a major revolution in the cooking process that make them unusefull to create packages and registry hives ?)
So could anybody give an advice for a good ROM (light and fast) where this RGU and DSM remains ?
Exactly,
recently I switched from Prophet from Trinity.
I couldn't wait to compare its performances to previous device, but was unpleasantly surprised to see that almost NONE of the ROMs posted in Trinity section is editable.
On the contrary Prophet ROM section is way more advanced.
In the end, I thought that ROMs are (at least ones posted here) kind of public property, and that the they shouldn't be locked (by removing rgu files prior to posting, or putting the time code on them!!!). If you want to sell them - then go apply for job at Micr0s0ft.
On the other hand - I can understand that someone is affraid that someone will overtake his/her work and claim it as their own. But again, we are here to help to each, and I never personally published any of my own modified ROMs - due to respect to the author. It would be good practice that someone who makes modification - always mentiones which ROM is used as a base for development.
Just imagine what would happen if Bepe, Mamaich, Olipro and other real developers made their tools just for themselves!
Cheers!
There's something I can't understand...
Why do you need to edit released ROMs, when you have access to ROM kitchens?
My best guess is that you don't want to spend endless hours figuring out the best tweaks, solving problems, creating packages, and so on, when you can have it all done by others.
Remember one thing:
None of the cookers here are releasing ROMs for profit. We do it as courtesy, to help the less skilled, so they can also have a more updated and efficient system running on their devices.
Cookers aren't by any means obliged to reveal their little secrets, which for you may seem trivial, but in fact, it may be the sum of many hours testing.
Cooking with a untouched kitchen is a good way to get to know how things work, and to improve your own cooking skills. So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not.
It's the cookers choice to release a ROM as he see fit, and it's the user choice to use it or not.
I don't have a problem with the so called "competition", since I'm not here to compete. I'm not here to win, rather to provide an alternative. But it's hard for me to give up my work just like that.
I wouldn't have any problem providing a kitchen, but unfortunately my main source is XDA-Developers, so I also rely on others to get a base for my work. My skill level is not yet that high, but I'm always trying to improve myself.
I'm sorry if I'm offending someone, but I needed to speak my mind...
FInixNOver said:
There's something I can't understand...
Why do you need to edit released ROMs, when you have access to ROM kitchens?
My best guess is that you don't want to spend endless hours figuring out the best tweaks, solving problems, creating packages, and so on, when you can have it all done by others.
Remember one thing:
None of the cookers here are releasing ROMs for profit. We do it as courtesy, to help the less skilled, so they can also have a more updated and efficient system running on their devices.
Cookers aren't by any means obliged to reveal their little secrets, which for you may seem trivial, but in fact, it may be the sum of many hours testing.
Cooking with a untouched kitchen is a good way to get to know how things work, and to improve your own cooking skills. So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not.
It's the cookers choice to release a ROM as he see fit, and it's the user choice to use it or not.
I don't have a problem with the so called "competition", since I'm not here to compete. I'm not here to win, rather to provide an alternative. But it's hard for me to give up my work just like that.
I wouldn't have any problem providing a kitchen, but unfortunately my main source is XDA-Developers, so I also rely on others to get a base for my work. My skill level is not yet that high, but I'm always trying to improve myself.
I'm sorry if I'm offending someone, but I needed to speak my mind...
Click to expand...
Click to collapse
+1 you've said everything
Hi, FInixNOver,
well I am glad you replied. Although better anything than nothing.
Watch now:
"Why do you need to edit released ROMs, when you have access to ROM kitchens?"
Well, why do you need kitchens (and tools) - why don't you develop them by yourself?
You say
"So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not".
No one said they have to. But after hours of testing and achieving something which only you succeeded to - to keep it as a secret? And not share it with the "less skilled" on the forum? I understand if someone invested hours in artistic-visual development of the ROM - everyone will recognize that as effort - but removing .rgu files used for creating the registry during ROM building - is creative???
Or when I dump the ROM and see the folder named "Don't touch my ROM"?
Cmon, thats pure blsht!!!
What if someone makes "Don't touch my Hard-SPL"?
phnikola said:
Hi, FInixNOver,
well I am glad you replied. Although better anything than nothing.
Watch now:
"Why do you need to edit released ROMs, when you have access to ROM kitchens?"
Well, why do you need kitchens (and tools) - why don't you develop them by yourself?
You say
"So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not".
No one said they have to. But after hours of testing and achieving something which only you succeeded to - to keep it as a secret? And not share it with the "less skilled" on the forum? I understand if someone invested hours in artistic-visual development of the ROM - everyone will recognize that as effort - but removing .rgu files used for creating the registry during ROM building - is creative???
Or when I dump the ROM and see the folder named "Don't touch my ROM"?
Cmon, thats pure blsht!!!
What if someone makes "Don't touch my Hard-SPL"?
Click to expand...
Click to collapse
You may be right about the tools, without them it would have been very hard to get many of the tasks completed successfully and probably I wouldn't have even started cooking.
But, how on earth would you be able to build a ROM without a kitchen?!! You certainly cannot make an omelet without the eggs, now can you?
And I never demanded any tools from anyone or even kitchen. When I have a request or something to say, I usually politely ask or give a suggestion.
You should try to create you own ROM before making assumptions about what cookers should keep a secret or not. Then you'll notice that cookers help each other whenever possible (e.g. when something important is fixed).
And I do share my findings, mainly in my ROMs obviously!! That doesn't mean I have to expose all my work. It's necessary to research a bit. You'll find it rewarding.
Also, almost all of the art work in my ROMs is my hard work, and it's painful to see it scattered around without so much as a credit (I'm not asking to be paid or anything). So, why not protect my work?
Tweaks? That's a whole different subject, the ones you may find helpful other may not, it's up to each one to use the one that will best suit your needs.
You will also learn, that most times, a cooker will not mess with the RGUs in a kitchen. Instead, a brand new package is created just for registry tweaks, this way the changes are easily tracked down. This being said, I can easily build a ROM, that you'll be able to dump and repackage, but you won't find my registry tweaks. Would that work for you? Because, I find this process to be more deceiving than providing the ROM without RGUs and DSMs.
You're making it sound like I say less skilled persons in a bad way. Every user is a potential cooker. Everything is available. Sometimes, you just have to dig a little deeper.
Some find it to hard to learn, others get what they need from the available options, others, well... they're just too damn lazy. But hey, everyone's got their reason, and who the hell am I to judge them?!!
"Don't touch my hard SPL"
This is a funny one!!! You have quite a mess in you attic. You're mixing 2 very different subjects...
I know one thing!! I wasn't fully satisfied, with the options I had, so I decided to get my hands dirty and do it myself. I learn everyday, and I have yet plenty to learn.
My conscience rests easy, as I've made some contributions, maybe not very important ones, but never the less...
I released some fine ROM(not perfect, I'm well aware of that) if I may say so, and made some users happy.
I don't want to start a war or anything. This all subject of protecting or not the cooker's work has already been extensively discussed, and I gave my opinion about it.
In the end I can say:
I've paid my dues. Have you?
OK, I wont argue anymore but will not change my oppinion either.
I am closing this thread by posting HTC Trinity - Complete Cooking tutorial for begginers in the forum.
Maybe my debts will be payed now!
Now let us be more useful and post comments and EDITABLE ROMs!
In the end - I would do that for you as a forum member
Cheers!
FInixNOver said:
There's something I can't understand...
Why do you need to edit released ROMs, when you have access to ROM kitchens?
Click to expand...
Click to collapse
To my mind, kitchen are not made to cook a rom but to learn to the newbies how it works. It's far from beeing a good solution to realy cleanly cook roms (often buggy, not possible to have an up to date OS, ...). However it's really instructive and it's great work from the creators of theese kitchens.
FInixNOver said:
My best guess is that you don't want to spend endless hours figuring out the best tweaks, solving problems, creating packages, and so on, when you can have it all done by others.
Click to expand...
Click to collapse
It's right but it's exactly the point of development, saving hours by using existing libraries to be able to create something realy new that's not another copy of something existing.
Do you know the meaning of a Community of Practice or did you forgot the first function of this board ?
Moreover, you must know that it's way more painfull to cook a rom without kitchen than with a kitchen, even if the result is best.
Finally, this kind of "protection" is quite useless as the rom is still dumpable and editable, it's just a bit more painfull as you need to find the missing files from other roms or from packages.
I was curently working on a rom editor to enable cookers to save time cooking rom with a GUI but I think I will stop the project for a time to try to develop a tool that will be able to recreate the missing dsm, rgu and packages.sof to proove:
1) I'm not a lazy lamer
2) Sharing knowledge is much more profitable for the community than keeping it for itself (even if it has already been done a hundred of times by bepe and so many other on this board)
However, don't think I don't respect cookers work but I think this point stands against this board main function, this will be my way to pay my dues
@phnikola : I found this rom http://forum.xda-developers.com/showthread.php?t=391450&highlight=KAEW working quite well (light, fast, stable and recent build) where the rgu, dsm and .sof are still existing. If you want to use another ROM, just copy all the rgu, dsm and packages.sof from this one to the dump directory of the other rom
Peace
@ phnikola
I welcome your gesture and I'll be more than happy to make some contribution, to make it the best tutorial that I never had.
@ tonio94
Well, my understanding of kitchen is the set that includes the ROM files, packages, tools (whether they are batch files, or fancy tools) used to edit and build the ROM. As I say that's only my understanding of it. I may as well be wrong. And I'm very thankful for the effort and hard work put into developing all the tools that can make our cooking experience so much better
I think you're missing my point. I'm all in favour of sharing. And I try to do it as much as I can, but you may also be aware that even though programmers may use the same libraries, they often protect their final work, so that other cannot take credit for it.
The same happens with ROMs. Altough I'm using the same base as many others to create my ROMs, the final result is different from cooker to cooker, and I can only speak for myself when I say that the main reason for protecting my work is to avoid having my work ripped off.
I have absolutely nothing against making available the kitchen as bug free as possible, so that everyone can make their own customization of it.
I'm well aware that this protection can only slowdown the process of editing the ROM, but it's a way to make it a bit harder for others (I mean only the ones whose sole purpose is to take someone elses's work as their own), to take my work.
Sometimes, just because of a handfull of gready people that take other people work and make it their own without any credits, the rest of the community ends up paying for it.
I wish I had some developer/programmer skils, so i could make a bigger contribution to this community, but unfortunately I've never learned that (however I'm hoping to work on it someday).
In the whole spirit of sharing, I'm going to release some treats, just to prove that it's was never my intention to undermine the work of new cookers (what am i saying?!! I'm also a new cooker!! and a noob for that matter ), I just wanted to protect myself.
FInixNOver said:
In the whole spirit of sharing, I'm going to release some treats, just to prove that it's was never my intention to undermine the work of new cookers (what am i saying?!! I'm also a new cooker!! and a noob for that matter ), I just wanted to protect myself.
Click to expand...
Click to collapse
I have a respect to that, mate
I think your ROMs are among the best. Keep up the good work
Cheers!
tonio94 said:
@phnikola : I found this rom http://forum.xda-developers.com/showthread.php?t=391450&highlight=KAEW working quite well (light, fast, stable and recent build) where the rgu, dsm and .sof are still existing. If you want to use another ROM, just copy all the rgu, dsm and packages.sof from this one to the dump directory of the other rom
Click to expand...
Click to collapse
Thanks a lot, tonio94!
Will try it as soon as download completes
FInixNOver said:
@ phnikola
In the whole spirit of sharing, I'm going to release some treats, just to prove that it's was never my intention to undermine the work of new cookers (what am i saying?!! I'm also a new cooker!! and a noob for that matter ), I just wanted to protect myself.
Click to expand...
Click to collapse
Hi FInixNOver
I don't normally get involved in these threads, but once again I have to admire the way you avoid an argument with yet another member of the community who seems to just take, take, take.
Had he and others bothered to have a look at not just the quantity and quality of ROMs you produce for everyone but the feedback and replies you give on a daily basis to people with problems, maybe he would have a clearer idea as to who the givers are in this forum.
You guys give up your time and effort for free so that others (including myself) can benefit and enjoy the fruits of your work. To show any anger or frustration is ridiculous. At least 70% of the people in Trinity forums have tried and enjoyed your ROMs. And yet still they expect you to give more. Incredible...
Mattster.
Mattster_spv said:
Hi FInixNOver
I don't normally get involved in these threads, but once again I have to admire the way you avoid an argument with yet another member of the community who seems to just take, take, take.
Had he and others bothered to have a look at not just the quantity and quality of ROMs you produce for everyone but the feedback and replies you give on a daily basis to people with problems, maybe he would have a clearer idea as to who the givers are in this forum.
You guys give up your time and effort for free so that others (including myself) can benefit and enjoy the fruits of your work. To show any anger or frustration is ridiculous. At least 70% of the people in Trinity forums have tried and enjoyed your ROMs. And yet still they expect you to give more. Incredible...
Mattster.
Click to expand...
Click to collapse
Man, I already posted that his ROMs are excellent, but you have a real problem with your selfesteem. Anyway we came to agreement - so be more useful and post in another thread
It would be great building a rom based on the Benchmarks of the roms wich you can find here http://forum.xda-developers.com/showthread.php?t=406640
The Chefs need to work together and exchange what they did in specific to get good scores in the sectors they lead and have best results.
I would exchange my knowledge. Please join this Project and lets make a fantastic rom.
What do you think about this ?
I think about a meeting on a chat with only developrs and we exchange our thoughts and knowledge.
Do you think it'd be that simple for everyone to agree upon which tweaks to enable, which ones leave out, as well as applications?
Some of them are standard procedure, but the rest depends on each different chef.
The first question would be: a light ROM, or a full-feature packed, at the cost of performance?
For my part, I usually cripple most of my ROMs to the mininum, adding afterwards only the apps I need.
Registry tweaking also is quite aggressive.
I don't like all the bloat in most of the ROMs, but that's what most users are looking for.
As for eye candy, I never integrate it at the cost of performance.
So the question would be: what do CHEFS want VS what do USERS want.
If you want to take this to the next level, you'll have to set a date for the meeting.
I'd recommend IRC, since not many ppl use jabber. MSN sucks, so...
adwinp said:
Do you think it'd be that simple for everyone to agree upon which tweaks to enable, which ones leave out, as well as applications?
Some of them are standard procedure, but the rest depends on each different chef.
The first question would be: a light ROM, or a full-feature packed, at the cost of performance?
For my part, I usually cripple most of my ROMs to the mininum, adding afterwards only the apps I need.
Registry tweaking also is quite aggressive.
I don't like all the bloat in most of the ROMs, but that's what most users are looking for.
As for eye candy, I never integrate it at the cost of performance.
So the question would be: what do CHEFS want VS what do USERS want.
If you want to take this to the next level, you'll have to set a date for the meeting.
I'd recommend IRC, since not many ppl use jabber. MSN sucks, so...
Click to expand...
Click to collapse
Well, I do think research will lead to a certain extra insight.
For example: I tested the recent Swtos ROMs: they are (real) fast, all three of them.
Why? Is it because he left something out, did he combine things, did he add something? (please tell us Swtos...)
The problem with this kind of collaboration is that cooks have to share their work. And their time...
Well, most experienced chefs have pretty established routines for performance gains.
Here's a quick MUST DO checklist for a good ROM:
1: remove bloat
2: tweak registry (services, caches, etc...)
3: DSM grouping
4: G'Reloc
5: Pagepool
Anybody with a little advanced knowledge of the windows internals can handle the first 2 tasks.
adwinp said:
Well, most experienced chefs have pretty established routines for performance gains.
Here's a quick MUST DO checklist for a good ROM:
1: remove bloat
2: tweak registry (services, caches, etc...)
3: DSM grouping
4: G'Reloc
5: Pagepool
Anybody with a little advanced knowledge of the windows internals can handle the first 2 tasks.
Click to expand...
Click to collapse
Doesn't that "lock" your ROM and come in contradiction with most thoughts exposed in the locked ROM thread?
tnyynt said:
Doesn't that "lock" your ROM and come in contradiction with most thoughts exposed in the locked ROM thread?
Click to expand...
Click to collapse
Yes it does, then again, it's not a compulsory step.
Every chef has his own preferences.
tnyynt said:
Doesn't that "lock" your ROM and come in contradiction with most thoughts exposed in the locked ROM thread?
Click to expand...
Click to collapse
May better to publish "Tree" of project (OEM,SYS,etc)?
Nothing new - look to opensource
But who will moderate it?
It is the big work, I think.
There are many tutorials, documents and even video presentations on the forum. Kitchens may differ according to device but the basic principles are the same. Search for them and do lots of research!
tnyynt said:
There are many tutorials, documents and even video presentations on the forum. Kitchens may differ according to device but the basic principles are the same. Search for them and do lots of research!
Click to expand...
Click to collapse
I guess they are not asking about how to cook a ROM... but they try to invite people (especially ROM chefs) to collaborate... and sharing how is the best way to cook a good ROM...
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
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.