CarPlay behaves differently across vehicles, head units and iOS versions. This page is the single source of truth for what DuoDash supports — please read it before purchasing.
iOS
| iOS versions | Status | Notes |
|---|---|---|
| iOS 14.x | Supported | — |
| iOS 15.x | Supported | — |
| iOS 16.x | Supported | — |
| iOS 17.x | Not tested | Not yet tested. Expected to work, but unverified. |
| iOS 18.x | Not tested | Not yet tested. Expected to work, but unverified. |
| iOS 26.0 | Not tested | Not yet tested. May work, but unverified. |
Jailbreaks
DuoDash needs a jailbroken iPhone, and whether your phone can be jailbroken at all depends on its model and the iOS version it is running.
SenseTechLab does not publish jailbreak instructions. For which devices and iOS versions can be jailbroken, and how to do it, use the iOS Jailbreaking guide at ios.cfw.guide — an independent, well-maintained community reference that covers every current tool.
| Jailbreaks | Status | Notes |
|---|---|---|
| Dopamine | Supported | Tested and verified by SenseTechLab. |
| Taurine | Supported | Tested and verified by SenseTechLab. |
CarPlay connection
Wired CarPlay with a good-quality USB cable is what we recommend. Wireless CarPlay works, but it is not recommended — the connection is less consistent, and a dropout in the middle of a drive is more disruptive than the convenience is worth.
If you are using a wired connection and it behaves unpredictably, try a different cable before anything else. A failing or low-quality cable produces symptoms that look exactly like a software fault.
iPhone performance
DuoDash is not a normal iPhone app, and it is not light. Depending on how you have it set up, it can be doing all of this at the same time:
- Drawing the CarPlay interface
- Bridging apps onto the car display
- Running an app in each pane
- Processing navigation
- Decoding video
- Keeping background apps alive
- Communicating with the head unit
- Running its own services and interface
Navigation and video playing side by side, with other apps still loaded and CarPlay drawing all of it, is the heaviest combination there is. Older devices have substantially less CPU and thermal headroom for that particular workload.
CPU generation makes a real difference. A newer processor has more headroom and gets through the same work more efficiently — though no processor stops an iPhone getting warm under sustained load.
| Processor | Example devices | DuoDash guidance |
|---|---|---|
| A9 | iPhone 6s / 6s Plus | Performance optimisation strongly recommended |
| A10 Fusion | iPhone 7 / 7 Plus | Performance optimisation strongly recommended |
| A11 Bionic | iPhone 8 / 8 Plus / iPhone X | Performance optimisation recommended |
| A12 Bionic | iPhone XS / XS Max / XR | Usable; optimisation may be beneficial |
| A13 Bionic | iPhone SE (2nd generation) / iPhone 11 family | Acceptable |
| A15 Bionic | iPhone SE (3rd generation) / iPhone 13 family | Recommended |
A15-class hardware or better gives the most comfortable experience, and is worth having if you use navigation, both panes, video streaming and background apps at the same time. A13-class devices are generally fine, although thermal and performance limits become more noticeable during sustained heavy use.
Recommended settings for older devices
If an A9, A10 or A11 iPhone runs hot, crashes, lags or feels unstable, the fix is to give DuoDash less to do. Two of the performance switches are worth turning on before you hit any of that, not after.
- Optimize CPU And Thermal — cuts unnecessary processing so DuoDash stays inside a more reasonable CPU and thermal range. On an older phone this is the first thing to enable. It restarts the Home Screen for about 15 seconds, and it only takes effect once CarPlay has been reconnected.
- Close Unloaded Pane Apps — closes an app when you swap it out of a pane instead of leaving it running behind the one you can see. An app left running keeps consuming CPU time, memory, GPU resources, background processing and power for nothing.
That configuration trades some app persistence and multitasking convenience for lower resource use and better thermal behaviour. On an older phone it is a trade worth making, and each switch can be turned back off on its own if it does not suit how you drive.
Video playback and resolution
Video is often the single heaviest thing DuoDash is asked to carry — whether that is YouTube, Twitch, Vimeo, Plex, Jellyfin or anything else streaming or playing locally.
Playing video at a resolution well above what the head unit can actually display gives you little or nothing to look at while costing:
- CPU usage
- GPU usage
- Memory bandwidth
- Power consumption
- Device temperature
DuoDash tells you what to aim for. Headunit Info reports the resolution of the connected display and the video quality it recommends for it — set your video apps to that, or below it. Running well above the recommendation can raise the phone’s temperature and cost you stability, without improving anything you can see on the car display.
Temperature
Expect the iPhone to get warmer when DuoDash is working hard. That is normal, and how warm depends on more than the processor: the workload, how many apps are running, navigation, video decoding and its resolution, whether the phone is charging, the state of the battery, the temperature around it, the other jailbreak tweaks installed, and the CarPlay configuration itself.
If you plan to use DuoDash heavily, choose the strongest processor you can. If a phone you already own gets excessively warm, Optimize CPU And Thermal is the setting that exists for it.
A dedicated iPhone that stays in the vehicle
A common DuoDash setup uses a second, older iPhone that lives in the car — wired to vehicle power and installed in the dashboard, the glove compartment or the centre console. If you are buying a phone for that, its battery deserves as much attention as its processor: between drives the phone has to survive on that battery, and a worn one is what cuts the time short.
DuoDash’s Deep Sleep setting is written for this installation. It winds the phone down when the vehicle’s power goes away and restores the DuoDash environment when it comes back, aiming to keep a parked phone alive for something in the region of 10 days to two weeks. Standby that long assumes a battery in good health, a reliable switched power source, and somewhere that does not get excessively hot — so treat the figure as the target it is rather than a promise, and expect less from an older phone with a tired battery.
How Deep Sleep behaves, and what to check before the phone goes out of reach
What “Supported” means
- The CarPlay ecosystem includes a very large number of vehicle and head-unit configurations.
- “Supported” describes the software. It does not mean DuoDash has been tried in every car.
- Please re-check this page before purchasing — it is updated as new results come in.
Important notice
DuoDash operates in an environment that is significantly different from a standard App Store application. It runs on jailbroken devices and interacts with internal iOS and CarPlay components, so compatibility and stability can be affected by:
- iOS version
- Jailbreak implementation
- Device hardware and CPU generation
- Available memory
- Device temperature
- Battery and charging conditions
- CarPlay head unit and display resolution
- The behaviour of the app being bridged
- Third-party tweaks and other injected libraries
SenseTechLab will continue improving DuoDash’s compatibility and stability, but cannot guarantee compatibility with every possible combination of jailbreak, application, third-party tweak, device and CarPlay head unit. Because DuoDash runs on jailbroken devices and interacts with internal iOS components, system-level instability cannot be eliminated entirely.
Owners of older devices should prioritise CPU and thermal optimisation, reduce unnecessary multitasking, and follow DuoDash’s recommended video resolution and performance settings.
Ready to upgrade your CarPlay experience?
DuoDash is distributed through Havoc. Check that your iPhone, jailbreak and head unit are supported first.