debugging bluetooth dialup
 

I am having issues getting bluetooth networking working with my Moto A780 w/ t-mobile. I was using the cheaper t-zones plan (5.99 plan), but am also trying the 19.99 plan.
Where do I find any log messages for bluetooth? The problem I'm having, is I've finally got it to dial out and connect, but after about 10 seconds it disconnects. Although once or twice, it actually connected and held the connection (although there was a bit of latency).
Here's what I've tried:
Phone number: *99# and also *99***1# and *99***2#
APN: wap.voicestream.com (and internet2.voicestream.com now that I've upgraded the data plan).
In the advanced tab, Supplementary AT commands: at+cgdcont=1,"IP","internet2.voicestream.com"
Also, "Use PPP compression:" I tried both checked and unchecked. The couple times that I've gotten it to work, this option was unchecked. But it didn't work a second time.
I've also added the line ":192.168.0.254" to the end of /etc/ppp/options as was suggested in another post.

Now, the phone itself doesn't have any problem connecting, with the APN internet2.voicestream.com. What else can I try? (I've searched the forums, which is where I got the above info from).

Re: debugging bluetooth dialup
 

I think sysklogd is the package to install for logging to be active.

I don't know about your phone, but on my SonyErricsson, I ended up using CID5, i.e. *99***5#. I guess you could try other CIDs if so far you've only tried 1 and 2. What value did you use on the occasion that it worked?

Re: debugging bluetooth dialup
 

I've had it work once using *99***1# and once with *99***2#. It doesn't even connect with 3 or 4.
Also, I'm on an n800 with os2008, but was having the same issues with os2007 (got it work once, then it didn't afterwards).

Re: debugging bluetooth dialup
 

OK. Well, I hope the logs help you out then. You should be able to tell if it fails on connection or establishing the PPP link.

It would be nice if we had off-the-shelf PAN support to avoid this kind of problem, but I guess Nokia knows best ;-)

Re: debugging bluetooth dialup
 

Did you try this ?

Type:Packet Data

Phone Number to dial: *99#

APN: wap.voicestream.com

username:<blank>

password:<blank>

ADVANCED-

Proxy: 216.155.165.50 port:8080

Re: debugging bluetooth dialup
 

Ok, better yet, what command gets run to establish the bluetooth connection? That way I can run it from the command line to see what error gets generated.
BTW, I just got a connection established using #99***2#, but I couldn't replicate this a second time (although again web browsing from the phone works without issue).

Re: debugging bluetooth dialup
 

Yes, I've used those settings when I was on the 5.99 plan, and I got a connection at one point but couldn't repeat it. I'm on the 19.99 plan now, which usese internet2.voicestream.com and no proxy, and I've gotten a connection a couple times, but most of the time it says connected, but drops the connection after 10 seconds (as if it was having an authentication error).

Re: debugging bluetooth dialup
 

I got it to work again, after letting the phone & tablet sit for a while. But when I disconnected, I couldn't get it to reconnect until it sat for another couple hours. So I don't know if it is an issue with the tablet (probably not), phone, or t-mobile. Even after a fresh reboot of phone & tablet, it still doesn't work. My guess is that t-mobile still thinks the session is open on their end and I have to wait for it to reset before I can use it again.. Does this sound plausible?

My other option is to try and establish a point-to-point network connection between the phone and the tablet, then use NAT on the phone to forward internet traffic (the A780 phone runs linux). This always works reliably between my PC and the phone using a usb connection (but I never could get usb dialup networking to work). I just have to figure out how to set up a bluetooth lan connection.

Re: debugging bluetooth dialup
 

How strong would you say your signal is? If it's marginal, I'd say try again in an area with a good signal and see if you connect more consistently.