Guide to changing your pagepool

[raidzero]

Does anyone have any suggestions for the VZW TP as to static/dynamic and what size would be optimal? I guess it probably depends on what you use the device for... But does anyone have any basic guidelines? Right now I am using a static 28mb pagepool. I use Bluefire VPN, mocha telnet, office, opera, google maps mainly.

[lafester]

Originally Posted by raidzero

Does anyone have any suggestions for the VZW TP as to static/dynamic and what size would be optimal? I guess it probably depends on what you use the device for... But does anyone have any basic guidelines? Right now I am using a static 28mb pagepool. I use Bluefire VPN, mocha telnet, office, opera, google maps mainly.

with vzw you have to be careful with ram use so its a bit trickier.
I think you are on the right track.. you will just have to play with it and see whats best for you.

[esqueue]

Credin, thanks for that response.

[LilRico]

GREAT WRITE-UP/ GUIDE. The only thing it is missing is how you can check your PP once you modified it and loaded it onto the phone.

[creedin]

Originally Posted by LilRico

GREAT WRITE-UP/ GUIDE. The only thing it is missing is how you can check your PP once you modified it and loaded it onto the phone.

simple, first, it actually flashes, second, the memory will be less, ie instead of seeing about 203 mb of free ram, you would see 184 for 32 mb, 192 for 24mb

[LilRico]

Originally Posted by creedin

simple, first, it actually flashes, second, the memory will be less, ie instead of seeing about 203 mb of free ram, you would see 184 for 32 mb, 192 for 24mb

That is correct... I only said something because someone PM'd me about it. Thanks again...

[keaolyen]

Thanks for making the update.

[FormerPalmOS]

I think the issue is with the definition of static vs. dynamic pagepool, and the specific directions how to change the pagepool and to what and why. My particular point of clarification of misinformation was that you can set a "dynamic" pagepool of size xxx. There is no such option. You can either set a static pagepool size of xxx or set a dynamic page pool. Static means the PP is xxx. Dynamic means the PP size is whatever WM6.1 thinks it should be without regard to how much free ram you may need (or have).

Below is an exerpt from the stock Verizon WM6.1 ROM NK.EXE module, disassembled into ARM instructions, referencing the data structure for setting the page pool. The stock Sprint ROM will have a similar sequence but likely at a different address and definitely with different pagepool sizes. Custom ROMs will also have either different sizes, or will replace the last STR instruction with MOV R0, R0 (effectively a NOP).

I've added everything after a semicolon as commentary, everything to the left of ; is pure ARM code disassembly so there is no subjectivity in interpreting the code. The code basically checks something, and based on whatever that something is determines if it shoudl set a static 12MB or 6MB pagepool. Whatever it checks results in it deciding on a 6MB pagepool for my device stock. The patch I recommend sets xxx MB regardless of the outcome of this check.

0005a06c: e59f3758 ldr r3,#0x5a7cc ; = #0xba0810c0 ; Load R3 with 0xba0810c0
0005a070: e59f0750 ldr r0,#0x5a7c8 ; = #0x80006b90 ; Unrelated register load, might be used in called sub
0005a074: e5933000 ldr r3,[r3,#0] ; Load R3 with data at address 0xba0810c0 + 0x00
0005a078: e3530c01 cmp r3,#0x100 ; Compare R3 with value of 0x100
0005a07c: e59f3740 ldr r3,#0x5a7c4 ; = #0x803d6350 ; Load R3 with 0x803d6350 (pointer to PP size constant)
0005a080: 03a01503 moveq r1,#0xc00000 ; If R3 compare was equal, load R1 with value xC00000 (12MB PP size)
0005a084: 13a01606 movne r1,#0x600000 ; If R3 compare was not equal, load R1 with value 0x600000 (6MB PP size)
0005a088: e5831000 str r1,[r3,#0] ; Store R1 at address 0x803D6350 (location of PP size)

[keaolyen]

Originally Posted by FormerPalmOS

The code basically checks something, and based on whatever that something is determines if it shoudl set a static 12MB or 6MB pagepool. Whatever it checks results in it deciding on a 6MB pagepool for my device stock. The patch I recommend sets xxx MB regardless of the outcome of this check.

So you're using a static page pool. Why wouldn't one always use a dynamic page pool assuming you've got plenty of available RAM?

[gguruusa]

Originally Posted by FormerPalmOS

You can either set a static pagepool size of xxx or set a dynamic page pool. Static means the PP is xxx. Dynamic means the PP size is whatever WM6.1 thinks it should be without regard to how much free ram you may need (or have).

Where'd that definition of dynamic come from? I can envision several strategies for dynamic beyond that one.