search

baljeetverma / android-notifier

Automatically exported from code.google.com/p/android-notifier
0 stars 0 forks source link

paired but not connected #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Using Android Froyo on Motorola Droid.
Wife has iMac that is a beast. Able to "pair"
phone with Mac (get code verify from both
devices ) but unable to "connect."

Original issue reported on code.google.com by bdug...@gmail.com on 9 Sep 2010 at 11:39

GoogleCodeExporter commented 9 years ago 
What do you mean by connect? Do you mean sending test notifications? Which 
client did you install on the mac?

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 4:16

GoogleCodeExporter commented 9 years ago

Original comment by rdamazio@gmail.com on 12 Sep 2010 at 6:33

GoogleCodeExporter commented 9 years ago 
I have the same issue. Both macbook pro and evo say paired but not connected. 
The active bluetooth connection between the two devices in not on. I know the 
macbook only has an active connection when transferring files/data to another 
device. 

Tried sending test notification and nothing. Not sure how to get my 
notification on my MBP.

Original comment by shawn.w...@gmail.com on 17 Sep 2010 at 5:19

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have the same issue. Nexus One with 2.2, netbook running Ubuntu 10.04 
(netbook remix).

In the Bluetooth settings in Android, the laptop is listed as "Paired but not 
connected"

In the Bluetooth preferences in Ubuntu the device is listed but the icon shows 
that it is disconnected. The disconnect button is disabled and there is no 
connect button.

Test notifications do not reach the laptop. I can send files to the phone, but 
the laptop cannot receive files.

The following is the contents of dmesg since turning on Bluetooth on the 
laptop. The "Unexpected continuation frame" errors occur when I try to send a 
test notification from the phone. They occur in groups: 2 immediately after the 
notification is sent and usually, though not always, a third some seconds after 
the notification was sent.

[ 1262.488217] usb 5-1: new full speed USB device using uhci_hcd and address 2
[ 1262.661786] usb 5-1: configuration #1 chosen from 1 choice
[ 1262.856249] Bluetooth: Core ver 2.15
[ 1262.858299] NET: Registered protocol family 31
[ 1262.858306] Bluetooth: HCI device and connection manager initialized
[ 1262.858314] Bluetooth: HCI socket layer initialized
[ 1262.902054] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 1263.144225] usbcore: registered new interface driver btusb
[ 1263.291256] Bluetooth: L2CAP ver 2.14
[ 1263.291263] Bluetooth: L2CAP socket layer initialized
[ 1263.383441] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1263.383453] Bluetooth: BNEP filters: protocol multicast
[ 1263.446335] Bridge firewalling registered
[ 1263.486429] Bluetooth: SCO (Voice Link) ver 0.6
[ 1263.486442] Bluetooth: SCO socket layer initialized
[ 1263.641492] Bluetooth: RFCOMM TTY layer initialized
[ 1263.641505] Bluetooth: RFCOMM socket layer initialized
[ 1263.641511] Bluetooth: RFCOMM ver 1.11
[ 1293.571253] l2cap_recv_acldata: Unexpected continuation frame (len 0)
[ 1293.600248] l2cap_recv_acldata: Unexpected continuation frame (len 0)
[ 1299.899268] l2cap_recv_acldata: Unexpected continuation frame (len 0)
[ 1692.623313] l2cap_recv_acldata: Unexpected continuation frame (len 0)
[ 1693.854318] l2cap_recv_acldata: Unexpected continuation frame (len 0)

Original comment by ryan.ko...@gmail.com on 27 Sep 2010 at 8:02

GoogleCodeExporter commented 9 years ago 
Update: issue appears to be resolved in latest version. Updating to v0.2.8 of 
the app and 0.4.0 of the linux program fixed this.

Original comment by ryan.ko...@gmail.com on 27 Sep 2010 at 8:13

GoogleCodeExporter commented 9 years ago 
Nice :)

Original comment by rdamazio@gmail.com on 27 Sep 2010 at 8:45