Jump to content

rowan_u

Verified Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by rowan_u

  1. It appears the app can now recover from this condition VS requiring a full reboot.  Still very clunky as it takes a good 20 seconds to recover.  Here is my log file from a recent instance.

    Quote

    [2021-05-31 06:13:29.949 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
    [2021-05-31 06:13:29.949 -6 0x32E4 INFO LOG] [SetCosmosAudio] Terminate OK.
    [2021-05-31 06:13:29.949 -6 0x32E4 INFO LOG] Show error code : 10001.9
    [2021-05-31 06:13:29.952 -6 0x32E4 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
    [2021-05-31 06:13:30.383 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
    [2021-05-31 06:13:30.383 -6 0x32E4 INFO LOG] Show error code : 10001.9
    [2021-05-31 06:13:30.385 -6 0x32E4 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
    [2021-05-31 06:13:30.613 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_COMMAND_IN_PROGRESS(12)
    [2021-05-31 06:13:30.613 -6 0x32E4 INFO LOG] Show error code : 10001.12
    [2021-05-31 06:13:30.616 -6 0x32E4 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
    [2021-05-31 06:13:31.018 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_NOT_SCANNING(16)
    [2021-05-31 06:13:31.021 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_SCANNING(4), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
    [2021-05-31 06:13:31.023 -6 0x32E4 INFO LOG] Connection Status set to 2(CONNECTION_STATUS_SCANNING)
    [2021-05-31 06:13:34.238 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTING(5), reason = SDK_CURRENT_STATE_REASON_AUTO_PROFILE_FOUND(4)
    [2021-05-31 06:13:34.240 -6 0x32E4 INFO LOG] Connection Status set to 3(CONNECTION_STATUS_CONNECTING)
    [2021-05-31 06:13:34.501 -6 0x363C INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTED(7), reason = SDK_CURRENT_STATE_REASON_SUCCEED_TO_CONNECT(13)

     

  2. 11 hours ago, CMDRZOD said:


    Seems to be something to do with the Intel SDK software. Would be nice for HTC to address this issue. It plagues many users. 

     

    Perhaps it's just something that's impossible to fix . . . it would be nice if they would even just admit its a known issue.  Even with having to reboot the PC every few hours to clear this error, wireless is still the best way to play :)

  3. I have this issue also, have tried absolutely everything to fix it.  Sometimes the screen goes black for just a few seconds then recovers . . . other times it goes black, game and tracking is still running (I can tell because of 3d sound sources); however the only way to recover is unplug the headset power, then reboot it on the fly.  Most of the time everything recovers without issue after the headset reboots. 

×
×
  • Create New...