Titan WM6.1 Build 20755 GPS kitchen

[gguruusa]

Originally Posted by electronicrice

so a recurring issue i've had along with some other people using ROMs past 20273, whenever a threaded text is received, you go into the conversation and rather than defaulting to the text box, the last text received is highlighted in blue. so instead of being able to immediately type, you have to press into the typing field to start a reply...

really annoying. also with multiple new texts, just opening the conversation will not toggle the new texts as read, unless you scroll over and highlight them..

is there anything related to sms that was changed since build 20273?

Nothing changed. Seems to be inherent to the builds.

[five40]

I'm getting "file creator error"

How to resolve this?

[justpctech]

Originally Posted by sadthai

anyone here have the old htc camera album? seems like it was removed and replaced with the new htc album (opal). the new album doesnt seem to view photo in landscape mode. thanks

just checked the HTC Jade Album on my device and landscape works fine on it.

[jminor]

I downloaded latest BuilderOS.msi (twice) and used Updater (twice). When I began to build, got the message that there were "updates available, do I want to use Updater". I began to download the Titan update that but got error "cannot copy file Titan kitchen core - file is unavailable or being used"

[Robtao]

Updater would not copy the BuildOS file. Manual Download for BuildOS.
Manual download failed 2 or 3 times. Finally took and completed.
Install seemed to fail 1st time. "Repair" install worked.
Build failed with "error building default and user .hv" message.
Mortscript broke the build. Removed Mortscript from selection.
Build worked past G'Reloc, but failed after Processing at "Computing Fill level" with "attempt to read/write protected memory. Maybe other memory is corrupt."

Edit: Build completes with no OEMs selected.
Edit: appears to be size level, not a specific OEM.
Edit: Computing Fill level failure appears to be a size limitation (not indicated by yellow or red in the Calc ROM sizes warning) at about 170 MB. (Freaking huge, though.) Edit: Not really true. That is still not the real limit.

Edit: Running the "Calc ROM Sizes" tool causes this break in the build. Since the size is so huge (probably about 200 Mb), there is really little need to check the ROM size. Doing so seems to cause changes in selections to break the builds. Saving, Closing, and Reopening BuildOS will fix the break and allow the build to complete.

By the way, the last BuildOS was a bit slow, and this one is screaming fast.

[Robtao]

Under PIM, Radio selections which should exclude each other allow all to be selected.

Edit: It appears all radio buttons allow all to be selected.

[gguruusa]

Originally Posted by Robtao

Updater would not copy the BuildOS file. Manual Download for BuildOS.
Manual download failed 2 or 3 times. Finally took and completed.

The servers are really busy, and you must have a poor connection

Install seemed to fail 1st time. "Repair" install worked.

uh...that's all your end.

Build failed with "error building default and user .hv" message.
Mortscript broke the build. Removed Mortscript from selection.

Not sure what you have going on there. Mortscript OEM hasn't changed in eons.

Build worked past G'Reloc, but failed after Processing at "Computing Fill level" with "attempt to read/write protected memory. Maybe other memory is corrupt."

Please provice an example of your selections.txt that leads to this. provide personal oems if you are including those in your build, too.

Edit: Build completes with no OEMs selected.

[gguruusa]

Originally Posted by Robtao

Under PIM, Radio selections which should exclude each other allow all to be selected.

Edit: It appears all radio buttons allow all to be selected.

Doh! Thanks for pointing that out.

[Robtao]

When I build with Mortscript, this is what happens (the last few lines of the build process):

importing registry file ".\Registry\ffffffff-4d6e-4e53-a0e4-ca1ff4720ce3.rgu"...
importing registry file ".\Registry\ffffffff-519d-4e0a-a9d2-41b532fe36ff.rgu"...
Failed to parse value name HKEY_LOCAL_MACHINE\Software\Spb Software House\Pocket Plus\11\Applications\MortScript.exe!!!
InitRegistry FAILED in file ".\Registry\ffffffff-519d-4e0a-a9d2-41b532fe36ff.rgu" within a few lines of line 31.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\ffffffff-519d-4e0a-a9d2-41b532fe36ff.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives

I just tested a working build and it broke the same way as before.

[justpctech]

yes the rgu in mortscript is jacked. i'll try to get it fixed ASAP.