Twiddler

Isolate where the issue resides. Connect the Twiddler to another host (PC, Tablet, Phone, etc…) and see if the issue occurs on the new host. If it does, the issue resides in the Twiddler. If it doesn't, the issue resides in the host.

1. Problem: Twiddler does not charge when plugged into USB-C on host or USB-C wall adapter.
   Solution: Try USB-C (Twiddler) to USB-A (host/adapter) cable.

1. Problem: Bluetooth performance low.
   Solution: RF performance is not guaranteed due to the variability of RF interference in each user's environment. Also, the performance of Bluetooth radios and antennas of host systems are also variable. If you are noticing a degradation of the Bluetooth performance try the following:
   • Establish a clear line of site between the Twiddler and your host's Bluetooth Antenna. PC Cases are excellent shields.
   • Charge the battery of the Twiddler.
   • Move to a known “clean” RF environment and see if that solves the issue.
   • Try an external Bluetooth module if your host has an internal Bluetooth Module.
   • Get closer to the Host's Bluetooth Radio.
     
     
2. Problem: Bluetooth performance low while connected to USB C on host computer.
   Solution: Use an extension cable to locate your external USB dongle away from the USB port on your host. Click here for more information
   
   
3. Problem: You can see the Twiddler in the Bluetooth Neighborhood but will not pair.
   Solution: Remove the Twiddler from the host's Bluetooth table. THEN, Erase the Twiddler's Bluetooth pair table by typing T14F4R. You will also need to re-pair the Twiddler with any other device you have paired with in the past.
   
   
4. Problem: You can pair the Twiddler in the Bluetooth Neighborhood but get a “Driver Error” once paired. Twiddler works fine if connected via USB.
   Solution:
   • Remove the Twiddler from your host's Bluetooth List.
   • Reset Twiddler's Bluetooth pair table by typing T14F4R.
   • You will also need to re-pair the Twiddler with any other device you have paired with in the past.
     
     
5. Problem: Twiddler does not pair with your host and does not even show up in the host's Bluetooth Neighborhood .
   Solution: The host does not support BLE 4.2. Install a Bluetooth device that supports BLE 4.2 like the LM506. https://www.tekgear.com/lm506.html
   
   
6. Problem: Bluetooth connection is intermittent or will not pair
   Solution:
   • Remove the Twiddler from your host's Bluetooth List.
   • Ensure battery is charged.
   • Enter bootloader mode while unplugged from USB (sleep, then hold T14 while waking the device by tapping T0).
   • Let the device time out and go to sleep (about 1 minute).
   • Wake the device.
   • Reset the Bluetooth pairs T14F4R.

If you have a Bluetooth dongle connected to a USB 3 port on your host, you may experience decreased Bluetooth performance. Popular motherboard manufacturers, like Intel and Asus, have white papers on this subject.

Here are links to:

1. The Asus white paper:
   • https://www.asus.com/support/FAQ/1004004/
     
     
2. The Intel white paper:
   • Download from USB.org
   • Download Local copy

The easiest solution to mitigate the RF interference is to get a USB extender cable and plug the dongle further away from the host's USB 3 port.

1. Problem: USB Drive does not mount.
   Solution 1 : Replace the USB cable. Most of the time, it is a cable issue. Either data or power is not flowing through the cable and is causing the error. If plugged in to a USB port, it just means power is flowing. It could be the data lines in the cable are not present or have been compromised.
   Solution 3 : Try a new USB Port that is known to work. Some systems have locked down USB ports or ports that are broken so plugging in to them will not work. Also, by changing ports, the OS will go through the enumeration process for the Twiddler USB Drive again and reload the driver.
   Solution 4 : Try a new computer. Sometimes it is a computer issue. Security settings set too high, Anti-virus getting in the way, or a hardware malfunction, trying a new computer may help to confirm the issue.
   

1. Problem: USB Drive mounts but is inaccessible.
   Solution 1 : Reformat the USB Drive. Format in FAT with an allocation unit size of 512. (The standard settings for FAT Formatting)