New features

The following features and improvements have been added to the QNX CAR platform for this release. All documentation references are to titles under QNX CAR Platform for Infotainment in your IDE help (Help > Help Contents).

Runtime for APK is no longer included with this product.

General

• If you switch themes frequently, memory usage will increase significantly. Switching themes 20 times consumes on the order of 50 MB of memory. After five to ten minutes the memory will return. This is unlikely to occur during normal usage. (Ref# 251103, J400879)
• In the Personalization screen, names that include the backslash character ("\") and other special characters aren't displayed correctly in the status bar. (Ref# 267213, J400950)
• On the Settings screen, if you hold the Personalization button for longer than two seconds, the system won't open the Personalization screen. (Ref# 267218, J400951)
• Setting the compiler/linker to use PIE causes the following compile error: crt1S.o not found. PIE isn't supported. (Ref# 258681, J400920)
• If you connect a physical keyboard to the platform, apps are resized as if to make room for the software keyboard, yet the software keyboard doesn't appear on the screen. (Ref# J580770)
• To ensure that the databases are backed up to save settings between sessions, always shut down the system either by running the reboot script at the terminal or by using the Shutdown application on the display. If you run the shutdown script at the terminal, the database won't be backed up and the settings won't be saved. (Ref# 258441)

Automatic speech recognition

• If Pandora is not installed, or newly installed and the system has not been re-booted, speaking the command "Go to Pandora" launches shutdown. (Ref# 601099)

  Workaround: Re-boot system after installing Pandora.

• If you launch the Settings app via the HMI, and then give the voice command "Close", the ASR will repeatedly ask you which application you'd like to close, even after you say "Settings". (Ref# J570665)
• If you give the voice command "play previous track" while in the middle of a track, the current track is restarted—the previous track is never played. (Ref# J570953)
• If the Nuance archive hasn't been installed on the platform, tapping the Push-to-Talk tab has no effect even though the button appears to be enabled. (Ref# J575135)

  Workaround: Install the Nuance archive before using ASR.

• The NMSP (Nuance Mobile Speech Processing) service cannot be accessed behind a proxy server, so attempts to use voice recognition at a location behind a proxy server may fail. Connection to the remote service is required to ensure that a proper license was obtained to use the service. Note that some voice processing (e.g., voice-activated dialing) may work behind a proxy server. (Ref# J537113)

  Workaround: If you have a license agreement with Nuance, access our source code integration of Nuance into io-asr and remove the off-board dependency.

Bluetooth

• If you pair with a phone that has no songs in memory, then launch the multimedia player and select Bluetooth Phone as a source, the player never indicates that there's no media available. (Ref# J571712)
• During a search in the BLUETOOTH CONNECTIVITY screen ( ADD NEW DEVICE > SEARCH ), if you tap the Apps Section icon in the taskbar, then select the Settings app and try to perform another search from the BLUETOOTH CONNECTIVITY screen, the search spinner doesn't appear. (Ref# J576625)
• If you open a long email message on a MAP-enabled phone, then try to open another email while the first one is still loading, the second message never appears in the HMI. (Ref# J575872)
• When playing songs on iPhones and on BlackBerry Z10s, the QNX CAR platform's Previous and Next UI buttons remain enabled even when reaching the first or last song in the phone's list. (Ref# J563470)
• A2DP audio quality isn't as good as required. (Ref# J524005)
• AVRCP: track progress isn't updated while streaming from Samsung S2, S3 or S4, or iPhone4S. (Ref# J441337)
• Unable to make AVRCP connection to Samsung S2 and BlackBerry Bold 9900. (Ref# J424540)

  Workaround: A2DP connections are successful.

• If you connect a phone, disconnect using the phone's interface, and then reconnect, only the HFP service will reconnect (MAP and PBAP won't be connected). (Ref# 242743, J400828, J420600)

  Workaround: Always disconnect the phone using the HMI.

• If you change the setting for CAR BLUETOOTH NAME, the new name won't show on the connected device. (Ref# 256756, J400906)

  Workaround: Reboot the QNX CAR system.

• Emails from a paired BlackBerry Bold 9700 phone might not be displayed correctly if they contain embedded HTML or images. (Ref# 260465, J400934)
• Pictures for contacts in connected phones might not appear in the Address book. (Ref# 211851, J240842)
• SPP can't be disconnected from the HMI. (Ref# 236550, J241120)

  Workaround: Disconnect using the phone.

• If you start synchronizing the contacts from a connected phone, then disconnect it before the synchronization completes, then connect another phone, you could see partial contact information from both phones. (Ref# 240581, J241171)

Browser

• No certification dialogs are available in the browser application. If you go to a website that requires verification of an SSL certificate, the browser will hang. (Ref# 259702, J400931)

Documentation

• The Bluetooth Architectural Overview and Configuration Guide incorrectly states that version 2.2 for the HFP Bluetooth profile is supported. For CAR 2.1, HFP version 1.4 is supported.
• The documentation in the Eclipse Help may be slightly out of date. For the most current version, see http://www.qnx.com/developers/docs/.
• In the PPS Objects Reference, the Bluetooth handsfree control and status objects are shown to be under the /pps/services/bluetooth/ directory like all the other profiles, but the software itself currently has those objects under the /pps/services/handsfree/ directory. In the next release of the software, the objects will be under /pps/services/bluetooth/. (Ref# J534756)
• In the QNX Momentics IDE help, the "QPlayer API" section in the Qt Development Environment guide has these inaccuracies:
  • The QPlayer class declaration shows two versions of the getMetadata() method but only the first version is actually defined by the class.
  • In the same class declaration, the getTrackSessionItems() function as shown takes four arguments but the real function takes one argument, which is a pointer to a TrackSessionItemsCommand object.
  • The same class declaration is missing this public slot: void stop(). However, the slot is documented under "Public slots in QPlayer".
  • The const keyword is missing from the arguments of these QPlayer functions: jump(), setPlaybackRate(), setRepeatMode(), and setShuffleMode(). The keyword is missing in the class declaration and the individual function pages.
  • The QPlayer::playerReady signal isn't documented.
  • In the next() and previous() QPlayer slot descriptions, the behavior specified for the REPEAT_ONE setting is wrong. For both these slots, the track selected for playback with the REPEAT_ONE mode enabled is the same as the one selected with the REPEAT_OFF mode enabled.

  Workaround: See the online documentation for up-to-date information on these QPlayer API components.

• Personalization demo app: The QNX CAR User's Guide doesn't state that using shutdown to shut down the QNX CAR platform doesn't save changes (such as the addition of new profile) to the database. (Ref# J400919)

  Workaround: To save changes to the database, run the reboot script from the host terminal.

Freescale i.MX6Q SABRE Lite

• The rearview camera may take up to three seconds from boot before it becomes visible. (Ref# J561180)
• The Scout application doesn't complete launching, but stays stuck at "Logging in..." (Ref# J400970)
• On the i.MX6Q board, if you run the HTML Gears demo, and then play a video, some of the Gears graphics might show through the multimedia app screen. (Ref# 267327, J400953)
• In some instances, rebooting the QNX CAR system after a crash on Freescale i.MX6Q SABRE Lite version 1.2 boards results in a black screen and non-functional graphics applications. (Ref# J400963)

  Workaround: Reboot again, using the shutdown command to reset the board. Sometimes multiple reboots are required.

• Calibration screen appears with black rather than white background. (Ref# 259302, J400926)
• Time from boot to display of splash screen is greater than desired. (Ref# J465328)

Geolocation

• In some cases, www.hostip.info gives incorrect results for an IP address. (Ref# J573184)

  Workaround: If the geolocation service happens to provide the wrong city, you can manually update the data:

  1. Go to the www.hostip.info site.
  2. Choose the Make a correction item and follow the instructions on your screen.
• Weather network app: automatic geolocation doesn't update geolocation. (Ref# J438165)

HTML5

• Pop-up windows created by a call to window.open() aren't correctly sized or positioned. (Ref# 580760)
• Eventseekr: If an event description is long, scrolling scrolls the entire app, not just the text area as required. (Ref# J532235)
• Time from boot to launch of Home screen is greater than desired. (Ref# 477824)
• Browser address bar doesn't return back to bottom position when the keyboard is minimized. (Ref# J242173)
• The on-screen keyboard may cover the input field. (Ref# J240984)

Multimedia

• HMI may freeze when DLNA is enabled. (Ref# J616225)

  This problem isn't present during normal in-car use where Wi-Fi is used to share DLNA between a phone and QNX CAR. It has been observed only on desktop systems using Ethernet LAN for connectivity to DLNA servers on a PC, and when the conditions that cause it have been present between six and 24 hours. It may occur when both:

  • The QNX CAR Wi-Fi service is enabled.
  • The QNX CAR system is not connected to a Wi-Fi access point.

  Workarounds: There are several possible workarounds to avoid this problem:

  • Disable Wi-Fi in /var/etc/services-enabled.
  • Use the SLM configuration to disable the QNX CAR Wi-Fi.
  • Connect the QNX CAR system to a wireless access point.
  • Enable a Wi-Fi hotspot on the QNX CAR system.
• mm-player: if the first file selected for a track session is not a playable file, mm-player doesn't create a track session as expected. (Ref# 584570)

  Workaround: Always ensure that the first file selected for a track session is a playable file. Once the track session is created, mm-player just skips over files it can't play.

• When playing media from a USB stick with a larger number of files, if you reboot the target while a track is playing, on resumption of playback the system doesn't display the progress bar and the track metadata. (Ref# J614980)
• If you attempt to play a file that isn't a valid media file, no tracksession is created. (Ref# J584570)
• If you run the Media Player application from MirrorLink Drive link and then switch to the HMI Jukebox, both audio sources are heard at the same time. (Ref# J569985)
• Pandora songs may unexpectedly resume playing when paused or may cause video to pause. (Ref# J553186, J468097)
• Browsing on DLNA device connected to through a QNX CAR Wi-Fi hotspot may fail to show the media files that are on the device. (Ref# 492896)

Navigation

• Navigation settings menus may be slow to render. (Ref# J613283)
• This release of the QNX CAR platform doesn't include the TCS and Telenav navigation engines.
• If you zoom out quickly during a long navigation, you can't zoom back in to street view. (Ref# J462277)
• EB navigation's memory consumption might increase significantly during long navigation sessions. (Ref# 237301, J241136)

Qt

• When a Samsung S3 is connected via USB hub, DriveLink closes during playback. (Ref# J610874)

  Workaround: Disconnect and reconnect the USB device.

• When a Samsung S3 is connected via USB, tapping the DriveLink icon from the Applications section causes the splash screen to appear momentarily. (Ref# J608577)
• It's currently not possible to connect to a WPA2 Enterprise Wi-Fi network that requires both a username and password. These networks don't appear in the HMI settings. WPA PSK networks are supported, however. (Ref# J583145)
• We provide the core Qt libraries in binary form for use in QNX CAR reference images and in the Qt packages for Linux and Windows application development. If you want to use the official Qt sources and build the core Qt libraries yourself, you'll need to apply a small patch to the official Qt sources. (Ref# J583427)

  The patch is available here:

  https://codereview.qt-project.org/#change,76213

• When building the Qt HMI (or any Qt app), you must manually set some compiler and linker flags for qmake. The ways to do this, from most to least preferred, are:
  1. In a QNX Neutrino terminal, enter a qmake command line with additional arguments specifying the necessary compiler settings and library paths (which are highlighted in this example):

     qmake qnxcar2.pro -r -spec qnx-armv7le-qcc INSTALL_PREFIX=$WORKSPACE/tmp QMAKE_CXXFLAGS+="-Wc,-std=gnu++0x -Wc,-std=gnu1x" QMAKE_LFLAGS+="-Wl,-rpath-link,QNX_QDF_PATH/lib"

     The name of the build utility and the value of QNX_QDF_PATH is platform-dependent. For Windows hosts, the utility is called qmake.exe and the QDF path is C:/QtQNX/Qt520. For Linux, the utility is called qmake and the QDF path is /base/qt5-5.2.

  2. Manually edit the project's .pro file by adding these lines:

     QMAKE_CXXFLAGS += -Wc,-std=gnu++0x -Wc,-std=gnu1x

     QMAKE_LFLAGS += -Wl,-rpath-link,QNX_QDF_PATH/lib

     After setting the qmake flags this way, you can build the project from either Qt Creator or the command line.

  3. In Qt Creator, do the following:
     1. Click the Projects icon on the left, select the project entry for the Qt app that you want to build, then select the Build & Run tab.
     2. Under Build Steps, click the Details button on the right of the first field to show the configuration fields for the qmake command.
     3. In Additional arguments, enter:

        QMAKE_CXXFLAGS+="-Wc,-std=gnu++0x -Wc,-std=gnu1x" QMAKE_LFLAGS+="-Wl,-rpath-link,QNX_QDF_PATH/lib"

     4. Click Apply in the bottom right corner to apply the new command settings.
  4. Open the mkspecs configuration file for qcc, found at QNX_QDF_PATH/mkspecs/common/qcc-base-qnx.conf, and add the directory with the installed Qt libraries to the libraries path by changing:

     QMAKE_LFLAGS += -Wl,-rpath-link,$${QNX_DIR}/$${QNX_CPUDIR}/lib -Wl,-rpath-link,$${QNX_DIR}/$${QNX_CPUDIR}/usr/lib

     to:

     QMAKE_LFLAGS += -Wl,-rpath-link,$${QNX_DIR}/$${QNX_CPUDIR}/lib -Wl,-rpath-link,$${QNX_DIR}/$${QNX_CPUDIR}/usr/lib -Wl,-rpath-link,$$[QT_INSTALL_LIBS]

     After setting the qmake flags this way, you can build the project from either Qt Creator or the command line.

• Binaries created using Qt Creator on Windows contain C:\ in the rpath value (e.g., as shown when using the ntoarmv7-objdump -x command). (Ref# J579699)

  Workaround: Make sure you have libraries in the C:\base\qt5-5.2\lib\ folder.

• The Qt HMI has these issues:
  • The carousel might display the next track to play (looping content) even though the "Continous Play" option has not been selected. (Ref# J569316)
  • The on-screen keyboard may cover the input field. (Ref# J525979)
  • The time from boot to the launch of the Home screen is more than 10 seconds. (Ref# J477824)
  • Browser video playback isn't paused and its sound is still heard after Juke Box video playback is stared. (Ref# J551250)

Soundtracker

• If you launch Soundtracker and then use a Facebook account to log in, the Soundtracker app may present an access-denied dialog and fail to run. (Ref# J580747)

  Workaround: Always use your Soundtracker account.

Spectrum Digital J5 ECO EVM811x EVM

• Time from boot to presence of rearview camera is greater than two seconds. (Ref# J242184)

System Launch and Monitor (SLM)

• Changing the /etc/slm-config-all.xml file and then issuing the reboot command will cause SLM to get stuck during the reboot. (Ref# J452674)

  Workarounds:

  • Finish the screen calibration, which will free up SLM.
  • Create a dummy/empty calibration file at /var/etc/system/config/calib.localhost.
  • Run the shutdown command instead of reboot.

Texas Instruments OMAP5 EVM

• Initial bootup time takes too long if low- or mid-range SD cards are used. (Ref# J511371)

  Workaround: Use the recommended SD card, namely, 16GB SanDisk Ultra® microSDHC™ UHS-I.

Wi-Fi

• To access DLNA media via a BlackBerry Z10 Wi-Fi hotspot, the Z10 must be running an OS version of 10.1 or lower. Later devices don't allow the phone to be the Wi-Fi hotspot and serve media at the same time. However if the phone connects to the same Wi-Fi network as the QNX CAR target, and the phone enables media sharing, then the DLNA media source appears in the QNX CAR HMI. (Ref# J611154)
• Packet loss occurs when using WIFI CLIENT. (Ref# J544882)
• You cannot connect to secure networks that use WPA2 Enterprise, which require you to enter both a username and password. Only WPA PSK networks are supported. (Ref# J583145)
• The HMI doesn't clearly indicate the currently connected network. (Ref# J579211)

Windows host

• On a Windows XP host, the default pathname for the workspace (e.g. C:\Documents and Settings\dagibbs\ide-5.0-workspace) contains spaces, which may cause problems for some commandline tools. (Ref# J393829)

  Workaround: Set the workspace in a path that doesn't contain spaces.

Installing and uninstalling

• You'll receive a warning to ensure that all QNX applications and utilities are closed prior to the uninstall. (Ref# 260491, J393515)
• The appropriate information have been added to the installation notes to prevent the installer failing to find the Java path. (Ref# 262222, J393509)
• The text in the dialog box has been updated to clarify the meaning of the user prompt. This dialog box is presented to customers who are installing on a host with another QNX SDP already installed. (Ref# 260840, J393849)
• Installers on Linux hosts create links in user-selected folder. These links point to the IDE launcher and the Uninstaller. On Windows, there is a choice to create shortcuts either on Desktop or in the Start Menu. (Ref# 226648, J393510)
• Installers now display license activation dialogs. (Ref# 250676, J393511)
• Installation notes now include information regarding the location where the Installer can be launched. (Ref# 261028, J393516)
• QNX_CONFIGURATION no longer needs to be set before running addLicense. (Ref# 262816, J393518)
• Installation notes now include recommended order of uninstalling. (Ref# 264895, J393519)
• The disk space requirement quoted in the Linux Installer is no longer incorrect. (Ref# 259685, J393514)

General

• The Home screen now starts up properly when the system time isn't set. (Ref# 216622, J400718)

Bluetooth

• The Communication menu is now visible in the Default theme, so you can now see Bluetooth devices in the Settings app. (Ref# J439998)
• When a paired device is deleted from the system in Settings, it no longer remains in the Personalization list. (Ref# 244039, J400842)
• On Jacinto 5 Eco, there's now audio during handsfree calling (HFP). (Ref# J400986)
• MAP synchronization no longer fails if you receive emails while it's in progress. (Ref# 259590, J400930)
• If you connect multiple devices, then disconnect one, the available device list in the Preferred Device screen now refreshes properly. (Ref# 244039, J400842)

Geolocation

• The browser Geolocation service now works. (Ref# 208430, J400665)
• When you're running the GeolocationTest app, and you close and reopen the app, the test no longer fails, and the ip-provider service no longer crashes. (Ref# J441099)

HTML5 and WebWorks

• JNext dependencies available on the installed system are now found correctly by the WebWorks application. (Ref# 232959, J400774)

Jacinto 5 Eco

• SATA disks no longer fail to boot. (Ref# J437962)

Multimedia

• When you're browsing the DLNA server and selecting a track to play while another track is already playing, the mm-player service no longer crashes. (Ref# J440235)
• When you're searching for an artist with mm-player, the results now contain the tracks from that albums, instead of the Album nodes, which can't be played in the tracksession. (Ref# J421401)

Navigation

• Issuing the NavigateTo command to the /pps/qnxcar/navigation/control object with the id parameter no longer causes eb-navigation to crash. (Ref# J401220)

Networking

• The io-pkt service no longer crashes after you connect and disconnect Bluetooth. (Ref# J435476)

OMAP5 uEVM

• The IPL can now find an IFS on the eMMC DOS partition. (Ref# J420160)

Qt HMI

• You can now use the category buttons to switch between the ALL and VEHICLE categories. (Ref# J437937)
• If a USB stick is unplugged while a song from the stick is playing, the default JukeBox screen is now displayed. (Ref# J424084)

Software Update

• Software Update now works on the Freescale i.MX6Q SABRE Lite board. (Ref# 260833, J400941)
• Native graphics app no longer fails during installation on the i.MX6Q board. (Ref# 264163, J400947)
• If Software Update touches a file, its permissions are no longer changed. (Ref# J440556)