MyT-Mobile MDA Windows Mobile application list as of 12/20/06

I am adding Windows Live Search (WLS) to my list of MDA applications. This a very useful application, I wrote about it here.

In Storage Memory:

• PhatWare Calligrapher version 8.3 (I could not get version 8.4 to load correctly)
• JetWare Bluetooth HFP Extensions version 1.20
• Stowaway Keyboard and Mouse drivers version 4.51
• Zagat To Go Version 5.0 (guides stored on SD card)
• Microsoft .NET CF 2.0 SP1
• Fizz Software Ltd Fizz Weather version 2.31
• Developer One ScreenSnap version 6.1
• WebIS Pocket Informant 2007 revision 2
• Omega One Battery Pack Pro version 3.03
• Omega One 1-Calc version 2.3.1
• PhatWare Phatpad version 3.0
• SBSH.net PocketBreeze version 5.1.02
• Ilium Software eWallet version 4.1
• SWC Ltd - MultiIE version v4.0-d72
• SOTI Pocket Controller version 5.05
• C. Ghisler & Co. Total Commander version 2.0
• Intent MIDlet manager version 2.0
• Smartskey version .56
• OmaClock version .02 startup with Smartskey at 240MHZ
• Windows Live Search beta version 1.0.2515.28025

On Mini SD card:

• Microsoft Office OneNote Mobile (comes with OneNote 2007) Version 12.0.4518.1010
• RandyRants.com Pocket SharpMT version 3.3
• Microsoft Pocket Streets 2005 version 12.0.07.0700 This is a nice small mapping application, too bad Microsoft has decided to stop development of this product.
• Ilium Software Newsbreak version 1.2
• Gougelet PE XnView Pocket version 1.35
• Sprite Backup version 5.1

Comments

[Robert Reinhardt]

You seem to have a good handle on your T-Mobile MDA--I hope that you don't mind me asking a quick question about Bluetooth DUN functionality on the MDA and other BT devices. I'm having problems getting my MDA to work my new Acura's Acuralink feature, which enables the car to connect to the Internet to send diagnostic info etc. I think it's a problem with the MS Bluetooth stack, because the feature works flawlessly with my Sony T68i and T-Mobile Internet. Any thoughts?

[sskarlatos]

The Microsoft DUN implementation requires a number to dial, a userid and password. Unless the Acura has a way to configure this information it is not going to work.

The number to dial is *99#, the uid/pwd are blank.

Have you tried configuring DUN with an XP workstation?

[Robert Reinhardt]

Thanks for the reply. The Acura has a dial string, which I can modify. I've tried *99# with a blank uid/pwd, to no avail. (That is the default dial string as well in the car setup menu.)

[Stephen Skarlatos]

Here is a GPRS modem command setting that you can try:
AT+CGDCONT=1,"IP","wap.voicestream.com". Depending on the T-Mobile service you may want to try internet2.voicestream.com or internet3.voicestream.com .

I assume that you have been able to pair the Acura and it shows up in your Bluetooth connections.

[Robert Reinhardt]

I'm not able to specify modem init strings with the Acura setup menu. :( I can specify a dialing number, a user name, and a password. I can see the phone's bluetooth light blink when the test first tries to connect, but it just fails. Do you know if there's a way to turn on debug/error messages on the MDA in the WM5 registry?

[Stephen Skarlatos]

I don't believe there is a diag mode in the production BT stack. You might try spaces in the user and password field. It could also be the com port that AcuraLink uses. Windows XP uses COM4 with the MDA. During the pairing and discovery process AcuraLink should determine the available com ports. If you could pair a Windows XP machine with your T68i and see what port it uses. We may be able to change the port on the MDA. I believe you can change the DUN com port in the Windows Mobile registry, I will have to research it.

I also saw that the Acura site shows no support for AcuraLink and the MDA.

[Robert Reinhardt]

Cool, thanks for the info.