Does GATT Server need special capabilities in the package manifest? about windows-dev-docs HOT 11 CLOSED

@mtbeaver I tried it, but could not get it to work.

The use case was:

I wanted to implement the HID reports from https://msdn.microsoft.com/en-us/windows/hardware/commercialize/design/component-guidelines/radial-controller-protocol-implementation to emulate a Surface Dial.

It seems that, for a device to be detected properly as a HID device, it should implement at least

• HID Service
• Battery Service
• Device Information Service

For the Device Information Service I still get BluetoothError.DisabledByPolicy. The same applies to the Generic Access Service (used to set a friendly name and icon, don't know whether it is required).

I'm afraid that unlocking only the HID Service doesn't allow implementing my usecase :(

Have you been able to emulate a HID device using an UWP Background App for Windows IoT Core, that was detected properly by another Windows 10 machine? If so, I'd be really glad to see an example.

from windows-dev-docs.

Unfortunately, HID is currently protected as a reserved service, which prevents it from being implemented by a 3rd party application. Please share details on the scenario, and we will discuss it internally.

from windows-dev-docs.

@mtbeaver thank you for your explanation. Could you add this to the documentation?

As for the usecase: I wanted to implement the HID reports from https://msdn.microsoft.com/en-us/windows/hardware/commercialize/design/component-guidelines/radial-controller-protocol-implementation to emulate a Surface Dial.

from windows-dev-docs.

I have a Nuimo device that has similar hardware to a Surface Dial, but it sends plain GATT messages (no HID). I wanted to use it in windows and writing a virtual hid driver or adjusting the HID injection example in c++ seemed complicated to me (I'm familiar with C#). So I hoped I could use the GATT server functionality to create a "bridge app".

from windows-dev-docs.

@mtbeaver do you have any update on this?

from windows-dev-docs.

@Wind-rider, we have discussed this internally and will be removing the HID restriction for Gatt Server in the next release. I’ll keep you posted here when the change is available in the Windows Insider builds.

from windows-dev-docs.

@mtbeaver Great to hear, I'm looking forward to it!

from windows-dev-docs.

@Wind-rider The restriction should be lifted in the Windows Insider Fast builds. Please let me know if you have any questions.

from windows-dev-docs.

@mtbeaver thank you for keeping me updated! Do you mean build 16226 for Windows IoT Core? (I couldn't find it in the release notes)

Also - do I need a special SDK version or was the limitation only in the OS and will the 15063 SDK work fine?

from windows-dev-docs.

The existing Creators Update SDK should work fine. As it was a minor update, it is not in the release notes, but I believe that build should have the relevant changes. Please use the latest build available to you though.

from windows-dev-docs.

Hi @wind-rider--I'm going to close this issue for now. If you still need a response, please either reopen this issue or open a new one. Thank you!!

from windows-dev-docs.