The "Motorola Q" is not the only Windows Mobile device that sends spurious
private messages (in the range [0x8000 to 0xBFFF] to applications.
(See
http://www.modaco.com/Motorola-Q-Spurious-private-messages-firmware-bug-confirmed-by-Motorola-t242539.html
and see discussion in the newsgroup:
http://groups.google.com/group/microsoft.public.smartphone.developer/browse_frm/thread/411c9e3b4e5be8f5/cc78007c7193d4f8?tvc=1#cc78007c7193d4f8 )
We just discovered a similar bug on the "Torq P100" aka "E-TEN M500" Pocket
PC!
The device where the bug was observed is a E-TEN M500. On this device,
apparently all running applications receive a message 0x8017 with lParam and
wParam set to 0 each time the user opens the Contacts application.
Our latest version of PocketTV (1.2.14) catches those spurious messages and
displays an error message in a pop-up, and the problem was reported today by
a E-TEN M500 user in India.
So clearly this indicates that MSFT has no platform test to check that the
platform does not send spurious messages to running applications. This is a
pretty serious testing issue that MSFT should address, since at least two
devices have that bug!
And again, all applications that use private messages in the range [0x8000
to 0xBFFF] for inter-thread communications should be aware of the issue, and
work around it on the devices that have the bug.