Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bluetooth notifications not delivered #3

Open
GoogleCodeExporter opened this issue Apr 16, 2015 · 187 comments
Open

Bluetooth notifications not delivered #3

GoogleCodeExporter opened this issue Apr 16, 2015 · 187 comments
Labels
auto-migrated Component-Communication OpSys-Android Priority-Critical Stability Type-Defect

Comments

@GoogleCodeExporter
Copy link 

The Android app doesn't seem to be able to send Bluetooth notifications on a 
Nexus One.

The phone is paired with just one computer, and bluetooth works in general.  
(E.g., I can transfer files with OBEX.)  PacketLogger doesn't show any 
bluetooth 
traffic from the phone when I send a test notification, so I'm pretty sure this 
is 
a bug on the handset side, not the computer side.

Tested on a Nexus One running Android 2.1 (build ERD79).  On the computer 
side, I tested with both a Mac Mini (Macmini2,1) running 10.5.8 and a Mac 
Book Pro (MacBookPro5,4) running 10.5.8.

Original issue reported on code.google.com by satw...@disjoint.net on 28 Jan 2010 at 9:08
@GoogleCodeExporter
Copy link
Author 

So apparently this is an issue with having multiple bluetooth devices paired. 
I'm adding 
bluetooth device selection soon, but I'm attaching your patch for review in the 
meantime.

Original comment by rdamazio@gmail.com on 2 Feb 2010 at 2:31

  • Changed state: Accepted
  • Added labels: OpSys-Android

Attachments:

@GoogleCodeExporter
Copy link
Author 

Patch reviewed and appears to work in my device, submitted as r67

Original comment by rdamazio@gmail.com on 2 Feb 2010 at 2:41

@GoogleCodeExporter
Copy link
Author 

r68 adds bluetooth target device selection.
r72 adds a possible regression - if lots of notifications are sent very quickly 
(unlikely), 
some of them may fail.

Please let me know if the latest version works on the N1.

Original comment by rdamazio@gmail.com on 7 Feb 2010 at 12:35

@GoogleCodeExporter
Copy link
Author 

Apparently r72 introduced a bug which breaks all delayed notifications. 
Preparing 
another fix.

Original comment by rdamazio@gmail.com on 18 Feb 2010 at 12:29

@GoogleCodeExporter
Copy link
Author 

Maybe, just maybe, r83 will fix what you're experiencing. Please update from 
the market 
and let me know.

Original comment by rdamazio@gmail.com on 22 Feb 2010 at 1:59

@GoogleCodeExporter
Copy link
Author 

I have a motorola droid running 2.0.1 and bugless beast rom 1.1 everything 
seems to connect fine to my mac 
mini. i run test notification for pairing with mac app. it finds device fine. i 
have growl running. no notifications 
display though. please help.

Original comment by lunacy...@gmail.com on 12 Mar 2010 at 10:50

@GoogleCodeExporter
Copy link
Author 

lunacyent, can you paste or attach the log output of the mac application here, 
after a 
notification is received (but not displayed)? You can find it by running 
Applications > 
Utilites > Console, then searching for MacDroidNotifier.

Do test notifications also not display?

Original comment by rdamazio@gmail.com on 15 Mar 2010 at 3:14

@GoogleCodeExporter
Copy link
Author 

Installed from market and from apk here - nexus one owner also reports no 
receipt of
bluetooth notifications. Wifi to specific IP, fine.

Original comment by gavin.co...@gmail.com on 24 Mar 2010 at 4:53

@GoogleCodeExporter
Copy link
Author 

Test notifications and regular notifications both are not received (tho phone 
reports
they are sent)

Original comment by gavin.co...@gmail.com on 24 Mar 2010 at 7:52

@GoogleCodeExporter
Copy link
Author 

I still haven't been able to reproduce this, even on the Nexus One - could you 
attach 
or paste the output of the android log after sending a (real or test) 
notification this 
way?
You can get the log by installing an app called alogcat from the market, which 
allows 
you to e-mail it.

Are you using any other bluetooth devices, like a headset?

(I'm also assuming you checked the basics - that bluetooth is enabled, that the 
devices are paired, etc.)

Original comment by rdamazio@gmail.com on 24 Mar 2010 at 8:10

@GoogleCodeExporter
Copy link
Author 

Raising the priority since more people are reporting the issue.

Original comment by rdamazio@gmail.com on 24 Mar 2010 at 8:11

  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author 

Bruno has a Nexus One and was able to reproduce it. He has kindly volunteered 
to 
investigate and fix the problem.

Original comment by rdamazio@gmail.com on 25 Mar 2010 at 2:28

@GoogleCodeExporter
Copy link
Author 

We just tried multiple times with the Nexus One, both with the current and a 
future version of Android, and we're 
still unable to reproduce. Can someone provide a log output?

Original comment by rdamazio@gmail.com on 30 Mar 2010 at 8:09

@GoogleCodeExporter
Copy link
Author 

Ping? Any logs?

Original comment by rdamazio@gmail.com on 7 Apr 2010 at 6:05

  • Added labels: Component-Communication, Stability

@GoogleCodeExporter
Copy link
Author 

I have the exact same issue being reported here. Here are the relevant logs. No 
logs
are being generated when I send a test notification. However in the list of 
bluetooth
devices in System Preferences -> Bluetooth, the connection status goes from red 
to
green for my Nexus One whenever I send a test notification. This probably means 
the
test notification reaches the mac, but the desktop app fails to receive the 
notification.

