Shizako

• Fixed the issue of "pairing failed but the interface showed that it was paired", and the issue of no prompt when pairing failed.
• Repair and optimization Pairing status is no longer misleading : Previously, as long as pairing was initiated even once (whether due to an incorrect pairing code, a port inaccessibility, or cancellation midway), a wireless debugging key would be left locally, causing the activation page to display "Paired"—even though the device did not recognize this key. Now, the key is only written to disk when pairing is truly successful , and a separate success record is made. The "Paired" status is based on this record. Pairing failure will now explain the reason : Previously, when pairing failed, the client would only reply with one message false, and the interface would display nothing; the user would only see a "spinning circle, then nothing." Now, it will differentiate between three situations: incorrect or expired pairing code , inability to establish an encrypted connection (port or pairing code expired) , and pairing being interrupted by the device . The corresponding next steps will be provided in the dialog box and notification bar. Key generation failure no longer blocks notifications : Previously, if the pairing path in the notification bar encountered a key generation failure, it would exit directly, and the notification would remain permanently stuck in "Pairing"; now, a clear failure message will be displayed. Automatic status recovery : For users upgrading from older versions or who already have a usable key locally, the pairing record will be automatically added after the service starts successfully, eliminating the need for re-pairing; "Forgot to pair" will now also clear successful records.

Write a review

• Николай today