Bluetooth notifications not delivered

GoogleCodeExporter commented 8 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 8 years ago

I have Android 2.1 and neither the Wifi nor the Bluetooth successfully sends a 
notification to my macbook pro. I do see the bluetooth quickly connect to my 
macbook pro, and then disconnect when I send a test notification.

Original comment by alex.lap...@gmail.com on 9 Sep 2010 at 6:14

GoogleCodeExporter commented 8 years ago

well my buddies 3g iphone wont stay connected either, but it could be its the 
older iphone3g and/or the 4.1 update he installed today for the iOS, but either 
way I cant get either phone to stay connected to my MBP bluetooth for longer 
than a few seconds to even try to test this program out, when I get home 
tonight I'll play around on my PC wifi, since i dont have a bt dongle and see 
if I can get that to work

Original comment by chicagof...@gmail.com on 9 Sep 2010 at 6:16

GoogleCodeExporter commented 8 years ago

Also not getting notifications to work correctly  - Wifi and Bluetooth.

HTC Droid Incredible, Android 2.2
Macbook Pro

Original comment by benship...@gmail.com on 9 Sep 2010 at 6:16

GoogleCodeExporter commented 8 years ago

I have received reports of this from 2.1 as well, and I've been unable to 
reproduce on Eclair, Froyo, Gingerbread or Honeycomb, so I would suspect it's 
not an issue in a specific version or even a specific phone (I've tried with 
the Nexus One and Milestone)

Original comment by rdamazio@gmail.com on 9 Sep 2010 at 6:17

GoogleCodeExporter commented 8 years ago

Issue 73 has been merged into this issue.

Original comment by rdamazio@gmail.com on 9 Sep 2010 at 7:24

GoogleCodeExporter commented 8 years ago

@rdamazio  I have been disregarding growl and the macdriod program, and I still 
cannot get my phone to stay connected to my MBP, its either in the bluetooth of 
the MBP or inside my phone, I work with a MacPro and MBP at work and I have a 
PC at home, if there is any way for me to help dev let me know.

Original comment by chicagof...@gmail.com on 9 Sep 2010 at 7:25

GoogleCodeExporter commented 8 years ago

I don't know if helps, but, the transmission occurs, bluetooth on desktop 
receives data but, the android notifier apparently don't process

Original comment by bemanuel...@gmail.com on 9 Sep 2010 at 8:28

GoogleCodeExporter commented 8 years ago

@bemanuel, are you on a mac? if so on your bluetooth preferences is your phone 
paired AND connected? I cant seem to even get my phone to stay connected

Original comment by chicagof...@gmail.com on 9 Sep 2010 at 8:51

GoogleCodeExporter commented 8 years ago

hi, i'm on PC, Linux ( Ubuntu AMD 64 ). Everything is ok, except the android 
notifier apparently don't process

Original comment by bemanuel...@gmail.com on 9 Sep 2010 at 8:55

GoogleCodeExporter commented 8 years ago

Ok, so I'm using wifi on my xp 32bit pc, and I hear a sound when i do a test 
notification, but no pop-up =\

Original comment by chicagof...@gmail.com on 9 Sep 2010 at 11:04

GoogleCodeExporter commented 8 years ago

Issue 85 has been merged into this issue.

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 3:03

GoogleCodeExporter commented 8 years ago

Issue 80 has been merged into this issue.

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 2:51

GoogleCodeExporter commented 8 years ago

Issue 100 has been merged into this issue.

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 5:23

GoogleCodeExporter commented 8 years ago

Issue 102 has been merged into this issue.

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 5:26

GoogleCodeExporter commented 8 years ago

Issue 86 has been merged into this issue.

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 5:32

GoogleCodeExporter commented 8 years ago

Issue 104 has been merged into this issue.

Original comment by rdamazio@gmail.com on 10 Sep 2010 at 5:42

GoogleCodeExporter commented 8 years ago

On a Mac, Nexus One, Froyo (2.2) - testing Bluetooth notifications.

Phone is connected and paired although not test notifications display. While my 
computer says the phone is paired and connected, the phone's Bluetooth settings 
display that it's paired only. Despite troubleshooting just about everything I 
can think of I can't get them both to be connected. Not sure if this is an 
issue outside of Notifier but interested to know if it's a known issue with 
N1's.

