Troubleshooting
Solutions for common issues with oxide-carplay
Solutions for common issues with oxide-carplay.
Startup and Dependency Issues
Audio Issues
Playback and URL Issues
UI and Map Issues
Sync Issues
Jailbreak Issues
Performance Tuning
If you need lower client overhead, review:
Config.CarPlay.PositionUpdateInterval = 150
Config.CarPlay.ProximityScanInterval = 2000
Config.CarPlay.MapUpdateInterval = 500Higher intervals reduce update frequency and can lower CPU use at the cost of responsiveness.
You can also reduce:
Config.CarPlay.AudioRange = 12.0Lower audio range means fewer nearby playback instances need to stay active.
Debug Mode
Enable debug output:
Config.Debug = trueCurrent debug prefix:
[oxide-carplay]Use this when validating:
- startup flow
- metadata lookups
- playlist persistence
- playback sync
- jailbreak behavior
Getting Help
If issues persist:
Enable Config.Debug.
Collect server console output during the issue.
Check client F8 output for NUI or playback errors.
Verify xsound is working.
Verify the required o-link modules are functioning for your server.
Test with a reduced resource set to isolate conflicts.
Support
Need more help?
- Discord: https://discord.gg/dZ6q8FyGhm
- Website: https://www.oxidestudios.dev/
- o-link (required abstraction layer): https://github.com/WHEREISDAN/o-link