dcd's hermann ROM & kitchen 2.16

[askwhy]

Forum having major issues -- I tried to post this earlier -- hope it goes this time...

Originally Posted by m_reyna_16

ive been trying to figure out how to use this type of kitchen...so then in order to have something cooked in you just place it in the OEM folder, open the kitchen (there wont be any option to select?) and then just cook the rom and it will be cooked just like that?

In a nutshell, yes. When you run the main batch file it is all automatic -- there are no options to adjust. If you don't have things prepared correctly you can get *some* useful feedback while watching it cook such as YELLOW warnings about files being overwritten (more on that below), but mostly you will not know what you may have done wrong until you flash it and see.

Anything within a subfolder of \OEM such as \OEM\MyProgramToCookIn\ will be 'included' by the kitchen when it runs. After the base (ROM/SYS) it processes OEMs, and then EXTs -- in that order -- which means that anything you add to \OEM which already has a corresponding file somewhere in \EXT will get overwritten by that EXT etc., so watch as the kitchen cooks for YELLOW warning messages and take note so you can resolve any version conflicts and so on.

Many other cook's OEMs can simply be dropped (the whole folder) into \OEM and as long as there is no file named _skip within them, the kitchen will try and include them. There are various other reasons why an OEM might not work right even if included, but this post is getting long already and there is a bit more to cover...

Originally Posted by philliyxx

My kitchen is crashing if I try to place calkulin's apps in dcd's oem folder... maybe I am noob and doing it wrong. I tried just dragging and dropping google maps into the oem folder=crash and then into the oemapp folder=crash...

I am using the OEM of Google Maps 3.2.0 from Calkulin's last kitchen (8/21) and it works fine. The only things I changed are the folder the shortcut goes to within initflashfiles (you do not need to do this), and I deleted option.xml (see below). Could you elaborate on 'crash' a bit? Try hitting pause/break on your keyboard while the kitchen is displaying any errors you might see flying by if they aren't normally around long enough to write down. You can drop the 'Navigation - Google Maps 3.2.0' folder in \OEM and it should work (you can also rename it if you like). The OEMAPP folder is basically its own OEM, it just has a confusingly similar name to the OEM root. Don't put anything else in that one, or OEMDrivers, or OEM_Lang_0409.

I do remove the option.xml files (which are for certain kitchens) from any OEMs that contain them, as they are not used by DCD's kitchen, but I don't think that it's required. It certainly doesn't crash the kitchen -- I have occasionally left them in by accident and the OEMs still processed without error as far as I could tell.

[viper8u2]

yeah, can someone explain what we copy over from Calkulins kitchen into DCD's? Just the OEM files for what we want to cook in? In DCD's root OEM folder or ???

What about the EXT files? I thought we had to do something with that also?

Thanks

[askwhy]

Originally Posted by viper8u2

yeah, can someone explain what we copy over from Calkulins kitchen into DCD's? Just the OEM files for what we want to cook in? In DCD's root OEM folder or ???

What about the EXT files? I thought we had to do something with that also?

Thanks

I think the post I made above yours answers, or at least mostly answers your first question. Let me know if it does not.

Regarding EXTs, they are very similar to OEMs. You don't necessarily need to do anything with them, but you may need to modify or remove a few to your own taste, or to resolve possible conflicts with OEMs you may add.

There is a great tutorial on OEMs and EXTs and the like here.

[viper8u2]

Thanks, I will take a look.

I did not see your post before I posted lol

[askwhy]

Originally Posted by hellraiser_osu

Can someone tell me which OEM folders I need to move for Manila 2.1 from Calc's kitchen? The last time I tried everytime I would get to the People tab and click Contacts it would crash Manila.

There are different dependencies for different parts of Manila, and I am not sure exactly which you might be missing. You do need a Tachi/Rhodium dialer for various Manila contact-related functions -- have you included that? Other than that, I can tell you what I am using which works for me.

From Calkulin's Kitchen - HTC/Manila-related things that don't overwrite files in or get overwritten by files in DCD 2.06:

Manila Gen.Y 2.1
Manila Engine Gen.Y 2.1
Manila White Flip Clock *or some other clock*
Tachi Phonecanvas 4
Tachi Phonecanvas Skin
Resource Proxy
FontLink
HTCScroll

HTC/Manila-related things I add from Calkulin's kitchen that already have some corresponding version or files in DCD 2.06 kitchen (which I have removed) and cause overwrites if not resolved -- they probably did not need updating at all, but I have done so and they work well for me:

Bootlauncher
Concurrence Manager
Shared Modules
GSensorCalibrator
USB2PC
SensorSDK
SmartTouch

Hopefully this will help a bit.

[hellraiser_osu]

Thanks AskWhy
Yes I included the Tachi dialer before but I think I was missing a dependency. I see one or two things I didn't include so I will try that out. Thanks for your help.

[m_reyna_16]

Originally Posted by askwhy

I think the post I made above yours answers, or at least mostly answers your first question. Let me know if it does not.

Regarding EXTs, they are very similar to OEMs. You don't necessarily need to do anything with them, but you may need to modify or remove a few to your own taste, or to resolve possible conflicts with OEMs you may add.

There is a great tutorial on OEMs and EXTs and the like here.

so then, technically if they are overiding the same files, then that means that they are the same? right? therefore not making any difference?

[askwhy]

Originally Posted by m_reyna_16

so then, technically if they [EXTs and OEMs] are overiding the same files, then that means that they are the same? right? therefore not making any difference?

Actually, that is not right. They *could* be the same file if they have the same name, but don't count on it. Same name does not, for example, mean same version, and that's the main reason you will need to be mindful of files being overwritten.

Example 1:
You include an OEM with an certain DLL, but it gets overwritten by an older version somewhere in EXT.

Example 2:
You include an OEM of Manila in a folder named 'Manila' but also include a Manila modification OEM in a folder named something alphabetically higher, like 'Blue Manila Highlights' -- you will find that the 'Blue Manila Highlights' gets applied before 'Manila' and the plain 'Manila' will overwrite the 'Blue Manila Highlights' instead of the other way around.

So, not only do EXTs overwrite OEMs (if files are the same) but OEMs later in the alphabet will overwrite OEMs earlier in the alphabet if the files are the same. Does that make sense?

[Elizle]

Thank you! I haven't tried this yet, but I am sure it will be good. I am going to try it out as soon as I know I am not going to be using my phone for an extended period of time. I loved your titan roms.

[probuild521]

where do i get the carrier file from?