SPRACO0 August   2019 AM6526 , AM6528 , AM6546 , AM6548

 

  1.   Enabling Android Automotive on Your TI Development Board
    1.     Trademarks
    2. 1  Introduction
    3. 2  Implementation
      1. 2.1 Prerequisites
      2. 2.2 Software Changes
    4. 3  Deploy Instructions
      1. 3.1 Build Instructions
      2. 3.2 Boot Instructions
    5. 4  Testing
      1. 4.1 Prerequisites/Setup for Automotive Testing
        1. 4.1.1 Compatibility Test Suite (CTS)
        2. 4.1.2 Vendor Test Suite (VTS)
      2. 4.2 Automotive Testing
        1. 4.2.1 Compatibility Test Suite (CTS)
        2. 4.2.2 Vendor Test Suite (VTS)
    6. 5  Open Source
    7. 6  Extending to a New Platform
    8. 7  Known Bugs
    9. 8  Future Work
    10. 9  FAQ
    11. 10 References

8 Future Work

  • Enable Android Auto Human-Machine Interface on new automotive-tuned TI platforms.
  • Migrate to Android Q Pastry Version:
    • Add multiple hardware display support:
      • Interactive: Individual input mapping, decorative elements and IME (soft keyboard)
      • Driver: Main IVI display with all UX restrictions applied
      • Passenger: Add support for more types of apps and individual launchers for each screen
    • Multiple users with “headless” system, where a user is not associated with a real user and does not have a lock screen.
    • Multi-zone Audio:
      • A zone is a collection of audio devices and each user device can only be in one zone.
      • Within each zone, audio usage determines which device the audio is routed to.