Original comment by d...@google.com on 10 Sep 2010 at 6:34

GoogleCodeExporter commented 8 years ago

my issue 104 got merged with this one, but there seems to be alot talk about 
"having multiple bluetooth devices paire up".. but just so you know, I only 
have one... perhaps the same problem anyway, that you know better =) but just 
whanted to get you to know that.

Original comment by fredrik....@gmail.com on 10 Sep 2010 at 7:51

GoogleCodeExporter commented 8 years ago

tried the updated apk 0.2.5, same result =(

Original comment by fredrik....@gmail.com on 10 Sep 2010 at 8:00

GoogleCodeExporter commented 8 years ago

Seems bluetooth is broken on my DroidX, can't test wireless at the moment.  
Using linux client on ubuntu 32bit.  Using the app to send a test message with 
anything else peered (bt headset) I get nothing received on pc when sending a 
test message.  Disconnecting my headset and sending a test, I get one message 
ping in console output, but never another after the first test.  It appears 
it's more of the phone app as an issue vs. client on pc.

I connect to a lot of different customer wifi networks, so bluetooth would be 
the preferred, consistent method of connectivity.  Looking forward to this 
working.

Original comment by mikebut...@gmail.com on 10 Sep 2010 at 8:11

GoogleCodeExporter commented 8 years ago

Actually playing with it a bit more, it does work past one try, but very 
inconsistently.  It'll work for a few sends, then not work, now I can't get it 
to work at all.  Bug reporting feature isn't putting log text in my clipboard 
either - doh!

Original comment by mikebut...@gmail.com on 10 Sep 2010 at 8:46

GoogleCodeExporter commented 8 years ago

Issue 113 has been merged into this issue.

Original comment by rdamazio@gmail.com on 11 Sep 2010 at 12:03

GoogleCodeExporter commented 8 years ago

Issue 112 has been merged into this issue.

Original comment by rdamazio@gmail.com on 11 Sep 2010 at 12:03

GoogleCodeExporter commented 8 years ago

HTC EVO WiFi works well but bluetooth has not corked at all...

Original comment by cs45...@gmail.com on 11 Sep 2010 at 3:49

GoogleCodeExporter commented 8 years ago

HTC Incredible will pair but not connect for more than 15 seconds.  I guess 
this is a known issue with the Droid Bluetooth.  If we could find a way to keep 
the BT connected then it would work.

Original comment by hector.e...@gmail.com on 11 Sep 2010 at 5:57

GoogleCodeExporter commented 8 years ago

Hi there, I'm new to the party.

On the phone:
T-Mobile G1/HTC Dream
CyanogenMod 6 (Android 2.2)
Remote Notifier 0.2.5

On the laptop:
Ubuntu 9.10
Android Notifier Desktop 0.2.1

The phone pairs fine with the laptop, and I can transfer files to and from 
using Bluetooth with no problems.

However, only 1 out of about 7 notifications actually come through on the 
laptop.  Running the desktop client through the terminal shows that it is 
receiving some notifications, but a) not all of them arrive from the phone, and 
b) not all of the notifications that /do/ arrive from the phone actually end up 
as popups.

Original comment by thelove...@gmail.com on 11 Sep 2010 at 10:28

GoogleCodeExporter commented 8 years ago

Issue 123 has been merged into this issue.

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

GoogleCodeExporter commented 8 years ago

Issue 91 has been merged into this issue.

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

GoogleCodeExporter commented 8 years ago

okay - i have updated my android client and installed the latest 0.3.0 version 
on my Windows XP PC

I have also installed Growl for Windows v2.0.4.2 - because I had error in 
android-notifier-log saying it couldn't communicate with GNTP server

2010-09-13 09:34:30,309 ERROR [GrowlNotificationBroadcaster] - Error 
communicating with GNTP server
java.net.ConnectException: Connection refused: no further information
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:384)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:354)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:276)
    at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
2010-09-13 09:34:30,465 DEBUG [bluetooth] - 

