Offical Bugs List with Sprint Touch Pro 2 - WinMob. 6.5 Update - Page 5

BillJr106 · #41 (**permalink**) 03-19-2010, 03:36 PM

Quote:

Originally Posted by willysp

- No, it's not registry settings
- There's a pagepool changer utility (attached) that you need to run on the .nbh before you flash it. It changes a couple bytes in the .nbh
- Run the Sprint update .exe, and click Next to let it extract. Stop. Don't go further with the update.
- Go to C:\Users\<yourname>\AppData\Local\Temp and copy the most recently time-stamped folder somewhere like your desktop. Name will be something like pftDA6C.tmp, but it'll vary.
- Cancel the Sprint update program
- Extract the zipped pagepool changer into the folder. Run it, selecting the .nbh file. Pick a different number. Make sure you click "Change To" before "Close". Try 20 or 24.
- Then run ROMUpdateUtility.exe to flash

Good luck!

Are there any side effects to be aware of? Also what does it change the pagepool to? Is there a reason why this isnt the default?

BillJr106 · #42 (**permalink**) 03-19-2010, 03:38 PM

Quote:

Originally Posted by willysp

- No, it's not registry settings
- There's a pagepool changer utility (attached) that you need to run on the .nbh before you flash it. It changes a couple bytes in the .nbh
- Run the Sprint update .exe, and click Next to let it extract. Stop. Don't go further with the update.
- Go to C:\Users\<yourname>\AppData\Local\Temp and copy the most recently time-stamped folder somewhere like your desktop. Name will be something like pftDA6C.tmp, but it'll vary.
- Cancel the Sprint update program
- Extract the zipped pagepool changer into the folder. Run it, selecting the .nbh file. Pick a different number. Make sure you click "Change To" before "Close". Try 20 or 24.
- Then run ROMUpdateUtility.exe to flash

Good luck!

If I already flashed... is it too late to do this? Can I reflash??

**zone23** · #43 (**permalink**) 03-19-2010, 03:38 PM

A lot of these comments don't sound like "bugs" in the ROM.

dynofrk666 · #44 (**permalink**) 03-19-2010, 03:39 PM

Not sure if this is a bug or i'm just looking in the wrong spot, but theres no option in the task manager for "tapping X to close a program". Is that feature removed from 6.5 or is it just in a different spot? I'm used to not having programs close since i've been using 6.5.x for a while, but thought maybe the office 6.5 update would have that feature included.

Edit - found it, User error!

**willysp** · #45 (**permalink**) 03-19-2010, 03:56 PM

Quote:

Originally Posted by BillJr106

Are there any side effects to be aware of? Also what does it change the pagepool to? Is there a reason why this isnt the default?

It changes the pagepool to whatever number you choose. (I suggest trying 20 or 24 if you think 6.5 is sluggish).

Yes, the one side effect is that every 1MB you increase the pagepool takes away 1MB of Total Program Memory. The 6.5 Stock has 183.18 MB by default. If you increase the pagepool from 15 to 20, say - the new Total Program Memory will be 178.18. So, you're trading RAM for pagepool. Think of pagepool as like windows pagefile (but that's not really a good analogy).

Do a search on "windows mobile pagepool". Also try setting it to 0, which is a "dynamic pagepool", but will be like a manual pool of 30. Too difficult to explain in detail here - google the phrases above.

Good news is that if you don't notice a more responsive 6.5 by changing pagepool from 15 to 20 or 24, then just change it back to 15. It really is as simple as just running the pagepool changer and flashing. You're not going to hurt anything.

**willysp** · #46 (**permalink**) 03-19-2010, 03:57 PM

Quote:

Originally Posted by BillJr106

If I already flashed... is it too late to do this? Can I reflash??

Yes, just run the pagepool changer and reflash!

fsfsfsfs · #47 (**permalink**) 03-19-2010, 03:58 PM

Quote:

Originally Posted by searcher61

There is a cab for LED notifications around, do a quick search. Run it and you will be able to change that setting. Hell... here it is!!

Thanks! I did a search for flash light and didn't get anything.

I mean, I guess it isn't a "bug," but the fact that it was there in 6.1 but they took it out for 6.5 is BS.