B1 Troubleshooting Tips — Audioengine Skip to Content
Support

B1 Troubleshooting Tips

The following troubleshooting tips can help diagnose and correct most concerns with the B1. We have attempted to make this list as comprehensive as possible. So, even though some of these may not apply to your issue, please still go through each one.

If you haven’t already, power cycle your B1 by unplugging the power connection, and reconnecting it.

1) Please make sure all of your connections are complete; also, check that all of your connector cables are in working order. You will want to swap out some interconnects to test for this.

2) Try playing audio from more than one application on your source device (phone, tablet, computer, etc.)

3) Check to make sure your source device is running the most up to date version of software available. If an update is available, make sure you restart your device after the update is installed.

4) Try disconnecting from, and "forgetting" the B1 through your source's Bluetooth settings. Then, try re-pairing and connecting to the B1. If your B1 is already connected to a device, then the LED will be on and solid. If your B1 has been idle (and not connected to a device) for more than two minutes, the LED will be off. Tap the LED and it will begin blinking to indicate it is ready to pair, then select the B1 in the Bluetooth settings of your source device. If your B1's LED indicator doesn’t light up, try using a different power source, and/or micro USB cable (many Android smartphones use the same connection, so your charger may be a good way to test for this).

5) Try using a different source device with your B1 to see if the issue follows. Try using the analog as well as the digital optical output, to see if you have this issue with both connections.

6) If at all possible, try your B1 in a different location and / or setup to see if something is causing interference in the current location. Something as simple as a router, cordless / mobile phone, halogen lamps, etc. near the speakers may be causing the issue in your setup.

View support page