After upgrading to the latest version of USB Modem (Version 1.5 that now adds support for connection via Bluetooth for Treo 700p), I decided to do a speed test using my regular DSL connection and the two available connection methods for the Treo 700p – Bluetooth and USB. I’ve been using the USB modem connection method and wanted to see if there would be a noticible connection speed difference using Bluetooth instead of USB as the connection method.
These tests were run using a G4 Powerbook running OS X Tiger 10.4.7 and the Palm Treo 700p and USB Modem software version 1.5 connected to Sprint’s EVDO network in St. Louis, Missouri.
||11:27 PM GMT
||~ 550 mi
Using Treo 700p as a USB Modem:
||11:52 PM GMT
||~ 550 mi
EVDO speeds are pretty fast, especially compared to an old-school dialup connection. About half as fast as my DSL line.
Using Treo 700p as a Bluetooth Modem:
||11:55 PM GMT
||~ 550 mi
Using Bluetooth was significantly slower than using USB cable. Nice to be able to connect without any wires though, and still basically fast enough to use. Warning: Nasty Bluetooth Reboot Required Bug When using Bluetooth as the connection method, when the connection gets disconnected or interrupted, you may get a
Disconnecting... message that never stops. Apparently this is a known bug for which there is no good solution. After getting this message the only solution seems to be to reboot your computer, which pretty much stinks. This is NOT the fault of the USB Modem software, I found tons of references to this bug dating back to regular dial-up days.
You can now use Bluetooth along with USB Modem software, and it works, but the OS X bug that requires a reboot to connect again when you use Bluetooth makes it significantly less attractive to use this feature.
I plan to continue using the USB cable connection method since it is significantly faster and does not suffer from the Bluetooth bug above. It also has the bonus feature of charging the phone at the same time.
If anyone has a suggestion for a solution to the Bluetooth disconnecting message bug other than this Applescript (didn’t seem to work for me), please let me know via the comments.