yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
No correction necessary you are correct.

Exactly.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] svcglobal:
Thanks guys, so we must act very carefully messing up in those bytes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Just create a copy of your .nbh or .nb and you can always have two different versions.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
Worked great , 24MB Page Pool, Total Memory after flashing 89.27 MB.

Thanks alot Dutty.

Best Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
It's thrue

24mb pagepool set here as well :D

New toys to test at work tomorrow :D

Thanks again Dutty!

I'm very happy :)

Leo
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jcespi2005:
Nice findig ;)

Many thanks, Dutty.... you're really great...

Cheers
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
bengalih

Great Assumptions, Zero Page Pool is as you assumed it to be, 113.36 MB after flashing.

Yet it is strange though, In Use memory is 44.00 MB and Free is 69.37.

So it increased the Total memory and also decreased the Free memory.

Device feels alot slower too.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Awesome work Dutty.

I was able to change your Hybrid PP to 24mb.

I didn't have to go through all the steps but simply extract the OS.nb from the Ruu_Signed.nbh.

Downloaded a program which is free called Hex Edit Free 2.5

Made the appropriate changes. Saved it. Used htcrt.exe and repackaged the ROM. Work's great. Now it's time to really mess around with some ROM's. Wondering how the 3.02, 3.03, 3.08, 3.10, and 3.14 ROM's will perform with changed page pools. Awesome work once again my friend
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] duttythroy:
Ok so that work for you I will try and edit the first post another time i will bring your post there also. thanks man and good night
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I wonder what a 6mb pp would feel like. Anybody willing to try 64mb pp?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
6 or 64 pp, I am willing to try it ,just tell me what you want .

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I say 64mb :)

I will try 6mb and see what we come up with. What ROM are you using to test with?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
I am Flashing 6mb PP at the moment,thought I would try both for you :)

I use my own coocked Rom, 3.03 OEM, ATT 3.14 Sys and OEMDrivers.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Ok let me know how each one works :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ramontrotman:
can i make a request?? that oem att rom...1.62. 24mb pp please thank yooou :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Ok will have to wait till later tonight after my 6 mile run ;) but I will get it to you.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
ok, 6mb pp

Total Memory: 107.34mb

In Use: 30.83mb

Free: 76.52mb

a bit slower than 12mb pp

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I take it you used my hex codes to get the 0MB pool? If so glad I could assist.

Remember that on the Hermes forum they found the best speeds with either 16MB and the second best was actually at 4Mb (which i think is the default on that device). The difference between those two was only 4 points in the benchmark tests but a loss of 11MB of RAM. My view is that having that 11MB is probably better than 4 points on the benchmark.

Let's not get too caught up with increasing the page pool to large numbers, as i don't think it has been proven that a 24MB pool even performs better than the default 12MB.

Let's also not go on feel (although it's a good indicator). Run a benchmark test no less than 4 times with each pool size and then take the average of the tests.

While 64MB may give a slight performance increase, i'm not sure it will be worth what it eats up in RAM.

happy testing though!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
Flashing 64mb pp now, I assumed the first value would be 40, hope it is correct :)

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
40 would be correct.. Windows calc (in scientific mode) will do the conversion for you.

I bet you are going to have about 20% free memory after all your apps load! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I know that from simply changing the false page pool via pagepool.exe that the SPB Benchmarks would be higher with a 24mb pp then the default one. I don't know how this will work with the real effect of changing the page pool. I agree some more testing needs to be done.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
ok guys

64mb pp, device stuck at first splash screen, no boot.

will go to 32 and do last trial, it is 1:10 am here and have to get up at 7 to take the kids to school :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I wonder if you are taking too much memory away from the system with a 64Mb.

You can try a 48MB with "30"Hex or a 52MB with "34"Hex. It would be interesting to note what the maximum is.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
This is much easier than using PB, FIXUPVAR & makeimg.exe!!!!

Retracted for a serious case of FootInMouthitis!

:o
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
I used "32"Hex by mistake and also device did not boot, now doing "20"Hex 32mb
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
So what does the brick master suggest we do :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
Here we go guys

32mb pp

Total Memory: 81.24mb

In Use: 31.34mb

Free: 49.91mb

Device boots faster, all over performance feels good and fast,screen update is also fast.

Start\Programs feels close to Launching from HTCHome.

I am off to bed now, will do Benchmarking tomorow :)

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
NOTHING!!!

