+- OrBit Forums (https://forums.spaycetech.com)
+-- Forum: General (https://forums.spaycetech.com/forumdisplay.php?fid=1)
+--- Forum: OrBit Q&A - Ask your questions here! (https://forums.spaycetech.com/forumdisplay.php?fid=24)
+--- Thread: Vida and/or Orbit Progression for Carplay (/showthread.php?tid=1404)
Vida and/or Orbit Progression for Carplay - titanbrave84 - 07-31-2026
Hey,
I have a 2016 Volvo XC90 T8 PHEV Inscription with single port USB. I want to activate CarPlay. I’m aware that the dual port is not necessary. So what’s the process. I have VOE cable and Windows device, do I go through the rigmarole of updating all my software via VIDA first and use wireshark to grab my pin, and then Orbit or should I just bypass VIDA altogether and do Orbit with Pin Retrieval, and simply activate CarPlay that way?
I don’t know what the latest software is on my vehicle, but I’ve heard that some of the software updates can actually make the car operate more efficiently in regards to the PHEV element.
TLDR:
VIDA > Wireshark for Pin > Software Updates > Orbit > Activate CarPlay
Bypass Updates > Orbit with Pin Retrieval > Activate Carplay
RE: Vida and/or Orbit Progression for Carplay - jos - 08-01-2026
Hi, you need to capture while a software update 2.0 is running. My log was around 400mb and covered bith pins for me CEM and VGM (Android) i have AAOS car. When on latest enable carplay with Orbit.
RE: Vida and/or Orbit Progression for Carplay - x119 - 08-01-2026
Throw money at the problem > OrBit PIN Service + OrBit.
Throw time & slightly less money at the problem > VIDA + OrBit.
You don't need to be on the latest and greatest software a vehicle of your vintage (no shade, mines 2015
) probably won't have had many meaningful updates for a while...
RE: Vida and/or Orbit Progression for Carplay - jos - 08-02-2026
Sorry but with AAOS you want to get rid of the newest bugs :-)
RE: Vida and/or Orbit Progression for Carplay - x119 - 08-02-2026
(08-02-2026, 07:45 AM)jos Wrote: Sorry but with AAOS you want to get rid of the newest bugs :-)
2016 isn't iCup/AAOS, so not applicable.