Guide to changing your pagepool

[lafester]

Regarding pagepool changers... to my knowledge there is no pagepool changer for the touch pro as of yet. I know someone was working on it but I am not sure where it stands as of now.

A couple chefs have modified their roms in order to use the current pagepool changer however this is not going to work in most cases. feel free to post your experiences with pagepool changers here as well.

Information about the pagepool changer can be found here:
http://forum.xda-developers.com/showthread.php?t=323269

thanks, chris

[creedin]

the problem is the page pool changer doesnt work with dynamic values, only static

[esqueue]

Originally Posted by creedin

the problem is the page pool changer doesnt work with dynamic values, only static

I have a few questions for you. From it's name I assume that Static pagepool remains the same while dynamic changes. My questions are, how do I check my pagepool? Do I have to set a value for both dynamic and static or Do I have to pick one?

Thank you in advance.

[creedin]

Originally Posted by esqueue

I have a few questions for you. From it's name I assume that Static pagepool remains the same while dynamic changes. My questions are, how do I check my pagepool? Do I have to set a value for both dynamic and static or Do I have to pick one?

Thank you in advance.

static = "stays"
dynamic = "dynamite" as in it goes everywhere

just for a little help

you only have to set one of them, static is what i use, a static 32 mb, gives me 184.13 ram

now to change it you have to get a hex editor and search for...

03 15 A0 03 06 16 A0 13 00 10 83 e5 3e

that key, there will be two occurences, change both values (03 15 only) to

"[PAGEPOOL EXAMPLES]

Below are examples of some possible values for the first two bytes of the pagepool offset.

03 15 - Sprint Diamond WM 6.1 stock rom (1.09) default; 12MB dynamic (When viewed under Settings -> System -> Memory, you should have around 203.84MB of Total Program memory available.)
02 15 - 8MB dynamic
01 15 - 4MB dynamic
18 16 - 24MB static (should give you around 191.84MB Total Program memory)
10 16 - 16MB static (should give you around 199.84MB Total Program memory)

[PAGEPOOL EXPLANATIONS AND CALCULATIONS]

"XX 15" pagepools are dynamic based (first byte value multiplied by 4 to determine pagepool size)
"XX 16" pagepools are static based (first byte value multiplied by 1 to determine pagepool size)

03 15 = 0x03 * 0x400000=0xC00000=decimal 12582912 bytes = 12 MB dynamic pagepool
02 15 = 0x02 * 0x400000=0x800000=decimal 8388608 bytes = 8 MB dynamic pagepool
18 15 = 0x18 * 0x400000=0x6000000=decimal 100663296 bytes = 96 MB dynamic pagepool
18 16 = 0x18 * 0x100000=0x1800000=decimal 25165824 bytes = 24 MB static pagepool
10 16 = 0x10 * 0x100000=0x1000000=decimal 16777216 bytes = 16 MB static pagepool
20 16 = 0X20 * 0x100000=0x2000000=decimal 33554432 bytes = 32 MB static pagepool"

copied from http://forum.ppcgeeks.com/showthread.php?t=43110

[FormerPalmOS]

Originally Posted by creedin

static = "stays"
dynamic = "dynamite" as in it goes everywhere

just for a little help

you only have to set one of them, static is what i use, a static 32 mb, gives me 184.13 ram

now to change it you have to get a hex editor and search for...

03 15 A0 03 06 16 A0 13 00 10 83 e5 3e

that key, there will be two occurences, change both values (03 15 only) to

"[PAGEPOOL EXAMPLES]

Below are examples of some possible values for the first two bytes of the pagepool offset.

03 15 - Sprint Diamond WM 6.1 stock rom (1.09) default; 12MB dynamic (When viewed under Settings -> System -> Memory, you should have around 203.84MB of Total Program memory available.)
02 15 - 8MB dynamic
01 15 - 4MB dynamic
18 16 - 24MB static (should give you around 191.84MB Total Program memory)
10 16 - 16MB static (should give you around 199.84MB Total Program memory)

[PAGEPOOL EXPLANATIONS AND CALCULATIONS]

"XX 15" pagepools are dynamic based (first byte value multiplied by 4 to determine pagepool size)
"XX 16" pagepools are static based (first byte value multiplied by 1 to determine pagepool size)

03 15 = 0x03 * 0x400000=0xC00000=decimal 12582912 bytes = 12 MB dynamic pagepool
02 15 = 0x02 * 0x400000=0x800000=decimal 8388608 bytes = 8 MB dynamic pagepool
18 15 = 0x18 * 0x400000=0x6000000=decimal 100663296 bytes = 96 MB dynamic pagepool
18 16 = 0x18 * 0x100000=0x1800000=decimal 25165824 bytes = 24 MB static pagepool
10 16 = 0x10 * 0x100000=0x1000000=decimal 16777216 bytes = 16 MB static pagepool
20 16 = 0X20 * 0x100000=0x2000000=decimal 33554432 bytes = 32 MB static pagepool"

copied from http://forum.ppcgeeks.com/showthread.php?t=43110

There is a bit of misinformation here. The approach you are suggestion will indeed change the pagepool but it will always change it to a static value. There is no concept of an XXX size dynamic page pool. Dynamic means the device can use as much RAM as it wants for a pagepool.

The procedure above is changing the value that gets written into a memory manager structure that defines the pagepool size. In ARM assembly language the two bytes being changed represent a constant and a shift value. If the 2nd byte is 16, then the value is the first byte. If the 2nd byte is 15 then the value is 4x the first byte. Thus 02 15 = 08 16 = 8MB pagepool. If you want a dynamic page pool, use 00 15. This establishes the value of 0 written to the memory manager structure (00 16 will yield the same result). Adventuresome non-Verizon folks could try this and see how it goes. Verizon folks should probably NOT try this.

Write the same value to both occurences of xx 15 or xx 16 - eg 04 15 A0 03 04 15 A0 13 will give you a 16MB page pool.

Non-Verizon folks can go for 24MB. Higher is possible but you may reach diminishing returns beyond 24MB. Us poor gimped Verizon folks should go for 8-12 for fully-loaded ROMs, 16MB if stripped down. For every 4MB more of pagepool that's 4MB less of program memory.

Note - the pagepool changer app floating around WILL NOT WORK on Touch Pro ROMs without an additional hex edit. If you are doing hex edits, might as well just make the above change and skip using the pagepool changer.

[keaolyen]

Originally Posted by FormerPalmOS

There is a bit of misinformation here. The approach you are suggestion will indeed change the pagepool but it will always change it to a static value. There is no concept of an XXX size dynamic page pool. Dynamic means the device can use as much RAM as it wants for a pagepool.

The procedure above is changing the value that gets written into a memory manager structure that defines the pagepool size. In ARM assembly language the two bytes being changed represent a constant and a shift value. If the 2nd byte is 16, then the value is the first byte. If the 2nd byte is 15 then the value is 4x the first byte. Thus 02 15 = 08 16 = 8MB pagepool. If you want a dynamic page pool, use 00 15. This establishes the value of 0 written to the memory manager structure (00 16 will yield the same result). Adventuresome non-Verizon folks could try this and see how it goes. Verizon folks should probably NOT try this.

Thanks, this makes sense.

I was reading the first part but the values the OP had in his explanation didn't add up, this does.

Admin should sticky this somewhere, there seems to be a lot of confusion out there about how pagepool is calculated.

[lafester]

Originally Posted by FormerPalmOS

There is a bit of misinformation here. The approach you are suggestion will indeed change the pagepool but it will always change it to a static value. There is no concept of an XXX size dynamic page pool. Dynamic means the device can use as much RAM as it wants for a pagepool.

The procedure above is changing the value that gets written into a memory manager structure that defines the pagepool size. In ARM assembly language the two bytes being changed represent a constant and a shift value. If the 2nd byte is 16, then the value is the first byte. If the 2nd byte is 15 then the value is 4x the first byte. Thus 02 15 = 08 16 = 8MB pagepool. If you want a dynamic page pool, use 00 15. This establishes the value of 0 written to the memory manager structure (00 16 will yield the same result). Adventuresome non-Verizon folks could try this and see how it goes. Verizon folks should probably NOT try this.

Write the same value to both occurences of xx 15 or xx 16 - eg 04 15 A0 03 04 15 A0 13 will give you a 16MB page pool.

Non-Verizon folks can go for 24MB. Higher is possible but you may reach diminishing returns beyond 24MB. Us poor gimped Verizon folks should go for 8-12 for fully-loaded ROMs, 16MB if stripped down. For every 4MB more of pagepool that's 4MB less of program memory.

Note - the pagepool changer app floating around WILL NOT WORK on Touch Pro ROMs without an additional hex edit. If you are doing hex edits, might as well just make the above change and skip using the pagepool changer.

this sounds reasonable however the information posted here is not new. I'm wondering why nobody has challenged this before now.

regardless i will update the first post to keep everyone informed.

[gguruusa]

Originally Posted by lafester

this sounds reasonable however the information posted here is not new. I'm wondering why nobody has challenged this before now.

Can't say I've looked at the assembly instructions, but this explanation doesn't jive particularly well (doesn't mean it's wrong, either) with the settings in a stock rom.

[keaolyen]

Originally Posted by FormerPalmOS

Write the same value to both occurences of xx 15 or xx 16 - eg 04 15 A0 03 04 15 A0 13 will give you a 16MB page pool.

Is there a typo there (well, something left out)? I follow the first part but I don't think the second part where you state that "04 15 A0 03 04 15 A0 13" will give you a 16MB page pool was all you meant to say...

Shouldn't there have been more? Another string showing "10 16 A0 03 10 16 A0 13" as also giving you a 16MB dynamic page pool?

[FormerPalmOS]

Originally Posted by keaolyen

Is there a typo there (well, something left out)? I follow the first part but I don't think the second part where you state that "04 15 A0 03 04 15 A0 13" will give you a 16MB page pool was all you meant to say...

Shouldn't there have been more? Another string showing "10 16 A0 03 10 16 A0 13" as also giving you a 16MB dynamic page pool?

You are correct - 04 15 will yield the same pagepool size as 10 16. However in either case it will be a static page pool of size = 16MB. There is no concept of a dynamic pagepool of size xxx. Dynamic pagepool size is whatever size Windows Mobile thinks it needs to be up to the limit of available RAM.