4/7/10 10:56:51 PM MacDroidNotifier[2525] Saving preferences 
4/7/10 10:56:51 PM MacDroidNotifier[2525] Pairing set to required but no devices
paired, switching to not required. 
4/7/10 10:56:51 PM MacDroidNotifier[2525] Pairing set to required but no devices
paired, switching to not required. 
4/7/10 10:57:31 PM MacDroidNotifier[2640] started listening for WiFi 
notifications 
4/7/10 10:57:31 PM MacDroidNotifier[2640] Started listening for Bluetooth 
notifications

Original comment by krishn...@gmail.com on 7 Apr 2010 at 5:35

@GoogleCodeExporter
Copy link
Author 

From Console.app:
4/13/10 4:11:03 PM MacDroidNotifier[46560] started listening for WiFi 
notifications 
4/13/10 4:11:05 PM MacDroidNotifier[46560] Started listening for Bluetooth 
notifications 

Attached is the droid log grepped for remotenotifier|bluetooth, let me know if 
this
isn't enough of the log.

Original comment by Matthew....@gmail.com on 13 Apr 2010 at 11:31

Attachments:

@GoogleCodeExporter
Copy link
Author 

Since I can't reproduce this, I'm taking a guess at what the problem may be - 
can one of you test the attached 
APK and see if it solves the problem?

Thanks

Original comment by rdamazio@gmail.com on 14 Apr 2010 at 2:12

Attachments:

@GoogleCodeExporter
Copy link
Author 

Works :) Thanks!

Original comment by gavin.co...@gmail.com on 14 Apr 2010 at 7:08

@GoogleCodeExporter
Copy link
Author 

Weird.  Downloaded it and it still doesn't work for me.  I'll uninstall and
re-install instead of doing an update/replace.

Original comment by tchentc...@gmail.com on 14 Apr 2010 at 8:05

@GoogleCodeExporter
Copy link
Author 

What this new binary does it just try again (up to 10 times) if sending the 
notification fails.

Original comment by rdamazio@gmail.com on 14 Apr 2010 at 9:21

@GoogleCodeExporter
Copy link
Author 

Does this app generate a log file I can drop on here for your review?

Original comment by tchentc...@gmail.com on 14 Apr 2010 at 9:51

@GoogleCodeExporter
Copy link
Author 

Yes it does. To get the log you have to use an app such as alogcat (available 
from the market).

Original comment by rdamazio@gmail.com on 14 Apr 2010 at 11:31

@GoogleCodeExporter
Copy link
Author 

[deleted comment]

@GoogleCodeExporter
Copy link
Author 

Same here with moto droid user using a custom rom. Wifi works fine though.

Original comment by ekimia1987@gmail.com on 28 Apr 2010 at 8:36

@GoogleCodeExporter
Copy link
Author 

Another confirmation of the issue using an HTC Evo.  Looking for a solution. 
Hoping for a fix.

Original comment by joo...@gmail.com on 2 Mar 2011 at 4:59

@GoogleCodeExporter
Copy link
Author 

Notifications work with UDP/wifi, not with Bluetooth.  Have tried both native 
mac client and multiplatform with same result.  Get "An error occurred while 
receiving bluetooth notification." message on mac client when receiving test 
notification.

2011-03-07 18:21:00,770 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(2) 
[0xe00002cd])
2011-03-07 18:21:00,874 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(2) 
[0xe00002cd]
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2011-03-07 18:21:00,874 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection


2011-03-07 18:14:10,474 DEBUG [bluetooth] - Java 1.4+ detected: 1.6.0_22; Java 
HotSpot(TM) 64-Bit Server VM; Apple Inc.
Samsung Galaxy S i9000m Android 2.2
MacBookPro OSX 10.6.6

Original comment by AiB...@gmail.com on 8 Mar 2011 at 2:23

@GoogleCodeExporter
Copy link
Author 

[deleted comment]

@GoogleCodeExporter
Copy link
Author 

Here's my contribution to this mess; Android 2.2.1 on Samsung Galaxy S ... OSX 
10.6.7 ... AND 0.5.1 x86_64 (Also tried with Mac 0.2.9) ... apk 0.2.8

