If a TV-style speaker works over Bluetooth but not USB, first confirm that the exact model supports USB audio. Then isolate the USB path: a suitable data cable, a direct computer port, the documented speaker mode and the selected computer output. Bluetooth playback confirms one working audio route; it does not test every part of the USB route.
The Tiivoo-2 example below explicitly documents USB sound-card mode. If your model documents only USB charging, silence over that connection may be a capability mismatch rather than a fault. Do not apply these model-specific mode instructions to a different device simply because the enclosure looks similar.
What does the working Bluetooth connection establish?
Write the successful result precisely: which source played, which speaker produced sound and which audio item was used. “The phone plays this song through the speaker over Bluetooth” is useful evidence. It is narrower than “the speaker is fine,” because a different input can involve a different cable, mode or computer setting.
Define the USB failure just as carefully. Does the computer show an output device? Does the speaker show the expected mode? Is the result silence, sound from the laptop instead or intermittent output? These observations lead to different checks and should not all become “USB is broken.”
Our recommendation is to keep the audio item and speaker placement as consistent as practical while changing the input path. Begin at a modest volume and use one ordinary recognizable item. That makes the comparison about USB delivery rather than an unfamiliar app, a silent file or a different physical setup.
Does this model actually accept audio through USB?
Check the exact manual for a computer-speaker, USB-audio or sound-card mode. A charging section alone does not establish that the port accepts digital audio. The USB Implementers Forum's USB Type-C guidance explains that performance and power capabilities vary; the connector name does not supply the missing model-specific promise.
For a documented case, Divoom Tiivoo-2 fits this comparison because its computer-speaker instructions describe connecting to a computer, switching to USB sound-card mode and selecting “Tiivoo” as the sound output. That gives you a real USB path to investigate. It does not establish support for an undocumented adapter, every operating system or a computer microphone input.
Altoparlante Bluetooth Pixel retrò Divoom Tiivoo-2 con display per album fotografico Divoom Tiivoo-2 retro pixel Bluetooth speaker with photo album display, FM radio, alarm, and app-controlled pixel art. $85.99 USD Buy now
If the exact model does not document the capability, pause that branch and ask model-specific support before buying more accessories or changing system settings. Keep using a supported working source if it meets the immediate task. A connector that supplies power can be behaving as designed without supplying the audio path you expected.
How do you isolate the cable and computer port?
Begin with the cable specified for the documented USB-audio workflow, or a verified suitable data cable meeting the device's requirements. A charging indication shows a power observation, not the completion of computer-audio recognition. Keep those results separate.
- Pause competing playback and note the current working source.
- Connect the documented speaker directly to an appropriate computer USB port with the intended cable.
- Remove an unnecessary hub or adapter from the diagnostic path where a direct supported connection is available.
- Observe whether the computer recognizes an audio output before changing another item.
- If needed, change one known suitable cable or one supported port, then repeat the same recognition check.
Do not replace several components at once. If a new cable, another hub and a different app are introduced together, a changed result does not tell you which part mattered. Record each trial with the cable, port and observation so the next step follows the evidence.
Stop using a damaged connector or cable. Do not force a plug, open the speaker or modify the port to make the connection fit. Keep the direct cable route accessible while you test, with enough slack to operate the computer and speaker controls. A connection that works only while someone holds a damaged part in position is not an acceptable result.
Is the speaker listening to USB rather than another source?
Look for the model's documented USB mode rather than assuming power automatically means the correct source is selected. The Tiivoo-2 manual describes automatic USB sound-card switching on connection, but the observed result still needs checking. If the display or controls do not match that state, record what they actually show.
Keep a TF card and a phone from becoming unexamined variables. The same manual documents TF-card insertion as another mode trigger. Start a clean test with only the intended source arrangement, following the actual handling instructions for any card, and use documented mode controls if needed.
Do not infer that removing one source must restore another. Selecting USB, leaving TF playback and reconnecting Bluetooth are different transitions. Verify the resulting mode after each change rather than repeatedly reconnecting everything and calling the final state obvious.
Is the computer sending sound to the recognized output?
If the computer recognizes the intended USB audio device, select it as the listening output. For Windows, Microsoft's audio troubleshooting guide calls for checking the chosen device when multiple outputs are available. Built-in speakers, a display and a headset can otherwise remain the destination.
The example manual names “Tiivoo” as the output to select. Use the actual device shown by your system and the current model instructions; do not guess that a similarly named display-control connection is the same audio endpoint. Other operating systems need their own documented sound-output path.
Play the same known audio item and check system, app and speaker volume controls without jumping straight to a high setting. Microsoft's guidance also notes that speakers and applications can have separate controls. If sound appears from the computer instead, record an output-selection problem rather than calling the external speaker silent.
If the output never appears, return to the documented cable, port and mode checks. Repeatedly changing an application's volume will not establish device recognition. Avoid unverified driver-download sites or a factory reset offered by an unrelated tutorial; use the exact manufacturer's and operating-system support route when the basic path remains unresolved.
What does each result tell you, and when should you escalate?
Use the observed result to describe the unresolved branch. The table is a guide to the next question, not a diagnosis of a failed component.
| Observation | Next focused question |
|---|---|
| Power indication, no audio output recognized | Is the data path and exact USB-audio mode established? |
| Output recognized, sound stays on computer | Is the intended system and application output selected? |
| Output selected, one app silent | Does the same known item work through another appropriate playback check? |
| Failure follows one cable or port | Can that observation be repeated while other conditions stay fixed? |
Before contacting support, record the exact model, computer and operating system, cable, direct port or adapter, selected mode, recognized output and the last working comparison. Include the steps already tried so the helper does not have to begin with the same uncertain description.
Stop the test when equipment is damaged, an abnormal condition appears or the remaining step would require an undocumented reset or modification. A working Bluetooth fallback can serve the immediate listening task while the USB branch remains unresolved. Keep that distinction visible rather than declaring a repair that has not happened.
When a change produces sound, return to the original intended application and repeat its ordinary listening task before calling the path restored. Check pause, resume and the final selected output after placing the speaker where it will be used. A one-time test sound from a system panel is narrower evidence than the application audio the user actually needs.
Keep the working cable identifiable and note any adapter removed from the path. That small record preserves the successful configuration without claiming the removed accessory was defective; a different supported setup may use it successfully.
