Android (Things) GATT server stops advertising

Question

I'm developing an Android Things app (Dev Preview 6.1, Raspberry Pi) with a GATT server. When a connected client app disconnects, my device has stopped advertising. However, the custom client app (out of my control) is written in such a way that it needs to disconnect between reads/writes, then reconnect.

I know that I can restart advertising upon disconnect, but since it has a new (pseudo-)MAC address, the client can't automatically reconnect.

FWIW, I see the same behavior in this sample (& using nRF Connect as a test clinet): https://github.com/androidthings/sample-bluetooth-le-gattserver

Is there way to keep the GATT server advertising in this case? Or can I specify the advertised device address so that I can keep it consistent across advertisements?

This question may be related: https://stackoverflow.com/questions/47676988/the-device-gattserver-stops-advertising-after-connecting-to-it — Nick Felker, Feb 18 '18 at 19:30

score 1 · Answer 1 · answered Feb 19 '18 at 20:23

1

It turns out this is a known bug in Android Things: https://issuetracker.google.com/issues/70269277

answered Feb 19 '18 at 20:23

David Chase

31
4

1

@ThomasSmyth I think that this is an actual answer - the answer is that "this is a known bug" and the link is there to provide evidence for that. – EJoshuaS - Stand with Ukraine Feb 19 '18 at 22:02

Android (Things) GATT server stops advertising

1 Answers1