yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] Skrobel:
I know this is not a solution you can expect, but at least I can suggest files that you should take a closer look. Your problems sound very common to mine when I was trying to change a ROM language. Besides many .mui files that influence language, there are also some .htm files and among them there are message composer templates.

And the effect you see is typical to the situation when outlook doesn't find a template or cannot use it, and the files in question are:

compose_note.XXXX.htm and

read_note.XXXX.htm where XXXX is a language code like 0409 for english.
[Windows Mobile] CRACING:
Hmm, the build order is annoying me. Cannot understand how to sort it out. :(

May be thats related to my email problem, though I tried my knowledge best with build order but still same problem with email. :(

If its with files, the same issue should be present in different kitchen. :rolleyes:

As of autosigning, shared flag etc, I even tried removing them but still same.

Like AndrewSh, its something with build order. Lets see or may be I should start from stock ROM again. :o

hmm, need to check it out. Thanks though. :)

Thanks all...

Best Regards
[Windows Mobile] Jackos:
Ensure you have included the following packages.

Webview

Riched20

SMS_Providers

SMIME

Keep in mind I have no experience with OS Builder and I assume you're trying to create a WM6.5.x ROM.

There is a high possibility that the problem lays in one of those files mentioned by Skrobel. Strange it didn't occur in your old kitchen :)

PS I hope you got a Message Enhancement package that matches the WM build.
[Windows Mobile] CRACING:
Alright, It was htm files issue present in Message Enhancement. In the reg, some entries paths to those htm (i.e HTC_compose_note.0409.htm). When I changed to WM ones (i.e compose_note.htm), the problem with email vanished.

But now I have a doubt, Why didn't I faced such troubles in OsKitchen since I was using same Message Enhancement version package from start.

Looks like its something to do with language (i.e HTC_compose_note.0409.htm).

Is there any language settings or reg I should do when using osbuilder? I have selected 0409 in osbuilder main window tool bar. Is there another one somewhere else?

Edit: pff finally figured out. Its with attributes. HTC_compose_note.0409.htm should be systemly hidden. How stupid thing! :S

And also why didn't htc systemly hidden the files whereas MS did. Of course oskitchen does this so I hadn't faced such and I wish this should be implemented in next osbuilder release. :)

Thanks...

Best Regards
[Windows Mobile] Jackos:
Thanks why I like my command line kitchen :) It gets the job done without any problems.

attrib +h +s dump\*.htm

...and you're ready to go.
[Windows Mobile] CRACING:
ok thanks. I have bunch of attrib command lines but I don't know how to include them in OSBuilder. Command line should perform while building (dump dir).

Now I do manually but sometimes I forgot when I update the packages. :o
[Windows Mobile] CRACING:
Damn, the issue with email isn't solved yet. :mad:

I made a cab, placed the htm file, applied attrib (+S, +H, +R) and installed the cab in device. The email issue vanished and I was sure its attrib issue.

But if the do the same thing in package (OEM - kitchen), It doesn't work and now I found that OSBuilder is applying its own attrib settings to OEM packages.

When I set that htm file +S, +H, +R and build the ROM, osbuilder resets to -S, -H, -R and there rises the email creation issue.

I really don't know how you guys don't have such issue but for me this is happening. I guess you guys aren't using Message Enhancement or the reg path (HKEY_LOCAL_MACHINE\System\Inbox\Templates\IPM\Note -> Compose) is linking to Windows Default htm (compose_note.htm). AndrewSh; Do you mind to check this reg in your ROM/device please?

I can get rid of this issue by simply using Windows Default htm (compose_note.htm) but there is slight difference between HTC's htm and I like it better.

Developers of OSBuilder, Please consider this issue as crucial...

Adding an settings about file attrib would be awesome (Like, file list for autosigning, recmod list, reversmod list)

Thanks...

Best Regards
[Windows Mobile] AndrewSh:
CRACING, buddy, my

(HKEY_LOCAL_MACHINE\System\Inbox\Templates\IPM\Note\Compose)

is linked to

\Windows\HTC_compose_note.0409.htm

...Read)

is also linked to correspondent HTC file

And the only attribute in my rom for those two files is "System"
[Windows Mobile] CRACING:
:confused:

But in my ROM, attribute for those two files is -S, -H, -R. Even though I set +S, +H, +R.

Edit: Is there any settings about attributes in OSBuilder?
[Windows Mobile] jmart518:
Hey CRACING, I actually had the same problem when I first switched to OSB. Unfortunately, I can't remember what I did to fix it. I don't have any problems with my current setup, so here is my package if you want to give it a shot.
[Windows Mobile] CRACING:
Thanks a lot but I solved it now. :p

OSBuilder reads flags from DSM and the DSM of Message Enhancement has no flag for those htm files. It wouldn't happened if I dragged packages straight from Stock ROM but I dragged from my OSKitchen and since it was Ext package, I had to use EXT to OEM tool. When it created DSMs for the packages, it didn't written attribute flags. :)

Anyways, now I have a big work to do. Extract all the ROMs in OSBuilder and get the original DSM's. :rolleyes:

Very sorry for doubting on the OSBuilder, it was my fault. :p

Edit: Ok, DSM Autocorrection saved my lots of time. Pff awesome!

Best Regards
[Windows Mobile] AndrewSh:
You should fix DSM I suppose

In Settings\DSM - apply S & H attributes to files & modules according to DSM records when saving DSM file

and

apply S & H attributes to files & modules according to DSM records when building dump

Added

You got it while I was replying :)
[Windows Mobile] CRACING:
Yeah, thanks. :)

Hope it solves my issues this time.

And btw; I love this kitchen a lot. It saves lots of time and manual works. Wish it had Ext feature but I hope the developers will implement it on upcoming OSBuilder versions. :)

Thanks...

Best Regards
[Windows Mobile] -=Barin=-:
OSbuilder supports EXT folder in the root of the kitchen, but all packages in EXT folder need to be converted to OEM (classic) format.
[Windows Mobile] CRACING:
:confused:

That means it supports OEM (classic) format only.

All I need is to sort packages in subfolders.

i.e

[-] Ext Packages

- [-] 3rd Party App

- - [-] uTasks 1.4

- - - [-] Files

- - - [+] 0409

- - [+] etc..

- [-] Leo 3.14

- - [-] Camera

- - - [-] Files

- - - [+] 0409

- - [+] etc..

- [-] Oboe 1.18

- - [-] Notification Enhancement

- - - [-] Files

- - - [+] 0409

- - [+] etc..

Edit: sorry I had misunderstood but now I got. Category wise packages (like I said above) is possible in OSBuilder. Thats awesome. I don't care whether it needs OEM format or EXT, all I need is to categories the packages. :)

Thanks a lot...

Best Regards
[Windows Mobile] -=Barin=-:
OSBuilder V1.2.133 is ready :)
[Windows Mobile] ct_moi:
Hi Barin,

Thanks for the new version, just read the changelog @asusmobile.

I've a request, don't know if it'll be possible.

In the file preview I check for files "Show all files in device \windows folder".

Is it possible as in others folders (with initflashfiles.txt or dat) to have the package of the files for the files under windows folder?

As we can have overwrite the files like phonecanvas, tweak on manila files or on sys.

Hope you can understand what I want to say :).

Best regards -
[Windows Mobile] AndrewSh:
OS Builder V1.2.133 FULL (11.08.2011)

Changelog:

1.	The ability to digitally sign cab and tsk files while assembling the rom (as it was for executable files in previous versions) is added. You can add cab or tsk files to the “sign files” list to sign files either manually or using the context menu of the package.

Not only target file itself is signed, but also all executable files inside it. The originals (source files) stay untouched.