2011-03-25 05:54:50,609 INFO [ApplicationImpl] - Starting SWT
2011-03-25 05:54:51,233 INFO [ApplicationImpl] - Showing tray icon
2011-03-25 05:54:51,295 DEBUG [ServiceServerImpl] - Starting service server on 
port [10700]
2011-03-25 05:54:51,305 DEBUG [InetAddresses] - Looking for local address
2011-03-25 05:54:51,313 DEBUG [InetAddresses] - Local address found
2011-03-25 05:54:51,329 INFO [ApplicationImpl] - Starting [Growl] broadcaster
2011-03-25 05:54:51,621 INFO [ApplicationImpl] - Starting [bluetooth] receiver
2011-03-25 05:54:51,635 DEBUG [bluetooth] - Java 1.4+ detected: 1.6.0_24; Java 
HotSpot(TM) 64-Bit Server VM; Apple Inc.
2011-03-25 05:54:51,643 DEBUG [bluetooth] - Use stack ClassLoader
2011-03-25 05:54:51,644 DEBUG [bluetooth] - set dll dir 
/var/folders/br/brDN3Ht7E-uwBhO-jyanX++++TI/-Tmp-/bluecove_jmvermil_0
2011-03-25 05:54:51,696 DEBUG [bluetooth] - Library loaded from 
/var/folders/br/brDN3Ht7E-uwBhO-jyanX++++TI/-Tmp-/bluecove_jmvermil_0/libbluecov
e.jnilib
2011-03-25 05:54:51,697 DEBUG [bluetooth] - BluetoothStack selected mac
2011-03-25 05:54:51,698 DEBUG [bluetooth] - nativeDebugCallback ON
2011-03-25 05:54:51,698 DEBUG [bluetooth] - 
getLocalDeviceSupportedSoftwareVersion
2011-03-25 05:54:51,719 DEBUG [bluetooth] - localDeviceSupportedSoftwareVersion 
20000
2011-03-25 05:54:51,722 DEBUG [bluetooth] - isLocalDeviceFeatureParkMode
2011-03-25 05:54:51,963 DEBUG [bluetooth] - getLocalDeviceBluetoothAddress
2011-03-25 05:54:51,979 INFO [ApplicationImpl] - Removing from startup
2011-03-25 05:54:51,979 DEBUG [bluetooth] - open using BlueCove 
javax.microedition.io.Connector
2011-03-25 05:54:51,979 DEBUG [bluetooth] - connecting 
btspp://localhost:7674047e6e474bf0831f209e3f9dd23f;name=AndroidNotifierService;a
uthenticate=true
2011-03-25 05:54:51,986 DEBUG [bluetooth] - isLocalDevicePowerOn
2011-03-25 05:54:52,011 DEBUG [bluetooth] - RFCOMM server created, ChannelID 4
2011-03-25 05:54:52,017 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2011-03-25 05:59:10,624 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(2) 
[0xe00002cd])
2011-03-25 05:59:10,796 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(2) 
[0xe00002cd]
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2011-03-25 05:59:10,797 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection

Original comment by sl...@theoriginals.in on 25 Mar 2011 at 10:03

@GoogleCodeExporter
Copy link
Author 

Same problem here, I have a SE Xperia mini pro with android 2.2.1, wifi 
notification working fine. Bluetooth with the same symptoms.

Original comment by willy...@gmail.com on 30 Mar 2011 at 3:41

@GoogleCodeExporter
Copy link
Author 

I have a Motorola Milestone with Froyo 2.2
Issues which I've got the same with #139 and #144. When I tried to send test 
message I got the first. Sometimes after starting of app I can see notification 
about call. All the following notifications is not showing

Original comment by rvandr...@gmail.com on 5 Apr 2011 at 11:45

@GoogleCodeExporter
Copy link
Author 

DroidX running 2.2. I can pair with my laptop (Win7-64bit) via BT, and can 
transfer files back and forth, stream media etc, but for some reason the 
desktop client (0.5.1) doesnt detect my BT stack? Searching this project 
continually brings me to this thread, but this thread seems to be about BT 
notifications. I havent even made it that far though... Am I missing something 
obvious?


2011-04-18 13:41:50,454 INFO [ApplicationImpl] - Starting [bluetooth] receiver
2011-04-18 13:41:50,455 DEBUG [bluetooth] - bind error [10050] A socket 
operation encountered a dead network.
2011-04-18 13:41:50,456 DEBUG [bluetooth] - BluetoothStack detected 0
2011-04-18 13:41:50,456 ERROR [bluetooth] - BluetoothStack not detected
2011-04-18 13:41:50,456 ERROR [ApplicationImpl] - Error starting [bluetooth] 
receiver
java.lang.IllegalStateException: Bluetooth not detected, disabling it.
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver.doStart(BluetoothNotificationReceiver.java:58)
    at com.notifier.desktop.app.AbstractLifecycle.start(AbstractLifecycle.java:36)
    at com.notifier.desktop.app.ApplicationImpl.startLifecycle(ApplicationImpl.java:256)
    at com.notifier.desktop.app.ApplicationImpl.adjustLifecycle(ApplicationImpl.java:310)
    at com.notifier.desktop.app.ApplicationImpl.adjustBluetoothReceiver(ApplicationImpl.java:143)
    at com.notifier.desktop.view.PreferencesDialog$7$1.run(PreferencesDialog.java:320)
    at java.lang.Thread.run(Unknown Source)
Caused by: javax.bluetooth.BluetoothStateException: BluetoothStack not detected
    at com.intel.bluetooth.BlueCoveImpl.detectStack(BlueCoveImpl.java:496)
    at com.intel.bluetooth.BlueCoveImpl.access$500(BlueCoveImpl.java:69)
    at com.intel.bluetooth.BlueCoveImpl$1.run(BlueCoveImpl.java:1044)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.intel.bluetooth.BlueCoveImpl.detectStackPrivileged(BlueCoveImpl.java:1042)
    at com.intel.bluetooth.BlueCoveImpl.getBluetoothStack(BlueCoveImpl.java:1035)
    at javax.bluetooth.LocalDevice.getLocalDeviceInstance(LocalDevice.java:75)
    at javax.bluetooth.LocalDevice.getLocalDevice(LocalDevice.java:95)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver.doStart(BluetoothNotificationReceiver.java:54)

