-
Notifications
You must be signed in to change notification settings - Fork 834
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
Android 6.0.1 - security patch level 1 don't work #412
Comments
To clarify, it sounds like you are suggesting that this ASUS_Z00LD 6.0.1 OS image breaks scanning on the newer Android 5+ BLE scanning APIs. Correct? To confirm the library still works with the older 4.3 APIs, can you try adding the line:
And retesting to see if scanning works? I will note that I have successfully scanned beacons with the library using the Android L APIs on the Nexus 9 and Nexus 5X with 6.0.1. |
On the basis of my tests:
It would seem a problem connected to the permissions of Android 6. The code I used is: [copy and paste of android-beacon-library-reference project]
P.S. |
Ok, my app work if I set It is not the same for AltBeacon Loc. I have reinstalled him, but something goes wrong. I'm happy to have solved, but I really feel AltBeacon Loc does not work. Thank You! |
Expected behavior
Scanning for detect the beacons nearby and getting information.
Actual behavior
The scanning start but on didRangeBeaconsInRegion anybody beacon is detected.
The method onRequestPermissionsResult is correctly set.
The Bluetooth work correctly in other applications (Bluetooth LE Scanner) that use classic onLeScan(...) method.
Other test: Locate application don't detect nothing.
Test with Locate:
no change detected...
Steps to reproduce this behavior
Start application e start scanning, but the size of the variable beacons of "final Collection beacons" is always zero.
Mobile device model and OS version
ASUS_Z00LD (http://specdevice.com/showspec.php?id=9275-2ed6-b72b-0cbf5429c89f), Android 6.0.1 - security patch level 1, API 23
Android Beacon Library version
2.9
The text was updated successfully, but these errors were encountered: