|
Posted by The PocketTV Team on January 16, 2007, 7:59 pm
Please log in for more thread options however in this case, the messages are sent in a range which is explicitely
reserved for private use by the application.
since the OS (that includes the shell and proprietary drivers) on various
devices (Samsung i-600, Motorola Q, and others) send messages in the private
range normally reserved for the inside use by applications (for inter-thread
communication), it is very difficult for application to determine for sure
what range of messages can be safely used for its own inter-thread
communications.
> It's pretty common that these devices broadcast messages without
> registering them properly. Hopefully the companies that the OEMS are
> outsourcing their work to will figure out the right way soon.
>
> So far, HTC, Samsung and Sharp PPC devices for sure do this. Probaly
> others. I suspect we're dealing with dev teams who are still a little in
> the embedded systems mindset - "the device will always be in the state it
> is when we ship it".
>
>
> CV
>
>
> The PocketTV Team wrote:
>> we just confirmed that the Samsung i-600 has the same firmware bug than
>> the Motorola Q, i.e. it sends spurious private messages to the
>> applications.
>>
>> this firmware bug is documented here:
>>
http://www.modaco.com/Motorola-Q-Spurious-private-messages-firmware-bug-confirmed-by-Motorola-t242539.html
>>
>> in the case of the Samsung i-600, the spurious messages are sent when the
>> phone is flipped open or closed. the message sent to all application is
>> 0x000080ca - which is a value reserved for interthread-communications in
>> applications and should NEVER be sent to an application unless it expects
>> this message to be sent.
>>
>> this can cause applications to randomly crash or misbehave when the
>> Samsung i-600 is flipped closed or opened.
>>
>> i think that the Samsung i-600 is also known as the Sprint PCS Vision
>> Smart Device SP-i600 (as we had other reports of this from people using
>> this device).
>>
>> we have received reports that the same firmware bug also affects the Asus
>> P525.
>>
>> it is very important that MSFT makes sure that they tests this in their
>> platform validation tests.
|