Merge pull request #30 from kjokinie/master

Add proper call state handling for vibra.
[canberra] Don't use context uninitialized.
[canberra] Remove timeout if stopped before callback is called.
[canberra] Remove pause callback since we don't support it anyway.
Merge pull request #32 from jusa/dev

Updates to canberra plugin.
[profile] Support multiple sound.level values.

profile.ini is now configured with for example:

sound-levels = system.sound.level;foo.sound.level
system.sound.level = 0;50;75;100
foo.sound.level = 0;30;60;90
[mce] Better LED pattern management

LED patterns usually used to indicate that something happened while
the user was away from the device, so we can't simply blink the pattern
once for 100ms like it is done now.

We use two indicators of user activity to detect when the LED pattern
should be cleared:

 - When the display goes on and it wasn't because of the event that
   requested the pattern (FIXME: imperfect timeout heuristic)
 - When MCE reports user activity

Between these two there is assumed to be no gap or alternatively a screen
where the user can see what was the indication about, thus acknowledging
the LED pattern for clearing.

If the pattern is requested when the device is active, it is assumed that
it is ok to leave the pattern on until the next cycle of inactivity or
display state happens. In other words, application developers: don't request
LED patterns for missed events if the device is active.

Signed-off-by: Kalle Vahlman <kalle.vahlman@movial.com>
[settings] Update default config for profile plugin.
Merge pull request #33 from jusa/dev

Support multiple sound.level values.
Merge pull request #31 from kvahlman/led-pattern-management

plugins/mce: Better LED pattern management
Revert "[mce] Better LED pattern management"

This reverts commit 670cd55e9a179684674035fd6345842974e0b9c1.

The logic here proved to be inadequate in further testing, we cannot
catch all display on scenarios reliably since there is not enough
information available through the MCE signals.

To make this work properly, MCE needs to learn new tricks.
[mce] Let MCE clear patterns since it knows better when to do that

MCE can monitor user activity with more granularity than what we have
available in ngfd, so it's better to let it decide when the LED pattern
should be cleared.

Old functionality is available through 'mce.clear_pattern = true' property.

Signed-off-by: Kalle Vahlman <kalle.vahlman@movial.com>
Merge pull request #34 from kvahlman/mce-handles-leds

Mce handles leds
[canberra] Really cache samples with canberra plugin.

CA_PROP_CANBERRA_CACHE_CONTROL "permanent" needs to specified for play
proplist to really play cached samples. Also clear cached_samples hash
table if canberra context dies.
Merge pull request #35 from jusa/canberra

[canberra] Really cache samples with canberra plugin.
[actdead] ngfd is started also in ACTDEAD mode

Signed-off-by: Pekka Lundstrom <pekka.lundstrom@jollamobile.com>
Merge pull request #38 from nemomobile/plu

ngfd is started also in ACTDEAD mode
[mce] Don't consider the MCE sink done with an event if a LED pattern has been started and mce.clear_pattern is set to true to allow manual stopping
[haptic] Make haptic policy (settings, calls) reusable

Extract the settings and call handling from the ffmemless
plugin to a reusable function in haptic.{c,h} for use by
other plugins.
Merge pull request #41 from nemomobile/reusable-haptic-filter-rules

[haptic] Make haptic policy (settings, calls) reusable