Hello,
I want to program a metro APP that is implemented about a profile(for example, ftp, opp with obex 1.5) over l2cap on Bluetooth.
How can my metro app use the l2cap protocol of windows?
So far, I considered I can use device IO control to get it, and I wrote an profile driver, a metro App, and a winrt library. The test signing mode enabled. I try the following steps to use l2cap of windows 8.
1. My profile driver with code below to set property data with restricted after create the interface, and the status is success.
status = g_pIoSetDeviceInterfacePropertyData(&symbolicLinkName,
&DEVPKEY_DeviceInterface_Restricted,
0,
0,
DEVPROP_TYPE_BOOLEAN,
sizeof(isRestricted),
&isRestricted /*true*/);
2. I add a node for my Bluetooth controller by BluetoothSetLocalServiceInfo(), install my interface driver into the node, and it's successful.
3. I create a metadata with below information.
a) Locale default is en-US.
b) the HWID (bthenum\{8c68f88f-ea75-4580-ace0-022691e843f2}_LOCALMFG&0000) is the HWID of the node I created by BluetoothSetLocalServiceInfo() in step 2.
c) package name, publisher, App ID with my metro APP.
d) primary category is "others".
e) Add my metro app to Privileged Application list.
f) Check "Copy packages to your system's local metadata store", and finish.
After these actions, the device metadata is created, but the file is not existed in my system's local metadata store(%PROGRAMDATA%\Microsoft\Windows\DeviceMetadataStore\en-US). So, I copy it to %PROGRAMDATA%\Microsoft\Windows\DeviceMetadataStore\en-US as
well. However, I use ddodiag.exe to get the log, I can't find any metadatapath property key in it. It seems the metadata package is not installed successfully. Why the metadata package can't be installed? Is it caused by the HWID of the device node is not
a real physical device?
Thanks.
