CDMA Touch Pro XIPs 20764 20771 20954 21015 21018 21028 21032 21109 - Page 9

rjmjr69 · #81 (**permalink**) 01-30-2009, 04:54 AM

Quote:

Originally Posted by scrosler

Ok, after finally spending some time with this XIP I have to say I must recant my first thoughts about speed. They gaines are pretty prevelant. I was uusing the old "opern \windows with file explorer" test and not much else.

I have..... Played with a couple differnt page pools. Updated my kitchen with some newer oems. Flashed and relfashed to confrim the results......
Then flashed and just used it for a while.....

Damn its fast! Its real fast! This thing is nice!

Verry well done!
..... This thing is fast.

I second this I'm running it on sprint tp and its blazing Thanks

**gguruusa** · #82 (**permalink**) 01-30-2009, 11:29 AM

Aside from fun and interesting, I can't see the purpose to this. Removing ULDR isn't going to speed your device up. Resizing the partitions are't going to either (ok, it'll make it boot about 1/20th of a second faster). Moving nk.exe from XIP to SYS isn't going to do anything either (except break some tools). With the exception of removing things like mencfilt (which most do anyway), I see ZERO that would affect speed.

So you get 1.5 MB of memory back. Are you seriously so short on memory that you need it? This device isn't cramped like the Titan.

Worse, by shrinking the partition, you limit your ability to import other xips (and you break some tools).

FormerPalmOS · #83 (**permalink**) 01-30-2009, 02:28 PM

The changes that (IMHO) affect speed aren't due to resizing or shrinking - gaining memory is just a bonus. The speed gains are from changes to boot.hv to take advantage of the file filter cache when a larger page pool is used (larger than stock 6) and the file system replication filter. Neither was set-up correctly in the stock boot.hv(again, IMHO). Of course what started this all was the fact that the XIP Scott started with had the CacheFilt removed (tough to take advantage of it if it ain't there). That and I need encryption so removing mencfilt isn't an option.

BTW - the way I have this set-up mencfilt isn't even attached to the FATFS running on the on-board NAND, so there would be ZERO speed difference from removing that dll. And it's not big enough that a significant amount of RAM could be recovered - so I see ZERO value in removing it - unless as you point out one were to run out of space in the XIP. I'll admit this is a possibility with the XIP as I have it, but keep in mind this project was intended to speed up my phone for the way I use it. I posted this here for anyone else in a similar situation who may benefit. FOr someone who wants to import new XIPs or load other stuff into XIP, this thread ain't the place to be lookin'...

FormerPalmOS · #84 (**permalink**) 01-30-2009, 02:30 PM

Quote:

Originally Posted by scrosler

No notabe speed over last ver right off that bat but I do see more free mem by about 1.5 megs.

Whats youre take on speed?

Between ver 1E and 2E there should be NO difference in speed. The changes from 1 to 2 were to a) recover memory and b) default encryption to zero because someone kept pestering me about it

Plus making the pagepool changer app work and a few other minor things.

**gguruusa** · #85 (**permalink**) 01-30-2009, 02:46 PM

Quote:

Originally Posted by FormerPalmOS

The changes that (IMHO) affect speed aren't due to resizing or shrinking - gaining memory is just a bonus. The speed gains are from changes to boot.hv to take advantage of the file filter cache when a larger page pool is used (larger than stock 6) and the file system replication filter. Neither was set-up correctly in the stock boot.hv(again, IMHO). Of course what started this all was the fact that the XIP Scott started with had the CacheFilt removed (tough to take advantage of it if it ain't there). That and I need encryption so removing mencfilt isn't an option.

BTW - the way I have this set-up mencfilt isn't even attached to the FATFS running on the on-board NAND, so there would be ZERO speed difference from removing that dll. And it's not big enough that a significant amount of RAM could be recovered - so I see ZERO value in removing it - unless as you point out one were to run out of space in the XIP. I'll admit this is a possibility with the XIP as I have it, but keep in mind this project was intended to speed up my phone for the way I use it. I posted this here for anyone else in a similar situation who may benefit. FOr someone who wants to import new XIPs or load other stuff into XIP, this thread ain't the place to be lookin'...

Yeah - I missed that your list of changes at the top of post 1 was for ver. 1 to ver. 2 of your xip. I can see your boot.hv changes having some effect. Sadly, they are 99% of the bang for 1% of the work (encryption aside). What concerned me is people adopting your xip for entirely the wrong reasons, which you nicely pointed out is getting encryption back. Thanks for the clarification.

BTW, thanks for the info early in this thread. Usefull stuff.

**scrosler** · #86 (**permalink**) 01-31-2009, 02:44 AM

Quote:

Originally Posted by FormerPalmOS

Between ver 1E and 2E there should be NO difference in speed. The changes from 1 to 2 were to a) recover memory and b) default encryption to zero because someone kept pestering me about it

Plus making the pagepool changer app work and a few other minor things.

I know you both say that the speed is not there but I am telling you it is, IMHO.

