Helmi Official AKU 3.5 Kitchen 1.0.2 Bugs / Patches

[Kolano]

Originally Posted by Maxx134

I almost got all my OEMs in oder I want from various kitchens, and now another Kitchen coming, lol thnx luv2chill 4 your efforts

Yeah, this is something I'd like to see improved with the kitchens. Having an "override" folder to drop updates in that would override existing items, instead of mixing everything into the OEM folder might be a good solution.

[gguruusa]

Having an "override" folder to drop updates in that would override existing items, instead of mixing everything into the OEM folder might be a good solution.

Assuming you haven't renamed or moved around kitchen directories,
1. Load the new kitchen into a different directory than the old kitchen
2. select all the directories in the old kitchen OEM folder
3. copy and paste the old OEM folder directories into the new kitchen OEM folder. Select "no to all" when it asks about replacing existing directories.

If it doesn't go smoothly (BuildOS fails), finding the conflicts between the old and new OEM folders can be time consuming.

BTW, anyone else have trouble with the .rgu of the FileDialogChanger 1.66 OEM? I had to recreate it to get it to work (not in Unicode?). Also, the .provxml for one of the Telus carrier OEMs is marked as a System file - no good reason for this (some editors - wordpad - treat it as readonly).

Is there a kitchen like way to build an ext_ROM?

[luv2chill]

A beter solution for transitioning between kitchens is to give all of your "portable" OEMs a unique foldername. Prefix them with "X_" or even "Custom_". BuildOS doesn't care what the folder is named so if you title them all with a single prefix at least they will all be grouped together.

Ideally BuildOS would allow for a "Custom" folder at the root of the kitchen where you could place your own personal OEMs and just tote that folder from kitchen to kitchen, but it's hard coded to only look in SYS and OEM so we just have to settle for "next best" until bepe or someone else invents a better mouse trap.

@gguru - as for your specific issues I was unable to confirm either one? The File Dialog changer in the kitchen doesn't have an rgu file (just looked again) and it built and works just fine for me.

And there is just one provxml file in the Telus carrier OEM (I should know--I made it ) and I just attribbed and it is not marked as a System file. Is it possible you were talking about something else or maybe it happened after you extracted the kitchen? Anyway please clarify.

I am not aware of any buildos-type app for an extrom. It would be sort of difficult to pull off automated program installs there because the main ROM still needs the reg entries and/or shortcuts. It is possible to create a flashable extended rom rom image though--lots of ROM releases on xda-dev offer them.

[Kolano]

Originally Posted by gguruusa

Assuming you haven't renamed or moved around kitchen directories,
1. Load the new kitchen into a different directory than the old kitchen
2. select all the directories in the old kitchen OEM folder
3. copy and paste the old OEM folder directories into the new kitchen OEM folder. Select "no to all" when it asks about replacing existing directories.

If it doesn't go smoothly (BuildOS fails), finding the conflicts between the old and new OEM folders can be time consuming.

This isn't a good solution, as it's prone to blow away change made in the newer kitchen.

Originally Posted by luv2chill

A beter solution for transitioning between kitchens is to give all of your "portable" OEMs a unique foldername. Prefix them with "X_" or even "Custom_". BuildOS doesn't care what the folder is named so if you title them all with a single prefix at least they will all be grouped together.

I've done this, but this solution only works well for additions to the kitchen, not revisions to existing content. I have taken a similar tact when making revisions to existing content (i.e. renaming the old folder with my Kolano_ prefix to differentiate it from the kitchen version), but when doing this I need to re-analyze each of OEM during a kitchen updte to ensure I don't miss something revised in the newer kitchens.

Is "bepe" a user on this forum, luv2chill? If not where is he/she from?

I was hopeful, with the recent revisions to support the option.xml files, that active development of the BuildOS tool was still going on. If it is I would love to see some override mechanism implemented.

[gguruusa]

Originally Posted by Kolano

This isn't a good solution, as it's prone to blow away change made in the newer kitchen.

I've done this, but this solution only works well for additions to the kitchen, not revisions to existing content. I have taken a similar tact when making revisions to existing content (i.e. renaming the old folder with my Kolano_ prefix to differentiate it from the kitchen version), but when doing this I need to re-analyze each of OEM during a kitchen updte to ensure I don't miss something revised in the newer kitchens.

Is "bepe" a user on this forum, luv2chill? If not where is he/she from?

I was hopeful, with the recent revisions to support the option.xml files, that active development of the BuildOS tool was still going on. If it is I would love to see some override mechanism implemented.

Bepe is on vacation, and from the looks of things, busy with more technical kitchen changes (for other phones). He's the creator/owner of BuildOS.

When you say "no to all" during the copy, it preserves the new kitchen at the expense of the old kitchen folder. So long as the kitchens are based on the same core, this will result in folders you've added to the old kitchen being added to the new kitchen (ignoring certs.oem - it shouldn't change anyway)

There's no way to avoid the analysis part if you make your own custom mods to a kitchen folder. WinDiff is your friend. In most cases, you can put the mods you'd make in a custom settings OEM - just make sure it has a late GUID (like FFFFFFF.....).

The FileDialogChanger 1.66 I have didn't come from the 1.02 kitchen. It either came from the zip at the start of this thread or Colonel's ftp, can't recall which. It has an exception entry in it for regedit.

[gguruusa]

Originally Posted by luv2chill

And there is just one provxml file in the Telus carrier OEM (I should know--I made it ) and I just attribbed and it is not marked as a System file. Is it possible you were talking about something else or maybe it happened after you extracted the kitchen? Anyway please clarify.

I am not aware of any buildos-type app for an extrom. It would be sort of difficult to pull off automated program installs there because the main ROM still needs the reg entries and/or shortcuts. It is possible to create a flashable extended rom rom image though--lots of ROM releases on xda-dev offer them.

Oops, not Telus, Telecom. If that's not it, let me know and I'll retrace my steps.

For te ext_rom, I'm looking for a way to say "build an ext_rom with these files". Seems backwards to have to put the files on my own ext_rom and then extract that image to get there.

[luv2chill]

Right you are gguru... wonder how that happened. In any case it shall be corrected for 1.0.3.

[friguy3]

I have a newer arcsftMMS, its version 4.0.41.23, but its a cab so didnt know how or what to do with it. here it is if someone can mess around with it...

[superevilllama]

Originally Posted by luv2chill

New kitchen in a day or so...

Releasing Today? Today? Yes? I hope! i have two days off....

[friguy3]

well i messed around with the arcsoft 4.0.41.23, the cab just removes my mms and cant find it anymore. anyone have any luck?