MeeGo wiki - User contributions [en]

In-vehicle

2011-05-15T08:57:46Z

Jimmyhuang: /* MeeGo IVI Weekly Builds */

= In-vehicle Infotainment (IVI) =

MeeGo IVI is setting the new standard for in-vehicle infotainment in cars, buses, airplanes, etc. MeeGo IVI is a Free and Open-Source Software (FOSS) OS distribution integrating the MeeGo Core for embedded systems leveraging and extending functionality known from mobile computers and handsets into vehicles. Building on the MeeGo OS Base and the MeeGo OS Middleware the MeeGo IVI software stack enables rich Internet and multimedia experiences to consumers while traveling.

== Organization ==

The MeeGo IVI organization is composed of a Working Group and a Project Team. The Working Group is responsible for the definition of the roadmap and the MeeGo IVI Project Team executes the implementation through the partnering organizations using the best practices of open-source development. Through the collaboration of organizations and companies covering automotive, computer hardware, communications, and software industries this partnership enables jump-starting product development for rapid delivery allowing adopters to concentrate on their core competencies while benefiting from this extensive know-how and the open-source assets.

For a graphical representation of the organizational structure: [[Media:MeeGo_IVI_OrgStruct.pdf]]

=== Working Group ===

The Working Group is composed from the following members and roles:

* Working Group Chair
** Represents and promotes the Working Group.
** Leads strategic discussions on requirements, direction, policies.
** Commitment: full-time role.
** Current Working Group Chair: '''[http://meego.com/users/RudolfStreif Rudi Streif (Linux Foundation)]'''

* Working Group Representative (the number is not limited, others participants to be invited)
** Represents his/her organization in the Working Group.
** Collects, organizes, prioritizes, and contributes requirements from his/her organization.
** Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
** Current Working Group Representatives:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** Leads the Project Team and defines the release schedule together with the Project Manager.
** Accountable to the Working Group for delivery of agreed upon requirements.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PDM.pdf]]
** Current Product Manager:

* Program Manager (cross-functional across Working Group and Project Team)
** Works the Lead Architects and Lead Designers on effort estimates and schedules.
** Leads the Project Team together with the Project Manager.
** Accountable to the Working Group for deliverables and schedule.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PJM.pdf]]
** Current Program Manager: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|IVI Working Group]].

=== Project Team ===

The Project Team has members with various roles that are subject to change according to the requirements of the current projects. The number of members and roles in the Project Team is not limited and grow as the team gains momentum and takes on larger tasks.

* Lead Architect
** Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
** Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
** Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
** Commitment: > 50% dependent on sub-project complexity.
** Current Lead Architect: '''[http://meego.com/users/tomcounihan Tom Counihan (Intel)]'''

* Lead Designer (multiple roles)
** Responsible for the detailed implementation design of the architecture.
** Estimates the effort necessary for implementation.
** Leads implementation team comprised of engineering resources of his/her organization.
** Commitment: full-time role.
** Current Lead Designers
***
***

* QA Lead (multiple roles)
** Transforms requirements into functionality test plans.
** Develops interface and compliance test procedures according to the architecture.
** Implements black box and white box test tools through the resources of his/her organization.
** Executes test plans and provides test reports.
** Commitment: full-time role.
** Current QA Leads:
***
***

* Release Manager
** Coordinates bug tracking, build and release with the design and QA leads.
** Develops and manages build tools.
** Leads build and release engineering team.
** Commitment: full-time role.
** Current Release Manager: '''[http://meego.com/users/jeremiah Jeremiah Foster (Pelagicore)]'''

* Engineers for Development and QA (many roles)
** Implement and test the required functionality.
** Qualification varies with sub-project.
** Commitment: full-time role.

== Roadmap ==

The roadmap is always under discussion. But the important thing it that it is open and transparent - and you can contribute. The path to contribution begins on the MeeGo IVI mailing list. This list is the central communication point with all the MeeGo IVI stakeholders participating. Through this list you can contribute ideas, code, and other resources. You will also receive support and advice as well as pointers to other resources on this list, this is where the community comes together.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com.

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features Submit new MeeGo IVI feature request ]

For a Feature Request to become part of the MeeGo IVI release plan, it needs to clearly define the engineering requirements and have resources working on development.

More details on the long term direction and short term Release plan may be found in the [[In-vehicle/Roadmap|IVI roadmap]].

=== MeeGo IVI Weekly Builds ===
Automated weekly MeeGo IVI repository and image builds are available on meego.com for testing and development baselining. Each build has a build version and date in its path. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.99.x''' is a 1.2 Release Candidate, and '''1.2.1''' is the first release update after the final 1.2 release.

[http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

IVI live .iso images are found under the ''IVI'' link. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the ''oss'' and ''non-oss'' links.

'''MeeGo IVI 1.2 Feature Status'''

[https://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&rep_platform=Automotive&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Featurezilla status report of MeeGo 1.2 IVI features]

[[In-vehicle/IVI Home Guide|Guide for the IVI Home Screen]]

;May 10, 2011
:IVI Home Screen Changes
::The IVI home screen has been ported to QML and it's now based on the MeeGo UX and launched through meego-ux-daemon. It implements an updated scroll menu and also supports quick access to commonly used apps through the desktop and a Top Application task bar. The scroll menu navigation has been updated to reduce the number of choices in the main menu. Instead of a dozen or so choices in the main menu and two to three choices in sub-menus, now there are five to six choices in the main menu and about the same in sub-menus. We changed this to make menu choices easier and quicker. The IVI home screen has been designed to support driver interaction with the minimal amount of distraction. This is enhanced by the use of scrollwheel, Text to Speech and Speech Recognition, removing the need to look at or touch the display. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.
:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
:WiFi Tethering
::MeeGo IVI now includes the capability to act as a WiFi Access Point enabling data sharing between tethered WiFi devices [https://bugs.meego.com/show_bug.cgi?id=7696 MeeGo WiFi Tethering Feature]
:EMGD
::The Embedded Media Graphics Driver (EMGD) is now integrated with all IA32 builds and provides support for the Power-VR graphics core in Intel IVI platforms. The driver package is named <nowiki> "emgd-bin...."</nowiki> and can be found in the <nowiki>"non-oss"</nowiki> repository. This driver is considered ENGINEERING SAMPLE quality with NO guaranteed response to issues. Anyone planning to use this driver in product should obtain production quality support from the EMGD team via http://edc.intel.com

;March 8, 2011
:EMGD
::The Intel EMGD graphics driver has had continued updates including the addition of support for hardware accelerated video decode.
:ML7213 platform
::kernel driver support for the Oki Semiconductor ML7213 IVI IOH chipset has been added. This chipset is used on the Intel Stephenville/Crossville IVI platform. This platform is in very early sampling now to select customers of the Intel Embedded Computing Group.

===MeeGo IVI 1.2 Release Supported Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|No known driver issues
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Intel Platform Controller Hub EG20T (Top Cliff)
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, PHUB, CAN
|No known driver issues
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|No known driver issues
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|ST Microelectronics ConneXt STA2x11
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, CAN, USB-OTG, MSP, BT, FM-Radio
|in development, several issues open
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]

In-vehicle/IVIHome Guide

2011-05-15T08:53:19Z

Jimmyhuang:

The new QML-based MeeGo IVI UX replaces the existing "IVIHome" application and now is the default MeeGo IVI homescreen when the system boots. A lot of the functionalities and features of the existing home screen are ported over to the new UX. This section provides information about the design and use of the new MeeGo IVI Home Screen.

== MeeGo IVI Home Screen Design Objectives ==

The primary objectives in designing the IVI Home Screen were:
# Provide a sample UX that utilizes a scrollwheel, Text to Speech and Speech Recognition so that it can be operated without distracting driver by requiring them to look at the display or a keyboard. During system development the home screen application may still be operated via touchscreen or mouse.
# Provide an "automotive" look and feel with a scrollable menu that reflects the scrollwheel use and the ability to easily customized the UX with the new QML-based and javascript language, which provides cutting edge UIs with unified user experience interating with other MeeGo applications.

== IVI Home Screen Use ==

Navigating the IVI home screen may be done via touchscreen, scrollwheel, and Speech Recognition of voice commands with the help of Text to Speech (TTS).

Touchscreen support
* IVI home screen has full touchscreen support for platforms with working touchscreen hardware and drivers
* IVI home screen can also be navigated using a mouse and the user can use the mouse wheel to scroll through the menu.
Scrollwheel Support
*Currently only the Contour ShuttleXpress is supported since the key mapping is hard-coded.
*Currently only the IVI home screen supports the ShuttleXpress. The application support has not been implemented yet.
*The ShuttleXpress controller has 5 dedicated mouse buttons and knob that turns left/right, all of these buttons simulate key presses on a hardware button in a car and currently only works when you are at the IVI home screen, they are not yet supported in any of the applications.
*Just plug in the ShuttleXpress and it will recognize the device automatically.
* The buttons are mapped to the following functions:
**Button1 – BACK, at the home screen, this takes you back to the previous menu or closes the menu completely. It will take you back to the home screen if you are within any other applications.
**Button2 – HOME, this will always open up the navigation menu if the menu is closed, or return you back to the home menu if you are in a sub menu.
**Button3 – SELECT/OPEN, this will open the highlighted menu or application, it is the same as clicking on the application.
**Knob Left – At the desktop, this makes the desktop icons rotate counter-clockwise. When the menu is opened, use this to navigate through the menu in UP direction.
**Knob Right – At the desktop, this makes the desktop icons rotate clockwise. When the menu is opened, use this to navigate through the menu in DOWN direction.
Text-to-Speech(TTS)
*Supported by home screen and menu navigation
*When you navigate the desktop icon list or the scroll menu list, it will use Festival to say the current menu item, you should hear “Navigation, Communication”, etc as you browse through the menu.
*Text to speech is turned on by default, however, if you use TTS with speech recognition on a system with a mic too close to the speakers, they might interfere.
*You can turn TTS on/off by clicking on the toggle button in the top menu of the home screen.
Speech recognition (IVI home screen voice commands)
*Speech recognition is supported by IVI Home Screen only. Speech recognition in applications needs to be added.
*Speech recognition does not support continuous speech, it only recognizes voice commands for the IVI home menu as shown below
*Speech recognition is turned off by default. To turn on speech recognition, click on the microphone toggle button in the top menu of the home screen.
*The following tables list the supported voice commands (you can also look in <code>/usr/share/meego-ux-ivi/voicerecognition/meego-ux-ivi.jsgf</code>):

{| class="wikitable"
|+ Menu Navigation Commands
|-
!Voice Command
!Resulting action
|-
|"Home"
|Goes back to the home screen if you are within any application. If you are at the home screen, it opens the home menu if the menu is closed, or returns to the home menu, same as the clicking HOME button on ShuttleXpress
|-
|"Back"
|goes back to the last menu, same as clicking the BACK button on ShuttleXpress
|-
|"Cancel"
|Same as the "Back" command
|-
|"Next"
|moves to the next application on the desktop or next item on the scroll menu, same as turning the knob to the RIGHT on the ShuttleXpress
|-
|"Previous"
|moves to the previous application on the desktop or the previous item on the scroll menu, same as turning the knob to the LEFT on the ShuttleXpress
|-
|"Open"
|launches the selected application on the desktop or the selected application on the scroll menu.
|-
|"Close"
|Closes the current applicatoin and return to the IVI home screen
|-
|"Tasks"
|Shows the task switcher with a list of running applications
|}

If you are in the desktop with the scroll menu closed, you can directly speak the name of any of the 5 application shown in the desktop menu. It will automatically highlight the recognized application.

{| class="wikitable"
|+ Shortcut Application Commands
|-
!Voice Commands
|-
|"Navigation"
|-
|"Settings"
|-
|"Dialer"
|-
|"Web"
|-
|"Panels"
|}

Voice commands may be used to skip menu navigation and go directly to specific applications
{| class="wikitable"
|+ Application commands
|-
!Voice Command
!Resulting action
|-
|"Open Navigation"
|opens the Navit application
|-
|"Open Dialer"
|opens the Dialer application with BT-HFP
|-
|"Open Contacts"
|opens the MeeGo contacts application
|-
|"Open Web"
|opens the MeeGo browser application
|-
|"Open Browser"
|opens the MeeGo browser application
|-
|"Open Photos"
|opens the the MeeGo photo application
|-
|"Open Music"
|opens the MeeGo music application
|-
|"Open Videos"
|opens the MeeGo video application
|-
|"Open Settings"
|opens the the MeeGo control panel application
|-
|"Open Panels"
|opens the the MeeGo panels
|}

The list of applications for each of the above application commands are defined in the <code>/usr/share/meego-ux-ivi/home.js</code> javascript file. You can edit this file to change the application that is launched by the voice commands. You cannot change the vocabulary list directly, it needs to be re-generated. If you want to add more voice commands, you’ll have to add the command in the dictionary and re-generate the language model (grammar) and dictionary and implement the logic in the application.

[[Category:IVI]]

In-vehicle

2011-05-15T08:03:50Z

Jimmyhuang:

= In-vehicle Infotainment (IVI) =

MeeGo IVI is setting the new standard for in-vehicle infotainment in cars, buses, airplanes, etc. MeeGo IVI is a Free and Open-Source Software (FOSS) OS distribution integrating the MeeGo Core for embedded systems leveraging and extending functionality known from mobile computers and handsets into vehicles. Building on the MeeGo OS Base and the MeeGo OS Middleware the MeeGo IVI software stack enables rich Internet and multimedia experiences to consumers while traveling.

== Organization ==

The MeeGo IVI organization is composed of a Working Group and a Project Team. The Working Group is responsible for the definition of the roadmap and the MeeGo IVI Project Team executes the implementation through the partnering organizations using the best practices of open-source development. Through the collaboration of organizations and companies covering automotive, computer hardware, communications, and software industries this partnership enables jump-starting product development for rapid delivery allowing adopters to concentrate on their core competencies while benefiting from this extensive know-how and the open-source assets.

For a graphical representation of the organizational structure: [[Media:MeeGo_IVI_OrgStruct.pdf]]

=== Working Group ===

The Working Group is composed from the following members and roles:

* Working Group Chair
** Represents and promotes the Working Group.
** Leads strategic discussions on requirements, direction, policies.
** Commitment: full-time role.
** Current Working Group Chair: '''[http://meego.com/users/RudolfStreif Rudi Streif (Linux Foundation)]'''

* Working Group Representative (the number is not limited, others participants to be invited)
** Represents his/her organization in the Working Group.
** Collects, organizes, prioritizes, and contributes requirements from his/her organization.
** Commitment: 20% - 50% dependent on how actively the organization wants to contribute requirements.
** Current Working Group Representatives:
*** Intel: '''[http://meego.com/users/jahoffmann Joel Hoffmann]'''
*** Nokia: '''[http://meego.com/users/alistair Alistair Adams]'''
*** Pelagicore: '''[http://meego.com/users/mikael Mikael Soderberg]'''
*** Visteon: '''[http://meego.com/users/PavelKonopelko Pavel Konopelko]'''

* Product Manager (cross-function across Working Group and Project Team)
** Unifies and prioritizes overall requirements set.
** Owns the roadmap.
** Leads the Project Team and defines the release schedule together with the Project Manager.
** Accountable to the Working Group for delivery of agreed upon requirements.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PDM.pdf]]
** Current Product Manager:

