I was one who could bluetooth tether with my DroidX (NOT ROOTED!) with my 101. It was wonderful, and worked well when bluetooth GPS-ed as well.
Well, I did upgrade (still w/Verizon) to Samsung Chase. Great phone, but when I when exactly through the same process as the DroidX (which I duplicated with factory reset 101 just to make sure), the Samsung pairs, but does not show up as an eligible device when going through BT setup. The DroidX is still there, but I just can't get the Samsung to show up in the BT tether menus.
It's a sad loss. Anyone have any suggestions?
There is likely no Bluetooth DUN SDP record on the cellphone, probably because Verizon disabled it.
If you have access to a Linux computer with Bluetooth, put the phone in discoverable mode and do:
$ hcitool scan
That will spit out a list of discovered Bluetooth devices and their MAC addresses. Select the relevant MAC address and copy it into a command like this:
$ sdptool browse xx:xx:xx:...
That will spit out all SDP records the phone is advertising. You should see in there (or not) one that is called "Dial-up Networking" or similar- but the name field is actually arbitrary. To identify it for certain, you'd look for an RFCOMM service that has a UUID that is noted as belonging to the standardized DUN service. I am pretty sure that the sdptool knows which that is and would print out a "friendly name" of the known service UUID, but I am not 100% sure on that.