d4rken/myolib

no sensor data appears in the sample app

Abouelenin opened this issue · 4 comments

when the exampleapp find the myo, it shows the myo, battery and firmware version but no sensor data, can you help me in fixing that?

Value: null
Identifier: 0000180f-0000-1000-8000-00805f9b34fb:00002a19-0000-1000-8000-00805f9b34fb
05-08 16:07:35.481 9122-9413/eu.darken.myolib.exampleapp V/MyoLib:BaseMyo:CA:0C:05:1F:16:F6: Processed: d5060001-a904-deb9-4748-2c7f4a124842:d5060201-a904-deb9-4748-2c7f4a124842
05-08 16:07:35.487 9122-9122/eu.darken.myolib.exampleapp I/ViewRootImpl: ViewRoot's KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=114433812, downTime=114433812, deviceId=-1, source=0x101 } to DecorView@5b47354[MainActivity]
05-08 16:07:35.538 9122-9138/eu.darken.myolib.exampleapp W/BluetoothGatt: onCharacteristicRead() - Device=CA:0C:05:1F:16:F6 handle=23 Status=0
05-08 16:07:35.539 9122-9138/eu.darken.myolib.exampleapp V/MyoLib:BaseMyo:CA:0C:05:1F:16:F6: rtt: 60ms | SUCCESS | ReadMsg

Thanks in advance.

I currently don't have Myo to test with.

I ran into this problem too, any suggestions?

I ran into this problem too, any suggestions?

now I solved this problem by simply set mTimeoutSendQueue to -1. (This variable is at line 65 of BaseMyo.java)

I saw some warnings about "Lost packet!", which is related to tryAcquire method. So I tried to remove the timeout and it works!

@suphanatnack @Abouelenin Although it's been a long time, I hope this can help you