* Program Manager (cross-functional across Working Group and Project Team)
** Works the Lead Architects and Lead Designers on effort estimates and schedules.
** Leads the Project Team together with the Project Manager.
** Accountable to the Working Group for deliverables and schedule.
** Commitment: full-time role.
** Full job description: [[Media:MeeGo_IVI_PJM.pdf]]
** Current Program Manager: '''[http://meego.com/users/joel Joel Clark (Intel)]'''

The Working Group meets regularly. Information on current and past meetings can be found on [[in-vehicle/working-group|IVI Working Group]].

=== Project Team ===

The Project Team has members with various roles that are subject to change according to the requirements of the current projects. The number of members and roles in the Project Team is not limited and grow as the team gains momentum and takes on larger tasks.

* Lead Architect
** Defines technical architecture to meet the requirements n terms of functionality, performance, etc.
** Defines interfaces between modules and components together with other Lead Architects within the same and/or other Project Teams.
** Performs feasibility studies and provides feedback to product manager on technical challenges, difficulties, “show stoppers”.
** Commitment: > 50% dependent on sub-project complexity.
** Current Lead Architect: '''[http://meego.com/users/tomcounihan Tom Counihan (Intel)]'''

* Lead Designer (multiple roles)
** Responsible for the detailed implementation design of the architecture.
** Estimates the effort necessary for implementation.
** Leads implementation team comprised of engineering resources of his/her organization.
** Commitment: full-time role.
** Current Lead Designers
***
***

