WM 6.5 Kitchen QVGA and VGA Developer Edition

[joojoobee666]

Is there some way we can tell how much space is going to be needed for module allocation from the WMReloc log so we can catch this before we flash and bang our heads on the wall?

[conflipper]

no real way to know. look at the log to see how many modules are being reloc when it finish, and it boots.

and then do it again when it fails. and try and narrow it down between those 2 numbers. I have seen it said that around 345 it will not boot.

[inertiax3]

Originally Posted by conflipper

no real way to know. look at the log to see how many modules are being reloc when it finish, and it boots.

and then do it again when it fails. and try and narrow it down between those 2 numbers. I have seen it said that around 345 it will not boot.

Could be.. again, thanks for pointing this out

With WM65 build 21231, on i780 (GSM) .. 321 relocated modules .. ROM boots and works OK

[anryl]

Originally Posted by ankit360

my 21231 SYS working on Gene full qwerty keyboard working fine

21231SYS.7z 18.83 MB (QVGA)

XIP

thanx this one perfect on kaiser

its all probably to too many modules as well

[dan-htc-touch]

just thought I would add a +1 for recmodding modules solving issues, on herman, I could not see storage, magicall 2.0 would not open, and ringtones were corrupted, recmodded browsingcore and browsingie, and all is well now

[joojoobee666]

Originally Posted by conflipper

no real way to know. look at the log to see how many modules are being reloc when it finish, and it boots.

and then do it again when it fails. and try and narrow it down between those 2 numbers. I have seen it said that around 345 it will not boot.

When I get some time, I will check this out. I do know that my last build (working fine so far) reloc'd 295 modules. But recmodding the browsing files only removes 18 modules.

Here's the first line and last line with the address blocks:

First
NextSlot: 01F7F000 03D66000
Module name: bthasplugin.dll (01F7F000 - 03D66000)
.
.
.
NextSlot: 0184E000 01840000
Module name: mscoree.dll (0184E000 - 01840000)
Last

My thought is that it's NOT necessarily the amount of modules being reloc'd, but how much is allocated in total. But, my limited understanding is that they have to be allocated in blocks of 0x1000 so MAYBE a lot of small modules could cause the issue too?

[anryl]

by last builds all were working fine no need for recmode but i did have romhdr value changed from 83400000(kaiser original) to 84400000 so gona test it when have time if it makes more space for modules

[gguruusa]

Originally Posted by conflipper

no real way to know. look at the log to see how many modules are being reloc when it finish, and it boots.

and then do it again when it fails. and try and narrow it down between those 2 numbers. I have seen it said that around 345 it will not boot.

It's a factor of multiple things. The exact number will vary, depending on modules in play. It's not as simple as just adding total size up, either.

And yes, it is calculatable, just not easily so...maybe we'll see that in the next generation of these tools.

[joojoobee666]

Originally Posted by anryl

by last builds all were working fine no need for recmode but i did have romhdr value changed from 83400000(kaiser original) to 84400000 so gona test it when have time if it makes more space for modules

Doesn't the kernel have to know where the allocation starts though?

[conflipper]

Originally Posted by gguruusa

It's a factor of multiple things. The exact number will vary, depending on modules in play. It's not as simple as just adding total size up, either.

And yes, it is calculatable, just not easily so...maybe we'll see that in the next generation of these tools.

this is true, it will be the size of all the modules, and not the number. so if you take 14 modules that are 5mb each, and 28 modules that are 100kb each, the 28 modules will take up less space, but give a higher total at the end. and you will be better off with more.

but yeah it is the size of the modules that will matter.