Develop Bugs

Call to the rom Developers [Rom Developers Read This]

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...

Developing a ROM

I don't really don't consider myself a noob but would prefer to add a little caution here since the solution will affect alot of phones.
I would like to build a ROM that would slim down the HTC Sprint 6800 by removing programs or tools that are not needed for my purpose, which in exchange cause alot of memory to be freed for another third party application.
I really need to help to understand that steps needed to build as I want. Can I use my own jpeg images for the boot screen? Incorporate third party software (that I have full control over) into the Rom? Will an unlocker be needed?
What applications/programs would you recommend in order to gain the most memory availability?
Thank you for any advice you could give.

I'm agree with you i searched a lot for some thing like that and i didn't find till now could some of members here help how to do that

Aniken010 said:
I don't really don't consider myself a noob but would prefer to add a little caution here since the solution will affect alot of phones.
I would like to build a ROM that would slim down the HTC Sprint 6800 by removing programs or tools that are not needed for my purpose, which in exchange cause alot of memory to be freed for another third party application.
I really need to help to understand that steps needed to build as I want. Can I use my own jpeg images for the boot screen? Incorporate third party software (that I have full control over) into the Rom? Will an unlocker be needed?
What applications/programs would you recommend in order to gain the most memory availability?
Thank you for any advice you could give.
Click to expand...
Click to collapse
Is there a reason as to why no one answers? Am I asking something wrong? I've read through search and "how to" on developing the rom but wanted more information about specific questions.... really? anyone?

You would do well to check out the Titan ROM forum here: http://forum.xda-developers.com/forumdisplay.php?f=384 and at www.ppcgeeks.com .
There is a plethora of information in these areas as well as ROMs that are doing what you are asking for.
Now, if you would like to do this on your own then I would still check the above areas as well as searching this site. There is a ton of info that can be found quite quickly.

[REF] How To Post and Promote a New ROM

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.

[Q] Modding or kernel mod ?

Hi, I am an android applications developer. I've been developing for a while now and i feel limited by the android library available. I would like to mod my galaxy nexus and modify the information available but I don’t know where to start.
I'm currently working with the signal strength libraries and the refresh rate is too low (i know its that way to be battery efficient) but for the needs of my application i need to boost that rate and to modify other. Should i look at modding the rom or modding the kernel directly for that kind of purpose? Any information on that subject is greatly appreciated

Alright so i'll assume you guys didn't understand what i am talking about.
I'm using android.telephony library. But the information it gives isn't accurate enough and the refreshrate of the listeners aren't precisse enough. Id like to modify it. But i'm not sure where to start. I've read a lot on internet but i can't find information about where to start. Can someone help me please ?

Yeah, I'm no expert, but that should be in the rom (radio interface layer).
Sent from my i9250

Hey thanks for the tip. I have read on ril and it might be about what I need. I'll be posing information about it if anyone needs it but googling ril gives pretty much all information needed.

This is hardcore hehe. I browsed trough all the ril libraries and i can't find the information. I really want to increase the sensitivity of the android.telephony.statelisterner and i am sure the hardware can dectect more information. It is just set like to prevent from battery drain... (imo)... There's not a lot of information on that topic. :S

[COMPETITION] Post Your Note 3 Setups! Fun and Also Helpful

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