The brick master has committed open mouth insert foot. Jesus, with a mistake like this, I would never let me touch my device again! (maybe I'll get a little peace?)

No wonder I'm haveing so many issues lately. I have a embeded umpc, running CE 6 & I just realized that for the last month I've been operating using data for CE6 on my CE5.2 Kaiser. :o

Too many projects at once, & look what happens. Now I only wonder what if anything I've been changing.

Man, I can't tell you how many time I reference the wrong data because I have too much going on.

You've hit it all Dutty! Sorry to question you, but I'm glad I did, because I just figured out several problems I've had with a few projects I've been working on. :o

A few Facts Stick though: The according to MS you should graph times alongside the pool size to determine optimum. The task that most commonly use the most paging are the device Boot Time (from reset till completely usable), Inbox Launch Time (from the time you hit the messaging button to the time you can access the inbox) & Contacts Launch Time (again, from the time you launch contacts to the time it become fully functional) There is a balance where the milliseconds of time are not worth the loss of RAM.

FYI!!!

Here is the Page pool skinny from MS:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
What was the hex that you used for 32mb. Dutty has the 24 and 32 listed as the same thing on the first post. I would like to test this as well.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
So let it be written.

So let it be done.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
32MB would be "20" Hex, 24MB would be "18" (as he has it)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
The HEX for 32 = 24? I'd also like to try 0, 4.5 & 15.

I have a contact that says 15 is optimal for the Kaiser.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
No the HEX for 32MB would be "20"

Hex for 36MB would be "24"

Hex for 15MB would be "0F" and 0 would just be 0 (0 is always 0 in any number system afaik :) ).

I don't think we can do half a MB like this, as we are only representing whole numbers with one byte of data. We would need a second byte of data to be able to reflect that, and I don't think it's worth the trouble for .5MB
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
LOL I know who that contact is :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
Funny guy, I'm not talking about Sleuth, unless he decided on using that b'c he knows Michelle @ MS CE6 Dev. Team.

She says that OEM's always bach at it though because the seconds it saves aren't worth all the phone calls they get about memory, as in where did it go?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
So re-reading your last post we should only increase the pp to .5 mb increments at a time?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
well I can say anything under the OEM 12 is not worth wasting your time with I have tested 2, 4, 6, 8, 10, and all where slower than the OEM 13 I have settled on 32 at this point since we have so much free RAM at boot and i don't run to many apps its not biggy the amount i loose to page pool and everything is smoother :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I am also running 32. Pretty nice so far. Using the 19199 build.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
I was just stating some info based on MS views of the page pool. Maybe I should've used a :rolleyes: to be clearer. As MS isn't really know for optimizing their creations, it takes xda to do that.

I would myself agree with Austin that anything below 12 is pretty pointless, except for maybe 0 if it can be properly configured, but then again that purportedly reaks havoc on the available ram from time to time.

Not sure how you could make half point increase without using PB either.

I was a little hesitant about using the 24 myself, & hell, I just flashed it & it's flying. Not much difference between that & 32 though from what I see.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I wonder if this has any effect on battery life?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MickyMax:
Thanks for sharing Dutty ! :)

Can you post the values of 6Mb, 8Mb, 10Mb, to have more RAM and see how it perform please ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thomassster:
i know i'm a noob at this stuff, but pagepool changer was all a placebo effect?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well this is interesting...as I was trying to answer the above question I found this...which ties into my thread on NOR/NAND:

Now from my interpretation this is saying that WITHOUT a pagepool the system (ROM) can load as

much as it wants into RAM

. Right...see the pagepool is like a backwards pagefile.sys on Windows (or swap on linux). Instead of swapping things out to disk to load more in memory, it swaps code pages in ROM out to RAM so it can run faster. This is why some devices run quicker with 0 pagepool, because

you don't limit

what they can put in RAM, so they put alot in RAM and thus can run faster.

Now some of the wording is murky, but based on the fact that we see more of our Total RAM eaten up when we increase our pagepool, it is safe to say that the pagepool is obviously in our RAM. So when you tell the ROM to allocate a 32MB pagepool you are telling it to allocate 32MB of the RAM and never to go above this amount.

So, when an application launches from the NAND ROM or from your NAND SD it loads into memory. Now my assumption is only certain types of code pages get loaded into the page pool. I say this because based on the statements in the quote, we obviously aren't limiting our TOTAL RAM use to 32MB if we set a 32MB pagepool. By this I mean I can load apps above the 32MB point. And, in fact, I do this everytime I load an app...since we see this app consume more RAM (and not just load into the already reserved pagepool area).

