Opened 11 years ago

Closed 9 years ago

#2377 closed bug (fixed)

bluetooth_server ignores command status after command 0xd

Reported by: monni Owned by: oruizdorantes
Priority: normal Milestone: R1
Component: Network & Internet/Bluetooth Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

how to reproduce: start bt_discovery with at least one remote device present experienced behavior: event 0xf is ignored expected behavior: neither event 0xf or opcode 0x0419 is ignored

bluetooth_server:

### Command going: len = 17 d:0:0:0:19:4:a:5a:bf:fb:af:1b:0:1:65:5c:45:### ### Event comming: len = 4 f:4:0:1:19:4:### Petition 0 ... of 1 msg #0x18010310 BMessage('btsR') {

hci_id = int32(0x0 or 0) raw command = (type = 'ANYT')(size = 17) eventExpected = int16 (0x7 or 7)

} ### Event comming: len = 255 7:ff:0:5a:bf:fb:af:1b:0:4e:6f:6b:69:61:20:36:31:32:30:20:63:6c:61:73:73:69:63:0: 0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0: 0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0: 0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0: 0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0: 0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0: 0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:### Petition 0 ... of 1 msg #0x18010310 BMessage('btsR') {

hci_id = int32(0x0 or 0) raw command = (type = 'ANYT')(size = 17) eventExpected = int16 (0x7 or 7)

} Event found 0 Sending reply ... 0 BMessage(0x0) {

status = int8(0x0 or 0 or '[') friendlyname = string("Nokia 6120 classic", 19 bytes)

} Sending reply message

Change History (2)

comment:1 Changed 11 years ago by oruizdorantes

Status: newassigned

Yes,

Currently the 0xf event is ignored in the retrieval of the remote name as it is providing no info.

Will use this ticket to leave some track of it.

comment:2 Changed 9 years ago by oruizdorantes

Resolution: fixed
Status: in-progressclosed

Server is now taking into account the "Command Status" Event in the RemoteName retrieval. If its status is not OK, the request would be aborted, and the kit reported about the error.

Note: See TracTickets for help on using tickets.