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.

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

Bluetooth notifications not delivered #3

Open
GoogleCodeExporter opened this issue Jan 29, 2016 · 187 comments
Open

Bluetooth notifications not delivered #3

GoogleCodeExporter opened this issue Jan 29, 2016 · 187 comments

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

This was referenced Jan 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant