Audio Fix / setup help
Qudelix-5K: connect the Android app through its existing audio pair
Qudelix-5K — connect the Android app through its existing audio pair. Use the stated exact hardware and connection scope.
Manufacturer-documented Reviewed 2026-11-09 · Revision 1
Follow these checks in Audio Fix →When this guide applies
Exact Qudelix-5K. Exact Qudelix-5K and its already-installed connected official mobile app where stated. Stop if named controls or exact identity cannot be confirmed. Android audio pairing is active but the intended app cannot connect while another mobile app controls this 5K. Only one mobile app connection is supported at a time.
Connection scope: Bluetooth. Symptom: The control app cannot find my device.
This is a documented check, not a diagnosis of your equipment. The model name does not confirm the selected input, mode, software or connected partner.
If your exact model or a required setting is unknown, use the “I don’t know” branch below. Do not apply a similarly named model’s instructions.
Checks and possible outcomes
Start at scope. Follow the link that matches what you actually observe. Alternative branches are not a single sequence of actions.
scope
Confirm the model and connection
Exact Qudelix-5K and its already-installed connected official mobile app where stated. Stop if named controls or exact identity cannot be confirmed. Android audio pairing is active but the intended app cannot connect while another mobile app controls this 5K. Only one mobile app connection is supported at a time.
Look for: Confirm this exact setup and observation before continuing.
- If Yes, I confirm → Confirm audio connection
- If No / my setup differs → Continue with source and model support
- If I cannot confirm → More information is required
- Manufacturer-documented Qudelix-5K — official 5 k user manual ↗Manufacturer-linked manual PDF pages 4–44 and 47–51, read visually — Blue Lower hold>3 s powers on/off; Blue Upper hold>3 s pairs and single-press answers incoming calls. Red Lower/Upper change level 0.5 dB. Android app uses an existing BR/EDR pair and one mobile app connection; i OS BLE differs. Windows audio entry is Qudelix-5K Audio, not BLE. Normal 1V/High 2V gain, battery/USB charge status, input priority icons, phone USB versus Bluetooth output, EQ bypass/headroom and mic selection/pass-through are documented.Exact Qudelix-5K. · Source checked 2026-11-09
a1
Confirm audio connection
Inspect Android Bluetooth and confirm this exact 5K is already paired and actively connected.
Look for: Observe the named indication or available control; stop if absent.
- If I completed this check → Close the other app
- If I cannot complete this → Continue with source and model support
- If I cannot determine this → More information is required
- Manufacturer-documented Qudelix-5K — official 5 k user manual ↗Manufacturer-linked manual PDF pages 4–44 and 47–51, read visually — Blue Lower hold>3 s powers on/off; Blue Upper hold>3 s pairs and single-press answers incoming calls. Red Lower/Upper change level 0.5 dB. Android app uses an existing BR/EDR pair and one mobile app connection; i OS BLE differs. Windows audio entry is Qudelix-5K Audio, not BLE. Normal 1V/High 2V gain, battery/USB charge status, input priority icons, phone USB versus Bluetooth output, EQ bypass/headroom and mic selection/pass-through are documented.Exact Qudelix-5K. · Source checked 2026-11-09
a2
Close the other app
Close the Qudelix app on the other phone currently controlling this 5K, leaving that phone Bluetooth and unrelated peripherals unchanged.
Look for: Observe the named indication or available control; stop if absent.
- If I completed this check → Open intended app
- If I cannot complete this → Continue with source and model support
- If I cannot determine this → More information is required
- Manufacturer-documented Qudelix-5K — official 5 k user manual ↗Manufacturer-linked manual PDF pages 4–44 and 47–51, read visually — Blue Lower hold>3 s powers on/off; Blue Upper hold>3 s pairs and single-press answers incoming calls. Red Lower/Upper change level 0.5 dB. Android app uses an existing BR/EDR pair and one mobile app connection; i OS BLE differs. Windows audio entry is Qudelix-5K Audio, not BLE. Normal 1V/High 2V gain, battery/USB charge status, input priority icons, phone USB versus Bluetooth output, EQ bypass/headroom and mic selection/pass-through are documented.Exact Qudelix-5K. · Source checked 2026-11-09
a3
Open intended app
Open the already-installed Qudelix Android app on the intended paired phone.
Look for: Observe the named indication or available control; stop if absent.
- If I completed this check → Inspect identity
- If I cannot complete this → Continue with source and model support
- If I cannot determine this → More information is required
- Manufacturer-documented Qudelix-5K — official 5 k user manual ↗Manufacturer-linked manual PDF pages 4–44 and 47–51, read visually — Blue Lower hold>3 s powers on/off; Blue Upper hold>3 s pairs and single-press answers incoming calls. Red Lower/Upper change level 0.5 dB. Android app uses an existing BR/EDR pair and one mobile app connection; i OS BLE differs. Windows audio entry is Qudelix-5K Audio, not BLE. Normal 1V/High 2V gain, battery/USB charge status, input priority icons, phone USB versus Bluetooth output, EQ bypass/headroom and mic selection/pass-through are documented.Exact Qudelix-5K. · Source checked 2026-11-09
a4
Inspect identity
In DEVICE inspect CONNECTION for Qudelix-5K before any setting change.
Look for: Observe the named indication or available control; stop if absent.
- If I completed this check → Check the result
- If I cannot complete this → Continue with source and model support
- If I cannot determine this → More information is required
- Manufacturer-documented Qudelix-5K — official 5 k user manual ↗Manufacturer-linked manual PDF pages 4–44 and 47–51, read visually — Blue Lower hold>3 s powers on/off; Blue Upper hold>3 s pairs and single-press answers incoming calls. Red Lower/Upper change level 0.5 dB. Android app uses an existing BR/EDR pair and one mobile app connection; i OS BLE differs. Windows audio entry is Qudelix-5K Audio, not BLE. Normal 1V/High 2V gain, battery/USB charge status, input priority icons, phone USB versus Bluetooth output, EQ bypass/headroom and mic selection/pass-through are documented.Exact Qudelix-5K. · Source checked 2026-11-09
observe
Check the result
Does the intended Android app display this exact 5K?
Look for: Confirm this exact setup and observation before continuing.
- If Yes, I confirm → Checks completed
- If No / my setup differs → Continue with source and model support
- If I cannot confirm → More information is required
- Manufacturer-documented Qudelix-5K — official 5 k user manual ↗Manufacturer-linked manual PDF pages 4–44 and 47–51, read visually — Blue Lower hold>3 s powers on/off; Blue Upper hold>3 s pairs and single-press answers incoming calls. Red Lower/Upper change level 0.5 dB. Android app uses an existing BR/EDR pair and one mobile app connection; i OS BLE differs. Windows audio entry is Qudelix-5K Audio, not BLE. Normal 1V/High 2V gain, battery/USB charge status, input priority icons, phone USB versus Bluetooth output, EQ bypass/headroom and mic selection/pass-through are documented.Exact Qudelix-5K. · Source checked 2026-11-09
Possible result
More information is required
An unknown state is not a diagnosis. Record the last visible indication and consult the exact model instructions.
insufficient data
Reaching this result does not mean the issue is solved. Only your own feedback can report improvement.
Possible result
Continue with source and model support
Keep the source, connection and last observation. Do not reset, open equipment or change full-scale output to compensate for an unconfirmed result.
next support
Reaching this result does not mean the issue is solved. Only your own feedback can report improvement.
Possible result
Checks completed
The requested observation was confirmed in this setup. It does not establish a hardware repair or guarantee another source behaves the same.
steps completed
Reaching this result does not mean the issue is solved. Only your own feedback can report improvement.