A computer does not need Bluetooth to play through a speaker that genuinely supports USB audio. Use the documented USB-audio model, a suitable data connection and the computer's sound-output selection, then verify the result in the application you actually use. You do not need to add wireless pairing to that wired setup.
The procedure uses Tiivoo-2 as an exact-model example and Windows as a supported output-selection example. A USB port used only for charging is a different capability. Confirm that distinction before arranging the desk or buying an adapter, because a cable cannot create an input the speaker does not document.
What is the minimum equipment for the wired setup?
Check the speaker's manual for an explicit computer-speaker, USB-audio or sound-card mode. The USB Implementers Forum's Type-C naming guidance distinguishes connector naming from performance and power. Use that as a reason to look up actual model support, not as proof that every Type-C speaker accepts sound.
- A computer with an available supported USB data path.
- A speaker whose exact instructions document USB audio.
- The manufacturer-specified cable or a verified suitable data cable.
- Any required power arrangement and a stable place for the speaker.
- An ordinary known audio item in the application you intend to use.
Inspect the computer port and cable ends before connecting. If an adapter is necessary, verify the complete chain rather than checking only whether both ends fit. Use a direct supported connection when available for the initial setup so that an extra hub does not become an unexplained dependency.
Our recommendation is to prepare this minimum kit before changing sound settings. It keeps a missing accessory or an undocumented speaker input from being mistaken for a Windows setting problem.
How do you make the documented connection?
For this wired computer task, Divoom Tiivoo-2 is a useful example because its computer-speaker mode instructions explicitly describe a USB sound-card connection. The manual names “Tiivoo” as the sound output to choose afterward. That supports a computer without Bluetooth, provided the actual cable and system path meet the documented conditions; it does not establish microphone input for calls.
Divoom Tiivoo-2 Retro Pixel Bluetooth Speaker with Photo Album Display Divoom Tiivoo-2 retro pixel Bluetooth speaker with photo album display, FM radio, alarm, and app-controlled pixel art. $85.99 USD Buy now
- Place the speaker on its stable intended surface with the controls reachable.
- Finish any existing listening session and prepare the documented power arrangement.
- Connect the specified USB cable between the speaker and the appropriate computer port.
- Observe the model's documented USB-audio state and let the computer complete its normal device recognition.
- Proceed to output selection only when the intended audio device is available.
The example manual describes automatic USB sound-card switching and automatic driver installation on a first connection. Treat that as the documented workflow, not a promise that every computer finishes without intervention. If the actual state differs, note it and use current manufacturer and operating-system guidance rather than downloading a driver from an unrelated site.
Keep the cable route visible during the initial setup. You can tidy it after audio works. Hiding a new connection behind the monitor before observing the result makes it harder to check the plug, read a label or identify which cable belongs to the speaker.
How do you select the right output on the computer?
Open your current system sound-output controls and choose the intended recognized device. For the named model, the manual says to select “Tiivoo.” If the computer lists several outputs, do not choose by position in the list; identify the one corresponding to the actual connected speaker.
Microsoft's sound-output troubleshooting guidance says to check that the appropriate output is selected when several audio devices are available. A laptop's own speakers, headphones or a connected display can remain the destination even after an external USB device is recognized.
Start with a modest listening level on the computer and speaker. Check the application as well: its own mute or volume controls can make a valid system output appear silent. Increase only as needed for the real room rather than using maximum volume as a recognition test.
If you use another operating system, follow its current documented output controls. The task is the same—choose the actual playback endpoint—but the menu names and supported device behavior need their own verification. Do not copy a Windows label onto a different system and assume it describes the same screen.
What proves the setup is ready for your actual work?
Play the known audio item and confirm that sound comes from the external speaker, not the computer or another device. Pause and resume it, then check that the volume control you expect to use affects the intended output. This is the useful listening result, not just evidence that a new device name appeared.
- Confirm a recognizable item through the newly selected output.
- Open the application that matters for your routine and check its actual program audio.
- Pause, resume and adjust the relevant controls at an ordinary starting level.
- Move the speaker and cable into their final arrangement without straining the connection.
- Repeat the short application check in that final position.
Record any narrower result honestly. “System audio works, but the meeting application is still using headphones” is a different state from “the computer does not recognize the speaker.” It tells you to check the application's device selection instead of rebuilding the physical path.
Do not infer low latency, a particular sound quality or compatibility with every game from this basic setup check. Those are different requirements. If timing matters, evaluate the actual task separately and compare under consistent conditions.
What changes when the application is a call or meeting?
A listening output and a microphone are separate choices. A working USB speaker can play another person's voice without becoming the device that captures yours. Keep the computer microphone, a headset or another verified input available until the actual input path is checked.
Microsoft's Teams device-settings guidance treats speaker and microphone selections separately. In that application, choose the intended listening output and an input that is actually present and supported. Verify both in a test appropriate to the current application rather than using a music track as evidence that the other person can hear you.
Listen for an unwanted feedback or echo problem at a modest level. If the arrangement does not suit a call, use a known-working headset or another appropriate audio setup while investigating. Do not raise the speaker level to compensate for an unverified microphone path or promise that the device supplies conferencing features its instructions do not establish.
How do you keep the routine easy to repeat?
Once the intended application works, identify the cable and leave enough access to reconnect it without moving the whole desk. Note the recognized output name and any separate application selection. Do not save passwords or unrelated account details in that note.
After disconnecting or changing equipment, check the selected output again. This guide does not guarantee that every system preserves the same choice through sleep, updates or another connected device. A brief real-audio check is more useful than assuming yesterday's state remains current.
If the computer has no suitable available USB path, or the speaker does not support USB audio, pause this procedure. Use another genuinely supported connection, a known-working existing output or an appropriate replacement only after checking the full requirement. Bluetooth hardware is an optional separate approach, not a prerequisite for the documented wired setup.
The routine is complete when your actual application plays through the intended supported speaker and you can repeat the connection with the equipment you have. Keep those conditions clear, and the absence of Bluetooth stops being an obstacle to this particular task.
Identify any necessary adapter in the kit note so that someone borrowing the cable returns the complete working path.