* QA Lead (multiple roles)
** Transforms requirements into functionality test plans.
** Develops interface and compliance test procedures according to the architecture.
** Implements black box and white box test tools through the resources of his/her organization.
** Executes test plans and provides test reports.
** Commitment: full-time role.
** Current QA Leads:
***
***

* Release Manager
** Coordinates bug tracking, build and release with the design and QA leads.
** Develops and manages build tools.
** Leads build and release engineering team.
** Commitment: full-time role.
** Current Release Manager: '''[http://meego.com/users/jeremiah Jeremiah Foster (Pelagicore)]'''

* Engineers for Development and QA (many roles)
** Implement and test the required functionality.
** Qualification varies with sub-project.
** Commitment: full-time role.

== Roadmap ==

The roadmap is always under discussion. But the important thing it that it is open and transparent - and you can contribute. The path to contribution begins on the MeeGo IVI mailing list. This list is the central communication point with all the MeeGo IVI stakeholders participating. Through this list you can contribute ideas, code, and other resources. You will also receive support and advice as well as pointers to other resources on this list, this is where the community comes together.

The roadmap pages are the central collaboration point on laying out the future of MeeGo IVI. Here architecture details, system diagrams, use cases, etc. are shared.

[[In-vehicle/Roadmap|View the Roadmap]]

