CDMA Verizon Touch Pro XIPs - WM6.5 Native Kernel 23047 23053

[FormerPalmOS]

Please see previous XIP thread here: http://forum.ppcgeeks.com/showthread.php?t=73316

These XIPs are in "old-style kitchen" format - ROM folder with os.nb.payload and boot.rgu in the ROM\XIP. I also have a romhdr.bin that should work with Visual Kitchen but I have not yet tested it.

I do not include WinCENLS - make sure this is in your SYS. Unless otherwise stated these are 12MB page pool, spinlock patched. I also include the no2chem GxDMA.dll wrapper for DDI. Make sure you don't duplicate GxDMA in your OEMDrivers.

These also include cachefilt.dll and some boot.hv tweaks to take advantage of that, and to remove some other generally useless stuff. I include the registry edits for the LockStream DRM package - removing this can cause you to get stuck in phone settings screen among other wierd problems.

EDIT 22-Sep - 23053 uploaded. Tested and booting. All seems well after a couple hours of playing. Made with PlatformRebuilder. Not quite as compact as the old way of doing it but not too bad either. ZIP includes entire ROM structure for Ervius Visual Kitchen - confirmed booting on VZW CDMA Touch Pro.

First up is 23047 tested and booting. Made with old-style touch, very compact, maximum memory recovery.

Massive huge thanks to Da_G and company for the CDMA Touch Pro WM6.5 native kernel.

[jucytec]

Hurray~!!!!

[FormerPalmOS]

For some reason, Visual Kitchen wants to re-allocate all the modules in my XIP, move things around and waste about 48KB of program memory. I've given up trying to straighten it out. On to see if I can actually get a booter...

Oh - and reserving this post in case I go past 5 attachments...

[jucytec]

Originally Posted by FormerPalmOS

For some reason, Visual Kitchen wants to re-allocate all the modules in my XIP, move things around and waste about 48KB of program memory. I've given up trying to straighten it out. On to see if I can actually get a booter...

Oh - and reserving this post in case I go past 5 attachments...

FPOS, how's the 6.5 NK in comparison to 6.1 after your tweak? I too have a Vzw TP and can't run 23053 due to lack of memory.

[raidzero]

FPOS, do you have any threads on how you do this and the general theory behind it? is cachefilt just a filesystem filter? We have also found out that spinlock patching thr 6.5 NK yields worse performance or did you find a way around that? thanks! I love the work you do with the xip..

[bikeandestroyx]

Originally Posted by raidzero

FPOS, do you have any threads on how you do this and the general theory behind it? is cachefilt just a filesystem filter? We have also found out that spinlock patching thr 6.5 NK yields worse performance or did you find a way around that? thanks! I love the work you do with the xip..

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS) [ONLINE] - xda-developers
check that out

[FormerPalmOS]

Manilla and the HTC dialer together eat about 20Mb right out of the chute. The Windows Mobile 6.5 CHome today screen is about 5Mb - not as much as Manilla. The Windows dialer is about 1Mb vs. HTC at 10Mb. Getting rid of those two and running 12Mb I haven't run into any memory problems - in fact I've just stopped checking it.

However I agree - on my 20771 with both Manilla and HTC dialer, I used 10MB and 8MB. I noticed a speed difference, but even 10MB cuts it close on memory.

Dang Verizion, what kind of a rectally-cranial-inverted idiot thought whacking 96MB of memory out of the phone was a good idea...

[jucytec]

Originally Posted by FormerPalmOS

Manilla and the HTC dialer together eat about 20Mb right out of the chute. The Windows Mobile 6.5 CHome today screen is about 5Mb - not as much as Manilla. The Windows dialer is about 1Mb vs. HTC at 10Mb. Getting rid of those two and running 12Mb I haven't run into any memory problems - in fact I've just stopped checking it.

However I agree - on my 20771 with both Manilla and HTC dialer, I used 10MB and 8MB. I noticed a speed difference, but even 10MB cuts it close on memory.

Dang Verizion, what kind of a rectally-cranial-inverted idiot thought whacking 96MB of memory out of the phone was a good idea...

I got bored last night... So...
I've used a Resource Hacker to extract all the Bitmaps of the Tachi Phone Canvas and converted them into Monochrome 4 bit bitmaps. The Images in the "phcanImages.dll" is 10 MBs, i've shrunk them down to under 1MB.
Then I got rid of all the other bitmaps that I don't use. The answer Slider, back ground, buttons... I've adjusted the image dimensions to 1x1 and recompiled the "phcanImages.dll" the entire Tachi Skin EXT is under 1MB. and the Tachi Phone Canvas is at 3.

This actually saves me 6 megs in program memory! and I can dial out using Manila 2.1 which requires Tachi to dial out of favorites.

The Bitmaps are very dirty as this was my initial test, i'll begin creating a very clean one shortly.

[juliend]

Originally Posted by jucytec

I got bored last night... So...
I've used a Resource Hacker to extract all the Bitmaps of the Tachi Phone Canvas and converted them into Monochrome 4 bit bitmaps. The Images in the "phcanImages.dll" is 10 MBs, i've shrunk them down to under 1MB.
Then I got rid of all the other bitmaps that I don't use. The answer Slider, back ground, buttons... I've adjusted the image dimensions to 1x1 and recompiled the "phcanImages.dll" the entire Tachi Skin EXT is under 1MB. and the Tachi Phone Canvas is at 3.

This actually saves me 6 megs in program memory! and I can dial out using Manila 2.1 which requires Tachi to dial out of favorites.

The Bitmaps are very dirty as this was my initial test, i'll begin creating a very clean one shortly.

Strong work man!

[juliend]

Just bumpin this up. I'd be excited to try out the slimmed down Tachi dialer!