Updated 5/2/09 Drellisdee WM6.5 PPC Kitchen

[vin255764]

Originally Posted by ali3nfr3ak

im not having a problem with it

You dont have clocks in the titlebar in 23004?
For me they show up every other time I tap on battery/clock icon

[ali3nfr3ak]

Originally Posted by vin255764

You dont have clocks in the titlebar in 23004?
For me they show up every other time I tap on battery/clock icon

phoneredist\d9d7d86d-3f83-4289-bd32-aa1972a1447e

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\TaskBa r]
"LimitedClock"=dword:1

removed that

also removed these from my personal reg oem entries

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\TaskBa r]
"LimitedClock"=dword:0
"ConsistentClockOrBattery"=dword:0

WDM mentioned this one, but i didnt know about that one so i left it alone alone

HKEY_LOCAL_MACHINE\Software\Microsoft\Shell]
"ShowTitleBarClock"=dword:1


but i just checked my registry and it seems that mine is:

HKEY_LOCAL_MACHINE\Software\Microsoft\Shell]
"ShowTitleBarClock"=dword:0

[vin255764]

I let my 3 years old daughter to play with my phone and now I have analog clocks instead of digital in the titlebar lol I never seen it before

[ali3nfr3ak]

Originally Posted by vin255764

I let my 3 years old daughter to play with my phone and now I have analog clocks instead of digital in the titlebar lol I never seen it before

lol me either

[Getitnowmarketing]

Here's something new for the vogue users. I have implemented LZX compression into PPCK which compresses the imgfs more than the typical XPR compression. End result is about 15mb or so more free storage space on vogue. There is a very small trade off of a slower 1st boot ie. hard reset as the LZX compressed imgfs take longer to decompress and it also takes about 1 second longer to load titanium after a soft reset. After titanium initially loads I have noticed no difference in speed of device related to the LZX compression. I have used LZX compression on Touch Pro and Apache for a few weeks and its very impressive on apache as it lets you add about 9mb more in packages to the rom than you could using XPR. I have also included a tuned boot.rgu made for vogue using FPOS xip tuning suggestions. Changes to the boot.rgu are notated instead of just deleted.

[Getitnowmarketing]

Originally Posted by vin255764

I let my 3 years old daughter to play with my phone and now I have analog clocks instead of digital in the titlebar lol I never seen it before

Can't believe you've never noticed this before Vin. On a non today/titanium screen press and hold the time/clock.

[vin255764]

Originally Posted by drellisdee

Here's something new for the vogue users. I have implemented LZX compression into PPCK which compresses the imgfs more than the typical XPR compression. End result is about 15mb or so more free storage space on vogue. There is a very small trade off of a slower 1st boot ie. hard reset as the LZX compressed imgfs take longer to decompress and it also takes about 1 second longer to load titanium after a soft reset. After titanium initially loads I have noticed no difference in speed of device related to the LZX compression. I have used LZX compression on Touch Pro and Apache for a few weeks and its very impressive on apache as it lets you add about 9mb more in packages to the rom than you could using XPR. I have also included a tuned boot.rgu made for vogue using FPOS xip tuning suggestions. Changes to the boot.rgu are notated instead of just deleted.

Thank you!!!Cooking right now!!
The .nbh file is 15Mb less then before!

[ali3nfr3ak]

Originally Posted by drellisdee

Here's something new for the vogue users. I have implemented LZX compression into PPCK which compresses the imgfs more than the typical XPR compression. End result is about 15mb or so more free storage space on vogue. There is a very small trade off of a slower 1st boot ie. hard reset as the LZX compressed imgfs take longer to decompress and it also takes about 1 second longer to load titanium after a soft reset. After titanium initially loads I have noticed no difference in speed of device related to the LZX compression. I have used LZX compression on Touch Pro and Apache for a few weeks and its very impressive on apache as it lets you add about 9mb more in packages to the rom than you could using XPR. I have also included a tuned boot.rgu made for vogue using FPOS xip tuning suggestions. Changes to the boot.rgu are notated instead of just deleted.

thank you kindly drellisdee, one question,
will the LZX compression still be enabled after porting this to a new xip?

[Getitnowmarketing]

Originally Posted by ali3nfr3ak

thank you kindly drellisdee, one question,
will the LZX compression still be enabled after porting this to a new xip?

Yes using LennySh or Ervius xip porting tools or by hand. The LZX cecompr.dll is in the oemxipkernel which is retained from your source and only the mxipkernel changes. I made it into a xip.bin for easy porting so you should use that one as your device source for xip porting. Make sure you use the LZX payload/nk.fat as your template for cooking too (make sure its the LZX nk.fat in your vogue core not your old one which is set for XPR).

[ali3nfr3ak]

i have been trying to gain more ram using this guide here http://forum.xda-developers.com/show...&postcount=104

8028cbee - 8028d020 L00000432 NUL
8028d020 - 8028d020 L00000000 End: highest physical address
8028d020 - 8028e000 L00000fe0 NUL
8028e000 - 8028e000 L00000000 Start: start of RAM
8028e000 - 80290000 L00002000 NUL
80290000 - 80296000 L00006000 uninitialized data of region_1 nk.exe
80296000 - 8031a000 L00084000 initialized data of region_2 nk.exe
8031a000 - 8031a000 L00000000 ------ start of RAM free space
8031a000 - 87900000 L075e6000 NUL
87900000 - 87900000 L00000000 End: end of RAM

now when i use M'Reloc_nk to reallocate nk.exe from 80290000 to 8028e000 it wont let me put in letters, does this that i cannot gain more ram