Automotive Linux Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== AGL Roadmap =====

The official AGL Roadmap is maintained in Jira. [[https://jira.automotivelinux.org/issues/?filter=10401 |This link]] will show the latest project list in Jira. More information on how AGL uses Jira for project management can be found [[start:using-jira|here]]. 

===== 2019 Roadmap/ Workplan from SAT =====

    * **Happy Halibut and Itchy Icefish on Yocto 2.6 (thud)**
    * Components to move from agl-devel to agl-extras
      * 4a
     * Review Reference Hardware System Architecture document and consider its implications for the software architecture. 
     * Move RHSA to doc site. 
     * Finish the documentation site improvements and increase the amount of documentation by 100%
     * Move to groups.io 
     * **Add video support to mediaplayer binding**
     * Finish AGL spec 2.0
     * Web App Manager maturity 
     * Speech API maturity
     * Home Screen and Window Manager re-architecture 
     * Instrument Cluster reference device improvements and maturity
     * Create Telematics reference device
     * New reference board for 2019? CES 2020 board should be M3 again or move to H3?  Need information from RHSA.



==== From App FW and Security EG ====

     * **HTML5 apps**
       * HTML5 home screen
       * Chromium

     * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them.
     * Define the list of privileges we are going to enforce in the security model.   
     * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} **Running apps not as root/ multi-user**
     * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) 
     * Changes necessary at binder level for V2C (SSL transport)
     * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Application signing and installation mechanism
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} Mechanism for checking signature is in place. 
       * Require all apps to be signed in GG
       * Developer workflow is needed for managing keys
       * Development mode and Production mode for app management 
     * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.
     * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} Binder APIv3 (enable dynamic APIs)
     * Improved Developer workflow for debugging apps including 
       * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Round trip download/debug/fix/download apps. 
       * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} **Supervision daemon for apps and services for development mode.** Allows a developers to have a central place monitor IPC in real time. Builds on the current monitor service that is available for binders. Extends its availability to startup and allows more general monitoring without requiring detailed knowledge of what is available in a specific binder.

     * **Task manager app** to allow developers to see what tasks/process are running in an app. Allow for killing apps.  
       * Review AGL spec 1.0 to determine what requirements are there for managing home screen and apps. Something like iphone where a double-tap on home button allows swiping up of apps to kill them. 
     * Terminal app on home screen

     * Introduce resource widgets to share content/ resources across multiple apps. 
     * App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5
     * App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? 
     * App Framework binder communications shall be able to manage return from sleep mode. 
     * Connection glitches in multi-ECU system shall be properly handled. 
     * **XDS features**
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} v1.1.0 - targeted release date: AMM (2018 February 20th)
         * Board console/terminal integration within XDS dashboard
         * Documentation improvement of debug section
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} v6.0.0 - targeted release date: ALS  (2018 June 20th)
         * Monitoring integration
       * v7.0.0 
         * Improved development cycle (based on partial Widget installation)
         * First step to support package manager for SDKs (Yomo)

     * **GG Priorities for App FW**
       * Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH
         * Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread)
         * Kill apps individually from life cycle manager
         * Need to define state diagram for app life cycle

       * **HTML5 app support as necessary**
       * Multi-user use case
       * API for abstraction of hardware mechanism for signing apps, packages, etc. 
       * Headless/ Telematics use case
       * Unit testing for app framework
       * Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms. 
         * Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]]
         * Allow keys to be changed by the device developers - git repo and recipe for keys
         * Library (or binding) to plug in key management to the app FW. 
         * Reference implementation will use the file system as the key store. Can be swapped for a trusted environment by a device creator at a later time. 
         * Sign at build time in AGL CI system with a check at run time 

==== From Graphics EG ====
     * Graphic
       * **Finish Window Manager and Homescreen work**
         * Home Screen API / service
           * UI for Qt
           * UI for HTML5
         * High level API for virtual keyboard in english and Japanese
         * Pop-up support
           * Virtual keyboard placement and removal
           * Alerts
         * Focus management for out of focus apps
         * Multi-resolution display support. 
           * Fix scaling issues across different display sizes 
           * Landscape vs. portrait 

 
         * Add new apps to home screen (not hardcoded) - SPEC-1734
         * Management of apps that overflow the screen - slider or multiple pages or folders
         * Improved secondary display support 
         * Transition Animation
           * Need to define use cases and requirements
           * Handled by Qt Compositor if we continue to use it for demos. 
           * Will need to rethink if we switch compositors
         * Hardware plane management; Rear view camera, smart phone connection,,,
         * User interactive response; vibration of screen, beep,,,
       * Upstream to Wayland/Weston
         * xdg protocol
         * Waltham protocol for internode display
       * Investigate replacement for Qt; HTML5, GTK+,,,,
     * **Audio**
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} High Level audio API
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} AGL Advanced Audio Agent (4A)
       * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Make PulseAudio optional
         * Switch to Bluez / Alsa for Bluetooth audio
       * Speech and Text to Speech Services collaboration
         * Policy management between mic input and Media player output

   * Questions for EG from SAT:
     * Do we remove support for IVI protocol is favor of XDG?
       * Answer: No. Cannot deprecate IVI protocol unless extensions to XDG are made.  

     * What is the roadmap for Wayland/Weston versions for 2018?
       * SAT recommends following Yocto. 


