BYD Song Plus Phone Connection, CarPlay and Android Auto

State the specific function you need

Define whether the requirement is hands-free calls, music playback, map projection, wired connection, wireless connection or a remote vehicle-control app. The same phrase about phone compatibility can conceal different expectations. Record phone platform, intended use and essential functions before comparing listings. A Bluetooth connection does not prove full projection, while a seller app controlling locks does not prove in-car navigation integration. The Song Plus software overview retains these separate categories. Buyers who do not need a particular convenience function should say so, rather than treating a long sales feature list as equally important.

Match documentation to market and software

Request original market, VIN, relevant equipment sheet and visible software-version information. Use the applicable owner manual and supported service instructions, not a translated feature list from another regional model. Keep a record of what the specification actually states and what remains unconfirmed. The Song Plus and export-name guide helps prevent model-family similarities from becoming assumed equipment equivalence. Do not infer projection support from a rotating display, a familiar USB socket or a menu icon. Different hardware or software states may require a different assessment, so preserve the version basis used for each candidate. BYD Mexico advertises Apple CarPlay and Android Auto for its Song Plus DM-i. That is a Mexico-market equipment reference, not evidence that every China-market used candidate has those functions.

Demonstrate the buyer phone and ordinary accessories

Where the function is supported, use the intended phone and an appropriate known-good cable if required. Show the normal connection process, relevant display and actual function, then disconnect and reconnect through the supported procedure. Record which socket and connection mode were used. A seller demonstration with another phone is helpful screening evidence but may not answer the buyer requirement. Do not ask for unofficial installation files, hidden-menu changes or security bypasses to force a result. If ordinary supported testing fails, request a qualified assessment before concluding that the vehicle needs hardware replacement or an undocumented software patch.

Keep connectivity limits separate from display faults

Distinguish a phone compatibility or regional-service limitation from an actual failure of the screen, socket, microphone or other fitted component. Test the ordinary local functions that the candidate is documented to support, preserving warnings and repeatable observations. Avoid treating a failed map projection as proof that the entire infotainment system is defective. The VIN-based repair-support guide is relevant when a component fault is diagnosed. Do not replace the unit simply because another market advertises more features; confirm fitment, supported procedures and destination implications before assigning any proposed remedy a cost.

Ask for a supported update boundary

If the seller says an update will add the required function, ask for the applicable official service basis, candidate eligibility and a completed demonstration before payment. A general statement that updates exist does not guarantee this feature for this car. Preserve the original version and warning state before any supported work. Do not use another owner success story as evidence of safe compatibility or warranty acceptance. The Song Plus overseas-support checks identify who can address a software or equipment dispute after import. Treat promised future capability as unresolved until the agreed result is demonstrated legitimately.

Write a function-level handover record

The approval should name the phone platform, connection mode, software basis, functions tested and known limits. Keep remote app transfer in the account handover file rather than combining it with projection. Remove personal phone pairings through the applicable process after demonstration and record essential supplied accessories. Repeat relevant checks after an update or candidate substitution. If the buyer accepts a function as unavailable, make that exception visible in the quotation. The useful outcome is a supported daily phone routine, not an inflated claim that the screen supports every smartphone or regional online service.

Example: the advertised function belongs to another market

A listing copies a feature from an export brochure, but the allocated China-market Song Plus has no supported demonstration of it. Ask the supplier to correct the equipment description and establish the actual vehicle capability. The buyer can compare a properly documented alternative or accept the limitation if it is not essential. Do not budget an assumed retrofit as though it guarantees an equivalent factory result. Keep the acceptance decision tied to the demonstrated candidate, so a clean touchscreen and working Bluetooth connection do not silently substitute for the specific navigation projection originally requested.

Buyer checklist

• Exact phone function defined
• Market and software evidence retained
• Intended phone tested normally
• Component faults separated from feature limits
• Handover includes known exceptions

Buyer questions