2.	The tool Cab/Tsk Signer is added to built-in utilities. With it you can sign cab and/or tsk files.

You can select either a single file or all files in a folder. It is possible to create a cab file to install the certificate, as well as the opportunity to add a certificate in _setup.xml of the cab file.

3.	The item ‘Quick registry assembling” is removed from Settings/Build DUMP and Rom if packages are merged. Now this option is hidden but selected by default. If Merge All Packages to One checkbox is toggled - the rapid registry assembling algorithm will be executed. If this checkbox is cleared – registry assembling will be usual (old-fashioned).

4.	The ability to sort / clean rgu files is added. Provides sorting/cleaning either the separate package rgu (via the package context menu), or all rgu files in the kitchen with a possibility to make a choice between EXT, OEM, ROM and SYS or all of them (Additional Tools-> Cleanup-> Sort / clean files rgu).

While sorting / cleaning process: double values will be removed from rgu (in case of different values of the same parameter the last value will be saved, as during the regular registry assembling), the removal directives for keys and values will be moved to the beginning of the file. Keys and values are sorted alphabetically.

If the key and value with OEM version (HKEY_LOCAL_MACHINE \ SOFTWARE \ OEM \ MASD) is present, it will be moved to the end of the file.

IMO optimized by this option rgu files are much more readable.

Remember that when sorting/cleaning rgu all comments will be deleted!

5.	While installation OSBuilder sets association with hv files. You can open it for viewing just double-clicking it in Windows Explorer.

6.	Registry comparer is added to Tools/Built-in. It can compare the contents of rgu and hv files, export to rgu either separate keys, or the difference obtained when comparing files.

Guys - screenshot is Russian - but you know - you can get English by yourself, switching the language in Settings :)
[Windows Mobile] CRACING:
Thanks for implementing Registry Compare tool. We no longer need to use any 3rd partly softwares.

Anyhow, I have found a minor issue in it. Tool reads reg files having REGEDIT4 header nicely but throws error if the reg header is Windows Registry Editor Version 5.00. Saying, REGEDIT4 not found or something that. Its not a big deal and I suppose can be easily solved. Just for your kind info. :)

Thanks again...

Best Regards
[Windows Mobile] -=Barin=-:
A part of changelog:
[Windows Mobile] CRACING:
oops, looks like I need a eye checkup. :p

Thanks...

Best Regards
[Windows Mobile] Nixeus:
Hello and thanks a lot for this new release :)

Have you news about a good set of files to don't compress ?

I use :

*.png

*.ttf

All Manila Images files

manila.exe

shell32.exe

gwes.exe

opera.exe

operaL.exe

Thanks a lot :)

Best regards,

Nixeus
[Windows Mobile] Farmer Ted:
I would add connmgr.exe, services.exe and cprog.exe to the list.
[Windows Mobile] CRACING:
Hello guys,

I have a another lil problem here which is making me worried and its with splitting L modules.

First I tried with my Topaz kitchen and saved about 5MB in slot 0. When I did that, none where loaded into Low. The same where moved to high.

However, when I did the same thing on my HD2 kitchen. Neither I'm getting 5MB more space in slot 0 nor low modules are moved to high. The low modules list stays as is while building, whether I tick splitting L modules or not. :confused:

FYI; I have checked the DSMs and those modules stays in low while building aren't marked as L in the DSMs. I have done full kitchen DSM autocorrection many times. OSBuilder Configurations XML is fresh and OSBuilder.osb also.

Am I doing something wrong? or there is a reg or etc file containing which modules should run low?

Edit: Looks like I have overload of modules in my HD2 kitchen. :(

Edit 2: Ok fixed it too. It was because of phcanImages.dll that I had reversmode'ed. When RecMod'ed, I got the 5mb back on VM slot 0 while building and Low modules were moved to high. :)

When this dll is as file, it of course comes above/out of slot 0 but it would take less then 500kb whereas as module, it was taking 5MB. Approx the same size of the dll.

On topaz, the case was different and the dll didn't take so much of space in slot 0 even though it is as module. FYI; Phone Canvas I use in topaz is rhod phone canvas 3G and on HD2 is 2G phone canvas. No idea why the case was different. :confused:

Edit 3: OK, I have found three dlls which were eating more space then what they eat outside slot 0 (as files). CameraCoreServices8650.dll1, mms.dll and phcanImages.dll.

Thanks...

Best Regards
[Windows Mobile] -=Barin=-:
OS Builder V1.2.140 is ready
[Windows Mobile] HD2Owner:
thanks barin

@all: please hit the thanks button on barin's posts
[Windows Mobile] CRACING:
Looks like AndrewSh is busy so I will translate and post the change log. :)

1. Fixed a bug that sometimes occurred when cleaning resource module of code.

2. Added ability to search for and delete the call from the library CePerf.dll executable files and modules. For the idea and algorithm thanks to the distinguished Ultrashot'u

The search for such files and modules with ext. instruments (Cleaning-> Delete calls CePerf.dll). In the window with found objects using the context menu, you can either patch the desired objects at once, or add them to a special list.

Objects added to this list will be patched in the assembly (the originals are not touched).

3. Removed parameter settings BuildImgfsGroupModules. Now when you build a IMGFS first written to all the modules, and then files.

4. When you combine packages into a single registry is going to make better

5. Added syntax checking files rgu during assembly (see the build configuration and dump ROM). By default this option is enabled.

Thanks a lot Barin...

Best Regards
[Windows Mobile] AndrewSh:
I will try to clarify this Google English:

1. The random bug occurred sometimes while cleaning code from resource files - fixed

2. The code of several dlls and executables contains the useless invocation of CePerf.dll (module containing functions of monitoring and logging performance) - needed for debugging purposes only. This test fails to generate results if CEPerf.dll - dependent logging library - is missing. As far as we operate with ready MS Build - we don't need it. But this useless invocation spoils system time and resources. (The idea and cleaning algorithm - by ultrashot)

So now it's possible either to completely remove CEPerf.dll invocation from all files and modules containing it, or do it on the fly while assembling rom (leaving the original files untouched).

3. Earlier it was possible to manually add BuildImgfsGroupModules parameter to osb file to regularize modules and files in IMGFS. Now it's a default feature - while assembling IMGFS first all modules are processed, than all files...

4. When "Merge all Packages to one" option is toggled - registry assembling is highly optimized.

5. .... clear enough in the previous post.
[Windows Mobile] Stephen:
I have been able to decompress the leo 3.14 rom and the only file I edited was the manila messaging rgu file. I added in the fix for the sms issue. When I compile I get an error

"the last line must not be empty"

Also when it decompiled all files are read only.

Any ideas?
[Windows Mobile] AndrewSh:
You read it incorrectly :) The last line MUST be empty!

Leave empty line after the last filled line in your edited rgu (just push Enter) and save file.
[Windows Mobile] Stephen:
The frase Doh! comes to mind cheers :)
[Windows Mobile] Stephen:
Ok now when I am building a rom I get the following error: Error building imgfs. Check imgfslog.txt Exit code =1073741790

Even if I decompile a rom and make no changes to it at all I get this error. :(
[Windows Mobile] AndrewSh:
Ghost, one dumb question - how much memory do you have on PC?

Would be nice to see this log attached here (imgfslog.txt) - look in TEMP of a kitchen

Possible issues: lack of memory or caching error...

Or some system dlls are missed in System32 - this case can not be solved by us :)

Anyway - first - log file, please......
[Windows Mobile] Stephen:
Ok Figured out what happened. Durinig the build process, the new windows that appear and have say a 10 second ok buttons for example were being hidden behind the main screen so it was timing out on me and then not adding anything into the logs.

It might be worth on the next version to have a bit of code on the windows to automaticly bring them into focus. What do you think?

