Porting Tizen IVI to Wayland

This proposal has been accepted as a session.

Accepted Session
Microconference Session

One Line Summary

Developing Tizen IVI Wayland features in collaboration with upstream projects


Historically, the “IVI” flavor of Tizen has been running using the X11 display system. So did the more generic “Common” profile, until the project decided to catch up with the latest developments of this new technology called Wayland.

As Wayland is now coming into shape and embedded systems such as set-top boxes are already using it, it has been decided to migrate IVI to Wayland. So it is now conceivable to create a Wayland-enabled Tizen IVI device ; but what challenges does that leave for us ?

The problematics adressed by the Tizen IVI team currently are :
- having a GENIVI-compliant API ready ; IVI-Shell, which is the official GENIVI implementation, is being pushed upstream and in the toolkits which applications will use ;
- helping mobile applications which have specific needs (being shown, hidden…) by improving the shell API ;
- adapting the application framework so it can communicate application states to the Wayland compositor ;
- fixing all related bugs and relaying application developers requests.

We will share knowledge of common pitfalls and experienced drawbacks with the audience.


wayland, ivi, tizen

Presentation Materials



  • Photo-manu

    Manuel Bachmann



    Manuel is a software engineer working for EUROGICIEL (France) and currently involved in the Tizen project. He has mainly been working on display issues (Wayland, Weston, EFL, Ozone-Wayland…) and was until recently the maintainer of GTK+ for Windows. He most notably made a proof of concept of OpenCPN running under Wayland, implemented the minimization feature in Weston, and ported the EFL and Ozone-Wayland toolkits to XDG-Shell. His main role is currently to adapt Crosswalk to the Application Framework requirements into Tizen.