GAC GS4 CarPlay & Android Auto: Phone Connection Checks

Write the phone task in plain language

Specify the phone platform and whether the customer needs hands-free calls, music, map projection or another application. Do not bundle them into a broad connectivity claim. A USB charging symbol can establish power to the phone without demonstrating projection, and a Bluetooth pairing can work for audio while the required map display remains untested.

The connected-function overview keeps those requirements separate from language and online services. Give the seller a short list of essential tasks and ask for each result. This makes it easier to compare candidates whose trim names or screens look similar without assuming their hardware and supported functions are the same.

Identify the installed equipment and market

Request visible head-unit information and ask whether the setup is original, replaced or modified. Keep the vehicle reference and production context with the demonstration. Regional marketing material can show supported functions for a particular release, but it should not become an equipment certificate for every GS4 carrying a familiar English name.

The naming and year review helps establish that context. If a seller proposes an adapter or another accessory, identify it separately, including its provider and applicable support. Do not describe an accessory-dependent result as built-in factory equipment without clarification. A photograph of a projection menu is a starting point, not a complete operating test.

The modified-vehicle decision identifies the actual added system and receiving method instead of treating a similar screen as original equipment.

Demonstrate connection and a routine reconnect

Use the intended phone type and the proposed supported method while the vehicle is safely parked. Show how the connection is made, open the required task and confirm relevant audio or display operation. Include a routine disconnect and reconnect. Record the phone and software context so the receiving customer knows which combination was actually tested.

If the demonstration uses the seller’s phone, identify what still needs checking on the buyer’s device. Avoid extending one successful result to every handset or future revision. Preserve failed attempts or warnings where they affect the requirement. Ask the responsible provider to assess an unresolved issue instead of naming a hardware fault from a short remote video.

Check language and navigation dependencies separately

Ask for the menus used in ordinary control and any important warning interface, not only an English opening screen. A phone application displayed in the buyer’s language does not establish that the vehicle’s other menus share it. Keep the language requirement in the accepted specification with any unconfirmed areas visible.

For navigation or other online content, identify whether the task relies on the phone’s service or a regional vehicle account. Destination coverage and access need their own evidence. The account handover checklist addresses the receiving user’s legitimate arrangement where one is needed. A working phone projection test should not become a promise of every connected vehicle service abroad.

Recheck changes made during preparation

If the seller resets the head unit, changes software or adds equipment before release, repeat the customer’s essential tests on the delivered setup. Record the change and the provider’s completion information. A demonstration performed before preparation can be incomplete evidence for the final arrangement, especially where an added device supplies part of the requested function.

For new vehicles, include this task in the agreed pre-delivery work. For used vehicles, retain disclosed equipment history as well as current findings. The equipment record should identify the final setup and supplied cables or accessories. An update label or a cleaner screen should not replace the buyer’s concrete requirement and its demonstrated result.

Record what the delivered vehicle supports

Summarise the verified tasks, method, necessary accessories and observed context in the handover file. Keep unresolved regional or device questions explicit. The receiving dealer should be able to explain whether the buyer needs a cable, a supported accessory or further activation without depending on a vague claim that every phone works.

For a batch, retain individual results where units differ. A common model name does not establish identical head units or software, and one demonstration should not certify unexamined vehicles. If an essential function cannot be established, compare another candidate or revise the accepted requirement before purchase. The useful answer describes the actual supplied arrangement and its limits.