Comments (187)
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 [email protected]
on 2 Feb 2010 at 2:31
- Changed state: Accepted
- Added labels: OpSys-Android
Attachments:
from android-notifier.
Patch reviewed and appears to work in my device, submitted as r67
Original comment by [email protected]
on 2 Feb 2010 at 2:41
from android-notifier.
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 [email protected]
on 7 Feb 2010 at 12:35
from android-notifier.
Apparently r72 introduced a bug which breaks all delayed notifications.
Preparing
another fix.
Original comment by [email protected]
on 18 Feb 2010 at 12:29
from android-notifier.
Maybe, just maybe, r83 will fix what you're experiencing. Please update from
the market
and let me know.
Original comment by [email protected]
on 22 Feb 2010 at 1:59
from android-notifier.
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 [email protected]
on 12 Mar 2010 at 10:50
from android-notifier.
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 [email protected]
on 15 Mar 2010 at 3:14
from android-notifier.
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 [email protected]
on 24 Mar 2010 at 4:53
from android-notifier.
Test notifications and regular notifications both are not received (tho phone
reports
they are sent)
Original comment by [email protected]
on 24 Mar 2010 at 7:52
from android-notifier.
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 [email protected]
on 24 Mar 2010 at 8:10
from android-notifier.
Raising the priority since more people are reporting the issue.
Original comment by [email protected]
on 24 Mar 2010 at 8:11
- Added labels: Priority-High
- Removed labels: Priority-Medium
from android-notifier.
Bruno has a Nexus One and was able to reproduce it. He has kindly volunteered
to
investigate and fix the problem.
Original comment by [email protected]
on 25 Mar 2010 at 2:28
from android-notifier.
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 [email protected]
on 30 Mar 2010 at 8:09
from android-notifier.
Ping? Any logs?
Original comment by [email protected]
on 7 Apr 2010 at 6:05
- Added labels: Component-Communication, Stability
from android-notifier.
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 [email protected]
on 7 Apr 2010 at 5:35
from android-notifier.
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 [email protected]
on 13 Apr 2010 at 11:31
Attachments:
from android-notifier.
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 [email protected]
on 14 Apr 2010 at 2:12
Attachments:
from android-notifier.
Works :) Thanks!
Original comment by [email protected]
on 14 Apr 2010 at 7:08
from android-notifier.
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 [email protected]
on 14 Apr 2010 at 8:05
from android-notifier.
What this new binary does it just try again (up to 10 times) if sending the
notification fails.
Original comment by [email protected]
on 14 Apr 2010 at 9:21
from android-notifier.
Does this app generate a log file I can drop on here for your review?
Original comment by [email protected]
on 14 Apr 2010 at 9:51
from android-notifier.
Yes it does. To get the log you have to use an app such as alogcat (available
from the market).
Original comment by [email protected]
on 14 Apr 2010 at 11:31
from android-notifier.
[deleted comment]
from android-notifier.
Same here with moto droid user using a custom rom. Wifi works fine though.
Original comment by [email protected]
on 28 Apr 2010 at 8:36
from android-notifier.
Does this still happen after the 0.2.5 update of the mac app (please choose
check for updates from the menu, I
posted the update yesterday) and version 0.2.3 of the android app?
Original comment by [email protected]
on 28 Apr 2010 at 9:08
from android-notifier.
Still failing to get the message, though I'm getting an interesting new error
in my
console app:
4/28/10 2:18:26 PM kernel IOMemoryDescriptor: attempt to create 32b virtual in
64b
task, use ::withAddressRange()
4/28/10 2:18:26 PM kernel Backtrace 0x430605 0x4304f5 0x42ff40 0x54df97f3
0x54df96bd
0x54df8fec 0x427525
4/28/10 2:18:26 PM kernel Kernel loadable modules in backtrace (with
dependencies):
4/28/10 2:18:26 PM kernel
com.apple.iokit.IOBluetoothFamily(2.1.9f10)@0x54dd0000->0x54e09fff
I should note: I don't appear to be running the 64 bit OS (at least it's not
explicitly saying I am in About). Also, I'm still running on 10.5.8 here.
Original comment by [email protected]
on 28 Apr 2010 at 9:25
from android-notifier.
Just downloaded this, and I'm having problems. I got everything installed, but
notifications aren't being sent
over bluetooth. I'm not somewhere that I can try WiFi for sure, but creating a
network with "Internet Sharing"
on my Macbook Pro doesn't work.
Here are relevant log entries from the Bluetooth attempts:
05-03 00:12:42.030 D/RemoteNotifier( 1314): Connecting to Bluetooth device owing
05-03 00:12:42.135 D/RemoteNotifier( 1314): Waiting to retry
05-03 00:12:42.135 D/RemoteNotifier( 1314): java.io.IOException: Service
discovery failed
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:377)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:201)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
org.damazio.notifier.notification.BluetoothNotificationMethod.doSendNotification
(BluetoothNotificationMethod
.java:163)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
org.damazio.notifier.notification.BluetoothNotificationMethod.sendNotification(B
luetoothNotificationMethod.ja
va:99)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
org.damazio.notifier.notification.MethodEnablingNotifier.onTick(MethodEnablingNo
tifier.java:50)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:124)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
android.os.Handler.dispatchMessage(Handler.java:99)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
android.os.Looper.loop(Looper.java:123)
05-03 00:12:42.135 D/RemoteNotifier( 1314): at
org.damazio.notifier.notification.Notifier$1.run(Notifier.java:63)
05-03 00:12:42.143 V/BluetoothEventRedirector( 1075): Received
android.bleutooth.device.action.UUID
05-03 00:12:42.308 D/BluetoothService( 1017): Registering opush record
05-03 00:12:42.338 E/BluetoothEventLoop.cpp( 1017): event_filter: Received
signal
org.bluez.Adapter:PropertyChanged from /org/bluez/1392/hci0
05-03 00:12:42.807 D/BluetoothService( 1017): Registering pbap record
And then it repeats. I hope this is relevant to this thread. Let me know if I
should post somewhere else.
Original comment by [email protected]
on 3 May 2010 at 4:31
from android-notifier.
Thanks for the log, it definitely helps.
Good news is, I just updated my milestone to 2.1-update1, so I'm hoping that
I'll be able to reproduce these
issues more easily.
Original comment by [email protected]
on 3 May 2010 at 5:18
from android-notifier.
Forgot to mention. I'm using Moto Droid 2.1-update1 and Macbook Pro with
10.5.8. Both phone app and
laptop app are newest version.
I have my phone and laptop paired. Notifier is set to do bluetooth with my
laptop as the target. Laptop has
bluetooth on (and it connects when a message is trying to be sent). Laptop
application settings are: Bluetooth
only, all "Display in Growl" on, Receive notifications from any device. This
application generates no logs during
test message.
Is there anything additional you need from me?
Original comment by [email protected]
on 3 May 2010 at 4:54
from android-notifier.
Can't get the bluetooth notifications working on Froyo (Nexus One).
Tried updating to the attached apk, didn't help.
W/Settings( 5997): Setting android_id has moved from
android.provider.Settings.System to
android.provider.Settings.Secure, returning read-only value.
D/RemoteNotifier( 5997): Sending notification:
e3dcc85417e9d0a4/4246a74c55603/PING/Test notification
E/BluetoothService.cpp( 78): stopDiscoveryNative: D-Bus error in
StopDiscovery: org.bluez.Error.Failed
(Invalid discovery session)
E/RemoteNotifier( 5997): Unable to find bluetooth device 'any' to send
notifications to
Original comment by lahdekorpi
on 31 May 2010 at 9:00
from android-notifier.
Hi. I have this Issue too. After sending notification from phone, it's
connectiong device.. and then disconnect.. but there is no notification... It's
work for tcp/udp.. but not for bluetooth. My device is HTC-Hero with VillianRom
(Android 2.1), an computer is MacBooc Pro.
Doyou need some more feedback? Some more logs or something?
Original comment by [email protected]
on 7 Aug 2010 at 5:08
from android-notifier.
Yes, please send logs, I'm still unable to reproduce this on my Nexus One (2.2)
or Motorola Milestone (2.1).
The app has a report bug option which will copy logs to the clipboard
automatically. The mac app outputs logs which you can see in the Console app
(under Applications > Utilities).
Can you also confirm the android and mac app versions you're using?
Also, a few more questions: does this happen for test notifications too? Are
you selecting the specific bluetooth device to send to, or are you using "Any"?
Thanks, and sorry for not having solved this one yet.
Original comment by [email protected]
on 7 Aug 2010 at 7:38
- Changed title: Bluetooth notifications not delivered
- Added labels: Priority-Critical
- Removed labels: Priority-High
from android-notifier.
Issue 21 has been merged into this issue.
Original comment by [email protected]
on 7 Aug 2010 at 7:39
from android-notifier.
Still trying to figure this one out. If anyone here happens to be a bluetooth
expert, please let me know. Otherwise, I'm keeping some findings here:
1) Apparently this stops happening if I put the mac in discoverable mode (can
someone confirm if discovery mode fixes it for them as well?). It's quite hard
to make it *start* happening again, though, meaning I'm still having trouble
reproducing.
2) (1) suggests that it's an issue with the phone finding the bluetooth service
on the computer. The fact that it starts working with discoverable mode
suggests that SDP on the device is caching information sent by the Mac's SDP,
and not properly updating it (e.g. maybe the app started while the phone had
bluetooth off or wasn't in range, so the mac broadcast a service update but the
phone never received it). Can someone confirm if doing the bluetooth pairing
(bluetooth, not the app's pairing) AFTER the app is already running changes
anything?
3) SDP registration is done by a weird-format plist file, which I don't fully
understand. I tried making Android itself expose an RFCOMM service, assuming
that it'd always be able to connect to a service declared in the same way it
exposes.
The service exposed by Android had two entries:
{
0x0000 = uint32(65544),
0x0100 = string(My Test),
0x0005 = { uuid16(10 02) },
0x0001 = { uuid128(e8 d5 15 b4 47 c1 48 13 b6 d6 3e ab 32 f8 95 3e) },
0x0004 = { { uuid16(01 00) }, { uuid16(00 03), uint8(24) } }
},
{
0x0000 = uint32(65545),
0x0100 = string(My Test),
0x0005 = { uuid16(10 02) },
0x0001 = { uuid128(e8 d5 15 b4 47 c1 48 13 b6 d6 3e ab 32 f8 95 3e) },
0x0004 = { { uuid16(01 00) }, { uuid16(00 03), uint8(3) } }
}
(all exactly the same except for attribute 4)
The one I'm exposing on the Mac side is the following (based on Apple's
example):
0x0000 = 0x00010005,
0x0100 = "rdamazio AndroidNotifierService",
0x0005 = { <1002> },
0x0001 = { <7674047e6e474bf0831f209e3f9dd23f> },
0x0004 = { { <0100> }, { <0003>, 0x04 } }
0x0009 = { { <0dad43655df111d69f6e00039353e858>, 0x0100 } },
0x0006 = { 0x656e, 0x006a, 0x0100 },
0x0303 = { 0xff },
which has also a different attribute 4, in addition to 3 extra attributes (9,
6, 303). (the UUID is different because I made it so)
Does anyone have any idea what the effect of these attributes is?
Can you guys try these 2 possible solutions (discoverable, and pairing after
the app is running) and let me know if it fixes the problem? If any of those
do, I can look for a more user-friendly solution.
Thanks
Original comment by [email protected]
on 23 Aug 2010 at 3:28
from android-notifier.
Issue 23 has been merged into this issue.
Original comment by [email protected]
on 23 Aug 2010 at 5:06
from android-notifier.
Issue 10 has been merged into this issue.
Original comment by [email protected]
on 23 Aug 2010 at 5:08
from android-notifier.
Hi there
I have a HTC Wildfire
Wildfire claims bluetooth messages sent - but they never appear.
Have a coding history so happy to help beta test / trouble shoot. Discovery
mode does not seem to help me.
Original comment by [email protected]
on 7 Sep 2010 at 6:36
from android-notifier.
Discovery mode does not help me either. I believe that the problem lies with
the computer service. My computer is receiving the test notifications, but it's
not displaying them for some reason.
Phone: Motorola Droid (Froyo)
Computer: Dell XPS m1330, Ubuntu 10.04
Output of "lsusb | grep -i blue":
Bus 003 Device 028: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 003 Device 027: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of
BCM2046 Bluetooth)
Original comment by [email protected]
on 7 Sep 2010 at 11:08
from android-notifier.
Hi,
I get the notification via Bluetooth but after 10-20 seconds. It's OK for
anything except for call notifications.
Phone: N1, CyanogenMod 6
Android Notifier: 0.2.4
Computer: Mac, 10.6.4
Android Notifier: 0.2.6
Original comment by [email protected]
on 8 Sep 2010 at 8:50
from android-notifier.
I have this same issue where the phone and Mac are paired, and the Bluetooth
notification is going out, and Bluetooth preferences on the Mac show it being
received, but Growl itself is not displaying a notification. Is there something
wrong with the formatting of the notification?
Original comment by [email protected]
on 8 Sep 2010 at 4:36
from android-notifier.
I was having trouble sending notifications as well, but after removing the
device pairing from both my laptop and phone and repairing them, it seems to be
working fine.
Original comment by [email protected]
on 9 Sep 2010 at 12:48
from android-notifier.
Issue 53 has been merged into this issue.
Original comment by [email protected]
on 9 Sep 2010 at 1:05
from android-notifier.
Issue 58 has been merged into this issue.
Original comment by [email protected]
on 9 Sep 2010 at 12:32
from android-notifier.
Im not sure im having the same problem in this thread but its similar. Im using
an Evo 2.2, with a MBP 10.6, my bluetooth settings show it not connected but
paired and only connected for a few seconds before it disconnects again. It
seems to me this is an issue on the phone, maybe with froyo?
Original comment by [email protected]
on 9 Sep 2010 at 4:13
from android-notifier.
@chicago yea sounds like my issue on incredible w/ 2.2. does your WiFi
notification work if your WiFi isn't turned on, but WiFi set to turn on for
notification push?
Original comment by [email protected]
on 9 Sep 2010 at 4:29
from android-notifier.
@Loesch, I have not tested it wifi, my wifi is a battery drainer and I really
cant wait for the usb interface, but no I have not even tried wifi, I will
later when I get home, but im not going to mess around in the office network
Original comment by [email protected]
on 9 Sep 2010 at 4:38
from android-notifier.
@chicago yea my WiFi is the same. There is an option in the WiFi menu that
enables the program to just turn on the WiFi for a second to send the
notification, then turn it off, but as far as battery use I donno because this
won't work either. Let me know what ya find out tonight tho.
Original comment by [email protected]
on 9 Sep 2010 at 5:04
from android-notifier.
[deleted comment]
from android-notifier.
I can't get notifications to work either, for both Wifi and Bluetooth
HTC Incredible, android 2.2
Windows 7
Original comment by [email protected]
on 9 Sep 2010 at 5:31
from android-notifier.
Im willing to bet this is an issue with Froyo, or the bluetooth settings on the
Evo/froyo, Im trying to see if my buddys iphone will stay connected as well
Original comment by [email protected]
on 9 Sep 2010 at 6:03
from android-notifier.
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 [email protected]
on 9 Sep 2010 at 6:14
from android-notifier.
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 [email protected]
on 9 Sep 2010 at 6:16
from android-notifier.
Also not getting notifications to work correctly - Wifi and Bluetooth.
HTC Droid Incredible, Android 2.2
Macbook Pro
Original comment by [email protected]
on 9 Sep 2010 at 6:16
from android-notifier.
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 [email protected]
on 9 Sep 2010 at 6:17
from android-notifier.
Issue 73 has been merged into this issue.
Original comment by [email protected]
on 9 Sep 2010 at 7:24
from android-notifier.
@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 [email protected]
on 9 Sep 2010 at 7:25
from android-notifier.
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 [email protected]
on 9 Sep 2010 at 8:28
from android-notifier.
@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 [email protected]
on 9 Sep 2010 at 8:51
from android-notifier.
hi, i'm on PC, Linux ( Ubuntu AMD 64 ). Everything is ok, except the android
notifier apparently don't process
Original comment by [email protected]
on 9 Sep 2010 at 8:55
from android-notifier.
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 [email protected]
on 9 Sep 2010 at 11:04
from android-notifier.
Issue 85 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2010 at 3:03
from android-notifier.
Issue 80 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2010 at 2:51
from android-notifier.
Issue 100 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2010 at 5:23
from android-notifier.
Issue 102 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2010 at 5:26
from android-notifier.
Issue 86 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2010 at 5:32
from android-notifier.
Issue 104 has been merged into this issue.
Original comment by [email protected]
on 10 Sep 2010 at 5:42
from android-notifier.
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 [email protected]
on 10 Sep 2010 at 6:34
from android-notifier.
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 [email protected]
on 10 Sep 2010 at 7:51
from android-notifier.
tried the updated apk 0.2.5, same result =(
Original comment by [email protected]
on 10 Sep 2010 at 8:00
from android-notifier.
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 [email protected]
on 10 Sep 2010 at 8:11
from android-notifier.
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 [email protected]
on 10 Sep 2010 at 8:46
from android-notifier.
Issue 113 has been merged into this issue.
Original comment by [email protected]
on 11 Sep 2010 at 12:03
from android-notifier.
Issue 112 has been merged into this issue.
Original comment by [email protected]
on 11 Sep 2010 at 12:03
from android-notifier.
HTC EVO WiFi works well but bluetooth has not corked at all...
Original comment by [email protected]
on 11 Sep 2010 at 3:49
from android-notifier.
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 [email protected]
on 11 Sep 2010 at 5:57
from android-notifier.
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 [email protected]
on 11 Sep 2010 at 10:28
from android-notifier.
Issue 123 has been merged into this issue.
Original comment by [email protected]
on 12 Sep 2010 at 5:12
from android-notifier.
Issue 91 has been merged into this issue.
Original comment by [email protected]
on 12 Sep 2010 at 6:01
from android-notifier.
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 [email protected]
on 13 Sep 2010 at 12:00
from android-notifier.
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 [email protected]
on 13 Sep 2010 at 12:30
Attachments:
from android-notifier.
Issue 141 has been merged into this issue.
Original comment by [email protected]
on 13 Sep 2010 at 9:54
from android-notifier.
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 [email protected]
on 14 Sep 2010 at 12:44
from android-notifier.
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 [email protected]
on 14 Sep 2010 at 3:00
from android-notifier.
... 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 [email protected]
on 14 Sep 2010 at 3:26
from android-notifier.
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 [email protected]
on 20 Sep 2010 at 12:53
Attachments:
from android-notifier.
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 [email protected]
on 20 Sep 2010 at 9:21
from android-notifier.
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 [email protected]
on 22 Sep 2010 at 8:10
from android-notifier.
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 [email protected]
on 23 Sep 2010 at 7:26
from android-notifier.
cryptic318 - the problem you're reporting is a problem with the multiplatform
client, it's not the same as this issue.
Original comment by [email protected]
on 23 Sep 2010 at 7:31
from android-notifier.
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 [email protected]
on 23 Sep 2010 at 7:50
from android-notifier.
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 [email protected]
on 28 Sep 2010 at 1:26
from android-notifier.
The latest 0.2.8 APK fixed all my bluetooth issues. Crossing my fingers, but so
far things look good =)
Original comment by [email protected]
on 28 Sep 2010 at 5:08
from android-notifier.
still the same as before
Error handling bluetooth notification
Protocol version [] is not supported
Original comment by [email protected]
on 28 Sep 2010 at 6:03
Attachments:
from android-notifier.
Has anyone else seen 0.2.8 fixing their issue?
Original comment by [email protected]
on 28 Sep 2010 at 10:30
from android-notifier.
On Moto Droid, Android 2.2, APK 0.2.8 and MacDroidNotifier.app 0.2.8, still no
luck.
Original comment by [email protected]
on 28 Sep 2010 at 1:52
from android-notifier.
wow at least test notifications work now. that is new!
will test more but for me it's better than ever
Original comment by [email protected]
on 28 Sep 2010 at 3:28
from android-notifier.
Gotta love it when bugs fix themselves without us doing anything :)
Original comment by [email protected]
on 28 Sep 2010 at 5:48
from android-notifier.
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 [email protected]
on 28 Sep 2010 at 7:39
from android-notifier.
AND doesn't support encryption yet (it will in the next release) - only the
native mac client has it.
Original comment by [email protected]
on 28 Sep 2010 at 8:24
from android-notifier.
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 [email protected]
on 29 Sep 2010 at 8:48
Attachments:
from android-notifier.
Related Issues (20)
- Enter one-line summary
- keeps crashing
- Services can't keep alive eventhough the notification icon is on.
- bt notifier
- fake package
- w
- Send notification to email
- puk code for smart watch HOT 1
- No text sent/received
- BT notifier not working
- Telefone não liga a tela.
- Code review request
- can't connect to smart watch
- Code review request
- Not sending notifications
- via bt Not working
- Enter one-line summary
- not working good
- Some messages won't display on computer
- smart phone will not stay paired to make a call or us my photos or messages
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from android-notifier.