WM6.5 build 21501 kitchen

[meanfishy]

Originally Posted by strickly_ppc670

Is there a way to figure out the if you stuffing too much into your ROM?
I tried building 4 times last night just to see it error out for capacity issues.

Thanks

from what I understand there is no "limit" on ROM size, from my own personal building the closer to 100 MB the better

EDIT: didn't proof

[gguruusa]

Originally Posted by Baryn

RRU Tool is disconnecting my USB connection, but it needs that same connection to flash the ROM. It leads me into a very polished Recovery Mode, though I lose the the ability to reconnect until I shut down the RRU Tool entirely.

What is going on?

Exactly what is supposed to go on, at first. You have one of 3 problems: device isn't unlocked, device is apache, or WMDC needs updating.

[gguruusa]

Originally Posted by meanfishy

from what I understand there is no "limit" on ROM size, from my own personal building the closer to <=1 MB the better

I want to see your rom that is <= 1MB.

There is a physical limit and a practical limit. The practical limit is a about 40MB less than the physcial limit, given todays software. You will get an error during the build if you reach the practical limit.

[meanfishy]

Originally Posted by gguruusa

I want to see your rom that is <= 1MB.

There is a physical limit and a practical limit. The practical limit is a about 40MB less than the physcial limit, given todays software. You will get an error during the build if you reach the practical limit.

See post for edit

[gguruusa]

Originally Posted by meanfishy

from what I understand there is no "limit" on ROM size, from my own personal building the closer to 100 MB the better

The limit is currently set at about 180-190 MB.

[Baryn]

Originally Posted by gguruusa

Exactly what is supposed to go on, at first. You have one of 3 problems: device isn't unlocked, device is apache, or WMDC needs updating.

I appreciate that, but I have an XV6800 and Windows XP, so it cannot possibly be one of those three issues.

[meanfishy]

Originally Posted by Baryn

I appreciate that, but I have an XV6800 and Windows XP, so it cannot possibly be one of those three issues.

not to split hairs but you have listed an Apache next to your name

what does the bootloader (tri color) screen say, so we know which unlocker you used.

[?GotJazz?]

I am running 20931. I have two problems (one is major):

(1) The "Menu" font size seems significantly larger (Notes >> Menu, Internet Explorer >> Menu, etc.)
(2) My battery power dissipates faster than a f@rt on a roller coaster. I was running N2C_5067 previously, and had much longer battery life.

Anybody else?

PS: Other than that, couldn't be happier!

[quadjacks]

when i receive a txt and open txt message, my cursor goes to the actual message instead of the input/type field, annoying... also unless i scroll through all the new txt message in the thread, they remain as new txt, annoying!!!!! is there a fix for either?

[Black69ta]

Ok I have an issue but its one that I have actually had for a long time in fact I have not been able to Burn a ROM since no2chem 5067, been too to busy. but now I want to take tie to figure this out. I get the following error when I run BuildOS, to make a ROM.

Scanning USER_OEM\Nadavi_HTC_GPS_TOOL
ERROR no dsm file found

I have located where the DSM is supposed to be but can't figure out how to get it there since all I find are CAB's of it and nothing that contains the dsm.

I've considered using the OEMizer on a CAB but not quite sure how to use it of if it would even work.

Also I think there is a way to just skip this entry with my selections.txt but I'm not sure exactly how to do that either.

Any help will be greatly appreciated