On my desk there are two beacons set up with Eddystone URLs.
The manufacturer's app (Estimote) can see both beacons.
On the same device, Chrome's Physical Web reports "No nearby Physical Web pages found". The device is Sony Experia E2535, with Android 5.0, Chrome 52.
Physical Web app detects and displays both beacons.
What are my debugging/investigation options to establish why Physical Web doesn't display the beacons?
use verify.physical-web.org on the URLs that you've set in each beacon. It diagnoses most reasons why the beacons don't show up.
My solution, on Scott Jenson's advice (via github), was to update Google Play Services (in Google Play).
Related
I'm using an app that uses Bluetooth low energy to scan and detect devices however it does not detects other phones
is there a specific way on flutter to make it detect other mobile phones
You can only detect BLE devices that are advertising their services. A mobile phone often does not do that on its own. There are two solutions:
Use an already available app on the other device to advertise some service. One of the possible apps I personally use is nRF Connect, another one would be BLE Peripheral.
This might not be sufficient depending on your project and goal this might not be sufficient. If you need some specific service or characteristic that can't be generated by pre-existing apps you have to develop your own app for advertising. This would be possible with flutter_ble_peripheral (limited functionality on iOS)
I have tried web Bluetooth API to access,but it is only for battery status, heart rate etc.., I need to access complete functionality of Bluetooth. Is there any option or API available
I think there is no other available API for this bluetooth function, The Web Bluetooth API is your only option, but it is not finalized yet.
According to this documentation, until now, the ability to interact with bluetooth devices has been possible only for native apps. The Web Bluetooth API aims to change this and brings it to web browsers as well. Alongside efforts like Physical Web, people can walk up to and interact with devices straight from the web.
And even though it is not finalized yet, the Chrome Team is actively looking for enthusiastic developers to try out this work-in-progress API and give feedback on the spec and feedback on the implementation.
Just take note that Web Bluetooth
API is currently
available to be enabled experimentally on your origin in Origin
Trials, or locally on your machine using an experimental flag. The
implementation is partially complete and currently available on Chrome
OS, Chrome for Android M, Linux, and Mac.
For more information, just read these documentation and video. You can also check the updates of the documents here.
Sonys website of the NSZ-GS7 devices says "There's also a 3-Axis motion sensor for gaming." in the description of the controller.
http://store.sony.com/webapp/wcs/stores/servlet/ProductDisplay?langId=-1&storeId=10151&catalogId=10551&productId=8198552921666462151
But when I ask the SensorManager for a list of sensors like on any other android device, there are none. Do I miss something here?
Sadly, the google page on Google TV supported features tells me that no sensors are supported, too.
https://developers.google.com/tv/android/docs/gtv_android_features#Hardware
So, any idea whats going on here? Is the Sony website lying? Or is there a motion sensor inside this device but not exposed by the OS? whats the point of a sensor you can't use, then? Will it work in future Google TV versions?
Sony support seems not to like me, as they answered none of this quaestions :(
Sony developed proprietary API's for their devices to allow developers to get access to sensor data from their physical remotes or the Sony MediaRemote app. You need to integrate their libraries into your app to get to use these API's. Sony has a developer web site with more information: https://android.developer.sony.com/pages/documents/view/?id=4000080
Just be aware that other Google TV devices do not support these API's.
I'm looking to write some Android or iOS applications to access a Bluetooth heart-rate monitor. There are currently some apps available like Android's "Heart Rate Monitor" that connect to heart-rate monitors like the Zephyr HxM, so I know it can be done.
What is the programming API like? If I write an app, would it be able to connect to any heart-rate device? Or would I have to follow some application-layer protocol from the device manufacturer and read and process Bluetooth packets?
Many of the bluetooth enabled Heart-rate monitors supports the SPP profile and you can use the Android Bluetooth SPP socket APIs to access the device.
The Android chat example is a good application to modify to start with.
During the I/O 2011 Building Android Apps for Google TV session (at 37:50 in the YouTube video) Googlers TV guys have said: "Probably not the accelerometer"... Actually why not? What about an accelerometer inside the remote-controller (and there is already one if you use your phone/tablet as a remote-controller)? Just imagine playing a 1st person car racing game on your TV using your remote as a driving-wheel (Wiimote style) !
As far as I can understand this will be doable, but it will require two different android apps: One for Google TV and one running on what you are using as a controller (tablet/phone).
The controller app would then use the acceleromter functionality and communicate with Google TV in the same way as the official remote.
Take a look at an android application I wrote called "iCruZn." It uses the accelerometers in your android phone to control Google Earth on your dekstop. iCruZn transmits the accelerometer data over WiFi to a browser on your desktop running Google Earth. You can use this same mechanism to control an application your write for the Google TV. The only reason iCruZn won't work with Google TV is because the Google Earth Plugin is not compatible with the Google TV Chrome browser.
Looks like new Sony TV has accelerometer in its remote -
http://www.techradar.com/news/television/hands-on-sony-nsz-gs7-review-1063737