Quote:
Originally Posted by zenkinz this is interesting.
No, I don't have AT&T Q9h (thank godness or what? But at least you get a GPS chip), so that might answer the mystery.
Then again, the availability of Bluetooth PAN profile, is based on the Bluetooth stack drivers, so I imagine the situation is the bluetooth stack available in AT&T Q9h is older and thus needs to be updated.
sorry I can't be of any more help than this.
Here's what I found out on the pros of using ICS over DUN |
Well....
(1) Not an issue since you only have to enter the connection string *99# the very first time you set up the DUN link in Windows. After that it's just hitting the connect button each time you want to start DUN.
(2) I don't think this is an issue since AT&T's 3G (UMTS/WCDMA) network handles simultaneous voice & data.
(3) I don't think this is an issue based on (2).
(4) Nothing to really comment on here.
(5) Not sure about this one.
From reading other posts on other forums about this, I don't think there is a practical difference between PAN and DUN in terms of connecting to the internet, connection speeds, simultaneous voice/data, etc. I think the attraction is that people believe that AT&T doesn't know you are tethering when connected via PAN. I don't know if this is true or not, but it would seem they might be able to tell it was tethering by patterns of data usage and amounts. I don't think the fact that Bluetooth PAN is missing from ICS is a Bluetooth stack issue. I'd bet that AT&T disabled the option somehow specifically to cut down on tethering.