The QNX CAR platform is designed to support a variety of third-party navigation engines.
For more information about the QNX CAR navigation engine, see "Navigation" in the QNX CAR Architecture Guide. For more information about using the navigation engine HMI, see "Navigation" in the QNX CAR User's Guide chapter "A Guided Tour of the HMI".
APKRUNTIME:true DLNA:false WIFI:true NAVIGATION:true APPUPD:false
If you are working with a configuration that has had the navigation engine disabled, as well as configuring the services-enabled file you may need to change the tablist.json file so that it displays a navigation tab correctly. To do this, you need to edit the tablist.json file:
"tab3": { "id": "navigation", "type": "local", "order": "3", "name": "Navigation", "opts": { "class": "nav" } }
The current QNX CAR release comes with the Elektrobit (EB) street director.
The EB street director navigation engine is called /apps/eb-navigation. If you are debugging your implementation and need more detailed information in the logs, just start the navigation engine with greater verbosity. For example: -vvvvvvvv.
The configuration file for the EB street director is /apps/eb-navigation/ebnav.conf. For more information about this file and configuring the EB street director, please see your Elektrobit documentation.