search

copyliu / android-notifier

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

Bluetooth notifications not delivered #3

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
It only works for me when target device is selected to the very device I send 
to. Any or all (whatever the difference is) does not work for me. Try all those 
settings hopefully you will find a working one.

Original comment by peter.v...@gmail.com on 29 Sep 2010 at 9:29

GoogleCodeExporter commented 9 years ago 
About any vs all - any will try to send to the first known device which is a 
computer), and all will send to all computer devices in parallel.

Original comment by rdamazio@gmail.com on 29 Sep 2010 at 1:20

GoogleCodeExporter commented 9 years ago 
app 0.2.8 made no difference for me  (see comment #87)

Original comment by fred.wel...@gmail.com on 29 Sep 2010 at 2:54

GoogleCodeExporter commented 9 years ago 
mac app 0.2.9, phone app 0.2.8  osx 10.6.4

my system tray's bluetooth icon is showing activity when i send a test message 
from my phone, but no response from the program..

Original comment by alex.li...@gmail.com on 1 Oct 2010 at 8:36

GoogleCodeExporter commented 9 years ago 
Issue 203 has been merged into this issue.

Original comment by rdamazio@gmail.com on 5 Oct 2010 at 12:48

GoogleCodeExporter commented 9 years ago 
I can confirm having the same problem running OS X 10.6.4, MacDroidNotifier 
0.2.9 and phone app 0.2.8 on an HTC EVO 4G running Froyo (2.2).  I would be 
happy to produce logs of this issue if someone would be so kind as to explain 
generally how I would go about it;  I am no stranger to linux and bash, just 
not sure where OS X would store the logs useful to this particular problem.

Original comment by Soleil.Golden on 6 Oct 2010 at 10:47

GoogleCodeExporter commented 9 years ago 
An android developer said HTC EVO has some known issues with bluetooth 
communication in this thread: 
http://groups.google.com/group/android-platform/browse_thread/thread/485db574093
04d3e?hl=en

He said "HTC is aware of the problem and I believe its already fixed but I 
guess you have not received the OTAed. I have asked HTC to reply to this 
thread.".

Original comment by lehph...@gmail.com on 6 Oct 2010 at 11:44

GoogleCodeExporter commented 9 years ago 
Issue 208 has been merged into this issue.

Original comment by lehph...@gmail.com on 6 Oct 2010 at 11:54

GoogleCodeExporter commented 9 years ago 
Issue 214 has been merged into this issue.

Original comment by lehph...@gmail.com on 7 Oct 2010 at 12:41

GoogleCodeExporter commented 9 years ago 
RE: Comment 107

This explains a lot- thanks for the information.  I do have a pending OTA 
update from HTC, though I cannot confirm that it resolves the issue, as the 
update has yet to successfully run.   Oh well!  I'll just stick to WiFi for 
now.  :)

Original comment by Soleil.Golden on 7 Oct 2010 at 1:33

GoogleCodeExporter commented 9 years ago 
I have the same issue with the EVO running Fresh EVO 3.3.0.1 Froyo 2.2.  No 
Bluetooth Notifications at all from the phone to my MacBook Pro.  So where are 
the logs for what we are looking for?

Original comment by cseabro...@gmail.com on 7 Oct 2010 at 2:11

GoogleCodeExporter commented 9 years ago 
@cseabrooks You can get android logs with alogcat app, the desktop app has an 
option called "Show Log" in the tray icon menu to open the directory where 
android-notifier-desktop.log file is kept.

Original comment by lehph...@gmail.com on 7 Oct 2010 at 3:29

GoogleCodeExporter commented 9 years ago 
Issue 215 has been merged into this issue.

Original comment by lehph...@gmail.com on 7 Oct 2010 at 5:00

GoogleCodeExporter commented 9 years ago 
I have the same issue with the DESIRE running Froyo 2.2.  No Bluetooth 
Notifications at all from the phone to my MacBook Pro.  So where are the logs 
for what we are looking for?

Original comment by andrea...@gmail.com on 7 Oct 2010 at 7:43

GoogleCodeExporter commented 9 years ago 
Issue 219 has been merged into this issue.

Original comment by lehph...@gmail.com on 8 Oct 2010 at 12:59

GoogleCodeExporter commented 9 years ago 
I'm getting this bluetooth issue with my Droid Incredible, by reading this post 
i'm gather there is currently no fix for this. Is that correct?

Original comment by jpiermar...@gmail.com on 8 Oct 2010 at 5:21

GoogleCodeExporter commented 9 years ago 
@jpiermarini No fix unfortunately.

User Meulfire said in issue 217 that he's having problems getting bluetooth 
working with his non-rooted HTC Hero, but some people got it working with 
rooted phones.

Original comment by lehph...@gmail.com on 8 Oct 2010 at 5:34

GoogleCodeExporter commented 9 years ago 
 @lehph
curses.

my phone is rooted i did the unrevoked root on it a week or two ago and just 
tried setting up the notifier today.

Original comment by jpiermar...@gmail.com on 8 Oct 2010 at 5:49

GoogleCodeExporter commented 9 years ago 
Issue 227 has been merged into this issue.

Original comment by lehph...@gmail.com on 14 Oct 2010 at 6:34

GoogleCodeExporter commented 9 years ago 
I'd like to add that I have an odd situation (perhaps it helps with figuring 
out where the problem is):
Phone is a Samsung Galaxy S i9000
RN works OK at home (Ubuntu Linux) but when I get to work (Win7 -- where I want 
it to work the most), notifications don't go through. Logging doesn't reveal 
anything about receiving a notification. I've downloaded and installed growl 
and enabled in addition to the system notifications (the RN log shows that it 
can connect to growl).
The phone is paired in both cases. In both cases, I can send a file to the 
phone from the pc. 

What other information can I supply to help sort this out?

Original comment by dav...@gmail.com on 18 Oct 2010 at 7:01

GoogleCodeExporter commented 9 years ago 
Issue 241 has been merged into this issue.

Original comment by rdamazio@gmail.com on 18 Oct 2010 at 9:27

GoogleCodeExporter commented 9 years ago 
Issue 252 has been merged into this issue.

Original comment by rdamazio@gmail.com on 21 Oct 2010 at 4:38

GoogleCodeExporter commented 9 years ago 
Remote Notifier v0.2.8 on HTC Desire
MacDroidNotivier v0.2.9 on a Macbook model A1278
Using bluetooth only.

Everything worked just fine a few days back, and have worked fine for a few 
weeks. Suddenly notifications doesn't work anymore. The notification reaches 
the Mac, so the error is not on the handset side. I've added the code below 
into BlueToothNotificationListener.m to see if the rfcomm fails, and it does. 
With error 0xe00002cd which according to IOReturn.h is "device not open".. I 
can't really see what all of a sudden would cause this though.. :/

- (void)rfcommChannelOpenComplete:(IOBluetoothRFCOMMChannel*)channel 
status:(IOReturn)error
{
    if ( error != kIOReturnSuccess )
    {
        //The ususal error 0xe00002cd is defined in IOError.h as:
        //#define kIOReturnNotOpen iokit_common_err(0x2cd) // device not open 
        NSLog(@"Failed to open the RFCOMM channel, error: 0x%08lx.\n", (UInt32)error);
        [self rfcommChannelClosed:channel];
        return;
    }
}

Original comment by duxz...@gmail.com on 24 Oct 2010 at 8:54

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Just to clarify: notifications get through, but are never displayed because 
something causes the rfcomm channel not to open correctly.

Original comment by duxz...@gmail.com on 24 Oct 2010 at 9:08

GoogleCodeExporter commented 9 years ago 
Issue 259 has been merged into this issue.

Original comment by lehph...@gmail.com on 25 Oct 2010 at 12:12

GoogleCodeExporter commented 9 years ago 
Issue 263 has been merged into this issue.

Original comment by rdamazio@gmail.com on 26 Oct 2010 at 4:24

GoogleCodeExporter commented 9 years ago 
Issue 267 has been merged into this issue.

Original comment by rdamazio@gmail.com on 29 Oct 2010 at 11:11

GoogleCodeExporter commented 9 years ago 
Issue 274 has been merged into this issue.

Original comment by lehph...@gmail.com on 31 Oct 2010 at 8:39

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Same issue with an HTC Desire running 2.1 and my Mac Book Pro 10.6.4.
Here is the log entries I get, it tries 11 times and gives up.

11-04 16:33:34.377: DEBUG/RemoteNotifier(1108): Connecting to Bluetooth device 
MacBook Pro de Marc
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108): Waiting to retry
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108): java.io.IOException: Service 
discovery failed
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:377)
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:201)
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
org.damazio.notifier.notification.methods.BluetoothNotificationMethod.doSendNoti
fication(BluetoothNotificationMethod.java:177)
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
org.damazio.notifier.notification.methods.BluetoothNotificationMethod.sendNotifi
cation(BluetoothNotificationMethod.java:123)
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
org.damazio.notifier.notification.Notifier.runNotificationThread(Notifier.java:1
71)
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
org.damazio.notifier.notification.Notifier.access$0(Notifier.java:167)
11-04 16:33:40.416: DEBUG/RemoteNotifier(1108):     at 
org.damazio.notifier.notification.Notifier$1.run(Notifier.java:93)
11-04 16:33:41.426: DEBUG/RemoteNotifier(1108): Connecting to Bluetooth device 
MacBook Pro de Marc

Original comment by marc.poppleton on 4 Nov 2010 at 3:52

GoogleCodeExporter commented 9 years ago 
Got the same issue with Nexus One (Froyo) and some recent Ubuntu. Android log 
here http://pastie.org/1276133 , just wondering, is desktop sending back some 
confirmation that it received notification?

Original comment by dusan.ma...@gmail.com on 5 Nov 2010 at 11:39

GoogleCodeExporter commented 9 years ago 
On subsequent trying, the notification gets delivered, so I assume that this 
could be solved (hacked) with just confirmation message and if failed, 
subsequent retries.

Original comment by dusan.ma...@gmail.com on 5 Nov 2010 at 11:41

GoogleCodeExporter commented 9 years ago 
Got one test notification (out of 20) and a notification about battery state 
but that's about all that I managed to get. Bluetooth pairing is ok, I can 
browse my phone from my Mac, share content between the phone and the Mac.

Original comment by marc.poppleton on 9 Nov 2010 at 3:58

GoogleCodeExporter commented 9 years ago 
Issue 283 has been merged into this issue.

Original comment by lehph...@gmail.com on 9 Nov 2010 at 7:41

GoogleCodeExporter commented 9 years ago 
Notifications work on my Nexus One (2.2.1) and OS X, but only after I restart 
the Remote Notifier notification service on the phone. If I get out of range 
for a while (usually over lunch), then get back in range I don't get any new 
notifications until I restart the notification service.

This only started happening after the Froyo 2.2.1 update. It worked fine on 
2.2.0. I even tried doing a factory reset, but to no avail. So, this could be 
an issue with 2.2.1.

Original comment by shr...@gmail.com on 9 Nov 2010 at 9:44

GoogleCodeExporter commented 9 years ago 
Still not working with  desktop-notifier 0.5.1. 

My details are comment 87 and unchanged except for new updated client.

Original comment by fred.wel...@gmail.com on 9 Nov 2010 at 10:46

GoogleCodeExporter commented 9 years ago 
Started the bluetooth service on my HTC Desire (2.1), started the Notifier 
Service....phone rebooted. Unable to restart the bluetooth service. Rebooted 
the phone, Notifier Service auto-started and started the bluetooth service 
without problem. A Notification regarding battery state was displayed on mon 
Mac. I then called my phone, no incoming call notification displayed on my Mac.
I fear the problem doesn't come from Android Notifier but from the bluetooth 
stack. Unless Android Notifier makes the stack go haywire to the point of 
crashing?

Original comment by marc.poppleton on 10 Nov 2010 at 9:20

