[PRJ][UPG]Universal ELF/IN 1.1.x & 2.2.X Roms PP Changer

[Swiftblade]

For Cooks


The main reason for creating this thread is that many here in this forum have asked me for the method to change the pagepool of the later ELFin ROMs that are based on the 2.20.xxx.xx stock roms. Incidentally, these ROMs are also used for the ELFs.

Firstly, I must thank duttythroy's thread HERE (http://forum.xda-developers.com/showpost.php?p=2098356&postcount=1) in the Kaiser forum that inspired me to successfully search for the illusive pagepool offsets in the ELFin ROMs, which I was searching for months. Following the same modus operandi, the unique hex string pattern responsible for the pagepool was found to be:
|03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB|



This walkthrough is targeted at the more advance users i.e. Chefs and I shall not be responsible for any damages to your devices if you do not follow the instructions given below.

For Regular Non Cooking Users please Look at The Second Post (http://forum.xda-developers.com/showpost.php?p=2274535&postcount=2) with the Multi PP Changer (Beta For Now)



Let me do a walkthrough on how to change the ELFin's 12MB Default Pagepool to 18MB Pagepool and other pagepools of your desire

[12MB Pagepool] |03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB| ELFin's Default Pagepool
[16MB Pagepool] |10 16 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[18MB Pagepool] |12 16 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[24MB Pagepool] |18 16 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB|

To begin with, we will need a few stuff to perform the pagepool change:

- OS.nb or .NBH file (your targeted 2.20.xxx.xx ROM)
- A Hex Editor [Hex Edit Free 2.5 (http://www.download.com/Hex-Edit-Free/3000-2352_4-10046060.html?tag=lst-1)] to edit the offsets
- Alot of guts.... keke :D

1. [HOW TO CHANGE ELFIN'S PAGEPOOL]

Step 1: Open the OS.nb or .NBH file with a Hex Editor
Step 2: Search the for hex string pattern |03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB| (Two addresses should be found)
Step 3: At the first address found, change the first two bytes "03 15" to "12 16" for 18MB pagepool
Step 4: Repeat Step No.3 at the 2nd address found
Step 5: Save & Exit the Hex Editor
Step 6: If you are using the OS.nb, start cooking your new ROM with it
Step 7: Flash the new .NBH file to your ELFin and enjoy the 18MB True Pagepool

For other pagepool sizes, change the first byte "03" to "XX" hex value corresponding to your desired pagepool in Step No.3 & 4. (Remember that this is hex value, i.e. "10" = 16MB, "12" = 18MB, "18" = 24MB, etc.)

2. [HOW TO CHANGE ELF'S PAGEPOOL]

Through comparison, I also discovered that the ELF's Default Pagepool is 8MB and is different from the ELFin's 12MB Pagepool within the same ROM. I reckoned then that it must be determined by a different set of bytes in the unique hex string pattern and discovered that they are "02 15", the fifth and sixth bytes of the string pattern:

[8 MB Pagepool] |03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB| ELF's Default Pagepool
[4 MB Pagepool] |03 15 A0 03 | 04 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[6 MB Pagepool] |03 15 A0 03 | 06 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[0 MB Pagepool] |03 15 A0 03 | 00 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|

Step 1: Open the OS.nb or .NBH file with a Hex Editor
Step 2: Search the for hex string pattern |03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB| (Two addresses should be found)
Step 3: At the first address found, change the 5th & 6th bytes "02 15" to "04 16" for 4MB pagepool
Step 4: Repeat Step No.3 at the 2nd address found
Step 5: Save & Exit the Hex Editor
Step 6: If you are using the OS.nb, start cooking your new ROM with it
Step 7: Flash the new .NBH file to your ELF and enjoy the 4MB True Pagepool

For other pagepool sizes, change the fifth byte "02" to "XX" hex value corresponding to your desired pagepool in Step No.3 & 4. (Remember again that this is hex value, i.e. "04" = 4 MB, "06" = 6 MB, "00" = 0 MB, etc.)

3. [EFFECTS OF ZERO PAGEPOOL:]

No pagepool or zero pagepool will force the device to go into the dynamic mode where the entire RAM can be used for pagepooling without limits. Your device should be snappier but your used RAM memory might suffers at times. Appear to work well for devices like Elf, Prophet, etc with low RAM memory of 64MB and below. Some tests carried out by the Dynamic Duo ababrekar and htctouchp had confirmed this phenomenon. Tests on Kaiser with 128MB RAM had shown disastrous results: the kaisers were just crawling very slowly... hehe. Some people sweared by it and said it's SUPER-FAST! Well, this you got to find out by yourself...:p

NOTE: I have intentionally described the steps in details in the hope that someone who is good in programming will develop a simple "Change Pagepool" program that can do all these with the simple click of a few buttons. Better still if the progam can change the pagepool of the ROM that is in use through USB activesync...That will be the day! :D

HAVE FUN & ENJOY YOUR TRUE PAGEPOOL! ;)

For Reference: SPB Benchmarking on the different pagepools done by pof (http://forum.xda-developers.com/showthread.php?t=295932) and Larentius26 (http://forum.xda-developers.com/showpost.php?p=2106352&postcount=132)

For those who want to change pagepool in ELF, the easy way using USB Activesync, download the small Change Pagepool App (ELF) created by tabi13 below:
ChangePPvAS (http://forum.xda-developers.com/attachment.php?attachmentid=101806&d=1217015256)

[dsixda]

This tool provides support for both Elf/Elfin and 1.1x/2.2x/3.xx ROMs, so it is a true universal Page Pool Changer. It will write to the appropriate area in memory, reboot your device and then read back the new value. This method is much faster than changing the page pool in the ROM file by hand, which requires re-flashing the entire ROM.

To use this: Unzip the attachment, connect your device to ActiveSync and then run pp.bat.
USE AT YOUR OWN RISK. BETA VERSION ONLY SO FAR. ENSURE YOU HAVE THE USPL INSTALLED!

This program would not have been possible without people like Swiftblade, tabi13, ayyu3m, htctouchp, Noonski and other cookers providing the offsets/strings to write to as well as testing it.


Posts for this Universal Testing PP Changer starts here:
http://forum.xda-developers.com/showpost.php?p=2585064&postcount=123


UPDATE: Now working with all 3.xx ROMs, INCLUDING 3.xx ROMs with ULDR removed.
STILL TO DO: 2.xx ROMs with ULDR removed


SCREENSHOT #1 - Changing Page Pool:

http://i293.photobucket.com/albums/mm71/dsi76/screenshots/screen1-1.gif


SCREENSHOT #2 - Reading back the new value after reboot (reboot time is partly dependent on the new page pool size):

http://i293.photobucket.com/albums/mm71/dsi76/screenshots/screen2-2.gif


I will need feedback for the following:

1) Elf with 2.2x ROM
2) Elfin with 2.2x ROM
3) Elf with 1.1x ROM
4) Elfin with 1.1x ROM (NOTE: don't flash a 1.1x shipped ROM on your Elfin! Use just the OS ROM)
5) Elfin with 2.81 ROM*
6) Elf with 3.xx ROM
7) Elfin with 3.xx ROM

*It looks like Elfins that come installed with a 2.81 stock ROM do not contain the Page Pool values at the expected locations. If you however flash the dumped 2.81 ROM to a non-2.81 Elfin, the PP is read correctly on the non-2.81 Elfin.

[Ameet]

cool walkthrough brother.. cool.. keep it up.. hope to see a nice pagepool changing software someday by some programmer ;)

[!Aman!]

Oops... some errors here.:( Thanks bro for pointing them out. I will edit them in a moment.:D
thanks for such an explanatory post bro :)
i've one question though. i modified the PP of my ROM to 16 MB and after flashing just when i got the prompt for screen alignment, i got some errors showing some exe's not able to run namely replog.exe, tskschedule.exe and 3-4 others. i didnt modify anything else in the ROM.

[Ameet]

how is the he value calculated? i want a 6mb pp for which i dont know what the hex value would be.. is there a calculator or something? so i wont have to ask each time ;)

[Swiftblade]

thanks for such an explanatory post bro :)
i've one question though. i modified the PP of my ROM to 16 MB and after flashing just when i got the prompt for screen alignment, i got some errors showing some exe's not able to run namely replog.exe, tskschedule.exe and 3-4 others. i didnt modify anything else in the ROM.

Hi htctouchp.. did you change the "03 15" at both occurrences in the .nbh files. The patterns should only appear twice, if not somethings is very wrong.. just curious.. you use os.nb or .nbh file?

[!Aman!]

Hi htctouchp.. did you change the "03 15" at both occurrences in the .nbh files. The patterns should only appear twice, if not somethings is very wrong.. just curious.. you use os.nb or .nbh file?
actually i tried this just 5 mins before ur post, in the manner explained by dutty(and ameet), first edited the S000 of nk.exe and then modified the os.nb and while editing the os.nb, i found this pattern just once, not twice.

[Swiftblade]

how is the he value calculated? i want a 6mb pp for which i dont know what the hex value would be.. is there a calculator or something? so i wont have to ask each time ;)

Some numbers in hex:

"00" = 0
"01" = 1
"02" = 2
"03" = 3
"04" = 4
"05" = 5
"06" = 6
"07" = 7
"08" = 8
"09" = 9
"0A" = 10
"0B" = 11
"0C" = 12
"0D" = 13
"0E" = 14
"0F" = 15
"10" = 16
"11" = 16+1 = 17
"12" = 16+2 = 18
"13 = 16+3 + 19
.....

[Ameet]

Some numbers in hex:

"00" = 0
"01" = 1
"02" = 2
"03" = 3
"04" = 4
"05" = 5
"06" = 6
"07" = 7
"08" = 8
"09" = 9
"0A" = 10
"0B" = 11
"0C" = 12
"0D" = 13
"0E" = 14
"0F" = 15
"10" = 16
"11" = 16+1 = 17
"12" = 16+2 = 18
"13 = 16+3 + 19
.....

cool.. so for 4mb pp, i have "04 16"
for 6mb pp, i should have "06 16"
and for 8mb pp, i should have "08 16"

rite? :) thanks for the prompt reply brother

[Swiftblade]

actually i tried this just 5 mins before ur post, in the manner explained by dutty(and ameet), first edited the S000 of nk.exe and then modified the os.nb and while editing the os.nb, i found this pattern just once, not twice.

hi htctouchp... the string pattern in Kaiser is different from ELFin and that explained why you found it once. So you probably edited some .exe program instead of pagepool.

Search the string pattern as given above and try it again. Should work and forget about nk.exe, just do it on the .NBH file straightaway and re-flash it back to your device. Cheers.

[!Aman!]

hi htctouchp... the string pattern in Kaiser is different from ELFin and that explained why you found it once. So you probably edited some .exe program instead of pagepool.

Search the string pattern as given above and try it again. Should work and forget about nk.exe, just do it on the .NBH file straightaway and re-flash it back to your device. Cheers.
no bro...i meant i only used that method..but the string which i used was the same as the one mentioned by u.

[Swiftblade]

no bro...i meant i only used that method..but the string which i used was the same as the one mentioned by u.

What ROM are you using? 1,17.xxx or 2.20.xxx ??

If you are using the 2.20.xxx rom and editing the .NBH file, the addresses found should be at 0X438DC and 0X353637... try searching again...

[!Aman!]

What ROM are you using? 1,17.xxx or 2.20.xxx ??

If you are using the 2.20.xxx rom and editing the .NBH file, the addresses found should be at 0X438DC and 0X353637... try searching again...
yup, the strings are at these very addresses mentioned by u bro and i use 2.20.xxx ROM

[pkoper]

Excellent.... have been waiting for this. Good job!

[zeflash]

THANK YOU!
thank you!
Finally I am able to get new ROMs with proper 4MB pagepool on my puny Elf!!!

Tried the trick on Ameet's 4.01 UC rom, and it worked.

[Swiftblade]

