Mobile/Build/Windows Mobile DevSpecificInfo

Device Specific Debugging Information

This page should contain information about specific devices and bugs which have shown themselves on those devices.

This page is NOT in any way a replacement for Bugzilla - it is only a cache of information in a readily accessible form.

If you are debugging on a particular device, please feel free to update the information on that device. However, do not remove other people's comments on a device - only add the information that you do (or do not) see that same issue.

HTC Touch Pro

This device is our current reference platform for developing XULRunner and Fennec Mobile Browser for Windows Mobile.

This device was chosen for it's large RAM and storage availability, as well as its good resolution, touch screen, and expansion card.

This device gets the most testing, and should need the least amount of information cached on this page.

HTC Orbit (XDA)

This is a Windows Mobile 5.0 Professional Device, code named HTC Artimis. This device has a Microsoft Windows Mobile 5.0 for Pocket PC Phone Edition (Magneto) AKU 3.0.0 OS, running on a Texas Instruments OMAP 850 CPU which executes ARMv5TEJ code at 201 MHz. This device has 128 MB ROM and 64 MByte RAM.

One user reports that this device will launch XULRunner, but he never sees any windows -- even when using the simple mybrowser application.

Samsung i900 Omnia

This is a Microsoft Windows Mobile 6.1 Professional device running on a 624MHz Marvell PXA312 processor. It has 128 MB RAM and 256 MB ROM.

Fennec just crashes with the following error log:

EvntType: WinCE501bException AppName : xulrunner.exe AppVer  : 5.2.0.0 AppStamp: 49921b5a ModName : xul.dll ModVer  : 5.0.0.0 ModStamp: 49921b28 Offset  : 00189d8c OwnName : xulrunner.exe OwnVer  : 5.2.0.0 OwnStamp: 49921b5a

The complete device and error logs are uploaded [1].