Updated 2/25 Unofficial PPCK Build Updates 20954, 210xx, 21015, 21018

[Csquared]

Originally Posted by drellisdee

Diamond KB oem is broken on newer releases so don't use it. Not sure on backlight as my backlight works fine on my vogue using 21015. The sys/xip is good just as always there may be oem conflicts with a new build. Unselect a few and try building again till you get a working one and try to narrow down the OEM that is causing it. Please post any known bad oems with these sys. I know the cambridge BT on Touch pro and possibly BT FTP and BT Print cause Pro roms to hang on splash with 20931 or higher. Can you add your selections.txt as an attachment?

I will rebuild tonight and post results. Im not sure if I still have the txt on the last build.

Do you know of a good working OEM for the diamond keyboard with this build.

[vin255764]

Originally Posted by Csquared

Drellisdee

I built a rom for my Sprint Touch using 21015 build. I had 2 issues and I was not sure if it was the build or my Rom and was hoping you might help. I had used the Diamond keyboard oem in PPCK and after my flash I was unable to type anything on any of the diamond keyboards. They came up but was umable to type. The other thing was the backlight did not work.

Here is a backlight fix.U probably have manila in your user OEM folder,if so,then overwright that dll.Im also attaching txt doc with my selections, it will give u an idea to start with.I can upload my user oem folder if somebody want one,its messed up a little,but works with that selection txt

[Csquared]

Originally Posted by vin255764

Here is a backlight fix.U probably have manila in your user OEM folder,if so,then overwright that dll.Im also attaching txt doc with my selections, it will give u an idea to start with.I can upload my user oem folder if somebody want one,its messed up a little,but works with that selection txt

Thanks Vin. Im not using Manilla, but I did use HTC Util oem.

[gguruusa]

Originally Posted by FormerPalmOS

Anyone know the difference between WMReloc and G'Reloc? Is WMReloc backwards-compatible with earlier builds? What doesn't G'Reloc do that WM6.5 requires?

And is the usage still the same?

1) Create dump directory using selected sys, and OEM
2) G'Reloc.exe -dump -doit
3) Build ROM

If there is a thread elsewhere that is more appropriate for this question, please direct me there.

WMreloc is a replacement for g'reloc. Usage is a little different, but similar. It has it's own self-explanatory usage output.

[FormerPalmOS]

Originally Posted by gguruusa

WMreloc is a replacement for g'reloc. Usage is a little different, but similar. It has it's own self-explanatory usage output.

I figured it was something like this. I see that you can specify VM slot 0 or 1 - but I'm not sure why you would want to - I'm not sure why it would matter. But a log output would be nice - right now to check on G'Reloc I have to dump the resulting ROM to get the memory map and make sure the modules don't overlap the XIP (which they haven't as long as I have the .VM file correct in SYS) and that they leave sufficient room for non-moduled DLLs and EXEs. I've been playing around with turning some of the OEM apps into modules - so-far so-good but haven't tried WM6.5 yet.

Also, will it automagically process all modules in a dump directory like G'Reloc.exe -dump -doit? Or do you have to have something else process the dump directory and call WMReloc.exe for each module? If the latter, I'm sure someone has written a utility to do this (I saw a "small G'Reloc.exe over at XDA that supposedly calls WMReloc.exe - wonder if that is it...?)

[gguruusa]

Originally Posted by FormerPalmOS

right now to check on G'Reloc I have to dump the resulting ROM to get the memory map and make sure the modules don't overlap the XIP (which they haven't as long as I have the .VM file correct in SYS) and that they leave sufficient room for non-moduled DLLs and EXEs.

G'reloc uses .VM to determine where to put stuff, hence you never have an overlap if it's correct.

Also, will it automagically process all modules in a dump directory like G'Reloc.exe -dump -doit? Or do you have to have something else process the dump directory and call WMReloc.exe for each module? If the latter, I'm sure someone has written a utility to do this (I saw a "small G'Reloc.exe over at XDA that supposedly calls WMReloc.exe - wonder if that is it...?)

Yes, WMreloc processes all modules. The "small G'reloc" is a stub replacement that calls WMreloc. It's used to trick apps that want g'reloc into using wmreloc. Of course, there are limitations to using wmreloc that way, so it's better to use WMreloc directly.

[FormerPalmOS]

Originally Posted by gguruusa

Yes, WMreloc processes all modules. The "small G'reloc" is a stub replacement that calls WMreloc. It's used to trick apps that want g'reloc into using wmreloc. Of course, there are limitations to using wmreloc that way, so it's better to use WMreloc directly.

OK - that's good. Am I correct in assuming that if you give a -g [module dir] command line option it processes only that module - otherwise it processes all modules in the current working directory? Is there a command line option like -dump required (g'reloc requires -dump to operate on a dump directory vs. on SYS, OEM and EXT directories individually).

Sorry for the questions - if this is detailed in some other thread, I'm happy to ask there instead.

[MatrixPlasm]

Anyone had any issues with 21015 on Apache or Vogue with Bluetooth ActiveSync?

I currently have 19212 on my Vogue and can ActiveSync via Bluetooth fine, but my wife currently has 20931 on her Apache and lost that ability ... has anyone tried ActiveSyncing via Bluetooth with 21015 on either the Vogue or Appache? If so, does it work?

[FormerPalmOS]

Originally Posted by MatrixPlasm

Anyone had any issues with 21015 on Apache or Vogue with Bluetooth ActiveSync?

I currently have 19212 on my Vogue and can ActiveSync via Bluetooth fine, but my wife currently has 20931 on her Apache and lost that ability ... has anyone tried ActiveSyncing via Bluetooth with 21015 on either the Vogue or Appache? If so, does it work?

FWIW I am using XIP 21015 and SYS 21015 on CDMA HTC Touch Pro (Verizon) and am able to ActiveSync over Bluetooth. The MS SYS files require an OEM BT driver - perhaps that driver may be incompatible with 21015 on Apache. If you could identify the BT hardware in the vogue or TP as the same in the Apache, you could try the BT driver from OEMDRIVERS package on one of those phones.

[cg83]

thanks for the 21015 build. just a few questions:

when typing out a sms the annoying grey box appears with the words. i tried going to the xt9 settings and turning everything off but the box still comes on. is there anyway to turn it off completely without selecting abc in the menu?