danielj
About
- Username
- danielj
- Joined
- Visits
- 9
- Last Active
- Roles
- Member
Comments
-
Another difficulty might be that I'm connecting to the device completely in the background so I can't use any of the ui-based mbientlab utilities. In my code I have the mac saved in prefs: App is started via alarm, scans for the device-> Tha…
-
I've been testing with a simpler app and get the same issue on the Pixel phone. The only thing that's driving me nuts is how if I try only with Metabase it works. Metabase will usually fail to connect 1 or 2 times but eventually will work. But bo…
-
'Log.d("TAG", "prior to connectAsync"); return metawear.connectAsync(); }).continueWith(task -> { if (task.isFaulted()) { Log.d("TAG", task.getError().getLocalizedMessage()); owner.r…
-
@Eric said: @danielj said: I'm trying to make sense of why the success rate for the first connection is so much higher on metabase. MetaBase does a BLE scan for the device selection UI. You can try using the BLE scan …
-
@Laura said: Do you have a phone that is not a Pixel and that is new-ish you can use? Yes, like I said I have two phones that work. The problem is that we are trying to provide mmr's to other people and there's no way to know if their ph…
-
Make: Google Model: PIxel (2016) Anroid OS: version 10 Build version: QP1a. 191005.007.A3 Board: sailfish Ble supported The other phones I've tried have worked fine, running android 8 and android 9. (galaxy s7 and note 9)
-
I handle disconnects by attempting to call onServiceConnected() again, and it works to reconnect the device if it comes out of range or anything like that. try { board.onUnexpectedDisconnect(new MetaWearBoard.UnexpectedDisconnectHand…
-
I tried only using a single device after a clear reset of the MMR. I've been pretty much using the code above. One possible issue is that I don't get to do any clean up on the connection because I'm reading sensor data constantly in the background(s…
-
Even when only using this instance I posted above it still fails frequently, but works if I ONLY use the metabase app. If I run my code and it happens to fail metabase will also frequently fail. There's nothing much to screenshot, metabase simply…
-
Trimmed down version of my app `public class MetaWearSensorManager implements ServiceConnection { private static MetaWearSensorManager SINGLE_INSTANCE = null; private String MW_MAC_ADDRESS; private BtleService.LocalBinder serviceBinder; privat…
-
So actually after a couple failures to connect I finally managed to reset the app through metabase once. Since them I've restarted the phone about 10 times and tried to connect only with metabase, and only with this specific phone. So far like this…
-
If I attempt to connect via nRFConnect I will discover the device but on pressing "connect" it will load and will no reach services discovered. Metabase will show "unable to connect to device" And for my code I call connectAsync().onSuccessTas…
-
I'm trying now with a few different ones like raising advertising power. With default settings I'm always able to discover the device itself with a ble scan. The problem is actually connecting to it. Do you have any settings recommendations? Most…
-
@Matt So the only option for persistent connection is connect when the phone turns on and receive unencrypted sensor data? It's odd that I can bond the device at all then.
-
After playing around with nRF Connect it seems like the MMR unit just refuses to stay bonded on restarts? I successfully bond the device through either settings, my app, or nRF Connect. The app tells me that the device is indeed bonded. But as soon …
-
@Laura said: You may want to try to play with the Bluetooth connection settings. You mean on the phone or the metawear board? Phone is just for testing. I was hoping connectAsync() would work well on most phones.
-
Actually, I found out how I can pair the device programmatically and I run into the issue of the board being extremely finicky. Even in the phone settings for the google pixel it will often take dozens of tries before working. I might just have to c…
-
I know that much, right now it's even hardcoded to my specific mac address. getRemoteDevice() gives me a valid bluetooth device but if I try to get data with connectAsync()... I get this error Failed to connect and discover services within 100…
-
That might be the case, but is there a way to at least have the phone remember the metawear board so there is only one time pairing?
-
Now that you mention it, it seems to work just fine on a galaxy s7 running android 8 but not on a Google pixel on android 10. The older galaxy s7 also lets me programmatically bond the device if I want while the pixel doesn't.
-
If the device isn't paired on the Bluetooth settings I just get this error: java.util.concurrent.TimeoutException: Failed to connect and discover services within 10000ms I have the mac address saved and this is how I'm supposed to get the board …
-
I'm using a Google pixel on android 10. The app compiles and targets sdk28. public void retrieveBoard(){ // Get the MetaWear device via MAC address final BluetoothManager bluetoothManager = (BluetoothManager) context.getSystemServ…
-
onAccelObserved and onGyroObserved just write the data to a file and have it constantly updating two textfields. For now having the textfields update less frequently seems to reduce the issue, I just recreate the whole process on crash. I though …
-
Should I retrieve the Accelerometer and Gyro data in the same task? I'm very very new to Android so I'm unsure about how to handle retries?