char.write(b'\x13\x03\x26\x00') #13032600

[to address #1 above]

Raspbian kernel is Linux 4.9.59-v7+ #1047  (from uname -a)

p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Menlo; color: #18b5b1}

I noticed that the above problem only occur when #1 method is used. If I close the (#2 method) and restart then its work perfectly fine,   

Following on https://github.com/mbientlab/MetaWear-SDK-Android/issues/13 :

#1  0x00007ffff7971f37 in mbl_mw_metawearboard_tear_down () from ../metawear/libmetawear_d.so.0

Did a few tests, sample #1 and #2, and nothing looks out of the ordinary compared with your data and what I would expect.  The IMU itself is not 100% accurate so you should consider "at rest"

as it is part of the settings module (#17 in the sequence) the change can't be made until after initialization which, as described above is slow to begin with. It's a bit of a chicken and the egg pro

According to the Bluedroid header files, 0x8 means connection timeout:https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/master/stack/include/gatt_api.h#108

How many devices are you attempting to simultaneously stream and at what data rates? Bluetooth le can't reliably handle data at frequencies higher than 100Hz. If you are flooding the radio with dat

The only thing I can think of is a Bluetooth error Samsung phones were having due to Samsung's Android OS variant:

I

#1    0x0017ebc6 in __34-[MBLRegister recievedData]_block_invoke at /Users/sschiffli/Code/metawear-ios-api/MetaWear/MBLRegister.m:268

of some type such as "Terry's MetaWear #1234", and my app would connect, ask for the calculated value, then disconnect.