THANK YOU!
thank you!
Finally I am able to get new ROMs with proper 4MB pagepool on my puny Elf!!!

Tried the trick on Ameet's 4.01 UC rom, and it worked.

Excellent.... have been waiting for this. Good job!

We are here to share and it's good to know that it is of help to you bros.... Enjoy the true pagepool... keke c",)

yup, the strings are at these very addresses mentioned by u bro and i use 2.20.xxx ROM

How did it go? Manage to solve the problem? I re-look your problem and it might not be related to the pagepool changing.

I suspect one or two things: UC and/or SQM removed from your Rom... ?? And again I may be very wrong.... Cheers.

[Ameet]

I suspect one or two things: UC and/or SQM removed from your Rom... ?? And again I may be very wrong.... Cheers.

even i can find only one instance of the hex string if i try to edit the nbh or nb file directly.. but i have the sqm removed from my rom, is that why?

[Swiftblade]

even i can find only one instance of the hex string if i try to edit the nbh or nb file directly.. but i have the sqm removed from my rom, is that why?

They are 2 separate issues. I'm saying that if SQM module in WM6.1 is not removed properly, it can cause some of the .dlls not loading as mentioned by Aman.

Ameet bro... you mean you can only find one instance of the hex string in your roms? Only possibility of that happening is when the nk.exe in the XIP was removed during porting.... Now this get me thinking, maybe we need to hex edit only once, i.e. the higher offset at 0X353637....ummh...:confused:

The one instance of hex string is at the higher offset address in your case?

[Ameet]

They are 2 separate issues. I'm saying that if SQM module in WM6.1 is not removed probably, it can caused some of the .dll not loading as mentioned by Aman.

Ameet bro... you mean you can only find one instance of the hex string in your roms? Only possibility of that happening is when the nk.exe in the XIP was removed during porting.... Now this get me thinking, maybe we need to hex edit only once, i.e. the higher offset at 0X353637....ummh...:confused:

The one instance of hex string is at the higher offset address in your case?

yes it is the highest offset.. but i tried this trick on a rom in which i had already hex edited the sooo in nk.exe and then after cooking i could find only one instance.. but the trick of directly editing nb file didnt work for me (or maybe i did something wrong, which i'll try again) but the nk.exe trick and then nb files worked like a charm for me

[zeflash]

even i can find only one instance of the hex string if i try to edit the nbh or nb file directly.. but i have the sqm removed from my rom, is that why?

Well, I found 2 instances of the hex chain in your 4.01 rom (nbh direct edit). You might want to check again ;)

[Ameet]

Well, I found 2 instances of the hex chain in your 4.01 rom (nbh direct edit). You might want to check again ;)

yes u will find 2 instances brother.. i found one coz i have already edited the s000 in nk.exe before cooking ;)

[!Aman!]

How did it go? Manage to solve the problem? I re-look your problem and it might not be related to the pagepool changing.

I suspect one or two things: UC and/or SQM removed from your Rom... ?? And again I may be very wrong.... Cheers.

well bro, i rebuilt my nbh file..and edited it like u said...this time no errors like i mentioned before...i dont know what went wrong the first time, lol...and i have removed SQM using no2chem's method from my ROM.

[Swiftblade]

well bro, i rebuilt my nbh file..and edited it like u said...this time no errors like i mentioned before...i dont know what went wrong the first time, lol...and i have removed SQM using no2chem's method from my ROM.

Hi Aman.. good to hear that things worked out and you are back on track...:) In WM6.1, the SQM is definitely more integrated and improper removal will cause those .dll and .exe not working properly.. I have that similar problem when I cooked my first WM6.1 rom... Well, cheers...:D

[!Aman!]

Hi Aman.. good to hear that things worked out and you are back on track...:) In WM6.1, the SQM is definitely more integrated and improper removal will cause those .dll and .exe not working properly.. I have that similar problem when I cooked my first WM6.1 rom... Well, cheers...:D
well bro, i followed an expert's (no2chem) way of removing it...so i dont think that was a problem... moreover, i faced that problem for the first time after removing SQM (used ROM without it for 10 days or so)

[Swiftblade]

well bro, i followed an expert's (no2chem) way of removing it...so i dont think that was a problem... moreover, i faced that problem for the first time after removing SQM (used ROM without it for 10 days or so)

yes, then it must be something else... nevermind and let's move on since it's no more an issue....:)

[kokotas]

Thanks for SHARING man!
I would never find that hex edit for ELFs myself.
You rock;)
Regards!

[ckpv5]

Hi Swiftblade

Wow... it's really amazing. With your guide I managed to change the Kokotas's Light ROM and AB's 4.02 pagepool size to 6MB and 4MB for my ELF.
Thank you.

Appreciate your confirmation on 6MB PP should read as 03 15 A0 03 06 16 or as posted. Both has same effect on the PP on ELF.

Originally Posted by Swiftblade:

[8 MB Pagepool] |03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB| ELF's Default Pagepool
[4 MB Pagepool] |03 15 A0 03 | 04 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[6 MB Pagepool] |12 16 A0 03 | 06 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[0 MB Pagepool] |18 16 A0 03 | 00 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|

Rgds

[Swiftblade]

Many thanks!

--------------------------------------------------------------------------------
Thanks for SHARING man!
I would never find that hex edit for ELFs myself.
You rock
Regards!

You are most welcome! We are here to SHARE, isn't it..:D Got to try out your Light ROM and Ameet's Clean ROM someday...;)

Hope this will relieve the chefs from cooking multi-pagepools rom versions to accede to requests and concentrate on what they do best... and that is COOKING!..keke

I kinda passed on my ELFin to my dearest one and now have "limited access" to it for testing...:( but I'll be getting my Diamond soon I hope..:D

Hi Swiftblade

Wow... it's really amazing. With your guide I managed to change the Kokotas's Light ROM and AB's 4.02 pagepool size to 6MB and 4MB for my ELF.
Thank you.

Appreciate your confirmation on 6MB PP should read as 03 15 A0 03 06 16 or as posted. Both has same effect on the PP on ELF.

Originally Posted by Swiftblade:

[8 MB Pagepool] |03 15 A0 03 | 02 15 A0 13 | 00 10 83 E5 | DA C2 FF EB| ELF's Default Pagepool
[4 MB Pagepool] |03 15 A0 03 | 04 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[6 MB Pagepool] |12 16 A0 03 | 06 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|
[0 MB Pagepool] |18 16 A0 03 | 00 16 A0 13 | 00 10 83 E5 | DA C2 FF EB|

Rgds

Hi ckpv5... no different to the ELF's pagepool which will be 6MB as so correctly confirmed by you. This is because the first two bytes "12 16" or "03 15" there determine the ELFin's pagepool and will not affect the ELF. You can leave them at default "03 15" if you go wishes...

Glad that you find the walkthrough useful...c",) Cheers.

[Ameet]

hi swift.. can u check this post (http://forum.xda-developers.com/showpost.php?p=2277648&postcount=178) and confirm it is correct for elfins please?

[captkkk]

Confirm: It is dead easy to simply use a Hex Editor and edit directly to the NBH file that comes from any, I mean ANY cooked ROM.
Of course those of you who have read my previous posts would know what I was using and reason for switching to Elves 5.0 18MB PP, but since this post shows the dead easy way in changing the PP, I have to go for stability over anything, so I am back to what I was with and a 18MB PP, happily.

[tabi13]

NB: I have intentionally described the steps in details in the hope that someone who is good in programming will develop a simple "Change Pagepool" program that can do all these with the simple click of a few buttons. Better still if the progam can change the pagepool of the ROM that is in use through USB activesync...That will be the day! :D



Swiftblade I have been able to take the old script for ChangePPViaAS script and been able to modify it using your instructions (thank you) so that PP change can be done now through activesync without need to reflash.
But this is for Elf's only and for the offsets for my rom (2.20.707.1B modified) here:
http://forum.xda-developers.com/showthread.php?t=397739

The PP changer is also attached and anyone can download my ROM, decompile the Os.nb and using this thread and my ChangePPViaAS scripts can write their own for Elfs or Elfins.

Write to me if anyone needs help with this but I am sure the talented people here would easily figure it out

[Noonski]

This is the only reason i'm reflashing my phone today.

This must have almost driven you crazy.

Great work, but it's not working ont the current ELF rom i'm using.

[Swiftblade]

This is the only reason i'm reflashing my phone today.

This must have almost driven you crazy.

Great work, but it's not working ont the current ELF rom i'm using.

Hi Noonski... ya it sort of drove me nuts... hehe..:rolleyes:

BTW do you want to point me to the ELF rom that is not working? I promise I will take a peek at it and see what is different. Are you talking about your own TMNL 2.26 rom in your signature and the rom is 1.17.xxx or 2.20.xxx based?

[Swiftblade]

Swiftblade I have been able to take the old script for ChangePPViaAS script and been able to modify it using your instructions (thank you) so that PP change can be done now through activesync without need to reflash.
But this is for Elf's only and for the offsets for my rom (2.20.707.1B modified) here:
http://forum.xda-developers.com/showthread.php?t=397739

The PP changer is also attached and anyone can download my ROM, decompile the Os.nb and using this thread and my ChangePPViaAS scripts can write their own for Elfs or Elfins.

Write to me if anyone needs help with this but I am sure the talented people here would easily figure it out

Hi tabi13... thanks for making the PP Changer. I haven't got a chance to try it though but nice works nevertheless..

Actually, I am also intrigued by kyphur's Kaiser PP Changer HERE (http://forum.xda-developers.com/showpost.php?p=2160011&postcount=1) and it's very nice and neat tool. If someone can go into the .exe file and edit the search addresses to those of Elf's and Elfin's, it should work perfectly.

Do we have a tool to edit .exe file? Cheers, Swiftblade

[Ameet]

Do we have a tool to edit .exe file? Cheers, Swiftblade

umm.. reshack maybe? i dont know programming but thought of still sharing my 2 cents ;)

[Swiftblade]

umm.. reshack maybe? i dont know programming but thought of still sharing my 2 cents ;)

Thanks Ameet. Yes, I think reshack should do it. Use it before a long time ago and now probably need to re-visit it when I have a little more time in hands. :)

[abinbasu]

Thanx a lot swiftblade. you have done a great job. This thread should be made wiki.

[nl1010]

I just used the tool on my Elf with ShadoW 2.1 TE Rom, and it worked :)
I now have a 4MB PP instead of 8MB, seems to work a bit better.
The tool only gives a warning, because the ShadoW ROM was not recognized.
But anyway change the PP result is okay.

Greez,

[wchiaoli]

Thanks very much, it's a very useful and effective method to change the pagepool of the rom file, thanks again!

[Noonski]

Hi Noonski... ya it sort of drove me nuts... hehe..:rolleyes:

BTW do you want to point me to the ELF rom that is not working? I promise I will take a peek at it and see what is different. Are you talking about your own TMNL 2.26 rom in your signature and the rom is 1.17.xxx or 2.20.xxx based?

It's working brother.

I switched Bases to a 2.26 and that's working just fine.
The old one i was using still had some Kaiser stuff in there.

I had to see it first to believe it.

I went crazy over this but the thought never crossed my mind to edit noth instances.

Mand seeing your solution drives me mad, i was this close but i gave up trying because i didn't want to take the risk bricking my device.

Then i take a two months break and both SQM CPUI and PP are solved.
You gotta love it.

Really apreciate this and so will a lot of other users as you know.

Your presence on the ELF thread is apreciated your cooking has motivated me to push it to the limit.

Very Big Up.

[ufoss]

Hi;
I want to ask what is pageepoll.
What is the difference 4, 8, 12, etc..
What is the advantage and disadvantage for machine


Most important what is the best pagepool for elf...

Thanks for answer

[blasev]

Hi;
I want to ask what is pageepoll.
What is the difference 4, 8, 12, etc..
What is the advantage and disadvantage for machine


