1. 24 Oct, 2019 1 commit
    • spiiroin's avatar
      [fingerprint] Use gesture actions for fingerprint wake up. Fixes JB#47437 · 64e71c69
      spiiroin authored
      Originally fingerprint wake up was modeled to:
      - wake up display like double tap does
      - exit from lockscreen when device is not locked, or
      - indicate need to unlock when device is locked
      i.e. behave as if double power key press were made.
      
      This however means that fingerprint wake up never ends up showing
      lockscreen where things like date and time would be visible.
      
      Switch from handling fingerprint wake up as something explicit into
      treating it as just another gesture with configurable actions.
      
      Add "tkunlock2" gesture action, which behaves like "tkunlock" when
      device is unlocked and does nothing when device is locked.
      
      After which users can tweak fingerprint behavior with mcetool.
      
      mcetool --set-touchscreen-gesture-actions=fpwakeup,unblank,tkunlock
      
        The default behavior.
      
      mcetool --set-touchscreen-gesture-actions=fpwakeup,unblank,tkunlock2
      
        Exits from lockscreen only if device is not locked.
      
      mcetool --set-touchscreen-gesture-actions=fpwakeup,unblank
      
        Just wakes up display, leaving lockscreen status as it is.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      64e71c69
  2. 15 Mar, 2019 1 commit
    • spiiroin's avatar
      [proximity] On-demand proximity sensor activation. Fixes JB#34789 MER#1562 · d9c917b7
      spiiroin authored
      MCE code has built-in assumption that proximity sensor is either not used at
      all, or it is constantly powered on. The former basically means that in-call
      proximity blanking is not available. And the latter can cause direct (the
      sensor itself) or indirect (might block suspend) power drain, or make it
      more likely for lower level sensor handling glitches to surface.
      
      Make it possible to select on-demand proximity sensor activation.
      
      When selected, proximity sensor is powered up:
      - While the device in a state where it might be needed (calls, alarms, etc).
      - When events that could lead to display wakeup are received (powerkey
        presses, doubletaps, etc).
      
      As the sensor state is not available immediately after requesting
      sensor powerup, implement on-proximity action queue which can be used
      to schedule actions to be taken when the sensor has reached a stable
      state.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      d9c917b7
  3. 20 Nov, 2018 1 commit
  4. 02 Nov, 2018 1 commit
    • spiiroin's avatar
      [led] Add proximity sensor debugging patterns. JB#43690 · 5667900c
      spiiroin authored
      Debugging proximity sensor issues is difficult as inspecting logs is
      usually not possible in the situation where the problem is detected,
      or the sensor has failed in distant enough past so that logs have been
      already lost due to log rotation.
      
      Add led patterns that are activated/deactivated as follows:
      - PatternProximityCovered when sensor is reporting closed state.
      - PatternProximityUncovering when sensor is reporting uncovered state, but
        effective state is still covered (uncover hysteresis).
      - PatternProximityUncovered when effective proximity state is uncovered.
      
      The patterns are disabled by default, but can be enabled via:
        mcetool --enable-led-pattern=PatternProximityCovered\
                --enable-led-pattern=PatternProximityUncovering\
                --enable-led-pattern=PatternProximityUncovered
      
      And disabled again with:
        mcetool --disable-led-pattern=PatternProximityCovered\
                --disable-led-pattern=PatternProximityUncovering\
                --disable-led-pattern=PatternProximityUncovered
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      5667900c
  5. 18 Sep, 2018 1 commit
  6. 15 Aug, 2018 1 commit
    • spiiroin's avatar
      [fingerprint] Add support for debug led patterns · 7f395b61
      spiiroin authored
      There are no visible clues for fingerprint authentication being
      possible / activated. This makes it difficult to differentiate between
      situations where fingerprint scanner has not been activated and lower
      lever functionality having problems with fingerprint acquisition.
      
      To ease debugging, add led patterns for lighting up the led in yellow
      color when fingerprint scanner is active and briefly turning the led
      blue on fingerprint acquisition events.
      
      These led patterns are not used by default, user must opt-in via:
        mcetool --enable-led-pattern=PatternScanningFingerprint
        mcetool --enable-led-pattern=PatternFingerprintAcquired
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      7f395b61
  7. 16 Mar, 2018 1 commit
  8. 01 Mar, 2018 1 commit
  9. 23 Feb, 2018 1 commit
  10. 30 Mar, 2017 1 commit
    • spiiroin's avatar
      [settings] Avoid internal recursion and ensure external notification · 512a96ae
      spiiroin authored
      When a setting key is changed via D-Bus interface, the value requested
      might get filtered by the mce side logic tracking the setting. If the key
      gets changed back to the original value, no change notification signal
      is emitted and clients can get out of sync with reality.
      
      When a key value changes, make sure a dbus notification for the key is
      emitted even if the value gets changed back to the original value.
      
      To avoid internal ringing, do not call internal change notifiers when a
      key is set to the same value as it is already holding.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      512a96ae
  11. 31 Mar, 2016 3 commits
  12. 21 Mar, 2016 1 commit
    • spiiroin's avatar
      [event-input] Enable doubletap emulation by default. Fixes JB#34610 · 16b4970f
      spiiroin authored
      Originally the disable/enable toggle could be used for enabling double
      tap detection even in display on states - this is because the feature
      was developed primarily with sdk and mouse double clicks in mind.
      
      Later the same detection logic was used for handling double taps that
      happen in lpm display states where hw gesture detection is not available.
      In these cases the enable/disable setting was in practice ignored.
      
      While fixing the double tap detection during display power off sequence,
      I accidentally changed the logic so that it requires
        touch grabbed && setting enabled
      instead of the original
        touch grabbed || setting enabled
      
      Since the new behavior actually makes more sense, fix the setting value
      so that double tap emulation is enabled by default.
      16b4970f
  13. 17 Mar, 2016 1 commit
    • spiiroin's avatar
      [leds] Disable DisplayDimmed led pattern by default. Fixes JB#34543 · 5a1d33cf
      spiiroin authored
      Before compositor side dimming was implemented, it was very hard to
      spot display dimming while the device was in low light conditions.
      To avoid display blanking without any notice, a pale blue led color
      was used as about-to-blank-screen indicator.
      
      With compositor blending graphics on screen towards black, the
      display dimming is always visually detectable and we can disable
      the DisplayDimmed led pattern as it seems to be more confusing
      rather than helpful.
      
      Anyone who still would like to have the led effect, can use
        mcetool --enable-led-pattern=PatternDisplayDimmed
      to restore the old behavior.
      5a1d33cf
  14. 07 Mar, 2016 1 commit
    • spiiroin's avatar
      [powerkey] Add enablers for configuring touchscreen gestures. Fixes MER#1537 · 9fe42f8b
      spiiroin authored
      Traditionally the only touchscreen gesture that has been able to wake
      the device from suspend has been the double tap. Now there are devices
      that support more gestures for waking up the device, but there are no
      means to differentiate / configure actions taken based on the various
      gestures.
      
      MCE already assumes EV_MSC:MSC_GESTURE event with value 4 is double tap.
      Extend on this and assume that also other gestures get reported in the
      similar fashion.
      
      Move gesture event handling from tklock.c to powerkey.c.
      
      Drop support for double tap setting and make gesture actions configurable
      similarly to what can be done with power key presses.
      
      Increase the number of user configurable dbus actions to 10. Tweak the
      related mcetool options so that instead of N similar but separate
      options (--set-powerkey-dbus-actionN=args) there is just one that takes
      action index as the first parameter (--set-powerkey-dbus-action=N,args).
      
      Add mcetool --set-touchscreen-gesture-actions options for configuring the
      gesture actions. Retain the old --set-doubletap-mode as an alias for the
      sake of backwards compatibility.
      9fe42f8b
  15. 07 Jan, 2016 1 commit
    • spiiroin's avatar
      [input] Add setting to allow/deny input device grabbing. JB#33644 · 0fa25544
      spiiroin authored
      Grabbing touch input events is problematic - especially with devices
      that use stateful protocol B for reporting. In general it would be better
      to allow lipstick to see all the touch events but ignore them while
      display is not in fully powered up state.
      
      Add a setting that can be used to instruct mce not to grab touch input
      device nodes. By default the grabbing is allowed.
      
      Normally platform specific configuration files are expected to be used
      when needed, but users can also tweak the setting via mcetool option
      --set-input-grab-allowed.
      0fa25544
  16. 11 Nov, 2015 1 commit
    • spiiroin's avatar
      [tklock] Add setting for lid is closed als limit. Fixes JB#33468 · 7cd25190
      spiiroin authored
      The light level limit used for filtering lid opened/closed events is hard
      coded - which makes it impossible to specify platform specific values.
      
      Add setting for the light level limit. By default it is assumed that
      ALS will report zero lux in complete darkness.
      
      Configuration files can be used to provide platform specific default.
      
      Users can - if necessary - users tweak the limit mcetool option:
        --set-filter-lid-als-limit=<lux>
      
      The value of the setting persists over mce / device restarts.
      7cd25190
  17. 30 Sep, 2015 3 commits
    • spiiroin's avatar
      [tklock] Add setting for tweaking volume key input policy. Contributes to JB#31567 · 3ff05a55
      spiiroin authored
      A lot of users think that volume keys should be reserved for adjusting
      media volume only.
      
      While it is not yet possible to adjust how ui interprets volume key
      presses, we can stop ui from getting any unless there is ongoing music
      playback and thus effectively limiting volume keys to only adjusting
      media volume.
      
      Add setting for selecting volume key input policy. By default the volume
      keys work just as before, but this can be changed via mcetool option:
        --set-volume-key-policy=<default|media-only>
      
      The value of the setting persists over mce / device restarts.
      3ff05a55
    • spiiroin's avatar
      [tklock] Add setting for disabling unblank to lockscreen animation. Contributes to JB#30849 · eae505cb
      spiiroin authored
      A lot of users think the animated unblank to lockscreen is too slow.
      
      While there is at present no way to directly control the animation that
      happens on the ui side, it does get implicitly disabled when display is
      unblanked due to alarms/calls/notifications. Utilize this and optionally
      fake notification unblank when a double tap or power key press is used
      to wake up the device.
      
      Add setting for enabling/disabling lockscreen unblank animations.
      
      By default the animations are enabled, but this can be changed via
      mcetool option:
        --set-lockscreen-animation=<enabled|disabled>
      
      The value of the setting persists over mce / device restarts.
      eae505cb
    • spiiroin's avatar
      [display] Add setting for dim timeout with hw keyboard available. Fixes MER#1321 · 6b3faedd
      spiiroin authored
      There are users that wish that the display would stay on longer when
      a hw keyboard is attached / slider keyboard is open.
      
      Add separate dim-timeout setting that is used when keyboard is available.
      Setting it to zero value means: Use the regular dim-timeout even if a hw
      keyboard is available.
      
      By default the value is set to zero. This can be changed by installing
      configuration files to /etc/mce directory or with mcetool option:
        --set-dim-with-kbdtimeout=<secs>
      
      The value of the setting persists over mce / device restarts.
      6b3faedd
  18. 29 Sep, 2015 1 commit
    • spiiroin's avatar
      [display] Add setting for kbd slide inhibit mode. Contributes to MER#1321 · 4af454d9
      spiiroin authored
      There are users that wish that the display would not blank when keyboard
      slide is in open state.
      
      Add inhibit mode setting that can be used to disable dimming / blanking
      blanking timers when kbd slide is in open position.
      
      By default kbd slide status does not affect display blanking timers.
      
      The default can be changed by installing configuration files to
      /etc/mce directory or via mcetool option:
        --set-kbd-slide-inhibit-mode=<disabled|stay-on-when-open|
                                      stay-dim-when-open>
      
      The value of the setting persists over mce / device restarts.
      4af454d9
  19. 25 Sep, 2015 1 commit
    • spiiroin's avatar
      [tklock] Add settings for tuning keyboard slide open/close policy. Contibutes to MER#1321 · 5752168d
      spiiroin authored
      Many users wish to tweak what happens when sliding keyboard is opened
      or closed, but reaction to keyboard slide events is hard coded in mce.
      
      Add settings for controlling when and how mce should react to keyboard
      slide open/close events.
      
      The default behavior is not changed, mce still does on slide
        * open: unblank display - if proximity sensor is not covered
        * close: blank and activate lockscreen - if display was unblanked
          due to keyboard slide open
      
      The defaults can be changed by installing configuration files to
      /etc/mce directory or via mcetool options:
        --set-kbd-slide-open-trigger=<never|no-proximity|always>
        --set-kbd-slide-open-actions=<disabled|unblank|tkunlock>
        --set-kbd-slide-close-trigger=<never|after-open|always>
        --set-kbd-slide-close-actions=<disabled|blank|tklock>
      
      The values of the settings persists over mce / device restarts.
      
      Also make sure closing keyboard slide does not blank the display when
      there are active alarms or calls as it might interfere with display
      state handling in a situation where power key can't be used to bring
      the display back on.
      5752168d
  20. 18 Sep, 2015 1 commit
    • spiiroin's avatar
      [orientation] Add options for tweaking orientation sensor usage. Fixes MER#1331 · ef1ba81a
      spiiroin authored
      Some users would prefer to stop orientation changes from keeping
      the display on. While it is possible to make this happen by disabling
      orientation sensor usage, this also stops flipover gestures from
      silencing calls/alarms.
      
      Add separate settings for "orientation change is activity" and
      "flipover gesture detection". If the already existing orientation
      sensor master toggle is set to disabled, the feature specific
      settings are ignored.
      
      By default all three settings are enabled, and can be modified via
      mcetool options:
        --set-orientation-change-is-activity=<enabled|disabled>
        --set-flipover-gesture-detection=<enabled|disabled>
        --set-orientation-sensor-mode=<enabled|disabled>
      
      The values of the settings persists over mce / device restarts.
      
      Also do light refactoring of sensor-gestures plugin.
      ef1ba81a
  21. 19 Aug, 2015 1 commit
    • spiiroin's avatar
      [tklock] Add setting to disable input device grabbing. Fixes MER#1250 · ccc324d6
      spiiroin authored
      There have been issues with unresponsive touch screen in various porting
      projects. It is difficult to tell whether problems occur because
      
      a) mce is denying touch events from reaching ui, or
      b) ui side does not process touch events as expected
      
      To ease debugging of such issues, add a setting that can be used to
      control whether mce is allowed to grab input devices or not.
      
      The setting is enabled by default and can be changed with:
      
        mcetool --set-input-policy-mode=<enabled|disabled>
      
      The value of the setting persists over mce / device restarts.
      ccc324d6
  22. 09 Aug, 2015 1 commit
    • spiiroin's avatar
      [display] Add configurable dimming settings. Contributes to JB#31214 · f92d7f5f
      spiiroin authored
      Depending on things like linearity of display backlight brightness control
      and use of content adaptive backlight algorithms it might happen that
      display dimming via reducing backlight level does not produce difference
      that is clear enough to human eye.
      
      MCE and lipstick already have logic in place for doing dimming by fading
      graphics on the compositor level when backlight level difference between
      display on and display dimmed states is too low.
      
      Add low threshold for compositor side dimming and linearly increase the
      compositor side dimming when backlight level difference is in between the
      low and high thresholds.
      
      Add settings for values used in evaluating dimming backlight level and
      compositor side dimming thresholds.
      
      By default use values that match behavior that was previously hard coded:
       * static dimmed backlight level = 3 % of the hw maximum
       * dynamic dimmed backlight level = 50 % of display on brightness
       * low compositor fading threshold = disabled
       * high compositor fading threshold = 10 % of the hw brightness range
      
      Changes to defaults can be made by installing configuration files to
      /etc/mce directory and/or while mce is running via mcetool options:
      
            --set-dimmed-brightness-static=<1...100>
            --set-dimmed-brightness-dynamic=<1...100>
            --set-compositor-dimming-threshold-hi=<0...100>
            --set-compositor-dimming-threshold-lo=<0...100>
      
      The values of the settings persists over mce / device restarts.
      f92d7f5f
  23. 05 Aug, 2015 1 commit
    • spiiroin's avatar
      [tklock] Add setting for lid open/close actions. Fixes MER#1202 · a69dd713
      spiiroin authored
      The actions taken when lid sensor indicates that cover is closed or opened
      are hard coded without any possibility for users to tweak the behavior.
      
      Add settings for tweaking of actions to taken when cover is closed:
        * disabled - do nothing
        * blank    - just turn off the display
        * tklock   - turn off display and activate lockscreen
      
      Default is 'tklock' and can be changed via:
        mcetool --set-lid-close-actions=<disabled|blank|tklock>
      
      
      Add settings for tweaking of actions to taken when cover is opened:
        * disabled - do nothing
        * unblank  - just turn on the display
        * tkunlock - turn on display and deactivate lockscreen (if possible)
      
      Default is 'unblank' and can be changed via:
        mcetool --set-lid-open-actions=<disabled|unblank|tkunlock>
      
      The values of the settings persists over mce / device restarts.
      a69dd713
  24. 04 Aug, 2015 1 commit
    • spiiroin's avatar
      [proximity] Optionally make proximity sensor behave like lid sensor. Fixes MER#1201 · 05e2ff1c
      spiiroin authored
      On devices that have a lid cover sensor, mce uses it for turning the
      display on/off when the cover is opened/closed. On devices that do not
      have a dedicated lid sensor, users might prefer using proximity sensor
      for that purpose even if it has some side effects.
      
      Add a setting for making mce treat proximity sensor act as if were
      a lid sensor.
      
      The setting is disabled by default and can be changed with:
      
        mcetool --set-ps-acts-as-lid=<enabled|disabled>
      
      The value of the setting persists over mce / device restarts.
      05e2ff1c
  25. 30 Jul, 2015 1 commit
    • spiiroin's avatar
      [display] Add setting for blanking pause mode. Fixes JB#27486 · bb134908
      spiiroin authored
      Usually navigation applications use blank prevent to keep display on.
      Sometimes - say when navigating while driving with bike - it might
      be desirable to still allow display to dim (or blank) to save battery.
      
      Add setting for controlling blank prevent handling to make it possible
      to allow display to dim or even blank while application is using blank
      prevention D-Bus interface.
      
      The supported modes are:
      
        * keep-on: blank prevent sessions keep the display on as before
        * allow-dim: display can be dimmed even if blank prevent is used
        * disabled: display can be blanked even if blank prevent is used
      
      By default the "keep-on" mode is used and blank prevention works just
      like it did before the changes. The mode can be changed via:
      
        mcetool --set-blank-prevent-mode=<disabled|keep-on|allow-dim>
      
      The value of the setting persists over mce / device restarts.
      bb134908
  26. 16 Jun, 2015 1 commit
    • spiiroin's avatar
      Allow fine tuning ALS usage via mce settings · 41f1e2e1
      spiiroin authored
      MCE has one setting that dictates whether ambient light sensor is used
      or not. This was ok as long as ALS was used only for display brightness
      tuning, but now that there are other reasons for using ALS functionality
      of those too depend on whether automatic brightness tuning is in use or
      not.
      
      Leave the existing setting in place, use it as ALS master toggle and
      add separate settings for:
      - Use ALS automatic display brightness tuning
      - Use ALS for filtering false positive lid closed events
      
      If the master toggle is set to disabled, ALS is not used by mce.
      
      If the master toggle is set to enabled, ALS is powered up/down depending
      on feature specific settings and device state.
      
      Refactor ALS data processing so that:
      - callback for passing lux value from sensorfw uses int, not unsigned int
      - als power up depends on all three settings
      - variables holding cached lux values are given more descriptive names
      - all auto brightness filters use similar logic for testing whether the
        feature is enabled & als data is available
      - move all constants related to display settings to display.h
      
      ALS data is used for filtering out potential false positive lid close
      events only if the relevant settings are enabled.
      
      Options for mcetool:
        --set-als-mode=<enabled|disabled>
        Now works as use als master toggle.
      
        --set-als-autobrightness=<enabled|disabled>
        Can be used to disable automatic brightness tuning even if using ALS
        is otherwise enabled.
      
        --set-filter-lid-with-als=<enabled|disabled>
        Can be used to disable lid close filtering even if using ALS is
        otherwise enabled.
      
      [mce] Allow fine tuning ALS usage via mce settings. Fixes JB#29892
      41f1e2e1
  27. 12 May, 2015 1 commit
    • spiiroin's avatar
      Add settings for exceptional display on state durations · 98e015d9
      spiiroin authored
      Certain triggers like incoming call, alarm, usb connect, volume key
      press, etc can cause the display to be turned on briefly. Many users
      wish to tweak display on time following some triggers, but the durations
      are hard coded.
      
      Replace all hard coded durations with settings that can be changed
      at run-time.
      
      Allow disabling of individual triggers by setting zero duration.
      
      Add mcetool options for changing the settings and showing the current
      values.
      
      [mce] Add settings for exceptional display on state durations. Fixes JB#27426
      98e015d9
  28. 05 May, 2015 1 commit
    • spiiroin's avatar
      Add setting for enabling/disabling orientation sensor use · 0e9f8b42
      spiiroin authored
      If orientation sensor is available, mce uses it for generating user
      activity (delay automatic display blanking) and detecting device flip
      over gestures (snooze alarm, silence incoming call). Sometimes neither
      feature is desired, but there is no way to disable use of orientation
      sensor.
      
      Add disable/enable setting for using orientation sensor.
      
      By default the setting is enabled, but can be changed for example by
      installing hw specific mce configuration files or from command line
      
        mcetool --set-orientation-sensor-mode=<enabled|disabled>
      
      The setting persists over mce/device restarts.
      
      [mce] Add setting for enabling/disabling orientation sensor use. Fixes JB#27427
      0e9f8b42
  29. 24 Apr, 2015 1 commit
    • spiiroin's avatar
      Add setting for ignoring lid/cover sensor · 1909bbaf
      spiiroin authored
      If mce find that a device has lid/cover sensor, it is used as a very
      high priority input for display blanking policy. It might be desirable
      to stop this from happening if for example:
      - user does not like the feature
      - mce input device probing produces a false match
      - the sensor is unreliable and makes using the device difficult
      - we want to keep the display on during sensor testing activities
      
      Add disable/enable setting for using lid/cover sensor.
      
      By default the setting is enabled, but can be changed for example by
      installing hw specific mce configuration files or from command line
      
        mcetool --set-lid-sensor-mode=<enabled|disabled>
      
      The setting persists over mce/device restarts.
      
      [mce] Add setting for ignoring lid/cover sensor. Fixes JB#28108
      1909bbaf
  30. 16 Mar, 2015 1 commit
    • spiiroin's avatar
      Add setting for autolock delay length · 147875a8
      spiiroin authored
      When the display blanks automatically via dimming, the autolock is
      not applied immediately. During this so called grace period users can
      get back to the app that was active before display was blanked.
      
      While having this grace period is useful from user's point of view,
      it also means applications do not get backgrounded and thus stay in
      active state - which can cause issues. The hardcoded 30 second grace
      period is a compromise between these conflicting needs.
      
      Making the length of the grace period changeable at runtime allows users
      to choose which of the two is more important for them.
      
      Default stays at 30 seconds, but can be changed via:
        mcetool --set-autolock-delay=<seconds[.fraction]>
      
      [mce] Add setting for autolock delay length. Fixes NEMO#787
      147875a8
  31. 15 Mar, 2015 2 commits
    • spiiroin's avatar
      Add option to ignore tklock removal while device lock is active · 5d25a308
      spiiroin authored
      The tklock status more or less equals "lockscreen is active". And
      removing tklock switches from lockscreen to home/app view. This
      is problematic if device unlocking should happen in the context of
      the lockscreen as power key actions / random tklock request from
      applications could effectively bypass the device lock.
      
      Add configuration setting "devicelock is in lockscreen". While the
      setting is enabled, mce will not allow removal of tklock while
      device lock is active.
      
      By the default the setting is disabled.
      
      Changing the setting should happen via installing configuration file
      to /etc/mce directory if (and only if) the ui side actually implements
      device unlocking within lockscreen.
      
      The option can also be toggled via mcetool. But since inappropriate
      use can make the device unlockable from ui, the mcetool option is
      flagged as dangerous and interactive confirmation is required.
      
      [mce] Add option to ignore tklock removal while device lock is active. Fixes JB#26525
      5d25a308
    • spiiroin's avatar
      Use mce_gconf_track_xxx() helpers in tklock module · 0bf71f26
      spiiroin authored
      Using helper functions for getting initial setting value and installing
      change notifier callback allows bit more compact code and makes it a bit
      more difficult to make obvious errors.
      
      Initialize fallback values from named constants. When possible use
      the same constants to initialize also the built-in config defaults.
      
      No functional changes.
      0bf71f26
  32. 14 Mar, 2015 1 commit
    • spiiroin's avatar
      Remove SoftOff mode · b6d161ea
      spiiroin authored
      SoftOff mode is basically manual suspend to RAM for pre N900 era maemo
      devices. The logic in MCE side does not work and also support needed by
      it has beed dropped from DSME side ages ago.
      
      Remove all remnants of SoftOff mode that still linger in mce code tree.
      
      [mce] Remove SoftOff mode. Fixes JB#27285
      b6d161ea
  33. 19 Feb, 2015 1 commit
    • spiiroin's avatar
      Make all blanking timeouts separately configurable · f2713205
      spiiroin authored
      We'd like to have different delays when blanking from application/home
      view (ON->DIM->OFF, relatively short delay) vs blanking from lockscreen
      (ON->OFF, give user some time to interact with the gui). Also it might
      be desirable to have better control over ON->LPM_ON->LPM_OFF->OFF
      transitions. Now LPM_OFF delay is hard coded and the rest use the same
      configuration setting.
      
      Provide separate blanking delay settings to use from:
      * application/home screen after dimming (default 3 seconds)
      * lockscreen (default 10 seconds)
      * visual low power mode (default 5 seconds)
      * blanked low power mode (default 5 seconds)
      
      The defaults can changed by installing config files to /etc/mce.
      
      And tweaked during runtime via D-Bus or mcetool options:
        --set-blank-timeout=<secs>
        --set-blank-from-lockscreen-timeout=<secs>
        --set-blank-from-lpm-on-timeout=<secs>
        --set-blank-from-lpm-off-timeout=<secs>
      
      The changes made during runtime persist over mce/device restarts.
      
      Also make sure the inactivity timeout is re-evaluated when parameters
      it depends on are changed.
      
      [mce] Make all blanking timeouts separately configurable. Fixes JB#26550
      f2713205
  34. 18 Feb, 2015 2 commits
    • spiiroin's avatar
      Provide fallback values dim timeouts setting and track changes · ea8e6d97
      spiiroin authored
      No change notification for dim timeouts setting was installed, which
      meant change did not get effective without mce restart. Also no
      fallback values were provided in case the config item is not available.
      
      Use common defaults for built-in config and fallback values.
      
      If dim timeouts setting changes, adjust related state variables
      and reprogram blanking timers.
      
      [mce] Provide fallback values dim timeouts setting and track changes. Contributes to JB#26550
      ea8e6d97
    • spiiroin's avatar
      Do not use hardcoded defaults for display plugin settings · bf406e74
      spiiroin authored
      The default and fallback values for settings should match. Having
      both of them hard coded makes it too easy to get them out of sync.
      
      Initialize fallback values from named constants. When possible use
      the same constants to initialize also the built-in config defaults.
      
      No functional changes.
      
      [mce] Do not use hardcoded defaults for display plugin settings. Contributes to JB#26550
      bf406e74