Downloads

For those of you who do not feel like compiling the software yourself, I have provided development builds of the different profiles for Windows Mobile and Windows CE. Note that a typical Windows CE image is customized by the hardware manufactures to only include the software components they need. It is possible that the builds below do not work if the DLL requirements cannot be fullfilled. These builds typically need at least AYGSHELL.DLL, WS2.DLL and WINSOCK.DLL, and that all the required methods are implemented by these DLLs. Note that for the phoneME Advanced Personal Profile builds, the AWT part may not work as expected whenever one of the unimplemented stubs is used.

Default, native DPI and high resolution MIDP stacks

If you are using a device with a VGA resolution (or any other non-96 DPI display) the default builds will do a 96 DPI emulation out of the box. The emulation rescales all fonts and graphics as if your device would have a QVGA resolution. However, the 96 DPI emulation may cause blurry texts on 128 and 131 DPI devices because these dot densities are no multiples of 96 DPI. That is why there are a few alternatives for the phoneME Feature and the phoneME Advanced Dual Stack builds which use the native dot density:

Native DPI: the native dpi build uses the native resolution of the device. This means the higher the DPI of the screen is, the smaller the fonts become. For a 192 DPI device, the fonts and graphics would appear as half the size when emulating 96 DPI.
High Resolution: the high resolution build has all the built-in graphics and fonts resized to twice their original size. This build is recommended if you want to have a crisp text on a high DPI device.

Primary links

Downloads

Default, native DPI and high resolution MIDP stacks

Windows Mobile 6

Windows Mobile 5

Windows Mobile 2003

Pocket PC 2002

Windows CE 5.0

Windows CE 4.2