Most important what is the best pagepool for elf...

Thanks for answer

* What is the page pool ?
The page pool is a reserved area in memory for the windows mobile kernel.
A ROM in a pocket pc is mainly divided into 2 parts (some other: IPL,SPL,ExtROM but forget it) :
- The Kernel
- The OS files (IMGFS)ETEN’s Pocket PCs do not have NOR/NAND ROM but a DiskOnChip that works like a SD card.
The real problem is that the system can’t execute ROM files (including the kernel) directly into the DiskOnChip.
It has to copy ‘pages’ of ROM into the RAM then execute them.
In a PC world it is called ROM shadowing.

To sum it up : the page pool is a container for pages of ROM shadowed in RAM.


* Why changing its size ? Device manufacturers tend to choose a big pool size in order to have a pocket pc that can do a wide range of tasks.
In pratice, most users do the same tasks : GPS mainly, some media, then a classical phone usage.
Most users don’t need a big pool size but a lot of RAM.
taken from " http://www.etenblog.com/2008/01/14/change-your-page-pool-size/"
next time use google dude >_<

as for the best result for elf generally is 4 MB PP (depends on the roms)
next time use search >_<

[dsixda]

This thread should definitely be stickied. I'm always searching for it to "fix" ROMs :-)

[!Aman!]

This thread should definitely be stickied. I'm always searching for it to "fix" ROMs :-)
there are too many stickies already. thats why kokotas has created new thread of "sticky rollup". whatever u need, u will find in that 'one' sticky only ;)

[dsixda]

Oh wow.. never noticed that. Thanks! That's a great idea. I guess we should take down the other stickies then? ;-)

[!Aman!]

yes!!!
but its upto the mods. so lets wait n watch :D

[Ameet]

hi swift.. i did the 0mb pp change trick. my available memory shot up sky high :D but the used memory gained another 10% and became 31% from 21%.. any idea why? but i can see that the device is become more faster and more responsive.. i think i put on some battery life too with that :D

hoping to know what happened to free memory

99600

[dsixda]

Ameet, I am assuming from the picture shown that you have an Elfin. Did you change the first 4 hex digits to "00 00" to get the 0MB PP? I tried that on my PDAViet ROM so that it would go from 18MB to 0MB, but it got stuck at the HTC logo during reset. Thankfully I have a USPL installed already, so I can flash the 18MB PP ROM back.

[!Aman!]

Ameet, I am assuming from the picture shown that you have an Elfin. Did you change the first 4 hex digits to "00 00" to get the 0MB PP? I tried that on my PDAViet ROM so that it would go from 18MB to 0MB, but it got stuck at the HTC logo during reset. Thankfully I have a USPL installed already, so I can flash the 18MB PP ROM back.
no, change the first byte to 00 and second one to 15 or 16 ;)

[Ameet]

no, change the first byte to 00 and second one to 16 ;)

oh i see.. i'll test this one too :) i did 00 15

[dsixda]

oh i see.. i'll test this one too :) i did 00 15

Too late.. i'm flashing 00 16 now :)

[!Aman!]

--deleted--

[dsixda]

i believe if u want a static pp, then u've to change second byte to 16, just like u do it for 4 mb pp ;)

Perhaps this info for 0MB PP should be updated for the 1st page?

[!Aman!]

Perhaps this info for 0MB PP should be updated for the 1st page?
well, that is upto Swiftblade or our new moderator to decide :p

[Ameet]

well, that is upto Swiftblade or our new moderator to decide :p

hmm. what do u say swift? can u add this info to the first post? :) i'll test htctouchp's static pp method of 00 16 and update my post

[dsixda]

Here's some program memory results with my PDAViet ROM:


With 18MB pp (after restore of backup PIMs and software)

101.86 overall
29.24 used
72.62 free


With 0MB pp (after restore of backup PIMs and software)

119.93 overall
40.55 used
79.38 free


So just like Ameet saw, there was about 10MB extra program memory usage with 0 page pool (but I still have more memory free due to no page pool memory being used).

Anyways I'm off to bed ...

[Swiftblade]

hmm. what do u say swift? can u add this info to the first post? :) i'll test htctouchp's static pp method of 00 16 and update my post

Nice results you got there for the zero pagepool. Oh yes, I will update this info in the first post later.

This sort of confirm that when pagepool is set to 0 (whether static or dynamic) the entire Program Memory is available for pagepool. That's explained the increase in Memory Used.

Conclusion: 0 MB Pagepool = Unlimited Pagepool

Perhaps you guys want to confirm that by running some large programs or somethings and monitor the used memory. Most programs don't use more to 10~12MB anyway.. Cheers, Swiftblade

[!Aman!]

brother, can u explain how the default pp comes out to be 12 mb with 03 15?

[!Aman!]

i can confirm by using 00 16 pp edit, the device becomes so so so sluggish. did u experience the same with 00 16 htctouchp?
not at all brother :)
my phone is working as much smoothly as it can ;)

[!Aman!]

wait.. sorry.. i think thats coz i use the glyph cache trick n few others.. will test again without that n then delete my earlier post :)
i also use these glyph cache, file systemcache etc tricks, i always have since the day i learnt cooking :D

EDIT: wait, i need to confirm on this. looks like all of these registry values are default for me :o

[Swiftblade]

brother, can u explain how the default pp comes out to be 12 mb with 03 15?

hi htctouchp... it seems that when it is set to dynamic "XX 15" the first byte value is multiply by 4. Example:

[02 15] = 8 MB pagepool
[03 15] = 12 MB pagepool
[01 15] = 4 MB pagepool
[00 15] = 0 pagepool (of course lah)

[!Aman!]

hi htctouchp... it seems that when it is set to dynamic "XX 15" the first byte value is multiply by 4. Example:

[02 15] = 8 MB pagepool
[03 15] = 12 MB pagepool
[01 15] = 4 MB pagepool
[00 15] = 0 pagepool (of course lah)
thanks a lot brother :)

[Ameet]

Swift, Htctouchp & Gang

I confirm using the 00 16 so called static PP has its perks :D My device is fast and speedy now, also managed to get the used memory down to 27% leaving me free memory (approx. 89MB to play around with ;))

The available memory seen is 119.99MB (but thats again because I have removed a few things from the XIP)

So like I suspected the culprit was the reistry entries :rolleyes: (glyph cache and a few likes) SO Htctouchp, you going to jail for that one :p

99624

[!Aman!]

Swift, Htctouchp & Gang

I confirm using the 00 16 so called static PP has its perks :D My device is fast and speedy now, also managed to get the used memory down to 27% leaving me free memory (approx. 89MB to play around with ;))

The available memory seen is 119.99MB (but thats again because I have removed a few things from the XIP)

So like I suspected the culprit was the reistry entries (glyph cache and a few likes) SO Htctouchp, you going to jail for that one :p
hahaha, u need to come here and escort me to the jail :p

btw, did u experience sluggishness as soon as ur phone booted? coz i've applied those tweaks now, and i really dont feel any problem so far. and how much difference do u feel in the speed after using pp 00 15 and 00 16?

[Ameet]

hahaha, u need to come here and escort me to the jail :p

btw, did u experience sluggishness as soon as ur phone booted? coz i've applied those tweaks now, and i really dont feel any problem so far. and how much difference do u feel in the speed after using pp 00 15 and 00 16?

the device was sluggish just after the bootup for sometime.. between those two its not actually much but u can make out the difference ;)

[!Aman!]

the device was sluggish just after the bootup for sometime.. between those two its not actually much but u can make out the difference ;)
ok, but for me there is no problem so far even after the tweaks. may be i should observe for a few hours to see :rolleyes:

[Swiftblade]

hahaha, u need to come here and escort me to the jail :p

btw, did u experience sluggishness as soon as ur phone booted? coz i've applied those tweaks now, and i really dont feel any problem so far. and how much difference do u feel in the speed after using pp 00 15 and 00 16?

Ya htctouchp should go to jail in Ameet's rpivate prison..keke:D

Just a caution on glyph cache.. it is also using the RAM memory like pagepool. My experience tells me that 16K and 32K are the optimum values. Setting it higher than 64K will at times runs into system errors... So Ameet what values did you set just now?

[Ameet]

Ya htctouchp should go to jail in Ameet's rpivate prison..keke:D

Just a caution on glyph cache.. it is also using the RAM memory like pagepool. My experience tells me that 16K and 32K are the optimum values. Setting it higher than 64K will at times runs into system errors... So Ameet what values did you set just now?

i've kept the default setting of 16k glyph cache and made the 0mb pp change in nk.exe itself :)

[!Aman!]

Ya htctouchp should go to jail in Ameet's rpivate prison..keke:D

Just a caution on glyph cache.. it is also using the RAM memory like pagepool. My experience tells me that 16K and 32K are the optimum values. Setting it higher than 64K will at times runs into system errors... So Ameet what values did you set just now?
right now i'm using 32K glyphcache. the default value was 8K. and so far no issues.

[!Aman!]

right now i'm using 32K glyphcache. the default value was 8K. and so far no issues.
default is 16k for u??? i thought we were using the same SYS :p

[Ameet]

default is 16k for u??? i thought we were using the same SYS :p

:D my bad.. 8k is my default :)

[!Aman!]

:D my bad.. 8k is my default :)
can u tell me what are default values of "ReplStoreCacheSize" and HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Cac heSize=
for u? in my boot.rgu, these values are set to 0 :rolleyes:

[dsixda]

Hi guys,

For my "00 16" ROM, I had set my Glyph Cache (in Schapps' tool) to 32KB, and File System Cache to 2KB. Everything seems to run smoothly.

Also the most noticeable improvement is when I am creating Word Mobile documents. If I select "New", the progress bar at the bottom now zips at a really fast speed! However if I open an existing Word document, it still opens at the same "slow" speed.

[!Aman!]

Hi guys,

For my "00 16" ROM, I had set my Glyph Cache (in Schapps' tool) to 32KB, and File System Cache to 2KB. Everything seems to run smoothly.

Also the most noticeable improvement is when I am creating Word Mobile documents. If I select "New", the progress bar at the bottom now zips at a really fast speed! However if I open an existing Word document, it still opens at the same "slow" speed.
so that means, having 0 mb pp does improve a few things :rolleyes:

[Ameet]

can u tell me what are default values of "ReplStoreCacheSize" and HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Cac heSize=
for u? in my boot.rgu, these values are set to 0 :rolleyes:

in my boot.rgu and device both, the values are 0.. why? any issues? :)

[!Aman!]

in my boot.rgu and device both, the values are 0.. why? any issues? :)
without tweaking these values are 4K for me. in the boot.rgu the value is 0. so i wonder what is changing the value from 0 to 4K :rolleyes:

[Ameet]

without tweaking these values are 4K for me. in the boot.rgu the value is 0. so i wonder what is changing the value from 0 to 4K :rolleyes:

:) maybe something in the rgus u gave me? coz in my device i didnt touch anything and it didnt change :)

[!Aman!]

:) maybe something in the rgus u gave me? coz in my device i didnt touch anything and it didnt change :)
aahhhh, found it :o

[Ameet]

aahhhh, found it :o
where and what was it?

[!Aman!]

where and what was it?
it was in one of the rgu's related to battery performance that i used. but i never opened to see what's inside it :o

[fzzyrn]

I don't know if this has been posted here, but if you set the pagepool to 0 you will have a dynamic pagepool that changes as you need it to. Your device should be far snappier but may have slightly less memory at times

[dsixda]

I don't know if this has been posted here, but if you set the pagepool to 0 you will have a dynamic pagepool that changes as you need it to. Your device should be far snappier but may have slightly less memory at times

Yup this was discussed in the previous 2 pages ;-)

[Swiftblade]

I have updated the first post with some information on the "Effects of Zero Pagepool" on Elfs in particular. These are based on the results of tests carried out by ababrekar and htctouchp.. Cheerio :D

[willy792003]

