You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
What brand device are you using?
I found that some devices would not show up using beacon tools app until the device was locked. It was a scary thought that locking the device meant I couldn't make changes and could mean the device would never work if I was still unable to find it, but for some reason it changed something and allowed it to be registered.
Maybe it takes it out of a diagnostic mode of some sort.
The alternative is using the Google beacon API to register the beacon using it's BeaconName (combo of namespace ID and instance ID). This should work provided that the beacon is broadcasting the instance and namespace ID's (you can check this with other beacon scanner tools Google's beacon tools app isn't great for this).
-helenclarko
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can anyone help me out about, Beacon configured as Eddystone EID is not even detected by Beacon Tool App.i am
Using Beacon Tool App on Android device.
The text was updated successfully, but these errors were encountered: