O2 Xda Zinc: More QWERTY, Less Flame

[Nurhisham Hussein]

Originally Posted by bnycastro

can we find out what memory card it uses? hopefully it's SDHC [just saw a 8Gb SDHC card online and it's really tempting! :P]

Based on the information gained from the SDHC debacle with the FSC T830, none of the current processor generation will be able to support SDHC cards at all. We won't see SHDC compatibility until at least 2008, when devices with the next-gen processors are released.

[Nurhisham Hussein]

Originally Posted by bnycastro

can we find out what memory card it uses? hopefully it's SDHC [just saw a 8Gb SDHC card online and it's really tempting! :P]

Based on the information gained from the SDHC debacle with the FSC T830, none of the current processor generation will be able to support SDHC cards at all. We won't see SHDC compatibility until at least 2008, when devices with the next-gen processors are released.

[bnycastro]

Originally Posted by Nurhisham Hussein

Based on the information gained from the SDHC debacle with the FSC T830

what debacle is that? the FSC T830 is on my list of devices to get [to replace my Exec] mainly because it's supposed to be SDHC ready. if it's not too much too ask maybe PM me the link to the story so we don't hijack this thread. thanks in advanced nurisham

[The PocketTV Team]

we just received information that the O2 Xda Zinc (designed by Asus) has a "spurious private messages" firmware bug similar to the one affecting the Motorola Q:

http://www.modaco.com/Motorola-Q-Spurious-...la-t242539.html

once again it shows that MSFT does not have anything to test this issue in their platform test suite, and that major Windows Mobile device manufacturers are still un-aware of this issue.

this firmware bug may affect applications that use private messages (in the range [0x8000 to 0xBFFF]) for inter-thread communications.

other Windows Mobile devices that are known to have this firmware bug include:

- Motorola Q
- Samsung i-600
- Asus P525
- E-Ten M500
- E-Ten E700

We have been unable to contact Asus or O2 to report this bug, but hopefully someone involved with this device will read this, some day.