so, what's the diff between setting it to "00 16" and "00 15"?

[Ameet]

so, what's the diff between setting it to "00 16" and "00 15"?

00 15 creates a dynamic PP whereas 00 16 creates a static PP. But I cant confirm if this theory works on 0MB PP. Swift?

[willy792003]

00 15 creates a dynamic PP whereas 00 16 creates a static PP. But I cant confirm if this theory works on 0MB PP. Swift?

dynamic means it starts from 0 and then dynamically changes whereas static means it stays 0 page pool size?

[guap]

what about to make this thread sticky? :p

[Swiftblade]

00 15 creates a dynamic PP whereas 00 16 creates a static PP. But I cant confirm if this theory works on 0MB PP. Swift?

dynamic means it starts from 0 and then dynamically changes whereas static means it stays 0 page pool size?

@ababrekar & willy...
In theory, what willy stated is correct from my understanding but for zero pagepool, both should be dynamic, i.e. it allows the entire RAM to be used for pagepool if there is a demand for it...

[ayyu3m]

@ababrekar & willy...
In theory, what willy stated is correct from my understanding but for zero pagepool, both should be dynamic, i.e. it allows the entire RAM to be used for pagepool if there is a demand for it...
hey Swiftblade, long time. and while ur here, i wana ask if u gona be making any roms soon??!!

[Swiftblade]

hey Swiftblade, long time. and while ur here, i wana ask if u gona be making any roms soon??!!

Hey ayyu3m... yes long time no see. My cooking tools now are mainly for cooking Diamond ROMs. I thought there is no lack of quality ROMs here from ababrekar, Bram, Noonski, pkoper, kokotas..:D

Tell you what, for old times sake, I am going to dig out my old ELF cooking tools and make one more ELFin ROM... give me abit of time kkk.:)

[ayyu3m]

Hey ayyu3m... yes long time no see. My cooking tools now are mainly for cooking Diamond ROMs. I thought there is no lack of quality ROMs here from ababrekar, Bram, Noonski, pkoper, kokotas..:D

Tell you what, for old times sake, I am going to dig out my old ELF cooking tools and make one more ELFin ROM... give me abit of time kkk.:)
yeah all the cooks are equally great. and i wud like to see ur releases as well, cos each cook have diff styles ;)

[Swiftblade]

yeah all the cooks are equally great. and i wud like to see ur releases as well, cos each cook have diff styles ;)

Yes, each cook has his own preferences. You should try your hands at cooking too..;) It is addictve at times... hehe:D

[Noonski]

Yes, each cook has his own preferences. You should try your hands at cooking too..;) It is addictve at times... hehe:D

ayyu3m, is hardcore Flashing material.

[ayyu3m]

ayyu3m, is hardcore Flashing material.
haha! you throw em' roms, i catch em' roms. keke. all this flashing is makin me want to coooooooooooook. :D

[hendrixus]

I got hold of a Touch XL.
What is the best PP for my TouchXL. The right balance in memory and speed. I am running the org PP of 12MB I think?"Thanks.

[!Aman!]

I got hold of a Touch XL.
What is the best PP for my TouchXL. The right balance in memory and speed. I am running to org PP of 12MB I think?"Thanks.
well, u should test that for your needs. i'll suggest u to try 0 mb, default or 16 mb pp.

[dsixda]

well, u should test that for your needs. i'll suggest u to try 0 mb, default or 16 mb pp.

Actually, so far the best have been either 0 MB or 18 MB (there is no 16MB) :)

[!Aman!]

Actually, so far the best have been either 0 MB or 18 MB (there is no 16MB) :)
no 16 MB??? :D
how can u say that?

[dsixda]

no 16 MB??? :D
how can u say that?

We could try ;-)

[!Aman!]

We could try ;-)
i'm already using 16 mb pp. i've been using it for a month or so

[dsixda]

i'm already using 16 mb pp. i've been using it for a month or so

Sorry for my ignorance! How is it working for you? Compared to 0MB?

[!Aman!]

Sorry for my ignorance! How is it working for you? Compared to 0MB?
well, i've not really noticed any difference in the performance. but i prefer to have a static PP. just my intution :rolleyes:
btw, if u want 16 mb pp for Elfin, first 2 bytes will be "10 16" in place of "03 15"

PS: u still using old SPL :p?

[dsixda]

PS: u still using old SPL :p?

LOL! I downoaded 2.28 this morning and then forgot. Thanks for the reminder!!

[hendrixus]

Actually, so far the best have been either 0 MB or 18 MB (there is no 16MB) :)

OK, I'll try. I am on default right now. For I am gonna to to get my DeviceId and CID (http://forum.xda-developers.com/showthread.php?t=379034)

Make a backup of the ROM (http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom) and hard-SPL the device.Then finding a good ROM:)

So for now I have to step back on one of my others devices like my VOX

[colonel]

I have an elfin (128mb) HTC Touch

however I am unsure as to the advantages/disadvantages of different pagepool sizes.

1. Is smaller or bigger pagepool faster (in terms of OS response) ?
2. is pagepool dynamic (e.g. if 8mb, does this mean its max is 8mb, or always 8mb) ?

could someone explain this ?

[!Aman!]

1. read this thread: http://forum.xda-developers.com/showthread.php?p=2098356#post2098356
although its for kaiser, but u'll get some idea.

2. 8 mb for Elf or 12 mb for Elfin is the fixed default value. it won't change after flashing.

[colonel]

1. read this thread: http://forum.xda-developers.com/showthread.php?p=2098356#post2098356
although its for kaiser, but u'll get some idea.

2. 8 mb for Elf or 12 mb for Elfin is the fixed value. it won't change.

Many thanks
this is quite complicated.
it appears that in general a smaller pagepool is faster, except that some folk have noticed better results with very large pagepools (e.g. 24 mb) being faster.

I suppose if we could force the elfin to be 4mb it would be beneficial.

[mr_ding]

Have been using Pagepool of 0MB myself and it's running quite fast and stable.

FYI:
Using PDAVietv47 (just upgraded today), was using PDAVietv44 with 0PP before that.

[el_gery]

I think 4MB is the best way to work with Elf. have tried 8mb and got back after 3 weeks.

for me , stability is what counts... :rolleyes:

[dsixda]

I was doing some tests with ayyu3m yesterday and we found out that the Page Pool changes do not seem to take effect when certain ROMs are flashed.

For example, if you dump the contents of the Part00 and Part01 partitions using itsme tools, you might notice the page pool string is there in both (e.g. if you search for 00 10 83 E5 DA C2 FF EB). However, if you flash a different ROM, they might not be there.

It seems like Blue Elves works fine because I can see the page pool settings in the flash. ayyu3m also noticed that they exist when he flashes Blue Elves, but no PP strings are found in his own self-cooked ROM. Could it just be that they are set to default somewhere?

If you actually want to take a look for PP settings in the Part01 partition, you can run my device_info.bat file, as it has been updated for PP.

[!Aman!]

which Base ROM does ayyu3m uses for his ROM?

[dsixda]

which Base ROM does ayyu3m uses for his ROM?

I don't know, you'll have to ask him.

Also when I flash the stock Rogers ROM on my device, it shows the PP info correctly.

[ayyu3m]

I don't know, you'll have to ask him.

Also when I flash the stock Rogers ROM on my device, it shows the PP info correctly.
i m using my good old 1.11.707.1B as a base rom. and after cooking i changed pagepool to 4MB via OS.nb using HexEDIT

my guess is we need to find a way to identify the pp strings when cooked roms are pagepooled in this manner?

i.e. via OS.nb

btw Aman, noonski gave me a good XIP. can you suggest a good SYS?

[!Aman!]

i m using my good old 1.11.707.1B as a base rom. and after cooking i changed pagepool to 4MB via OS.nb using HexEDIT

my guess is we need to find a way to identify the pp strings when cooked roms are pagepooled in this manner?

i.e. via OS.nb

btw Aman, noonski gave me a good XIP. can you suggest a good SYS?
first thing. if u use any ROM version older than 2.20 as the Base ROM, swiftblade's method of pp change by hex editing may not work. 2nd, i found 20273 is quite stable. i suggest u to use that. i've used that build for more than 2 weeks and it behaved nicely.

[dsixda]

first thing. if u use any ROM version older than 2.20 as the Base ROM, swiftblade's method of pp change by hex editing may not work. 2nd, i found 20273 is quite stable. i suggest u to use that. i've used that build for more than 2 weeks and it behaved nicely.

By the way --

If the PP info is visible, you'll find the string at the following locations:

In Part00 DOC partition: 0x432BC
In Part01 DOC partition: 0x4327C
In Part02 DOC partition (operating system): Nowhere

e.g.
- pdocread -w -d TrueFFS -p Part01 0x4327c 16 pp.raw
- dump pp.raw

That means whenever we edit the Page Pool in our ROMs it gets applied to Part00 and Part01. That's probably why we have to edit that string twice in the ROM.


Whenever I couldn't find the PP setting at those locations, it was not found in the rest of the partition either.

[dsixda]

