Open guillaumelachaud opened 6 years ago
The library is not yet updated to allow the notification for the service on 8.0. So, even though you get back the relevant events there is no actual BLE transmission started. Interesting. Does Beacon Toy behave the same when trying to start a beacon?
I just tried Beacon Toy and yes, it does behave the same. Note that I also tried Beacon Simulator (https://play.google.com/store/apps/details?id=net.alea.beaconsimulator) and had the same results.
Are you sure the S8 can detect other beacons? The only API updates in Oreo relate to Bluetooth 5.0 support for extended advertising (up to 251 bytes using data channel multiplexing).
I don't have physical beacons to try with unfortunately. If you have any ideas on how I can make sure the problem isn't with the S8, I'll be more then happy to try them.
On Tue, Jan 2, 2018, 20:13 Adrian Crețu notifications@github.com wrote:
Are you sure the S8 can detect other beacons? The only API updates in Oreo relate to Bluetooth 5.0 support for extended advertising (up to 251 bytes using data channel multiplexing).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/uriio/beacons-android/issues/3#issuecomment-354924367, or mute the thread https://github.com/notifications/unsubscribe-auth/AB-tcaoQ9mt6oEQYeq17pksuczwKQMsuks5tGuJTgaJpZM4RQ2VT .
And it does detect beacons created from an other S8 so this is why I am suspecting the pixel to be the problem.
On Tue, Jan 2, 2018, 20:15 Guillaume LACHAUD guillaume.lachaud@gmail.com wrote:
I don't have physical beacons to try with unfortunately. If you have any ideas on how I can make sure the problem isn't with the S8, I'll be more then happy to try them.
On Tue, Jan 2, 2018, 20:13 Adrian Crețu notifications@github.com wrote:
Are you sure the S8 can detect other beacons? The only API updates in Oreo relate to Bluetooth 5.0 support for extended advertising (up to 251 bytes using data channel multiplexing).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/uriio/beacons-android/issues/3#issuecomment-354924367, or mute the thread https://github.com/notifications/unsubscribe-auth/AB-tcaoQ9mt6oEQYeq17pksuczwKQMsuks5tGuJTgaJpZM4RQ2VT .
That logcat is suspiciously referencing BLE GATT connections. Usually a BLE chip will not advertise while there is an active GATT connection in progress. Do you have accessories that are connecting to your Pixel somehow?
I don't think so. The Bluetooth icon isn't showing as "connected", my headphones are off, I tried rebooting my device,...
On Tue, Jan 2, 2018, 20:22 Adrian Crețu notifications@github.com wrote:
That logcat is suspiciously referencing BLE GATT connections. Usually a BLE chip will not advertise while there is an active GATT connection in progress. Do you have accessories that are connecting to your Pixel somehow?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/uriio/beacons-android/issues/3#issuecomment-354925187, or mute the thread https://github.com/notifications/unsubscribe-auth/AB-tcTyN3chGzCqdhIKyaEL01fubf-Ljks5tGuRWgaJpZM4RQ2VT .
AOSP Oreo 8.1r1 on a Nexus 6 behaves as expected, beacons can be created and even the service works correctly, waking up at the correct time in case of refreshable beacons such as EID.
I'll release shortly a new library version that compiles against the latest SDK, so that the notification works without the app crashing when targeting API 26 or later. But that doesn't fix your issue, which is likely an app on the Pixel that is interfering with the BLE stack.
I am trying to use the library to broadcast a Beacon from my Google Pixel XL running Android 8.1. I am facing two issues:
Logcat excerpt: