Eric
Do not send private messages with technical questions; they will be discarded. All technical questions must be posted publicly on the forum.
About
- Username
- Eric
- Joined
- Visits
- 9,275
- Last Active
- Roles
- Administrator
Comments
-
The email goes to whatever address you want. It simply runs whatever app you want to use to handle the email Intent.
-
I haven't had any issues with the launcher icon in the library but yes, it is pointless to have it in a library so it will be removed.
-
No, you can definitely hold more than 36 entries. Try a logging session after resetting the board. MetaWear is using Bluetooth 4.0. We may upgrade to the newer standard somewhere down the line but there is no benefit in upgrading right now.
-
You use the logBytesToGs fn to convert the log data into Gs
-
What do these numbers represent? Also, the BLE connection isn't meant for streaming data at 200Hz or higher.
-
What kind of data are you trying to log and how have you attempted to do it? It sounds like your phone is sending read commands rather than the device internally reading data on its own. Downloading data is initiated from the app side, not the bo…
-
There is both acceleration (at the beginning) and deceleration (at the end) of the motion so you should see both. The accelerometer (mma8452q) on the MetaWear does not support different axis thresholds.
-
You import the project into Android Studio with the "Open an existing Android Studio project" option from the Android Studio welcome screen. The option is under the "Quick Start" section.
-
How are you importing the project into Android Studio? Also, what are the contents of the Metawear-SampleAndroidApp-master folder?
-
The latency parameter is for configuring double tap. For how the API configures single tap, latency does not affect single tap.
-
Using a threshold of 0.25g seems to detect the motion you linked.
-
This is most likely caused from the android ble stack. Try resetting the bluetooth adapter if this happens.
-
The purpose of the guide is to help users understand the MetaWear library, not teach them about the Android platform. It is the user's responsibility to have a good understanding of the Android topics (Activity, Service, BroadcastReceiver, etc.) be…
-
The accelerometer has built in motion detection. You can enable it with the enableMotionDetection method and receive motion notifications from the movementDetected callback function.
-
What kind of movement are you looking for? Pulse detection settings will be highly dependent on your type of motion and will probably require other filter to clean up the data.
-
Thanks for feedback on the docs page. As for a simple project, the SOSTrigger (https://github.com/mbientlab/SOSTrigger) project demos the full code flow. You can use that as reference for future projects. Not sure why you had to restart the bo…
-
We are no longer developing on Eclipse as Android Studio is the official IDE. The code will compile in Eclipse provided you have the correct Android SDK (SDK 21 as of right now) but you will need to build the source yourself if you wish to continue…
-
How are you using the API to control the accelerometer? It sounds like you are configuring XYZ sampling while the accelerometer is still running. You have to stop accelerometer before configuring any of its components.
-
The library is now distributed as an AAR file and published on our Ivy Repo.
-
Already been fixed http://community.mbientlab.com/discussion/305/android-api-v1-6-21-and-app-v2-5-9-update-2015-03-18
-
Post a picture comparing the two batteries.
-
You can use the Timer and Event modules to replicate what you want. I wrote up what the code would look like in this gist: https://gist.github.com/mbientlab/11d00d8e980f2952dfe6
-
Try holding the button down and connecting the USB cable. It will put the device in Bootloader mode which will then show up in a ble scan as "MetaBoot".
-
Ah, offset was never implemented in the firmware; the withPulseOffset method should be deprecated.
-
It is fixed in the latest API release, v1.6.0
-
Try calling the play method with true instead of false to enable autoplay.
-
Yes, that is correct. There is actually only about ~15k entries in the logger and that number varies based on the size of the firmware. You pass in 0xffff to guarantee that all log entries are removed.
-
Another user has brought a similar problem up and it turns out the sample app is using outdated callback functions which incorrectly interpret the data coming from boards with firmware v1.0.0. An update has been pushed out on GitHub (commit 4cb9fe6…
-
It appears that the api project isn't linked to the app. The folder structures should be: MetaWearApp/ +___metaWearAPI/ +___metaWearApp/ -___build.gradle Unless you are going to be playing with the API source code, you should use one of …