There was a thread (Noonski's Cooking Class) where someone mentioned how to change the Page Pool for the pre-2.20 ROMs; it's at 0x37b55a of the OS.nb file:

http://forum.xda-developers.com/showpost.php?p=1629944&postcount=130

After working with ayyu3m, we found that this value directly affects partition Part01 at offset 0x6b55a.

This single byte contains the following info:

00 = 0 MB page pool
20 = 2 MB
40 = 4 MB
60 = 6 MB
80 = 8 MB

I've verified this on my own, by manipulating Noonski's 1.1x base ROM, and ayyu3m did the same with his own base ROM.

[Noonski]

There was a thread (Noonski's Cooking Class) where someone mentioned how to change the Page Pool for the pre-2.20 ROMs; it's at 0x37b55a of the OS.nb file:

http://forum.xda-developers.com/showpost.php?p=1629944&postcount=130

After working with ayyu3m, we found that this value directly affects partition Part01 at offset 0x6b55a.

This single byte contains the following info:

00 = 0 MB page pool
20 = 2 MB
40 = 4 MB
60 = 6 MB
80 = 8 MB

I've verified this on my own, by manipulating Noonski's 1.1x base ROM, and ayyu3m did the same with his own base ROM.

Dammit it you beat me to quoting myself.
Now how if we can huddle up we can make the SmartPagePool changer for default users.

The last one i found was Elf only and did not have 0 MB PP.
Just a moment BRB.

So here's Tabi's fixed Active Sync PP changer again for the ELF only
http://forum.xda-developers.com/attachment.php?attachmentid=91210&d=1212934964

A version for Elfin Devices shouldn't be that hard to make now.

And then we can put it to the first post as per Swifts Initial intention's.

Am i correct that
The Offset needs to be changed for ELFIN's are

0x35327C
0x436BC

Need to be the addresses in the Bat files.

(At Least I Hope So)

I have attached a modified MULTITESTChangePPviaAS.zip (http://forum.xda-developers.com/attachment.php?attachmentid=109714&d=1220094772) from Tabi's Source with a 0MB ELF NB file, And a few ELFIN nb and Bat files.

If anyone can confirm the correct offset or confirm the workings.
Then this show can start.

Had a little trouble getting the correct offset, as i was looking at the .nbh adress instead of the os.nb adress. (Silly Me)

FOR OTHER USERS THE ATTACHED FILE IS FOR TESTING PORPUSES ONLY AND FOR THOSE THAT KNOW WHAT THEY ARE DOING.

[dsixda]

Noonski, I beat you again ;-) I was actually going to write a universal PP changer last night but realized Pdocread wasn't working the way I wanted it to. But now, looking at this code, it seems a little less complex, as it doesn't require the Part01 argument and such! Hmm maybe I am just a newb.

BTW you are correct about the offsets for Elfin.

I'll get cracking on it..



Dammit it you beat me to quoting myself.
Now how if we can huddle up we can make the SmartPagePool changer for default users.

The last one i found was Elf only and did not have 0 MB PP.
Just a moment BRB.

So here's Tabi's fixed Active Sync PP changer again for the ELF only
http://forum.xda-developers.com/attachment.php?attachmentid=91210&d=1212934964

A version for Elfin Devices shouldn't be that hard to make now.

And then we can put it to the first post as per Swifts Initial intention's.

Am i correct that
The Offset needs to be changed for ELFIN's are

0x35327C
0x436BC

Need to be the addresses in the Bat files.

(At Least I Hope So)

I have attached a modified MULTITESTChangePPviaAS.zip (http://forum.xda-developers.com/attachment.php?attachmentid=109714&d=1220094772) from Tabi's Source with a 0MB ELF NB file, And a few ELFIN nb and Bat files.

If anyone can confirm the correct offset or confirm the workings.
Then this show can start.

Had a little trouble getting the correct offset, as i was looking at the .nbh adress instead of the os.nb adress. (Silly Me)

FOR OTHER USERS THE ATTACHED FILE IS FOR TESTING PORPUSES ONLY AND FOR THOSE THAT KNOW WHAT THEY ARE DOING.

[Noonski]

Noonski, I beat you again ;-) I was actually going to write a universal PP changer last night but realized Pdocread wasn't working the way I wanted it to. But now, looking at this code, it seems a little less complex, as it doesn't require the Part01 argument and such! Hmm maybe I am just a newb.

BTW you are correct about the offsets for Elfin.

I'll get cracking on it..

No you did not beat me to it.

The package should already contain everything then :p

[dsixda]

No you did not beat me to it.

The package should already contain everything then :p

Hehe.. ok ok I'm using ideas from the package LOL

EDIT: Actually working on one that works on devices with 1.1x ROMs as well as 2.2x ROMs.

[blasev]

FOR OTHER USERS THE ATTACHED FILE IS FOR TESTING PORPUSES ONLY AND FOR THOSE THAT KNOW WHAT THEY ARE DOING.

wow, thx :D

[Noonski]

And since we are Sharing


[HKEY_LOCAL_MACHINE\System\GWE\Menu\BarFnt]
"Ht"=dword:000004b0
[HKEY_LOCAL_MACHINE\System\GWE\Menu\PopFnt]
"Ht"=dword:000004b0

To get larger Menu Fonts for Easy Finger control of the tiny menu's
From Shcapps new Advanced Config.
Can confirm this works for qvga.

The above setting is for the 1200 value

<setting key="HKEY_LOCAL_MACHINE\System\GWE\Menu\BarFnt" name="Ht" type="integer">
<title>Menu bar font size</title>
<description>Defines font size of menu bar.</description>
<values default="1000">
<value data="1000">Standard (default)</value>
<value data="1200">Large</value>
</values>
</setting>
<setting key="HKEY_LOCAL_MACHINE\System\GWE\Menu\PopFnt" name="Ht" type="integer">
<title>Popup menu font size</title>
<description>Defines font size of popup menu.</description>
<values default="1000">
<value data="1000">Standard (default)</value>
<value data="1200">Large</value>
</values>
</setting>

[dsixda]

I guess i should ask other people to beta test what I have so far.

So far I've provided support for both Elf/Elfin and 1.1x and 2.2x ROMs, so it is a true universal Page Pool Changer. It will write to the appropriate area in memory, reboot your device and then read back the new value.

This is what needs to be tested:

1) Elf with 2.2x ROM
2) Elfin with 2.2x ROM
3) Elf with 1.1x ROM
4) Elfin with 1.1x ROM (don't flash a 1.1x shipped ROM on your Elfin! Use just the OS ROM)

Cases #1, 2 and 4 have already been tested but I'd like more feedback on your devices.


The tool and screenshots are found here:
http://forum.xda-developers.com/showpost.php?p=2274573&postcount=2

[Noonski]

Re arranged the thread a bit.

Making it Temp Sticky to grab some Attention for Testing Purposes.

[dsixda]

Just found out that 24MB dynamic page pool on 2.2x Elfins will brick the OS. I will update the tool to exclude it.

[!Aman!]

Just found out that 24MB dynamic page pool on 2.2x Elfins will brick the OS. I will update the tool to exclude it.
what do u mean by dynamic PP :)?

[dsixda]

what do u mean by dynamic PP :)?

Hey man, I was hoping you'd help ;)

I meant the string "18 15".
The second byte is either 15 or 16, I called it either "dynamic" or "static". But I'm probably wrong here. What is the difference between "xx 15" and "xx 16"?

[!Aman!]

Hey man, I was hoping you'd help ;)

I meant the string "18 15".
The second byte is either 15 or 16, I called it either "dynamic" or "static". But I'm probably wrong here. What is the difference between "xx 15" and "xx 16"?
i told u in my PM last night that there is nothing like dynamic PP. the only "dynamic" characteristic of the 2.20+ version ROM is the kernel's ability to chose between 8/12 MB PP depending upon the device.
15 or 16 doesn't mean static/dynamic PP. XX 15 and XX 16 is just the Operand value in assembly language. when u say 10 16 means 16 MB PP, u can also use 01 14 to make 16 MB PP. you need to know the MOV table values of assembly for hex encoding to understand the meaning of XX 15 and XX 16.

[dsixda]

haha. i've told u in my PM last night that there is nothing like dynamic PP. the only "dynamic" characteristic of the 2.20+ version ROM is the kernel's ability to chose between 8/12 MB PP depending upon the device.
15 or 16 doesn't mean static/dynamic PP. XX 15 and XX 16 is just the Operand value in assembly language. when u say 10 16 means 16 MB PP, u can also use 01 14 to make 16 MB PP. you need to know the MOV table values of assembly for hex encoding to understand the meaning of XX 15 and XX 16.

Oh, so it's an assembly instruction. :)

I'm going to be out for a few hours so when I get back I'll update the tool so that it uses just the values in Swiftblade's post.

[!Aman!]

"18 15" doesnt mean 24 MB 'dynamic' PP. "18 15" means 96 MB static PP

[kokotas]

..the only "dynamic" characteristic of the 2.20+ version ROM is the kernel's ability to chose between 8/12 MB PP depending upon the device..
+1
That's the only "dynamic" characteristic!

But for a dynamic pp in a sense that it "resizes" itself to whatever size seems necessary
someone could only use the 0 MB pp size TRICK!
Please correct me, if I'm wrong:)
So dsixda could name as "dynamic pp" the "0 MB pp"!
Just an idea...

[!Aman!]

---del----

[kokotas]

lol, no. he meant 24 MB dynamic PP, which most of us (including myself, but a couple of months ago :p) think is equal to "18 15" :D
but as i said in my last post, thats not 24 MB, but 96 MB.
lol:D
Well, you misunderstood what I posted but nevermind..
PS: 0 MB PP means no PP at all.
I spoke about a "trick", not an actual dynamic behavior.
pp is a locked space of the whole ram,right?
so it's not a seperate faster memory!It's as fast as the normal ram.
If the paging pool is not enabled, the entire RAM on the device is available for paging
(which however can drastically increase RAM usage and I guess decrease battery lifetime&boottime)
I don't know if now you get what I meant by
calling 0 MB PP -> dynamic PP:)
Anyway,I think I'm getting off topic!
dsixda is making a great tool for all of us and that's important!
Regards!

[!Aman!]

Well, you misunderstood what I posted but nevermind..

I spoke about a "trick", not an actual dynamic behavior.
pp is a locked space of the whole ram,right?
so it's not a seperate faster memory!It's as fast as the normal ram.
If the paging pool is not enabled, the entire RAM on the device is available for paging
(which however can drastically increase RAM usage and I guess decrease battery lifetime&boottime)
I don't know if now you get what I meant by
calling 0 MB PP -> dynamic PP:)
Anyway,I think I'm getting off topic!
dsixda is making a great tool for all of us and that's important!

ok, i'll just keep quiet on this issue now.

[kokotas]

ok, i'll better keep quiet then :)
On the contrary bro!
You should better be (evenmore) loud!
The knowledge that you have&share here with all of us is just pure gold!
Regards!

[Satyan]

Hi,
I have tried to change the 12mb pagepool with the ppchanger to 18mb dynamic, now the phone just crashes on smart mobility screen....
Plsss help ...

Thanks ...

[blasev]

Hi,
I have tried to change the 12mb pagepool with the ppchanger to 18mb dynamic, now the phone just crashes on smart mobility screen....
Plsss help ...

Thanks ...

u can try to upgrade using sd card. and use original rom ;)

[Satyan]

blasev thanks for your quick reply...

if i understand, i need to get to the RUU boot-loader and apply the Original ROM ?

my SPL/IPL version is 2.20

Thanks again ....

[Satyan]

Thanks Bro, was finally able to fix it by applying the original ROM from the RUU bootloader..

Thanks again :) !!!

This forum Rocks !

[Noonski]

Just came back frm some good old Bar Hopping and Girl Gazing.

I have to repeat. This is still in PROJECT mode. needing some good input from at least users that have Hex edited anything ever.

To keep people from getting Heart attacks and spontaneously Grey hairs.

It will be Unstickied again as it now has the attention of at least a few Good cooks and users.

With the heads showing up in the last posts this tool is bound to be a success.


This is BETA and in development.

[dsixda]

Ok guys, I've made the adjustments and removed all that static/dynamic crap.

Let me know if it looks good to you now, Aman ;) :D


Please go back to Post #2 for the screenshots/file (or click on the link in my sig)

[dsixda]

Thanks Bro, was finally able to fix it by applying the original ROM from the RUU bootloader..

Thanks again :) !!!

This forum Rocks !

Guys, as mentioned in the PP Changer post --- install the USPL before you change the page pools. If you didn't have the shipped ROM you woulda been outta luck ;)

[!Aman!]

Let me know if it looks good to you now, Aman ;) :D

as u are directly asking me, so i'd just say the nb's are fine. but i didnt check the batch file.

[dsixda]

as u are directly asking me, so i'd just say the nb's are fine. but i didnt check the batch file.

Well, I mean everyone else too ;) But you are one of the resident experts in page pool info ;)

PS. Thanks for checking

[!Aman!]

Well, I mean everyone else too ;) But you are one of the resident experts in page pool info ;)

PS. Thanks for checking
welcome
i'm not an expert here like some of the other guys here though.

[dsixda]

welcome
i'm not an expert here like some of the other guys here though.

You may not know the inner technicalities but you know what you are doing... It's good to have you on this board.

[!Aman!]

just in case someone is interested to understand "03 15", "18 15" or "18 16" etc:

1. 03 15 <> 0x03 * 0x400000=0xC00000= decimal 12582912 bytes= 12 MB
2. 02 15 <> 0x02 * 0x400000=0x800000= decimal 8388608 bytes = 8 MB
3. 18 15 <> 0x18 * 0x400000=0x6000000= decimal 100663296 bytes= 96 MB
4. 18 16 <> 0x18 * 0x100000=0x1800000= decimal 25165824 bytes = 24 MB
5. 10 16 <> 0x10 * 0x100000=0x1000000= decimal 16777216 bytes = 16 MB

and so on...

[dsixda]

Haha.. 96 MB.. that cracks me up.. and I thought it was 24MB dynamic.
Thanks for the lesson.

BTW, for all of the following options, which are valid for Elf and Elfin, or can all of them be used on each device?

0 MB
4
6
8
12
16
18
24


just in case someone is interested to understand "03 15", "18 15" or "18 16" etc:

1. 03 15 <> 0x03 * 0x400000=0xC00000= decimal 12582912 bytes= 12 MB
2. 02 15 <> 0x02 * 0x400000=0x800000= decimal 8388608 bytes = 8 MB
3. 18 15 <> 0x18 * 0x400000=0x6000000= decimal 100663296 bytes= 96 MB
4. 18 16 <> 0x18 * 0x100000=0x1800000= decimal 25165824 bytes = 24 MB
5. 10 16 <> 0x10 * 0x100000=0x1000000= decimal 16777216 bytes = 16 MB