Original comment by kcl...@staff.gwi.net on 18 Apr 2011 at 5:50

@GoogleCodeExporter
Copy link
Author 

I get the error message below in the debug log.

I am using bluetooth on HTC Desire GSM
I get the message from the PC client that
"An error occured while receiving bluetooth notification".
Is this also the famous issue 3???
If additional Info is needed, please request what info you need.

2011-04-20 11:29:50,729 DEBUG [bluetooth] - rfs(1) rf(2) RFCOMM server waits 
for connection
2011-04-20 12:21:14,428 DEBUG [bluetooth] - rfs(1) rf(2) RFCOMM server 
connection made
2011-04-20 12:21:14,444 DEBUG [bluetooth] - new RemoteDevice 38E7D8C32554
2011-04-20 12:21:14,444 DEBUG [bluetooth] - new devicesCashed 0x38e7d8c32554
2011-04-20 12:21:14,444 DEBUG [bluetooth] - connection open, open now 1
2011-04-20 12:21:14,444 DEBUG [bluetooth] - rf(2) read(byte[4096])
2011-04-20 12:21:14,444 DEBUG [bluetooth] - read[] waits for data
2011-04-20 12:21:14,444 DEBUG [bluetooth] - read waits returns WAIT_OBJECT_0
2011-04-20 12:21:14,444 DEBUG [bluetooth] - read waits returns WAIT_OBJECT_0
2011-04-20 12:21:14,444 DEBUG [bluetooth] - rf(2) read([]) received 0
2011-04-20 12:21:14,444 DEBUG [bluetooth] - rf(2) read([]) not connected
2011-04-20 12:21:14,444 DEBUG [bluetooth] - read([]) no data
2011-04-20 12:21:14,444 DEBUG [bluetooth] - read([]) return EOF
2011-04-20 12:21:14,444 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
com.notifier.desktop.exception.ParseException: 
com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol 
message, the input ended unexpectedly in the middle of a field.  This could 
mean either than the input has been truncated or that an embedded message 
misreported its own length.
    at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:53)
    at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:27)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:87)
    at java.lang.Thread.run(Unknown Source)
Caused by: com.google.protobuf.InvalidProtocolBufferException: While parsing a 
protocol message, the input ended unexpectedly in the middle of a field.  This 
could mean either than the input has been truncated or that an embedded message 
misreported its own length.
    at com.google.protobuf.InvalidProtocolBufferException.truncatedMessage(InvalidProtocolBufferException.java:49)
    at com.google.protobuf.CodedInputStream.refillBuffer(CodedInputStream.java:691)
    at com.google.protobuf.CodedInputStream.readRawByte(CodedInputStream.java:714)
    at com.google.protobuf.CodedInputStream.readRawVarint32(CodedInputStream.java:318)
    at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:42)
    ... 3 more
2011-04-20 12:21:14,444 DEBUG [bluetooth] - closing RFCOMM Connection 2
2011-04-20 12:21:14,444 DEBUG [bluetooth] - connection closed, open now 0
2011-04-20 12:21:14,444 DEBUG [bluetooth] - rf(2) CloseServerConnection
2011-04-20 12:21:14,444 DEBUG [bluetooth] - rf(2) closing RfCommPort, 
Connected[FALSE]
2011-04-20 12:21:14,506 DEBUG [bluetooth] - rf(2) closed RfCommPort
2011-04-20 12:21:14,506 DEBUG [bluetooth] - rfs(1) acceptAndOpen
2011-04-20 12:21:14,506 DEBUG [bluetooth] - rfs(1) rf(3) RFCOMM server waits 
for connection

Original comment by menedet...@gmail.com on 20 Apr 2011 at 10:27

@GoogleCodeExporter
Copy link
Author 

I'm having problems with OS X 10.6.7/HTC Evo/Bluetooth as well. Seemingly 
relevant Console.app output:

5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
rfcommServiceOpenNotificationCallback
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStackRFCOMMSe
rver.mm(270)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
RFCOMM incomming connection authenticated
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStackRFCOMMSe
rver.mm(296)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
rfcommChannelOpenComplete
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStackRFCOMM.m
m(139)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] 2011-05-13 
13:49:57,262 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(2) 
[0xe00002cd])
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
invoke    BTOperation RFCOMMChannelClose
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStack.mm(240)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
rfcommChannelClosed->
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStackRFCOMM.m
m(89)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
rfcommChannelClosed
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStackRFCOMM.m
m(92)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
rfcommChannelClosed
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStackRFCOMM.m
m(160)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:       
execute  BTOperation RFCOMMChannelClose
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStack.mm(223)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:       
finished BTOperation RFCOMMChannelClose
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStack.mm(225)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] NATIVE:      
return    BTOperation RFCOMMChannelClose
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     OSXStack.mm(248)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] 2011-05-13 
13:49:57,357 ERROR [BluetoothNotificationReceiver] - Error handling bluetooth 
notification
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] javax.bluetooth.B
luetoothConnectionException: Failed to open connection(2) [0xe00002cd]
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     at 
com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Na
tive Method)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     at 
com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFC
ommConnectionNotifier.java:74)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     at 
com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(
BluetoothNotificationReceiver.java:83)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855]     at 
java.lang.Thread.run(Thread.java:680)
5/13/11 1:49:57 
PM  [0x0-0xfe0fe0].com.notifier.android-notifier-desktop[39855] 2011-05-13 
13:49:57,357 DEBUG [bluetooth] - create ChannelController to accept incoming 
connection

