Best PagePool?

[jim256]

just wondering if anyone has experimented much with pagepool sizes on the vogue to see which was the fasted/optimal setting?

thanks.

[bugzy]

n00b question

but what is page pool exactly? and how is the setting changed

[mindfrost82]

n00b question

but what is page pool exactly? and how is the setting changed
My understanding is that it is basically a way to change the RAM/ROM storage (what you have available for storage vs what you have available for running programs). It is used when creating a custom ROM. I'm not sure if you can change it without creating a ROM, I don't think you can.

[jim256]

as i understand it, its some sort of system.. "cache" (?) which is accessed quite frequently by the system by most everything. increasing this decreases program memory (which means slowing down), so the important thing is finding the right balance...or so they say.

personally, idk if that ^^ is even half true, but thats what ive read and understand it to be.

supposedly, you can use activesync to change it, though i do not understand how to use it...not sure which rom version my wm6 sprint vogue uses.

heres the link, if anyone can figure it out...do explain!
http://forum.xda-developers.com/showthread.php?t=323538

other than that i have just been using the pagepool changer included with blee0125's vogue kitchen and reflashing, trying to see whats the best.

not sure whats the right answer though...

good luck, thanks, and post results!!

[OrionSX]

As far as I know, the "Page Pool" is a section of storage memory that WinMo uses as if it were RAM. The only difference is, from what I can tell, that Page Pool is directly related to how well WinMo runs, versus your Program RAM, which is essentially for other programs. I think.

On a device like the Vogue, with 128 meg of RAM and a slow as hell WinMo interface, I'd recommend increasing the page pool. Not going to run out of Program Memory anytime soon.

[fowen]

I flashed my Vogue and increased the page pool to 16MB and after using the device for a week I found myself restarting the device often because of qwerks and lag. I am not sure if that is from a tweak I preformed or the page pool.

I reflashed my device and moved it down to 14MB and I plan on using it for a few days and slowing installing what I need on it to see if it is a specific program or the page pool size.

[jim256]

I flashed my Vogue and increased the page pool to 16MB and after using the device for a week I found myself restarting the device often because of qwerks and lag. I am not sure if that is from a tweak I preformed or the page pool.

I reflashed my device and moved it down to 14MB and I plan on using it for a few days and slowing installing what I need on it to see if it is a specific program or the page pool size.

sounds good, please be sure to post your results.

and yes, wm on a touch is SLLOOWW i cant stand it! right now i actually have my pagepool at 34/36mb (cant remember) and...not noticing too much of a difference!! :(

dare i try 70mb??? like you said, the touch has a lot of RAM, and i usually dont find myself too low on it.

[dharvey4651]

sounds good, please be sure to post your results.

and yes, wm on a touch is SLLOOWW i cant stand it! right now i actually have my pagepool at 34/36mb (cant remember) and...not noticing too much of a difference!! :(

dare i try 70mb??? like you said, the touch has a lot of RAM, and i usually dont find myself too low on it.

If you up it to 70, the phone itself may not boot at all. It has to have enough RAM available for the OS itself.

I have my pagepool set at 16 and find it to be much snappier than at the default 12. I also have quite a few apps installed and am still noticing a difference.

[jim256]

If you up it to 70, the phone itself may not boot at all. It has to have enough RAM available for the OS itself.

I have my pagepool set at 16 and find it to be much snappier than at the default 12. I also have quite a few apps installed and am still noticing a difference.

hmm...what are you using to change the pp? just the tool included in blees kitchen? i really havent noticed much difference in any of them at all. you really can tell the difference all the time; its obviously faster?

thanks.

[dharvey4651]

Yes I used the unlocker first and then used the pagepool changer in his kitchen to change the pagepool on the OEM ROM and then reflashed it with the new ROM(OEM but with 16MB pagepool) effectively re-locking my device and notice a nice speed boost.

It sometimes takes a few mins to get some apps up that I frequently use and that speeds things up considerably but yes it does make a difference especially when browsing files on the device. It loads much faster. Try accessing the Windows folder with a 12MB pagepool using file explorer and time it and then do the same thing with a 16MB pagepool. You will also see a difference.

[jim256]

ok thanks a lot.

do you know out how to use that pagepool changer via activesync?
i saw you posted in that forum but...i didnt understand which rom version mine was.

but thx i will definitely try that.

[dharvey4651]

ok thanks a lot.

do you know out how to use that pagepool changer via activesync?
i saw you posted in that forum but...i didnt understand which rom version mine was.

but thx i will definitely try that.

I'm not too familiar with that other method that changes the pagepool via activesync but I'm glad I was able to help you at least a little.

[OrionSX]

@dharvey4651: What I'm interested in is the page pool's relation to software rendering. For example, when scrolling through a large (or hell, even medium to small) sized web page, the screen jerks and tears and all sorts of nasty things. But when I had my Mogul, it didn't do that. Now, I know the problem is REALLY caused by HTC not releasing proper DirectDraw drivers for the Imageon chipset, but the Mogul had the same chipset, and same lack-of-drivers, but still scrolled better. I'm wondering if this is because of Sprint bloatware. The Touch is loaded with even more of it then the Mogul was. Any ideas?

[Red49er]

@dharvey4651: What I'm interested in is the page pool's relation to software rendering. For example, when scrolling through a large (or hell, even medium to small) sized web page, the screen jerks and tears and all sorts of nasty things. But when I had my Mogul, it didn't do that. Now, I know the problem is REALLY caused by HTC not releasing proper DirectDraw drivers for the Imageon chipset, but the Mogul had the same chipset, and same lack-of-drivers, but still scrolled better. I'm wondering if this is because of Sprint bloatware. The Touch is loaded with even more of it then the Mogul was. Any ideas?

I've noticed a similar problem in Opera web pages. I always thought it was due to the page loading still, but I suppose I could be wrong. I think I'm using either a 12 or 16mb pp. (No2Chem's 6.1 roms, and before that DCD 0.2.0). If I remember correctly, I never saw this with the stock rom.

[jim256]

I've noticed a similar problem in Opera web pages. I always thought it was due to the page loading still, but I suppose I could be wrong. I think I'm using either a 12 or 16mb pp. (No2Chem's 6.1 roms, and before that DCD 0.2.0). If I remember correctly, I never saw this with the stock rom.

i am pretty sure i saw this plenty with the stock rom. the stock pp is 12mb i believe. i was hoping to have gotten rid of that by upping the pp as well. i am currently running no2chems build 107 and ive modified the pagepool to...24 mb i think?

though htc says they do not intend to release the better drivers for the touch, im sure it wont be too longer after they are out that someone is able to rip them from a device that has them, and modify them for the vogue.

gosh i wish it was faster...

[Red49er]

So your 24mb pp still stutters on web pages?

[jim256]

So your 24mb pp still stutters on web pages?

thats right. with 32mb as well i believe.
we need drivers!

[dodgeboy]

I've had the best luck with 20mb. It seems to slow down with a higher or lower settings. 20mb is a sweet spot with my phone, the way it's setup now.

Dave

[jim256]

I've had the best luck with 20mb. It seems to slow down with a higher or lower settings. 20mb is a sweet spot with my phone, the way it's setup now.

Dave

thanks a lot for your input, will be trying 20mb on my next flash.