EDIT: Tried a third time and worked perfectly. Odd. Looks as if I had been letting the time out buttons time out! Really like the way you can edit the D very easily, that is something you cant do in oskitchen!

Flashed my first successful rom!
[Windows Mobile] ultrashot:
Always look at error code first ;)

IMGFS Builder itself from newest osb versions doesn't return such error code. Interval: 0 - 14.
[Windows Mobile] -=Barin=-:
0 means success :)
[Windows Mobile] -=Barin=-:
OS Builder V1.2.143 is ready
[Windows Mobile] AndrewSh:
Changelog for OS Builder V1.2.143

1.	The item ZeroLength is added to UL partition drop-down menu (Settings\ Buid Dump and Rom) - ULDR partition is physically removed, but the record about it remains in the Partition Table (SectorsBefore = 0; SectorsCount = 0). In my opinion this is the most viable option for the removal of ULDR. (Here "my opinion" means the opinion of Barin but I would say that this feature removes a lot of bugs - especially if you build so called "empty" roms).

2.	The option "Remove flag IMAGE_SCN_COMPRESSED" is added to Advanced IMGFS compression options. This option helps to avoid the idle invocation of the function CEDecompres and thus speeds up the loading of modules.

3.	The check-box “Group modules at the beginning of IMGFS partition" is now available in Settings/Build Dump and Rom. Don’t use this option cooking for 6.0-6.1 nk devices and old devices. Good for Leo and other stuff like that. (feature is checked by Barin - for Asus P750, ultrashot - for X1, me - for Asus P525)
[Windows Mobile] Farmer Ted:
You guys are on one hell of a roll. Thanks!

I'm going on 18 days since I last soft reset my device, which is a major record for me, lol. The disabled page pool\ kernel flag=1 is really working for me.
[Windows Mobile] AndrewSh:
Farmer Ted, thanks for your report, my friend. We really did not have an opportunity to check the feature for 18 days.... Maybe 18 hours only :) We really appreciate your feedback

I would offer to try also to toggle the option "Remove flag IMAGE_SCN_COMPRESSED" - works nice!

Regards, Andrew.
[Windows Mobile] ai6908:
Hey Ted, what setting are you exactly talking about? I want to try this in my CDMA TP2, and see if that makes a difference. Thx.
[Windows Mobile] Farmer Ted:
It's the kernel flag setting '1'; it disables paging, and loads all dll-modules into ram at startup. It eats into available RAM (maybe 20 MB or so for me), but works great.
[Windows Mobile] CRACING:
So no virtual memory?

This seems very interesting.

Let me try and see how it goes. :)

Edit: sorry, its paging loads to ram. Not vm :p

Thanks...

Best Regards
[Windows Mobile] ffboy2009:
when i try to upgrade OSBUILDER to V1.2.143,it keeps saying"Error: Error building IMGFS. Check ImgfsLog.txt

Exit code=14 [APP_ERROR_FILE_CACHING]"

i just installed V1.2.143 withouit change anything

my PC gets 500G HD and 4G RAM

there's the error mess in TEMP\IMGFSLOG.TXT

Error! Caching "F:\ROM\osbuilder\EXT\NEED\0_CallerLoc\国际区号" failed

can anybody help me?
[Windows Mobile] Farmer Ted:
There's still the 32 slot/32 MB virtual memory limitations, but the difference is that there's no paging, which seems to make things faster. When I benchmark with sk tools, the RAM performance index goes from ~500 to ~900 for me. I don't know if it means anything or not, but you have to figure that if the kernel isn't wasting time paging out data, there's more time for other things. Also, since all the modules are pre-loaded into RAM, things load a lot faster. SK tools loads in about 1.6-.8 seconds for me, when it used to load in ~2.8 seconds.

As long as you have enough free RAM that loading all your dll modules at startup doesn't kill you, it is definitely worth trying. It works great for me.
[Windows Mobile] CRACING:
I see

