• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help pdanet not working with 2.01?

martin515 said:
I did follow the instructions but for some reason I get a RFFcomm error when I do it through bluetooth and the app doesnt recognize the fone when I connect it.
Click to expand...

What I got from the newest info on the PDAnet for Android page and then the Mac link is that it's only USB now. I just tried the old bluetooth way and confirmed it does not work and I get the RFcomm error. Try USB. I had no problems using USB.
 
Just DL PDAnet and i have the usb working fine. I have yet figured out a way to use the Bluetooth.

My laptop says that the phone does not support DUN. How did you guys set the BT up?
I am up-to date with all software. Running Xp.
What steps did you use to connect?
I have paired my phone to the laptop. (it says on the laptop that the BT device is paired with the headset service. And on the phone it says laptop is connected to phone audio.)

Set up DUN no username or password and selected BT as modem and also have a PDAnet BT modem in the list. ( i have tried both)

I feel real dumb here i had my moto rocker setup on this same laptop and it did BT or USB no problem.

I feel like i am missing a step somewhere.

Any ideas?
 
I think what's going on is there are seperate capabilities for Apple OS and Windows. Before the Android 2.01 update the only way to tether with PDAnet on a Mac was with Bluetooth. Now its USB only on Mac. Perhaps Bluetooth DUN doesn't work on Windows now, I don't know but I only ever had Bluetooth DUN running on Apple OS.
 
People are saying that they had no problem connected with bluetooth before and that is a lot more convenient than connecting through usb
 
martin515 said:
People are saying that they had no problem connected with bluetooth before and that is a lot more convenient than connecting through usb
Click to expand...

That was my experience too. I finally got an answer from PdaNet saying that the Android 2.01 update broke PdaNet's Bluetooth (at least for Macs, although I can't imagine what difference it would make), and that they are working on getting that going again, but haven't figured it out yet.

Unfortunately, the new Mac USB software isn't working for me either. The install is supposed to create a new network interface, which PdaNet uses when it connects via USB, but it didn't appear in my Network Preferences, and when I try to connect using USB, it says "Fail to find network interface"... What's weird is PdaNet on the Droid says it's connected, but nothing is actually connecting.
 
carlaron said:
That was my experience too. I finally got an answer from PdaNet saying that the Android 2.01 update broke PdaNet's Bluetooth (at least for Macs, although I can't imagine what difference it would make), and that they are working on getting that going again, but haven't figured it out yet.

Unfortunately, the new Mac USB software isn't working for me either. The install is supposed to create a new network interface, which PdaNet uses when it connects via USB, but it didn't appear in my Network Preferences, and when I try to connect using USB, it says "Fail to find network interface"... What's weird is PdaNet on the Droid says it's connected, but nothing is actually connecting.
Click to expand...

I was just able to finally use the tethering successfully. I reinstalled the program and in the network settings I hit the little ad button and select ethernet en4 or en3, then hit aply and go to your fone and hit usb tether then on the task bar clik the pda icon and hit connect. Try it oout
 
martin515 said:
I was just able to finally use the tethering successfully. I reinstalled the program and in the network settings I hit the little ad button and select ethernet en4 or en3, then hit aply and go to your fone and hit usb tether then on the task bar clik the pda icon and hit connect. Try it oout
Click to expand...

I've tried manually adding interfaces in the Network Prefs, but that doesn't help... PdaNet still says it can't find a network interface

When I add one, the choices are AirPort, Ethernet, Bluetooth, and Firewire... I pick Ethernet, then name it something... I've tried to match their screenshot of "Ethernet Adaptor (en2)"... but it doesn't help.

Did you set any particular settings for it, or name it anything specific?
 
carlaron said:
That was my experience too. I finally got an answer from PdaNet saying that the Android 2.01 update broke PdaNet's Bluetooth (at least for Macs, although I can't imagine what difference it would make), and that they are working on getting that going again, but haven't figured it out yet.
Click to expand...

Oddly enough, I've had some sporadic success getting the BlueTooth DUN connection working again... It's very odd. If I create a new BlueTooth DUN network interface, it seems to connect OK, and I can browse and check email, etc... but it seems to close the connection after a few minutes... I can't tell if it's time, or inactivity that triggers the closing.

Then, if I try to restart the connection, it just won't work... But if I create another one, with a new name that I've never used before... that might work... or it might not... it is very unpredictable.

Right now, I'm trying having a ping command from the terminal run in the background as a "keepalive" signal to keep the connection awake as I type this... so far so good after a few minutes
 
OK... I've been connected via Bluetooth DUN for quite a while now and no time out... I even cancelled the ping, and it still stays connected. The next test is to disconnect, then try to reconnect... See you later... I hope.
 
carlaron said:
OK... I've been connected via Bluetooth DUN for quite a while now and no time out... I even cancelled the ping, and it still stays connected. The next test is to disconnect, then try to reconnect... See you later... I hope.
Click to expand...

AW CR@P... Now it won't connect... I keep creating new Bluetooth DUN connections with new names and they won't work... Every time I think I see a pattern, it changes...

There's something to this creating new Bluetooth interfaces, but I can't figure what.
 
OK... This still doesn't make sense. I can sometimes get the BlueTooth DUN to work, but I am now not sure if I can detect ANY pattern at all in when it works and when it doesn't. My previous posts indicate that I got it working by creating a new Bluetooth DUN network interface in Network Prefs, with a new name. I now think that may have been a false clue. It seemed like it worked a few times, but then it didn't.

I have another possible clue, in that I can sometimes get it going using the original Bluetooth DUN interface (deleted all the rest), if I turned on PdaNet as the FIRST app after shutting the phone off an turning it back on... Again, not 100% of the time, but it's something to try.

Eventually, I hope PdaNet gets updated to work right with Android 2.01, but for now, I'm just trying to find a work-around... especially since my cable-modem is on the fritz and won't get fixed for a few days. I am posting this via the Azlink solution mentioned here.

In the mean time, I've gotten "AZLINK" to work. It's another USB tethering solution, but it's not in the Android Market. It's at: azilink - Project Hosting on Google Code

The developer is not especially detailed in his instructions, but it can be made to work.

The first hurdle is downloading and installing the Android developers SDK... I happened to have downloaded it the other day, because I'm interested in programming Android apps, but all you really need out of it is the one utility program "adb".

The next hurdle is that the OpenVPN site he mentions doesn't have a Mac version... luckily, there are several OpenVPN programs out there for Mac, the one I chose was TunnelBlick tunnelblick - Project Hosting on Google Code

Next, the AZLINK OpenVPN configuration file is named aziLink.ovpn, but TunnelBlick doesn't want that file name. You have to re-name it "azlink.conf" and copy it into the Configurations folder for TunnelBlick, located at ~/Library/Application Support/Tunnelblick/Configurations

Once you have the pieces in place, you:
1) start Azlink on the phone and check Service Active
2) run the adb command in the mac Terminal (outlined in the instructions and repeated in the About area of the Droid app itself in case you forget what it is)
3) start TunnelBlick and connect to the VPN defined by the azlink.conf file.
 
You must log in or register to reply here.
Back
Top Bottom