[mlaverd]

Hello all!

I'm implementing an application that requires to analyze CODs.

Major service bits are OK, but minor service bits are wrong.

I'm comparing those values with the official BT reference:
https://www.bluetooth.org/foundry/as...ument/baseband


For example, I detect a cellphone, and I get: 01010000, which means nothing in the spec. I should be getting 00000100 or 00001100.

I'm detecting a laptop, and I'm getting 00010000, which is a deviceclass for a handheld, not a laptop.

Detecting a computer, I'm getting 00110000, which, again, means nothing at all. I should be getting 00000100.

Has anyone faced values like those? Is that a known bug in Nokia's BT implementation? I could always check against those specific values, but I'm afraid of making my code not portable.

All suggestions welcomed

[ferranhalden]

Hi,

I am trying to filtering Bluetooth devices specifying the major class TInquirySockAddr::SetMajorClassOfDevice () before calling RHostResolver::GetByAddress(). However, it doesn't work.

It seems that you are able to get the Major Service class of the bluetooth devices. Could you please inform me about the approach you are using?

Best regards,

Fernnado