Open Phoscur opened 9 years ago
I'm unsure of your situation as described. As I understand it, beacons are specific types of BLE device (depending on the beacon being used) and have specifications you could mimic. I have experienced poor performance on android 4.x also, especially when not using stock firmware. iOS is more stable in this respect (but has a horrible non-specific UUID system to contend with).
Closing issue
Please reopen! Evothings peripheral Android API So adapters already support virtual beacons, will bleat too?
This library has turned into a web-bluetooth shim
to allow the web-bluetooth API to be used wherever there is JavaScript access to to a central device. As web-bluetooth only supports this mode, I've considered writing a similar library for peripheral abstraction.
I've not come across any solid peripheral API specifications, however. What API would it follow? Bleno? evothings?
Currently, I have to use a real beacon as the state holder, on which I constantly update a charactaristic to get a dynamic code I can scan with a portable device. I would make sense to use the situated device (android tablet) as a virtual beacon, but it seems impossible to get it working below android 5. What's your stand on this?