awsllcjeff
About
- Username
- awsllcjeff
- Joined
- Visits
- 190
- Last Active
- Roles
- Member
Comments
-
Laura, In order to get the Advanced button to work on my IOS device I had to change the advancedPressed code in the Controller --> DiagnosticViewController to: basically I added the code for iPad specific code below and now it works great. …
-
So, how do I downgrade the firmware if the IOS app crashes when I click on the advanced options and the Android app wont recognize the 1.5.1 firmware
-
I tried this using the Android app and when I enter the version 1.5.1 I get the following error: No value for 0.3.2
-
The app that I created for Android works great when the sensor has a firmware version of 1.5.1, but not when the sensor has firmware version 1.7.3. The sensor disconnects from the phone after a minute or two if it has 1.7.3
-
Once I upgraded to 1.7.3 the macro is being saved. But now I have an issue with the sensor disconnecting at odd times. My app works great when the firmware on the sensor is 1.5.1, but not 1.7.3
-
Model: MetaMotionR Hardware: .4 Firmware: 1.7.3
-
When I click on the advanced button the app crashes. I reinstalled the app from the app store and it still crashes when I click on the advanced button.
-
How can we downgrade from 1.7.3 back to 1.5.1? Since I upgraded 2 sensors they no longer stay connected to my app?
-
I am wondering if there is a problem with the 1.7.2 firmware. Since I upgraded to the 1.7.3 firmware the macro does seem to save the data and the code returns a value for the macro id.
-
Does anyone have any ideas as to why I cannot write the calibration data to the device and store it in a macro? Why the macro ID always returns null? I am using a MetaMotion R model 5 hardware version .4 with the firmware 1.7.2. The app I am using …
-
Laura, I finally got the code working to calibrate the sensor, but now I am having issues with storing the calibration data in a macro. I followed the code examples to store the data and it seams to work except that it returns null for the macro ID…
-
I will keep an eye out for it.
-
Laura, Once I got the permissions issue fixed, the new release of 3.8.0 works great with the new feature to reset the orientation of the device. Jeff
-
Yes, I just verified that 0.3.1 works great. Jeff
-
I will try it and let you know. Jeff
-
Or just update the setup instructions to include the permissions in the AndroidManifest file as well as checking for it during the start of the app.
-
I reverted back to the bletoolbox 0.3.0 and got it to work now. I just had to make sure that the permission for ACCESS_FINE_LOCATION exists for 29 and above.
-
I tried for 29 and it did not work and yes I did use bletookbox 0.3.0. I am wondering if your app is checking the ACCESS_FINE_LOCATION somewhere else. You may want to clean up my code as I was hard coding it to see if I could get it to work. Je…
-
Laura, In order to see any sensors once migrating to SDK 29 or 30 you need to check for: BleScannerFragment only looks for ACCESS_COARSE_LOCATION. I made a local copy of bletoolbox and modified the BleScannerFragment to: private boolean c…
-
Laura, It only works when the targetSdkVersion is 28. Once I got to 29 or 30 I cannot find any of the sensors. Jeff
-
Laura, No, it still does not work. Thank you, Jeff
-
Laura, When I change the compiledSDKVersion to 29 or 30 and the corresponding buildTooolsVersion my app no longer see any of the Metawear sensors. Thanks.
-
Do you think it will be today or later this week? I will test it as soon as you release it and let you know. Thanks. Jeff
-
Great. Thank you.
-
If you need anyone to test it please let me know. Thanks. Jeff
-
Has anyone found a solution to this problem? I am running into the same issue. Thanks.
-
I am waiting for this as well. An update would be nice. Thanks.
-
Laura, Any updates on when the app will be updated? Thanks Jeff
-
Laura, Any updates on when the Android apps update will be completed? Do you know if the example code will include the calibration code?
-
Great. Thank you for the update.