Tizen v2.3 System & App Framework

1. Tizen v2.3 System & App Framework

2. Contents • Overview • System & App FW • What is Ecore? • System Framework • Overview • Deviced • Inter-process Communication • Sensor Framework • App Framework • Overview • Appcore • AUL • App Service • Package Manager, AIL, RUA

3. Overview • System Framework • System managements and Device Abstractions • System condition management  Low memory, Low battery, process, CPU frequency handling • Device abstraction and control  display, mmc, earjack, GPS, haptic, etc. • System logging  dlog • Sensor management  sensor server and client library • App Framework • Application main loop • Inter-app communication and launching • Application Install & Uninstall • System event callback

4. System Framework

5. System FW Overview

6. Deviced Architecture

7. Deviced (framework/system/deviced/core) • System monitoring, managing, notifying • Battery, display, vibrator, led, mmc, power, USB, storage, extcon devices • Use Ecore main_loop for event handling • main() (main.c) • ecore_init(): initializing Ecore • deviced_main() • edbus_init: initializing Ecore dbus • deviced_init(): initializing deviced components • Display, storage, USB, lowbat … etc. • notification to systemd • ecore_main_loop_begin(): start main loop of ecore

8. Deviced (framework/system/deviced/core) DD_LIST_APPEND(device_ops, List)

9. What is Ecore? (Event main loop) • Ecore: EFL core library for application • “Operating system abstraction and integration”, http://enlightenment.org • Event-driven main loop  Because GUI application is event-driven. • Many GUI Toolkit use event-driven main loop, ex) Glib • Frequently switch between IDLE / Event handling • save core resource • Can handle file descriptor and signal event • socket, pipe, vconf, IPC, etc. • Also able to use in non-GUI event driven program

10. list.h • Double linked list to handle device operation • “eina_list_*” functions are provided by enlightenment • eina_list_append(Eina_List *list, const void *data) • Append the given data to the given linked list. • eina_list_nth(const Eina_List * list, unsigned int n) • Get the n`th member's data pointer in a list. • Display • EINA_LIST_APPEND(lcdon_ops, ops); • Gpio • DD_LIST_APPEND(gpio_head, (void*)gpio); • USB • DD_LIST_APPEND(storage_job, job); • MMC • DD_LIST_APPEND(fs_head, (void*)fs); Various list types

11. devices.c • Perform device registration and management • add_device() / remove_device() / find_device() • Use “eina_list_*” functions • devices_init() / device_exit() / device_start() / device_stop() / device_execute() • Execute each function of device_ops Start/Stop flags

12. Device Registration Example • ./touch/touchscreen.c • Enable / Disable touchscreen on specific status Check flag • sys_get_int(path,value) • provides access to kernel device driver node parameters Each device is registered automatically in module initializing process

13. device-notifier.c • register_notifier() • Register Notification (Function) for specific status • device_notify() • Execute registered function

14. udev.h / device-change-handler.c • Provide information and callback function for device status change • Use udev • basic way to get a event from kernel in deviced • Support below devices • Input / extcon / power_supply / USB / block device • Register_uevent_control(“Subsystem & Handler”) • Unregister_uevent_control(“Subsystem & Handler”) • Event control management Subsystem / Path Handler

15. Deviced Schema

16. Others • Other system events (battery, USB connection, Device change, MMC device) are also similar as touchscreen • Module structure • Register device operation functions • Init / Exit / Start / Stop / Status / Execute • Use device flags • Handle only the system-level events for devices • Storage I/O will not be handled from deviced

17. Inter-process communication • Various Inter-process communication • heynoti • ss_sysnoti • socket • pipe • vconf • dbus

18. heynoti (framework/appfw/heynoti) • ligHt, Easy, speedY • light-weight notification library • using inotify mechanism • alert filesystem event • doesn't support data delivery, just send event notification. • To send event with data like integer, string, use DBus for IPC. • simple mechanism • make inotify fd for specific name • subscribe for specific name • sender publishes notification • App notifies and handles notification

19. ss_sysnoti • Send event into system-server • Enable run_queue (in system-server) to handle the event from proper handler • Using socket communication • /libslp-sysman • Helper library to notify the message to system-server • sysnoti.c • sysnoti_send(msg): send socket msg into /tmp/sn • sysman_call_predef_action(): request into system-server to run predefined function for the event

20. vconf (framework/appfw/vconf) • Key-value fair + inotify • Various functionality than heynoti • Store system configuration using SQLite (libsqlfs) • Able to communicate between inter-process using inotify

21. dbus • Inter-process communication mechanism using socket • Using Dbus daemon, App (or process) can send message into other App (or process) • Access control using SMACK

22. libdevice-node • Library that manages device node for each device in system • Not only real device, sysfs node also can be managed. • Add device node into device list, and register the callback function for get and set request  OAL Interface Function • device_get_property • Get device information (through corresponding OAL interface function) • device_set_property • Set device status (or command)(with OAL interface function) • OAL Interface • libslp_devman_plugin.so • System developer should make OAL Interface library for each system devices

23. Sensor Framework • Types of Sensors • Sensor plugins retrieve data from sensor hardware and enable the client applications to use the data • Tizen supports individual plugin frameworks for these sensors: • Accelerometer sensor • Gyroscope sensor • Proximity sensor • Motion sensor • Geomagnetic sensor • Light sensor • Gravity sensor • Orientation sensor • Pressure sensor • Etc

24. Sensor details • Accelerometer sensor • The accelerometer sensor is used to measure the acceleration of the device. The three dimensional coordinate system is used to illustrate the direction of the acceleration. When a phone is moving along an axis, the acceleration is positive if it moves in a positive direction. • Gyroscope sensor • A gyroscope is a device used primarily for navigation and measurement of angular velocity. Gyroscopes measure how quickly an object rotates. This rate of rotation can be measured along any of the three axes X, Y, and Z. • Proximity sensor • A proximity sensor can detect the presence of nearby objects without any physical contact. That is, it indicates if the device is close or not close to the user. • Motion sensor • A motion sensor is a virtual sensor that uses the accelerometer and gyroscope sensors. Motion sensor detects snap, panning, tilt, shake, overturn, and double tap event. • Geomagnetic sensor • A geomagnetic sensor indicates the strength of the geomagnetic flux density in the X, Y, and Z axes. This sensor is used to find the orientation of a body, which is a description of how it is aligned to the space it is in.

25. Sensor details • Light sensor • A light sensor measures the amount of light that it receives or the surrounding light conditions. The ambient light state is measured as a step value, where 0 is very dark and 10 is bright sunlight. • Gravity sensor • The gravity sensor is originated from the 3-axis acceleration sensor. It calculate gravity vector based on measured data of 3-axis acceleration sensor. The gravity sensor outputs 4 values: 3 Cartesian axis values and a timestamp.   • Orientation sensor • The Orientation sensor can determine three angular positions (Azimuth / Pitch / Roll). It is consist of the 3-axis accelerometer sensor and 3-axis magnetic sensor • Pressure sensor • The pressure sensor measures pressure, typically the pressure of gases or liquids. The measurement unit is hPa. The min value is 260 hPa and the max value is 1260 hPa.

26. Sensor Framework details • Components of Sensor Framework • Sensor Server • A daemon which communicates uniquely to sensor drivers in the system and dispatches sensor data to the application. • Takes care of interacting with the sensor driver in hardware initialization, driver configuration, and data fetching, to manage all sensors on the platform. • Sensor Client Library • The application that wants to access the sensor service should communicate with the server through the sensor API library. • Allows the application to access the sensor service. • Sensor Plugins • Retrieve data from sensor hardware and enable the client applications to use the data for specific requirements. • Take care of interacting with the sensor driver. • Process data from sensor drivers and communicate it to the sensor server.

27. Sensor Framework details • Interfaces of sensor plugins in sensor framework • Sensor_base • Connect the sensor plugin to the sensor server • Physical_sensor • Pushes sensor event from the plugin to the server event queue. • Sensor_hal • Configure sensor driver and read raw sensor data from the sensor driver. • Type of sensor plugins • Hardware sensor • Sensor_base + physical_sensor + sensor_hal • Virtual sensor • Sensor_base + virtual_sensor

28. Sensor Data Acquisition • Sensor Data Acquisition • How to acquire sensor data from device and notify sensor event of application • Sensor Data Acquisition Policies • Polling: ~Tizen 2.2 • Event-driven: Tizen 2.3

29. Sensor Data Acquisition: Polling • Application requires sensor data of server periodically. • Used up to Tizen 2.2 • Problem • Sensor data requests for each application→ Too many kernel-device interactions→ Sensor event drop occur

30. Sensor Data Acquisition: Event-driven • Application only register sensor event handler on server • Used from Tizen 2.3 • Sensor event drop problem resolved • Kernel-device interaction is decreased • Problem • Every registered sensor event handlers are called • → Increased IPC, Decreased CPU idle time • cf. • Batching in Android 4.4~, • Model-driven in BraceForce

31. App Framework

32. App Framework Overview

33. Tizen Core Application Types • UI Application • Application with UI (GUI) • Developed using EFL + Core APIs • Service Application • Applications without UI • Developed using Ecore (+α) + Core APIs

34. Appcore • Appcore is the application core handling various important events each of which application should be ware of. • Using appcore, developers can • Manage application life-cycle • Create, Reset, Pause, Resume, Terminate • Handle System Events • Low Memory • Low Battery • Screen orientation Change • Language & Region Change

35. Appcore Internal callback

36. Appcore AUL Handler • Appcore registers default internal AUL handler in initialization appcore/appcore.c

37. Using appcore • Include appcore-common.h or appcore-efl.h • fill appcore_ops for proper function pointers • call appcore_efl_main when using EFL appcore/appcore-common.h appcore/appcore-efl.c

38. Application Life Cycle: State and Transitions

39. Tizen GUI App Structure

40. Application Utility Library: AUL • Application Utility Library (AUL) provides the following features • Launching/terminating applications • Providing running application information • AUL consists of the following sub-components: • AUL library: Sending/receiving requests for launching and terminating • AUL daemon (a.k.a. launch pad): Handling the requests • Open socket file • wait for recv() at __launchpad_main_loop aul/launchpad.c

41. AUL: Launch • In case of single-instance application • If app is not running, launch application • If app is already running, send reset event to the running application • In case of multi-instance application • launch an app • _launchpad_main_loop()handles launch event aul/launchpad.c

42. App to Launchpad aul/launch_app.c aul/launch.c

43. AUL Overall Architecture • Application provides APN(application package name) to launch. • Unix Domain Socket is used to send events between launchpad and applications. • Launchpad daemon is responsible for setup default configuration of application. • DB is used to store / retain default configuration of application.

44. App Service (high-level App Launcher) • App service exposes general service terms, such as view, create, call, and so forth, to developers in case of launching an application with a specific feature • More desirable asking image view service without knowing what image viewer apps are available. • Each service can be determined by given operation, URI and MIME type. • Operation: expected action for the request (e.g., view, edit, call, send..) • URI: URI information for requested operation (e.g., http://... file://...) • MIME type: MIME type information for requested operation (e.g., image/jpeg) • Data: Extra data to launched service application(contained in a bundle packet)

45. App Service Overall Flow

46. App Service Request

47. Application Data Exchange • The actual Application Data Exchange (ADE) occurs as an argument between the caller and callee, using a bundle. • Bundle is a type of dictionary abstract data, in which information is stored as key-value pairs. • Bundle contains information regarding the state the app should prepare.

48. Package Manager • Package manager is responsible for installing, upgrading and uninstalling of applications and storing their information. • Expandable structure to support various types of applications • Designated installation modules can be added to the manager • Web app, native app, java app, and so forth

49. Application Information Library: AIL • AIL is the library providing functionalities to execute application information-related tasks. • AIL provides the following features • Adding, updating and removing application information. • Managing application's information –application name, type, icon path, exec path, etc. • Retrieving an application list which meets a given filter.

50. App Use History: RUA • Recently Used Application (RUA) logs application use history. • When an application is launched, launch pad updates the history and task manager can either get or clear the history. • RUA also provides below information regarding launching: • package name • launch time • application path • application launch argument