When the Motorola Droid X volume issues came to light last week, many of you emailed and commented that it wasn’t the only huge issue affecting the device. Instead of issues with the sound, a lot of you were having problems using Exchange on the phone.
Well, just like the volume issues, Motorola has responded to your pleas and they are going to offer you a remedy until Froyo arrives:
First, I want to thank everyone for their help and patience as we worked though this. Much appreciated.
Some Droid X users are experiencing an issue using Exchange 2003 email. Though the email is arriving on the Droid X, no notifications are appearing. A fix for this will be included in the upgrade to Android 2.2 scheduled for deployment by early September.
So, you’ll have to wait a few weeks for it to be fixed, but for now, here’s what you can do:
In the interim, many owners have reported success using Touchdown from NitroDesk, Inc. to manage Exchange email. Touchdown appears to provide email notifications.
Motorola does not support Touchdown in its call centers or guarantee Touchdown. However, we are working with Touchdown to provide Droid X owners Touchdown licenses (supplies permitting) that can be used to get Exchange 2003 email and notifications on the DroidX.
To request a Touchdown license from Motorola, please send an e-mail to level3@mailwc.custhelp.com, and include the following information.
Your email address
Your name (for validation purposes)
Your Droid X cell number (for validation purposes)
Your Droid X DEC and HEX MEID numbers – dial *#06# to find them.
Please indicate what your issue is – for example: “I don’t get notifications when my Exchange email arrives.”
Once these items have been verified, a Touchdown license will be sent to you at the email address you provide. (Supplies permitting.) Our goal is to respond within 24 hours. I’m sorry, but refunds are not available for owners who have already purchased Touchdown.
Boom, problem solved San Francisco.
For more info or to send a tip: admillios@gmail.com
Follow me on Twitter: @admillios
Comments