and so on...

[!Aman!]

Haha.. 96 MB.. that cracks me up.. and I thought it was 24MB dynamic.
Thanks for the lesson.

BTW, for all of the following options, which are valid for Elf and Elfin, or can all of them be used on each device?

0 MB
4
6
8
12
16
18
24
it is possible for both of the devices, but allocating too much of memory to PP may render the device unbootable, as was the case with 96 MB PP. all these PP values surely applie to ROM versions 2.20+. but i have not checked the kernel for pre-2.20 ROMs, so i can't confirm that.

[dsixda]

it is possible for both of the devices, but allocating too much of memory to PP may render the device unbootable, as was the case with 96 MB PP. all these PP values surely applie to ROM versions 2.20+. but i have not checked the kernel for pre-2.20 ROMs, so i can't confirm that.

Ok, I guess I'll just go with the popular values that have been mentioned in the posts.

[!Aman!]

Ok, I guess I'll just go with the popular values that have been mentioned in the posts.
yeah, the current values in the nb's of the tool are just fine. if u want u can experiment though. now the concept must be clear like how different values are being calculated.

[Noonski]

just in case someone is interested to understand "03 15", "18 15" or "18 16" etc:

1. 03 15 <> 0x03 * 0x400000=0xC00000= decimal 12582912 bytes= 12 MB
2. 02 15 <> 0x02 * 0x400000=0x800000= decimal 8388608 bytes = 8 MB
3. 18 15 <> 0x18 * 0x400000=0x6000000= decimal 100663296 bytes= 96 MB
4. 18 16 <> 0x18 * 0x100000=0x1800000= decimal 25165824 bytes = 24 MB
5. 10 16 <> 0x10 * 0x100000=0x1000000= decimal 16777216 bytes = 16 MB

and so on...

Well this Hex explanation makes more sense to you then me;)

I got my Phone reserved for some other flashes but will test all PagePool settings for ELF 2.2x tomorrow.

[!Aman!]

Well this Hex explanation makes more sense to you then me;)
i know this is not useful to most of the people (99%) here, thats why i never thought to post it in public.

[dsixda]

i know this is not useful to most of the people (99%) here, thats why i never thought to post it in public.

Where did you get these calculations from?

[!Aman!]

Where did you get these calculations from?
read the assembly language related to ARM.

[dsixda]

Well this Hex explanation makes more sense to you then me;)

I got my Phone reserved for some other flashes but will test all PagePool settings for ELF 2.2x tomorrow.

If possible, can you try on your Elf with 1.1x ROM?

[blasev]

read the assembly language related to ARM.

yes I'm that 1% guys, who doesn't even know what is assembly language
and only have below 1% interest for it LOL :D

[dsixda]

A UK T-Mobile Elfin user is reporting an Unknown page pool value after using my device_info.bat - http://forum.xda-developers.com/showpost.php?p=2588703&postcount=5

My tool is looking for the following "popular" values for 2.2x ROMs:
0016 (0 MB)
0416 (4 MB)
0616 (6MB)
0215 (8 MB)
0315 (12 MB)
1016 (16 MB)
1216 (18 MB)
1816 (24 MB)

If it's not equal to any of these for a 2.2x Elfin ROM, then it returns Unknown. What else could it be?? 12MB should be the default.

I'm waiting for his reply to see what 2-byte value his device is actually returning.

P.S. In his original post he said his IPL was 2.81..... ??

[!Aman!]

i guess 2.81 ROM is older than 2.20 :rolleyes:

[dsixda]

i guess 2.81 ROM is older than 2.20 :rolleyes:

Do we have any dumped ROMs from 2.81 IPL devices? I'd like to take a look at the OS.nb there.


EDIT: Saw your post here - http://forum.xda-developers.com/showpost.php?p=2497528&postcount=125

I guess this has a different OS structure than a 1.1x or even 2.2x ROM!

EDIT 2: Ok, I have a copy of the 2.81 ROM, but it looks the same as 2.2x. I think the problem is that it doesn't write to the same area of the Part01 partition for the old 2.81 devices, so my program couldn't read it (on my own Elfin it's the same area in Part01 however). The OS.nb however has the same PP offset as in 2.2x ROMs. So I'll just read from the OS instead of Part01 then. The tool has now been updated.

EDIT 3: The person who has this particular device with the 2.81 ROM cannot extract the proper PP values. So it looks like it's the device itself, not the ROM that is the problem (because PP can be changed on my device if I flash 2.81). Looks like a different address mapping on this device.

[Noonski]

So what would the value be to get a 2MB Pagepool on a 2.2 ELF?

(hate the 0MB version and want to test something beyond 4)

What the heck i'll just try 02 16
Yay 28.02 Free

[dsixda]

Is this the correct value, and shall I add 2MB to the tool?

[dsixda]

Here are some numbers I got from the PP tool, with my Rogers Elfin ROM... I changed the PP, did a reboot and then checked the Memory usage (before running any programs or ActiveSync connection):

Page Pool Size, Total Program Memory Free:
0MB, 75.58MB
12, 74.66 (default size)
16, 70.65
18, 68.61
24, 62.64

With 0MB Page Pool you get the most program memory available (since it uses none up for PP), followed by the default 12MB.

However, this does not truly indicate which one is best, since more memory allocated for PP (and less Program Memory free) could mean snappier performance for starting up programs.

Comments?

[benjih]

Is this the correct value, and shall I add 2MB to the tool?
yes noonski´s numbers fit i have tried them.. runs great

[dsixda]

Ok thanks, I've updated the tool to support 2MB PP for Elfs.

[Noonski]

Ok thanks, I've updated the tool to support 2MB PP for Elfs.

Same goes for 1MB PagePool.

01 016

(Massive free memory, better then 0MB, but it does have a slow start, really needs to warm up)

But your latest incarnation misread my Default Elf value as a 12MB version.

[dsixda]

Same goes for 1MB PagePool.

01 016

(Massive free memory, better then 0MB, but it does have a slow start, really needs to warm up)

But your latest incarnation misread my Default Elf value as a 12MB version.

You have a 2.2x Elf, no? The tool is looking for 0216 for 2MB PP.

EDIT: Ouch, nevermind.. bad GOTO statement. It should be working now. Sorry.

[dsixda]

Holy crap.. is 1 MB PP ever slow!

[dsixda]

I've added a little benchmark number in this script to see how fast each page pool size is.

So... the tool can now display the time it takes after the start of reboot (after changing PP) until the time it establishes ActiveSync again. It's not entirely accurate sometimes, as it can be affected by various factors, such as your PC being busy with other tasks.

I've uploaded the new version with this 'benchmark'.

I got the following values with the new code:

0 MB PP = 59 seconds to boot till ActiveSync established (71 seconds next time)
1 MB = 98 seconds!! (got 96 seconds next time)
2 MB = 88 seconds (got 93 seconds next time)
4 MB = 70 seconds (got 61 seconds next time; 58 afterwards)
8 MB = 58 seconds (got 60 seconds next time)
12 MB = 56 seconds (got 56 seconds again next time; 55 afterwards; 56 again)
16 MB = 55 seconds (got 57 seconds next time; 58 afterwards)
18 MB = 58 seconds (got 62 seconds next time)
24 MB = 65 seconds (got 59 seconds next time)

The best seems to be the default 12MB for my Elfin

[iii_see_tagpi_run_iii]

successfully edited my rom and flashed with a 0 mb pp.. just wanted to know if this types of pagepool have a negative effect on the device's hardware after sometime? pls advice,

thank you

[dsixda]

successfully edited my rom and flashed with a 0 mb pp.. just wanted to know if this types of pagepool have a negative effect on the device's hardware after sometime? pls advice,

thank you

Hi, did you use the tool in the 2nd post or did you do edit it manually?
I've been using 0 MB PP for a while now, no harm done.

[Swiftblade]

I must confessed that I have been neglecting my threads in the Elf forum for quite a while till Noonski "knocked" on my head with his promptings... :)

Just wanted to express my heartfelt thanks to dsixda and Noonski for realising my dream of having a Universal Pagepool Changer for the Elf/Elfin community as I had expressed in my main post. Not forgetting the enormous contributions from our Dynamic Duo htctouchp and ababrekar, and eager-breavers like kokotas and blasev too for beta testings the tool. Great jobs bros and keep it going manz...!

This community is the best there is and I really feel like owning a HTC Touch all over again...:D

[Ameet]

This community is the best there is and I really feel like owning a HTC Touch all over again...:D
And believe me brother, this community would love to see you back around in here :D

[dsixda]

I must confessed that I have been neglecting my threads in the Elf forum for quite a while till Noonski "knocked" on my head with his promptings... :)

Just wanted to express my heartfelt thanks to dsixda and Noonski for realising my dream of having a Universal Pagepool Changer for the Elf/Elfin community as I had expressed in my main post. Not forgetting the enormous contributions from our Dynamic Duo htctouchp and ababrekar, and eager-breavers like kokotas and blasev too for beta testings the tool. Great jobs bros and keep it going manz...!

This community is the best there is and I really feel like owning a HTC Touch all over again...:D

Thanks SB, but it wouldn't have been possible without your research :D Yes this forum is a pretty tight-knit community, we all work together and help each other to achieve our goals :)

[iii_see_tagpi_run_iii]

Hi, did you use the tool in the 2nd post or did you do edit it manually?
I've been using 0 MB PP for a while now, no harm done.

i edited it manually via hex on the os.nb then flashed it. so far its good but im a bit worried on "the wear and tear within the hardware aspect"

[dsixda]

i edited it manually via hex on the os.nb then flashed it. so far its good but im a bit worried on "the wear and tear within the hardware aspect"

I wouldn't worry about it, it shouldn't affect anything in your hardware.

If you really want to be safe, just use the Universal PP Changer in post #2 instead of flashing a new ROM every time you change the PP.

[iii_see_tagpi_run_iii]

I wouldn't worry about it, it shouldn't affect anything in your hardware.

If you really want to be safe, just use the Universal PP Changer in post #2 instead of flashing a new ROM every time you change the PP.

oh i see. thanks for the reply.. just wnt to clear my head:)

[insaned]

I've managed to cook all my stock elfin thanks to all you guys.

However, since I DON'T have a shipped ROM backed up, and I'm ot very confortable making this step.. but would like to try the PP in my phone...

also, I didn't understood quite well, with my ROM version, can or cannot use the PP changer? (yes, I'm goona using the dsixda program ;) )

http://img175.imageshack.us/img175/9532/allcookedrm4.th.jpg (http://img175.imageshack.us/my.php?image=allcookedrm4.jpg)

[dsixda]

I've managed to cook all my stock elfin thanks to all you guys.

However, since I DON'T have a shipped ROM backed up, and I'm ot very confortable making this step.. but would like to try the PP in my phone...

also, I didn't understood quite well, with my ROM version, can or cannot use the PP changer? (yes, I'm goona using the dsixda program ;) )

http://img175.imageshack.us/img175/9532/allcookedrm4.th.jpg (http://img175.imageshack.us/my.php?image=allcookedrm4.jpg)


You should be able to use it.
If you want to be safe, just do the following before you do anything to your Page Pool:

1) Make a backup of your device (use the link in my sig to use the script. it's easy)
2) Install the latest USPL by htctouchp (again, in my sig)
3) Make a backup of all your PIMs and SMSes (use PPCPimBackup.exe) and also your Documents (ActiveSynced to your PC)...
4) Then finally, you can change your PP. :D
5) If your device freezes, you can go to the bootloader and restore your backup :-)

It's not very dangerous, plus I have checks to make sure you have the correct device before it writes anything.

[insaned]

You should be able to use it.
If you want to be safe, just do the following before you do anything to your Page Pool:

