1. 23 Oct, 2019 1 commit
  2. 14 Aug, 2019 2 commits
  3. 13 Aug, 2019 1 commit
  4. 08 May, 2019 2 commits
  5. 07 May, 2019 1 commit
  6. 23 Apr, 2019 3 commits
  7. 18 Apr, 2019 2 commits
  8. 17 Apr, 2019 1 commit
  9. 31 Mar, 2019 1 commit
  10. 21 Mar, 2019 1 commit
  11. 28 Feb, 2019 2 commits
  12. 25 Feb, 2019 1 commit
  13. 22 Feb, 2019 1 commit
  14. 07 Feb, 2019 1 commit
  15. 15 Jan, 2019 2 commits
  16. 11 Jan, 2019 1 commit
  17. 08 Nov, 2018 2 commits
  18. 07 Nov, 2018 1 commit
  19. 01 Oct, 2018 6 commits
  20. 28 Sep, 2018 5 commits
  21. 27 Sep, 2018 3 commits
    • spiiroin's avatar
      [hybrisadaptor] Provide fallback values for select sensors. JB#43020 · a997710c
      spiiroin authored
      It is possible that on-change type sensors are not reported by android
      hal until a change is actually detected. Sensorfwd is left using zero
      initialized default values like proximity=covered / light=darkness -
      which in turn can cause various issues after each bootup.
      
      As the initial state can't be queried, choose the lest harmful option
      and define fallback values during sensor hal probing:
      - proximity sensor = not covered
      - light sensor = 400 lux
      
      If no actual sensor data has been received in a situation where sensor
      state needs to be communicated to clients, apply the fallback value.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      a997710c
    • spiiroin's avatar
      [hybrisadaptor] Subject sensor type specific actions to common policy · ed38fb45
      spiiroin authored
      Sensor specific adaptors derived from HybrisAdaptor class can be configured
      to enable/disable sensors directly via sysfs. While doing that they also
      bypass enable/disable policy that is implemented in HybrisAdaptor.
      
      Fix each HybrisXxxAdaptor class so that common policy logic is executed
      first, and direct sysfs manipulation is done based on policy decision.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      ed38fb45
    • spiiroin's avatar
      [hybrisadaptor] Refactor sensor start/stop logic · 8fab5538
      spiiroin authored
      Whether sensors should be started or stopped depends on a number
      of state variables. Using case specific conditionals at places
      where state variables might change makes the code fragile and
      hard to maintain.
      
      Separate sensor hal operations more clearly from logic and forms
      dictated by sensorfwd conventions.
      
      Use m_memberName naming convention for member variables, make
      all member data private and usable only via accessor functions.
      
      Use a single sensor start/stop policy evaluation function and
      call it from each place where relevant state variables might
      change.
      
      Use sensorfwd specific logging functions instead of qDebug etc.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      8fab5538