We use their BluetoothSecurity.PairRequest method, using their doc
https:,
to pass in a null pin to initiate the Windows pairing request via
Bluetooth’s SSP. The user then gets a windows prompt to pair the new device
and assigns a com port number. Here, pairing seems to have succeeded, yet
to actually connect to the device properly, an unplug / replug of the
external bluetooth receiver is necessary (versus a turn off / on of the
device).
ᐧ
On Mon, Oct 16, 2017 at 4:36 PM, xxxxx@microsoft.com <
xxxxx@lists.osr.com> wrote:
> What is the InTheHand pairing process?
>
> Bent from my phone
> ------------------------------
> From: xxxxx@lists.osr.com > osr.com> on behalf of xxxxx@gmail.com
> Sent: Monday, October 16, 2017 3:08:23 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Bluetooth Pairing / Registry / Com Ports
>
> Version 1703
> OS build: 15063.674, though has been happening in earlier versions.
>
> ᐧ
>
> On Mon, Oct 16, 2017 at 2:12 PM, xxxxx@microsoft.com <
> xxxxx@lists.osr.com> wrote:
>
>> Which version of windows 10?
>>
>>
>>
>> From: xxxxx@lists.osr.com [mailto:bounce-640044-26293@li
>> sts.osr.com] *On Behalf Of *xxxxx@gmail.com
>> Sent: Monday, October 16, 2017 12:24 PM
>> To: Windows System Software Devs Interest List
>> Subject: Re: [ntdev] Bluetooth Pairing / Registry / Com Ports
>>
>>
>>
>> Windows 10, thanks.
>>
>> ᐧ
>>
>>
>>
>> On Mon, Oct 16, 2017 at 11:31 AM, xxxxx@microsoft.com <
>> xxxxx@lists.osr.com> wrote:
>>
>> What OS version?
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com [mailto:bounce-640033-26293@li
>> sts.osr.com] On Behalf Of xxxxx@gmail.com
>> Sent: Monday, October 16, 2017 10:28 AM
>> To: Windows System Software Devs Interest List
>> Subject: [ntdev] Bluetooth Pairing / Registry / Com Ports
>>
>> All,
>> All,
>> We use InTheHand to pair our Bluetooth classic devices to an external
>> Bluetooth dongle. Sometimes, though not always, this requires an
>> unplug/replug of the dongle. When I look into the registry using WinObj, I
>> notice that the pairing adds a new association (BTHENUM // BTHModem), but
>> the BTHModem references are incorrect.
>>
>> For example, after pairing 1 device, I see this in the registry:
>>
>> - BTHENUM#{00001101-00805f9b34fb}_LOCALMFG&000a#b34fb ? \Device\BthModem8
>> - BTHENUM#{00001101-00805f9b34fb}_LOCALMFG&000a#01f73 ?
>> \Device\BthModem3
>> - BTHENUM#{00001101-00805f9b34fb}_LOCALMFG&000a#b3c70 ? \Device\BthModem8
>>
>> And after unplug / replug:
>>
>> - BTHENUM#{00001101-00805f9b34fb}_LOCALMFG&000a#b34fb ? \Device\BthModem1
>> - BTHENUM#{00001101-00805f9b34fb}_LOCALMFG&000a#01f73 ?
>> \Device\BthModem1
>> - BTHENUM#{00001101-00805f9b34fb}_LOCALMFG&000a#b3c70 ? \Device\BthModem1
>>
>>
>> Has anyone seen this behavior before // found a workaround? I?d
>> probably like to avoid a call to ?disable / reenable? the bluetooth dongle,
>> though that may be my best option.
>>
>> Thanks,
>> Michael
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list online at: https:>> tion.outlook.com/?url=http%3A%2F%2Fwww.osronline.com%
>> 2Fshowlists.cfm%3Flist%3Dntdev&data=02%7C01%7CDoron.Holan%
>> 40microsoft.com%7Ce6a4ad6a201b409ef87b08d514bb54fa%7C72f988b
>> f86f141af91ab2d7cd011db47%7C1%7C0%7C636437717177582742&
>> sdata=DG4CKhxNaKdww%2Fv7EpP7Z66W3VXeFighCOsVh60ah7Y%3D&reserved=0>
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at https:>> 2F%2Fwww.osr.com%2Fseminars&data=02%7C01%7CDoron.Holan%
>> 40microsoft.com%7Ce6a4ad6a201b409ef87b08d514bb54fa%7C72f988b
>> f86f141af91ab2d7cd011db47%7C1%7C0%7C636437717177582742&
>> sdata=ld%2FOcyQYdra4c3bW9IFUkR17NBidFsJvIwAiEvJNmcw%3D&reserved=0>
>>
>> To unsubscribe, visit the List Server section of OSR Online at <
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> 2F%2Fwww.osronline.com%2Fpage.cfm%3Fname%3DListServer&data=
>> 02%7C01%7CDoron.Holan%40microsoft.com%7Ce6a4ad6a201b
>> 409ef87b08d514bb54fa%7C72f988bf86f141af91ab2d7cd011db47%7C1%
>> 7C0%7C636437717177582742&sdata=gSkKxI0a%2BvvLHssdUmnb2pVb%2BAXiDvyY20b
>> Qxgm4ByU%3D&reserved=0>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list online at: http:>> lists.cfm?list=ntdev
>> https:
>> >
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at http:>> https:
>> >
>>
>> To unsubscribe, visit the List Server section of OSR Online at <
>> http://www.osronline.com/page.cfm?name=ListServer
>> https:
>> >
>>
>>
>>
>> — NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
>> on crash dump analysis, WDF, Windows internals and software drivers!
>> Details at To unsubscribe, visit the List Server section of OSR Online at
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list online at: http:>> lists.cfm?list=ntdev
>> https:>
>>
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at http:>> https:>
>>
>>
>> To unsubscribe, visit the List Server section of OSR Online at <
>> http://www.osronline.com/page.cfm?name=ListServer
>> https:>
>>
>>
>
> — NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
> on crash dump analysis, WDF, Windows internals and software drivers!
> Details at To unsubscribe, visit the List Server section of OSR Online at
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:></https:></https:></http:></https:></http:></https:></https:></http:></https:></http:></https:></https:></https:>