Now I have Growl installed and I have the following log results
2010-09-13 09:51:38,421 INFO [ApplicationImpl] - Starting SWT
2010-09-13 09:51:38,562 INFO [ApplicationImpl] - Showing tray icon
2010-09-13 09:51:38,640 INFO [ApplicationImpl] - Starting [Growl] broadcaster
2010-09-13 09:51:38,937 INFO [ApplicationImpl] - Starting [bluetooth] receiver
2010-09-13 09:51:38,952 DEBUG [bluetooth] - Java 1.4+ detected: 1.6.0_20; Java 
HotSpot(TM) Client VM; Sun Microsystems Inc.
2010-09-13 09:51:38,968 DEBUG [bluetooth] - Use stack ClassLoader
2010-09-13 09:51:38,984 DEBUG [bluetooth] - set dll dir 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0
2010-09-13 09:51:39,031 DEBUG [bluetooth] - Library loaded from 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\intelbth.dll
2010-09-13 09:51:39,031 DEBUG [bluetooth] - nativeDebugCallback ON
2010-09-13 09:51:39,031 DEBUG [bluetooth] - socket error [10047] An address 
incompatible with the requested protocol was used.
2010-09-13 09:51:39,046 DEBUG [bluetooth] - BluetoothStack detected 2
2010-09-13 09:51:39,046 DEBUG [bluetooth] - Use stack ClassLoader
2010-09-13 09:51:39,046 DEBUG [bluetooth] - tmp file 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\bluecove.dll
2010-09-13 09:51:39,093 INFO [GrowlNotificationBroadcaster] - Registered with 
GNTP server sucessfully
2010-09-13 09:51:39,109 DEBUG [bluetooth] - Library loaded from 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\bluecove.dll
2010-09-13 09:51:39,124 DEBUG [bluetooth] - nativeDebugCallback ON
2010-09-13 09:51:39,156 INFO [ApplicationImpl] - Adding to startup
2010-09-13 09:51:39,156 DEBUG [bluetooth] - open using BlueCove 
javax.microedition.io.Connector
2010-09-13 09:51:39,156 DEBUG [bluetooth] - connecting 
btspp://localhost:7674047e6e474bf0831f209e3f9dd23f;name=AndroidNotifierService
2010-09-13 09:51:39,484 DEBUG [bluetooth] - rfs(1) ServerOpen
2010-09-13 09:51:39,484 DEBUG [bluetooth] - serverSCN 1
2010-09-13 09:51:39,484 DEBUG [bluetooth] - rfs(1) acceptAndOpen
2010-09-13 09:51:39,484 DEBUG [bluetooth] - service_name assigned 
[AndroidNotifierService]
2010-09-13 09:51:39,484 DEBUG [bluetooth] - rfs(1) rf(2) RFCOMM server waits 
for connection
2010-09-13 09:52:05,202 INFO [NotificationManagerImpl] - Waiting for test 
notification to pair device
2010-09-13 09:52:26,952 INFO [NotificationManagerImpl] - Pairing canceled
2010-09-13 09:55:20,140 INFO [ApplicationImpl] - Shutting down...
2010-09-13 09:55:20,140 INFO [ApplicationImpl] - Hiding tray icon
2010-09-13 09:55:20,156 INFO [ApplicationImpl] - Stopping [bluetooth] receiver
2010-09-13 09:55:20,171 INFO [ApplicationImpl] - Stopping [Growl] broadcaster
2010-09-13 09:55:20,171 INFO [ApplicationImpl] - Stopping SWT
2010-09-13 09:55:20,202 DEBUG [bluetooth] - destroy WIDCOMMStack
2010-09-13 09:55:20,515 DEBUG [bluetooth] - will throw exception 
java/io/InterruptedIOException(Stack closed)
2010-09-13 09:55:20,515 DEBUG [bluetooth] - closing ConnectionNotifier 1
2010-09-13 09:55:20,515 DEBUG [bluetooth] - will throw exception 
java/io/IOException(Stack closed)
2010-09-13 09:55:20,515 WARN [BluetoothNotificationReceiver] - Error closing 
bluetooth
java.io.IOException: Stack closed
    at com.intel.bluetooth.BluetoothStackWIDCOMM.rfServerCloseImpl(Native Method)
    at com.intel.bluetooth.BluetoothStackWIDCOMM.rfServerClose(BluetoothStackWIDCOMM.java:877)
    at com.intel.bluetooth.BluetoothRFCommConnectionNotifier.stackServerClose(BluetoothRFCommConnectionNotifier.java:59)
    at com.intel.bluetooth.BluetoothConnectionNotifierBase.shutdown(BluetoothConnectionNotifierBase.java:146)
    at com.intel.bluetooth.BluetoothConnectionNotifierBase.close(BluetoothConnectionNotifierBase.java:119)
    at com.google.code.notifier.desktop.notification.bluetooth.BluetoothNotificationReceiver$1.run(BluetoothNotificationReceiver.java:115)
    at java.lang.Thread.run(Unknown Source)
