Name the phone task precisely
Bluetooth calling, music streaming, screen mirroring and smartphone projection are not interchangeable descriptions. Tell the supplier whether you need calls, navigation on the vehicle display, voice control or a particular connection method. A successful Bluetooth pairing does not establish Apple CarPlay or Android Auto support.
Record the phone model, operating-system version and cable or wireless method used for the demonstration. Testing the seller’s phone may be useful, but the result should not be extended to every handset. Keep a customer requirement specific enough that both parties know what counts as a pass.
Identify the installed head unit
Ask for the vehicle identity, head-unit information screen and an explanation of any replacement or software change. Where records exist, distinguish original equipment from later accessories. A newer-looking display is not proof that the rest of the system is factory supported or appropriate for the vehicle.
The specification record should describe installed equipment separately from brochure equipment. If the seller relies on a regional advertisement, ask how it applies to the candidate. Do not let the names Changan and Oshan stand in for a verified hardware and software configuration.
When the uncertainty is the socket or cable, use the USB charging and data checklist. Record each port separately, identify the complete connection path and distinguish a successful charging test from the requested data or projection function.
Request a continuous demonstration
A useful video begins with the identifiable vehicle and shows the relevant connection being made, the requested function operating and the system returning to normal vehicle controls. Demonstrate sound and any steering-wheel control functions that matter to the buyer. Do this while parked; a sales video should not require a driver to operate a phone in traffic.
Ask what happens after the car is switched off and restarted normally. A system that worked once with an engineer’s setup may not provide the everyday experience the customer expects. Record interruptions, extra steps and functions that were not tested rather than trimming them out of the evidence.
Treat adapters as separate equipment
An adapter may provide some requested functionality, but its presence changes the support question. Identify its maker, model, connection requirements and supplied instructions. Establish which original functions are retained, which limitations apply and who will help if the accessory stops working.
Avoid approving a software modification solely from a promise that “all languages and apps are unlocked.” Ask for legitimate support and a clear description of the work. The support plan should include any changed hardware and the party responsible for completing or reversing an agreed installation.
Separate local operation from connected services
A menu in English does not prove that online navigation, voice services, account registration or data connectivity will work at destination. Some functions operate locally; others depend on a phone, a subscription, an account or regional services. Ask the supplier to identify those dependencies rather than making an unrestricted compatibility claim.
Use the screen and function checklist for cabin controls beyond phone projection. Retain a line for destination operation that could not be demonstrated. A source-market test can be reported honestly without being presented as evidence of future service availability in another country.
A competing Geely screen needs its own actual setup. The Coolray purchase review demonstrates the customer’s needed function without extending a regional projection claim to every related China-market advert.
Compare the cost of a supported solution
If phone projection is mandatory, compare a candidate that already demonstrates it with one requiring additional work. Include the accessory, installation, setup and verification in the proposed cost. Do not treat a cheap device listing as the completed solution or assume every regional head unit accepts the same adapter.
For a dealer batch, test each installed configuration. One car may have been modified while another remains original. Standardising the customer experience may be useful, but an installation plan should not erase differences in the underlying equipment or its support arrangements.
A phone that charges through a USB port does not prove that the port supports the required data connection. Ask the demonstrator to identify which port and cable were used, and whether any hidden adapter remains installed. That detail gives the customer a repeatable setup and prevents an ordinary charging demonstration being mistaken for evidence of smartphone projection.
Write an acceptance statement the buyer can use
A useful statement names the phone function, tested handset, connection method, installed equipment and result. It also names untested online features and any third-party accessory. Avoid an unqualified “full smartphone support” entry when only calls and music were demonstrated.
Before handover, agree the removal of previous personal data and the transfer of any included legitimate account or subscription rights through the appropriate provider. For a new vehicle, check the actual delivery equipment; for a used one, also retain the modification history. Include your essential phone requirement in the first enquiry so unsuitable candidates can be filtered early.
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