| Test record | What it establishes |
|---|---|
| Port and cable | The physical connection actually used |
| Charging observation | Power behaviour in that test only |
| Data function | The specific supported function demonstrated |
| Projection | A separate CarPlay or Android Auto result |
| Accessory | Identity, inclusion and support responsibility |
List the ports on the actual vehicle
Ask for clear photographs showing each accessible socket and its location. Record the connector shape and any nearby label without assigning a capability from shape alone. Keep front and rear sockets separate in the checklist. A charging outlet for passengers need not serve the same function as the port used by the multimedia system.
Changan Azerbaijan's regional X5 PLUS page lists USB and Type-C ports together with Bluetooth among its equipment. That regional listing does not establish the capabilities of every source-market vehicle. Use the vehicle specification record to connect the equipment claim to the candidate instead of assuming a brochure for another configuration answers the question.
Define the task before testing a connection
Write down whether the buyer needs charging, calls, audio, a supported data function or phone projection. These tasks require separate observations. Include the phone model, software version and intended cable or accessory in the test record. Avoid a broad entry such as USB works when the operator has only confirmed that the charging icon appears.
The CarPlay and Android Auto buying guide covers the projection requirement and any advertised adapter. This page focuses on the physical connection and the evidence needed to reproduce it. If a seller advertises operation without an adapter, ask for a clear view of the connection path rather than a cropped screen video that leaves the installed equipment unknown.
Start with an uncomplicated stationary demonstration
Have the operator park safely and follow the applicable vehicle and device instructions. Use an undamaged, suitable cable and the intended socket. Record what the phone and vehicle display show and whether the requested function opens. Do not manipulate the phone while driving just to produce a more dramatic demonstration video.
If the result is unsuccessful, note the message and conditions. Where appropriate, change one variable at a time using a known suitable cable or another authorised test device. Record the change so a workshop can interpret the result. Multiple changes at once may produce success without revealing which setup the buyer will actually need at handover.
Keep power observations separate from data support
A socket can supply power without providing the requested data function. Charging speed also depends on the actual equipment and test conditions; do not invent a model-wide wattage or fast-charging promise from one short demonstration. If charging performance is important, request the relevant specifications and an agreed check with the intended device.
Do not force connectors, probe sockets or suggest improvised electrical alterations. Visible damage, looseness or inconsistent operation belongs in a qualified technician's assessment. A failed connection does not prove the head unit needs replacement. The screen and function review helps keep local controls and other cabin features in view while the connection concern is investigated.
Document adapters and changed equipment
Where an adapter, hub or aftermarket head unit is used, identify it and confirm whether it is included in the sale. Record the supplied instructions, connection requirements and support provider. A temporary accessory used only for the video should not become an implied part of the vehicle's factory equipment or the final delivery list.
After any agreed installation, repeat the requested connection test and check affected original functions. Ask the provider to investigate any remaining issue. Use the support checklist to price the completed result rather than the accessory alone. A promised future solution remains an open preparation task until its applicable functions have been demonstrated.
Give the receiver a repeatable setup
At delivery, show the recipient which socket, cable and included accessory were tested, along with the phone combination and result. Name any function not verified. Remove authorised test-device data through the supported settings and keep personal account details out of the inspection material. A buyer needs a usable connection description, not the seller's private credentials.
For new stock, include the check in the pre-delivery inspection. For a used car, retain any modification history and repeat the demonstration after repairs. In a batch, test each installed configuration. The practical acceptance statement is a specific function demonstrated with identified equipment, rather than a blanket claim that every USB port supports every phone service.
Manufacturer references
These sources support specific model statements. Candidate condition and transaction details need their own evidence.
State the requirement, the evidence needed and the decision that depends on it.
Build your X5 PLUS brief