So, If I load up any app on my phone, some of it's code pages (and perhaps this is determined by the coder...or maybe just the OS at runtime?) get loaded into the pagepool, and the rest consume additional RAM.

However, anything running from the NOR ROM (\XIP directory) always just gets eXecuted In Place and doesn't need to copy anything to the pagepool or to the RAM. In fact

in a pure NOR device, no pagepool would be necessary

.

So why would we care whether an application gets loaded into the PP, normal RAM, or a combination of both? After all it is still taking up RAM (And infact with the PP that RAM is always being taken up whether we are using it or not). Again, this is supposition...but my guess is that the pagepool handles reusable code better. Meaning if I unload an app from RAM it gets fully removed and has to be fully reloaded every time I open it. However the parts of it loaded into the pagepool are not unloaded unless that space is needed for something else. This makes it quicker because it doesn't need to recopy those code pages from ROM everytime it wants to launch.

So what would all that mean for battery life?

My guess is that it would correlate a slightly better battery life to a larger page pool. This is because the larger the pool, the more it can store, the less swapping or reloading of code. However the question remains is how much swapping (or how much/what code) is actually being loaded into the pagepool in comparison to non-paged RAM? My guess is that it is insignificant as to affect battery life. The difference between a 6MB or a 32MB pagepool might only be 2-3%.

please comment on all the above!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Mmm.. I tried today my ROM with a 24mb pagepool today, battery live seems better yes. I don't have prove about this, I only wanted to say I noticed.

Thanks,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
I remove this post, wrong numbers...

i apologize :o

Leo
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Hmm interesting. I think I am noticing a slightly faster diminish in battery life with a 32mb pp. Using the 19199 Voda phone build with the 1.58.16.27 Radio, which gives me the best battery life. Going to try another radio.

Found something interest in the NOR/NAND thread.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
SPB Benchmark results 24mb pagepool

SPB Benchmark 24mb pagepool

I'll show you here a benchmark of my upcomming rom set with a 24mb pagepool.

ROM is based on the ATT 209 build.

Memory:

Program

Total: 89.27mb

In use: 40.62mb

Free: 48.65mb

Storage

Total: 124.54mb

In use: 19.88mb

Free: 104.66mb
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
SPB Benchmark results 32mb pagepool

And here are the results of the same ROM set with 32mb pagepool.

Memory:

Program

Total: 81.24mb

In use: 40.62mb

Free: 40.62mb

Storage

Total: 124.54mb

In use: 19.88mb

Free: 104.66mb
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
Quick question, I'm not a ROM cooker so it's a bit new to me.

Is it possible to extract a cooked ROM (udK's for example), make the changes for a true PagePool, and then cook the ROM again?

Is it that simple or is it more difficult?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Unless there is another option it's pretty complicated for someone who never cooked a ROM.

You need to dump the ROM, hexedit os.nb and recook.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
1.) Extract the .nbh and place this in your BaseROM Kaiser Kitchen folder

2.) run the 1a.ExtractNBHContent.cmd

3.) In the BaseROM folder you will now have a OS.nb

4.) Open the Hexeditor and search for the 12mb default pp string like in Dutty's first post.

5.) Make the changes too both values. There are two changes you must make.

6.) Run htcrt.exe located in the tools folder of the Kaiser Kitchen.

7.) Click on the builder tab.

8.) Click on the System with the .... and select the OS.nb that you just modified.

9.) Rename the .nbh file that you are going to create whatever you want.

10.) package your new .nbh with the KaiserCustomRUU.exe that is also located in the tools folder.

11.) Flash away.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
I already gave it a try.

I have extracted the ROM, modified the HEX values, but now cooking the ROM gives some problems. Maybe I should READ first! :D

It should work with Vista, isn't it?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
Wow, thanks!

I'm going to try now! I'll report back if it works for me! :D

[EDIT] Just modified the ROM (to 24mb PagePool), I'll try to flash it now! Wish me luck!

[EDIT] Flashing in progress.

[EDIT] Flashing finished. Hard resetting now.

