New Kitchen (Helmi_APAC_WM3.5_NEW_Kitchen_R0) Bugs
 

Since new kitchen posts seem to be a bit scattered, here's a place to collect bugs...

The above applied to a pre-release version. Still active bugs appear below...

OEM\Optional_ZIP_Application:
The "option.xml" is missing a "d" in "Standard".

OEM\Optional_Spb Pocket Plus 3.2.0 QVGA:
"initflashfiles.txt" is missing the line...
"Directory("\Windows\Icons"):-File("tab12.png","\Windows\tab12.png")"
...which allows tabs to have icons.

BuildOS:
I'm getting an error...
"The file 'temp\dump\clg_in.gif' already exists."
on "SYS\DespiserBlackPhone_DPI_96 /w any theme besides "Despiser Black Theme" selected.

For some reason if I choose the "RealPlayer" package, CreateROM.bat will crash at mkimgfs.

Are these bugs from the kitchen that was released today, or from the one that was labeled as incomplete?

Mine were from the "Helmi_APAC_WM3.5_NEW_Kitchen_R0.rar" formerly in your FTP folder. as opposed to the one in /Apache/Helmi_APAC_WM3.5_NEW_Kitchen_R0/

That was:238 MB (249,656,387 bytes)
The newer one is: 253 MB (265,669,893 bytes)

So it seems I'm not current. Sorry, the duplicate file name threw me off, updating my post to apply to new release.

Re: New Kitchen (Helmi_APAC_WM3.5_NEW_Kitchen_R0) Bugs
 

This is becase the DespiserBlack_Base_DPI_96 directory option.xml file has the UUID wrong for the above phone theme. You have to edit the option.xml and correct the 2nd UUID which is for the phone skin.

Also, if you use anything skin, it will throw up again.

-AR

you are correct. good catch. that is being fixed right now

Some issues with the kitchen so far... I should have mentioned it earler before the full release. Anyway,

The TrayLaunch optional OEM has registry entries pointing to Total Commander, Task Manager/Registry Editor and ToggleBT. Probably these should be moved in their folders, because if I dont select them I get invalid shortcuts in the tray (3 of them.. thats annoying).

For now I just delete the reg, entries and put Items as 0. So I can customize it in the device later.

Also, probably it will be a good idea for people who plan on uploading their OEMs by modifying other's OEMs to generate an entirely new UUID. Otherwise, CreateOS just craps out.

I downloaded the black skin from the ftp site, and modified the skin by adding my own, then it crapped out on another phone skin as the UUIDs were the same. CreateOS is not friendly in this matter, it just crashes.

-AR

Will keep you guys posted as I find some more.

Probably it might be a good idea to seperate the Phone skins out of the base ones, so that anything can be used with any other.

This has been a pretty stable OS so far. And cudos to BigJ's writeup. That helped me troubleshoot some of the registry stuff.

-AR

I definitely agree. Having something like optional sub-install items might be nice, with some handling of missing items rather than errors/crashes (i.e. if UUID exists add this sub-item by it's UUID, if not ignore).

Well, that was just ID10t error by me not replacing the proper UUID