Hello,
my name is Markus, i think about to build up a database, where devs can upload and post their ROMS. I think about this, because it is very difficult to find here a rom with features wich i want to have. I will build up only a database, with no forum, the support and things like this, schould stay here.
But I think this is only possible, when i find some devs wich have interest to use an offer like this.
What think you about this? A Database where you can search and filter roms. For example you can search for special applikations, wich schould be in the rom or a special language.
Related
Newbie question. I don't understand, what is difference between a kitchen and tools like mamaich's ? At first I thought they were the same but now I'm not sure because I keep seeing references that don't make sense.
Post removed.
Post removed? That's it? Pardon me....Look, I know this is a newbie question but I am honestly confused as to what the definition of kitchen is. If I use mamaich's tools to prepare, view, etc. I end up with what seems, to me, to be a similar thing as a kitchen. Are they the same? Is there something about a "kitchen" that is fundamentally different than only using the tools? I have read many, many pages here and I'm honestly trying to understand. Please point me in the right direction. Thank you.
edit: sorry, I thought "post removed" in the earlier post meant I got my message removed from the forum by an admin, anyway, my question still stands.
Since the unhelpful member above failed to give you a decent answer, I will help you. Tools are either a program or a set of programs designed to do a task with the roms (for example, Mammich's tools are designed to help you edit the imgfs part of the rom). A kitchen is a set of tools (made by various people) designed to edit the whole rom or most of the rom and build your own custom roms.For future reference, if you ever have any other questions about rom building, let me know and I will help you out as much as I can.
Thank you very much Steven855 and I appreciate the offer to help.
I originally gave an inadequate answer - thus the removed post. Home ill with the flu, Nyquilled up and forgot which section I was in (thought I was in the Kaiser specific section and gave an answer associated with that). No ill intentions, so to speak.
What I will say is the various tools are something a newbie should probably feel comfortable using. Before using a kitchen, read, learn and flash a number of others' custom ROMs. While the great developers here have made cooking custom ROMs very easy with the kitchens, you can cause a lot of problems with your device if you don't know what you're doing.
No ill intentions taken. Like I said, at first I misunderstood and thought my post got nixed by an admin. btw notwithstanding Steven855's helpful answer, I had my question answered earlier on another thread when the same question came up.
Quote originally Posted by ramsses:
My understanding is the kitchen implies each module (with its associated registry - RGU - files and dlls etc.) is explicitly separated so it can be incrementally and selectively combined. What we are doing here is taking an existing set of ROMs and combining the dlls, exe etc. by hand - there isn't a handy gui where you can select which module you want. Also, the registry is necessarily hand crafted too. So by using the extract/rebuild tools, we are making a ROM, but it isn't a kitchen, more a roadside burger van!
Thanks again, really enjoying this site, and learning alot.
Steven855 said:
Since the unhelpful member above failed to give you a decent answer, I will help you. Tools are either a program or a set of programs designed to do a task with the roms (for example, Mammich's tools are designed to help you edit the imgfs part of the rom). A kitchen is a set of tools (made by various people) designed to edit the whole rom or most of the rom and build your own custom roms.For future reference, if you ever have any other questions about rom building, let me know and I will help you out as much as I can.
Click to expand...
Click to collapse
Hi Steven. I was wondering if you knew about ROM cooking for Verizon CDMA devices..ie the i730? I was looking around to see where I would be able to find the bootloader for it but I haven't found any answers yet. Thanks.
Sorry! Unfortunately, I don't know anything about rom cooking for pocket pc phones (yet). I'm still trying to get the hang of this rom building stuff myself (after 2 failed attemps to make an updated rom for the axim X50(mid)).
Hello,
because for a noob like me, it's very difficult to see the differences between ROM's, I want some hints and advice for this.
I noticed the ROM of Shady and the ROM of Emrulez. For me the difference is not clear.
Can someone compare those ROM's please?
Also the word kitchen isn't clear .... :$
There is no differences. You should say Kudos to Microsoft for these ROMs and their effort. The cookers here only add and delete programs using kitchen.
thats my question, whats the difference.
nobody?:s ...
Yes it is a good question.
I am trying to figure it out myself.
At the moment, only thing that I am certain about, is that build number is different
is there any difference about battery drain ?
well the build number is like an update of the windows, higher build >>more recent release.
and roms differs with stability, free ram, storage, bugs, addons
that's why every1 r keep trying till he got the rom he like.
and about the battery drain,, they r differs too, since some have a UI interface which drains battery and other background processes assuming they use the same radio version since the radio version is one of the important things with battery drains.
to build a rom u need to build a kitchen with by it u can do it... there some ppl who like to share their kitchens to make any1 can modify the rom with his needs.. but to do that u have to know a few things
hope this helped
maybe it's a good idea if someone (I? ) creates a new topic with a Rom-overview?
The first message will show all the ROMS with the following info:
Date of last update
Windows version, build number
Programs added
Programs deleted
Free Memory
Bugs
Link to the topic
...?
Based on that message, users can choose their favorite ROM. I do not want to make a competition of this, only make it user friendly to choose.
y_bother said:
to build a rom u need to build a kitchen with by it u can do it... there some ppl who like to share their kitchens to make any1 can modify the rom with his needs.. but to do that u have to know a few things
hope this helped
Click to expand...
Click to collapse
Hello thanks for your information. So there is no general kitchen which i can use to modify the ROMs? has every ROM it own kitchen? And I wonder where the people always get the new OS versions since I never seen you can download them at Microsoft or so....
@ babbelut
well yes i think cud be so helpful too , but i think it's too hard specially when a lot of roms r being created !!
@ TalhaX
well ya there is no a general kitchen, each cooker has his own kitchens some share it as u can find.
u can build ur own kitchen or use one of these kitchens,,, couple of days ago a saw a kitchen called superjustkitchen i think this may help u.. i don't know about these stuff. and where from they came with these builds but u can search here,,, and if r planning to do this make sure of what u r doing
I've made a wikipage:
http://wiki.xda-developers.com/index.php?pagename=XDA_ROMS
Please feel free to contact me or add some ROMS !!
It's not so wise to make such a page. ROM i for specific device and will not work on other.
Here is a page for Artemis
http://wiki.xda-developers.com/index.php?pagename=HTC_Artemis
and you should make your subpage there.
I use xdadevelopers many years and it's sad that everyone works alone on ROMs. There are only a few people owning each model and doing their own kitchen/ROMs. They should work together to make one, best kitchen, and set of quality ROMs.
Now we have for example SHADY's kitchen which is probably very good, but ROMs have many bugs. And there is nobody who can fix them, because Shady don't have time, and others fix their own ROMs. And now we have new build and new kitchen and new ROM and new bugs. Yes, they are the newest, have all bells & whistles, but are useless because of bugs
I'm looking to replace my Touch ROM, which were very good, but author has abandoned it.
it is a subpage of artemis, not?
I'm looking for a 2.2 Froyo rom, WITH HTC Sence UI.
pref, 720p recording, newest radio ect..
tried searching through the forum but can't seem to find one i like, most roms have been trimmed down..
couldn't understand the rom kitchen othervise i would compile my own..
any link for this kind of rom or if someone could compile it for me, would be highly aprishiated.
excuse my bad grammar.
Your kidding right?
I'd have a look again if I were you.
Please use search before posting! When you signed up to these forums you agreed to the forum rules, and the number 1 rule is:
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
Click to expand...
Click to collapse
Everything you need to know is here, but always search before asking.
Chef Central > Android http://forum.xda-developers.com/forumdisplay.php?f=613
Learn Android ROM development. For serious students only. This forum is monitored and moderated by seasoned developers.
http://forum.xda-developers.com/showthread.php?t=667298
cyanogen said:
Here's my advice 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 (the links below have almost everything you could possibly want to know). 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 **** 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.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
Click to expand...
Click to collapse
Klutsh said:
Your kidding right?
I'd have a look again if I were you.
Click to expand...
Click to collapse
It's quite hilarious now when I read it again. How %&ยค/"# some people can be
Does anybody know if it's possible to install Hebrew fonts with any of the Android ROMs?
I think I recall that question being asked previously, but cannot recall which thread, or if it is in fact possible, I expect it will be though.
OK found a few mentions of it, I may have to make up a little update.tar for them, but here's the link to the thread:http://forum.xda-developers.com/showthread.php?t=613826&highlight=hebrew+fonts&page=4
As if by magic, ( or merely synchronicity), Duke911 has just produced this guide : http://forum.xda-developers.com/showthread.php?p=7343996#post7343996 which should help sort you out, I did make up an upgrade, and will post it if you wish to try that.
Talk about magic! That's awesome!
Thanks!
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.