yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] Ameet:
the device was sluggish just after the bootup for sometime.. between those two its not actually much but u can make out the difference ;)
[Touch GSM ROM Development] !Aman!:
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:
[Touch GSM ROM Development] Swiftblade:
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?
[Touch GSM ROM Development] Ameet:
i've kept the default setting of 16k glyph cache and made the 0mb pp change in nk.exe itself :)
[Touch GSM ROM Development] !Aman!:
right now i'm using 32K glyphcache. the default value was 8K. and so far no issues.
[Touch GSM ROM Development] !Aman!:
default is 16k for u??? i thought we were using the same SYS :p
[Touch GSM ROM Development] Ameet:
:D my bad.. 8k is my default :)
[Touch GSM ROM Development] !Aman!:
can u tell me what are default values of "ReplStoreCacheSize" and HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\CacheSize=

for u? in my boot.rgu, these values are set to 0 :rolleyes:
[Touch GSM ROM Development] 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.
[Touch GSM ROM Development] !Aman!:
so that means, having 0 mb pp does improve a few things :rolleyes:
[Touch GSM ROM Development] Ameet:
in my boot.rgu and device both, the values are 0.. why? any issues? :)
[Touch GSM ROM Development] !Aman!:
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:
[Touch GSM ROM Development] Ameet:
:) maybe something in the rgus u gave me? coz in my device i didnt touch anything and it didnt change :)
[Touch GSM ROM Development] !Aman!:
aahhhh, found it :o
[Touch GSM ROM Development] Ameet:
where and what was it?
[Touch GSM ROM Development] !Aman!:
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
[Touch GSM ROM Development] 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
[Touch GSM ROM Development] dsixda:
Yup this was discussed in the previous 2 pages ;-)
[Touch GSM ROM Development] Swiftblade:
Effects of Zero Pagepool added in 1st post...

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
[Touch GSM ROM Development] willy792003:
so, what's the diff between setting it to "00 16" and "00 15"?
[Touch GSM ROM Development] Ameet:
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?
[Touch GSM ROM Development] willy792003:
dynamic means it starts from 0 and then dynamically changes whereas static means it stays 0 page pool size?
[Touch GSM ROM Development] guap:
what about to make this thread sticky? :p
[Touch GSM ROM Development] Swiftblade:
@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...
[Touch GSM ROM Development] ayyu3m:
hey Swiftblade, long time. and while ur here, i wana ask if u gona be making any roms soon??!!
[Touch GSM ROM Development] Swiftblade:
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.:)
[Touch GSM ROM Development] ayyu3m:
yeah all the cooks are equally great. and i wud like to see ur releases as well, cos each cook have diff styles ;)
[Touch GSM ROM Development] Swiftblade:
Yes, each cook has his own preferences. You should try your hands at cooking too..;) It is addictve at times... hehe:D
[Touch GSM ROM Development] Noonski:
ayyu3m, is hardcore Flashing material.
[Touch GSM ROM Development] ayyu3m:
haha! you throw em' roms, i catch em' roms. keke. all this flashing is makin me want to coooooooooooook. :D
[Touch GSM ROM Development] 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.
[Touch GSM ROM Development] !Aman!:
well, u should test that for your needs. i'll suggest u to try 0 mb, default or 16 mb pp.
[Touch GSM ROM Development] dsixda:
Actually, so far the best have been either 0 MB or 18 MB (there is no 16MB) :)
[Touch GSM ROM Development] !Aman!:
no 16 MB??? :D

how can u say that?
[Touch GSM ROM Development] dsixda:
We could try ;-)
[Touch GSM ROM Development] !Aman!:
i'm already using 16 mb pp. i've been using it for a month or so
[Touch GSM ROM Development] dsixda:
Sorry for my ignorance! How is it working for you? Compared to 0MB?
[Touch GSM ROM Development] !Aman!:
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?
[Touch GSM ROM Development] dsixda:
LOL! I downoaded 2.28 this morning and then forgot. Thanks for the reminder!!
[Touch GSM ROM Development] hendrixus:
OK, I'll try. I am on default right now. For I am gonna to to get my DeviceId and CID

