Skip navigation.
Home

Issue Tracker for Windows Mobile/CE

Here is list of known bugs and issues with links to the forums where the issue may have been reported or confirmed. Some of issues have already been fixed or a workaround is provided, others are unconfirmed or no fix is available.



28. Auto-completion does not work properly

Problem: Auto-completion for a suggested word of N characters inserts the first character N times, rather than the full word
Status: Confirmed
Fix: None yet
Forum links:


27. VM crashes with exception after dragging pointer over to the SIP button

Problem: If you drag the pointer towards and over the SIP button with the latter on top of an AWT frame, the VM crashes with an
exception 0xc0000005 (STATUS_ACCESS_VIOLATION).
Status: Confirmed
Fix: None yet
Forum links:


26. DateEditor and StringItem button widgets don't work properly [WORKAROUND]

Problem: Using the stylus to press a StringItem button does not call the default command when set. You need to use
the keypad to do this. A similar problem occurs when selecting a date with the date editor widget. This might have to do with adding
drag support in svn rev 17582 and 17670.
Status: Confirmed
Fix: Disable dragging support as it does not work well for capacitive touch screen devices without stylus anyway.
Forum links:

  • None


25. Fatal crash on phoneME Feature [FIXED]

Problem: The VM crashes when you touch the bottom of the menu above the right soft key.
Status: Confirmed
Fix: Fixed the index out of bounds exception by first checking the range of the index in the menu commands array.
Forum links:


24. Russian symbols support

Problem: Some fonts and cyrillic symbols are not displayed correctly. This is because fonts are built into the VM and
only a fixed subset is included, not all unicode characters.
Some fonts and cyrillic symbols are indeed displayed correctly. This is because fonts are built into the VM and only a limited subset is included (e.g. the first 127 ASCII characters).
Status: Confirmed
Fix: None yet
Forum links:


23. Virtual keyboard issues

Problem: Some people want to have the virtual keyboard pop up as soon as you enter a text field.
This may be tricky as we need to check whether the device has a real keyboard or not
Status: Confirmed
Fix: None yet
Forum links:


22. AWT Menu with many entries does not work properly

Problem: An AWT Menu in Personal Profile with lots of entries does not behave as it should. For some reason, the
11th MenuItem calls a native Windows Mobile application. Perhaps the window message is mapped on the unique identifier
of a native application
Status: Confirmed
Fix: None yet
Forum links:


21. Get IMEI number of windows mobile by using System.getproperty(); [FIXED]

Problem: This is feature request to get the IMEI number. Not sure yet which WinCE APIs one can use to get this number
Status: Confirmed
Fix: You can get the IMEI number by calling System.getproperty("IMEI");
Forum links:


20. Recordstore corruption in dual stack

Problem: The RMS recordstores to store data appear to suffer from corruption
Status: Unconfirmed
Fix: None yet
Forum links:


19. MIDlet-Data-Size not working

Problem: Changing the JAD property MIDlet-Data-Size to avoid RecordStoreFullException does not work
Status: Unconfirmed
Fix: None yet
Forum links:


18. Updating a midlet fails

Problem: Updating a midlet seams to fails. Perhaps there is something odd with the urls to the jad/jar midlet files?
Status: Unconfirmed
Fix: None yet
Forum links:


17. Certificate issue when installing OTA

Problem: Installing a signed midlet OTA fails because we do not have the required permissions.
Status: Unconfirmed
Fix: None yet
Forum links:


16. Random JIT crashes on Windows Mobile 6.1 [FIXED]

Problem: The phoneME Advanced builds sometimes crash on a Windows Mobile 6.1 device. The problem does not occur when JIT is disabled
Status: Confirmed
Fix: Disable code cache to reside in read/write/execute segment of the executable
Forum links:


15. Error triggers Microsoft feedback notice [WONT FIX]

Problem: Some unknown error with phoneME Advanced seems to trigger a popup on a Windows Mobile 6.1 device that asks you to send feedback about the problem back to Microsoft. It is currently unclear when and why this occurs, and why the problem cannot be reproduced on an emulator
Status: Confirmed
Fix: This popup appears a.o. after a segmentation fault or other errors (e.g. accessing fields of a null object). The correct solution is to fix the original programming mistake that causes the fault. We wont fix the bug by hiding the popup.
Forum links:

  • None


14. phoneME Advanced - Personal Profile: Menus [FIXED]

Problem:There were some issues with the AWT menus of pMEA Personal Profile on Windows Mobile 2005 and higher. On these devices a dummy menu was shown that should have been replaced with the one of the application. The problem occured even when running binaries for Pocket PC 2003.
Status: Confirmed, and fixed (except for pure WinCE devices)
Fix: The cause of this problem were several Window messages to replace a submenu that no longer work on WM5 and higher. A workaround was implemented but the visual result is slightly different.
The screenshots below show the DemoFrame test application. This application defines a menu bar that adds a menu with the caption "Menu". This menu contains the "Graphics", "Font", "Event", etc menu items. On WM5 and higher, you will notice an extra menu "Application" that holds the original AWT menu.

On Windows Mobile 2003

On Windows Mobile 5
   

Forum links:

  • None


13. UnsatisfiedLinkError with JNI

Problem: From development build b92 on, the pMEA builds are having problems with loading libraries through JNI. This problem seems to be related to the fact that some classes have been moved from btclasses.zip to personal.jar. It appears to be a general problem that occurs on all platforms as for linux builds some of the classes have been moved as well.
Status: Confirmed
Fix: None
Forum links:


12. Stroke width ignored in Graphics2D.drawPolygon()

Problem: The stroke width is ignored in the Graphics2D.drawPolygon() drawing method. This is illustrated by the video in the forum at the first link. It is currently not clear whether this is a WinCE only problem that needs to be solved in the native backend of the AWT peers, or a
more general problem that occurs on all platforms.
Status: Unconfirmed
Fix: None
Forum links:


11. Setting the focus to a Frame [FIXED]

Problem: AWT applications with multiple Frames may want to shift the focus programmatically from one frame to another. The two most appropriate methods to do this are requestFocus() and toFront(). However, these methods do not seem to work correctly, or behave differently compared to other Java VMs. For some, toFront() and requestFocus() do the same. Some do and others do not assign focus when calling Frame.toFront(). For Frame.requestFocus(), some do and others do not bring the window to the front when assigning the focus.
Status: Confirmed, and fixed.
Fix: The method Frame.toFront() is able to get a Frame to the front and assign it the focus. The Frame.requestFocus() previously did not have any effect, but now has the same implementation as the Frame.toFront() method.
Forum links:

  • None


10. Frame and Dialog decorations [FIXED]

Problem: AWT applications have two title bars: one in the window decoration, and another in the system task bar. For both java.awt.Frame and java.awt.Dialog: the setUndecorated(boolean) method should be used to enable/disable this decoration. When decoration is disabled, a user cannot drag the frame or dialog to another position.
Status: Confirmed, and fixed.
Fix: The window decoration of a Frame is disabled by default, and for a Dialog enabled by default. You can change the decoration by calling setUndecorated() in the constructor in the window.
Forum links:


9. Some available serial ports are not listed [WORKAROUND]

Problem: You cannot connect to a com port that is known to exist (say COM5:). System.getProperty("microedition.commports") tells us that only port COM0 is available. The cause of this problem is the following line in cdc/src/win32/javavm/runtime/java_props_md.c: sprops->commports = "com0";
Status: Confirmed, but only a workaround
Fix: Use a WinCE implementation of RXTX to access the serial ports..
Forum links:


8. Options not visible in awt.Choice widget [WORKAROUND]

Problem: The entries are not visible in the drop down part of the Choice widget. This could be a font size or a widget resizing issue. Most likely, the problem occurs with devices other than a 96 DPI display. In that case, all widget sizes and positions may need to be scaled.
Status: Confirmed, fix does not work on WM2003
Fix: Reimplement AwtChoice::GetDropDownHeight() to take into account the DPI of the screen.
Forum links:


7. GameCanvas not working in Dual Stack build [FIXED]

Problem: There is repainting issue for midlets using the GameCanvas on top of a dual stack build of pMEA. The problem does not occur on phoneME Feature and repainting with a regular Canvas seems to work fine too. GameCanvas works for the demo application of MicroEmulator, but it fails for the test example on the forum. Game elements jump around instead of scrolling smoothly. It appears old buffers are being blitted to the screen.
Status: Confirmed, and fixed
Fix: Don't use DirectDraw blitting code
Forum links:


6. Fullscreen/maximized AWT Frames [FIXED]

Problem: Some people want to run applications in full screen and hide the top task bar as well as the bottom bar with the software input panel (SIP). Also, application windows do not use the whole screen area by default.
Status: Confirmed, but no real fix
Fix: We override in the VM the size and position of a window so that it matches the working area of the screen. Note that it breaks window resizing calls (e.g. setBounds()) within the application. We do not hide the top taskbar and the bottom SIP bar, because devices without a physical keyboard may not be able to use the virtual keyboard. Moreover, you cannot close an weirdly behaving application either if the top bar is hidden.
Forum links:


5. Transparent PNG images [WORKAROUND]

Problem: The png image loaders does not process the alpha channel of png properly. The native Windows Mobile routines appear to only support 1-bit alpha blending (verified with a transparent png on IE/Windows Mobile).
Status: Confirmed, but only a workaround
Fix: Only a workaround, by doing the alpha blending in the application itself. Windows Mobile 5 provides the AlphaBlend method call, but it appears that not all devices support it. We can implement our own blending algorithm, but there is a serious performance penalty if we have to do that purely in software (without hardware acceleration support).
Forum links:


4. Exception c0000005 (STATUS_ACCESS_VIOLATION) [WORKAROUND]

Problem: This exception has been reported on Windows Mobile 5 and 6, but also on a Windows CE 5 emulator. The exception can be reproduced by using the virtual keyboard to fill in a text field. AwtToolkit::PreProcessMsg(msg) in PPCToolkit.cpp seems to be the culprit.
Status: Confirmed, but only a workaround
Fix: Disable preprocessing by the target component (p->PreProcessMsg(msg)).
Forum links:


3. Granularity System.currentTimeMillis() [FIXED]

Problem: The granularity of the current time is in seconds and not in msec. This is a software/hardware limitiation of the OS and also due to the workaround for the bug reported in "1. Accuracy current time".
Status: Confirmed, and fixed
Fix: Use a combination of the hardware clock and tick counter. We use the old approach of getting msec granularity by computing the current time in milliseconds using a base time (vm startup time) and an offset (tick counter). If the value based on the tick counter differs more than a second from the current hardware clock, then the device quite likely went in suspend mode for a while. In that case, we recompute the base time so that the tick counter offset returns the correct time again.
Forum links:


2. awt.Frame setMenuBar does not work [FIXED]

Problem: The menu bar does not work properly on Windows Mobile 5 and higher. The application shows a dummy menu. Apparently, the menu handling code that works fine on Windows Mobile 2003 no longer works on WM5.
Status: Confirmed, and fixed
Fix: The VM now checks on which WinCE version it runs and uses different menu handling code when running on WM5 or higher.
Forum links:


1. Accuracy current time [FIXED]

Problem: The current time is not accurate when a device resumes from suspend mode while an application is still running. The current time is based on the hardware clock value when the VM started and a WinCE tick counter used as an offset to compute the current time in msec. The accuracy problem is caused by the fact that the tick counter continues with the value where it left off before suspending. This means that the current time is not computed correctly as it does not take into account the time passed while in suspend mode.
Status: Confirmed, and fixed
Fix: Never use the tick counter, but use the hardware clock to get the current time instead
Forum links: