# CarDash V3 — beta 17

Beta 17 fixes the reproduced native JPEG black-screen failure and allows the hosted viewer to select compatible playback on older browsers. The receiving browser's capabilities are separate from the jailbroken host's framework profile.

## Why older iPhone viewers could connect without an image

Safari 16.0 lacks WebCodecs video and iPhone ManagedMediaSource. The earlier hosted viewer rejected it before connecting; the local viewer selected native JPEG instead. Native capture counters could rise even though no browser image was being displayed.

The JPEG path failed when the client imported the decoded IOSurface from iOS's media service. The original service launcher used exec to enter the shared Python executable, replacing the launcher's signing entitlements. Without the IOSurfaceRootUserClient permission, IOSurface access returned kIOReturnNotPermitted and VideoToolbox's output callback reported OSStatus -12780. This was reproduced with both synthetic video and actual CarPlay frames on the development iPhone 8 Plus / iOS 16.6.

The service now runs the installed Python runtime through its public Py_BytesMain entry point inside the signed CarDash service process. That process has the specific IOSurfaceRootUserClient permission. It discovers the installed shared Python version with a bounded, isolated query, validates the library path, and reports a clear startup error if the runtime cannot be loaded. It does not replace or re-sign the shared Python installation. The native AVC/JPEG decoder itself is unchanged.

## Viewer and diagnostics

Both local and hosted viewers select secure WebCodecs first, then supported ManagedMediaSource/MediaSource, then native JPEG canvas. JPEG is a compatibility route capped at 10 image updates per second and adds phone-side decoding; it is not a claim of equivalent smoothness or power use to direct H.264 playback. Existing direct H.264 paths keep their current behavior.

Safari may still block an HTTPS page from accessing local HTTP. The hosted page offers an explicit link to the validated local viewer after a failed connection. This does not change browser security settings or relay media through a server.

Repeated empty JPEG responses cannot extend startup forever: the browser stops after 12 seconds without a first image. Native errors include the decoder stage and OSStatus after a bounded recovery grace, and successful recovery clears the current error. A stationary image that already displayed remains valid. Exported diagnostics retain decoder stages, image counts, viewer context and stop reasons without session credentials. The phone app now labels captured native frames accurately rather than treating them as proof of browser playback.

Beta 16's ordered touch input, prompt releases, swipes and renewable intentional holds are retained. Authentication, native framework profiles, video budgets, display geometry, audio routing and installer recovery are unchanged.

## Verification and limits

On the iPhone 8 Plus / iOS 16.6, the same short live CarPlay capture produced zero images under the previous Python process and 51/51 decoded frames, 20 JPEGs and zero decode/JPEG failures under the entitled embedded process. The resulting JPEG matched an independent FFmpeg decode (mean RGB absolute error 1.146/255). Synthetic video and Python module/subprocess checks also passed. These are isolated component tests; the existing CarPlay session was not restarted and the installed package was not replaced for the probes.

332 Python tests and 134 JavaScript tests pass. Automated checks cover service-process identity, runtime discovery failures/timeouts, native image recovery, bounded error responses, browser playback selection, stationary frames, reconnect behavior and the existing input/audio regressions. Package audits verify architecture, signatures, the iOS 15.0 deployment floor and the service entitlement.

The tester's iPhone 14 Pro Max / iOS 16.0 has not been directly retested with this package. Its reported failure matches the investigated image-import path, but final device acceptance still requires their installation. This release adds no blanket guarantee for every iOS version, jailbreak or unknown native framework profile. Shared rootless Python 3.9 or later remains required.

## Tester steps

1. Refresh Sources in Sileo and install CarDash V3 `3.0.0~beta.17`, then reopen CarDash.
2. Reload the receiving browser so it loads the updated viewer. Use https://fluidlabs.app/viewer or the jailbroken phone's local HTTP address. For viewing on that same phone, http://127.0.0.1:8890/ is available; another device must use the phone's Wi-Fi/hotspot address.
3. Connect and start CarPlay. If HTTPS-to-local HTTP is blocked, use the offered local-viewer link. Keep both devices on a network that allows them to reach each other.
4. Check actual displayed pixels, quick Home taps, swipes, an intentional hold and Device output audio. If playback fails, export diagnostics and include the receiving device/browser and the message shown.
