| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
The sample application that achieves the interrupt policy management
But an applications on background sometimes can't get events.
I guess this is caused by WorkerThread on Qt(QML)
So, the sequence sometimes stops
Change-Id: I8008872ccb4c3c8d3f838095ded118fb5fdf6a6f
Signed-off-by: Kazumasa Mitsunari <kazumasa_mitsunari_za@mail.toyota.co.jp>
|
|
First version 2017/08/29
SoundManager consists of main 4 parts
1. doc
Document of sound manager and audio manager architecture
This describes application sequence
Please open ApplicationGuide.md with browser
2. include
Contains API of libsoundmanager
LibSoundmanager API is going to be modified, so please don't use for now
Update will be done in near future
3. soundmanager_binding
Contains soundmanager binding. This is the service midleware
If installing this, soundmanager is automatically launched by AppFW(systemd)
4. sample
Contains sample applications. These applications follow the AudioManager sequence and using soundmanager binding
Change-Id: I75b6c5c652e1dc00b39bc499a2ee6bf1e2aeaf6d
Signed-off-by: Kazumasa Mitsunari <kazumasa_mitsunari_za@mail.toyota.co.jp>
|
|
This document describes Audio Manager usecase and architecture
To see the document, open ApplicationGuide.md with firefox and so on
(Markdown should be enabled with plugin of the browser)
From the view of the applications, the sequence is the most important point
ApplicationGuide may be updated according to any feedbacks
Change-Id: Ifc17a4bd0d7efb0d4beb3f45c400f169abd81d68
Signed-off-by: Kazumasa Mitsunari <kazumasa_mitsunari_za@mail.toyota.co.jp>
|
|
|