I released the 1.4 beta with a PP of 7.5 and it out runs the same sys files with older XIP.

Am I just imagining this?

Also, You say the first XIP is not PP editable but the first thing I did was change it to 9 and had no issues at all. How did you try chaning the PP?

FormerPalmOS · #87 (**permalink**) 01-31-2009, 03:50 PM

Quote:

Originally Posted by scrosler

I know you both say that the speed is not there but I am telling you it is, IMHO.

I released the 1.4 beta with a PP of 7.5 and it out runs the same sys files with older XIP.

Am I just imagining this?

Also, You say the first XIP is not PP editable but the first thing I did was change it to 9 and had no issues at all. How did you try chaning the PP?

I said that the PP changer app wouldn't work - it will change the default value stored in the struct that defines memory partitioning at boot, however the code (as I left it) will promptly over-write that with a pagepool size of 12MB. Again, don't know why I thought that would be a good idea at the time.

As for speed, either ver 1 or ver 2 should be faster than stock - I meant that ver 2 shouldn't be any faster than ver 1 (using the same size pagepool).

**scrosler** · #88 (**permalink**) 01-31-2009, 07:23 PM

Quote:

Originally Posted by FormerPalmOS

I said that the PP changer app wouldn't work - it will change the default value stored in the struct that defines memory partitioning at boot, however the code (as I left it) will promptly over-write that with a pagepool size of 12MB. Again, don't know why I thought that would be a good idea at the time.

As for speed, either ver 1 or ver 2 should be faster than stock - I meant that ver 2 shouldn't be any faster than ver 1 (using the same size pagepool).

Stange strange strange....

I can set PPC with the first one and it sticks. Never saw the issue you did on that. as a matter of fact I set the PP on the payload to 9 and never looked back. I wonder if it was because I used the ervius buildos to set the RMO ver first? Could that have unlocked it all the way?

What do you think I need to do about the phone settings issue? What will it take to resolve it?

FormerPalmOS · #89 (**permalink**) 01-31-2009, 09:42 PM

Quote:

Originally Posted by scrosler

Stange strange strange....

I can set PPC with the first one and it sticks. Never saw the issue you did on that. as a matter of fact I set the PP on the payload to 9 and never looked back. I wonder if it was because I used the ervius buildos to set the RMO ver first? Could that have unlocked it all the way?

What do you think I need to do about the phone settings issue? What will it take to resolve it?

I'm absolutely sure that the PP changer app will NOT change the PP on rev 1 - it will change the default, but the default is overwritten with 12 by the code as I left it. Anyway, it's not relevant as I fixed that anyway.

I'm working right now on a 20754 SYS and XIP with your OEMs to address the phone settings issue. 21109 is a wierd build on a number of levels. I grabbed the sys from the just-released WWE Diamond (GSM) ROM update. Boatload of nicely packaged APPs just ready for the picking in that one as well

If I had more time, I may go through and compare versions with what's in your kitchen - but you've got far more experience working with the VZW operator package than do I - I'd probably screw something up. So for now, I'm just going to a) work on the XIP with 20754, b) cook with that plus your existing OEMs and SYS and see what that does, then c) cook with the 20754 sys and 20754 XIP.

BTW I'm hoping lifting the DDI from this ROM works - supposedly it's a new version and should improve 2D performance. We'll see...

**scrosler** · #90 (**permalink**) 02-01-2009, 08:08 AM

Quote:

Originally Posted by FormerPalmOS

I'm absolutely sure that the PP changer app will NOT change the PP on rev 1 - it will change the default, but the default is overwritten with 12 by the code as I left it. Anyway, it's not relevant as I fixed that anyway.

Maybe I have a special Page pool changer OR my thoeroy about running through the Ervius Kitchen is tru. I will download and test again. But like you said. Not relevant. But just side note: There are many people running diff page pools on this ROM and I did nothing to the payload other than change it to refelct the ROM very and set PP to 9. I really think its in the kitchen. But seeings how you are swapping builds it doesnt matter....
This one is just strange.

Quote:

Originally Posted by FormerPalmOS

Boatload of nicely packaged APPs just ready for the picking in that one as well

If I had more time, I may go through and compare versions with what's in your kitchen - but you've got far more experience working with the VZW operator package than do I - I'd probably screw something up.

Too late, beat you to it ;c) 1.4 will have the newer apps and much more along the lines of packages instead of OEM/DLL's

Quote:

Originally Posted by FormerPalmOS

So for now, I'm just going to a) work on the XIP with 20754, b) cook with that plus your existing OEMs and SYS and see what that does, then c) cook with the 20754 sys and 20754 XIP.

Ok, let me know how that works out. I have always liked 20754 more than most. Never had time to switch back from 21109.... Too busy....

Quote:

Originally Posted by FormerPalmOS

BTW I'm hoping lifting the DDI from this ROM works - supposedly it's a new version and should improve 2D performance. We'll see...

Hmmmm, that would be nice ;c)

Cant wait to see how this turns out!