1. 17 May, 2019 1 commit
    • spiiroin's avatar
      [mce] Unify license blurbs. JB#33684 · 091d6e7e
      spiiroin authored
      MCE uses LGPL v2.1 (without "or later") license, but due to missing / use
      of different license blurbs this is not always clear enough.
      
      Replace blurbs referring to "LGPLv2" short form which could be either
      LGPL v2.0 or v2.1 without "or later" with the same blurb that is used
      in mce.c file.
      
      Similarly add blurb to source files that are missing one altogether.
      
      Add all authors that can be derived from git logs.
      
      Update Jolla Ltd. copyright statements to match git activity.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      091d6e7e
  2. 23 Jan, 2019 1 commit
  3. 01 Mar, 2018 1 commit
  4. 23 Feb, 2018 1 commit
  5. 18 Nov, 2017 1 commit
  6. 31 Mar, 2016 2 commits
  7. 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
  8. 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
  9. 30 Sep, 2015 2 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
  10. 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
  11. 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
  12. 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
  13. 23 Jun, 2015 1 commit
    • spiiroin's avatar
      Make display blank faster after dismissing an alarm · 607d3137
      spiiroin authored
      Having display stay on 2.5 seconds after dismissing an alarm was
      felt too long by many users. Also since power key is reserved for
      snoozing alarm until the dialog is gone, people have learned a
      habit of repeatedly pressing the power key until display actually
      blanks - which can trigger reset proximity state via triple power
      key press.
      
      Shorten the display on time after alarm to 1.25 seconds.
      
      Users that are not pleased with the new default value can use
      mcetool to select a custom time value - for example 1 second:
      
        mcetool --set-exception-length-alarm=1000
      
      [mce] Make display blank faster after dismissing an alarm. Fixes JB#28552
      607d3137
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 13 Mar, 2015 1 commit
    • spiiroin's avatar
      Remove unused mce.ini configuration items · 9545acf7
      spiiroin authored
      During the evolution of mce it has repeatedly happened that code for
      some features has disappeared, but the related config items, macros
      and in some cases even variables remain littering the source tree.
      
      Remove all ini-file based configuration items, defines and variables
      that are not actually used in the code.
      
      [mce] Remove unused mce.ini configuration items. Fixes JB#25531
      9545acf7
  20. 30 Jan, 2015 1 commit
    • spiiroin's avatar
      Make touch input blocking by proximity sensor optional · 979d3376
      spiiroin authored
      Many users have had problems with touch input immediately after bootup.
      It is verly likely that it is caused by touch input getting blocked
      by the proximity sensor. Since there is not yet visual clues about the
      fact that it is happening, the users have no way of knowing what is
      happening and how to remedy the situation.
      
      Also porting projects where sensor adaptation is not fully working
      have had trouble with this feature.
      
      Add setting for enabling/disabling touch blocking by proximity sensor.
      
      Disable the feature by default.
      
      The default can be changed via:
        mcetool --set-ps-blocks-touch=<enabled|disabled>
      
      [mce] Make touch input blocking by proximity sensor optional. Fixes JB#25467
      979d3376
  21. 24 Oct, 2014 1 commit
    • spiiroin's avatar
      Make unblank and unlock via double tap work again · 33978390
      spiiroin authored
      Legacy option to allow bypassing of lockscreen with doubletap was
      broken.
      
      Make it work again.
      
      Also do not use raw numeric values to evaluate doubletap_gesture_policy.
      
      [mce] Make unblank and unlock via double tap work again
      33978390
  22. 12 Aug, 2014 1 commit
    • spiiroin's avatar
      Add setting for selecting automatic lpm ui triggering modes · eb569a0d
      spiiroin authored
      Previously both "from-pocket" and "hover-over" proximity triggering
      was enabled implicitly when use_low_power_mode setting was enabled.
      The proximity sensor interaction needed for "hover-over" triggering
      can be confusing and disabling it was not possible.
      
      Now both triggering types can be disabled/enabled individually via
      mcetool - for example:
      * only "from-pocket"
        mcetool --set-lpmui-triggering=from-pocket
      * both "from-pocket" and "hover-over"
        mcetool --set-lpmui-triggering=from-pocket,hover-over
      * neither
        mcetool --set-lpmui-triggering=disabled
      
      Default is to enable "from-pocket" only.
      
      [mce] Add setting for selecting automatic lpm ui triggering modes. Fixes JB#20959
      eb569a0d
  23. 26 May, 2014 1 commit
  24. 25 Sep, 2013 1 commit
  25. 19 Feb, 2013 1 commit
    • spiiroin's avatar
      Allow disabling of automatic screen blanking from lock screen · f5ae869f
      spiiroin authored
      New config setting "/system/osso/dsm/locks/tklock_blank_disable".
      
      When enabled, tklock module uses longer timeouts for display
      dimming / blanking. Effectively the lock screen is shown until
      power key is pressed.
      
      The config setting can be toggled with:
        mcetool --set-tklock-noblank=enabled|disabled
      f5ae869f
  26. 02 Oct, 2012 2 commits
  27. 21 Nov, 2011 1 commit
  28. 07 Nov, 2011 1 commit
  29. 04 Oct, 2011 1 commit
  30. 06 Jul, 2011 1 commit
  31. 20 May, 2011 1 commit
  32. 12 May, 2011 1 commit
  33. 28 Jan, 2011 1 commit
  34. 16 Dec, 2010 1 commit