Before any new feature is committed to the Roadmap, a feature request is created in http://bugs.meego.com.

[https://bugs.meego.com/enter_bug.cgi?product=MeeGo%20IVI%20Features Submit new MeeGo IVI feature request ]

For a Feature Request to become part of the MeeGo IVI release plan, it needs to clearly define the engineering requirements and have resources working on development.

More details on the long term direction and short term Release plan may be found in the [[In-vehicle/Roadmap|IVI roadmap]].

=== MeeGo IVI Weekly Builds ===
Automated weekly MeeGo IVI repository and image builds are available on meego.com for testing and development baselining. Each build has a build version and date in its path. [[Release Engineering/Release Versioning|MeeGo Release Versioning]] explains the build version numbering scheme. For example '''1.2.80.xx''' is a 1.2 Alpha build, '''1.2.90.xx''' is a 1.2 Beta build, '''1.2.99.x''' is a 1.2 Release Candidate, and '''1.2.1''' is the first release update after the final 1.2 release.

[http://repo.meego.com/MeeGo/builds/trunk/ MeeGo weekly build repositories]

IVI live .iso images are found under the ''IVI'' link. A list of every package included a live image is found in the same directory as the image. RPM packages are found under the ''oss'' and ''non-oss'' links.

'''MeeGo IVI 1.2 Feature Status'''

[https://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&rep_platform=Automotive&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Featurezilla status report of MeeGo 1.2 IVI features]

[[In-vehicle/IVIHome Guide|Guide for the IVI Home Screen]]

;May 10, 2011
:IVI Home Screen Changes
::The ''IVIHome'' screen has been ported to QML and it's now based on the MeeGo UX. It still have a scroll menu and also supports desktop icons for fast access to commonly used apps. The scroll menu navigation has been updated to reduce the number of choices in the main menu. Instead of a dozen or so choices in the main menu and two to three choices in sub-menus, now there are five to six choices in the main menu and about the same in sub-menus. We changed this to make menu choices easier and quicker. The IVI home screen has been designed to support driver interaction with the minimal amount of distraction. This is enhanced by the use of scrollwheel, Text to Speech and Speech Recognition, removing the need to look at or touch the display. Both Text to Speech and Speech Recognition can now be toggled on the home screen for easier access. Since the UX is now based on QML, it makes customizing the UI much easier since they are script-based, and thus without the need of re-compiling for any changes.
:Nokia Terminal Mode
::Packages implementing the client side of Nokia Terminal Mode have been included in the build repositories. There are two packages(libqterminalmode and qterminalmodeclient) which must be installed from the ''oss'' repositories in order to try this code. These packages interact with phonesets that support the server side of Nokia Terminal Mode. Nokia has developer kit phone sets that implement the server side of terminal mode. [http://www.terminalmode.org/en/developer/developer-offering/ Terminal Mode Developer Offering] has more information about the software and how to get developer kits
:WiFi Tethering
::MeeGo IVI now includes the capability to act as a WiFi Access Point enabling data sharing between tethered WiFi devices [https://bugs.meego.com/show_bug.cgi?id=7696 MeeGo WiFi Tethering Feature]
:EMGD
::The Embedded Media Graphics Driver (EMGD) is now integrated with all IA32 builds and provides support for the Power-VR graphics core in Intel IVI platforms. The driver package is named <nowiki> "emgd-bin...."</nowiki> and can be found in the <nowiki>"non-oss"</nowiki> repository. This driver is considered ENGINEERING SAMPLE quality with NO guaranteed response to issues. Anyone planning to use this driver in product should obtain production quality support from the EMGD team via http://edc.intel.com

;March 8, 2011
:EMGD
::The Intel EMGD graphics driver has had continued updates including the addition of support for hardware accelerated video decode.
:ML7213 platform
::kernel driver support for the Oki Semiconductor ML7213 IVI IOH chipset has been added. This chipset is used on the Intel Stephenville/Crossville IVI platform. This platform is in very early sampling now to select customers of the Intel Embedded Computing Group.

===MeeGo IVI 1.2 Release Supported Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32
|Congatec IVI Kit (Russellville)
|Intel Atom Z5xx Series and Intel System Controller Hub US15Wx (eMenlow)
|Timberdale
|GPIO, DMA, SPI, I2C, UART, USB, IDE, Audio, KS8842 GigE, EMGD, Video-in, SDHC, TSC2007, I2S, SDHC, ADV7180, BT, Radio
|No known driver issues
|-
|meego-ivi-ia32
|Crown Bay
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Intel Platform Controller Hub EG20T (Top Cliff)
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, PHUB, CAN
|No known driver issues
|-
|meego-ivi-ia32
|Stephenville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|Oki Semiconductors ML7213 IVI IOH
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, EMGD, SD/SDIO/MMC, USB-OTG, TDM, sDVO
|No known driver issues
|}

===MeeGo IVI Trunk Prototype Platforms===

;IA32
{| border="1"
! Image name
! Platform name
! Intel chipset
! I/O Hub name
! drivers included
! status
|-
|meego-ivi-ia32-conx
|Stephenville/Northville/Crossville
|Intel Atom E6xx Series for Embedded (Tunnel Creek)
|ST Microelectronics ConneXt STA2x11
|GPIO, DMA, SPI, I2C, UART, USB, SATA, Audio, GigE, EMGD, Video-in, MMC, CAN, USB-OTG, MSP, BT, FM-Radio
|in development, several issues open
|}

;ARM
:Jeremiah Foster and Jan-Simon Moeller are working on updates to enable automated weekly builds of MeeGo IVI images for the Beagleboard-XM.
:The suggested reference platform is the Beagleboard xM. The [[ARM/OMAP4_Panda|PandaBoard]] and [[ARM/Snowball|Snowball]] most likely will be supported in the future.
{| border="1"
! Image name
! Platform name
! chipset
! status
|-
| meego-ivi-armv7l
| Beagleboard xM
| OMAP 3
| Not yet smoke tested. No QA
|-
| meego-ivi-armv7l
| Tegra2
| ARM v7 rev 0
| Not yet smoke tested. No QA
|-
|}

=== Releases ===
* [http://meego.com/downloads/releases/1.0/meego-v1.0-in-vehicle-infotainment-ivi MeeGo IVI 1.0]
* [http://meego.com/downloads/releases/1.1/meego-v1.1-in-vehicle-infotainment-ivi MeeGo IVI 1.1]

== Resources ==
* IRC irc.freenode.org #meego-ivi
* Mailing list sign-up: http://lists.meego.com/listinfo/meego-ivi
* Mailing list archive: http://lists.meego.com/pipermail/meego-ivi/
* [[In-vehicle/IVI for users and developers|IVI for users and developers]]
* [[IVITopic|Topics]]

[[Category:IVI]]