Original comment by hdon...@gmail.com on 13 May 2011 at 6:54

@GoogleCodeExporter
Copy link
Author 

Same message from above user.  Seemingly relevant Console Log
HTC Inspire 4G, running CordDroid 6.3 (IE: rooted)
5/17/11 6:49:29 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] 2011-05-17 
18:49:29,397 DEBUG [bluetooth] - create ChannelController to accept incoming 
connection
5/17/11 6:49:37 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
rfcommServiceOpenNotificationCallback
5/17/11 6:49:37 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStackRFCOMMSe
rver.mm(270)
5/17/11 6:49:37 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
RFCOMM incomming connection authenticated
5/17/11 6:49:37 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStackRFCOMMSe
rver.mm(296)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
rfcommChannelOpenComplete
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStackRFCOMM.m
m(139)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
rfcommChannelClosed->
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStackRFCOMM.m
m(89)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
rfcommChannelClosed
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStackRFCOMM.m
m(92)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
rfcommChannelClosed
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStackRFCOMM.m
m(160)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] 2011-05-17 
18:49:38,401 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(2) 
[0xe00002cd])
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
invoke    BTOperation RFCOMMChannelClose
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStack.mm(240)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:       
execute  BTOperation RFCOMMChannelClose
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStack.mm(223)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:       
finished BTOperation RFCOMMChannelClose
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStack.mm(225)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] NATIVE:      
return    BTOperation RFCOMMChannelClose
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     OSXStack.mm(248)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] 2011-05-17 
18:49:38,483 ERROR [BluetoothNotificationReceiver] - Error handling bluetooth 
notification
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801] javax.bluetooth.B
luetoothConnectionException: Failed to open connection(2) [0xe00002cd]
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     at 
com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Na
tive Method)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     at 
com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFC
ommConnectionNotifier.java:74)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     at 
com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(
BluetoothNotificationReceiver.java:83)
5/17/11 6:49:38 
PM  [0x0-0x329329].com.notifier.android-notifier-desktop[25801]     at 
java.lang.Thread.run(Thread.java:680)

Original comment by gkwait on 17 May 2011 at 11:53

@GoogleCodeExporter
Copy link
Author 

If it helps.. I'm facing the intermittent reception of bluetooth pings. Here's 
what I know. (HTC G1, rooted, running Froyo)

1) hcidump on Ubuntu _always_ shows activity when I send a test notification. 
Some of these translate to desktop notifications, some do not. So it could not 
be an issue with the mobile app (or it could in the sense that it does not make 
a correct connection everytime. But data seems to go through every time).

2) Upon startup of notifier app on ubuntu, the first ping is usually ignored, 
but the subsequent ones show up.

3) Pings seem to be more reliable when bluetooth is on, as opposed to delayed 
pings. It just seems that way though .. I have not maintained hard statistics.

As someone else pointed out, this thread probably discusses the same issue.
http://groups.google.com/group/android-platform/browse_thread/thread/485db574093
04d3e?hl=en&pli=1

Given that the issue reported is on mac, pc and linux, and on various versions 
of the android app, my take is that the issue is not with bluetooth stack 
implementation at all. It is rather the protocol used, or the way rfcomm 
connection is being made. If there is an alternative way of sending a ping than 
rfcomm, remote-notifier should dump the existing method for a new one.

Original comment by anil.ve...@gmail.com on 19 May 2011 at 2:58

@GoogleCodeExporter
Copy link
Author 

Workaround (N1/Win7): My Remote Notifier works with Bluetooth File Transfer 
(it.medieval.blueftp) installed, but not without.

Notifier initially worked via Bluetooth, then stopped working. I narrowed it 
down to my having uninstalled BFT (darn 512 MB app space...). Re-installed BFT, 
and notifications began working again.

Nexus One running stock 2.3.4 to a Win 7 (Ultimate) with ANS and Growl.

Original comment by pyrolu...@gmail.com on 2 Jun 2011 at 4:36

@GoogleCodeExporter
Copy link
Author 

Thanks a lot to comment 170!!
I have tried a lot of times to connect through Bluetooth but always failed. 
Installed Bluetooth File Transfer app, and Bluetooth method now works 
flawlessly!

HTC Incredible S (Android 2.3.3)
Windows 7 64 bit

Original comment by oleg...@gmail.com on 27 Jun 2011 at 12:08

@GoogleCodeExporter
Copy link
Author 

The system is working thanks to comment 170.

After installed "Bluetooth File Transfer" which is free from Market, everything 
is working.

Tested working on Lenovo Windows XP SP3, N1 CM7.1 RC1, connected via bluetooth 
connection.

Original comment by nutty.knot on 18 Jul 2011 at 7:58

@GoogleCodeExporter
Copy link
Author 

HTC Wildfire (Android 2.2) with android-notifier 0.2.8
Ubuntu 11.04 0.5.1 installed from deb
WiFi notification works, but bluetooth doesn't. Installing "Bluetooth File 
Transfer" made no difference. I get the traceback with the error about parsing 
the message (same as in comment 166)

Turning off encryption made bluetooth work however - so perhaps this particular 
is due to how bluetooth and encryption interact

Original comment by dav...@j5int.com on 19 Jul 2011 at 5:21

@GoogleCodeExporter
Copy link
Author 

Windows 7 Starter on a Samsung Netbook
USB-Bluetooth device by Sitecom
HTC Sensation 4G


Not working either. Love the idea though.

Original comment by ameesdo...@gmail.com on 5 Oct 2011 at 8:02

@GoogleCodeExporter
Copy link
Author 

Yet another example of working fine, then deciding not to work at all:

2011-11-12 14:42:20,265 DEBUG [bluetooth] - rfcomm (16) client connected
2011-11-12 14:42:20,265 DEBUG [bluetooth] - rfcomm MTU 1007
2011-11-12 14:42:20,266 DEBUG [bluetooth] - connection open, open now 1
2011-11-12 14:42:20,266 DEBUG [bluetooth] - ->read(byte[4096])
2011-11-12 14:42:20,275 DEBUG [bluetooth] - read([]) return 58
2011-11-12 14:42:20,275 DEBUG [bluetooth] - ->read(byte[4096])
2011-11-12 14:42:20,776 DEBUG [bluetooth] - read([]) received 0
2011-11-12 14:42:20,776 DEBUG [bluetooth] - read([]) no data
2011-11-12 14:42:20,776 DEBUG [bluetooth] - read([]) return EOF
2011-11-12 14:42:20,777 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1242453231589675, type=Ping
2011-11-12 14:42:20,781 DEBUG [bluetooth] - closing RFCOMM Connection 16
2011-11-12 14:42:20,781 DEBUG [bluetooth] - connection closed, open now 0
2011-11-12 14:42:20,906 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2011-11-12 14:42:30,445 DEBUG [bluetooth] - rfcomm (17) client connected
2011-11-12 14:42:30,445 DEBUG [bluetooth] - rfcomm MTU 1007
2011-11-12 14:42:30,445 DEBUG [bluetooth] - connection open, open now 1
2011-11-12 14:42:30,445 DEBUG [bluetooth] - ->read(byte[4096])
2011-11-12 14:42:30,456 DEBUG [bluetooth] - read([]) return 58
2011-11-12 14:42:30,456 DEBUG [bluetooth] - ->read(byte[4096])
2011-11-12 14:42:30,957 DEBUG [bluetooth] - read([]) received 0
2011-11-12 14:42:30,958 DEBUG [bluetooth] - read([]) no data
2011-11-12 14:42:30,958 DEBUG [bluetooth] - read([]) return EOF
2011-11-12 14:42:30,958 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1242453241668643, type=Ping
2011-11-12 14:42:30,958 DEBUG [bluetooth] - closing RFCOMM Connection 17
2011-11-12 14:42:30,958 DEBUG [bluetooth] - connection closed, open now 0
2011-11-12 14:42:31,082 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2011-11-12 14:44:54,851 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2011-11-12 14:44:54,975 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2011-11-12 14:44:55,031 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2011-11-12 14:45:03,050 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2011-11-12 14:45:03,198 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2011-11-12 14:45:03,198 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection

Original comment by reachjo...@gmail.com on 12 Nov 2011 at 2:47

@GoogleCodeExporter
Copy link
Author 

I send a test notification but my laptop does not show anything.  I am 
connected, paired, encrypted and authenticated.  As I read this fixes above it 
looks like you need to be a programmer to figure this out.  In layman's terms, 
what do I need to do to get this working?  It's a great idea of an app but I 
can not get it to work.

Original comment by roblat...@gmail.com on 22 Nov 2011 at 3:16

@GoogleCodeExporter
Copy link
Author 

Oleg@gmail has it right on. Installing Bluetooth File Transfer app does it for 
me too. Seems like its able to keep the connection open.

Im using my bluetooth connected to my mac pro to do handsfree through my mac.

Original comment by msguasta...@gmail.com on 10 Jan 2012 at 5:39

@GoogleCodeExporter
Copy link
Author 

I Have exactly the same error from my Macook with Lion and my Samsung Galaxy S2

Original comment by m...@jeanherfs.nl on 27 Jan 2012 at 1:00

@GoogleCodeExporter
Copy link
Author 

I'm having the same issue as wel.
Using Mac OS Lion10.7.2 and and HTC Sensation with Android 2.3.4 and following 
trace in my log:

2012-01-30 16:00:21,513 INFO [NotificationManagerImpl] - Waiting for test 
notification to pair device
2012-01-30 16:00:26,456 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2012-01-30 16:00:26,573 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)

Original comment by wtr...@gmail.com on 30 Jan 2012 at 3:04

@GoogleCodeExporter
Copy link
Author 

I have the same issue, again with Mac OS Lion 10.7.2 and a Samsung Galaxy S2. I 
have tried installing Bluetooth File Transfer and that does NOT seem to have 
helped for me, but I will keep trying. Here is my stack trace.

If there is an debugging or testing to be done, let me know.

