ElliothDracke
commented
5 years ago I have the exact same problem, it seems the only solution for now would be to revert to 1809 :/
Closed Joanit876 closed 5 years ago
ElliothDracke
commented
5 years ago I have the exact same problem, it seems the only solution for now would be to revert to 1809 :/
cboulay
commented
5 years ago If pairing is the problem... Back before we had reliably pairing in Win8/Win10, my primary computer was a macbook that I dual booted in MacOS or Windows. I was able to pair it in MacOS then when I booted into Windows the controller was still paired. The BT MAC address was the same so it worked. I think someone could boot into a Linux image, pair there, then when booting in Windows it should still be paired. This only applies to people who have difficulty pairing.
@kugiugi Have you tried running PSMoveService and the client on different machines? As long as the machines are on the same network and the ports are open then in theory it should work but I don't think I've ever tried it.
iXmerof
commented
5 years ago Hi All, I had similar issue on Windows 10, never had this to occur on Windows 8.1 before and as I'm migrating (for H.265 in Riftcat) this had happened to me as well. My BT radio is a single CSR 4.0 that cost me 4$ and worked on win8.1 with psm beautifully. I was debugging the issue like crazy, finally I made them working but not in the way we'd like to have it scripted. The main issue here is that ...\HidBth\Parameters\Devices key is never created for the device. What's ever more interesting is a situation on Windows UWP device list they are switching from paired to connected and so on. Once I plug in the USB cable windows finds it as a "Motion Controler" properly, then I move to pairing. It finds the controller and tries to patch the registry but never succeeds (because of the key from previous paragraph). The BTHPort entry exists with proper MAC of the BT device but I haven't found that useful. I was jiggling here a lot, adding, removing keys, creating C app to try to pair manually and it never helped. What helped is a removal of the HidBth and BTHPort keys (not everything on the latter can be removed but that's not an issue) and re-applying the values from Win8.1 where controllers were successfully paired. Next I had to do is to pair them from PSMoveConfigTool again and... magic! Paired immediately. Some keys were missing, I will need to focus on the diffs of *.reg exports now.
@cboulay You made me curious about that solution (and I found a branch for the Rbpi pairing solution what made me for the first time asking "why?", but next I was like "hmm, it actually could be proven useful...". What concerns me is how we should tell SteamVR to connect to a service on other device? The second concern I might have is the additional lag this solution includes.
chegalou
commented
5 years ago I have exact same problem. I used psmoveservice before I format. But after format and update bios, it cannot working anymore.
Same OS, same hardware. I don't know what is the problem.
My hardware is Intel i5 7500 b250 motherboard radeon RX 570
Is this associated with Intel security update? I want to know spec of users have same problem.
chegalou
commented
5 years ago https://github.com/psmoveservice/PSMoveService/issues/618 maybe this will help us?
ElliothDracke
commented
5 years ago Yes it seems the only viable solution without having to format is to revert to an older windows build, as 1903 broke bluetooth for some hid devices. That is only if you didn't pass the 10 days period after the update, if you did then you have to reinstall windows completely as the option to revert is grayed out ( unrelated but you can extend this period to 30 or 60 days ).
@chegalou specs are asus rog g751, i7 4700k, gtx 980M, built-in bluetooth adapter. Never had a problem before the new windows build.
@cboulay I never thought of that ! Thought the way it paired was exclusive to windows or that it simply wouldn't work. Did anyone was succesful trying to pair the controller on another os and then in windows ? I'll try that as soon as I have time.
chegalou
commented
5 years ago @ElliothDracke I cannot. too many times pasted. I think we'd better say to MS.
Yozer
commented
5 years ago @iXmerof You were right. I had the same problem with pairing as you. Windows 10 1903 for some reason is no longer creating registry keys...
Anyway, I fixed that in #634 I have no idea if that change will be merged. You can use this binary to pair your ps move: https://1drv.ms/u/s!An8ls2qnV1z_n_57p7s2utrsq_x0LQ
Alternatively you can build PSMoveService from my fork.
zimirken
commented
5 years ago @iXmerof You were right. I had the same problem with pairing as you. Windows 10 1903 for some reason is no longer creating registry keys...
Anyway, I fixed that in #634 I have no idea if that change will be merged. You can use this binary to pair your ps move: https://1drv.ms/u/s!An8ls2qnV1z_n_57p7s2utrsq_x0LQ
Alternatively you can build PSMoveService from my fork.
This build crashes steamvr. But, it does allow me to use my navi controllers. Is there anything you can do?
Yozer
commented
5 years ago @zimirken In this build I only fixed pairing issue. You should be able to pair your controlers using my build and then use regular PsMoveService to play steamVR. Did you try this?
zimirken
commented
5 years ago The pinav navi support is only in the unreleased master version, but that crashes steamvr. Using the release version the navis dissapear off the configuration.
Yozer
commented
5 years ago Sorry I won't be able to help you :( I guess that someone did not finish his work on pinav navi support. I don't even own one to check if it's a quick fix or no.
Zangetsu38
commented
5 years ago Not works for me, i have no idea why, but get soundenly psmove no want connect anymore, i have update few time insider build/ create news windows user, no want connect, but if i using second windows installation that works normally, but after return on myu main windows, no want connect and get same loop on log
And also, i have same issue with psmoveapi, oin both, is impossible connected on my main installation, and just no idea why
Edit: i have get finnaly workin with opening before and keep open detect news bt periopherique on windows
this
i have after try connect; have not wortks, but in moment i have close this, i have get directly psmove connected success
vbence121
commented
5 years ago Not works for me, i have no idea why, but get soundenly psmove no want connect anymore, i have update few time insider build/ create news windows user, no want connect, but if i using second windows installation that works normally, but after return on myu main windows, no want connect and get same loop on log
Edit: i have get finnaly workin with opening before and keep open detect news bt periopherique on windows this
Do I understand correctly, you only needed to run the scan for a new Bluetooth device before trying to connect to the PS move? Or I misunderstood something? Also when trying to connect the normal method, for me the motion controller actually shows up as a connected Bluetooth device in device manager, but psmoveservice still says it isn't connected
smittyinthesky
commented
4 years ago Hey everyone,
I struggled with this issue and here's what I was able to do (pretty pain free) to get past this issue.
tl;dr
1) go into "Control Panel" -> "Devices and Printers" 2) Right click -> "Properties" on any "Motion Controllers" and select the "Services" tab. 3) Click the checkbox for "Drivers for keyboard, mice, etc (HID)" and click Apply or OK. 4) Make sure you do this for both devices.
If you do not see anything listed under the "Services" tab, you may need to press the PS button on your PSMove controller and get the light to blink or do this config while you're trying to pair the PSMove controller.
If you've made it this far, here's my theory for why this works.
The PSMoveService app is complaining about two things here. 1) The HID service isn't working as expected and 2) there are some registry keys that appear to be uninitialized.
I believe in a recent Windows 10 update something with how these registry keys is managed/accessed was changed.
Please let me know if this works for anyone so that the devs can assimilate the conceptual changes into their code.
Thanks and good luck!
googleooer
commented
4 years ago When I connect my psmove controller to my PC the "Pair?" popup doesn't show up. It just sets up the controller and when it's done, it shows up as "Motion Controller (COM [random number])" and says "driver issue" or something like that. If I use Zadig to change the driver to libusb, it no longer says the drivers are broken, the charging light works but the controller still doesnt show up in PSMoveService.
PantACRO4life
commented
4 years ago same here im totally unable to connect my ps move controller
PixelHUN
commented
4 years ago Hey everyone,
I struggled with this issue and here's what I was able to do (pretty pain free) to get past this issue.
tl;dr
- go into "Control Panel" -> "Devices and Printers"
- Right click -> "Properties" on any "Motion Controllers" and select the "Services" tab.
- Click the checkbox for "Drivers for keyboard, mice, etc (HID)" and click Apply or OK.
- Make sure you do this for both devices.
If you do not see anything listed under the "Services" tab, you may need to press the PS button on your PSMove controller and get the light to blink or do this config while you're trying to pair the PSMove controller.
If you've made it this far, here's my theory for why this works.
The PSMoveService app is complaining about two things here. 1) The HID service isn't working as expected and 2) there are some registry keys that appear to be uninitialized.
I believe in a recent Windows 10 update something with how these registry keys is managed/accessed was changed.
Please let me know if this works for anyone so that the devs can assimilate the conceptual changes into their code.
Thanks and good luck!
It didn't work for me... :( i rlly wanna make this work. and i can't even revert to older version.
darkessaiden
commented
4 years ago The files posted by yowzer and zimirken are no longer available. If they did work does anyone know where they're still up?
DSVAR
commented
4 years ago I have the same problem... is there asnwer how fix it???
AnriiAndrushko
commented
4 years ago Have the same problem, does someone fix it?
Bellum1410
commented
4 years ago Check this reddit post: https://www.reddit.com/r/PSVRHack/comments/ar0xkm/ps_move_controllers_not_pairing_to_psmove_service/
I've been looking for a solution for 2 hours now, and the last comment, by FZ_VR, finally worked. I am on Windows 10 2004 btw.
- First, I did not unplug PSMove controller during pairing,
- Then when it jump between step 3 and 5, I can see in "BlueTooth and other device" of windows setting, under "Mouse, Keyboard and Pen", there is "Motion Controller" Paired but keep un-pairing. In "Other Device" list, there is also a "Motion controller".
- Remove the "Motion Controller" under other device during pairing (when psmoveservice jump between step 3 and 5). After it was removed by win10, the pairing success.
It was a matter of trial and error because most of the time the "Motion Controller" in "Other devices" removed successfully, but the pairing didn't finish. I would just cancel and start over. Also, after successful pairing of the first controller, I couldn't connect the second one. I turned off PSMoveService, then turned off the first (paired) controller by holding the PS button. Only then I could pair the second one with success (when the first one was off). Hope it helps!
Kromazeka
commented
3 years ago @iXmerof You were right. I had the same problem with pairing as you. Windows 10 1903 for some reason is no longer creating registry keys...
Anyway, I fixed that in #634 I have no idea if that change will be merged. You can use this binary to pair your ps move: https://1drv.ms/u/s!An8ls2qnV1z_n_57p7s2utrsq_x0LQ
Alternatively you can build PSMoveService from my fork.
And you can upload the file over a new one? I cannot compile
QWEXZZ
commented
3 years ago @iXmerof Ты был прав. У меня была такая же проблема с парностью, как и у тебя. Windows 10 1903 по какой-то причине больше не создает разделы реестра... Во всяком случае, я исправил это в #634 Я понятия не имею, будет ли это изменение объединено. Вы можете использовать этот двоичный файл для сопряжения вашего ps move: https://1drv.ms/u/s! An8ls2qnV1z_n_57p7s2utrsq_x0LQ В качестве альтернативы вы можете построить PSMoveService из моей вилки.
И вы можете загрузить файл поверх нового? Я не могу компилировать
please upload the file again
GamerHun1238
commented
3 years ago To build download the latest Visual Studio, import .sln file and build it (its obvious)
DeadOfLegend
commented
3 years ago i have a problom with pairing ps move to psconfig issue #631 and im using built-in bluetooth do i need to buy the BT400 for the issue to be fixed so i can pair?
Colin-J-School
commented
3 years ago @iXmerof You were right. I had the same problem with pairing as you. Windows 10 1903 for some reason is no longer creating registry keys...
Anyway, I fixed that in #634 I have no idea if that change will be merged. You can use this binary to pair your ps move: https://1drv.ms/u/s!An8ls2qnV1z_n_57p7s2utrsq_x0LQ
Alternatively you can build PSMoveService from my fork.
This link does not work anymore. Where can i find this
QWEXZZ
commented
3 years ago https://disk.yandex.ru/d/Ju6BPUv4SiLasg держи ссылку на файл. я не знаю сколько ещё будет работать ссылка.
QWEXZZ
commented
3 years ago https://disk.yandex.ru/d/Ju6BPUv4SiLasg держи ссылку на файл. я не знаю сколько ещё будет работать ссылка.
также нашёл рабочую чужую ссылку https://github.com/psmoveservice/PSMoveService/pull/634#issuecomment-680417436
Hello everyone, thank you very much for reading my post, but I am trying to match my PSMove, I have been doing it with previous versions of this program on my old windows, but since I upgraded to Windows 10: 1903. I can not match my controls. This is the log:
I spent hours trying to do this and I am already VERY frustrated :(
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent libusb: error [windows_get_device_list] program assertion failed - existing device should share parent [2019-07-11 23:10:13.782]: AsyncBluetoothPairDeviceRequest - Found a bluetooth radio [2019-07-11 23:10:13.784]: AsyncBluetoothPairDeviceRequest - Retrieved radio info [2019-07-11 23:10:13.889]: AsyncBluetoothPairDeviceRequest - Assigned host address 00:1a:7d:da:71:13 to controller id 0 [2019-07-11 23:10:13.891]: ServerRequestHandler - Async bluetooth request([Pair] ID: 0 Conn: 0) started. [2019-07-11 23:10:13.892]: AsyncBluetoothPairDeviceRequest - Making radio discoverable [2019-07-11 23:10:15.209]: AsyncBluetoothPairDeviceRequest - No bluetooth devices connected. [2019-07-11 23:10:15.212]: AsyncBluetoothPairDeviceRequest - No Bluetooth device found matching the given address: 00:07:04:ab:12:37 [2019-07-11 23:10:16.627]: AsyncBluetoothPairDeviceRequest - Bluetooth device found matching the given address: 00:07:04:ab:12:37 [2019-07-11 23:10:16.630]: AsyncBluetoothPairDeviceRequest - Bluetooth device matching the given address is the expected controller type [2019-07-11 23:10:16.634]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:10:16.637]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:16.638]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:16.641]: AsyncBluetoothPairDeviceRequest - Checking HID service [2019-07-11 23:10:16.643]: AsyncBluetoothPairDeviceRequest - HID service not enabled, attempting to enable [2019-07-11 23:10:19.661]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:19.663]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:19.666]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5 [2019-07-11 23:10:19.672]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:19.674]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:19.677]: AsyncBluetoothPairDeviceRequest - HID service not enabled [2019-07-11 23:10:19.681]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection [2019-07-11 23:10:19.684]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:10:19.689]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:19.992]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80 [2019-07-11 23:10:19.994]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:20.297]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80 [2019-07-11 23:10:20.299]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:20.601]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80 [2019-07-11 23:10:20.604]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:20.906]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80 [2019-07-11 23:10:20.908]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:21.210]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80 [2019-07-11 23:10:21.212]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:21.514]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80 [2019-07-11 23:10:21.516]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:21.819]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80 [2019-07-11 23:10:21.821]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:22.124]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80 [2019-07-11 23:10:22.128]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:22.430]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80 [2019-07-11 23:10:22.432]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:22.734]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80 [2019-07-11 23:10:22.736]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:23.37]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80 [2019-07-11 23:10:23.40]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:23.341]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80 [2019-07-11 23:10:23.343]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:23.644]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80 [2019-07-11 23:10:23.647]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:23.949]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80 [2019-07-11 23:10:23.951]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:24.253]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80 [2019-07-11 23:10:24.255]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:24.559]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80 [2019-07-11 23:10:24.564]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:24.867]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80 [2019-07-11 23:10:24.869]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:25.171]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80 [2019-07-11 23:10:25.173]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:25.476]: AsyncBluetoothPairDeviceRequest - Connection attempt: 19/80 [2019-07-11 23:10:25.478]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:25.780]: AsyncBluetoothPairDeviceRequest - Connection attempt: 20/80 [2019-07-11 23:10:25.782]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:26.84]: AsyncBluetoothPairDeviceRequest - Connection attempt: 21/80 [2019-07-11 23:10:26.87]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:26.389]: AsyncBluetoothPairDeviceRequest - Connection attempt: 22/80 [2019-07-11 23:10:26.391]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:26.693]: AsyncBluetoothPairDeviceRequest - Connection attempt: 23/80 [2019-07-11 23:10:26.696]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:26.998]: AsyncBluetoothPairDeviceRequest - Connection attempt: 24/80 [2019-07-11 23:10:27.1]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:27.303]: AsyncBluetoothPairDeviceRequest - Connection attempt: 25/80 [2019-07-11 23:10:27.307]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:27.614]: AsyncBluetoothPairDeviceRequest - Connection attempt: 26/80 [2019-07-11 23:10:27.617]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:27.619]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:27.622]: AsyncBluetoothPairDeviceRequest - Checking HID service [2019-07-11 23:10:27.627]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5 [2019-07-11 23:10:27.631]: AsyncBluetoothPairDeviceRequest - Device Connected [2019-07-11 23:10:27.634]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:27.636]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:27.639]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled [2019-07-11 23:10:27.948]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5 [2019-07-11 23:10:28.136]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:28.234]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:28.241]: AsyncBluetoothPairDeviceRequest - HID service not enabled [2019-07-11 23:10:28.254]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection [2019-07-11 23:10:28.266]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:10:28.278]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:28.587]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80 [2019-07-11 23:10:28.589]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:28.891]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80 [2019-07-11 23:10:28.896]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:29.200]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80 [2019-07-11 23:10:29.203]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:29.506]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80 [2019-07-11 23:10:29.508]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:29.810]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80 [2019-07-11 23:10:29.812]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:30.114]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80 [2019-07-11 23:10:30.117]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:30.418]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80 [2019-07-11 23:10:30.422]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:30.723]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80 [2019-07-11 23:10:30.726]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:31.29]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80 [2019-07-11 23:10:31.34]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:31.337]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80 [2019-07-11 23:10:31.339]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:31.641]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80 [2019-07-11 23:10:31.643]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:31.944]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80 [2019-07-11 23:10:31.946]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:32.249]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80 [2019-07-11 23:10:32.252]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:32.554]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80 [2019-07-11 23:10:32.557]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:32.859]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80 [2019-07-11 23:10:32.861]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:33.163]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80 [2019-07-11 23:10:33.165]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:33.467]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80 [2019-07-11 23:10:33.471]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:33.773]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80 [2019-07-11 23:10:33.775]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:34.78]: AsyncBluetoothPairDeviceRequest - Connection attempt: 19/80 [2019-07-11 23:10:34.80]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:34.382]: AsyncBluetoothPairDeviceRequest - Connection attempt: 20/80 [2019-07-11 23:10:34.384]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:34.686]: AsyncBluetoothPairDeviceRequest - Connection attempt: 21/80 [2019-07-11 23:10:34.688]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:34.990]: AsyncBluetoothPairDeviceRequest - Connection attempt: 22/80 [2019-07-11 23:10:34.998]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:35.301]: AsyncBluetoothPairDeviceRequest - Connection attempt: 23/80 [2019-07-11 23:10:35.304]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:35.606]: AsyncBluetoothPairDeviceRequest - Connection attempt: 24/80 [2019-07-11 23:10:35.610]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:35.912]: AsyncBluetoothPairDeviceRequest - Connection attempt: 25/80 [2019-07-11 23:10:35.914]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:36.216]: AsyncBluetoothPairDeviceRequest - Connection attempt: 26/80 [2019-07-11 23:10:36.218]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:36.520]: AsyncBluetoothPairDeviceRequest - Connection attempt: 27/80 [2019-07-11 23:10:36.523]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:36.825]: AsyncBluetoothPairDeviceRequest - Connection attempt: 28/80 [2019-07-11 23:10:36.828]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:37.129]: AsyncBluetoothPairDeviceRequest - Connection attempt: 29/80 [2019-07-11 23:10:37.132]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:37.434]: AsyncBluetoothPairDeviceRequest - Connection attempt: 30/80 [2019-07-11 23:10:37.438]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:37.745]: AsyncBluetoothPairDeviceRequest - Connection attempt: 31/80 [2019-07-11 23:10:38.157]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:38.159]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:38.163]: AsyncBluetoothPairDeviceRequest - Checking HID service [2019-07-11 23:10:38.174]: AsyncBluetoothPairDeviceRequest - HID service not enabled, attempting to enable [2019-07-11 23:10:41.212]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:41.612]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:41.619]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5 [2019-07-11 23:10:41.625]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:41.627]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:41.630]: AsyncBluetoothPairDeviceRequest - HID service not enabled [2019-07-11 23:10:41.636]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection [2019-07-11 23:10:41.649]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:10:41.655]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:41.962]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80 [2019-07-11 23:10:41.969]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:42.273]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80 [2019-07-11 23:10:42.319]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:42.623]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80 [2019-07-11 23:10:42.625]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:42.928]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80 [2019-07-11 23:10:42.931]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:43.243]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80 [2019-07-11 23:10:43.257]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:43.559]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80 [2019-07-11 23:10:43.562]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:43.864]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80 [2019-07-11 23:10:43.867]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:44.169]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80 [2019-07-11 23:10:44.171]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:44.473]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80 [2019-07-11 23:10:44.475]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:44.777]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80 [2019-07-11 23:10:44.781]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:45.83]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80 [2019-07-11 23:10:45.87]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:45.391]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80 [2019-07-11 23:10:45.393]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:45.700]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80 [2019-07-11 23:10:45.707]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:46.11]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80 [2019-07-11 23:10:46.13]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:46.316]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80 [2019-07-11 23:10:46.319]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:46.621]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80 [2019-07-11 23:10:46.623]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:46.925]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80 [2019-07-11 23:10:46.927]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:47.228]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80 [2019-07-11 23:10:47.232]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:47.535]: AsyncBluetoothPairDeviceRequest - Connection attempt: 19/80 [2019-07-11 23:10:47.537]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:47.840]: AsyncBluetoothPairDeviceRequest - Connection attempt: 20/80 [2019-07-11 23:10:47.842]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:48.145]: AsyncBluetoothPairDeviceRequest - Connection attempt: 21/80 [2019-07-11 23:10:48.148]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:48.450]: AsyncBluetoothPairDeviceRequest - Connection attempt: 22/80 [2019-07-11 23:10:48.452]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:48.754]: AsyncBluetoothPairDeviceRequest - Connection attempt: 23/80 [2019-07-11 23:10:48.758]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:48.759]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:48.763]: AsyncBluetoothPairDeviceRequest - Checking HID service [2019-07-11 23:10:48.766]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5 [2019-07-11 23:10:48.791]: AsyncBluetoothPairDeviceRequest - Device Connected [2019-07-11 23:10:48.810]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:48.812]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:48.817]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled [2019-07-11 23:10:49.123]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5 [2019-07-11 23:10:49.126]: AsyncBluetoothPairDeviceRequest - Device Connected [2019-07-11 23:10:49.128]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:49.130]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:49.134]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled [2019-07-11 23:10:49.453]: AsyncBluetoothPairDeviceRequest - Verification attempt 2 / 5 [2019-07-11 23:10:49.969]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:10:49.973]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:10:49.977]: AsyncBluetoothPairDeviceRequest - HID service not enabled [2019-07-11 23:10:49.979]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection [2019-07-11 23:10:49.984]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:10:49.987]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:50.296]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80 [2019-07-11 23:10:50.299]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:50.602]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80 [2019-07-11 23:10:50.606]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:50.919]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80 [2019-07-11 23:10:51.254]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:51.569]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80 [2019-07-11 23:10:51.651]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:51.954]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80 [2019-07-11 23:10:51.957]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:52.260]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80 [2019-07-11 23:10:52.263]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:52.565]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80 [2019-07-11 23:10:52.568]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:52.872]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80 [2019-07-11 23:10:52.877]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:53.182]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80 [2019-07-11 23:10:53.229]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:53.532]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80 [2019-07-11 23:10:54.88]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:54.473]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80 [2019-07-11 23:10:54.477]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:54.780]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80 [2019-07-11 23:10:54.783]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:55.85]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80 [2019-07-11 23:10:55.89]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:55.392]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80 [2019-07-11 23:10:55.394]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:55.696]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80 [2019-07-11 23:10:55.703]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:56.5]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80 [2019-07-11 23:10:56.8]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:56.310]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80 [2019-07-11 23:10:56.311]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:56.614]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80 [2019-07-11 23:10:56.616]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:56.918]: AsyncBluetoothPairDeviceRequest - Connection attempt: 19/80 [2019-07-11 23:10:56.920]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:57.221]: AsyncBluetoothPairDeviceRequest - Connection attempt: 20/80 [2019-07-11 23:10:57.224]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:57.526]: AsyncBluetoothPairDeviceRequest - Connection attempt: 21/80 [2019-07-11 23:10:57.529]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:57.831]: AsyncBluetoothPairDeviceRequest - Connection attempt: 22/80 [2019-07-11 23:10:57.834]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:58.137]: AsyncBluetoothPairDeviceRequest - Connection attempt: 23/80 [2019-07-11 23:10:58.139]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:58.441]: AsyncBluetoothPairDeviceRequest - Connection attempt: 24/80 [2019-07-11 23:10:58.444]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:58.746]: AsyncBluetoothPairDeviceRequest - Connection attempt: 25/80 [2019-07-11 23:10:58.749]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:10:59.53]: AsyncBluetoothPairDeviceRequest - Connection attempt: 26/80 [2019-07-11 23:10:59.56]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:10:59.60]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:10:59.67]: AsyncBluetoothPairDeviceRequest - Checking HID service [2019-07-11 23:10:59.70]: AsyncBluetoothPairDeviceRequest - HID service not enabled, attempting to enable [2019-07-11 23:11:02.95]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:11:02.97]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:11:02.100]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5 [2019-07-11 23:11:02.102]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:11:02.104]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:11:02.106]: AsyncBluetoothPairDeviceRequest - HID service not enabled [2019-07-11 23:11:02.108]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection [2019-07-11 23:11:02.111]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:11:02.113]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:02.415]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80 [2019-07-11 23:11:02.419]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:02.721]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80 [2019-07-11 23:11:02.724]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:03.27]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80 [2019-07-11 23:11:03.29]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:03.332]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80 [2019-07-11 23:11:03.334]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:03.636]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80 [2019-07-11 23:11:03.638]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:03.940]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80 [2019-07-11 23:11:03.942]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:04.244]: AsyncBluetoothPairDeviceRequest - Connection attempt: 7/80 [2019-07-11 23:11:04.247]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:04.550]: AsyncBluetoothPairDeviceRequest - Connection attempt: 8/80 [2019-07-11 23:11:04.551]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:04.854]: AsyncBluetoothPairDeviceRequest - Connection attempt: 9/80 [2019-07-11 23:11:04.857]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:05.160]: AsyncBluetoothPairDeviceRequest - Connection attempt: 10/80 [2019-07-11 23:11:05.162]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:05.464]: AsyncBluetoothPairDeviceRequest - Connection attempt: 11/80 [2019-07-11 23:11:05.467]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:05.769]: AsyncBluetoothPairDeviceRequest - Connection attempt: 12/80 [2019-07-11 23:11:05.771]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:06.73]: AsyncBluetoothPairDeviceRequest - Connection attempt: 13/80 [2019-07-11 23:11:06.76]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:06.378]: AsyncBluetoothPairDeviceRequest - Connection attempt: 14/80 [2019-07-11 23:11:06.380]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:06.682]: AsyncBluetoothPairDeviceRequest - Connection attempt: 15/80 [2019-07-11 23:11:06.686]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:06.989]: AsyncBluetoothPairDeviceRequest - Connection attempt: 16/80 [2019-07-11 23:11:06.992]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:07.294]: AsyncBluetoothPairDeviceRequest - Connection attempt: 17/80 [2019-07-11 23:11:07.297]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:07.599]: AsyncBluetoothPairDeviceRequest - Connection attempt: 18/80 [2019-07-11 23:11:07.603]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:07.905]: AsyncBluetoothPairDeviceRequest - Connection attempt: 19/80 [2019-07-11 23:11:07.908]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:08.210]: AsyncBluetoothPairDeviceRequest - Connection attempt: 20/80 [2019-07-11 23:11:08.212]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:08.514]: AsyncBluetoothPairDeviceRequest - Connection attempt: 21/80 [2019-07-11 23:11:08.516]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:08.819]: AsyncBluetoothPairDeviceRequest - Connection attempt: 22/80 [2019-07-11 23:11:08.821]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:09.123]: AsyncBluetoothPairDeviceRequest - Connection attempt: 23/80 [2019-07-11 23:11:09.125]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:09.427]: AsyncBluetoothPairDeviceRequest - Connection attempt: 24/80 [2019-07-11 23:11:09.429]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:09.731]: AsyncBluetoothPairDeviceRequest - Connection attempt: 25/80 [2019-07-11 23:11:09.733]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:10.35]: AsyncBluetoothPairDeviceRequest - Connection attempt: 26/80 [2019-07-11 23:11:10.39]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:10.341]: AsyncBluetoothPairDeviceRequest - Connection attempt: 27/80 [2019-07-11 23:11:10.344]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:10.647]: AsyncBluetoothPairDeviceRequest - Connection attempt: 28/80 [2019-07-11 23:11:10.649]: AsyncBluetoothPairDeviceRequest - Patching the registry ... [2019-07-11 23:11:10.652]: AsyncBluetoothPairDeviceRequest - Failed to open registry key, it does not yet exist [2019-07-11 23:11:10.676]: AsyncBluetoothPairDeviceRequest - Checking HID service [2019-07-11 23:11:10.679]: AsyncBluetoothPairDeviceRequest - Verification attempt 0 / 5 [2019-07-11 23:11:10.682]: AsyncBluetoothPairDeviceRequest - Device Connected [2019-07-11 23:11:10.684]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:11:10.689]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:11:10.692]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled [2019-07-11 23:11:10.994]: AsyncBluetoothPairDeviceRequest - Verification attempt 1 / 5 [2019-07-11 23:11:10.997]: AsyncBluetoothPairDeviceRequest - Device Connected [2019-07-11 23:11:10.999]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:11:11.1]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:11:11.5]: AsyncBluetoothPairDeviceRequest - Connected, Remembered, and HID service enabled [2019-07-11 23:11:11.311]: AsyncBluetoothPairDeviceRequest - Verification attempt 2 / 5 [2019-07-11 23:11:11.423]: AsyncBluetoothPairDeviceRequest - Device Remembered [2019-07-11 23:11:11.425]: AsyncBluetoothPairDeviceRequest - HID service enabled [2019-07-11 23:11:11.439]: AsyncBluetoothPairDeviceRequest - HID service not enabled [2019-07-11 23:11:11.480]: AsyncBluetoothPairDeviceRequest - Verified failed. Re-establish connection [2019-07-11 23:11:11.502]: AsyncBluetoothPairDeviceRequest - Connection attempt: 0/80 [2019-07-11 23:11:11.526]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:11.828]: AsyncBluetoothPairDeviceRequest - Connection attempt: 1/80 [2019-07-11 23:11:11.830]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:12.132]: AsyncBluetoothPairDeviceRequest - Connection attempt: 2/80 [2019-07-11 23:11:12.136]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:12.441]: AsyncBluetoothPairDeviceRequest - Connection attempt: 3/80 [2019-07-11 23:11:12.444]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:12.747]: AsyncBluetoothPairDeviceRequest - Connection attempt: 4/80 [2019-07-11 23:11:12.750]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:13.52]: AsyncBluetoothPairDeviceRequest - Connection attempt: 5/80 [2019-07-11 23:11:13.54]: AsyncBluetoothPairDeviceRequest - Device not connected [2019-07-11 23:11:13.356]: AsyncBluetoothPairDeviceRequest - Connection attempt: 6/80 [2019-07-11 23:11:13.359]: AsyncBluetoothPairDeviceRequest - Device not connected