Is there anyway to change your page pool with a registry editor or something ? got the rom installed but only 16 mb Memory :S
Thanks In Advance
Nick..
No other way but to...
...follow the guide here: http://forum.xda-developers.com/showthread.php?t=313263
just my opinion but i found a 4mb page pool made the device run slightly slower, i am now using 6mb which seems the perfect balance for me.
Related
anyone can give me the explanation of this upgrade to windows mobile 5.0? pleasee...ups..thanks so much
READ.THE.WIKI.
Well i think it was mamaich who finds out that the Paging Pool size was only set to 2 MB.
Now in the new release the Paging Pool Size is 16MB and this improve the speed.
example:
Befor i was looking for an Internet Browser replacement because the speed was terrible slow.
Now the speed with the buildin Browser is very nice.
cu
mdajimmi
PS: Here is the complete story
http://forum.xda-developers.com/viewtopic.php?t=61926
mamaich found small page pool, made it bigger, saved the rom.
basically in my experience wm5 is now running almost, if not as fast as 2003se on b.a.
btw download the file n read the readme after reading the wiki.
if the wiki confuses you lots of the things in the readme will clear it up, if not then i suggest you dont mess with ur b.a.
This thread is for everyone using one of FARIA's 3.2 ROMs. I want to find out and share information about which paging pool size works better on your phone, 12 or 8.
Some Explanations:
There are 2 versions available, one with 8MB paging pool and one with 12MB paging pool. The paging pool is like virtual memory on a desktop windows computer. Basically, it's memory for open, running programs to sit in until the computer needs them again. More paging pool equals less program memory available. (program memory is similar to RAM on a windows computer.) A smaller paging pool equals MORE available program memory.
We all know WindowsMobile devices lose available program memory over time. Because of that, we have to soft reset the devices on a regular basis. I have tried both versions of FARIA. It seems that the 12MB rom uses memory BETTER! Since I have loaded the 12MB version a few days ago, I have only had to soft reset the device once or twice. When I had the 8MB version I had to reset every hour or so.
What has been your experience?
yeah, i installed the 12mb version. I don't have too much problem with the memory leak. After i closed all the programs, i still have almost 10 mb memory left. I had it running for almost 3 days already.
Can't really say, as I haven't tried the 8mb version yet. Other than a few known issues, I've been really happy with this ROM, so I won't change over to the other one until sometime next week (after I purchase and use Sprite Backup).
The 8MB version works good so far... Requiring a reset once per day or so if i am using my copy of Pocket Player...
vseehua said:
The 8MB version works good so far... Requiring a reset once per day or so if i am using my copy of Pocket Player...
Click to expand...
Click to collapse
Ive made my own rom, based on Faria OS 3.0 with 4mb paging pool (and 2Mb)
Now i have 35 Mb free memory (and 38 on 2 Mb pp), and this releas is very stable and fast. But i have only one problem - battery decrease very quickly in gprs session (cause of pp's size).
mun_rus said:
Ive made my own rom, based on Faria OS 3.0 with 4mb paging pool (and 2Mb)
Now i have 35 Mb free memory (and 38 on 2 Mb pp), and this releas is very stable and fast. But i have only one problem - battery decrease very quickly in gprs session (cause of pp's size).
Click to expand...
Click to collapse
Can you upload this 4MB rom? I would really to try it out.
Attn Lurkers
It would be really good to get everybody to chime in on this. So far, it looks like there is little, if any, difference between the roms. Let's hear what the rest of us have to say...
i've read @ modaco that s730 has 12mb pagepool.
can anyone comfirm that? i think it's way too much considering our low memory probs...
Wings has 6 MB paging pool.
How to change page pool on S730, and where is missing memory (43.58 of 64MB)
I have just flashed to the unbranded stock rom and felt the rom was running a little slow.
I changed the pagepool size of the rom to 32MB and reflashed, I must say the performance seems so much greater.
I have been keeping tabs on these threads, and havn't noticed anyone mention they have done this, a quick search in the xperia threads also shows no result,
I appologise if this info already exists, but I could not find it.
So here is a quick step by step,
Download whichever rom you prefer,
Download pagepool changer 2.21 from here:
http://forum.xda-developers.com/showthread.php?t=323269
open the pagepool changer, select the NBH file of the rom you want to flash,
change the pagepool size,
Flash to phone as you usually would and Voila!
Yeah I don't think anyones been playing with it too much yet, anychance of a benchmark to compare?
I found that big files (such as OS maps for memory map) loaded better with a 16mb one on my advantage but others seemed to think otherwise.
Changed Itje's blackstone based rom to 32mb and reflashed.
1st boot takes a long time, subsequent boots are much faster.
Opening big files feels much quicker.
128mb map opens in 2:13 seconds with 32mb pagepool
and 3:35 seconds with a 6mb (stock) pagepool.
(not full view, just 4x4 km squares of map)
that's initial load, subsequent maps are nearly instant.
Not huge amounts but noticeable
Is there a point in trying to flash it to 64mb, or does it cause an error?
I don't think I've ever seen any one reporting trying.
0 16 or 24 seem to give the best results.
its most common by cookers to change pagepool, but we dont brag about it, i used almost everytime a 16mb on my roms, but the latest i made got alot of "large" files in it, and therefor i changed it to 20mb, and setting it to 0 the phone takes care of the size, see itjes 3.5...
smaberg said:
its most common by cookers to change pagepool, but we dont brag about it, i used almost everytime a 16mb on my roms, but the latest i made got alot of "large" files in it, and therefor i changed it to 20mb, and setting it to 0 the phone takes care of the size, see itjes 3.5...
Click to expand...
Click to collapse
hehe I was going to PM you about it, I was going to try 32MB on your Xion 2.2 ROM, would it give something or should I just leave it at 20MB?
Gille1 said:
hehe I was going to PM you about it, I was going to try 32MB on your Xion 2.2 ROM, would it give something or should I just leave it at 20MB?
Click to expand...
Click to collapse
as above, its not the benchmark that makes the feel of speedin a rom, in my rom 20mb is great for userinterface speed, it feels like its more speedy, but a little slower at other things, so it depends on build of rom, what you want out of rom, there is no final best setting.
I'm using Jack Leung's Lite ROM v2.1.
Originally with a 16Mb pagepool, I've altered that to 20Mb and find it overall faster, especially re-loading large geological map series I use constantly
Tried 24Mb pagepool, seemed a bit too slow in booting and loading new programs - quite subjective though. 20Mb seems to work best for my uses
Hi,
with this tool
http://forum.xda-developers.com/showthread.php?t=323269
it is possible to change the page pool size of exisiting roms.
The new R2 generic german rom has 6MBytes
This one (based on the new R2)
http://forum.xda-developers.com/showthread.php?t=476386
has 24MBytes
As far as I was able to get informations about the page pool size there is not the "one and only" setting.
But is there any experience allready on the X1 with different sizes?
Best regards
dingolino
i make more testing on it and it depends on the rom in my eyes, sometimes i used 16MB and also 32MB, with my last build i feel that 24MB gives me best performance, if you look at cmex he uses i think 12MB as example, so i think it is hard to say what the best is.
Regards,
cHarOn
some people seem to have had success with 0mb ones, but personally I prefer a 16mb one, it seems to load bigger files a bit quicker.
I'm using 32mb and it seems to be quicker than my 16mb build but i think i need to decrease it.