I am trying to make a tizen gear application in which I record accelerometer and gyroscope data of user activity for about an hour and give analytics based on this raw sensor data saved in a csv file.
I have a tizen wearable hybrid application. I am using native service application to retrieve sensor data, and further sending it to web application for writing into csv file.
Upon testing, I have observed that after few minutes of starting the data recording (after about 3-8 minutes) the sensor data is no longer received (seen from the logs in sensor_callback() function). Moreover, during the test scenarios, I have observed that SHealth application opens up and starts recording the dynamic workout activity of the user. Is it possible that SHealth application might be hindering my application from receiving sensor data? If yes, how could one possibly resolve this?
Thanks in advance.
Actually nothing can be say without seeing any code.
SHealth can be an issue but it is just a guess as you have not provided any logs that can show SHealth is an issue.
I will suggest you to follow the sensor app workflow properly from the below guide. The guides also provided sample app.
Accessing Heart Rate Monitor (HRM) Sensor data for Native applications
How to use Light Sensor in Tizen
Related
We are working on developing our own iOS app connecting with two Movesense sensors and fetching the acc, gyro and mag data. The app is going to be used for measurement of 8 hours, with 52 Hz. We'd like to collect both sensor time stamps and the phone time stamps, in order to make an accurate synchronisation of these two sensors. The default DFU settings seem to only give us sensor time stamps, which looks like this (example of only gyroscope data by Movesense Showcase app):
Should I modify the DFU, or is it possible to just state it in Xcode when getting the data package? I have tried to go through the available DFU packages and the .apk files as listed on the Movesense website. I am personally not familiar with the DFU programming, therefore we'd like to use one existing DFU package from Movesense, which is hopefully stable for the connection and data sampling.
You do not need to create your own firmware (DFU) for that. All the API's are available from the mobile phone, so just follow up the instructions given in this question & answer:
Android app dev: Finding the best way to synchronize the timestamps of two sensors
When recording using our Movesense Showcase app the situation is different since that app does not do multi sensor clock synchronisation. When recording with plain iOS Showcase app I would do "hit sensors together in the beginning and end of the recording" to synchronise the sensor data streams using the peak in acceleration. Then remember to treat the data streams as having different sample rates and base your analysis on the timestamps instead.
On the Instant Play Games site google recommends the following:
Integrate sign-in using Google Play Games Services and a cloud save
solution to preserve progress in the game.
However in this other document the following is stated:
If the player is using a device that runs Android 8.0 (API level 26)
or higher, and if your game specifies a targetSandboxVersion of 2,
then the player's progress is transferred automatically to the full
version of your game. Otherwise, you must transfer the data related to
player progress manually. To do so, use one of the following APIs...
So it seems that cloud saves are not needed, there exists a simple API for transferring progress to the main app. So why is cloud save recommended? Am I missing some aspect or restriction of instant apps?
I found at least one reason for this, which seems critical enough:
The instant app data does not persist over for example restarting the device. More info here.
I am working with real time tracking application using react-native.
And want the accuracy Uber and Swiggy and other tracking application do.
I am using react-native-geolocation-service, but not getting accuracy like Uber.
I just want to know how Uber track realtime? Does they request to server every single second?
Because there position is moving continuously, which is not possible in my app. I am saving coordinates after every 15 seconds.
Please suggest what can I use for making accurate path?
And what does Uber and other tacking apps used for tracking? And how they get realtime data for every single second?
For getting real time location you can use paid services like https://www.navixy.com/. I have used this service year ago and they are providin lot of functionalities track Android device with their API's.
Try Firebase Realtime database or cloud firestore. It works like realtime data update.
Store lat long on firestore/database whenever there is change in position and within a second you will be able to get those data on other end.
It is having nice performance when it comes to real time data update. I have used it with one of the native application before a year.
For react native, you can use Geolocation api which is having watchposition method. It will be invoked whenever there is location change.
Copied from the old forum:
Hello,
The app on the phone is good for analyzing the data from max 2-3 days.
I would like to have an access to the more detailed data on my computer.
Is there any way I can do that? Is there a tool for Windows 10, I could reach UP3 heart rate data? or sleep time?
Thank You in advance,
Agnieszka
As of now, Jawbone only provides mobile applications for iOS, Android, and Windows phones.
For retrieving UP user data on a non-mobile device, you have two options:
Download a CSV from the jawbone.com Settings page.
Use the UP APIs to retrieve the data you want.
I'm currently in the early stages of designing a cross-platform mobile app (iOS, Android, WP8). At its core, the application will allow proximity based interaction between an unknown number of client devices.
Could someone recommend a framework or technology that would allow me to push server generated location based proximity alerts to the clients that even scales well? Could push notifications (cross platform using PushSharp) be a viable option for this, or will Push notifications always go hand in hand with some kind of toast notification on the device?
Update: 30 seconds or even a minute delay should do.
Push Notifications have way to much latency to give you anything near real-time. Also Push Notifications are not guaranteed to reach a device.
You really need to think about how much time constrained the location updates should be. You should also make some tests with how fast the GPS on various devices updates. I have tested on a Nexus 4 and it is not near real-time either. So throughout your entire application whether it is server side or client side you will have things blowing your real-time wishes.
However IF you can live with a delay of a couple of seconds to maybe 30 seconds or more, Push Notifications my work well for you, they also scales quite nicely.
EDIT:
Push notifications always go hand in hand with some kind of toast
notification on the device?
There is a concept called RAW notifications, which allow you to send arbitrary information with the Notifications. However personally I would just notify the client about updates ready on a server, where it then can get all the information the application needs. This is because as I said Push Notifications are not guaranteed to ever reach the device, but also because you are limited to how much information you can embed in the Notifications.
So my suggestion for a flow would be:
Client A updates its location and sends it to a web service
Web Service receives info from Client A and prepares notifications for all the other Clients, which need information about Client A and pushes information about they need to update their info.
Client B receives a Push Notification telling it to refresh data from the Web Service and does that.
That would work well if the application is in a background state. When showing in the foreground I would simply poll a server every second or so; Still receiving Notifications just forcing the client to update.
For the "scales well" part, you might also want to take a look at Windows Azure Service Bus Notification Hubs. It's currently in preview and supports only Windows 8 Store apps and iOS but support for Android and Windows Phone is on the way.