2010-09-13 09:55:22,281 DEBUG [bluetooth] - WIDCOMM destroyed
2010-09-13 09:55:27,296 INFO [ApplicationImpl] - Starting SWT
2010-09-13 09:55:27,421 INFO [ApplicationImpl] - Showing tray icon
2010-09-13 09:55:27,515 INFO [ApplicationImpl] - Starting [Growl] broadcaster
2010-09-13 09:55:27,812 INFO [ApplicationImpl] - Starting [bluetooth] receiver
2010-09-13 09:55:27,827 DEBUG [bluetooth] - Java 1.4+ detected: 1.6.0_20; Java 
HotSpot(TM) Client VM; Sun Microsystems Inc.
2010-09-13 09:55:27,843 DEBUG [bluetooth] - Use stack ClassLoader
2010-09-13 09:55:27,843 DEBUG [bluetooth] - set dll dir 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0
2010-09-13 09:55:27,906 DEBUG [bluetooth] - Library loaded from 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\intelbth.dll
2010-09-13 09:55:27,906 DEBUG [bluetooth] - nativeDebugCallback ON
2010-09-13 09:55:27,906 DEBUG [bluetooth] - socket error [10047] An address 
incompatible with the requested protocol was used.
2010-09-13 09:55:27,906 DEBUG [bluetooth] - BluetoothStack detected 2
2010-09-13 09:55:27,921 DEBUG [bluetooth] - Use stack ClassLoader
2010-09-13 09:55:27,921 DEBUG [bluetooth] - tmp file 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\bluecove.dll
2010-09-13 09:55:27,984 DEBUG [bluetooth] - Library loaded from 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\bluecove.dll
2010-09-13 09:55:27,984 DEBUG [bluetooth] - nativeDebugCallback ON
2010-09-13 09:55:28,296 INFO [ApplicationImpl] - Adding to startup
2010-09-13 09:55:28,296 DEBUG [bluetooth] - open using BlueCove 
javax.microedition.io.Connector
2010-09-13 09:55:28,296 DEBUG [bluetooth] - connecting 
btspp://localhost:7674047e6e474bf0831f209e3f9dd23f;name=AndroidNotifierService
2010-09-13 09:55:28,734 DEBUG [bluetooth] - rfs(1) ServerOpen
2010-09-13 09:55:28,734 DEBUG [bluetooth] - serverSCN 1
2010-09-13 09:55:28,734 DEBUG [bluetooth] - rfs(1) acceptAndOpen
2010-09-13 09:55:28,734 DEBUG [bluetooth] - service_name assigned 
[AndroidNotifierService]
2010-09-13 09:55:28,734 DEBUG [bluetooth] - rfs(1) rf(2) RFCOMM server waits 
for connection

Server appears to be waiting - but sending test notification still does not work

Original comment by luke.a.i...@gmail.com on 13 Sep 2010 at 12:00

GoogleCodeExporter commented 8 years ago

well I got Android Notifier to successfully show up in Growl for Windows by 
selecting Allow Network Notifications in the Security options - see attachment 
for what it looks like

but if i send test notification from Galaxy S i still don't receive anything

