Dell Axim users say: Enough is enough. Fix WM5!

Last month I was extremely frustrated with the problems that exist in my Dell Axim’s (x51v/x51) Bluetooth implementation. The problem centered around Dell opting not to use a third-party Bluetooth stack (i.e. Widcomm) in its Windows Mobile 5 products like it’s competitors but instead sticking with the meager Microsoft stack that lacks the most basic profiles users have come to expect. This made using a Bluetooth headset impossible, for example. The worst part is that Dell’s older x50v and x50 actually had a third-party Bluetooth stack in WM2003SE leaving Dell’s current flagship models with less functionality than the ones they replace. Although Dell did release ROM version A06 as an update in January 2006, it fixed none of the problems I have been hampering usability.

A quick search through my web server logs and general postings on Dell’s Forums and Aximsite’s Forums show that this problem is a widespread issue. After Dell has repeatedly ignored requests from the Axim community for answers, Chris (of Aximsite fame) decided to create an online petition that he posted in a forum message. It is our hope to not only get some answers from Dell but also a fix. If you have a Dell x50/x50v that is upgraded to WM5 or a x51/x51v (native WM5) user that has had any problems (partial list below), then please consider signing this petition.

Just for reference I have taken a few of problems listed by users at Aximsite that are occurring in WM5.

Originally Posted by enquerir

1. The unit gets hot even when power-off (before the “Fake Server Trick”).
2. Cannot choose manual sync (without “Fake Server Trick”).
3. PIE cannot browse javascript/jscript enabled server (Win CE 3.0 can).

Originally Posted by Lofty

4. Lack of Bluetooth Profiles
5. Bluetooth connection manger
6. Very sluggish performance
7. Disappearing memory cards
8. Battery drain issues
9. VGA Out doesn’t work
10. Backup Utility
11. Software Compatibility
12. Available Memory
13. GAPI performance
14. Can’t Use As Mass Storage Device

Originally Posted by jdepew

15. Frequent Memory Errors on power-on requiring Contact Button push
16. Many apps crash before start up - See Opera Browser which actually uses the VGA rez
17. White screen on dock if you don’t turn it on first requiring a hard reset
18. Ridiculously slow performance.
19. Poor implementation of WPA Wireless Security - no AES support, also will not connect using TKIP to APs that implement WPA TKIP+AES. No WPA2 support. At least include the most recent copy of Funk if you’re not going to give us a complete wireless solution.

If you are having any of these problems, members of the Aximsite community forums have temporarily fixed some through of these through clever patches/band-aids. However, the underlying problem is with Dell and these items need to be fixed. I’m hoping Dell listens to it’s customers by fixing the problems we are complaining about instead of giving us the usual “an update will be out in a week or two” line and not following through. I’m also expecting Dell to release AKU 2.0 which should fix our Bluetooth profile problems (already provided to OEMs) and including the Messaging and Security Feature Pack for Push Email. Until this is all fixed, I do not recommend anyone to buy any of Dell’s Axims equipped with Windows Mobile 5 (WM5). Asus, HP and others are far better choices for anyone in the market for a WM5 equipped PDA.

February 16, 2006 | Filed Under Tech/Gadgets 

Comments

2 Responses to “Dell Axim users say: Enough is enough. Fix WM5!”

  1. danno on October 23rd, 2006 11:21 am

    19. Poor implementation of WPA Wireless Security - no AES support, also will not connect using TKIP to APs that implement WPA TKIP AES. No WPA2 support. At least include the most recent copy of Funk if you’re not going to give us a complete wireless solution.

    Just as an FYI the Odyssey Client will support WPA2/wAES. It is likley the driver that is the problem. As many of these drivers are non-standard on WM5 and CE5. If you can do WPA wTKIP then you are pretty well of considering a lot of 3rd party supplicants can’t recognize the adaptor or should I say the adaptor does nto allow for 3rd party supplicants.

  2. Frank Hunter on October 25th, 2006 12:32 pm

    Same problems have been hammering the Mio handheld community !

    I am extremely frustrated to see that Microsoft has stripped almost all functionality from it’s WM5 BT implementation. Also the poor WPA implementation is a HEADACHE being unable to connect to Wifi AP’s using WPA-TKIP/AES and no WPA2 support, but I don’t want to downgrade security on my network just for connecting a couple of handheld devices !

    Mio is not supporting it’s community by upgrading it’s ROM’s and fixing the BT issues, nor is Mickey$oft is NOT doing anything to improve the situation.

    Handheld devices are a multimillion dollar business, but the only thing thes companies are interested in in developing the next gadget i.o properly supporting the products they have put into the marketplace !

    Pathetic !!!!!!!!!!!