Make a backup of the ROM 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
[Touch GSM ROM Development] colonel:
Advantages of 4mb, 8mb, etc. pagepool

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 ?
[Touch GSM ROM Development] !Aman!:
1. read this thread: http://xdaforums.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.
[Touch GSM ROM Development] colonel:
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.
[Touch GSM ROM Development] 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.
[Touch GSM ROM Development] 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:
[Touch GSM ROM Development] 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.
[Touch GSM ROM Development] !Aman!:
which Base ROM does ayyu3m uses for his ROM?
[Touch GSM ROM Development] dsixda:
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.
[Touch GSM ROM Development] ayyu3m:
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?
[Touch GSM ROM Development] !Aman!:
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.
[Touch GSM ROM Development] dsixda:
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.
[Touch GSM ROM Development] 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://xdaforums.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.
[Touch GSM ROM Development] Noonski:
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://xdaforums.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 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.
[Touch GSM ROM Development] 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..
[Touch GSM ROM Development] Noonski:
No you did not beat me to it.

The package should already contain everything then :p
[Touch GSM ROM Development] dsixda:
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.
[Touch GSM ROM Development] blasev:
wow, thx :D
[Touch GSM ROM Development] 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>
[Touch GSM ROM Development] dsixda:
Universal Page Pool Tester -- beta testers needed

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://xdaforums.com/showpost.php?p=2274573&postcount=2
[Touch GSM ROM Development] Noonski:
Re arranged the thread a bit.

Making it Temp Sticky to grab some Attention for Testing Purposes.
[Touch GSM ROM Development] 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.
[Touch GSM ROM Development] !Aman!:
what do u mean by dynamic PP :)?
[Touch GSM ROM Development] dsixda:
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"?
[Touch GSM ROM Development] !Aman!:
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.
[Touch GSM ROM Development] dsixda:
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.
[Touch GSM ROM Development] !Aman!:
"18 15" doesnt mean 24 MB 'dynamic' PP. "18 15" means 96 MB static PP
[Touch GSM ROM Development] kokotas:
+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...
[Touch GSM ROM Development] !Aman!:
---del----
[Touch GSM ROM Development] kokotas:
lol:D

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!

Regards!
[Touch GSM ROM Development] !Aman!:
ok, i'll just keep quiet on this issue now.
[Touch GSM ROM Development] kokotas:
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!
[Touch GSM ROM Development] Satyan:
Elfin Unable power up after using pp changer

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 ...
[Touch GSM ROM Development] blasev:
u can try to upgrade using sd card. and use original rom ;)
[Touch GSM ROM Development] Satyan:
htc crash

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 ....
[Touch GSM ROM Development] Satyan:
Figured it out !

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

Thanks again :) !!!

This forum Rocks !
[Touch GSM ROM Development] 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.​
[Touch GSM ROM Development] dsixda:
Ok made the changes.... see if you like it!

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)
[Touch GSM ROM Development] dsixda:
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 ;)
[Touch GSM ROM Development] !Aman!:
as u are directly asking me, so i'd just say the nb's are fine. but i didnt check the batch file.
[Touch GSM ROM Development] dsixda:
Well, I mean everyone else too ;) But you are one of the resident experts in page pool info ;)

PS. Thanks for checking
[Touch GSM ROM Development] !Aman!:
welcome

i'm not an expert here like some of the other guys here though.
[Touch GSM ROM Development] dsixda:
You may not know the inner technicalities but you know what you are doing... It's good to have you on this board.
[Touch GSM ROM Development] !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...
[Touch GSM ROM Development] 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
[Touch GSM ROM Development] !Aman!:
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.
[Touch GSM ROM Development] dsixda:
Ok, I guess I'll just go with the popular values that have been mentioned in the posts.
[Touch GSM ROM Development] !Aman!:
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.
[Touch GSM ROM Development] Noonski:
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.
[Touch GSM ROM Development] !Aman!:
i know this is not useful to most of the people (99%) here, thats why i never thought to post it in public.
[Touch GSM ROM Development] dsixda:
Where did you get these calculations from?
[Touch GSM ROM Development] !Aman!:
read the assembly language related to ARM.
[Touch GSM ROM Development] dsixda:
If possible, can you try on your Elf with 1.1x ROM?
[Touch GSM ROM Development] blasev:
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
[Touch GSM ROM Development] dsixda:
A UK T-Mobile Elfin user is reporting an Unknown page pool value after using my device_info.bat - http://xdaforums.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..... ??
[Touch GSM ROM Development] !Aman!:
i guess 2.81 ROM is older than 2.20 :rolleyes:
[Touch GSM ROM Development] dsixda:
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://xdaforums.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.
[Touch GSM ROM Development] 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
[Touch GSM ROM Development] dsixda:
Is this the correct value, and shall I add 2MB to the tool?
[Touch GSM ROM Development] 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?
[Touch GSM ROM Development] benjih:
yes noonski´s numbers fit i have tried them.. runs great
[Touch GSM ROM Development] dsixda:
Ok thanks, I've updated the tool to support 2MB PP for Elfs.