2010-09-13 10:17:24,717 INFO [ApplicationImpl] - Starting SWT
2010-09-13 10:17:24,873 INFO [ApplicationImpl] - Showing tray icon
2010-09-13 10:17:24,967 INFO [ApplicationImpl] - Starting [Growl] broadcaster
2010-09-13 10:17:25,265 INFO [ApplicationImpl] - Starting [bluetooth] receiver
2010-09-13 10:17:25,296 DEBUG [bluetooth] - Java 1.4+ detected: 1.6.0_20; Java 
HotSpot(TM) Client VM; Sun Microsystems Inc.
2010-09-13 10:17:25,296 DEBUG [bluetooth] - Use stack ClassLoader
2010-09-13 10:17:25,312 DEBUG [bluetooth] - set dll dir 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0
2010-09-13 10:17:25,374 DEBUG [bluetooth] - Library loaded from 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\intelbth.dll
2010-09-13 10:17:25,374 DEBUG [bluetooth] - nativeDebugCallback ON
2010-09-13 10:17:25,374 DEBUG [bluetooth] - socket error [10047] An address 
incompatible with the requested protocol was used.
2010-09-13 10:17:25,374 DEBUG [bluetooth] - BluetoothStack detected 2
2010-09-13 10:17:25,390 DEBUG [bluetooth] - Use stack ClassLoader
2010-09-13 10:17:25,390 DEBUG [bluetooth] - tmp file 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\bluecove.dll
2010-09-13 10:17:25,499 DEBUG [bluetooth] - Library loaded from 
C:\DOCUME~1\abcdef~1\LOCALS~1\Temp\bluecove_abcdefgh_0\bluecove.dll
2010-09-13 10:17:25,499 DEBUG [bluetooth] - nativeDebugCallback ON
2010-09-13 10:17:25,765 INFO [GrowlNotificationBroadcaster] - Registered with 
GNTP server sucessfully
2010-09-13 10:17:25,828 INFO [ApplicationImpl] - Adding to startup
2010-09-13 10:17:25,828 DEBUG [bluetooth] - open using BlueCove 
javax.microedition.io.Connector
2010-09-13 10:17:25,828 DEBUG [bluetooth] - connecting 
btspp://localhost:7674047e6e474bf0831f209e3f9dd23f;name=AndroidNotifierService
2010-09-13 10:17:26,266 DEBUG [bluetooth] - rfs(1) ServerOpen
2010-09-13 10:17:26,266 DEBUG [bluetooth] - serverSCN 11
2010-09-13 10:17:26,266 DEBUG [bluetooth] - rfs(1) acceptAndOpen
2010-09-13 10:17:26,266 DEBUG [bluetooth] - service_name assigned 
[AndroidNotifierService]
2010-09-13 10:17:26,266 DEBUG [bluetooth] - rfs(1) rf(2) RFCOMM server waits 
for connection
2010-09-13 10:19:39,618 INFO [NotificationManagerImpl] - Waiting for test 
notification to pair device

Original comment by luke.a.i...@gmail.com on 13 Sep 2010 at 12:30

Attachments:

growl-android-desktop-notifier.png

GoogleCodeExporter commented 8 years ago

Issue 141 has been merged into this issue.

Original comment by rdamazio@gmail.com on 13 Sep 2010 at 9:54

GoogleCodeExporter commented 8 years ago

Bluetooth notifications are so intermittent. They will work for a few minutes, 
and while I keep pressing "Send Notification" they'll stop working. I'll have 
to restart my computer a couple times for bluetooth notification to "magically" 
work for a few minutes before I have to repeat the whole process over again. 
Nexus One -> Win7 64 bit

Original comment by saama...@gmail.com on 14 Sep 2010 at 12:44

GoogleCodeExporter commented 8 years ago

Sorry to add another chunk of log output to this bug, but the error messages 
I'm seeing are different from other others already here.  Hopefully it'll help.

My phone is a Nexus One running Android 2.2, build FRF91.  I'm using remote 
notifier 0.2.5 from the Market.

The particular thing I'm seeing that other people aren't is an IOException 
"Device or resource busy" during socket.connect().  Here's a snippet:

D/RemoteNotifier(  412): Got battery level: 87
D/RemoteNotifier(  412): Notifying of battery state change
D/RemoteNotifier(  412): Sending notification: 
v2/a201c3346d4403f9/8d436330a81719/BATTERY/87/Discharging, remaining charge: 87%
E/BluetoothService.cpp(   78): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
E/BluetoothService.cpp(   78): stopDiscoveryNative: D-Bus error in 
StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/RemoteNotifier(  412): Connecting to Bluetooth device camden-macbookpro
D/BluetoothService(   78): updateDeviceServiceChannelCache(60:FB:42:71:DA:90)
D/BluetoothService(   78): uuid(application): 
7674047e-6e47-4bf0-831f-209e3f9dd23f 1
D/BluetoothService(   78): Making callback for 
7674047e-6e47-4bf0-831f-209e3f9dd23f with result 1
D/RemoteNotifier(  412): Waiting to retry
D/RemoteNotifier(  412): java.io.IOException: Device or resource busy
D/RemoteNotifier(  412): at 
android.bluetooth.BluetoothSocket.connectNative(Native Method)
D/RemoteNotifier(  412): at 
android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:204)
D/RemoteNotifier(  412): at 
org.damazio.notifier.notification.BluetoothNotificationMethod.doSendNotification
(BluetoothNotificationMethod.java:162)
D/RemoteNotifier(  412): at 
org.damazio.notifier.notification.BluetoothNotificationMethod.sendNotification(B
luetoothNotificationMethod.java:99)
D/RemoteNotifier(  412): at 
org.damazio.notifier.notification.Notifier$1.run(Notifier.java:54)
V/BluetoothEventRedirector(  503): Received android.bleutooth.device.action.UUID