GoogleCodeExporter commented 9 years ago 
hi
i have HTC Desire(custom rom AuraxTSens 8.0) with Remote Notifier v0.2.8
and Ubuntu 10.10 with Android desktop-notifier 0.5.1
wi-fi notify works but bluetooth not :(
i got an error message and this at log file

2010-11-20 12:06:04,059 INFO [ApplicationImpl] - Starting [bluetooth] receiver
2010-11-20 12:06:04,832 INFO [ApplicationImpl] - Stopping [TCP] receiver
2010-11-20 12:06:04,873 INFO [ApplicationImpl] - Stopping [UDP] receiver
2010-11-20 12:09:43,970 INFO [NotificationManagerImpl] - Waiting for test 
notification to pair device
2010-11-20 12:09:45,851 DEBUG [bluetooth] - RFCOMM client accepted, handle 34
2010-11-20 12:09:45,852 DEBUG [bluetooth] - connection open, open now 1
2010-11-20 12:09:45,852 DEBUG [bluetooth] - Connection closed, Connection reset 
by peer
2010-11-20 12:09:45,872 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(Thread.java:619)
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
2010-11-20 12:09:45,879 DEBUG [bluetooth] - closing RFCOMM Connection 34
2010-11-20 12:09:45,880 DEBUG [bluetooth] - connection closed, open now 0
2010-11-20 12:09:45,880 DEBUG [bluetooth] - RFCOMM disconnect, handle 34
2010-11-20 12:09:49,778 INFO [NotificationManagerImpl] - Pairing stopped
2010-11-20 12:09:49,781 INFO [NotificationManagerImpl] - Pairing stopped

Original comment by psy...@gmail.com on 20 Nov 2010 at 10:17

GoogleCodeExporter commented 9 years ago 
Issue 306 has been merged into this issue.

Original comment by lehph...@gmail.com on 1 Dec 2010 at 1:14

GoogleCodeExporter commented 9 years ago 
Issue 315 has been merged into this issue.

Original comment by rdamazio@gmail.com on 9 Dec 2010 at 11:44

GoogleCodeExporter commented 9 years ago 
Issue 301 has been merged into this issue.

Original comment by rdamazio@gmail.com on 9 Dec 2010 at 11:49

GoogleCodeExporter commented 9 years ago 
Im on a Samsung Galaxy S i9000 and i get this:

2010-12-16 08:39:22,378 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(2) 
[0xe00002cd])
2010-12-16 08:39:22,462 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)

i cant use wifi because the phone connect to the WPA2 Enterprise Network we use 
here at the University :/

Would be great if Online-Notifications would work over 3G to Wifi (using my 
google account for example) :o

Original comment by summel...@googlemail.com on 16 Dec 2010 at 7:43

GoogleCodeExporter commented 9 years ago 
I have a Samsung Galaxy S and I get a similar error as #139.
Also note that it worked a little: I received the message test a couple of 
times, but then I got a popup window that an error occurred and it stopped 
working.
Tried to restart the application a couple of times; unpaired the device and 
paired it again; nothing worked.

If that helps:

Windows 7 Home Edition 64 bit

Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)

Android Notifier Desktop 0.5.1
Android Remote Notifier Version 0.2.8 (downloaded from Android Market)

The error message:

2010-12-18 14:10:16,438 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 bogdan.s...@gmail.com on 18 Dec 2010 at 12:22

GoogleCodeExporter commented 9 years ago 
I have a Samsung Galaxy S and I can't get the bluetooth notification to work. 
Every time I press test notification after about 5 seconds my mac would display 
an error saying theres an error. And from the logs, this is what I get.

74)
    at com.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:83)
    at java.lang.Thread.run(Thread.java:680)
2010-12-19 05:08:27,369 DEBUG [bluetooth] - create ChannelController to accept 
incoming connection
2010-12-19 07:33:02,063 DEBUG [bluetooth] - will throw exception 
javax/bluetooth/BluetoothConnectionException(Failed to open connection(2) 
[0xe00002cd])
2010-12-19 07:33:02,272 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:

Original comment by rocky....@gmail.com on 19 Dec 2010 at 7:14

GoogleCodeExporter commented 9 years ago 
Issue 322 has been merged into this issue.

Original comment by rdamazio@gmail.com on 21 Dec 2010 at 6:19

GoogleCodeExporter commented 9 years ago 
Using a mytouch 4g and macbook 4,1  works using wi-fi not with bluetooth.

Original comment by simplepn...@gmail.com on 25 Dec 2010 at 3:02

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I'm using an LG P500 with froyo and a mac os x 10.6.5. Wifi works fine but not 
bluetooth. I'm having the same output as rocky.clt on the log file.

Original comment by filipeva...@gmail.com on 27 Dec 2010 at 7:21

GoogleCodeExporter commented 9 years ago 
I'm using an LG P500 with froyo and a mac os x 10.6.5. Wifi works fine but not 
bluetooth. I'm having the same output as rocky.clt on the log file.

Original comment by filipeva...@gmail.com on 27 Dec 2010 at 7:21