2/6/12 2:47:55.524 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      rfcommServiceOpenNotificationCallback
2/6/12 2:47:55.524 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStackRFCOMMServer.mm(270)
2/6/12 2:47:55.558 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      RFCOMM incomming connection authenticated
2/6/12 2:47:55.558 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStackRFCOMMServer.mm(296)
2/6/12 2:47:55.727 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      rfcommChannelClosed->
2/6/12 2:47:55.727 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStackRFCOMM.mm(89)
2/6/12 2:47:55.727 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      rfcommChannelClosed
2/6/12 2:47:55.727 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStackRFCOMM.mm(92)
2/6/12 2:47:55.727 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      rfcommChannelClosed
2/6/12 2:47:55.727 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStackRFCOMM.mm(160)
2/6/12 2:47:55.871 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
2012-02-06 14:47:55,870 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2/6/12 2:47:55.871 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      invoke    BTOperation RFCOMMChannelClose
2/6/12 2:47:55.871 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStack.mm(240)
2/6/12 2:47:55.871 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:       execute  BTOperation RFCOMMChannelClose
2/6/12 2:47:55.871 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStack.mm(223)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:       finished BTOperation RFCOMMChannelClose
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStack.mm(225)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
NATIVE:      return    BTOperation RFCOMMChannelClose
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
    OSXStack.mm(248)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
2012-02-06 14:47:55,994 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop:     at 
com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Na
tive Method)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop:     at 
com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFC
ommConnectionNotifier.java:74)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop:     at 
com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(
BluetoothNotificationReceiver.java:83)
2/6/12 2:47:55.995 PM [0x0-0x145145].com.notifier.android-notifier-desktop:     at 
java.lang.Thread.run(Thread.java:680)
2/6/12 2:47:55.996 PM [0x0-0x145145].com.notifier.android-notifier-desktop: 
2012-02-06 14:47:55,995 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection

Original comment by pardsb...@gmail.com on 6 Feb 2012 at 7:51

@GoogleCodeExporter
Copy link
Author 

Seeing the same problem on Galaxy SII and Ubuntu 11.10. The delivery is flaky. 
Some notifications get through. Logs won't show anything that is not already 
posted in the thread.

Rodrigo, can add more logging to both desktop and android parts so that we 
could help you catch this ugly bug?

Original comment by kapran...@gmail.com on 22 Feb 2012 at 7:35

@GoogleCodeExporter
Copy link
Author 

same here on Ubuntu 11.14 AND htc explorer

Original comment by prat...@hibiscustech.com on 14 Mar 2012 at 1:47

@GoogleCodeExporter
Copy link
Author 

So I'm not a Java developer, but I play one on TV.

That being said, looking at the logs and testing on my system, I'm getting 
every other Bluetooth call.  Looking at the code, I think what's happening is 
that after a broadcast message is received, it closes the connection and places 
it in a state where it cannot receive new information.  The next time, the 
system throws the exception and puts itself back in a "good" state.  If you 
look at the debug info, you see alternating lines "connection closed, now open 
0" and "connection closed, now open 1".  My guess would be that if the 
connection wasn't closed, the notifier would work more reliably.

2012-04-11 10:07:56,662 DEBUG [bluetooth] - open using BlueCove 
javax.microedition.io.Connector
2012-04-11 10:07:56,662 DEBUG [bluetooth] - connecting 
btspp://localhost:7674047e6e474bf0831f209e3f9dd23f;name=AndroidNotifierService;a
uthenticate=true
2012-04-11 10:07:56,668 DEBUG [bluetooth] - isLocalDevicePowerOn
2012-04-11 10:07:56,685 DEBUG [bluetooth] - RFCOMM server created, ChannelID 4
2012-04-11 10:07:56,690 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2012-04-11 10:08:25,871 DEBUG [bluetooth] - rfcomm (2) client connected
2012-04-11 10:08:25,872 DEBUG [bluetooth] - rfcomm MTU 1007
2012-04-11 10:08:25,875 DEBUG [bluetooth] - new RemoteDevice 984B4AD64EE4
2012-04-11 10:08:25,875 DEBUG [bluetooth] - new devicesCashed 0x984b4ad64ee4
2012-04-11 10:08:25,876 DEBUG [bluetooth] - connection open, open now 1
2012-04-11 10:08:25,878 DEBUG [bluetooth] - ->read(byte[4096])
2012-04-11 10:08:25,880 DEBUG [bluetooth] - read([]) return 58
2012-04-11 10:08:25,880 DEBUG [bluetooth] - ->read(byte[4096])
2012-04-11 10:08:26,380 DEBUG [bluetooth] - read([]) received 0
2012-04-11 10:08:26,381 DEBUG [bluetooth] - read([]) no data
2012-04-11 10:08:26,381 DEBUG [bluetooth] - read([]) return EOF
2012-04-11 10:08:26,386 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1227869386515127, type=Ping
2012-04-11 10:08:26,387 DEBUG [bluetooth] - closing RFCOMM Connection 2
2012-04-11 10:08:26,387 DEBUG [bluetooth] - connection closed, open now 0
2012-04-11 10:08:26,476 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2012-04-11 10:08:35,478 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2012-04-11 10:08:35,566 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2012-04-11 10:08:35,568 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2012-04-11 10:08:40,668 DEBUG [bluetooth] - rfcomm (4) client connected
2012-04-11 10:08:40,668 DEBUG [bluetooth] - rfcomm MTU 1007
2012-04-11 10:08:40,668 DEBUG [bluetooth] - connection open, open now 1
2012-04-11 10:08:40,668 DEBUG [bluetooth] - ->read(byte[4096])
2012-04-11 10:08:40,703 DEBUG [bluetooth] - read([]) return 58
2012-04-11 10:08:40,703 DEBUG [bluetooth] - ->read(byte[4096])
2012-04-11 10:08:41,203 DEBUG [bluetooth] - read([]) received 0
2012-04-11 10:08:41,203 DEBUG [bluetooth] - read([]) no data
2012-04-11 10:08:41,203 DEBUG [bluetooth] - read([]) return EOF
2012-04-11 10:08:41,204 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1227869401813286, type=Ping
2012-04-11 10:08:41,204 DEBUG [bluetooth] - closing RFCOMM Connection 4
2012-04-11 10:08:41,204 DEBUG [bluetooth] - connection closed, open now 0
2012-04-11 10:08:41,315 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2012-04-11 10:08:48,317 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2012-04-11 10:08:48,403 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2012-04-11 10:08:48,403 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2012-04-11 10:11:21,438 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(3))
2012-04-11 10:11:21,554 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
javax.bluetooth.BluetoothConnectionException: Failed to open connection(3)
    at com.intel.bluetooth.BluetoothStackOSX.rfServerAcceptAndOpenRfServerConnection(Native Method)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.acceptAndOpen(BluetoothRFCommConnectionNotifier.java:74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2012-04-11 10:11:21,554 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2012-04-11 10:31:07,851 DEBUG [bluetooth] - rfcomm (7) client connected
2012-04-11 10:31:07,851 DEBUG [bluetooth] - rfcomm MTU 1007
2012-04-11 10:31:07,852 DEBUG [bluetooth] - connection open, open now 1
2012-04-11 10:31:07,852 DEBUG [bluetooth] - ->read(byte[4096])
2012-04-11 10:31:07,861 DEBUG [bluetooth] - read([]) return 58
2012-04-11 10:31:07,861 DEBUG [bluetooth] - ->read(byte[4096])
2012-04-11 10:31:08,361 DEBUG [bluetooth] - read([]) received 0
2012-04-11 10:31:08,362 DEBUG [bluetooth] - read([]) no data
2012-04-11 10:31:08,362 DEBUG [bluetooth] - read([]) return EOF
2012-04-11 10:31:08,362 INFO [NotificationManagerImpl] - Notification received: 
notificationId=1227870696502277, type=Ping
2012-04-11 10:31:08,362 DEBUG [bluetooth] - closing RFCOMM Connection 7
2012-04-11 10:31:08,363 DEBUG [bluetooth] - connection closed, open now 0
2012-04-11 10:31:08,453 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection

Original comment by brett.le...@gmail.com on 11 Apr 2012 at 2:34

@GoogleCodeExporter
Copy link
Author 

I had the same problem, but then i found a workaround.

I didn't pair my device from the beginning.I deleted all the previous pairing 
with my computer. Enabled "auto-enable Bluetooth", then set both my phone & 
desktop(running Ubuntu natty)as visible from Bluetooth option. Now when i try 
send a test notification it automatically initiates Bluetooth pairing process!

After successful pairing, Bluetooth notification works fine. However it doesn't 
notify about all the notifications. :(

Original comment by sunnysig...@gmail.com on 26 Jun 2012 at 8:07

@GoogleCodeExporter
Copy link
Author 

This was what I got when trying to do a test notification:
2013-01-21 13:21:24,558 ERROR [BluetoothNotificationReceiver] - Error handling 
bluetooth notification
com.notifier.desktop.exception.ParseException: 
com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol 
message, the input ended unexpectedly in the middle of a field.  This could 
mean either than the input has been truncated or that an embedded message 
misreported its own length.
    at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:53)
    at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:27)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:87)
    at java.lang.Thread.run(Unknown Source)
Caused by: com.google.protobuf.InvalidProtocolBufferException: While parsing a 
protocol message, the input ended unexpectedly in the middle of a field.  This 
could mean either than the input has been truncated or that an embedded message 
misreported its own length.
    at com.google.protobuf.InvalidProtocolBufferException.truncatedMessage(InvalidProtocolBufferException.java:49)
    at com.google.protobuf.CodedInputStream.refillBuffer(CodedInputStream.java:691)
    at com.google.protobuf.CodedInputStream.readRawByte(CodedInputStream.java:714)
    at com.google.protobuf.CodedInputStream.readRawVarint32(CodedInputStream.java:318)
    at com.notifier.desktop.parsing.MultiNotificationParser.parse(MultiNotificationParser.java:42)
    ... 3 more

Original comment by jrf...@gmail.com on 21 Jan 2013 at 6:28

@GoogleCodeExporter
Copy link
Author 

Hello
I may not be on the right post, excuse me if it is the case.

I have installed 0.5.1 x86_64.exe file on a win7-64 pro dell desktop.
I have selected WiFi and invalidated Bluetooth on the phone (Samsung Ace and 
android
2.3.6)
Options  Ring and Ping are selected.
Whether ring or ping,it is correctly logged on the log.
Trouble is that though the visual and audio notification works correctly with 
the Ping, I don't get anything when a Ring comes up.
Exactly the same problem with a HP Probook Laptop
Regards

Original comment by Fossard...@gmail.com on 26 Sep 2013 at 1:09

@GoogleCodeExporter
Copy link
Author 

klkllarfg

Original comment by swarajin...@gmail.com on 9 Sep 2014 at 9:28

@GoogleCodeExporter GoogleCodeExporter mentioned this issue Apr 16, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Communication OpSys-Android Priority-Critical Stability Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter