ARM and Intel
The RC1 APK packages native libraries for armeabi-v7a, arm64-v8a, x86 and x86_64. Architecture coverage does not validate every head unit or its proprietary services.
CHAPIN SOFTWARE / PIC
Compatibility
Check the FYT/SYU platform, Android 8.1/API 27+ requirement and the dependencies of each PIC function.
REQUIRED PLATFORM
Compatibility starts with the hardware.
This release is intended for FYT/SYU automotive head units running Android 8.1 Oreo or later, API 27+. An Android version number alone does not establish compatibility.
Porsche 987 and 997
PIC provides profiles for the supported 987 Boxster/Cayman and 997 Carrera, Carrera S and Turbo variants. Profiles supply calculation assumptions; the physical installation and vehicle interface remain separate requirements.
FYT/SYU is the primary scope
Radio, Phone, Bluetooth media, Sound/DSP and vehicle controls require the matching firmware interfaces. Discovery identifies exposed capabilities; it does not add hardware or guarantee control.
Additional Bluetooth integration
HCT/Microntek Bluetooth integration is implemented but has received limited testing. Treat it as experimental on the exact unit. It does not establish full PIC hardware compatibility for all HCT/Microntek devices.
FUNCTION BY FUNCTION
What each function needs.
Radio
Compatible tuner and provider; reception and RDS determine available station data.
Local / USB media
Android-accessible files and storage permission; reconnect removable storage when required.
Bluetooth / Phone
Native pairing, media/calling support and the relevant phone sharing permissions.
Navigation / Compass / Trip
Location access and a usable GPS/heading source. Maps, search and routing have separate dependencies.
Sound / DSP
A supported audio backend or native provider; controls vary by hardware.
OBD
Optional compatible adapter, supported Bluetooth/Wi-Fi path, ignition and ECU data.
CarPlay / Android Auto
A compatible installed projection receiver/provider; PIC supplies launch access.
DISCOVERY
Check what the unit exposes.
Complete the first-run discovery, then review Settings > Head unit & vehicle and Application integrations. Rescan after relevant provider changes. A detected package can exist without usable integrated controls.
Follow first-run setup