Only check driving behaviour after a successful installation

If installation fails, the matching XPENG handbooks say not to use the vehicle. Follow the displayed permitted retry and seek support if it fails again; do not take a test drive or restart a still-installing system. Learn changed controls while parked after successful completion and with no unresolved safety warning. The release announcement is not permission to install a package assigned to another car or to use unsupported assistance.

Match the exact model handbook and offered-release instructions.

What XPENG highlighted in XOS 5.8.7

AreaPublished focus
ACC and LCCRefinements intended to make assistance calmer and more predictable
Steering and decelerationReduced unnecessary deceleration and small steering corrections
SystemImproved stability and faster OTA installation
Phone projectionStronger Apple CarPlay and Android Auto connectivity
InterfaceLanguage optimisation

Availability and behaviour can vary by model, hardware, country and approval status. The vehicle’s release notes and matching handbook remain authoritative.

Before installation

  1. Confirm that the vehicle itself offers 5.8.7 for the correct model and market.
  2. Read the on-screen release notes and photograph the current complete version.
  3. Park securely with the battery and connectivity conditions shown by the car.
  4. Do not start before an essential journey.

Post-update checks while parked

  1. Confirm that the software screen reports the new build.
  2. Test phone pairing, CarPlay or Android Auto and navigation audio.
  3. Check charging limits and schedules.
  4. Review camera views and driver-assistance settings.

Complete a careful road check

On a quiet, familiar road, test only one assistance function at a time. Confirm its displayed state and cancellation method. Driver assistance remains supportive technology: stay attentive and intervene immediately if behaviour differs from expectation.

If installation or behaviour is abnormal

Save the error, time, battery percentage, old and new versions, road conditions and exact warning. Do not interrupt power or force undocumented restarts. Contact XPENG if the update loops, the car cannot become ready or a safety warning remains.

PRACTICAL NEXT STEP · MyXPENG

Test the behaviour. Keep the evidence.

Applies to: XOS 5.8.7 exact offered model/hardware/market. Release features compared with dated XPENG announcement; failed-installation stop from exact-model handbook.

Evidence checked · Review due

First useful check

Park and record installed/offered build, read the exact release and meet the vehicle’s own preparation conditions before installing.

Read the result

Successful installation reports new version with normal parked controls and no unresolved warning. Feature checks follow actual supported equipment; no-offer remains separate from failed install.

Stop or change approach: Do not use the vehicle after installation failure, drive to test a failed update, interrupt power or install unofficial packages. Never intentionally induce unsafe assistance behaviour.

Prepare a useful record

Exact model/generation/XOS, offered/before/after build, failure stage/message, battery/network/time and changed parked setting.

Keep registration, VIN, account numbers and personal addresses out of this note. Nothing typed here is sent to us or saved automatically. Copy it before leaving the page.

Evidence and answer standard

Full body and published feature list reviewed; failed-installation/no-test-drive boundary added, original owner feature summaries and images preserved.. The date records an evidence review, not a physical test of your car. A forum report can identify a question; it cannot establish a universal repair.

How MyXPENG checks owner guidance →

Did this guide move you forward?

Count a helpful answer or flag a gap. This is editorial feedback, not a repair diagnosis or a request for a personal reply.

What this sends

Only this guide ID, revision, selected category and vote are counted. No notes, name, search text or IP address are stored in the feedback database. Standard hosting logs still apply. Counts are votes, not unique owners or verified faults.