Quote:
Originally Posted by Trident
Quick thing that I've noticed.
When I get to the customization, the customization fails. I get a message that it can't find the file Bluetoothiconnotifier1.cab.
I checked and sure enough it was in the regular Sprint Carrier OEM, but not the one with Titanium add-ons. I threw it in there and everything worked fine.
It does appear that there is quite a bit of overlap with the files in 21725 and many of the OEMs. I can't select MSVC and a bunch of other things without getting duplicate errors.
|
You're getting errors, because you're mix and matching kitchen elements between kitchens. You need to pay close attention to the config_operator.txt file, if you are gonna be doing kitchen mixing.
Also, this can be dangerous, because not all kitchens at 100% uniform. For example, recently dnsapi.dll has been showing up in sys builds, and previouslu it was in oemDrivers. I haven't really looked into this specific dll or it's function, but I have been leaving it in my sys, while other chefs have opted to use the OEMdrivers version. If you used one oem base witout dnsapi.dll, and a sys that also had it excluded, you'd likely have a bad rom. Another example is the HTC dialer contacts list corruption fix, that involve cprog.exe and tpcutil.dll. They are normally in the sys, but in my kitchen I have them in OEM dirvers, so if I forget to modify future sys' with the fix, I'll bet build errors to remind me. So, if you use my sys with another oem base, you'll have major issues with the phone.
The issue you were having with the dialer, is because I basically just skinned Calkulin's Black S2A OEM package, and since you were leaving both packages in the kitchen, you were having redundancy issues.
I personally am not a big fan of having any OEM packages in the kitchen that I don't want in my rom. I know that their not supposed to be build in if their not selected, but I've had at least one OEM (HD Manila) that would cook in even unselected. Also, since we can't save rom build info with the Calcu kitchen the way you can with other kitchens, it's the only real way to ensure uniformity.
In my kitchen, I try to make every option.xml in there "true". Some chefs, like Mighty, just delete all option.xmls, since they serve no real purpose for many. Any package without an option.xml cooks in automatically.
For future reference, OEMizer or PackageCreator will both generate unique rgu and dsm guids, along with an option xml.