Status Update
No update yet.
Comments
st...@google.com
st...@google.com
Hello,
I'm only a little familiar with Power Apps. Is your app a mobile app or a web app?
This link
The primary
If your app does not work on Android mobile devices, you can also consider the
th...@gmail.com
st...@google.com
Sorry, there's no update. I haven't tested on more recent hardware or OS version but I don't believe the behavior has changed. Reassigning since I'm not working on this anymore.
a....@samsung.com
Hello, we are experiencing this issue using the latest Samsung galaxy watch binaries using the attached code sample.
br...@google.com
Are you able to specify how you are testing the fall event with real sensors?
Specifically I am wondering if the device is being dropped, or if it remains on the wrist.
th...@gmail.com
What can we do here? Any UPDATES? Is there any alternative we can use to resolve this as this solution will be used by our end users.
Description
SDK Version used: 0.1.33
Devices/Android versions reproduced on: Samsung Galaxy Watch 4 and 5
We integrated WHS EAP library version 0.1.33 inside our app developed for Wear devices (version 3).
If we enable on a real device synthetic data providers, HealthEventType are correctly raised and sent to our BroadcastReceiver. For example, to simulate a fall we run this command:
```shell
$ adb shell am broadcast \
-a "whs.synthetic.user.FALL_OVER" \
com.google.android.wearable.healthservices
If we reset the device to use sensor providers, the fall event is never raised.
We saw in system logs of Samsung Galaxy Watch 4 and 5 devices that devices are detecting a fall (log entries containing "fall detection event" and "FallClassifier_Recognize" appear), but the event is not raised and received by our BroadcastReceiver.
Thanks