Q1: Why I couldn't connect my detectors to my Android 7 smartphone?

We have found that there are issues when connecting to CT007 series detectors using some phones running Android 7. This seems to be caused by an incompatibility between the way Android 7 handles Bluetooth versions and our firmware's Bluetooth stack, which creates issues during service discovery. The latest release of GammaGuard (4.4.11) aims to address this issue. To get the full benefit of this update, your CT007 detector's firmware should be updated. The procedure to do so is as follows.

If possible, use an Android phone not running Android 7 to perform the firmware update. Android versions 4.3, 5, 6, and 8+ should all work better. If that's not possible, an Android 7 phone can perform the update as well, but it may take several connection attempts before a successful connection is made.

  1. Install the latest release of GammaGuard (4.4.11)
  2. Power on the CT007 detector and start GammaGuard.
  3. From the main GammaGuard menu (top left icon, or drag in from left of screen), go to 'Settings' under 'External'.
  4. When prompted for a password, enter the default '1234'.
  5. Scroll down to the 'Automatic Firmware Updates' setting, and enable it. (Second last setting in the list.)
  6. Make sure that the 'Clear Bluetooth Cache' setting is DISABLED. (That is the default setting, unless you previously changed it.)
  7. Go to 'External Detector', and connect to your detector. As noted above, this may take several connection attempts before successfully connecting.
  8. Once connected, the firmware update should start automatically.
  9. Let the update finish and you will be automatically connected once it is done.

Note that if for any reason the update fails or is interrupted, it can be restarted and resumed as many times as necessary, with no risk of permanently bricking your detector. Even if you need to resume later from another phone. All you will need to do is choose your device type from a list (for example, a CT007-F would choose a device type of 'F') when prompted, then enter the serial number from your label.

Once the firmware is updated, connections to Android 7 devices should go better. Once the CT007 detector has been connected to  a particular phone, the connection parameters are cached and subsequent connections are much quicker.

After your Firmware is updated, you may want to disable the  'Automatic Firmware Updates' setting again. This also speeds up connection and it prevents GammaGuard from starting Firmware updates at inopportune times.

Q2: What happens when a firmware update on GammaGuard fails? Why can't I find my detectors in the scan list?

All our detectors use BotSpine as their firmware platform. During the firmware update process, lines of code are erased, then re-programmed over the air via Bluetooth. If the process gets interrupted due to a bad Bluetooth connection or other reasons, the incomplete firmware will cause the detector to not function properly.

To fix this, you will need to reconnect your detector to GammaGuard, and complete the firmware update. When connecting this time, the app may not recognise the detector as "CT-X-YY" in the scan list, due to the incomplete firmware. This doesn't mean the detector is not advertising though. Instead it may appear as "BASIC#XX" or "BOTSP#XX", which is the name of the firmware platform, then the last two characters of its MAC address. Click and connect to the detector named  "BASIC#XX" or "BOTSP#XX" in the scan list. A pop-up window may ask you to select detector type and then detector number. Choose the type and number based on the sticker on top of your detector. So for a CT007-F, the detector type would be “F”. After this, the firmware update will start. This will take a few minutes to complete. Once the update is completed and successful, your detector will be automatically connected to the app.

If you continue to experience issues, if possible, try performing the update using another phone. Some Android phones have inherently unreliable Bluetooth connections, which can make updating difficult or impossible. Note though, that permanently bricking the detector during an update should not be possible, as it can always be attempted again on another phone.

Q3: Why do my detectors stop advertising (not appearing on scan list) and why does the OLED not turn back on after disconnecting from GammaGuard?

This may happen on Android phones after many connections. When you disconnect your detector, it seems to be disconnected from GammaGuard, but the phone hasn’t properly closed the connection. The leaves the detector in a connected state, with the OLED display off and not advertising.

If you encounter this situation, try to restart your phone. After a restart, the phone’s Bluetooth should resume working properly, and the problem should be fixed.

Not advertising (appearing in scan list) can also be fixed by turning the detector off and on again. It is still a good idea to restart your phone though, as its Bluetooth not working properly is generally the cause of this state.

Q4: When I try to connect my detector to GammaGuard, why does it display “not a compatible detector” and the connection fails?

This may happen when the phone has cached incorrect Bluetooth credentials for the detector, possibly during a firmware update or a failed connection. If this happens, check the “clear Bluetooth Cache” option in the external detector settings. After a successful connection, the proper Bluetooth credentials should be stored. This setting can then be disabled again, as it may unnecessarily increase Bluetooth connection times.

If you have questions that are not listed above or still have troubles after following the solutions, please don't hesitate to contact us