This happens every time on my device; no intermittent successes.  For each 
message, this same stack trace is delivered 11 times (one or each retry).  I've 
tried turning my adapter on/off, taking my phone in and out of discoverable 
mode, letting android-notifier turn on the adapter.  No dice.

I went digging through the code and did some web searching for the error 
message, and I don't immediately see the problem.  However, it does look 
related to this thread: 
http://groups.google.com/group/android-developers/browse_thread/thread/531639c4c
13a579b.  I don't *think* you should have to do anything different than you're 
doing now, but you might want to toss in a try { socket.close() } before 
calling connect(), just in case.

Original comment by cam...@gmail.com on 14 Sep 2010 at 3:00

GoogleCodeExporter commented 8 years ago

... and of course the moment I convinced myself that I was always seeing the 
exact same stack trace, I started getting a new one.  Now it's getting passed 
the connect() and dying during write():

D/RemoteNotifier( 4189): Waiting to retry
D/RemoteNotifier( 4189): java.io.IOException: Transport endpoint is not 
connected
D/RemoteNotifier( 4189): at 
android.bluetooth.BluetoothSocket.writeNative(Native Method)
D/RemoteNotifier( 4189): at 
android.bluetooth.BluetoothSocket.write(BluetoothSocket.java:317)
D/RemoteNotifier( 4189): at 
android.bluetooth.BluetoothOutputStream.write(BluetoothOutputStream.java:85)
D/RemoteNotifier( 4189): at java.io.OutputStream.write(OutputStream.java:82)
D/RemoteNotifier( 4189): at 
org.damazio.notifier.notification.BluetoothNotificationMethod.doSendNotification
(BluetoothNotificationMethod.java:163)
D/RemoteNotifier( 4189): at 
org.damazio.notifier.notification.BluetoothNotificationMethod.sendNotification(B
luetoothNotificationMethod.java:99)
D/RemoteNotifier( 4189): at 
org.damazio.notifier.notification.MethodEnablingNotifier.onTick(MethodEnablingNo
tifier.java:50)
D/RemoteNotifier( 4189): at 
android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:124)
D/RemoteNotifier( 4189): at android.os.Handler.dispatchMessage(Handler.java:99)
D/RemoteNotifier( 4189): at android.os.Looper.loop(Looper.java:123)
D/RemoteNotifier( 4189): at 
org.damazio.notifier.notification.Notifier$1.run(Notifier.java:63)

Original comment by cam...@gmail.com on 14 Sep 2010 at 3:26

GoogleCodeExporter commented 8 years ago

okay - i have updated to android-notifier-desktop 0.4.0 and remote-notifier 
0.2.6

getting closer

i send the test notification - and actually get a popup showing error

attached is the android-notifier-desktop.log

Protocol Version is not supported?

Original comment by luke.a.i...@gmail.com on 20 Sep 2010 at 12:53

Attachments:

android-notifier-desktop.log

GoogleCodeExporter commented 8 years ago

actually this is getting really close 

anytime my phone rings it connects via bluetooth to my pc - but i get a popup 
displaying an error

so bluetooth is connecting sweet - just the info isn't quite going through 
correctly

keep up the good work

Original comment by luke.a.i...@gmail.com on 20 Sep 2010 at 9:21

GoogleCodeExporter commented 8 years ago

Hi, 

This a cool and fun app.   But not quite there for me yet:

NexusOne + Froyo +  Remoter Notifier 0.2.6. 

Ferdora 13 32 bit + SUN Jdk 1.6.0_20-b02 + Desktop app 0.4.0  + GNOME 

