Skip to main content

FAQ - App Runtime Environment and Platform Resources

Checking the Runtime Platform​

To identify the device or environment in which an app is running, read the device identification value.

Use android.os.Build.DEVICE to check the value corresponding to ro.product.device.

This value is provided only on a real vehicle, so it cannot be used to distinguish platforms in an emulator.

The values returned for each platform are as follows:

  • Connect-S: CONNECT_S
  • Connect-L: CONNECT_L
  • Connect-W: CONNECT_W

Checking the Region Code​

Apps must use product.sw.target_region to identify the region and apply the corresponding regional UX policy. The values by region are as follows.

  • Korea region: KOR
  • Europe region: EUR
  • North America region: USA, CAN (United States, Canada)

The method for checking whether navigation is installed in a vehicle is currently not publicly open. For details, please contact partnership@pleos.ai.

Checking Cluster Speed​

The speed shown on the Pleos Connect cluster and the speed displayed in an app may differ when they come from different data sources. For example, a speed calculated from GPS in the app may differ from the vehicle-signal-based speed used by the cluster.

The Pleos Connect cluster displays vehicle speed using Google's PERF_VEHICLE_SPEED property. To use the same speed as the cluster, read PERF_VEHICLE_SPEED with CarPropertyManager.

To use the same vehicle speed as the cluster, query the PERF_VEHICLE_SPEED property through the AAOS CarPropertyManager. Declare the required permission, obtain CarPropertyManager, and use the APIs for reading the current value or subscribing to change events.

For API usage and version-specific details, refer to Google's official CarPropertyManager documentation and the PERF_VEHICLE_SPEED property documentation.

Checking Battery Information​

To check the battery state of charge in a vehicle, refer to the Vehicle SDK getEvBatteryStateOfCharge API documentation.

Media Codec Support Information​

Media codec support in a real vehicle may vary by platform. For details, refer to the platform-specific information in this section. Media codec support in the Pleos Connect Emulator may differ from that in a real vehicle. Do not apply emulator test results directly to a real-vehicle environment.

Media Codec Support Information by Platform​

Connect-S/L Codec Information​

Media TypeSupported Codec
AudioFLAC, AC3+, ALAC, APE, PCM, TTA, AIFF, WMA, OGG, DSD, DFF/DSF, DTS, WAV, MP2, MP3, BSAC, ADPCM, HE-AAC, HE-AAC+, AAC, EAC3, EAC3+JOC, OPUS, AMR, etc.
VideoMPEG-1, MPEG-2, VC-1, WMV, H.263, MP42, MP43, MPEG4 Part2, Xvid, VP6, VP7, VP8, VP9, H.264, HEVC(H.265) – main 10 profile (including others), x265, AV1, etc.

Connect-W Codec Information​

Media TypeSupported Codec
AudioPCM, AAC, MPEG, AMR, WMA, Opus, Vorbis, FLAC, ALAC, APE, Dolby, DTS, ADPCM, AIFF, TTA, BSAC
VideoMPEG-1, MPEG-2, MPEG-4 Part 2, H.263, H.264 (AVC), H.265 (HEVC), AV1, VP8, VP9

Pleos Connect Emulator Codec Information​

Media TypeSupported Codec
Audio DecoderAMR-NB: c2.android.amrnb.decoder
AMR-WB: c2.android.amrwb.decoder
FLAC: c2.android.flac.decoder
G.711 A-law: c2.android.g711.alaw.decoder
G.711 μ-law: c2.android.g711.mlaw.decoder
AAC: c2.android.aac.decoder
MP3: c2.android.mp3.decoder
Opus: c2.android.opus.decoder
PCM Raw: c2.android.raw.decoder
Vorbis: c2.android.vorbis.decoder
Video DecoderH.263: c2.android.h263.decoder
AV1: c2.android.av1.decoder
AVC/H.264: c2.android.avc.decoder
HEVC/H.265: c2.android.hevc.decoder
MPEG-4 Part 2: c2.android.mpeg4.decoder
VP8: c2.android.vp8.decoder
VP9: c2.android.vp9.decoder
Audio EncoderAMR-NB: c2.android.amrnb.encoder
AMR-WB: c2.android.amrwb.encoder
FLAC: c2.android.flac.encoder
AAC: c2.android.aac.encoder
Opus: c2.android.opus.encoder
Video EncoderH.263: c2.android.h263.encoder
AV1: c2.android.av1.encoder
AVC/H.264: c2.android.avc.encoder
HEVC/H.265: c2.android.hevc.encoder
MPEG-4 Part 2: c2.android.mpeg4.encoder
VP8: c2.android.vp8.encoder
VP9: c2.android.vp9.encoder