|
Posted by The PocketTV Team on June 8, 2007, 4:19 pm
Please log in for more thread options we don't have a HTC Hermes unit to test that.
even when we have the device, it is very difficult to figure out who sends
those spurious messages, since there is no information in the message to
identify the thread that posted the message.
in the case of the Motorola Q, the engineering team at Motorola was able to
trace the spurious messages to the driver that handles the speakerphone and
car kit.
it is probably a different situation for each device, unless they originate
from the same OEM (e.g. on the O2 Xda Zinc and Asus, since the O2 Xda Zinc
is made by Asus).
yes, it could be caused by a carrier app, or even by some third-party app
installed on the device where the problem was observed. we'll try to get
more information from the user who reported the issue.
> For any of the devices that do this, have you tracked down who is sending
> them? is it an HTC App? A Carrier app?
>
> Riki
>
>
> The PocketTV Team wrote:
>> we have just been informed that the HTC Hermes has the spurious private
>> messages bug.
>>
>> i.e. the system broadcast to all applications some messages in the range
>> [0x8000, 0xBFFF] normally reserved for application private messages (e.g.
>> inter-thread messages private to the application).
>>
>> in the case of the HTC Hermes, the bogus messages that are broadcasted to
>> applications have number 0x00008101.
>>
>> if an application uses private messages, this bug can cause the
>> application to fail/misbehave/freeze/loose-data randomly.
>>
>> the following devices also have this firmware bug:
>>
>> - Samsung i-600
>> - Asus P525
>> - Asus P535
>> - E-Ten M500
>> - E-Ten M700
>> - O2 Xda Zinc
>> - Motorola Q
>>
>>
>> details of this firmware bug can be found here:
>>
>> http://www.modaco.com/index.php?showtopic=242539&st=0
>
>
> --
> ThemeChanger and AbstractStart for Smartphone :
> http://www.IfIHadADollarForEveryTimeSomeoneSaidThatIWouldHaveMyOwnWebsite.com/
> Windows CE Base Team Blog:
> http://blogs.msdn.com/ce_base/
>
> "You can only examine 10 levels of pushdown, because that's all the
> fingers you have to stick in the listing." -- Anonymous programmer -
> "TOPS-10 Crash Analysis Guide"
| 
XML Sitemap