1) Make a backup of your device (use the link in my sig to use the script. it's easy)
2) Install the latest USPL by htctouchp (again, in my sig)
3) Make a backup of all your PIMs and SMSes (use PPCPimBackup.exe) and also your Documents (ActiveSynced to your PC)...
4) Then finally, you can change your PP. :D
5) If your device freezes, you can go to the bootloader and restore your backup :-)

It's not very dangerous, plus I have checks to make sure you have the correct device before it writes anything.

Thanks man,

I've done a SO dump before the new shadow ROM (installed few hours before posting this), but I'll run it again just in case.

Any recommended PP size for single tasks only?

[dsixda]

Thanks man,

I've done a SO dump before the new shadow ROM (installed few hours before posting this), but I'll run it again just in case.

Any recommended PP size for single tasks only?

0, 12 and 16 are the best for Elfins, if you're talking about time it takes to start up a program (and not necessarily the available RAM). I set my Task Manager to terminate the process upon closing, so I don't care about available RAM.

I'm not sure about the optimal value for Elfs though. Just experiment with the values.. the "Reboot Time" benchmark should give you an estimate.

I get good times at 12MB for Blue Elves, but then 0MB is best for my Rogers stock ROM.

[insaned]

0, 12 and 16 are the best for Elfins, if you're talking about time it takes to start up a program (and not necessarily the available RAM). I set my Task Manager to terminate the process upon closing, so I don't care about available RAM.

I'm not sure about the optimal value for Elfs though. Just experiment with the values.. the "Reboot Time" benchmark should give you an estimate.

I get good times at 12MB for Blue Elves, but then 0MB is best for my Rogers stock ROM.

I'm right now updating the rom to the blue elves 5 veersion, to try it out, I'll see how it goes...
So you liked the default PP with blue elves then?

thks, for the help and for all the other usefull programs you provided! ;)

[andrei.nica]

while running the program from xp on my elf I receive a message that "msvcr71.dll" cannot be found. googled it, downloaded - all ok, except for when setting 16 MB PP on my Elf, Pdaviet ROM - after a lot of device rebooting occurs. so I change back to 12 MB - all ok till now - great tool, guys!

[dsixda]

I'm right now updating the rom to the blue elves 5 veersion, to try it out, I'll see how it goes...
So you liked the default PP with blue elves then?

thks, for the help and for all the other usefull programs you provided! ;)

You're welcome!
Yeah I liked the default 12MB on Blue Elves best :)

[dsixda]

while running the program from xp on my elf I receive a message that "msvcr71.dll" cannot be found. googled it, downloaded - all ok, except for when setting 16 MB PP on my Elf, Pdaviet ROM - after a lot of device rebooting occurs. so I change back to 12 MB - all ok till now - great tool, guys!

Not sure about the error you got, but for Elfs, try not to go higher than 12MB.. I'm not sure if it will work properly since they don't have a lot of memory compared to Elfins. For Elfins however it is ok.

[hehehi]

hi snior,, how to check our pp value on elf?

thx

[dsixda]

hi snior,, how to check our pp value on elf?

thx

Just run the program and it will tell you the current PP value.

[grox]

What is the best PP for the UCE ROM version 14.01?

[dsixda]

What is the best PP for the UCE ROM version 14.01?

UCE is fast enough, isn't it :D

You should try to experiment and compare the boot times.

For Elfin, I prefer the default 12MB most of the time. Depends on the ROM.. if it is a quick ROM already then try 0MB. If it is a slow ROM with a lot of memory usage requirements, then go for 12MB or even 8MB.

[kokotas]

NOTE: I have intentionally described the steps in details in the hope that someone who is good in programming will develop a simple "Change Pagepool" program that can do all these with the simple click of a few buttons.
I'm not good in programming but here is a simple pp patcher!And when I say simple, I mean REAL simple!
All it does is hexediting certain bytes!
Not able to search for hex string pattern, but able to edit it if the address is known!
For example for the 2.2x Roms the pattern's (03 15 A0 03 02 15 A0 13...) address is known:
For the OS.nb
1st address:
first byte 03 @ 0x0436BC
2nd address:
first byte 03 @ 0x035327C

For the RUU_Signed.nbh(ONLY OS! NOT WITH ANYTHING ELSE LIKE IPL,SPL,SPLASHSCREEN,etc!)
1st address:
first byte 03 @ 0x0438DC
2nd address:
first byte 03 @ 0x0353637

So I hope you get the way it works.

I have included it in the Hybrid kitchen, but better have it as a standalone tool too!
Any feedbacks are most welcome!

It could be implemented into the final step of any kitchen if you have a favorite pp size that you always use
and you know the correct offsets to edit.
eg:Speaking for a Kitchen based on bepe's Extended kitchen, having OEMXIPKERNEL from 2.2x ROM and choosing 8MB for ELFIN & 4MB for ELF
Having the hexalter.exe in your tools dir
add in your script after the creation of the OS.nb :
..
..\TOOLS\ImgfsToNb imgfs-new.bin OS.nb.payload OS-new.nb -bigstoragemove
..\TOOLS\hexalter OS-new.nb 0x0436BC=2,21 0x0436C0=4,22 0x035327C=2,21 0x0353280=4,22
..
and your final OS.nb is already patched with the PP_size you prefer!
Regards!

[ayyu3m]

nice. no more need to go into hex editor

:D thankx a lot man. this will come in handy very much

[dsixda]

Awesome work. This is a very good tool and will prevent mistakes...



Here is a simple pp patcher!And when I say simple, I mean REAL simple!
All it does is hexediting certain bytes!
Not able to search for hex string pattern, but able to edit it if the address is known!
For example about the 2.2x Roms the pattern's (03 15 A0 03 02 15 A0 13...) address is known:
For the OS.nb
1st address:
first byte 03 @ 0x0436BC
2nd address:
first byte 03 @ 0x035327C

For the RUU_Signed.nbh(ONLY OS! NOT WITH ANYTHING ELSE LIKE IPL,SPL,SPLASHSCREEN,etc!)
1st address:
first byte 03 @ 0x0438DC
2nd address:
first byte 03 @ 0x0353637

I was going to include it in the Hybrid kitchen, but better have it as a standalone tool first!
Any feedbacks are most welcome!

It could be implemented into the final step of any kitchen if you have a favorite pp size that you always use.
eg: 8MB for ELFIN & 4MB for ELF
You could add the hexalter.exe in your tools dir
and add in your script after the creation of the OS.nb :
..
..\TOOLS\ImgfsToNb imgfs-new.bin OS.nb.payload OS-new.nb -bigstoragemove
..\TOOLS\hexalter OS-new.nb 0x0436BC=2,21 0x0436C0=4,22 0x035327C=2,21 0x0353280=4,22
..

Regards!

[ayyu3m]

Here is a simple pp patcher!And when I say simple, I mean REAL simple!
All it does is hexediting certain bytes!
Not able to search for hex string pattern, but able to edit it if the address is known!
For example about the 2.2x Roms the pattern's (03 15 A0 03 02 15 A0 13...) address is known:
For the OS.nb
1st address:
first byte 03 @ 0x0436BC
2nd address:
first byte 03 @ 0x035327C

For the RUU_Signed.nbh(ONLY OS! NOT WITH ANYTHING ELSE LIKE IPL,SPL,SPLASHSCREEN,etc!)
1st address:
first byte 03 @ 0x0438DC
2nd address:
first byte 03 @ 0x0353637

I was going to include it in the Hybrid kitchen, but better have it as a standalone tool first!
Any feedbacks are most welcome!

It could be implemented into the final step of any kitchen if you have a favorite pp size that you always use.
eg: 8MB for ELFIN & 4MB for ELF
You could add the hexalter.exe in your tools dir
and add in your script after the creation of the OS.nb :
..
..\TOOLS\ImgfsToNb imgfs-new.bin OS.nb.payload OS-new.nb -bigstoragemove
..\TOOLS\hexalter OS-new.nb 0x0436BC=2,21 0x0436C0=4,22 0x035327C=2,21 0x0353280=4,22
..

Regards!
WORKINGS LIKE A CHARM!! JUS TESTED :D

Thankx Man!

[vaxoie]

When I'm change PP on my Elf to 4mb (old 2mb) I'm lost contacts on my People page in manila TF2D. Only for statistic , no problem ;)
Very nice program, thanks.

[flaviocc]

Hi,

The application can not see my PP, the error of missing dll.

And asked to reinstall the app. It happened with rom 3.1 and 3.1.1 Onyx.

Tks,

[!Aman!]

The PP HEX string is changed now if someone is working with the latest 3.07 ROM as his Base ROM for OEMXipkernel. the new Hex string is as follows:
03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB
The offsets have changed in new the kernel, so the current PP changer needs to be modified for 3.07.XX ROMs with new offsets.

Also, if the cooks are using old (2.2X) os.nb.payload for cooking the new OEMXipkernel, then the first HEX string would be same as the previous 2.2X. And if version 3.07 os.nb.payload is used for cooking then the PP depends upon the new HEX string and new offsets.

[dsixda]

The PP HEX string is changed now if someone is working with the latest 3.07 ROM as his Base ROM for OEMXipkernel. the new Hex string is as follows:
03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB
The offsets have changed in new the kernel, so the current PP changer needs to be modified for 3.07.XX ROMs with new offsets.

Also, if the cooks are using old (2.2X) os.nb.payload for cooking the new OEMXipkernel, then the first HEX string would be same as the previous 2.2X. And if version 3.07 os.nb.payload is used for cooking then the PP depends upon the new HEX string and new offsets.

Thanks a lot Aman, I will try to fix the PP changer later.

[dsixda]

Universal Page Pool Changer now updated for 3.xx ROMs!!!

http://forum.xda-developers.com/showpost.php?p=2274573&postcount=2


Please note, however, it will only work with 3.xx cooked ROMs that were built with a 3.xx ROM's OS.nb.payload. (e.g. My Onyx 4.0 Beta 1 most likely will NOT work, but future ones will, because I will build them properly next time ;) )

[!Aman!]

Universal Page Pool Changer now updated for 3.xx ROMs!!!

http://forum.xda-developers.com/showpost.php?p=2274573&postcount=2


Please note, however, it will only work with 3.xx cooked ROMs that were built with a 3.xx ROM's OS.nb.payload. (e.g. My Onyx 4.0 Beta 1 most likely will NOT work, but future ones will, because I will build them properly next time ;) )
what if we only change the 2nd Hex string and leave the 1st one as such? doesn't it change the PP?

[dsixda]

what if we only change the 2nd Hex string and leave the 1st one as such? doesn't it change the PP?

The program will give an error if the 3.xx is built with the 2.xx payload. I don't know how it would affect it (or if it would work as expected) with that combination.

[ayyu3m]

what if we only change the 2nd Hex string and leave the 1st one as such? doesn't it change the PP?
i tried changing one set as u suggested bro

but it doesnt work..and pagepool remains the same

[dsixda]

i tried changing one set as u suggested bro

but it doesnt work..and pagepool remains the same

How do you know it remains the same?

[!Aman!]

i tried changing one set as u suggested bro

but it doesnt work..and pagepool remains the same
oh..i was thinking that only 2nd HEX string should control the PP coz thats where the XIP (hence the kernel nk.exe) is.

[dsixda]

oh..i was thinking that only 2nd HEX string should control the PP coz thats where the XIP (hence the kernel nk.exe) is.

I think we should just give an error if the 2.xx payload is used in a 3.xx ROM. It's bad cooking practise anyway ;-)

[!Aman!]

I think we should just give an error if the 2.xx payload is used in a 3.xx ROM. It's bad cooking practise anyway ;-)
yeah, but it would have been a lot better if changing the 2nd Hex string only did the job.

[dsixda]

yeah, but it would have been a lot better if changing the 2nd Hex string only did the job.

We'll need to confirm if that really works... best way to tell is to change PP to 1MB and see if it slows down really bad ;-)

[!Aman!]

We'll need to confirm if that really works... best way to tell is to change PP to 1MB and see if it slows down really bad ;-)
why not just observe the program memory?

[dsixda]

why not just observe the program memory?

Oh yeah.. nevermind. Pardon the brain cramp, I should go to bed now.

[alx75]

Universal Page Pool Changer now updated for 3.xx ROMs!!!

http://forum.xda-developers.com/showpost.php?p=2274573&postcount=2


Please note, however, it will only work with 3.xx cooked ROMs that were built with a 3.xx ROM's OS.nb.payload. (e.g. My Onyx 4.0 Beta 1 most likely will NOT work, but future ones will, because I will build them properly next time ;) )

Yup Very Correct:p Cos Just Use Your New PPC IT WORKS

[!Aman!]

i tried changing one set as u suggested bro

but it doesnt work..and pagepool remains the same
are u sure u did it properly? i just tested it by changing only the 2nd offset PP value in my ROM which i've cooked using payload 2.2x and new OEMxipkernel, and i can see that the PP changed successfully :D

PS: i confirm changing the 2nd HEX string should be enough. Pls test it out guys.

[!Aman!]

are u sure u did it properly? i just tested it by changing only the 2nd offset PP value in my ROM which i've cooked using payload 2.2x and new OEMxipkernel, and i can see that the PP changed successfully :D

PS: i confirm changing the 2nd HEX string should be enough. Pls test it out guys.
nobody interested??? amazing :D!!

[dsixda]

nobody interested??? amazing :D!!

HAha.. I could try but too lazy to go back to 2.2x cooking ;)

Ok how about this.. what if we use a 3.3x payload.. Do we only have to change the 2nd set of strings in order to really change the PP???

I mean maybe it is visibly noticeable that the memory has been adjusted for the new PP, but perhaps there are other things that weren't changed.. which may affect stability.

[!Aman!]

HAha.. I could try but too lazy to go back to 2.2x cooking ;)

Ok how about this.. what if we use a 3.3x payload.. Do we only have to change the 2nd set of strings in order to really change the PP???
yeah only the 2nd HEX string needs to be changed, whatever the base ROM may be.

[dsixda]

yeah only the 2nd HEX string needs to be changed, whatever the base ROM may be.

Are you 100% sure? If your life depended on it? (I will buy a gun)

[dsixda]

Ok, the PP Changer has now been updated for ALL 3.xx ROMs.. thanks to htctouchp's findings.. as usual.

[Berfurd]

Ok, the PP Changer has now been updated for ALL 3.xx ROMs.. thanks to htctouchp's findings.. as usual.

I just tried it on 4 Beta and I have IPL/SPL 3.07 on my Elfin. Works fine.

[dsixda]

I just tried it on 4 Beta and I have IPL/SPL 3.07 on my Elfin. Works fine.

Thanks for testing!

[Berfurd]

Thanks for testing!

No problem!! :D

[!Aman!]

Are you 100% sure? If your life depended on it? (I will buy a gun)
yeah i'm 100% sure, only the 2nd Hex string is responsible for PP. did u test it?

[dsixda]

yeah i'm 100% sure, only the 2nd Hex string is responsible for PP. did u test it?

I noticed a change in memory.. so it looked like it worked :)

[!Aman!]

I noticed a change in memory.. so it looked like it worked :)
good :). the PP changer can be simplified now, but i suggest u don't modify it as yet coz once we remove the ULDR partition from our ROMs the offsets will change again ;)

[dsixda]

It's already changed ;-)

Another thing I noticed ----
If you change the XIP from 19972 (the Elfin's XIP) to 19971 (the Opal one), and then build the ROM again, then one of the two 3.xx PP strings is missing.


EDIT: IF the ULDR causes the offsets to change again, it's not a big deal.. the script can check for that when I fix it later.

[!Aman!]

It's already changed ;-)
will have to change again, coz the 1st HEX string is going to disappear forever ;)

Another thing I noticed ----
If you change the XIP from 19972 (the Elfin's XIP) to 19971 (the Opal one), and then build the ROM again, then one of the two 3.xx PP strings is missing.


EDIT: IF the offsets change again, it's not a big deal.. the script can check for that.
do u mean u used OEMXIPKernel form Opal?

[dsixda]

will have to change again, coz the 1st HEX string is going to disappear forever ;)

do u mean u used OEMXIPKernel form Opal?

Yes I did.
I also noticed that changing the PP for XIP 19971 causes Manila 2D to not start up.
I think I'll go back to Elfin XIP 19972.

[dsixda]

will have to change again, coz the 1st HEX string is going to disappear forever ;)


PP Changer only looks at the 2nd hex string for 3.xx ROMs now.

[!Aman!]

Yes I did.
I also noticed that changing the PP for XIP 19971 causes Manila 2D to not start up.
I think I'll go back to Elfin XIP 19972.
using OEMXIPKernel from another device is never a good idea :). it has information specific to the phone.

[dsixda]

using OEMXIPKernel from another device is never a good idea :)

Not really, I used 19971/19971 SYS/XIP (Opal) for about a month without any stability problems. I ported the SYS though, so that it worked, but XIP was straight copy.

BTW (off-topic) do you know how to change the byte on 19972 so that it retains the real-time clock value? It looks like the address changed in the S000 file of the kernel.

[!Aman!]

PP Changer only looks at the 2nd hex string for 3.xx ROMs now.
2nd HEX string works for 2.2X based ROMs also. i have not checked the older ROMs though, but i'm sure it is same for them.

[!Aman!]

Not really, I used 19971/19971 SYS/XIP (Opal) for about a month without any stability problems. I ported the SYS though, so that it worked, but XIP was straight copy.
i know opal and elfin are almost same, but this part of the XIP is specific to the device hardware.
BTW (off-topic) do you know how to change the byte on 19972 so that it retains the real-time clock value? It looks like the address changed in the S000 file of the kernel.
yeah i know, the kernel is changed now as per WM 6.1. u need to edit the hex byte at 0x45BDF now.

[dsixda]

i know opal and elfin are almost same, but this part of the XIP is specific to the device hardware.

yeah i know, the kernel is changed now as per WM 6.1. u need to edit the hex byte at 0x45BDF now.

Excellent, thanks.. I see 0A there. Did you decompile it?

I used XIP (straight copy) from other devices in previous ROMs, and it worked fine for me.

[!Aman!]

Excellent, thanks.. I see 0A there. Did you decompile it?

yeah, u have to disassemble to find out the correct code. there is no method otherwise to find out which is the correct offset. so change 0A to EA.

[!Aman!]

I used XIP (straight copy) from other devices in previous ROMs, and it worked fine for me.
which other devices? kaiser, diamond etc? or just another Elfin's ROM?

[dsixda]

yeah, u have to disassemble to find out the correct code. there is no method otherwise to find out which is the correct offset. so change 0A to EA.

Excellent work as always.. you should write a guide for this. I have it open in IDA but I think I got my offsets wrong so it looks like nothing to me.

[dsixda]

which other devices? kaiser, diamond etc? or just another Elfin's ROM?

I think XIPs were from Kaiser. They were straight copy, but SYS were ports... OEM was Elfin of course.

[!Aman!]

Excellent work as always.. you should write a guide for this. I have it open in IDA but I think I got my offsets wrong so it looks like nothing to me.
hehe, i don't think we need to write a guide for this feature. its only for the cooks and i guess they (u, me, koko, ameet etc) already know it. and also it is device specific, so it may not work for other devices.

[!Aman!]

I think XIPs were from Kaiser. They were straight copy, but SYS were ports... OEM was Elfin of course.
:rolleyes: r u sure? i really doubt it.

[dsixda]

:rolleyes: r u sure? i really doubt it.

Onyx 1.0, 2.0, 2.2.. Kaiser 6.1 XIPs ;-) Might be Experia, but I'm almost sure it's Kaiser.

[dsixda]

hehe, i don't think we need to write a guide for this feature. its only for the cooks and i guess they (u, me, koko, ameet etc) already know it. and also it is device specific, so it may not work for other devices.

Hey I need a guide :)

[!Aman!]

Onyx 1.0, 2.0, 2.2.. Kaiser 6.1 XIPs ;-) Might be Experia, but I'm almost sure it's Kaiser.
no way. just copy out the OEMXIPkernel from a kiaser's XIP.bin, cook it in ur kitchen and test.

[dsixda]

no way. just copy out the OEMXIPkernel from a kiaser's XIP.bin, cook it in ur kitchen and test.

Dude, I'm going to sleep.. it's past 5am and I have to host a party at my place in a few hours LOL :) My life has evolved (or devolved?) to just sleep and XDA.

Ask ayyu3m, he can confirm the XIP, as he was helping me w/ the porting.

Take care and thanks!

[!Aman!]

alright... i'll ask him :D

[ayyu3m]

alright... i'll ask him :D
heyllo bro. as much as i want to believe on that xip straight from other devices are possible, the experiments have proved wrong.

i never had any xip which was straight from another device working straight man. i think dsixda maybe mistaken by the fact when we extract xip.bin, the old modules and files in the OLD_XIP folder and ROM\XIP folders in koko's kitchen are used to create the final XIP for our ELVES.

i repeat, that i have tried many times XIP''s that have been extracted and placing them directly in the kitchen doesnt boot my elf. and so i have to get hold of the xip.bin and extract via kitchen....which does as said above

[dsixda]

heyllo bro. as much as i want to believe on that xip straight from other devices are possible, the experiments have proved wrong.

i never had any xip which was straight from another device working straight man. i think dsixda maybe mistaken by the fact when we extract xip.bin, the old modules and files in the OLD_XIP folder and ROM\XIP folders in koko's kitchen are used to create the final XIP for our ELVES.

i repeat, that i have tried many times XIP''s that have been extracted and placing them directly in the kitchen doesnt boot my elf. and so i have to get hold of the xip.bin and extract via kitchen....which does as said above

Hmm.. it's been a while since we did those experiments.. But I kind of remember just using the XIPs from the Nike kitchen. And for me, some of them worked with straight copy, and others caused the device to hang.

Anyway it was back when I was a newb so I probably didn't understand it enough either. I think ayyu3m is right when he said we did the xip extraction via Koko's kitchen.

[!Aman!]

yeah, thats what i'm saying that u can use another device's XIP as such. we can only use MSXIPkernel from that after porting.

[dsixda]

Ok, another update to the Universal PP Changer... This time we can handle 3.xx ROMs with ULDR removed. I have tested it.

A huge thank-you to htctouchp for allowing us to remove the ULDR and thus make our ROMs 3MB smaller!!!!!

[chihliouma]

Ok, another update to the Universal PP Changer... This time we can handle 3.xx ROMs with ULDR removed. I have tested it.

A huge thank-you to htctouchp for allowing us to remove the ULDR and thus make our ROMs 3MB smaller!!!!!

Hi DSIXDA, does that mean you will relaese another version of PP changer soon ?

[dsixda]

Hi DSIXDA, does that mean you will relaese another version of PP changer soon ?

yes, it's already there... that's why I posted the message..

[chihliouma]

yes, it's already there... that's why I posted the message..

You mean the one in the post 2 of this thread ? Sorry I thought it was still the previous one. I'll try later. But just let me to uncerstand more clear that by using this new PP changer, I can save 3M ?

[!Aman!]

You mean the one in the post 2 of this thread ? Sorry I thought it was still the previous one. I'll try later. But just let me to uncerstand more clear that by using this new PP changer, I can save 3M ?
no, PP changer doesn't give u extra space. if the ULDR partition is removed from the ROM that u are using, only then it gives u extra space. Dsixda meant that new PP changer works for those kinds of ROMs where ULDR partition has been removed.

[chihliouma]

no, PP changer doesn't give u extra space. if the ULDR partition is removed from the ROM that u are using, only then it gives u extra space. Dsixda meant that new PP changer works for those kinds of ROMs where ULDR partition has been removed.

Thanks for the explanation.