Razer Pro Click and Pro Click Mini: Difference between revisions

Line 25:

The Bluetooth functionality is limited to three different actions by design: A slider enables Bluetooth, a button cycles through three different connection profiles and if not already connected, a channel goes directly into pairing mode. Channels are identified by colors (blue, green, yellow). Pairing mode is displayed by a blink-blink-pause pattern, connection mode by a single long on-time before the LED turns off<ref>{{Cite web |title=How to pair or connect a wireless mouse to a system via Bluetooth or USB Dongle |url=https://mysupport.razer.com/app/answers/detail/a_id/5387/~/how-to-pair-or-connect-a-wireless-mouse-to-a-system-via-bluetooth-or-usb-dongle |access-date=2025-04-19 |website=Mysupport.Razer.com}}</ref>.

Users of the devices have noticed, that once every channel has been paired to a device once, one can no longer enter pairing mode in any channel. The LED keeps blinking, but the device can not be seen by any other Bluetooth-capable device in range. Pressing the button for five seconds or longer also does nothing. Since there is no hardware-reset built into the device, there is no physical way of resseting the connections. Some users have reported, that connecting to an Android or Linux device can teporarily "fix" this bug. However, this seems to require at least one of the three channels to be still free to connect. Some users supposedly had success in disconnecting and removing their ~~mouses~~ from the Bluetooth list of their Windows or Linux devices. Firmware updates have yet to address the bug. When all three Bluetooth channels are blocked by the bug, there is no way for the Synapse software to recognize the device anymore. It seems, the RF USB dongle does not offer extended connectivity and only transmits mouse movement and button presses. Without a possibility to connect to Razer software<ref>{{Cite web |title=Software and Firmware Updates for Razer Peripherals |url=https://mysupport.razer.com/app/answers/detail/a_id/4166/~/software-and-firmware-updates-for-razer-peripherals |access-date=2025-04-19 |website=Mysupport.Razer.com}}</ref>, firmware updates for the mice are impossible to conduct (updating the RF USB dongle is still possible, but this will not fix the BT issue).

Users of the devices have noticed, that once every channel has been paired to a device once, one can no longer enter pairing mode in any channel. The LED keeps blinking, but the device can not be seen by any other Bluetooth-capable device in range. The computer mice might not even connect to formerly paired devices anymore<ref>Own experience while troubleshooting.</ref>. Pressing the button for three-five seconds or longer also does nothing. Since there are no hardware-reset buttons or similar measures built into the device, there is no physical way of resseting the connections. Some users have reported, that connecting to an Android or Linux device can teporarily "fix" this bug. However, this seems to require at least one of the three channels to be still free to connect. Some users supposedly had success in disconnecting and then completely removing their mice from the Bluetooth list of their Windows or Linux devices. Firmware updates have yet to address the bug. When all three Bluetooth channels are blocked by the bug, there is no way for the Synapse software to recognize the device anymore. It seems, the RF USB dongle does not offer extended connectivity and only transmits mouse movement and button presses. Without a possibility to connect to Razer update software<ref>{{Cite web |title=Software and Firmware Updates for Razer Peripherals |url=https://mysupport.razer.com/app/answers/detail/a_id/4166/~/software-and-firmware-updates-for-razer-peripherals |access-date=2025-04-19 |website=Mysupport.Razer.com}}</ref>, firmware updates for the mice are impossible to conduct (updating the RF USB dongle is still possible, but this will not fix the BT issue).

As of April 2025, there is no official statement by Razer regarding this issue. Customer requests are seemingly answered, but end with no solution to the bug other than replacement devices (which may break again soon after).

@@ Line 25: / Line 25: @@
 The Bluetooth functionality is limited to three different actions by design: A slider enables Bluetooth, a button cycles through three different connection profiles and if not already connected, a channel goes directly into pairing mode. Channels are identified by colors (blue, green, yellow). Pairing mode is displayed by a blink-blink-pause pattern, connection mode by a single long on-time before the LED turns off<ref>{{Cite web |title=How to pair or connect a wireless mouse to a system via Bluetooth or USB Dongle |url=https://mysupport.razer.com/app/answers/detail/a_id/5387/~/how-to-pair-or-connect-a-wireless-mouse-to-a-system-via-bluetooth-or-usb-dongle |access-date=2025-04-19 |website=Mysupport.Razer.com}}</ref>.
-Users of the devices have noticed, that once every channel has been paired to a device once, one can no longer enter pairing mode in any channel. The LED keeps blinking, but the device can not be seen by any other Bluetooth-capable device in range. Pressing the button for five seconds or longer also does nothing. Since there is no hardware-reset built into the device, there is no physical way of resseting the connections. Some users have reported, that connecting to an Android or Linux device can teporarily "fix" this bug. However, this seems to require at least one of the three channels to be still free to connect. Some users supposedly had success in disconnecting and removing their mouses from the Bluetooth list of their Windows or Linux devices. Firmware updates have yet to address the bug. When all three Bluetooth channels are blocked by the bug, there is no way for the Synapse software to recognize the device anymore. It seems, the RF USB dongle does not offer extended connectivity and only transmits mouse movement and button presses. Without a possibility to connect to Razer software<ref>{{Cite web |title=Software and Firmware Updates for Razer Peripherals |url=https://mysupport.razer.com/app/answers/detail/a_id/4166/~/software-and-firmware-updates-for-razer-peripherals |access-date=2025-04-19 |website=Mysupport.Razer.com}}</ref>, firmware updates for the mice are impossible to conduct (updating the RF USB dongle is still possible, but this will not fix the BT issue).
+Users of the devices have noticed, that once every channel has been paired to a device once, one can no longer enter pairing mode in any channel. The LED keeps blinking, but the device can not be seen by any other Bluetooth-capable device in range. The computer mice might not even connect to formerly paired devices anymore<ref>Own experience while troubleshooting.</ref>. Pressing the button for three-five seconds or longer also does nothing. Since there are no hardware-reset buttons or similar measures built into the device, there is no physical way of resseting the connections. Some users have reported, that connecting to an Android or Linux device can teporarily "fix" this bug. However, this seems to require at least one of the three channels to be still free to connect. Some users supposedly had success in disconnecting and then completely removing their mice from the Bluetooth list of their Windows or Linux devices. Firmware updates have yet to address the bug. When all three Bluetooth channels are blocked by the bug, there is no way for the Synapse software to recognize the device anymore. It seems, the RF USB dongle does not offer extended connectivity and only transmits mouse movement and button presses. Without a possibility to connect to Razer update software<ref>{{Cite web |title=Software and Firmware Updates for Razer Peripherals |url=https://mysupport.razer.com/app/answers/detail/a_id/4166/~/software-and-firmware-updates-for-razer-peripherals |access-date=2025-04-19 |website=Mysupport.Razer.com}}</ref>, firmware updates for the mice are impossible to conduct (updating the RF USB dongle is still possible, but this will not fix the BT issue).
 As of April 2025, there is no official statement by Razer regarding this issue. Customer requests are seemingly answered, but end with no solution to the bug other than replacement devices (which may break again soon after).