==== From Connectivity EG ====
     * Vehicle Signaling 
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **Signal composer stabilization an improvements**
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} API to define new virtual messages at run-time
       * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} Extend low level binding to hardware other than CAN. Need to determine what the next target hardware should be. 
       * Factory programming of CAN message set based on final vehicle configuration. Requires multiple vehicle message dictionaries to be present in the code. 
       * **Add GPS data to virtual signal composer**
       * **Sensor data collection and include in signal composer**
       * **V2C interface**
       * **Improved performance using Denso Ten baseline as presented at ALS 2018**
       * Content encryption within vehicle for streaming services or Blue Ray content. 
       * Telematics reference device profile with built in modem

     * Bluetooth improvements
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **Bluetooth binding rewrite** for stability and robustness 
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **PBAP/Contacts binding**
       * BLE binding 
     * WiFi improvements
       * {{:ff-ready-brightgreen.png?nolink&75|FF-READY}} **WiFi binding rewrite** for stability and robustness
       * **AP mode**
       * **Additional Wifi dongle support**
       * 802.11p support
       * Investigate LPWAN support for automotive
     * WWAN binding
       * Support current QMI  modems via either modemmanager or ofono
     * Telephony app improvements
       * Show missed call, last outgoing, last incoming call log info
       * Contacts integrated into dialing, caller ID, and call log info
     * NFC binder and NFC for user identification
     * Hardwired connection to telephone for **Telematics use cases**
     * Network management binding
       * GG priorities in bold
       * General network connectivity above connman to manage connectivity including **IPv4/v6 configuration**, bridging, tethering, network QOS and switching
       * **Add configuration support for networking into settings app**
       * User profiles to allow authorized users to configure interfacing
       * Support multiple low-level interface binding backends including **Ethernet, WiFi**, BT PAN, and WWAN

     * For 2018 - evaluate usage of connman versus network manager/modem manager for long-term especially for 4G and complex use cases.


==== From V2X EG ====
     * Kickoff EG

==== From Virtualization EG ====
     * AGL virtualization support (HOST)
       * Add support for open-source hypervisors in meta-egvirt for both ARM and Intel AGL platforms. In this way, at compilation time it will be possible to select the hypervisor to use
         * Finalize KVM support (today available on Renesas RCar-M3 only)
         * Add support for other solutions such as XEN and Jailhouse
       * Write documentation and guides to use AGL as a host system
     * AGL virtualization support (GUEST)
       * Add official support for AGL to be run as a guest on ARM and Intel CPU architectures
       * Add support for XEN, KVM, Jailhouse
         * Add support to automatically build pre-built binaries for each solution, in a way that users can directly download the latest stable version
       * Write documentation and guides to use AGL as a guest system
     * Build a a graphical virtual machine manager application for AGL
       * Create (or extend) a tool to handle guest operating systems from the AGL Graphic User Interface
       * Add support to start and stop guests, or to attach USB device to a guest OS
     * VMs/AGL profiles communication
       * define, design and develop a common API to enable communication/interaction between different VMs/AGL profiles
     * CES2019 demonstrator integration
       * include virtualization in the CES2019 demo, in a way that all the new features developed in 2018 are demonstrated
         * showcase at least two operating systems running concurrently (e.g., two AGL profiles), interacting and exchanging data with each other


==== From CIAT EG ====
     * Lab in a box
       * Board management
       * Board on developer's desk
     * Improved publishing of test results
     * Additional tests
       * Applications
       * {{:ff-partial-yellow.png?nolink&75|FF-PARTIAL}} App Services
       * Platform
       * BSPs
     * Fuego integration

==== From Navi EG ====
     * AGL Navigation API
       * Complete OSS implementation of Navi API 1.0 by ALS2018(FF release). 
       * Complete documentation of Navi API 1.0 by ALS2018(FF release). 
     * Ref. Apps
       * Navigation app divide to Navi service and Navi Apps.
       * Text to Speech Services collaboration
         * Guide voice (TTS function using) migrate to AGL standard.
--------
===== Methodology =====
  * Original project list was started in 2014 maintained [[project-ratings|here]]. The projects were rated by the steering committee at that time from 1 - 5 stars. 
  * Project list was updated in 2015 - still on wiki. 
  * Feb 2016 
    * Reviewed list with Expert Groups, System Architecture Team, and Advisory Board prior to All Member Meeting
    * Rated projects from 1 to 5 Stars
    * Roadmap is based on moving ahead with 4 and 5 Star Projects
    * Roadmap moved to [[https://jira.automotivelinux.org/issues/?filter=10401 | AGL Jira]]. 

===== 5 Star Projects =====

Current Five-Star projects [[https://jira.automotivelinux.org/issues/?filter=10409 | as listed in Jira]]

===== 4 Star Projects =====

Current Four-Star projects [[https://jira.automotivelinux.org/issues/?filter=10410 | as listed in Jira]]


===== 3 Star Projects =====

Current Three-Star projects [[https://jira.automotivelinux.org/issues/?filter=10411 | as listed in Jira]]

===== Unrated/Low Rated Projects =====

Current Unrated or Low Rated projects [[https://jira.automotivelinux.org/issues/?filter=10412 | as listed in Jira]]
Automotive Linux Wiki

User Tools

Site Tools

Page Tools