I tried it an hour ago. Feels good so far, though I have benchmarked.

But as of RAM, it has taken lil more I guess. Free size after disabling pp is 240 and I guess it was 290+ when enabled (Default pp). I forgot to take the exact free space. so 50MB approx! :rolleyes:

Edit: oh ****, it reached to 216 free ram after I ran devhealth. Curious about what is using so much memory. I haven't ran any app either. Just navigated though manila tabs, file explorer, task manager and devhealth.
[Windows Mobile] AndrewSh:
I normally have the following meanings (permanently) on my Leo TMOUS:

Total 475,64 Mb

In use - about 220

Free - about 255

That's after flashing.

After some activities free meaning can be reduced to 235 (actually usually not lower) and it increases after idle up to 245 - 250 by itself.

Something like that.

ffboy2009, if one of the files being cached is not currently opened for editing or something like that - then wait for the reply of ultrashot - he's in charge of Error Code 14

:)
[Windows Mobile] ultrashot:
either it doesn't like chinese paths or file can't be opened for reading.
[Windows Mobile] ffboy2009:
do u mean the OSbuilder can't open file with chinese paths or with a chinese file name?

but why i can build well in other verison os OSB?

i'm sure the file that can't caching is'nt useing or editing by any programme

may be i will change the chinese paths or file names to english and give a try
[Windows Mobile] AndrewSh:
New built-in ImgFsFromDump engine (part of OsBuilder) is not currently in Unicode - so just use non-Chinese names in path.... Older OsBuilder versions had different engine.
[Windows Mobile] ultrashot:
In some specific cases chinese path may work, but no special support was done. Perhaps in next version.
[Windows Mobile] ultrashot:
Next osb provides full support of unicode file names.
[Windows Mobile] -=Barin=-:
OS Builder V1.2.148 is ready
[Windows Mobile] AndrewSh:
OS Builder V1.2.148 FULL (04.09.2011) changelog

1. IMGFS assembling engine now supports paths and object names in UNICODE. (Hats off to ultrashot)

2. Several internal fixes (not visible from UI but important)
[Windows Mobile] caliban2:
@point 2:

are they that important that re-cooking a .143-rom is indicated? :)
[Windows Mobile] AndrewSh:
Is re-cooking a big deal? If yes - do not re-cook. :)
[Windows Mobile] caliban2:
huh?! then i shouldn't be cooking my own roms. na, just curious.

too late now anyway, didn't wait for answer - flash already in progress. :rolleyes:
[Windows Mobile] AndrewSh:
caliban2, changes in compression engine - I prefer to re-cook...
[Windows Mobile] CRACING:
@Farmer Ted

I have an issue with HTC Messaging Client not opening when kernel flags is set to 1.

Do you have such issue, just a guess but strange why its happening for me. :confused:

I'm sure its due to kernel flags = 1

@AndrewSh

Metal Detector doesn't wanna open as HTCSensorService.dll is RW Shared in my ROMs. I will confirm this in few mins.

Edit: Sorry, it wasn't RW Shared HTCSensorService.dll fault. Something else is wrong, still digging out.

Edit2: Ok fixed it by refreshing the package from original cab. Strange that package in my kitchen got corrupted. :S

Thanks...

Best Regards
[Windows Mobile] Farmer Ted:
I don't use the HTC messaging client. I know other people had issues with that flag, though, but I'm not sure what they were. Maybe you need to recmod one (or more) of the dll's in that package.
[Windows Mobile] CRACING:
Oh ok.

Anyways, I will stay without that flag as I"m afraid about the unknown issues it may cause to my ROM users. :rolleyes:

Thanks...

Best Regards
[Windows Mobile] ultrashot:
KF=1 can be "emulated" using *.dll and *.exe in demand paging list. No issues with it.

But good demand paging list can really replace KF=1 (and "emulated" one), eliminating performance penalties.