Test ping from my hand set works about 1 out of 5 times. I have never actually 
gotten any other popups from rings or SMS or email arrival. 

The BLUEMAN Applet (and /var/log/message) indicate bluetooth activity when I do 
a test ping from handset.  

I can provide any sort of additional information you'd need -- I just don't 
know what is helpful..

Original comment by fred.wel...@gmail.com on 22 Sep 2010 at 8:10

GoogleCodeExporter commented 8 years ago

I am having the same issue with moto droid 1, osx 10.6.4.

I've paired the droid and the mac via bluetooth. Mac is discoverable. I turn on 
android notifier and it pops up with the following error: "An error occurred 
while setting up bluetooth to receive connections." I'm not sure what this is 
about because phone and computer are paired properly. When I send a test 
notification on the droid I can see the bluetooth connecting and receiving the 
information, but nothing happens.

I'm not a code monkey but if there's any troubleshooting I can do to help get 
this problem resolved I'm happy to do so!

Original comment by cryptic...@gmail.com on 23 Sep 2010 at 7:26

GoogleCodeExporter commented 8 years ago

cryptic318 - the problem you're reporting is a problem with the multiplatform 
client, it's not the same as this issue.

Original comment by rdamazio@gmail.com on 23 Sep 2010 at 7:31

GoogleCodeExporter commented 8 years ago

Thanks for the quick reply on that. You are absolutely correct, I had the 
multiplatform going instead of the native mac one. I switched and my problem is 
completely resolved.

Thank you !

Original comment by cryptic...@gmail.com on 23 Sep 2010 at 7:50

GoogleCodeExporter commented 8 years ago

This is not working at all.
Mac 10.6.4 .

Bluetooth is not working and if you are on a big LAN also WIFI dosent work.
I tried the multiplatform one and it fails to load the GUI?!?!

Uninstall...

Original comment by dek...@gmail.com on 28 Sep 2010 at 1:26

GoogleCodeExporter commented 8 years ago

The latest 0.2.8 APK fixed all my bluetooth issues. Crossing my fingers, but so 
far things look good =)

Original comment by saama...@gmail.com on 28 Sep 2010 at 5:08

GoogleCodeExporter commented 8 years ago

still the same as before 

Error handling bluetooth notification
Protocol version [] is not supported

Original comment by luke.a.i...@gmail.com on 28 Sep 2010 at 6:03

Attachments:

android-notifier-desktop.log

GoogleCodeExporter commented 8 years ago

Has anyone else seen 0.2.8 fixing their issue?

Original comment by rdamazio@gmail.com on 28 Sep 2010 at 10:30

GoogleCodeExporter commented 8 years ago

On Moto Droid, Android 2.2, APK 0.2.8 and MacDroidNotifier.app 0.2.8, still no 
luck.

Original comment by thetaco...@gmail.com on 28 Sep 2010 at 1:52

GoogleCodeExporter commented 8 years ago

wow at least test notifications work now. that is new!
will test more but for me it's better than ever

Original comment by peter.v...@gmail.com on 28 Sep 2010 at 3:28

GoogleCodeExporter commented 8 years ago

Gotta love it when bugs fix themselves without us doing anything :)

Original comment by rdamazio@gmail.com on 28 Sep 2010 at 5:48

GoogleCodeExporter commented 8 years ago

will test it more throughoutly during the day since it's there where I 
need/have BT. I saw an exception so there might be small things to fix but 
basically something comes through instead of plain nothing :)
encryption doesn't seem to work, I didn't find settings for that in AND only in 
the .apk but that's probably not BT encryption anyway so a different topic

Original comment by peter.v...@gmail.com on 28 Sep 2010 at 7:39

GoogleCodeExporter commented 8 years ago

AND doesn't support encryption yet (it will in the next release) - only the 
native mac client has it.

Original comment by rdamazio@gmail.com on 28 Sep 2010 at 8:24

GoogleCodeExporter commented 8 years ago

On HTC Hero with Android 2.2, APK 0.2.8 and AND 0.4.0 the same problem. No 
notifications send via BT, but in my company i can't connect via wifi to my 
desk. :-(
Log attached.

Original comment by marco.fu...@gmail.com on 29 Sep 2010 at 8:48

Attachments:

android-notifier-desktop.log

venliong / android-notifier

Bluetooth notifications not delivered #3