Develop Bugs

noob question: kitchen vs tools..same?

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

Help compiling a ROM please ?

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

[Q] Jargon Buster

I'm new at these forums, I came here for tips & advice to learn how to get rid of all the T-Mobile branding from my HTC Desire HD. With no technical experience of such devices (other than standard use) I soon found out there was a lot to learn.
The purpose of this thread is to get as much information for myself (and other newbies) to learn about the technical terms used, all in one place.
Would anybody be so kind as to offer plain English explanations of the following words/phrases.
Although I have a little understanding of some of these words/phrases, I have had trouble in the past so I am listing them for the benefit of others;
S-OFF/S-ON
HBOOT
ENG
Root
Flash
ROM
Radio
ClockWorkMod
CyanogenMod
RUU
BootLoader
Kernal version
Build number
Superuser
I think this is all for now. If you are also a newbie, feel free to post more related Jargon here to help build an all-in-one jargon busting thread!

I am my no means an expert but will try and help as much as I can.
S-OFF/S-ON - Security On/Off, this is to do with being able to write to protected parts of the device memory.
ENG <----This is the custom HBOOT that is part of the security work around ^^
ROM - Read Only Memory, usually this is the operating system that you are installing, eg LeeDroid or CyanogenMod.
Radio - Is the software used to link the hardware to the operating system.
ClockWorkMod - A custom recovery image that is used to install new roms, also allows you to do backups of the existing rom (operating system) before upgrading or patching.
CyanogenMod - A team of people developing an AOSP (Android Open Source Project) rom. It has no "sense" from HTC and is very minimalistic, usually very fast and stable.
RUU - (ROM Update Utility) The stock rom installer, use the correct one to return your phone to stock, usually used for returning to the manufacturer.
Build number - The version of the software you are looking at, usually it is in chronological order.
I have not answering the one's I know nothing about, better to wait for someone with more knowledge to come along. I may not be 100% correct, I am sure someone will correct me if I am wrong.
Good luck.
Blinky

Thanks Blinky!
On another thread CitizenLee pointed me to a website that contains a lot of the jargon and their descriptions! I found this unbelievably helpful. Here it is guys;
http://www.villainrom.co.uk/vBwiki/index.php/Glossary_of_Android_Terms

Very nice site, have bookmarked that myself, cheers.

[Q] Requirements for AOKP on serranoltexx

Hey guys!
I just got my serranoltexx and am fairly happy. However, I really would like to try and get AOKP running. Could any devs point me in the direction of where to start, you know, just bootstrap me with some reading? I have a background in Linux and UNIX, have developed some networking stack API projects on windows and have written a ****load of bash, perl etc. scripts in the past. I've also worked on the Matroska container format. Compiling etc. pose no challanges for me. However, I have never fumbled around with Android and I have no idea what drivers and other components might be needed. And how to start finding out what's missing...
I do know how to bootstrap my source repository and sync it... and in theory also how to compile AOKP - for supported devices, that is. What I don't know is: how do I start resolving unmet dependencies, and, you know, generally port a rom to a new device?
Please don't post if you haven't even compiled your own ROM yet. More likely than not, you'd be wasting your time.
I've posted on xda-dev as well, not sure which is the more suitable forum, possibly this one... Link to the other thread:
http://forum.xda-developers.com/showthread.php?t=2501539
And please don't post me to this guide right here as it is only of limited help. As I said, I know how to do it in general... You know, this guide:
http://aokp.co/learn/so-you-want-to-build-aokp-jb-ubuntu-1204

I tried to build it, but many things are missing once i flashed the *.zip.
Maybe i messed up with sources and patches.
Tell us if you have success! :good:

Porting Firefox OS to FP1

Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
madde on Fairphone Forum said:
Well there already is a recovery file for the fp1 + fp1u by chrmhoffmann up and running. The MTK6589 source code is kind of released and there has been a lot of work on the android code by the omnirom project, which might come in handy.
Should be definitely manageable to build and try out Firefox OS on the FP1. UnfortunatelyI'll just don't have the time to really dig into that. Maybe someone with a bit more experience can give it a shot. I'd love to see and try out the result...
Click to expand...
Click to collapse
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.

I'm very interested by a portage of Firefox OS to the Fairphone
Don't have enought time to test for now, but I stay connected

Newluck77 said:
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
Click to expand...
Click to collapse
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.

madde- said:
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
Click to expand...
Click to collapse
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Porting#Create_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...

Newluck77 said:
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US...reate_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Click to expand...
Click to collapse
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!

madde- said:
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
Click to expand...
Click to collapse
No haven't been able to work on this.
I still have no idea, where and how to build this configuration tree. Do you have advice on this?
Thank you, Stefan

Fyi, a build is now available. As a new user on XDA, I can not post link here (what a ****ty rule), but check bug 1139642 on bugzilla and search Fairphone on the Mozilla Developer Network (MDN) to have more info.

Wrong phone (FP1(U) vs FP2)
The build, you are referring to, is for FP2, not for FP1.
A Firefox OS for FP1 could possibly be built using the source by @chrmhoffmann: http://forum.xda-developers.com/fairphone/orig-development/rom-fairphone-fp1-kitkat-4-4-2-t3243623