[EDIT] It works. Now let's see how fast it is. Thanks for helping Alltheway!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
your not really dumping and cooking roms here people your just extracting the OS.nb from the RUU_signed.nbh then repacking the OS.nb into a RUU_signed.nbh lets try and keep the terms right so we dont get confucked :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jhernand1102:
So I tried this with Dutty's April 1st rom and was able to do everything but I noticed that the new file sixe is 70,0512 kb vs 87,496 for his orginal file...Something doesn't seem right so I don't think I should flash...Any Ideas? I noticed that there are 2 nbh file one is 17,000 kb is that that radio? and is that why the new file is smaller?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Just a taught.

Maybe it's easy to extract os.nb (and add it back in!) from ruu_signed.nbh with this cool tool :D

http://xdaforums.com/showthread.php?t=377514

Worth a try!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
Never mind, it feels like I cooked my first own ROM. :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
No problem now in payment I expect you to give me that 8800 GTX card you have, my two 7800GT's are running mighty slow LOL.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
Sounds fair isn't it. :D

Ohh wait.., can't give that away until we have video drivers for our Kaisers.

Sorry mate. ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
I use _romkoch_v099661 which I used for my hermes before to extract the RUU_Signed.nbh to any folder.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
I agree with you since when I did the test last night, the improvement in the device performance was not significant and i used my device today with 32mb pp and did not feel it was alot faster than 12mb pp.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thomassster:
32MB PP seems to be just a very tiny bit faster. i gotta try playing videos to see if there was a speed up there. If someone can do some benchmarks before and after, that'll be great to see.

edit: nm...benchmarks has been done by Laurentius26, but still waiting for the after PP change benchmarks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Benchmark

Currently I'm at work but will be home in a view hours. As soon as I'm home I will post the second benchmark

Regards,

Leo
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Compared 24 and 32mb pagepool with exactly the same ROM.

Benchmarks added on page 11 of this thread!

Cheers,

Leo ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] xkam8x:
So Judging by this thread, Im assuming that the pagepool changing utility that comes with the kaiserkitchen does not "truly" change the pagepool? =P
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Correct. This actually changes the PagePool. To what effect it has on battery life and performance is still yet to be determined.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
That's correct.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hakushox:
Lower index's just about across the board on that 32. I was hoping to see a little bit better results. Thanks for the post
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johanromijn:
--removed--
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MobilePhoneUser:
So, then what does the KaiserKitchen PagePool changer do if it doesn't "really" change the page pool?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hakushox:
Just installed 32MB pagefile one one of my devices. So far I'm not noticing any real improvment in speed. As far as battery life, we shall see tonight. Thanks AllTheWay for posting the 32MB pg of dutty's latest.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
No problem I am going to post a 16mb pp later tonight.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hakushox:
I've been doing side by side comparisons with 2 tilt's. 1 running dutty's default 24mb and the other 32mb. From what I see the 32 takes a few more seconds to boot as well as load programs. Once the programs are open, the reaction time is exactly the same.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rotohammer:
I'm looking forward to that. I rarely run more than 5 apps at a time, and if each app is between .5 and 2 megs, Id never exhaust a 16meg page pool.

Thank you in advance!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
I'm already on a 16mb pagepool.

Benchmark in next post.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
SPB Benchmark 16mb pagepool

SPB Benchmark 16mb pagepool

I'll show you here a benchmark of my upcomming rom set with a 16mb pagepool.

ROM is based on the ATT 209 build.

(24mb and 32mb pagepool based on the same source you can find on page 11 of this thread.)

Memory:

Program

Total: 97.30mb

In use: 48.57mb

Free: 48.73mb

Storage

Total: 124.66mb

In use: 23.58mb

Free: 101.09mb
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Looks like 24mb pp is the winner. 32 being second, and 16 coming in third.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
First of all, Thanks to Laurentius26 for his time and efforts doing the benchmarking for different PP.

Somehow 24mb pp causes random freezes with 3.14 build 19209 which I use at the moment, 16mb pp is ok, and seems alot faster too !!!

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Yes I agree with you, for me 16mb is the winner ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shadowlabs9:
Hi Leo,

Nice job...

But, what about battery life... any changes?

cheers
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I agree excuse my rude behavior, for not thanking you for your time and effort. I too am using a 16mb pp and it seems to work on Dutty's 19209 Build.

Sometimes when I get issues like that I re-flash the radio. I don't know why this helps, but I noticed when flashing a lot of the times changing the pagepool, I never changed my radio from 1.58.16.27. I would get random freezes like you said re-flash the radio and the problems would go away.

Anyways Great Job my friend :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Hi,

The bigger the pagepool, the worse battery live becomes.

I noticed this by comparing 24 and 32mb pagepool.