FAQ

Yes. DuoDash is distributed through Havoc and installs as a package on a jailbroken iPhone.

See the compatibility page for the authoritative, per-version table. It is kept up to date as testing progresses.

The compatibility page lists each jailbreak we have tested and its current status.

An A15 Bionic device or better — iPhone SE (3rd generation), the iPhone 13 family or anything newer — gives the most comfortable experience. A13-class devices such as the iPhone SE (2nd generation) and the iPhone 11 family are generally fine. Older processors still work, but they have much less thermal headroom and should have DuoDash’s performance options turned on from the start. The compatibility page has the full processor table.

DuoDash can be drawing the CarPlay interface, running an app in each pane, processing navigation and decoding video all at the same time, and that is genuinely demanding. Heat also depends on the processor, how many apps are loaded, the video resolution, whether the phone is charging, the ambient temperature and the other tweaks you have installed. Optimize CPU And Thermal is the setting to reach for first.

Disconnect it from the CarPlay cable or head unit and wait — anywhere from about 30 seconds to a few minutes — so iOS can recover the processes that are stuck. Once it responds again, close the apps that were involved and respring or restart if it still feels unstable. Do not keep reconnecting while iOS is still trying to recover. The install page has the full sequence.

Whatever DuoDash’s Headunit Info screen recommends for your display, or below it. Playing video far above what the head unit can show costs CPU, memory bandwidth, battery and heat without putting anything more on screen.

That is exactly what Deep Sleep is for. Plenty of DuoDash setups use an older, inexpensive iPhone as a dedicated CarPlay device, wired to vehicle power and left out of sight in the dashboard, glove compartment or centre console. Deep Sleep follows the vehicle’s power: it winds the phone down to a low-power state when you switch the vehicle off, and restores the DuoDash environment when power comes back. The features page describes it in full.

With Deep Sleep on, a battery in good health and a sensible configuration, the target is somewhere in the region of 10 days to two weeks. That is a target rather than a guarantee — actual standby time depends on the iPhone model, the battery’s condition, the iOS version, the jailbreak, the tweaks installed, signal and wireless conditions, temperature and how DuoDash is configured. Deep Sleep reduces battery drain; it cannot eliminate it.

No. Deep Sleep deliberately keeps the iPhone powered on, because on many jailbreaks a shutdown or reboot means the jailbreak environment has to be restored by hand before DuoDash will run again. It suspends unnecessary apps, services and background activity instead of powering anything off. The thing that does cost you the jailbreak is a battery going flat, which is the problem Deep Sleep exists to postpone.

No. Its power saving is aggressive by design: it suspends apps and services that a personal phone is expected to keep running, and while the vehicle is parked Wi-Fi, Bluetooth and Location stay off — so a Bluetooth accessory or a personal hotspot will not be available. Deep Sleep is for a phone dedicated to the vehicle.

Not necessarily. Apps bridged into CarPlay often have their own jailbreak tweaks injected into them, and those can conflict with DuoDash, with iOS or with each other. Disable the third-party tweaks on that app, run the unmodified version through DuoDash, and see whether the problem survives. If you report an app-specific crash you may be asked to do this first.

No. Tweak Management is the layer that manages compatible extension modules, and a module is its own package — installed, updated and removed independently of DuoDash. Seeing something listed there does not mean it is installed. The Developer API is not published yet, so there are no third-party modules to install today; the developer guide describes what the architecture will support.

Wired and wireless CarPlay are tracked separately on the compatibility page, because they do not always behave the same way.

See the CarPlay connection table on the compatibility page.

We cannot promise that for every vehicle. The tested-setups table lists configurations that have been confirmed first-hand; if yours is not listed, it is not necessarily unsupported, only unverified.

Some aftermarket units have been tested. Check the tested-setups table before buying.

The install page has a step-by-step guide and a troubleshooting section.

Updates are delivered through Havoc in your package manager. The changelog lists what changed in each release.

Purchases and licensing are handled by Havoc. Contact us by email for anything account-related.

To be confirmed by SenseTechLab against the shipping build. This answer must describe the real behaviour.

To be confirmed by SenseTechLab. Whatever the answer, the privacy policy must state it accurately.

Start on the support page. It links to compatibility, known issues, the FAQ and troubleshooting, and has the Discord and email routes.

Refunds are handled through Havoc. See the terms page, and contact us by email if you need help.